Hi Daniel,
On 2025. Feb 3., Mon at 1:42, wrote:
> Hi Bálint,
>
> > No, the wireshark-qt package has been removed for some time now.
> > Outdated packages on ports should be ignored when building the metadata
> database.
>
> Oh, I did not realize that the wireshark-qt package was already removed
Hi Bálint,
> No, the wireshark-qt package has been removed for some time now.
> Outdated packages on ports should be ignored when building the metadata
> database.
Oh, I did not realize that the wireshark-qt package was already removed. Sorry!
I agree that removed packages should definitely be
Hi Bálint,
> No, the wireshark-qt package has been removed for some time now.
> Outdated packages on ports should be ignored when building the metadata
> database.
Oh, I did not realize that the wireshark-qt package was already removed since
it is still displayed on packages.debian.org[1]. Sorr
Hi,
ezt írta (időpont: 2025. febr. 2., V, 14:28):
>
> I wonder if the wireshark-qt package is still useful? It seems to be stuck on
> a version 4.0.7-1 and built only for riscv64 + even older builds for ia64,
> m68k and x32 (all of them are already supported by the base "wireshark"
> package).
I wonder if the wireshark-qt package is still useful? It seems to be stuck on a
version 4.0.7-1 and built only for riscv64 + even older builds for ia64, m68k
and x32 (all of them are already supported by the base "wireshark" package).
The base wireshark package is already on version 4.4.3-1.
It
Package: wireshark
Version: 4.4.3-1
Wireshark has no valid AppStream metadata generated and is not displayed in
modern GUI software centers such as GNOME Software or KDE Discover. This seems
to be caused by an AppStream ID collision with wireshark-qt (probably the
riscv64 debports package):
"m
6 matches
Mail list logo
