Bug#1043427: src:utop: fails to migrate to testing for too long: blocked by ocaml-logs rebuild
Le 11/08/2023 à 20:53, Paul Gevers a écrit : One current blocker is xmlrpc-light, which I mistakenly uploaded with urgency low 2 days ago, which therefore should not migrate before 8 days from now. It seems the connection is hidden. It would be nice if you could show how that works. Look for "(not considered)" implicit dependencies with grep-excuses: utop -> ocaml-logs/ppc64el -> ocaml-x509/ppc64el -> ocaml-zarith -> ocsigenserver/s390x -> xml-light -> xmlrpc-light AFAIU, these 7 items (at least) need to migrate to testing together. I am wondering: Couldn't the required age for xmlrpc-light be lowered? Or should I upload a new package with a higher urgency? I have added an age hint and dropped required age to 5. Thank you. Cheers, -- Stéphane
Bug#1043427: src:utop: fails to migrate to testing for too long: blocked by ocaml-logs rebuild
Hi, On 11-08-2023 08:34, Stéphane Glondu wrote: On Thu, 10 Aug 2023 21:44:23 +0200 Paul Gevers wrote: One current blocker is xmlrpc-light, which I mistakenly uploaded with urgency low 2 days ago, which therefore should not migrate before 8 days from now. It seems the connection is hidden. It would be nice if you could show how that works. I am wondering: Couldn't the required age for xmlrpc-light be lowered? Or should I upload a new package with a higher urgency? I have added an age hint and dropped required age to 5. Paul
Bug#1043427: src:utop: fails to migrate to testing for too long: blocked by ocaml-logs rebuild
Dear Paul, On Thu, 10 Aug 2023 21:44:23 +0200 Paul Gevers wrote: [...]¨ Your package src:utop has been trying to migrate for 37 days [2]. [...] > 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. One current blocker is xmlrpc-light, which I mistakenly uploaded with urgency low 2 days ago, which therefore should not migrate before 8 days from now. I am wondering: Couldn't the required age for xmlrpc-light be lowered? Or should I upload a new package with a higher urgency? Cheers, -- Stéphane
Bug#1043427: src:utop: fails to migrate to testing for too long: blocked by ocaml-logs rebuild
Source: utop Version: 2.13.0-1 Severity: serious Control: close -1 2.13.1-2 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:utop has been trying to migrate for 37 days [2]. Hence, I am filing this bug. The version in unstable seems to be involved in some ocaml transition that appears to be stalled somehow. (I hardly understand how the ocaml ecosystem in Debian works). 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=utop
