Your message dated Thu, 08 Jan 2015 21:15:03 +0100
with message-id <54aee547.3020...@thykier.net>
and subject line Re: debhelper: Dependency added by dh_installdocs --link-doc
breaks binary-only NMUs
has caused the Debian Bug report #766711,
regarding afterstep not binnmu safe and not installable in sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
766711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: afterstep
Version: 2.2.12-2+b2
Severity: serious
x-debbugs-cc: pkg-tigervnc-de...@lists.alioth.debian.org
It seems after the binnmu for the libjpeg-turbo transition afterstep is
no longer installable in sid (and hence the binnmu won't migrate and the
transition won't complete in testing).
The following packages have unmet dependencies:
afterstep : Depends: afterstep-data (= 2.2.12-2+b2) but 2.2.12-2 is to
be installed
I haven't checked in detail but I suspect this is caused by use of
link-docs. currently doing link-docs between arch specific packages and
arch all packages is not binnmu safe (and there are aguments as to
whether it should or shuoldn't be).
--- End Message ---
--- Begin Message ---
# Unsupportable!
tags 766711 wontfix
thanks
On Sat, 25 Oct 2014 09:10:15 +0200 Robert Luberda <rob...@debian.org> wrote:
> Package: debhelper
> Version: 9.20141022
> Severity: serious
> Justification: Policy 12.3
>
> afterstep package after recent binary-only NMU is no longer installable,
> because dh_installdocs has added the following strict dependency on
> arch-independent package:
> afterstep-data (=2.2.12-2+b2)
>
> See this log:
> https://buildd.debian.org/status/fetch.php?pkg=afterstep&arch=i386&ver=2.2.12-2%2Bb2&stamp=1413508373
> and compare it with the log of previous binary-only NMU from last year:
> https://buildd.debian.org/status/fetch.php?pkg=afterstep&arch=i386&ver=2.2.12-2%2Bb1&stamp=1387741360
>
>
> The policy in section 12.3 and footnote 116 refers to source versions,
> not binary versions:
> /usr/share/doc/package may be a symbolic link to another directory in
> /usr/share/doc only if the two packages both come from the same source
> and the first package Depends on the second.[116]
>
> [116] Please note that this does not override the section on changelog files
> below, so the file /usr/share/doc/package/changelog.Debian.gz must refer
> to the changelog for the current version of package in question. In
> practice, this means that the sources of the target and the destination
> of the symlink must be the same (same source package and version).
>
>
> Regards,
> robert
>
>
> [...]
Hi Robert, Simon and Axel,
It is not possible for debhelper to provide a *policy compliant*
link-doc *between arch:all and arch:any* packages under binNMUs[1].
Accordingly, the use of --link-doc between such packages now triggers a
warning (or a flat error under compat 10).
I have taken the liberty of marking the bug as wontfix (read: "cantfix")
and closing it.
~Niels
[1] This is not limited to debhelper. The reading of the policy
actually (implicitly) forbids link-doc between arch:all and arch:any
packages as the binNMU version is not the same as the source version.
--- End Message ---
