Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

packagecloud.io repository gives a 402 Payment Required #1054

Open
ParthKolekar opened this issue Jan 28, 2021 · 9 comments
Open

packagecloud.io repository gives a 402 Payment Required #1054

ParthKolekar opened this issue Jan 28, 2021 · 9 comments

Comments

@ParthKolekar
Copy link

The packagecloud.io repository has started to send HTTP 402 Payment Required to requests from CentOS7 builds (and as far as I tested, also for Debian builds).

This doesn't appear to be isolated to Riak, but also applies to RiakCS and Stanchion packagecloud.io deployments.

Exact error line

https://packagecloud.io/basho/riak/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 402 - Payment Required
@martinsumner
Copy link
Contributor

I have to confess, I wasn't aware of packagecloud.io, and I wouldn't expect that anyone is keeping anything riak-related up to date on there (and indeed paying for it, if payment is required). Perhaps basho kept packages up to-date there back in-the-day.

For simple pre-built packages of riak - you can download from here.

If there is value in having packages available via packagecloud.io, then perhaps ping @Bob-The-Marauder of TI Tokyo who may be able to assist in supporting this.

@ParthKolekar
Copy link
Author

packagecloud.io does provide a free hosting plan for OSS projects. They typically need a backlink to packagecloud in the project's README.md (and some pain setting up the signing process for the packages). The process is to send their support staff an email.

The official documentation : https://docs.riak.com/riak/kv/2.2.3/setup/installing/rhel-centos.1.html, points me to use packagecloud.io, so I suspect that a lot of people are currently using it and are not aware of updates / changes done in the code.

@andrealcantara
Copy link

The packagecloud.io repository has started to send HTTP 402 Payment Required to requests from CentOS7 builds (and as far as I tested, also for Debian builds).

This doesn't appear to be isolated to Riak, but also applies to RiakCS and Stanchion packagecloud.io deployments.

Exact error line

https://packagecloud.io/basho/riak/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 402 - Payment Required

i have same problema in my case with Debian Bullseyes. You have any workarround?

@martinsumner
Copy link
Contributor

See earlier comment #1054 (comment)

There is a link in that comment for downloading pre-built packages for CS as well as KV. I will ask @Bob-The-Marauder of TI Tokyo about supporting packagecloud.io going forward.

@Bob-The-Marauder
Copy link
Contributor

As a short term work around, try https://files.tiot.jp as packages can be downloaded direct from there. If you use the latest docs found at https://www.tiot.jp/riak-docs/ then all the links in there point to the packages directly. At some point, we plan to move the docs to https://www.riak.info to make things a bit more obvious but we're trying to get the docs up to date first. To the best of my knowledge, https://docs.riak.com is not under community control and is only there for historical reference.

We did start implementing repo functions with files.tiot.jp in addition to the web/ftp interfaces it already has but that's still very much WIP. If memory serves, it does work as a repo for rhel based systems (manually add as a repo) but has not had the most recent packages added to it yet. It doesn't have repo functions for Debian/Ubuntu/FreeBSD related systems yet as they use a completely different file arrangement to generate their repo files.

In the package cloud link, the path includes a link to basho. This could be an issue as Basho doesn't exist any more. In 2017, bet365 purchased all the IP rights and made them open source but didn't actually buy Basho outright to my knowledge. As such, we could probably spawn a new package cloud repo with a non-basho name but that wouldn't fix the issue with the current broken links to outdated versions of Riak.

@alandsidel
Copy link

packagecloud.io does provide a free hosting plan for OSS projects. They typically need a backlink to packagecloud in the project's README.md (and some pain setting up the signing process for the packages). The process is to send their support staff an email.

The official documentation : https://docs.riak.com/riak/kv/2.2.3/setup/installing/rhel-centos.1.html, points me to use packagecloud.io, so I suspect that a lot of people are currently using it and are not aware of updates / changes done in the code.

Same with the Ubuntu documentation at https://docs.riak.com/riak/kv/2.1.4/setup/installing/debian-ubuntu.1.html

Excuse my salt, but isn't 2 years long enough for this to have been addressed? At a minimum the page should just be removed or some sort of warning added saying the information is out of date and doesn't work. Bad and incorrect documentation is worse than none at all in cases like this.

@ParthKolekar
Copy link
Author

Some context that you might be missing here is that Basho went bankrupt, so while the software does continue to exist and receive updates from the community, the licensing might not be valid for packagecloud to offer it for free, especially when it used to be a commercial product while Basho existed (open source with paid support).

@alandsidel
Copy link

Some context that you might be missing here is that Basho went bankrupt, so while the software does continue to exist and receive updates from the community, the licensing might not be valid for packagecloud to offer it for free, especially when it used to be a commercial product while Basho existed (open source with paid support).

I did not know that Basho went bankrupt and am sorry to hear that. I suppose that means there are legal reasons they can't update/remove the documentation?

@ParthKolekar
Copy link
Author

Not a clue. But I think some of the existing maintainers can drop an email to packagecloud support and ask then if they're willing to rehost the package as a fully OSS project now.

Due to the 402, as opposed to 404 or 401 or 403....

I think that packagecloud still has their stuff setup and around.

I'm not a maintainer, but I think you could send the email with a link to this thread and there's a reasonable chance that packagecloud staff re-enable this as a fully OSS project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants