https://chocolatey.org (the community feed) - Keep questions related to the community feed please
@dufferzafar: Would the
telegram.portable package work for you? https://chocolatey.org/packages/telegram.portable
@paulppp2008: Are you talking about the Chocolatey.Server? If so, the issues for that are over here: https://github.com/chocolatey/simple-server/issues
Plz help! https://chocolatey.org/packages/7zip-zstd/1.4.5.40 https://chocolatey.org/packages/lzip7z/1.6 https://chocolatey.org/packages/gping/0.1.7 waiting for review 2 month already
It often helps to just discard chocolatey downloading the package and instantly re-do the download to have it speeded up
like trying download 4-5 times and then set the download timeout much longer
@paradonym: There is the
webRequestTimeoutSeconds config option, I'm not %100 sure that that is what you are wanting.
@pauby please don't forget this one too (https://chocolatey.org/packages/admobilize-vision-service/1.5.1.0) ;) Thank you
Nevermind it finally worked
Byeeee
I'm getting a new computer in a few weeks, is there a way for me to get a list of the choco packages I installed in my current computer and then install everything with a single command (or small script) in the new computer?
I was checking the documentation but didn't see anything like that
Does anyone knows what is the error here? https://gist.github.com/choco-bot/68319f09f5e52f02305695bc9267a081 I can't find any and it still fails the verification.
@Supermouse: There is no way through choco currently, however there is work under way for an export command.
I would suggest using this package instead: https://chocolatey.org/packages/choco-package-list-backup
That will generate a
packages.config file, which you can install in one command; choco install /path/to/packages.config
@ericoporto: It looks like the verifier is timing out, due to the dependencies taking too long to install. I would suggest asking for an exemption from the verifier.
@Nick1023822Who_twitter: Hi
hi, we keep our packages in our private feed and I am looking for a way to reserve a prefix like
https://docs.microsoft.com/en-us/nuget/nuget-org/id-prefix-reservation
Is there a way to accomplish this as a security measure to prevent "dependency confusion" ? https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610
MyCompany* for the chocolatey.org feed, like it can be done for nuget.org.https://docs.microsoft.com/en-us/nuget/nuget-org/id-prefix-reservation
Is there a way to accomplish this as a security measure to prevent "dependency confusion" ? https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610
14 replies
not work i should say sorry
I've a small issue. I want to push a update of a packet and I get a error message: "It's possible the package version already exists on the repository."
Take a look please:
PS F:\GitHub\chocolatey-packages\powerautomatedesktop> choco push .\powerautomatedesktop.2.3.2121.nupkg
Chocolatey v0.10.15
Attempting to push powerautomatedesktop.2.3.2121.nupkg to https://push.chocolatey.org/
An error has occurred. It's possible the package version already exists on the repository.
Take a look please:
PS F:\GitHub\chocolatey-packages\powerautomatedesktop> choco push .\powerautomatedesktop.2.3.2121.nupkg
Chocolatey v0.10.15
Attempting to push powerautomatedesktop.2.3.2121.nupkg to https://push.chocolatey.org/
An error has occurred. It's possible the package version already exists on the repository.
PS: I'm the Package Maintainer.
Link: https://chocolatey.org/packages/powerautomatedesktop/
Link: https://chocolatey.org/packages/powerautomatedesktop/
I have just unrejected it, so you should now be able to push it with the same version
New version has been successfully pushed :)
@djschumacher: Assuming that the automated checks pass, it will go in a queue for a human moderator to look over it. Then, assuming no changes are needed, the package will be approved, making it available. The queue is a bit long at the moment, in the ballpark of three weeks.
Here is the full documentation for the process: https://docs.chocolatey.org/en-us/community-repository/moderation
And here is the link to the queue of packages to review: https://chocolatey.org/packages?q=&moderatorQueue=true&moderationStatus=all-statuses&prerelease=false&sortOrder=package-download-count
You can install it immediately if you explicitly specify the version. Like
choco install sonicwallnetextender --version=10.2.300 or similar. Keep in mind that until the package is approved, that it is not immutable, and that if changes are required during the review, you may have an old "version" of that version of the package installed on your local machine(s).
Hi, I am trying to install dotnet 4.7.2 using "choco install dotnet4.7.2" but it looks like it is only downloading the dependent packages and not doing the actual installation of dotnet 4.7.2. I am seeing this message while running the command: The install of dotnetfx was successful. Software install location not explicitly set, could be in package or
default install location if installer. Can someone please help me on this.
default install location if installer. Can someone please help me on this.
@neerajsingh315: The dotnet4.7.2 package is a legacy package id, and is kept around to point people and scripts at the dependency dotnetfx, which the the package that actually installs dotnet.
I'm creating a Choco package for an open-source app. I understand packages that contain $url in them. 👍
However, the docs also recommend embedded binaries. It points to the example https://github.com/chocolatey-community/chocolatey-coreteampackages/tree/master/automatic/qbittorrent
Its install script has:
but I don't actually see any binaries in that repo folder. Where are the binaries/how does the install script locate them at install time? If there is documentation, code, or a thread I should look at please let me know, thank you! 🙏
However, the docs also recommend embedded binaries. It points to the example https://github.com/chocolatey-community/chocolatey-coreteampackages/tree/master/automatic/qbittorrent
Its install script has:
file = "$toolsDir\qbittorrent_4.3.3_setup.exe"
file64 = "$toolsDir\qbittorrent_4.3.3_x64_setup.exe"but I don't actually see any binaries in that repo folder. Where are the binaries/how does the install script locate them at install time? If there is documentation, code, or a thread I should look at please let me know, thank you! 🙏
@rlatm Generally, embedded binaries are not commited to the source repository for the package, but only are on the local machine where the package is packed and pushed. So if you look on chocolatey.org, the installers are there: https://chocolatey.org/packages/qbittorrent#files