Control: tags -1 wheezy
Hi Lucas,
On Thu, Nov 06, 2014 at 09:08:25AM +0100, Lucas Nussbaum wrote:
> Given that this bug was present (unfixed) in wheezy, and the situation
> can only have improved since then, I think that this bug should be
> jessie-ignore'd.
As this is an upgrade issue from sque
Processing control commands:
> tags -1 wheezy
Bug #706877 [insserv] insserv: breaks dist-upgrade by installing before
packages fix their init scripts
Added tag(s) wheezy.
--
706877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706877
Debian Bug Tracking System
Contact ow...@bugs.debian.org
I have tried to install task-xfce-desktop, clementine, virtualbox on a
fresh install of wheezy and do a dist upgrade while running virtualbox
and clementine and I encounter no errors. Am I missing something?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
On 20/10/13 at 09:33 +0200, Petter Reinholdtsen wrote:
> [Jamin W. Collins]
> > It may be bogus or incomplete boot script ordering information, but it
> > previously worked, keep that in mind. One does not expect a Debian
> > dist-upgrade from one stable release to another to result in a
> > non-f
[Jamin W. Collins]
> It may be bogus or incomplete boot script ordering information, but it
> previously worked, keep that in mind. One does not expect a Debian
> dist-upgrade from one stable release to another to result in a
> non-functional system.
Sure. But the fact that the ordering was not
On 10/19/2013 02:08 PM, Petter Reinholdtsen wrote:
[Jamin W. Collins]
Perhaps listing a conflict with package versions prior to those that
have the fixed init scripts would be enough. However, this would
need to be tested. I don't have details on hand for which specific
versions of packages ha
On 09/27/2013 12:38 AM, Petter Reinholdtsen wrote:
Do you have any idea how to solve it for everyone? Would it help if
insserv list a conflict or break on the problematic package versions
to make sure they are upgraded first? Which package version should be
listed like that?
I don't have spe
[Jamin W. Collins]
> Perhaps listing a conflict with package versions prior to those that
> have the fixed init scripts would be enough. However, this would
> need to be tested. I don't have details on hand for which specific
> versions of packages had init scripts that caused the issue, I'm
> so
[Jamin Collins]
> Examples of this are: fetchmail and munin-node. The munin-node init
> script bug report is #680223. However, the updated package wasn't
> installed until after insserv. While I haven't found a bug report for
> the fetchmail issue, I did notice an updated init script being
> ins
Package: insserv
Version: 1.14.0-5
Severity: critical
This bug completely breaks dist-upgrades, leaving the system in an
indeterminate state. In my case, it resulted in being unable to use sudo
from my account and having to completely reboot the box and use init=/bin/bash
to recover.
This bug
10 matches
Mail list logo
