Package: reprepro
Severity: important
For some time now dak has been keeping arround extra versions of source
packages to satisfy built-using. Recently dak also started including
them in packages files marked with the extr control field
"Extra-Source-Only: yes". Extra source versions may be either older or
newer than the primary source version. Wanna-build has also been made to
ignore packages that are marked with "Extra-Source-Only: yes".
Reprepro doesn't know anything about this new control field and just
blindly imports the "extra" source package if it happens to be the
newest version available during an update run. It also blindly pulls in
the extra control field. This causes two problems, particulally for
reprepro users who pull from testing and use wanna-build (for those who
pull from unstable the risk of bad things happening is much lower but I
don't belive it's impossible).
1: source packages may be pulled into the reprepo repository before they
are ready (and for those who import at least some binaries* before the
corresponding binaries are available).
2: wanna-build refuses to see the package due to the tag and gives no
obvious indication of why it is refusing to see it. This caused
significant frustration along the lines of "why the hell isn't
wanna-build seeing eglibc". Due to the way reprepro doesn't re-import
metadata when the version stays the same the tag will remain even when
the previously "too new" version becomes "current" in the distribution
that is being pulled from.
IMO until/unless reprepro implements proper support for built-using and
extra packages to support it packages with "Extra-Source-Only: yes"
should be ignored when updating. This will restore the old behaviour
before dak started adding those packages to it's Sources file.
* At raspbian we import arch all binaries and build our own arch
specific binaries.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
