Bug#541980: [Debian-ha-maintainers] Bug#541980: redhat-cluster: Incorrect provides, dependencies and runlevels in init.d scripts

2009-10-11 Thread Guido Günther
tags 541980 +fixed-upstream The provides have been fixed upstream for 3.0.3. -- Guido On Sat, Oct 10, 2009 at 09:56:49AM +0200, Petter Reinholdtsen wrote: found 541980 3.0.2-3 thanks This issue was reintroduced into unstable when version 3.0.2-3 was uploaded. Happy hacking, --

Bug#541980: redhat-cluster: Incorrect provides, dependencies and runlevels in init.d scripts

2009-10-10 Thread Petter Reinholdtsen
found 541980 3.0.2-3 thanks This issue was reintroduced into unstable when version 3.0.2-3 was uploaded. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#541980: redhat-cluster: Incorrect provides, dependencies and runlevels in init.d scripts

2009-09-16 Thread Petter Reinholdtsen
I had a closer look at the package, and here is an updated patch which should reproduce the order of the init.d scripts before dependency based boot sequencing. I've uploaded a package with this patch to the 2 day delayed queue. diff -ruN ../redhat-cluster-2.20081102/debian/changelog

Bug#541980: redhat-cluster: Incorrect provides, dependencies and runlevels in init.d scripts

2009-09-12 Thread Petter Reinholdtsen
Any hope of having a fix for this issue uploaded soon? Should I NMU to fix it? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#541980: redhat-cluster: Incorrect provides, dependencies and runlevels in init.d scripts

2009-08-17 Thread Petter Reinholdtsen
Package: redhat-cluster-suite Version: 2.20080801-1 Severity: important Tags: patch User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-runlevels incorrect-dependency With dependency based boot sequencing, I discovered what I believe is a bug in the init.d scripts.