Bug#524120: transitions.yaml handling: the PTS needs to grok finished transitions
+ Stefano Zacchiroli (Wed, 15 Apr 2009 10:02:55 +0200):
> On Tue, Apr 14, 2009 at 11:56:51PM +0200, Adeodato Simó wrote:
> > The way it works is that the Release Team specifies a target
> > package/version combination that must migrate to testing, and all listed
> > packages are blocked until that version or a later one migrates. When
> > that happens, the block is automatically lifted, i.e. dak no longer
> > rejects uploads.
> > It’d be good if the PTS could gain support for doing the same.
> Hum, I wonder whether the PTS is the right place where to fix
> that. Ideally, my preferred solution would be a way, release manager
> side, that automatically cleans up the YAML file when transitions are
> done.
> This is not (only :-)) because it would you that do the work rather
> then us :-), but rather because I see the PTS as the consumer of the
> YAML file. There can be, theoretically, other consumers and basically
> you are implicitly proposing that all consumers implement the "cleanup
> upon migration" logics.
> If you have strong reasons for not implementing the cleanup your side,
> I have no objection fixing the PTS the way you proposed. Let me know.
There is code in dak that can do the cleaning up, but it’s not triggered
automatically, i.e., some release person has to run a command by hand. I
perfectly get whan you mean, though I’m unsure what could be done about
it: AFAIK, the file not being cleaned in a fully automated fashion is in
case there could be any mistakes with the cleanup, plus it really can’t
be cronned by anybody else than ftpmaster because the setup is done by
handing sudo access to the command to members of the release team.
Maybe it should be indeed automatically cleaned up. Let’s put this bug
on hold until we can figure that out. Cc'ing -release and ftpmaster@ in
case they have any comments.
Thanks,
--
- Are you sure we're good?
- Always.
-- Rory and Lorelai
Reply to: