i used the same method in my software
Hi @pauby :) Concerning Issue chocolatey/chocolatey.org#687 about Tor Exit nodes. I just tested from about 10 various exit nodes. It's still 403 forbidden on the API no matter what.
2 replies
(hCaptchas are not required on the chocolatey.org website from a Tor Browser but are required when accessing the API). So there is no issue accessing the website in itself from Tor. Just the API URL.
Hello! I work at Electronic arts, managing an internal service that caches chocolatey (among other things) and starting today we're getting HTTP response 403 when trying to reach chocolatey. I've created a support ticket for this, but a colleague suggested I'd reach out here. Anyone up for a chat about why this happened and what we can do to get unblocked?
@misse ^^
hi new to chocolatey. hope all is well. I have a question..I recently install a software called kate (program editor app). I did not like it so i uninstalled using the choco command "choco uninstall kate". However, it did uninstall it from programs & features but I still notice some files under appdata\local & C:\programdata\chocolatey. What is the safest way to remove these kate files from my system? Also, when i right click on a file, i still notice the phrase "Edit with kate"? If i unistall the software shouldnt this be removed? Anyway how to i remove this from the system?
Hello Everyone, I'm new to chocolatey. Chocolatey is not using skip tokens for FindPackagesById if we have many versions. The issue is with only the virtual repository. It's working as expected for the Remote repository.
Scenario 1: Package(git) has 70+ versions, repository type is remote.
choco install git -y
fiddler logs:
/api/nuget/choco
/api/nuget/choco/$metadata
/api/nuget/choco/Packages()?$filter=(tolower(Id)%20eq%20'git')%20and%20IsLatestVersion
/api/nuget/choco/FindPackagesById()?id='git.install'
Scenario 2: Package(git) has 70+ versions, repository type is virtual.
choco install git -y
fiddler logs:
/api/nuget/chocolatey
/api/nuget/chocolatey/Packages(Id='git',Version='2.30.0.2')
/api/nuget/chocolatey/$metadata
/api/nuget/chocolatey/FindPackagesById()?id='git.install'
/api/nuget/chocolatey/FindPackagesById?id='git.install'&$skiptoken='git.install','2.15.0'
/api/nuget/chocolatey/FindPackagesById?id='git.install'&$skiptoken='git.install','2.5.2'
/api/nuget/chocolatey/Download/git/2.30.0.2
Hello everyone. I am new to open source. Can anybody help me with this issue.fossasia/pslab-desktop#653
14 replies
This is the commit I made fossasia/pslab-desktop#659
But not sure what went wrong.
Hi everyone, we have packaged our application using chocolatey and it has been working fine for us. but recently we're seeing message like "ShimGen has successfully created a shim for jaccessinspector.exe".. and then it failed with the non-zone return code... but looks like the packages already installed. just wondering if anyone had such issue before?
1 reply
One option is to use the
choco source add command to add the repository, using --user and --password arguments to specify the login; then Chocolatey Gui will pick up that source because it uses the same config that choco.exe uses. The other option is to go into the Chocolatey GUI settings, go over to the sources tab, and set the username and password for the repository source that needs it.
For docker-desktop we're facing the problem that the program auto-updates itself which seem to break subsequent updates on the choco package. My idea is to check in the install & uninstall script for the actual installed version and skip further processing when it already matches for the install and skip when it doesn't match for the uninstall. Is this a normal thing to do?
2 replies
Hello. I maintain a small package for a soft that sees several years between releases, so I have to relearn things every time. I'm trying to push a new version, and it's -I think- the first time I have to do it through choco push rather than the website. However, even after setting up my API key, I still have a 403 while pushing (the full error message is simply "forbidden"). My IP is not listed at projecthoneypot, I'm a single user who don't use Chocolatey often enough to have any sort of temporary ban. Is that a known problem for packages that have only been updated through the web site, am I out of luck ?
I've got a question, and maybe I should direct this to the Ansible team, but here goes. I use Ansible to install chocolatey packages on a remote host -- it works fine. I've created my own chocolatey packages as well. All 3 work when I run them locally with
choco install PACKAGES -s .. 2 out of the 3 work fine when invoked using the win_chocolatey module as well. But one is not working.
The only difference in the one that isn't working is that it requires an AutoHotKey (AHK) script to handle the install. Again, it works fine when I invoke it locally, but doesn't seem to work when invoked with Ansible.
I checked the logs and it gets stuck at:
2021-01-24 23:05:05,944 6084 [INFO ] - Installing orthocad...
2021-01-24 23:05:05,990 6084 [DEBUG] - Running Start-ChocolateyProcessAsAdmin -validExitCodes '0' -workingDirectory 'C:\tmp\chocolatey\orthocad\1.0' -statements ' ' -exeToRun 'C:\tmp\chocolatey\orthocad\1.0\iTero_Online_Setup_5.9.1.20.exe'
2021-01-24 23:05:05,990 6084 [DEBUG] - Unable to use current location for Working Directory. Using Cache Location instead.
2021-01-24 23:05:06,005 6084 [DEBUG] - Test-ProcessAdminRights: returning True
2021-01-24 23:05:06,020 6084 [DEBUG] - Elevating permissions and running ["C:\tmp\chocolatey\orthocad\1.0\iTero_Online_Setup_5.9.1.20.exe" ]. This may take a while, depending on the statements.
It does have a dependency on Autohotkey, in which i have autohotkey.portable installed via chocolatey
seen that happen a few times on automated ci systems, usually the cause from what I have seen is that you can not use any mouse click handlers in the autohotkey script
This particular installer should pop up on the screen but it never does when invoked with Ansible
The installer for the exe itself that is (not AHK)
I will try to remove the AHK script and see if it will at least launch the installer
hmm, sounds like a problem with the launch procedure when used trough ansible then, and not the autohotkey script.
I am afraid that I have very limited experience with ansible, so if the problem only occurs during the install through ansible I am not able to help in that case.
There are other people in the community with experience of ansible that can be of help, but I believe there will still be a few hours before they come on...
I am afraid that I have very limited experience with ansible, so if the problem only occurs during the install through ansible I am not able to help in that case.
There are other people in the community with experience of ansible that can be of help, but I believe there will still be a few hours before they come on...
Gotcha! Thank you Kim! It's not really a rush, but I would love to understand what's going on. I removed the invocation of the AutoHotKey script and tried it again with this particular package and it's still not getting passed that last step,
Elevating permissions and running. So that at least rules out AHK. Not yet sure why it can't move any further. Other packages install and work just fine with Ansible/chocolatey...