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

Bug#680961: marked as done (unblock: redhat-cluster/3.0.12-3.2)

Your message dated Sat, 21 Jul 2012 00:30:52 +0200
with message-id <20120720223052.GA21084@elende>
and subject line Re: Bug#680961: unblock: redhat-cluster/3.0.12-3.2
has caused the Debian Bug report #680961,
regarding unblock: redhat-cluster/3.0.12-3.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

680961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680961
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: freeze-exception

Hi Release-Team

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
second first.

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[1].

 [1]: http://bugs.debian.org/669446

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[2].

 [2]: http://lintian.debian.org/tags/init.d-script-missing-dependency-on-remote_fs.html

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[3]. It is about co-installability of rgmanager
and resource-agents (both maintained by Debian HA Maintainers), which
is still unresolved.

 [3]: http://bugs.debian.org/649068

In case you agree on all the above:

unblock redhat-cluster/3.0.12-3.2

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

--- End Message ---
--- Begin Message ---
Hi Release-Team

This was already unblocked.


Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: