Hi,
Julien Cristau escreveu isso aí:
> On Sun, Nov 6, 2011 at 15:48:46 +0000, Antonio Terceiro wrote:
>
> > ruby-gnome2 (1.0.3-1) unstable; urgency=low
> > .
> > [ Antonio Terceiro ]
> > * New upstream release (Closes: #642024)
> > * Build-depend on libjpeg-dev instead of libjpeg62-dev (Closes: #644804)
> > * Drop Debian-only patch that was breaking stuff (Closes: #639398)
> > * Remove debian/source/options with single-debian-patch
> > .
> > [ Olivier Sallou ]
> > * Do not uncompress examples (Closes: #593325)
>
> Hrm. So with this apparently highly non-urgent upload, you've just
> reset the counter for the big gnome 3 transition, which needs
> ruby-gnome2 to go in first (for the panel-applet binding removal).
I am very sorry to disturb the GNOME 3 transition.
I was assuming that ruby-gnome2 was still being blocked by sshmenu-gnome and
screenruler anyway so that this upload would not affect the transition to
testing. But they were removed from testing two days ago without any
communication with the ruby-gnome2 maintainers, so how was I supposed to known
that the ruby-gnome2 version that was already on in sid was now ready to enter
testing?
Moreover, http://release.debian.org/transitions/html/gnome3.html does not list
ruby-gnome2 at all. Starting from that page, how do I reach the conclusion that
ruby-gnome2 is involved in the GNOME 3 transition?
I was wondering, is there a place where I can check "is it ok to upload
${package} now?"? Is there any machine-parseable data source that can be
processed to provide a yes/no response for this question?
Cheers,
--
Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature