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

Re: Solutions for the Apache upgrade hell



Le dimanche 13 juillet 2014 à 15:28 +0200, Arno Töll a écrit :
> > Moving them to apache2 package would mean you won't have to move them
> > again in the upgrade to apache 2.4, but it would create a new and
> > circular dependency of apache2.2-common on apache2. Given that
> > apache2.2-common already depends on apache2.2-bin and there exists a
> > transitional package in jessie it might be a better candidate. Then
> > you would have to move it again in the jessie package, but I'm afraid
> > there aren't any easy solutions.
> 
> Pretending the Release Team would allow us to do that (Frankly, I
> wouldn't dare to ask :p) thee are two caveats with that approach that
> would make it very hard and complicated because our historic heritage
> dating back to Etch days again.
> 
> [Not a good idea to move them to apache2]

> [Not a good idea to move them to apache2.2-bin either]

How about creating a new apache2-config package just to move these
configuration files?

-- 
 .''`.      Josselin Mouette
: :' :
`. `'
  `-


Reply to: