Given a package where the version in testing is arch:all and uninstallable
on architecture $arch and the version in unstable is arch:any but still
uninstallable on $arch, we need to ensure that installability checks add the
package to $arch's uninstallble list rather than just the list for
${arch}+all.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
Rather than mapping "src:foo" to "foo" whilst building the bug hashes,
we store the src: bugs "as is" in the hash, and then include them in the
list of relevant bugs when building the list for a source package.
This avoids a situation where a bug filed against "src:foo" can impede
the migration of the binary package "foo", built from a different source
package.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
Commit 7bba1173e0 increased the size of the
binary package and virtual packages hash and introduced the constant
SIZEOFHASHMAP to ease further changes.
Apply the same change to the source package and source note hashes
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
If new binary packages are removed from the system afer the original
packages have been re-introduced, a binary package which has moved
between source packages may be removed entirely. See Debian bug #624716
for more details.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
Starting with version 0.7.100, python-apt introduced a new API which
replaced several functions which created objects with real classes and
updated a number of method names to be PEP8 compliant.
get_full_tree may be passed an initial package which does not exist in the
target suite, for example because a package declares an obsolete conflict
on a second package which has subsequently been removed.
If the package was previously arch:all and uninstallable and has moved to
being architecture-dependent, becoming installable in the process, then it
will not be in the architecture-dependent uninstallability set; we
therefore should try removing it from that set.
When marking the reverse dependencies of each binary package as affected
by a sourceful update to testing, the reverse dependencies of those
packages are also affected, and so on.
This helps to avoid situations where the installability of immediate
reverse dependencies is unchanged, but that of other packages in the
dependency chain is altered, for example where alternative dependencies
are used.
See Debian bug #614249 for further details.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
This extends the scope of commit 5e3a245759
to include cases where the tpu binNMUs are explicitly included in an "easy"
or "hint" rather than processed as part of the main run.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
When undoing the addition to the result set of a binNMU from tpu, the package
name from the hint will end in ${arch}_tpu, not ${arch}, so we should check
for both cases. At the same time, reverse the sense of the associated test
to make the logic more obvious.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
"${pkg}/${arch}_tpu" means "the tpu binary packages for $pkg on
architecture $arch", not "the unstable binary packages for $pkg on
architecture ${arch}_tpu"
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
Previously, an "approve" hint would allow a package to migrate from
testing-proposed-updates to testing even if packages were not available
for some architectures on which the package existed in testing.
The t-p-u package must now have built on the same architectures as the
existing package in testing; the previous behaviour can be achieved by
combining "approve" and "force" hints.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
t-p-u packages are identified by the package name ending in "_tpu", not
by the first character of the name doing so
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
t-p-u approval previously required both an "unblock" and an "approve"
hint if the package was blocked; the "approve" should be sufficient and
this is the simplest method of achieving that.
There are some cases where this does not quite do the right thing (e.g.
for a package which has both a t-p-u "approve" hint and an "unblock"
hint for the package in unstable) but it is preferable to requiring
t-p-u hints to be added in pairs always.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
If the internal tables used in the C module are not large enough to store
the list of discovered packages then checking installability becomes very
slow.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
This ensures that changes to HELPERS (e.g. the addition of udeb hints)
automatically propagate to the relevant users
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
Allow a package which is a candidate but invalidated by one or
more dependencies to be "force"d.
Based on a patch to britney by Andreas Barth <aba@debian.org>
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
The Sources file for unstable will contain multiple records for a single
source package when one or more architectures has out-of-date binaries.
As the latest version is that which will be considered for migration, only
that version should be added to the list of available sources.
This is not currently an issue in live use, as the data files are already
pre-processed by britney before being passed to britney2.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
Currently a bug against src:foo is treated as if it were filed against
foo. As both may exist in the input list, we accumulate bugs for each
package rather than assuming package names are unique.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
britney now uses the "BugsV" files rather than "Bugs". The new
files contain a list of bugs, not a count, and the migration
of the package is dependent on there being no new RC bugs in unstable
relative to testing, rather than simply fewer RC bugs.
Adam D. Barratt
Mehdi Dogguy