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
Does the tool follow soft dependencies? I cannot see where the
qemu -> glusterfs-ganesha dependency comes from.
Rich.
This line of events is very long and can be stopped at any point by
fixing at least one package or dropping a dependency somewhere or
removing a no longer wanted subpackage.
Hence, technically, the danger to qemu is minimal. But the chain is
there. Especially the build time only transitive dependencies behave
like this.
>Does the tool which generates the report
>follow provides in other packages?
Yes.
>
> qemu-block-gluster-2:6.1.0-10.fc36.x86_64 requires libgfapi.so.0()(64bit),
libgfapi.so.0(GFAPI_3.4.0)(64bit), libgfapi.so.0(GFAPI_3.5.0)(64bit),
libgfapi.so.0(GFAPI_6.0)(64bit)
>
>These are provided by libgfapi0, see below. This seems like a
>different kind of mistake from above.
Same thing.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v