chocolatey-community / chocolatey-packages Goto Github PK

The installer for clipgrab appears to include the OpenCandy adware.

I’ve experienced that this OpenCandy Adware stuff never installs when the installer is run in silent mode, so this package should be safe.

We should add a note to the package description about this.

Set a packagename.ketarin.xml file in each folder - This gives folks the ability to make fixes that can be imported out of band versus attempting to put a merge against a binary file. It also promotes discussion due to the increased visibility.

Right now folks really don't have the ability to fix the ketarin jobs in a way that is maintainable besides linking to gists, as @TomOne did in #11.

The latest build is 44.0.2389.0 !

The seafile-client package throws an 1603 error when the same version is already installed.

When updating the PDFCreator package, the settings (e.g. printers, profiles) are lost after each update. This needs to be fixed.

ok, what has changed with this repository...

I have just done a fresh git clone, and immediately all 358 files are marked as changed:

I haven't changed anything in my git configuration, so something must have changed in this repository, unless anyone can think of something else.

What do we need to add to the gitattributes file to solve this problem? I can only assumed that the issue is to do with line endings, when shared between *nix and windows.

@Redsandro @TomOne @ferventcoder

The python*-packages throw 1603 errors under certain circumstances. We need to investigate and fix that.

Many corporate firewalls block FTP connections. Would it be possible to set the HTTP mirror as a default, or make it configurable?

I've also found this comment:
https://chocolatey.org/packages/cyg-get#comment-1800404245

Apparently the FTP mirror is already announced deprecated in the cygwin package: https://chocolatey.org/packages/cygwin

Will have to fix up the ketarin query, as the layout of the page must have changed.

It's here: https://github.com/chocolatey/chocolatey-coreteampackages/tree/master/automatic/sidesync

https://github.com/adgellida/chocolateyautomaticpackages

Edit git config files to not include my email address as default.

This commit broke the package icons again: 9acf17b 😄

I would highly suggest to create a gh-pages branch in this repository and store the icons there. Then you wouln’t have any problems at changing the folder hierarchy/renaming icons. I did that already in my repository: https://github.com/tomone/chocolateyautomaticpackages

Many developer tools require bash-style shells in order to function, but chocolatey currently is only available in batch form.

Could we add support for cygwin shells? E.g. by dropping in a shell script in addition to each batch file, e.g. https://gist.github.com/mcandre/5467825.

As per this conversation:

http://chocolatey.org/packages/rdcman#comment-1596433702

I am trying to create the package LightAlloy but I cannot figure out how to get the download link from fosshub because the functionality changed.

This problem also impacts Classic-Shell and MkvToolNix on the core repo.

Can anyone figure out how to change this?

This also reminds me of the benefit to have helpers for certain sites, as discussed here: chocolatey-archive/chocolatey#377

If fosshub was a helper, updating the helper would update all affected packages. (Except of course for the ketarin regex/download script.)

Unable to install Cygwin package when a proxy is necessary.

Cywgin is installed via an external installer that is referred to as the installerFile. chocolateyInstall.ps1 does not forward any detected proxy settings onto the installerFile which is needed when Chocolately is using a proxy. The cygwinInstall.exe command line arguments needed is --proxy

Got this comment in an email (however I don't see it on disqus):

Dear all,

I used to use Pale Moon 25.2.1 and wanted to update to 25.3.0 by cup. It failed though. Well it actually is installed and it works. But clist -lo doesn't show up palemoon. And cinst -force palemoon always fails. I put the log as enclosure.

Thank you for any help and work.

Gunner

2015-03-22 10:59:30,891 [INFO ] - ============================================================
2015-03-22 10:59:30,912 [INFO ] - Chocolatey v0.9.9.2
2015-03-22 10:59:30,967 [INFO ] - Installing the following packages:
2015-03-22 10:59:30,973 [INFO ] - palemoon
2015-03-22 10:59:30,974 [INFO ] - By installing you accept licenses for the packages.
2015-03-22 10:59:32,511 [INFO ] - 
palemoon v25.3.0 (forced)
2015-03-22 10:59:32,580 [INFO ] - Found 'chocolateyInstall.ps1':
2015-03-22 10:59:32,582 [INFO ] - 
$packageName = 'palemoon'
$installerType = 'exe'
$url = 'http://relmirror.palemoon.org/release/palemoon-25.3.0.win32.installer.exe'
$url64 = 'http://www.fosshub.com/genLink/Pale-Moon/palemoon-25.3.0.win64.installer.exe'
$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
$validExitCodes = @(0)
$pwd = "$(split-path -parent $MyInvocation.MyCommand.Definition)"

Combatibility - This function has not been merged

if (!(Get-Command Get-UrlFromFosshub -errorAction SilentlyContinue)) {{{{
Import-Module "$($pwd)\Get-UrlFromFosshub.ps1"
}}}}

$url = Get-UrlFromFosshub $url
$url64 = Get-UrlFromFosshub $url64

Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" "$url" "$url64" -validExitCodes $validExitCodes

2015-03-22 10:59:32,596 [INFO ] - 
Do you want to run the script? 
NOTE: If you choose not to run the script, the installation will 
fail.
Skip is an advanced option and most likely will never be wanted.

2015-03-22 10:59:32,597 [INFO ] - 1) yes
2015-03-22 10:59:32,599 [INFO ] - 2) no [Default - Press Enter]
2015-03-22 10:59:32,599 [INFO ] - 3) skip
2015-03-22 10:59:36,318 [ERROR] - Cannot index into a null array.
2015-03-22 10:59:36,320 [ERROR] - At C:\ProgramData\chocolatey\lib\palemoon\tools\Get-UrlFromFosshub.ps1:13 char:
2015-03-22 10:59:36,321 [ERROR] - 3
2015-03-22 10:59:36,322 [ERROR] - + $fosshubAppName = $Matches[1]
2015-03-22 10:59:36,323 [ERROR] - + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2015-03-22 10:59:36,323 [ERROR] - + CategoryInfo : InvalidOperation: (:) [], RuntimeException
2015-03-22 10:59:36,324 [ERROR] - + FullyQualifiedErrorId : NullArray
2015-03-22 11:00:04,832 [INFO ] - Installing palemoon...
2015-03-22 11:00:26,404 [INFO ] - palemoon has been installed.
2015-03-22 11:00:26,454 [ERROR] - palemoon install not successful.
2015-03-22 11:00:26,457 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\palemoon\tools\chocolateyInstall.ps1'.
See log for details.
2015-03-22 11:00:28,471 [WARN ] - 
Chocolatey installed 0/1 package(s). 1 package(s) failed.
See the log for details.
2015-03-22 11:00:28,473 [ERROR] - Failures:
2015-03-22 11:00:28,475 [ERROR] - - palemoon

This comment has been added to the disqus forum thread for palemoon.

Package Url: http://chocolatey.org/packages/palemoon
Comment Url: http://chocolatey.org/packages/palemoon#comment-1921466149

I'm not sure what is going on here. I believe fosshub has changed. This could be fixed globally if fosshub was a global helper.

chocolatey-archive/chocolatey#377

The keepassx-langfiles package contains languages for the keepass-classic package. The package name has been changed as per request:

https://github.com/Redsandro/chocolatey/issues/14

The keepassx package now contains the actual KeePassX Qt port of KeePass Classic

I think it is not specified which prerequisites a package must have to be accepted and pulled into this repo (in addition to the existing guidelines for contributing of course). That is a quite important matter, therefore we should specify it and write it into the README.md of this repo.

How about these prerequisites?

1. At least one member of the Chocolatey core team must be interested into the package to get it added to the core team packages repo. Therefore, before making pull requests for adding new packages to this repo, open an issue to ask if it can be added.
2. This repository is not indented as place to host random orphaned packages or package where the original maintainer is no longer interested to keep the package. Prerequisite 1 must be applicable to such packages.

This seems quite obvious, but nevertheless I’d add it (or a grammatically improved version) to the README.md.

Thoughts?

New version has been released:

http://blogs.technet.com/b/rmilne/archive/2014/11/19/remote-desktop-connection-manager-download-rdcman-2-7.aspx

It would be very useful to be able to install cygwinports packages via cyg-get.
At least there should be way to pass additional options (i.e. -K http://cygwinports.org/ports.gpg) to cygwinsetup.exe.

The thunderbird package needs the same fixes as Firefox in 2e3a83b.

The download link does no longer work

Currently I use https://rawgit.com/ (production links) for my package icons in my repo. Although the service is still beta, it works very well. I never had problems with it.

As you probably know, using raw links to resources on GitHub directly – as most package maintainers do now – is not recommendable, because it has these drawbacks:

• It’s not nice to GH, because the requests have to go through their backend. GH raw links are not indended to be used like a CDN anyways.
• GH temporarily blocks raw links if they have too much traffic.
• Raw links don’t serve the correct Content-Type for most file types.

Some time ago I used a GitHub pages branch to serve the icons, but also that solution didn’t satisfy my. It makes it more complicated for contributors to contribute to a package, because then the have to make 2 pull requests in 2 different branches.

A big advantage of using http://cdn.rawgit.com is that once the link to an icon is set up, there will never be a 404 error, even if the icon gets removed from the repo or moved to another location.

So my question is if it’s OK for you if I leave cdn.rawgit.com for my package icons and if also the other packages in this repo can be adapted to use it.

I know, this change won’t be relevant forever. I see that there are plans to serve the icons directly from the gallery itself. That’s a very good idea.

But until that is implemented I’d find it good to use cdn.rawgit.com for package icons.

As noted in #11, I would like for the _output folder to be checked in. This aids folks in providing fixes to the released packages in case there is an issue and a package is broken.

https://github.com/chocolatey/chocolatey-coreteampackages/blob/master/automatic/audacity/tools/chocolateyInstall.ps1#L5

The chromium package is not updating.

I have these packages that I no longer use, e.g. Ext2Explore, or partition tools, which have apparently too many users who keep bugging me for updates.

So I thought, nice packages for Core Team packages. But the process is vague. All the repo says is this:

These packages are managed by the chocolatey core team. To get a package added here, the official Chocolatey Account has to have push access to the package on chocolatey.org.

So I added the chocolatey user, but basically the feedback I get is:

This is not a dumping ground for offloading packages that folks are no longer interested in maintaining.

However, for my package KeePassX I was approached by someone advising me to put it on core team packages because I don't update fast enough.

So how does this work? Is the process of packages that get or would get accepted arbitrary? Subjective to the people that are "in" the core team?

This needs a wiki with clear instructions on how to get a package nominated, accepted, added, how to transfer the package, how to transfer the package source code, if and how to request help when your package is not an autopackage, etc.

For now, for some of the most popular packages I have found some random other users who were willing to host the autopackage. But in the light of trustworthiness and the future plan of trusted certificates for package maintainers, the core team would me a safer bet.

Also, who are the core team members?

• TomOne
• gep13
• ferventcoder

The javaruntime* package should really install the latest version of JRE. Many packages on Chocolatey.org take dependency on that package and it isn’t nice that it installs JRE 7, even if all these programs would work with JRE 8 too.

We need to figure out a proper way how the javaruntime* packages should work.

For some reason, the iTunes package is missing the 64-bit URL. Moderation URL: https://chocolatey.org/packages/iTunes/12.1

The packages for Google Chrome should really include a note that it is not possible to install older versions of Google Chrome.

Google does not offer older versions of Chrome and third party sources, e.g. http://www.oldapps.com/, http://filehippo.com/ also seem to be forced to do the same.

So there’s no way to get older versions of Chrome.

Or anything else that signifies we need action from the people with access to the batch (for now ketarin) machine.

Common packages on which a lot of packages (should) depend on should be part of the core packages. Namely Visual C++ redistributables:

• vcredist2005 - https://chocolatey.org/packages/vcredist2005
• vcredist2008 - https://chocolatey.org/packages/vcredist2008
• vcredist2010 - https://chocolatey.org/packages/vcredist2010
• vcredist2012 - https://chocolatey.org/packages/vcredist2012
• vcredist2013 - https://chocolatey.org/packages/vcredist2013
• vcredist2015 - https://chocolatey.org/packages/vcredist2015

Right now it seems that almost all packages which depend on the Visual C++ runtime, individually install it either in the bootstrapper or as a merge module in the MSI file.

Making the redistributables available as maintained packages would make it easier for these packages to split up the dependencies.

Command cyg-get pkg1,pkg2,pkg3 doesn't do what it should.
It runs

"C:\tools\cygwin\cygwinsetup.exe" -q -N -R C:\tools\cygwin -l C:\tools\cygwin\packages -s ftp://mirrors.kernel.org/sourceware/cygwin -P "pkg1 pkg2 pkg3"

instead of

"C:\tools\cygwin\cygwinsetup.exe" -q -N -R C:\tools\cygwin -l C:\tools\cygwin\packages -s ftp://mirrors.kernel.org/sourceware/cygwin -P "pkg1,pkg2,pkg3"

I had to run cyg-get 'pkg1,pkg2,pkg3' to get correct result.
At least it should be documented as temporary work-around.

I wanted to download the new blender by updating to 2.73, and noticed it only updates to 2.72.2.

I noticed the chocolatey user but the update is not available.

1. Why doesn't blender update?
2. Does the big ketarin machine a name for referencing or should we give one?
3. Can we make packages show which user uploaded a certain version? (For example, I could see if the chocolatey user in fact did all the latest releases)

The package doesn’t update anymore.

The package didn’t update to v2.6.9.

@gep13, it wasn’t a good idea that you deleted your ChocolateyAutomaticPackages repository. The icons of these packages were stored in this repository and now they no longer exist.

I suggest that you recreate that repository and remove everything except the icons. I hope that you don’t think that package icons are irrelevant. 😄

Currently the package updater creates a folder for each package version in _output. This bloats the repo and isn’t necessary, because the files are versioned with Git. Therefore it’s better to only keep the latest version in _output of each package and make an automatic commit after each package update.

The Python package is a good candidate for installation into %ChocolateyInstall%, instead of the current Get-BinRoot. It's essentially self-contained and it only places two binaries in the PATH, python.exe and pythonw.exe, both of which can be shimmed into %ChocolateyInstall%\bin. This also has the effect of consolidating one more directory in the PATH into %ChocolateyInstall%\bin.

Hi, I've installed cyg-get via $cinst cyg-get
but whenever I try to install package, for ex: cyg-get.bat openssh, it writes to console :
"Attempting to install 'openssh' to C:\Cygwin\packages' " and exits immediately.
As a result folder C:\Cygwin\packages' stays empty.

Currently it misuses the install arguments override to achieve that.

Same story with thunderbird.

This should be updated to match the icon that @ferventcoder is using in the fiddler package.

Cygwin's site seems to have two separate setup files now: setup_x86 and setup_x86_64, as seen here http://cygwin.com/install.html

The original setup.exe that this package queries no longer exists.