control: affects -1 bcron-run Hi Gerrit,
On Dienstag, 28. Oktober 2014, Gerrit Pape wrote:
> Thanks. Can you say whether this might affect even more packages?
> daemontools-run comes to mind.
piupartsm@pejacevic:/srv/piuparts.debian.org/master$ rgrep "Package runit is
not configured yet" */fail */bugged |sort -u
experimental/fail/git-daemon-run_1:2.1.1+next.20140919-1.log: Package runit
is not configured yet.
jessie/fail/git-daemon-run_1:2.1.1-1.log: Package runit is not configured
yet.
sid-nodoc/fail/bcron-run_0.10-3.log: Package runit is not configured yet.
sid-nodoc/fail/git-daemon-run_1:2.1.1-1.log: Package runit is not configured
yet.
sid/fail/bcron-run_0.10-3.log: Package runit is not configured yet.
sid/fail/git-daemon-run_1:2.1.1-1.log: Package runit is not configured yet.
sid2experimental/fail/git-daemon-run_1:2.1.1+next.20140919-1.log: Package
runit is not configured yet.
testing2sid/fail/bcron-run_0.10-3.log: Package runit is not configured yet.
testing2sid/fail/git-daemon-run_1:2.1.1-1.log: Package runit is not
configured yet.
piupartsm@pejacevic:/srv/piuparts.debian.org/master$
(this will not have caught packages which passed half a year ago but not
today. packages are being rescheduled, but this takes time. failed
packages are rescheduled more often then passed ones and uplods with new
versions lead to immediate testing...)
I've rescheduled daemontools-run in jessie, should be visible on the piuparts
website around 1400-1500 UTC today, else 12h later.
> But if maintainers that utilized inittab added a fallback for a
> non-existing inittab, as also was requested for the runit package
> (#453106), the error cannot be found through piuparts I guess.
>
> Do you know a way to find out which packages of the whole archive adjust
> inittab through the maintainers script, can piuparts do that?
no, not really. I believe sources.debian.net can tell you though :)
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
