Bug#680961: unblock: redhat-cluster/3.0.12-3.2
I would like to ask for a freeze-exception for redhat-cluster
3.0.12-3.2 uploaded as NMU to unstable.
I encoutered redhat-cluster during searching to help on RC bugs for
I added two patches, I agree that afterwards I should only have added
the patch for the FTBFS. Please let me know if I should revert the
First the diffstat:
diffstat for redhat-cluster_3.0.12-3.1 redhat-cluster_3.0.12-3.2
debian/patches/0006-Fix-FTBFS-due-to-moved-header-files.patch | 36 ++++++++++
debian/patches/0007-Add-remote_fs-to-Required-Start-and-Required-Stop.patch | 32 ++++++++
redhat-cluster-3.0.12/debian/changelog | 11 +++
redhat-cluster-3.0.12/debian/patches/series | 2
4 files changed, 81 insertions(+)
The first patch 0006-Fix-FTBFS-due-to-moved-header-files.patch is to
fix the FTBFS.
This was due to pacemaker moved header files.
The second patch is
0007-Add-remote_fs-to-Required-Start-and-Required-Stop.patch. It is to
add $remote_fs facility to Required-Start and Required-Stop to the
initscripts for gfs and gfs2.
Should I remove this one? I'm sorry It was not my intention to put
extra work on you.
A side note: redhat-cluster has still 1 further serious
release-critical bug. It is about co-installability of rgmanager
and resource-agents (both maintained by Debian HA Maintainers), which
is still unresolved.
In case you agree on all the above:
Many thanks for you work!
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash