On 22. 11. 21 15:11, Richard W.M. Jones wrote:
On Mon, Nov 22, 2021 at 03:00:04PM +0100, Miro Hrončok wrote:
On 22. 11. 21 14:56, Richard W.M. Jones wrote:
On Mon, Nov 22, 2021 at 02:44:16PM +0100, Miro Hrončok wrote:
On 22. 11. 21 14:11, Richard W.M. Jones wrote:
On Mon, Nov 22, 2021 at 01:12:28PM +0100, Miro Hrončok wrote:
Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-11-22.txt
grep it for your FAS username and follow the dependency chain.
A lot of virt and filesystem packages are shown in the report, but I
think it seems to be a mistake.
For example qemu:
qemu (maintained by: berrange, bonzini, crobinso, dwmw2, ehabkost, jforbes, lkundrak, quintela, rjones, virtmaint-sig)
qemu-2:6.1.0-10.fc36.src requires glusterfs-api-devel = 10.0-1.fc36
This is provided by libgfapi-devel which appears to exist still.
It exists, but it is from the glusterfs package, which is also
included in the report. The dependency is transitive (and in this
case, indirect, because only glusterfs-ganesha is impacted).
So I think this line is wrong.
That is a matter of perspective. If nobody does anything, qemu will
be removed from the distribution in ~1 year:
1. ipmitool will be retired in 6 weeks
2. fence-agents-ipmilan will fail to install
3. fence-agents will be orphaned in 8 weeks
4. fence-agents will be retired in 6 weeks
5. pcs will fail to build
6. pcs will be orphaned in 8 weeks
7. pcs will be retired in 6 weeks
8. glusterfs-ganesha will fail to install
9. glusterfs will orphaned in 8 weeks
10. glusterfscs will be retired in 6 weeks
11. qemu will fail to build and qemu-block-gluster will fail to install
13. qemu will be orphaned in 8 weeks
14. qemu will be retired in 6 weeks
Somehow I have qemu installed but not glusterfs-ganesha or pcs (on a
Rawhide system):
$ rpm -q qemu glusterfs-ganesha pcs
qemu-6.1.0-10.fc36.x86_64
package glusterfs-ganesha is not installed
package pcs is not installed
Sure you do. It is a transitive indirect *build* dependency.
Does the tool follow soft dependencies?
No.
I cannot see where the
qemu -> glusterfs-ganesha dependency comes from.
There is no such dependency.
qemu (build) requires *a* subpackage of glusterfs, *another*
subpackage of glustefs is indireclty impacted. If nobody takes
action, the entire glusterf component will be eventually retired,
impacting qemu. I've described this in the numbered list.
OK I see now. However I think it's not quite so clear cut as above.
qemu.spec has:
BuildRequires: glusterfs-api-devel
glusterfs-ganesha (an unrelated, unneeded subpackage of glusterfs) is
what requires pcs, but we would never need to install that in order to
build qemu. It seems like qemu would not in reality be directly
impacted, although that is not to detract from the point that this is
something that still needs to be fixed in Fedora.
No, in reality, somebody will take an orphaned package or break the indirect
chain (e.g. by removing glusterfs-ganesha from glusterfs) many months before
this would impact qemu.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
