[MIR] false-positives, do not promote

plzip & lzlib are false positive component-mismatches (MIR), as lintian depends on `plzip | lzip-decompressor` and lzip-decompressor is provided by `lzip` in Ubuntu “main” already.

$ sudo apt install lzip-decompressor
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package lzip-decompressor is a virtual package provided by:
  xlunzip 0.7-3
  plzip 1.10-1
  pdlzip 1.12-1
  minilzip 1.13-1
  lziprecover 1.23-1
  lunzip 1.13-1
  clzip 1.12-4
  lzip 1.23-1
You should explicitly select one to install.

E: Package 'lzip-decompressor' has no installation candidate

xterm is a false positive component-mismatch (MIR), as tk8.6 "Recommends: xterm | x-terminal-emulator" and x-terminal-emulator is provided by "gnome-terminal" in Ubuntu "main" already.

https://git.launchpad.net/ubuntu/+source/tk8.6/tree/debian/control#n20

$ apt install x-terminal-emulator
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package x-terminal-emulator is a virtual package provided by:
  xterm:i386 372-1ubuntu1
  xterm 372-1ubuntu1
  xiterm+thai 1.10-2build1
  xfce4-terminal 0.8.10-1
  tilix 1.9.4-2build1
  termit 3.1-1
  terminology 1.12.1-1
  terminator 2.1.1-1
  stterm 0.8.4-1
  sakura 3.8.4-1
  rxvt-unicode 9.30-2build1
  qterminal 0.17.0-0ubuntu1
  pterm 0.76-2
  mlterm-tiny 3.9.0-1build1
  mlterm 3.9.0-1build1
  mate-terminal 1.26.0-1ubuntu2
  lxterminal 0.4.0-2
  lilyterm 0.9.9.4+git20150208.f600c0-5build1
  konsole 4:21.12.3-0ubuntu1
  kitty 0.21.2-1build1
  eterm 0.9.6-6.1
  deepin-terminal 5.2.11-1build1
  cool-retro-term 1.2.0+ds-5
  gnome-terminal 3.44.0-1ubuntu1
You should explicitly select one to install.

E: Package 'x-terminal-emulator' has no installation candidate

The reason for esmtp is actually bug 1895011 - but until then track it here to show better in weekly checks.

src:inetutils (in universe) contains the 'inetutils-telnet' binary, which "Provides:" telnet.

A "telnet" binary package was provided by src:netkit-telnet (in main) in the past, but this was renamed to "netkit-telnet" as of https://launchpad.net/ubuntu/+source/netkit-telnet/0.17-48 which makes germinate think there would be a component-mismatch: https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.kinetic/all

There's also a transition related to this: https://people.canonical.com/~ubuntu-archive/transitions/html/auto-netkit-telnet.html

IIUC an AA needs to demote the "telnet" binary and promote "netkit-telnet" (and "netkit-telnetd") instead. This should restore status quo with src:netkit-telnet being in main and src:inetutils being in universe, like before the rename of binary packages.

(Keeping this bug open as "Triaged" – for now, to show up as an update-excuse bug)

netkit-telnet and netkit-telnetd are already in main (even in kinetic-proposed).

I thus only demoted telnet binary package, coming in kinetic-proposed, which is the transitional dummy package coming from inetutils (as in https://launchpad.net/ubuntu/+source/inetutils/2:2.3-4/+build/24264390). I’ll let you track the rest of the migration and thus keep this bug as "Triaged".

$ ./change-override -c universe -s kinetic-proposed telnet
Override component to universe
telnet 0.17+2.3-4 in kinetic amd64: main/net/standard/100% -> universe
telnet 0.17+2.3-4 in kinetic arm64: main/net/standard/100% -> universe
telnet 0.17+2.3-4 in kinetic armhf: main/net/standard/100% -> universe
telnet 0.17+2.3-4 in kinetic i386: main/net/standard/100% -> universe
telnet 0.17+2.3-4 in kinetic ppc64el: main/net/standard/100% -> universe
telnet 0.17+2.3-4 in kinetic riscv64: main/net/standard/100% -> universe
telnet 0.17+2.3-4 in kinetic s390x: main/net/standard/100% -> universe
Override [y|N]? y
7 publications overridden.

There is nothing keeping netkit-telnet in Standard. It is in component-mismatches for demotion to Universe. And an update of ubuntu-meta will drop telnet. If you need to have a telnet in main, it will need to be seeded somewhere.

There is no specific need from my side to keep netkit-telnet in main, other than it beeing seeded. If dropped from the seed, it can move to universe all together. At very least netkit-telnetd should be demoted to universe (as it was in the past), to resolve the src:netkit-telnet proposed migration.

libnet-libidn2-perl is a false positive component-mismatch (MIR), as libnet-dns-perl "Recommends: libnet-libidn2-perl | libnet-libidn-perl" and libnet-libidn-perl is in Ubuntu "main" already.

We might want to switch from libnet-libidn-perl to libnet-libidn2-perl at some point, but it's still newly packaged, so let's give it some more time.

See also:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019281
https://salsa.debian.org/perl-team/modules/packages/libnet-dns-perl/-/commit/936d80f5b4d2c3a89f0951b907d4137601075bba

Adding link to libnet-dns-perl, to make the libnet-dns-perl -> libnet-libidn2-perl component-mismatch show up in update-excuses.

packages in main should not pull in packages in universe by default. Either libnet-dns-perl needs to list libnet-libidn-perl as the first alternative, or libnet-libidn2-perl needs to be promoted.

This bug was fixed in the package libnet-dns-perl - 1.36-1ubuntu1

---------------
libnet-dns-perl (1.36-1ubuntu1) lunar; urgency=medium

  * d/control: prefer libnet-libidn-perl over IDN2, to avoid MIR (LP: #1980663)
    We want to move to libIDN2 in the future, but avoid having libnet-libidn-perl
    and libnet-libidn2-perl in "main" at the same time. See LP#2003076

 -- Lukas Märdian <email address hidden> Tue, 17 Jan 2023 12:30:16 +0100

I worked with upstream to get the tk8.6 -> xterm false-positive resolved. It should get fixed in tk8.6_8.6.13-2 via https://bugs.debian.org/1030148

due to 2008789 inetutils no more is a false positive