I wonder why debian-parl was removed from testing today, since (as I understand it) the reason for removal was solved 2 days ago.
Is there perhaps some spell I could have thrown when uploading a known close-to-deadline package? E.g. the trick of posting something to a bugreport to reset its timer?
On 28-11-2021 11:41, Jonas Smedegaard wrote:
I wonder why debian-parl was removed from testing today, since (as I understand it) the reason for removal was solved 2 days ago.
parl-desktop-eu in testing at the time of removal had a dependency on iitalian. It's iitalian that has an RC bug. The only way to remove
iitalian from testing was to also remove reverse dependencies.
Is there perhaps some spell I could have thrown when uploading a
known close-to-deadline package? E.g. the trick of posting
something to a bugreport to reset its timer?
Pinging the RC bug that's causing the removal is indeed the way to
delay the removal (mind you, there's some delay between updating a bug
and the removal script being aware of the ping, so don't wait till the
last moment). In this case slightly inappropriate as the bug is in
another package, but we don't have anything better.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 72:32:23 |
Calls: | 6,489 |
Calls today: | 2 |
Files: | 12,096 |
Messages: | 5,275,731 |