Re: Bug#116727: Problem with libexpat & php
Anthony Towns (email@example.com) wrote:
> On Tue, Dec 04, 2001 at 09:28:55AM -0600, Ardo_Vanrangelrooij wrote:
> > > I'm sorry, but it's too late to start transitions like this for
> > > woody. (And has been for almost a month now, see ).
> > Ok, but I don't see any reference to optional in ,
> Heh. You mean that URL didn't implicitly encode the exact sentence from
> that email that I was thinking of? Must be a bug.
> ] As of today, policy is frozen. Any further changes to packages need to
> ] be made by unanimous agreement amongst all the maintainers the change
> ] will affect.
> ...was what I was particularly thinking of. Any sort of process that goes
> "change the way my package works, file RC bugs against everyone who uses
> it" pretty much falls afoul of that.
Ok, I understand.
> > only base and standard.
> libexpat is "effectively" standard, since for the freeze's purposes
> standard includes tasks, the desktop task includes abiword, and abiword
> uses libexpat.
Ah, that explains a lot. That covers a large number of packages then.
> I haven't made this particularly clear I know. :-/ (And my scripts don't
> look at task package deps to notice, unfortunately)
Well, something to work on for the next freeze. :-)
> > I'll at least upload a new version with the autotools-dev approach in place
> > and the missing manpage for the binary in the packagei (this just got in).
> Note that there's no rush for this: we're just getting rid of RC bugs
> in standard packages and stopping making major changes to them; "minor"
> changes are still okay until around the end of the month.
Ardo van Rangelrooij
home email: firstname.lastname@example.org
home page: http://people.debian.org/~ardo
GnuPG fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9