Re: Bug#116727: Problem with libexpat & php
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 [0]).
> Ok, but I don't see any reference to optional in [0],
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.
> 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.
I haven't made this particularly clear I know. :-/ (And my scripts don't
look at task package deps to notice, unfortunately)
> Ok. Hmm, and all this only because some NMU f**ked up. Oh well.
Yah. :-/
> 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.
Cheers,
aj
Reply to: