[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Please let oregano into testing again

On Sun, 2005-05-29 at 23:59 -0700, Steve Langasek wrote:
> On Mon, May 30, 2005 at 01:25:46AM -0300, Maximiliano Curia wrote:
> > On Thursday 26 May 2005 23:09, Steve Langasek wrote:
> > > Looks like there's a new RC bug against the package that will need to be
> > > fixed first.
> > The RC bug [1] was closed today, with the patch provided by the submiter, in 
> > the package oregano version 0.40.0-5 uploaded by Jordi Mallach.
> > No other changes were made. Upstream agrees an has applied the changes to 
> > newest version.
> > Please consider this oregano version for sarge.
> > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310936
> So here's the deal, libgpewidget has been uploaded now dropping the
> dependency on libcairo.
> This means we have (after libgpewidget is built everywhere) no packages in
> testing that would prevent removing libcairo from the release, as the
> maintainer requests.
> And oregano is free of RC bugs again in unstable and is a candidate for
> release, but depends on libcairo.
> Could the two of you decide between yourselves what should be done with this
> set of packages for sarge, and let the release team know whether to re-add
> oregano, or remove libcairo/libpixman?

Let me try to make my strongest position:
 Shipping any application in sarge based on cairo 0.4.0 API is a mistake

The upstream developers think so and won't be providing any support for
that API now that they have made a big API change.  And they don't
promise not to do it again in a more minor way before cairo 1.0 although
0.5.0 was the big API change.

I plan to track the 0.5.0 version onwards with packages with new names
like source: cairo0.5 binary: libcairo0.5 conflicting and replacing the
older one, as they both provide libcairo.so.0

Applications of cairo are planning to move to 0.5.0 shortly and that
list includes Mono, Mozilla for SVG and in due course, GTK (devel
version).  The future users of cairo in debian are larger than the
current ones.

I expect Oregano will have to shortly have to make this step, leaving
the current Oregano's cairo support behind unless somebody in debian
keeps it alive.

So shipping with cairo+oregano as is going with something we *already
know* is obsolete and will be rather quickly getting unmaintainable
except by DDs taking on the code.


Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: