[MIR] false-positives, do not promote

Bug #1980663 reported by Lukas Märdian
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
esmtp (Ubuntu)
Won't Fix
Undecided
Unassigned
inetutils (Ubuntu)
Fix Released
Undecided
Unassigned
lzlib (Ubuntu)
Fix Released
Undecided
Unassigned
netkit-telnet (Ubuntu)
Triaged
Undecided
Lukas Märdian
plzip (Ubuntu)
Fix Released
Undecided
Unassigned
xterm (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

This bug is for tracking MIR false positives, it shall never be assigned to ~ubuntu-archive.

https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg

Each bug task should be accompanied by a comment below describing why this package is a false-positive component-mismatch.

Archive-Admins, please DO NOT promote those packages into "main".

Lukas Märdian (slyon)
Changed in lzlib (Ubuntu):
status: New → Incomplete
Lukas Märdian (slyon)
description: updated
description: updated
Changed in lzlib (Ubuntu):
status: Incomplete → New
Changed in plzip (Ubuntu):
status: Incomplete → New
assignee: nobody → Lukas Märdian (slyon)
assignee: Lukas Märdian (slyon) → nobody
Changed in lintian (Ubuntu):
assignee: nobody → Lukas Märdian (slyon)
tags: added: update-excuse
Revision history for this message
Lukas Märdian (slyon) wrote :

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

summary: - [MIR] plzip & lzlib
+ [MIR] false-positives, do not promote
no longer affects: lintian (Ubuntu)
tags: removed: update-excuse
tags: removed: kinetic
description: updated
description: updated
description: updated
Changed in lzlib (Ubuntu):
status: New → Fix Released
Changed in plzip (Ubuntu):
status: New → Fix Released
Revision history for this message
Lukas Märdian (slyon) wrote (last edit ):

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

Changed in xterm (Ubuntu):
status: New → Fix Released
Lukas Märdian (slyon)
description: updated
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

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

Lukas Märdian (slyon)
Changed in esmtp (Ubuntu):
status: New → Fix Released
Lukas Märdian (slyon)
Changed in inetutils (Ubuntu):
status: New → Fix Released
Revision history for this message
Lukas Märdian (slyon) wrote (last edit ):

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)

tags: added: update-excuse
Changed in inetutils (Ubuntu):
status: Fix Released → Triaged
Lukas Märdian (slyon)
Changed in inetutils (Ubuntu):
status: Triaged → Fix Released
Changed in netkit-telnet (Ubuntu):
assignee: nobody → Lukas Märdian (slyon)
status: New → Triaged
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

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.

Revision history for this message
Jeremy Bicha (jbicha) wrote :

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.

Revision history for this message
Lukas Märdian (slyon) wrote :

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.

Steve Langasek (vorlon)
Changed in esmtp (Ubuntu):
status: Fix Released → Won't Fix
Changed in xterm (Ubuntu):
status: Fix Released → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers