[Pkg-xfce-devel] Bug#668806: Bug#668806: Bug#668806: Bits from the Release Team: Freeze approaching!

Yves-Alexis Perez corsac at debian.org
Sat May 26 14:41:43 UTC 2012

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:
> > Hello Yves-Alexis,
> > 
> > Yves-Alexis Perez <corsac at debian.org> (14/05/2012):
> > > This is just a friendly ping about #668806. I think it's safe to say
> > > that we won't squeeze Xfce 4.10 in Wheezy, but at least paving the way
> > > for Wheezy+1 upgrades would be better.
> > 
> > as discussed on IRC, I think having “traditional” transitions would be
> > the easiest for everyone, we have tools to handle them. Worst case, you
> > don't actually need to bump the soname for one release; then you just
> > don't bump it, and done. I don't see any drawback with this approach.
> > 
> > And thanks for the friendly ping.
> > 
> Ok, since it seems things are a bit unclear, we can't really use the
> traditional (soname) way because we would need to split the binary and
> the lib and then we might have:
> xfce4-foo-plugin built against libxfce4panel.so.1 (Xfce 4.6)
> xfce4-bar-plugin built against libxfce4panel-1.0.so.3 (Xfce 4.8)
> with both lib packages installed. But we can only have one binary
> xfce4-package installed (4.8), and at runtime, xfce4-foo-plugin won't
> load in xfce4-panel 4.8.
> So we do need to have stricter dependencies than soname here.

After a  bit more thinking, we may have a way to split libxfce4panel in

Basically, we would have

xfce4-panel (linked against and depending on libxfce4panel-1.0-6)
xfce4-foo-plugin (linked against and depending on libxfce4panel-1.0-6,
and depending on xfce4-panel)

If a new xfce4-panel is released (with, say, libxfce4panel-1.0-7) which
breaks plugins built against libxfce4panel-1.0-6 we could ship a shlib
file with:

Breaks: libxfce4panel-1.0-6

so xfce4-panel would only be installed with the previous library
removed, so at least users would have the choice not to install it until
it's ready. Then, depending on the context, we would ask for binNMUs or
do the required porting.

I need to think a bit more about that, but in any case this will only
happen in experimental, since right now I'm a bit more thinking about

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?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-xfce-devel/attachments/20120526/4d186795/attachment.pgp>

More information about the Pkg-xfce-devel mailing list