On Thu, Sep 28, 2006 at 10:12:11AM +0200, Tollef Fog Heen wrote: > >On Thu, Sep 28, 2006 at 09:51:36AM +0200, Tollef Fog Heen wrote:
> >>>So can we have apache2.2 uploaded to unstable so that this can happen? > >>>:-) > >>Working on it. We are going to rename apache2-common to > >>apache2.2-common and any apache modules must depend on the appropriate > >>-common to ensure they are removed when an incompatible apache is > >>installed. JFYI. > >Is there an ETA for this and/or a public list of issues that need to be > >resolved before it happens? > I intended to upload last night, but ran out of time due to a) headache > and b) libtool. I enjoy that you listed libtool separately from the headache ;) > I'll see if I can get it done tonight. It'll need NEW processing so it > will take a little more time to actually get into unstable. Any news on this? I'd like to ask the ftpmasters to expedite the NEW processing for it, but I can't before it's been uploaded. :) > >The sooner the better if we're to give maintainers an appropriate amount of > >time to update their dependencies to apache2.2-common and fix any source > >incompatibilites. > They probably want to test-build against apache2 from experimental to > fix any source incompatibilities. It has apache2-common, not > apache2.2-common, but should otherwise be very similar. Probably, but in practice we aren't going to get useful coverage from maintainers until an upload to unstable forces them to act. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]