Control: severity -1 serious
Control: tags -1 + pending
Hello Víctor Cuadrado Juan,
Thanks for your bug report. (Reply inline below.)
On Thu, Aug 02, 2018 at 08:59:33PM +0200, Víctor Cuadrado Juan wrote:
> Package: util-linux
> Version: 2.32-0.3
> Severity: critical
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hello util-linux maintainer,
>
> Looping in the bash-completion maintainer too.
>
> On a Stretch system with:
^^^^^^^ (important detail highlighted)
> util-linux_2.32-0.3
> bash-completion_1:2.1-4.3
>
> I get an error performing a full-upgrade to Testing, as both packages
> own `/usr/share/bash-completion/completions/su`:
>
> ```
> Preparing to unpack .../util-linux_2.32-0.3_amd64.deb ...
> Unpacking util-linux (2.32-0.3) over (2.29.2-1+deb9u1) ...
> Replacing files in old package login (1:4.4-4.1) ...
> dpkg: error processing archive
> /var/cache/apt/archives/util-linux_2.32-0.3_amd64.deb (--unpack):
> trying to overwrite '/usr/share/bash-completion/completions/su', which
> is also in package bash-completion 1:2.1-4.3
>
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> dpkg: considering deconfiguration of util-linux, which would be broken by
> installation of login ...
> dpkg: no, util-linux is essential, will not deconfigure
> it in order to enable installation of login
> dpkg: error processing archive
> /var/cache/apt/archives/login_1%3a4.5-1.1_amd64.deb (--unpack):
> installing login would break existing software
> Errors were encountered while processing:
> /var/cache/apt/archives/util-linux_2.32-0.3_amd64.deb
> /var/cache/apt/archives/login_1%3a4.5-1.1_amd64.deb
> ```
>
>
>
> After a brief look at both source packages, I can see that meanwhile
> the last util-linux doesn't ship that file, bash-completion does.
Yes, except switch places of util-linux and bash-completion in your
sentence. ;)
I'll bump the version used in the Breaks/Replaces relationship in the
next upload. It's ofcourse easy enough to work around this issue, since
it only effects partial upgrades, by making sure you upgrade both
util-linux and bash-completion to both use the versions from
unstable/testing.
> Also, util-linux declares a Break and Conflicts with specific versions
> of bash-completion, so I have assumed that the bug report goes indeed
> against util-linux.
>
> Please don't hesitate to reassign or reduce severity if needed.
Technically, 'serious' is the correct severity as this is a debian
policy violation. (Critical would be if the update would lead to
for example your harddrive dying because of the update which could
lead to data loss.)
Also for correctness, you should include a 'Justification:' field
in your bug report citing which section of debian policy you're
arguing isn't followed.
In practice is doesn't really matter though. Any severity >= serious
is considered "RC" (release critical), which has some implications
on testing migration.
Regards,
Andreas Henriksson
