Bug#524120: transitions.yaml handling: the PTS needs to grok finished transitions
+ Mark Hymers (Wed, 15 Apr 2009 19:39:53 +0100): On Wed, 15, Apr, 2009 at 11:04:18AM +0200, Stefano Zacchiroli spoke thus.. On Wed, Apr 15, 2009 at 10:25:40AM +0200, Adeodato Simó wrote: 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. FWIW, Adam Barrat (thanks!) just prodded me on IRC about this, remembering me that devscripts contains another consumer of that YAML file (/usr/bin/transition-check), which is affected by the very same problem. In a sense, that strengthen my feeling that the solution should be FTP master side, let's gather some more comments ... As I've just mentioned to Dato and Luk on #-release, we've no objection to cleaning up the file at each dinstall and have a patch for it if they're happy for us to apply it. They're just discussing it now (I assume checking that it won't have any unwanted side effects from their side). Right. I thought about it, and please do implement such cleaning on each dinstall, and we can close this bug when the code is in place. Additionally, it’d be great if a mail could be sent for each transition that gets automatically cleaned, but it’s not a requisite. Thanks, -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524120: transitions.yaml handling: the PTS needs to grok finished transitions
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.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524120: transitions.yaml handling: the PTS needs to grok finished transitions
On Wed, Apr 15, 2009 at 10:25:40AM +0200, Adeodato Simó wrote:
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.
FWIW, Adam Barrat (thanks!) just prodded me on IRC about this,
remembering me that devscripts contains another consumer of that
YAML file (/usr/bin/transition-check), which is affected by the very
same problem. In a sense, that strengthen my feeling that the solution
should be FTP master side, let's gather some more comments ...
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524120: transitions.yaml handling: the PTS needs to grok finished transitions
On Wed, 15, Apr, 2009 at 11:04:18AM +0200, Stefano Zacchiroli spoke thus.. On Wed, Apr 15, 2009 at 10:25:40AM +0200, Adeodato Simó wrote: 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. FWIW, Adam Barrat (thanks!) just prodded me on IRC about this, remembering me that devscripts contains another consumer of that YAML file (/usr/bin/transition-check), which is affected by the very same problem. In a sense, that strengthen my feeling that the solution should be FTP master side, let's gather some more comments ... As I've just mentioned to Dato and Luk on #-release, we've no objection to cleaning up the file at each dinstall and have a patch for it if they're happy for us to apply it. They're just discussing it now (I assume checking that it won't have any unwanted side effects from their side). Mark -- Mark Hymers mhy at debian dot org Don't you hate those Claims Direct adverts? 'I slipped on a banana skin and sued the Dominican Republic!' Linda Smith on the News Quiz talking about the Compensation Culture -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524120: transitions.yaml handling: the PTS needs to grok finished transitions
Package: qa.debian.org Hello, the PTS has support to show information about packages blocked by the Release Team because of some ongoing transition. The set of blocked packages is found via the transitions.yaml file at [1]. 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. At the moment, for example, the transitions.yaml file lists the evolution-data-server transition, and hence packages like beagle [2] are listed as affected. The target source is given in the “source” field of each transition stanza, and the target version in the “new” field. Until this bug is fixed, I’ll try to always leave a finished transition around in case you need it for testing or whatever. Thanks, [1]: http://ftp-master.debian.org/transitions.yaml [2]: http://packages.qa.debian.org/b/beagle.html -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
