Hi! On Thu, 2015-02-26 at 19:07:46 +0100, Ondřej Surý wrote: > On Sat, Feb 21, 2015, at 16:51, Guillem Jover wrote: > > I think the other merged bug, already fixed in git should cover this > > problem, by improving the documentation. Let me know if it does not. > > > > <https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?id=9d70c7a6582b2d>
> I still think you should explicitly mention the cases when switching > from arch:all to arch:any or vice versa and what to do and what not. As > I am not so well versed in dpkg internals the commit you mentioned > doesn't make it very clear for me. This is the change: ,--- +The package name. When the package is "Multi-Arch: same" this parameter +must include the architecture qualifier, otherwise it should \fBnot\fP +usually include the architecture qualifier (as it would disallow +cross-grades, or switching from being architecture specific to +architecture \fBall\fP or vice versa). +If the parameter is empty or omitted, the \fBDPKG_MAINTSCRIPT_PACKAGE\fP +and \fBDPKG_MAINTSCRIPT_ARCH\fP environment variables (as set by \fBdpkg\fP) +will be used to generate an arch-qualified package name. `--- Here, I'm actually mentioning the arch:all ←→ arch:any case explicitly, and it seems to be clear to me, so it would be helpful if you could point out where the wording is not clear or what can be improved to make it so? Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
