-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have the same problem on two different wheezy hosts with aptitude
safe-upgrade (both fresh installed wheezys and no distupgrade from
squeeze) and the package libapache2-svn was, and is, not installed on
both hosts.
But I have other fresh inst
On Sun, Aug 11, 2013 at 11:50:09AM +0200, Stefan Fritsch wrote:
> Am Mittwoch, 7. August 2013, 20:39:25 schrieb Julian Gilbey:
> > Or are you saying that a Breaks would be needed on every depending
> > package in stable?
>
> We would also need to add breaks for all packages depending on
> apache2
Am Mittwoch, 7. August 2013, 20:39:25 schrieb Julian Gilbey:
> Or are you saying that a Breaks would be needed on every depending
> package in stable?
We would also need to add breaks for all packages depending on
apache2.2-common that have been in Debian since Debian etch and have
been removed
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 apac
On 07.08.2013 21:39, Julian Gilbey wrote:
> On Sun, Jul 14, 2013 at 02:39:41PM +0200, Arno Töll wrote:
>>> * The only way to ship a package named apache2.2-common is to add a
>>>Breaks header listing every single reverse dependency with correct
>>>version information.
>>
>> That would be 1
On Sun, Jul 14, 2013 at 02:39:41PM +0200, Arno Töll wrote:
> > * The only way to ship a package named apache2.2-common is to add a
> >Breaks header listing every single reverse dependency with correct
> >version information.
>
> That would be 100+ Breaks. I do not think that is feasible b
clone 716880 -1
retitle -1 apache2 package upgrade fails if the configuration is inconsistent
thanks
Am Sonntag, 14. Juli 2013, 01:51:55 schrieb Vincent Lefevre:
> Purging configuration files for apache2.2-common ...
> The problem seems to come from the following
> /var/lib/dpkg/info/apache2.pos
On 14.07.2013 12:38, Helmut Grohne wrote:
> My point was that if modules had their dependencies satisfied in such a
> way, then dependencies are wrong even for a wheezy -> jessie upgrade,
> because as you later point out it would break the whole server.
They are wrong and this can get really nasty
Control: retitle -1 apache2 upgrade fails when apache2.2-common is purged in
the process
On 2013-07-14 09:47:04 +0200, Helmut Grohne wrote:
> You are likely using --purge-unused something similar causing the no
> longer needed package apache2.2-common to be purged.
Yes, actually I marked it as p
On Sun, Jul 14, 2013 at 12:14:04PM +0200, Arno Töll wrote:
> Pretending we provided apache2.2-common, modules depending on the 2.2
> version of the server had their depdencies satisfied. Thus, they would
> be co-installable with Apache 2.4, they would migrate to Testing and so on.
My point was tha
On 14.07.2013 12:08, Helmut Grohne wrote:
> I do not see how the transition is affecting this option. If it breaks
> during the transition, it can also break a partial upgrade. Introducing
> apache2.2-common later can cause a broken wheezy->jessie upgrade when a
> user fails to upgrade the correspo
On Sun, Jul 14, 2013 at 11:50:55AM +0200, Arno Töll wrote:
> we cannot do this as long as the transition is ongoing. Sadly lots of
> packages reverse-depends on on apache2.2-common. Satisfying this
> dependency would create (even more) havoc on such systems as apt would
> not force a removal of pac
Hi,
On 14.07.2013 09:47, Helmut Grohne wrote:
> As far as I can tell the only way to fix this issue is to introduce a
> transitional apache2.2-common package containing no files. apache2 would
> need to depend on apache2.2-common for one release (skipping a release
> is not supported).
we cannot
Control: severity -1 important
Thanks for the detailed log, because it highlights the cause.
On Sun, Jul 14, 2013 at 01:51:55AM +0200, Vincent Lefevre wrote:
> Purging configuration files for apache2.2-common ...
> dpkg: warning: while removing apache2.2-common, directory '/usr/lib/cgi-bin'
> no
On 2013-07-14 01:51:55 +0200, Vincent Lefevre wrote:
> Package: apache2
> Version: 2.4.4-6
> Severity: grave
> Justification: renders package unusable
>
> The apache2 upgrade failed:
[...]
And when I tried to remove it, this failed:
The following packages will be REMOVED:
apache2* apache2-bin*
Package: apache2
Version: 2.4.4-6
Severity: grave
Justification: renders package unusable
The apache2 upgrade failed:
(Reading database ... 475293 files and directories currently installed.)
Removing libapache2-svn ...
Module authz_svn already disabled
Module dav_svn already disabled
Purging conf
16 matches
Mail list logo
