Control: reassign -1 ftp.debian.org
Control: retitle -1 dak: Please ignore packages with empty arch keys from 
Package-List

Hi!

[ Leaving enough context for the reassign. ]

On Mon, 2012-09-10 at 17:46:26 +0200, Andreas Beckmann wrote:
> Package: dpkg-dev
> Version: 1.16.8
> Severity: normal
> File: /usr/bin/dpkg-genchanges

> the changes file generated by dpkg-genchanges includes in its Binary
> field packages that have been intentionally disabled by setting an empty
> Architecture field.
> 
> Disabling a package by just clearing its Architecture has the big
> advantage to create a very minimal diff compared to deleting a package
> entry. This may be helpful if source packages are forked and shall be
> diffed (and changes merged) later on - deleting an unneeded package
> entry usually causes bigger diffs and more conflicts.
> Example: src:fglrx-driver -> fglrx-legacy-driver (a few packages have
> been disabled (as there is no need for e.g. 2 clinfo binaries), the
> remaining ones have been renamed to contain "-legacy-" in the name.
> 
> Having these unneccessary entries in the Binary field causes a dak
> reject:
> 
>     DMs must not hijack binaries (binary=libxvbaw-dev,
>     other-source=fglrx-driver)
> 
> With 
> 
>     Source: fglrx-legacy-driver
>     [...]
> 
>     Package: libxvbaw-dev
>     Section: non-free/libdevel
>     Architecture:
>     Depends: ...
>     [...]
> 
> and
> 
>     Source: fglrx-driver
>     [...]
> 
>     Package: libxvbaw-dev
>     Section: non-free/libdevel
>     Architecture: i386 amd64
>     Depends: ...
>     [...]

The explicit request here has been fixed with the changes in 1.19.2+
to not include packages not uploaded in the Binary field in the
.changes file. But I don't think this will fix your core request,
which is to be able to disable these and upload them to the Debian
archive, as there will still be references in the Package-List field
in the .dsc, which means they will get rejected, or queued for NEW
processing.

Thus, this is something ftp-masters need to consider whether to
support or not. In this case these kind of packages will have an empty
arch= key in the Package-List. This is related to bug #913965.

Thanks,
Guillem

Reply via email to