On Thu, Mar 24, 2022 at 5:50 PM Kevin Fenzi <kevin@scrye.com> wrote:
>
> On Wed, Mar 23, 2022 at 09:18:08PM -0500, Carl George wrote:
> > On Wed, Mar 23, 2022 at 2:54 PM Carl George <carl@redhat.com> wrote:
>
> Also could we tell if deps changed? Say I have foo-plugin in epel
> Reccommending foo, and RHEL drops foo. None of our 'will it install' or
> broken deps type checks will know that it is now not working. ;(
As far as I know RHEL doesn't really drop packages, they stay on the
CDN for the life of distro. Even if they do get dropped, this seems
like an edge case we shouldn't really need to worry too much about.
If it happens and it results in an EPEL package not working, we'll
know it should have been a Requires and not a Recommends all along,
which will lead to either the maintainer adding the necessary
dependency to EPEL, or retiring the package with the missing
dependency.
RHEL doesn't drop any packages from the CDN without a major item. Various packages which have already gone past their 'Appstream lifecycle' in 8 are still there. The problem was one of two places. One, the CentOS rebuild which only kept the latest in their dot releases. Two, the scripts Fedora used to reposync from the mirrors usually got only the latest from a dot branch which would drop certain packages when they were 'removed'. The second was fixed when we no longer synced from /X.Y/ but only with /X/, this then keeps the older packages. [I had switched to syncing X.Y so we would be better able to deal with dot releases breaking CentOS users but that was seen as breaking koji in other ways so we went back to the X method.]