Bug 27874

Summary:	Unsatisfied dependency for package wireshark-libvirt when upgrading from Mageia 7 to Mageia 8.
Product:	Mageia	Reporter:	PC LX <mageia>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	luigiwalser
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	libvirt-6.10.0-1.mga8.src.rpm	CVE:
Status comment:

Description PC LX 2020-12-19 12:19:39 CET

Description of problem:

When upgrading an up-to-date Mageia 7 system to Mageia 8/cauldron the following message is shown:

"""
A requested package cannot be installed:
wireshark-libvirt-6.10.0-1.mga8.x86_64 (due to unsatisfied libwireshark.so.13()(64bit))
"""

System: Mageia 7, x86_64, Intel CPU, nVidia GPU using nvidia-current proprietary driver.



Version-Release number of selected component (if applicable):

wireshark-libvirt-6.10.0-1.mga8.x86_64



How reproducible:

Always.



Steps to Reproduce:
1. Start with a fully up-to-date Mageia 7 system with the package wireshark-libvirt installed.
2. Remove all the Mageia 7 repositories (urpmi.removemedia -a).
3. Add the Mageia 8/cauldron repositories (urpmi.addmedia --distrib "http://ftp.free.fr/mirrors/mageia.org/distrib/cauldron/x86_64/").
4. Do an update (urpmi --split-length 0 --auto-update).
5. See the error message indicated above.

PC LX 2020-12-19 12:19:49 CET

Severity: normal => major

Comment 1 David Walser 2020-12-19 16:56:17 CET

This is because libvirt-wireshark is dynamically linked to the Wireshark libraries, but has not been successfully rebuilt against the updated libraries in Wireshark 3.4.x.

Comment 2 Lewis Smith 2020-12-19 20:22:44 CET

David, please bounce this if you wish, but it is difficult to avoid assigning this (against normal practice) to you; for libvirt:
 Fri Dec 4 by luigiwalser rebuild for wireshark
[Otherwise to tv]

Assignee: bugsquad => luigiwalser

Comment 3 David Walser 2020-12-19 20:34:59 CET

I'll keep an eye out for a fix, but it should be assigned to the libvirt maintainer.

CC: (none) => luigiwalser
Assignee: luigiwalser => thierry.vignaud

Comment 4 David Walser 2020-12-19 20:59:31 CET

I think this needs to be reported upstream, as it builds in Fedora, so upstream is not aware that there is an issue.

Comment 5 Thierry Vignaud 2020-12-22 11:34:05 CET

(In reply to David Walser from comment #3)
> I'll keep an eye out for a fix, but it should be assigned to the libvirt
> maintainer.

I disagree, that should be assigned to the maintainer would uploaded a new whireshark w/o fixing the fallout…
It looks like it wasn't even submited to the BS…

Comment 6 David Walser 2020-12-22 12:58:43 CET

No, I didn't even know something was built against Wireshark's internal libs and was surprised by that, and Wireshark was updated because it needed to be.  As it is, it almost always goes EOL before we do, so I need to have it on the newest branch I can.  Combine that with the fact that other distros don't share this build issue, there was absolutely no way to expect "fallout."

Either report it upstream or disable the Wireshark subpackage.

Comment 7 Thierry Vignaud 2020-12-22 14:17:25 CET

But there's no fallout at all.
I'd only to submit the package to the BS and that's all…
I don't see the point in opening a bug report and saying we need to get in touch with upstream when all was needed was bumping the release number and submit it…

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 8 David Walser 2020-12-22 14:21:59 CET

Actually it was submitted to the build system and the build failed.  Maybe it was one of our famous random build system issues.