On sam., 2012-05-26 at 16:41 +0200, Yves-Alexis Perez wrote: > On lun., 2012-05-14 at 23:13 +0200, Yves-Alexis Perez wrote: > > On lun., 2012-05-14 at 20:45 +0200, Cyril Brulebois wrote: > So, this is another friendly ping about the main issue. Can I upload a > new 4.6 xfce4-panel which adds the Conflicts against xfce4-panel 4.8 in > shlibs. Then RT would need to schedule the binNMUs for all the relevant > dependencies so, when Wheezy/Wheezy+1 upgrade time comes, a plugin not > working with with 4.10+ panel has a chance to be upgraded *before* the > new panel is used? Hi RT, I know you're all quite busy, but that won't get better as freeze comes closer. Right now, we won't have an upgrade path for xfce4-panel and plugins between Wheezy and Wheezy+1: for partial upgrades there's a window where panel might already be updated to 4.10+ while plugins are still at 4.8, and it'll break at runtime unless we force (4.8) plugins to be upgraded at the same time as the (4.8) panel. If it's a bit painful to schedule the binNMUs I can do the xfce4-panel upload and then do a sourceful upload of each and every panel plugin but that looks too much like an uncoordinated transition and that doesn't look desirable. Maybe the change is small enough that it could be done post-freeze along with all the binNMUs, but then I wouldn't be against some kind of confirmation of that. So, TL;DR: what can I do to help, and could I have a small bit of update so I have an idea what to do for the upgrade path? Regards, -- Yves-Alexis
Attachment:
signature.asc
Description: This is a digitally signed message part