On 6 June 2024 at 08:22, Johannes Ranke wrote: | Am Mittwoch, 5. Juni 2024, 22:27:09 CEST schrieb Dirk Eddelbuettel: | > On 5 June 2024 at 21:55, Paul Gevers wrote: | > | Source: survival | > | Version: 3.5-8-1 | > | Severity: serious | > | Control: close -1 3.6-4-1 | > | Tags: sid trixie | > | User: release.debian....@packages.debian.org | > | Usertags: out-of-sync | > | | > | Dear maintainer(s), | > | | > | The Release Team considers packages that are out-of-sync between testing | > | and unstable for more than 30 days as having a Release Critical bug in | > | testing [1]. Your package src:survival has been trying to migrate for 40 | > | days [2]. Hence, I am filing this bug. The version in unstable triggers | > | autopkgtest failure in r-cran-popepi. | > | | > | If a package is out of sync between unstable and testing for a longer | > | period, this usually means that bugs in the package in testing cannot be | > | fixed via unstable. Additionally, blocked packages can have impact on | > | other packages, which makes preparing for the release more difficult. | > | Finally, it often exposes issues with the package and/or | > | its (reverse-)dependencies. We expect maintainers to fix issues that | > | hamper the migration of their package in a timely manner. | > | | > | This bug will trigger auto-removal when appropriate. As with all new | > | bugs, there will be at least 30 days before the package is auto-removed. | > | | > | I have immediately closed this bug with the version in unstable, so if | > | that version or a later version migrates, this bug will no longer affect | > | testing. I have also tagged this bug to only affect sid and trixie, so | > | it doesn't affect (old-)stable. | > | | > | If you believe your package is unable to migrate to testing due to | > | issues beyond your control, don't hesitate to contact the Release Team. | > | > It is beyond my control that package r-cran-popepi descides to run | > autopkgtests that than hijack and blackmail this package of mine. | > | > Maybe the maintainers of r-cran-popepi should look at their package tracker | > and eg attempt to update to a _current_ version? That's how things work at | > CRAN. | | A look at the ChangeLog of popEpi confirms that that package just needs an | update: | | News for version 0.4.12 | Unit tests | No changes in the package itself — fixed a unit test that used the output of | survival::summmary.survfit which had improved slightly in 3.6-4. | | Should we reassign the bug to r-cran-popepi?
See #1072661 It would be nice if a package tracker should display not only 'this package is behind' (which it does, and which seems to get ignored) but also 'this package is involved in an autopkgtest failure of one of its reverse depends'. survival is just a victim of its success: popEpi uses it, the maintainers sleep and what is likely a routine update (possibly even initiated by CRAN with a nudge) gets ignored here -- but we have massive amounts of manual labour and headaches as a result. I am not a fan of this rather imperfect setup. :-/ Dirk | Johannes | | > I am really tired of this here in Debian. If the package gets autoremoved, | > so be it. The blame will rest with the so-called maintainer team for these | > R package that are effectively taking down maintained packages of mine. | > | > Dirk | > | > | Paul | > | | > | [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html | > | [2] https://qa.debian.org/excuses.php?package=survival | > | | > | x[DELETED ATTACHMENT OpenPGP_signature.asc, application/pgp-signature] | -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
