Re: Handling packages with missing dependencies provided by HA-RS repos?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Fri, 25 Mar 2022 at 00:25, Carl George <carl@xxxxxxxxxx> wrote:
On Thu, Mar 24, 2022 at 5:50 PM Kevin Fenzi <kevin@xxxxxxxxx> 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@xxxxxxxxxx> 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.]

--
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
_______________________________________________
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

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux