alkaris2
commented
2 years ago I get this same issue but on Arch Linux. Status 403 is returned on download.
Closed pkmnsnfrn closed 2 years ago
alkaris2
commented
2 years ago I get this same issue but on Arch Linux. Status 403 is returned on download.
cornixsenex
commented
2 years ago Was any fix found for this issue? I'm having it right now error: failed retrieving file 'dkp-libs.db' from downloads.devkitpro.org : The requested URL returned error: 403
pkmnsnfrn
commented
2 years ago Unfortunately no, I gave up and moved onto a different solution.
On Sat, Feb 5, 2022, 10:28 cornixsenex @.***> wrote:
Was any fix found for this issue? I'm having it right now error: failed retrieving file 'dkp-libs.db' from downloads.devkitpro.org : The requested URL returned error: 403
— Reply to this email directly, view it on GitHub https://github.com/devkitPro/pacman/issues/31#issuecomment-1030675484, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASMQWQPMVVSPHYDYAYERVCLUZVT45ANCNFSM5CPRPJEA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
cornixsenex
commented
2 years ago It's very strange that this had been working for me for around a year and only this morning started occuring Thanks for the input, I'll look at removing the devkitPro repo I suppose
cornixsenex
commented
2 years ago Actually it has started working again...I'm going to assume it was a server downtime issue
pkmnsnfrn
commented
2 years ago Interesting, perhaps I should try again then. Thanks for the update!
On Sat, Feb 5, 2022, 10:40 cornixsenex @.***> wrote:
Actually it has started working again...I'm going to assume it was a server downtime issue
— Reply to this email directly, view it on GitHub https://github.com/devkitPro/pacman/issues/31#issuecomment-1030677726, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASMQWQJELMIP4G5642FX4S3UZVVLVANCNFSM5CPRPJEA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
WinterMute
commented
2 years ago 403 is permission denied. It could be anything from your ISP's "parental controls" to doing something that's triggered filters. Depending on how much abuse and harassment I've been subjected to recently it might be possible to convince me to look & see if you've triggered a ban and whether or not it might be unfortunate collateral damage.
pkmnsnfrn
commented
2 years ago The machine in question is a remote machine (a Windows 365 cloud PC to be exact) so it could either be collateral damage or Microsoft's ISP... Oh well. Happy to try to help investigate if need be.
On Sat, Feb 5, 2022, 11:03 Dave Murphy @.***> wrote:
403 is permission denied. It could be anything from your ISP's "parental controls" to doing something that's triggered filters. Depending on how much abuse and harassment I've been subjected to recently it might be possible to convince me to look & see if you've triggered a ban and whether or not it might be unfortunate collateral damage.
— Reply to this email directly, view it on GitHub https://github.com/devkitPro/pacman/issues/31#issuecomment-1030681216, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASMQWQKJFX2G5YEXACTWFYLUZVX6LANCNFSM5CPRPJEA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
WinterMute
commented
2 years ago In some cases people are getting banned because, for some ridiculous reason, they feel it necessary to run a script checking for updates several hundred times a day. This has a negative impact on other users so, if you're running a cron script to run `dkp-pacman -Syu' more than once a day then please stop.
In other cases people are using pacman to install every single binary we provide for every single commit they make as part of their CI. Please don't do this either. This has led to banning of CI infrastructure which has impacted on Windows 365 cloud PC. We provide docker images for CI purposes, please use those. https://hub.docker.com/u/devkitpro
Other users are just leeching everything we do and hosting our binaries elsewhere despite being asked not to. Not only that but they are providing instructions to use their binaries in preference to our CI in a way that is incompatible with our infrastructure purely in order to not update their projects to work with our stock tools. This causes massive support issues for us and mires users who follow their instructions in technical debt that is incredibly difficult to dig them out of.
Unfortunately this means that some innocent users may have ended up banned which we regret. It may be possible, as I've said, to get some bans lifted but bear in mind that we have no way to tell if you are genuinely innocent or a user who wants to get unbanned in order to carry on one of the problematic activities listed above.
Istador
commented
1 year ago In other cases people are using pacman to install every single binary we provide for every single commit they make as part of their CI. Please don't do this either. This has led to banning of CI infrastructure which has impacted on Windows 365 cloud PC. We provide docker images for CI purposes, please use those. https://hub.docker.com/u/devkitpro
Please make this more prominent. E.g. on the wiki page that is linked in the issue description and/or on the Getting Started page. As far as I see the only mentioning of the docker registry on the wiki is on the About page that no one's gonna read.
WillSams
commented
1 year ago In some cases people are getting banned because, for some ridiculous reason, they feel it necessary to run a script checking for updates several hundred times a day. This has a negative impact on other users so, if you're running a cron script to run `dkp-pacman -Syu' more than once a day then please stop.
In other cases people are using pacman to install every single binary we provide for every single commit they make as part of their CI. Please don't do this either. This has led to banning of CI infrastructure which has impacted on Windows 365 cloud PC. We provide docker images for CI purposes, please use those. https://hub.docker.com/u/devkitpro
Other users are just leeching everything we do and hosting our binaries elsewhere despite being asked not to. Not only that but they are providing instructions to use their binaries in preference to our CI in a way that is incompatible with our infrastructure purely in order to not update their projects to work with our stock tools. This causes massive support issues for us and mires users who follow their instructions in technical debt that is incredibly difficult to dig them out of.
Unfortunately this means that some innocent users may have ended up banned which we regret. It may be possible, as I've said, to get some bans lifted but bear in mind that we have no way to tell if you are genuinely innocent or a user who wants to get unbanned in order to carry on one of the problematic activities listed above.
You could have just mentioned the Docker images for CI purposes :P
I am following the instructions from https://devkitpro.org/wiki/devkitPro_pacman.
After running
sudo gdebi devkitpro-pacman.amd64.debcat /proc/versionreturnsand lsb_release -a returns
Google leads to https://github.com/devkitPro/pacman/issues/22#issue-653659360, but I am not using a CI workflow (I'm not super familiar with the concept, but a cursory glance of wikipedia tells me this is not what i'm doing). Am I doing something wrong, or is something broken on server side? Thanks!