[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Testing migration now requires Build-Depends(-Arch) to be satisfied



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

We have just changed Britney to consider the satisfiability of
Build-Depends(-Arch) for testing migration.  For now this is to be
regarded as an experiment and it may be disabled if it turns out to be
too much effort.

For the time being, this means that your package might not migrate if it
has a Build-Depends(-Arch) relation on a package that is neither in
testing nor appears "ready" to migrate to testing.  This ensures that
packages that were auto-removed due to issues in build-dependencies no
longer migrate to testing right after being removed with the issues
still unfixed.


There are some limitations to this change
=========================================

 * The experiment is limited to Build-Depends and Build-Depends-Arch.
   This means that the Build-Depends-Indep relation is currently
   exempted from this new check.  If the experiment turns out to be
   positive we expect to remove this limitation.

 * This change does *not* ensure that testing is self-contained (even if
   we were to add support for Build-Depends-Indep).  There are several
   cases  where a package might still migrate before its build-
   dependencies.  Additionally, build-dependencies are still not
   considered when packages are removed.


Known issues:
=============

The original implementation did not support build-dependencies with the
":native" modifier and incorrectly flagged them as "unsatisfiable".  We
have just applied a patch for that.
  However, the first updated report will at the earliest appear in 30
minutes from now on release.debian.org.  It will then take another 4-6
hours (in the worst case) before tracker.debian.org/the PTS refreshes
their copy of the testing migration report ("excuses").

 * If you see complains about build-dependencies with a ":native"
   modifier on the tracker/PTS, please wait 4-6 hours to see if the
   issue persists before starting to debug it.

 * Alternatively, wait an hour and then use grep-excuses from devscripts
   (which fetches the report directly from release.debian.org)

For the Release Team,
  Niels


-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAloIBY4ACgkQBUu7n32A
ZELZzQ/8DHYI2yC+iAV7R1NoVtEphDlIwWvzxSBQYiqoJrAb8IbTjAPI1FsUhfbc
4pddLRRUZO4D4Awnv/VajbVFT3PhjSQL7yjM9a1J5xzF+l/h251FGuokSQtWSWRY
5DFCiclp2PftCwF9qp8Od+712Jdz1nJNApKoD1aHeF/ff4WbBOuxRDSt6D9FuMmx
ceeL/qQl0Zps9sf207wR84v08Kx6rr6t2HxhHkl7Tsf9cW8lV3YTWH5t51jU+bbs
329urjlGzRBGZXrOK2PPs/WeYeq335vxurO3FxIGP3oeADJ+wne1bX2AUrPloU5y
Kk48JVKp/vLlqTqG5lnklP/SftVZndUIThLJlgj9o4hBGy0rip4uPP8HYAI1t5Dt
TLqB9SgJsGx2K8+bzxits0h59HWhnowy4V9V/P47fIfrpsbsVv0nF5zpdmuol1fb
DjqZnmK0OIus4sSo8O0R+sA06KaOycuBEerJavZNB3e4M3IKnTk5D8HMX1rD1f6d
DelaIwneaay5xVYVcWDM8Buoe9JdWjXrWu+7xz52GsTAbL+qRu51cIJzFLpdrXNb
53kFH7qNN2rcGfcqYxeDhPNHGEEFV/hDhxyI+M4A9VzQTG3VavCPirDFrbTokp/W
Uv16+zQ27J7i0LKfRu9onTssFeJK4rGfWfXM9uPyPpdV1EKcgIE=
=5+hS
-----END PGP SIGNATURE-----


Reply to: