On Sat, Aug 16, 2008 at 02:36:51PM +0200, Paul van Tilburg wrote: > Finally, I have noticed there are a few packages of our that should get > a release block exception, but I haven't created a script to determine > which of our packages have a newer version in Sid w.r.t. Lenny. If > someone could do this and check if we need to request exceptions for > them (because they fix severity important or RC bugs), I would be > grateful.
I haven’t written a script either, but rather scanned our QA overview page manually. These packages need freeze exceptions to fix RC or important (*) bugs: | libcairo-ruby 487204 ruby1.9/hppa again, but we’ll force it in then (see Lucas’ mail). | libgemplugin-ruby 493227 | libgems-ruby 493309 [new upstream release] | libxml-ruby 485738* [new upstream release] These two won’t get approved by the release team (huge debdiffs). I suppose this means backporting changes and uploading to t-p-u, which should be easy for libgems-ruby, but more complex for libxml-ruby. | libxtemplate-ruby1.8 472430* | mongrel 491807* If I understand [1] correctly, mongrel, libgems-ruby, libgemplugin-ruby, and shoes (not maintained by us) need to go in together. Or are there better interpretations? [1] http://release.debian.org/migration/testing.pl?package=libgems-ruby;expand=1 -- Michael Schutte <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
