Bug#716880: apache2 upgrade failed
On Wed, Aug 07, 2013 at 10:07:28PM +0200, Arno Töll wrote:
> >> That would be 100+ Breaks. I do not think that is feasible but that may
> >> need a wider discussion.
> >
> > How did you reach that conclusion? I looked at the current testing
> > distribution, and the only direct dependency on apache2.2-common is
> > libapache2-svn, which may go away when subversion is able to
> > transition to testing.
>
> It's one now. :)
>
> It was the state as of Squeeze at the time I wrote this as we were in
> the middle of the transition. Now we can seriously consider doing the
> transition package approach.
Ah ;-)
> > So it seems like having a dependency on a dummy apache2.2-common would
> > be the sensible (if annoying) thing to do.
>
> Thanks for this list. I'm short of time for the next 2-4 weeks, and
> unless sf beats me with it I will address all the outstanding Apache
> packaging issues then (or try to find a feasible solution at least).
Pleasure! It will help others not suffer the (minor) losses which I
had, which might be more major for them (I was on a non-server
machine which only used apache for local use).
Julian
Reply to: