Hi Michael, thank you for the feedback! We will look for an internal solution in this case.
Kind regards, Stijn ________________________________ From: Michael Shuler <mshu...@apache.org> Sent: Friday, March 18, 2022 18:19 To: user@cassandra.apache.org <user@cassandra.apache.org> Subject: Re: Apache archive RedHat repodata CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. On 3/18/22 02:31, Stijn Vanden Brande (External) wrote: > > The solution should be simply running `createrepo` after the new package > is added in archive repository to have the correct repo data. You stated the issue in your initial observation. The contents of archive.a.o are an automated ASF-wide rsync from downloads.a.o. There is no human to run `createrepo` on the archives. Nor would the addition of some sort of post-rsync script work for all Apache Software Foundation projects, as this would be error prone. It is a rolling archive of all ASF current release artifacts. That's it. If users have a need to follow a specific version for their clusters, the recommendation has always been that they download the specific artifacts they need, verify sigs, etc. and toss them on their own web server, using the package repository tools they like for deb/rpm packages. It is very common for database clusters to have no direct internet access at all, and for nodes to have an internal-only web server in the infrastructure with their "golden" cluster package repository. Test test test some new version in dev or from the public repos, then upload those verified packages to the "golden" repo for production deployment. Done. There is no simple way to do this on archive.a.o, so you'll have to do this yourself, which ends up being way more stable and predictable in the long run. It's a great question that comes up from time to time, it just hasn't been asked recently. Warm regards, Michael Worldline and Ingenico Group are registered trademarks and trade names owned by the Worldline Group. This e-mail and any documents attached are confidential and intended solely for the addressee. If you are not the intended recipient of this e-mail, you are not authorized to copy, disclose, use or retain it. Please notify the sender immediately and delete this e-mail (including any attachments) from your systems. As e-mails may be intercepted, amended or lost, they are not secure. Worldline and its subsidiaries therefore cannot accept liability for any errors in their content. Although the Worldline Group endeavours to maintain a virus-free network, we do not warrant that this e-mail is virus-free and do not accept liability for any damages or losses resulting from any transmitted virus if any. The risks are deemed to be accepted by anyone who communicates with Worldline or its subsidiaries by e-mail.
