* Axel Beckert <a...@debian.org> [141109 17:33]:
> I suspect that's currently the only solution. zsh is affected, too:
>
> Depends: zsh-common (= 5.0.7-3), zsh-common (= 5.0.7-3+b1), [...]
>
> debian/control says:
>
> Depends: zsh-common (= ${source:Version}),
> ${misc:Depends},
> [...]
>
> So it may be worth reinvestigating this issue instead of removing
> ${misc:Depends} from tons of packages (and causing lintian warnings
> about that) and requesting freeze exceptions for all these uploads. (I
> expected hundreds of them, zsh and afterstep only being some
> examples.)
>
> Any advice by the release team on this issue is appreciated.
The problem is that removing the misc:Depends just replaces one bug with
another one: The packages created that way will not include a changelog
for the binnmu.
Packages using --link-doc to link from an architecture any[1] to an
architecture all package are not really bin-nmuable. So the only
possiblities I see are:
- keep the way it is which causes those packages generate uninstallable
packages if binnmu'd [2]
- remove the dependencies (in the packages or debhelper), causing
binnmu'd packages to have no changelog of the binnmu.
- try to add some bin-nmu and affectedness detection (with the danger of
false positives) to debhelper to make thsoe packages fail to build
if binnmu'd so that no uninstallable packages are generated.
- change the affected packages in question to not use --link-doc.
Bernhard R. Link
[1] Or rather anything but "all".
[2] What is the status if multi-arch and bin-nmu, does being bin-nmu'd
still break multi-arch packages?
--
F8AC 04D5 0B9B 064B 3383 C3DA AFFC 96D1 151D FFDC
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
