On Mon, Jun 22, 2020 at 02:36:20PM +0200, Miro Hrončok wrote: > The following packages are orphaned and will be retired when they > are orphaned for six weeks, unless someone adopts them. If you know for sure > that the package should be retired, please do so now with a proper reason: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > Note: If you received this mail directly you (co)maintain one of the affected > packages or a package that depends on one. Please adopt the affected package or > retire your depending package to avoid broken dependencies, otherwise your > package will be retired when the affected package gets retired. > > Request package ownership via the *Take* button in he left column on > https://src.fedoraproject.org/rpms/<pkgname> > > Full report available at: > https://churchyard.fedorapeople.org/orphans-2020-06-22.txt > grep it for your FAS username and follow the dependency chain. > sysfsutils orphan 2 weeks ago This one looks like a serious problem which will lead to a very long chain of broken packages if it is actually removed: Depending on: sysfsutils (15), status change: 2020-06-02 (2 weeks ago) bridge-utils (maintained by: dwmw2, twoerner) bridge-utils-1.6-5.fc32.src requires libsysfs-devel = 2.1.0-28.fc32 edac-utils (maintained by: mchehab) edac-utils-0.16-22.fc32.i686 requires libsysfs.so.2, sysfsutils = 2.1.0-28.fc32 edac-utils-0.16-22.fc32.src requires libsysfs-devel = 2.1.0-28.fc32 edac-utils-0.16-22.fc32.x86_64 requires libsysfs.so.2()(64bit), sysfsutils = 2.1.0-28.fc32 libmetal (maintained by: jsmith) libmetal-2020.04.0-1.fc33.i686 requires libsysfs.so.2 libmetal-2020.04.0-1.fc33.src requires libsysfs-devel = 2.1.0-28.fc32 libmetal-2020.04.0-1.fc33.x86_64 requires libsysfs.so.2()(64bit) libzfcphbaapi (maintained by: sharkcz) libzfcphbaapi-2.2.0-6.fc33.src requires libsysfs-devel = 2.1.0-28.fc32 open-amp (maintained by: pbrobinson) open-amp-2020.04.0-2.fc33.src requires libsysfs-devel = 2.1.0-28.fc32 open-amp-2020.04.0-2.fc33.i686 requires libmetal.so.0 open-amp-2020.04.0-2.fc33.x86_64 requires libmetal.so.0()(64bit) openhpi (maintained by: karsten, pknirsch, rdossant, sharkcz) openhpi-3.8.0-11.fc33.src requires libsysfs-devel = 2.1.0-28.fc32 openhpi-3.8.0-11.fc33.x86_64 requires libsysfs.so.2()(64bit) pcmciautils (maintained by: harald) pcmciautils-018-18.fc32.src requires libsysfs-devel = 2.1.0-28.fc32 pcmciautils-018-18.fc32.x86_64 requires libsysfs.so.2()(64bit) pcsc-cyberjack (maintained by: jenslody, pcfe) pcsc-cyberjack-3.99.5final.SP13-3.fc32.src requires libsysfs-devel = 2.1.0-28.fc32 rng-tools (maintained by: jcapik, nhorman) rng-tools-6.10-3.fc33.src requires libsysfs-devel = 2.1.0-28.fc32 rng-tools-6.10-3.fc33.x86_64 requires libsysfs.so.2()(64bit) sblim-gather (maintained by: vcrhonek) sblim-gather-2.2.9-16.fc33.src requires libsysfs-devel = 2.1.0-28.fc32 sblim-smis-hba (maintained by: vcrhonek) sblim-smis-hba-1.0.0-24.fc33.src requires libsysfs-devel = 2.1.0-28.fc32 lnst (maintained by: jirka, jtluka, olichtne, rpazdera) lnst-slave-15-6.fc33.noarch requires bridge-utils = 1.6-5.fc32 netcf (maintained by: berrange, laine) netcf-libs-0.2.8-15.fc32.i686 requires bridge-utils = 1.6-5.fc32 netcf-libs-0.2.8-15.fc32.x86_64 requires bridge-utils = 1.6-5.fc32 origin (maintained by: jcajka, tdawson) origin-sdn-ovs-3.11.1-6.fc33.x86_64 requires bridge-utils = 1.6-5.fc32 cryptobone (maintained by: senderek) cryptobone-1.3-1.fc33.x86_64 requires rng-tools = 6.10-3.fc33 netcf-libs will in turn break libvirt, and in turn break much much more. Anyone know why sysfsutils was orphaned ? I don't see any FTBFS bugs that triggered it. Did the maintainer no longer have time, or did they consider the package obsolete expecting people to use something else instead ? Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
