On Mon, Nov 29, 2021 at 09:11:48AM -0500, Neal Gompa wrote: > On Mon, Nov 29, 2021 at 9:04 AM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > > > > On Mon, Nov 29, 2021 at 07:00:30AM -0500, Neal Gompa wrote: > > > If Fedora and EPEL were to have older versions, we'd have to have a > > > dedicated CDN endpoint for them, because mirrors would seriously have > > > trouble taking it. > > > > How often would such packages be used? If we had a non-default repo > > available but not enabled by default, it could be optional to mirror and > > probably still be okay. So, we actually do have this for fedora updates today. We had to set it up to solve an issue with the updates flow and CoreOS. See the fedora-updates-archive subpackage of fedora-repos. This is hosted on amazon S3, behind cloudfront. > I suspect it would be fairly heavily used. There are significant > benefits to having those: > > * DeltaRPM would be considerably more useful In order to have deltarpms the packages would have to be available at compose time and in the same repo. > * "dnf history undo" would actually work > > We could make it non-default and tell people that rollbacks require an > --enablerepo= option, though. This would work for Fedora now with the archive repo above. I suppose we could look at setting up a similar setup with epel. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
