[CentOS-devel] Handling packages retired in epel but not yet available in CentOS?
Nico Kadel-Garcia
nkadel at gmail.comThu May 14 23:59:57 UTC 2020
- Previous message: [CentOS-devel] [EPEL-devel] Re: Handling packages retired in epel but not yet available in CentOS?
- Next message: [CentOS-devel] Handling packages retired in epel but not yet available in CentOS?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, May 14, 2020 at 3:32 PM Michel Alexandre Salim <michel at michel-slm.name> wrote: > > Hi, > > We're working on validating CentOS 8 for some desktop use cases at work, > and noticed that after working fine on a machine that's installed > several months ago, it's now failing on a freshly-installed machine. Do not get me *started* on the ansible version fun and games, or the confusing state of the python3 for various EPEL, RHEL and CentOS migrations. The situation is exacerbated when RHEL elects to use a kind-of-sort-of distinct naming scheme for software previously published via EPEL. It's an ongoing problem. EPEL's decision to show only the most recent versions of RPMs, and to trim old RPMs out, is a destabilizing problem and why I make hrdlinked snapshots of EPEL using "rsnapshot" for internal access to old packages.
- Previous message: [CentOS-devel] [EPEL-devel] Re: Handling packages retired in epel but not yet available in CentOS?
- Next message: [CentOS-devel] Handling packages retired in epel but not yet available in CentOS?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS-devel mailing list