So, I'm open for ideas how to improve the workflow and making it
easier for the release team and us (especially for me ;)
We could add an option --verbose to cruft-report that actually runs the
suggested commands with the --no-action option added (but only if the
command is actually doing an
Joerg Jaspert schrieb:
And if one made sure no-action actually follows its name. :)
I am not aware of any problems in 'dak rm --no-action'. What's wrong
with it?
Cheers,
Torsten
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Hi!
I think that the decrufting of our archive is done rather suboptimal for
both of us, the ftp-team as well as the release-team. I'm not yet sure,
how things can be done easier, so I guess the best thing to start
discussing it, is describing how things are don currently.
So, what is
Hi,
Alexander Reichle-Schmehl schrieb:
The problems arise, when there are still some packages (build-)depending
on the binary packages to be removed. I guess the correct thing for
broken build-depends is to fill RC bugs against the affected packages,
as they are (defacto) FTBFS.
I've given
4 matches
Mail list logo
