On Wed, Jun 17, 2015 at 05:59:28PM +0100, Jonathan Wiltshire wrote: > On 2015-06-17 17:26, Antonio Terceiro wrote: > >Hi, > > > >On Wed, Jun 17, 2015 at 05:02:24PM +0100, Jonathan Wiltshire wrote: > >>Control: tag -1 moreinfo > >> > >>On 2015-06-17 16:08, Antonio Terceiro wrote: > >>>This transition will be used to track which packages need to be rebuilt > >>>with Ruby 2.2 suport before we make it the default. Ruby 2.1 is still > >>>supported, and only after 2.2 becomes the default we will start another > >>>transition to phase 2.1 out. > >> > >>Please stage the transition in experimental first, and come back when > >>it's > >>clearer what needs to be done. > > > >We already know what needs to be done, since the transitions from 1.9 to > >2.0 and from 2.0 to 2.1 were done in a very similar way. We do the > >transition in phases so that unstable is never broken: > > Right, I didn't appreciate from your mail that's it is to be a two-pronged > transition or that ruby2.2 is already in waiting in testing. > > You'll tangle with the ongoing hiredis transition but we can sort that out > later. > > Scheduled first round of binNMUs. Thanks. Looking at https://release.debian.org/transitions/html/ruby2.2.html the Bad: criteria will not get us the results we need. It has to be ! .depends ~ "libruby2.2" i.e. the packages that do *not* have Ruby 2.2 support, because at this stage packages will not lose the libruby2.1 dependency yet. -- Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature