Your message dated Mon, 19 Mar 2018 18:28:48 +0100 with message-id <[email protected]> and subject line Re: Bug#893500: pacemaker_1.1.16-1~bpo8+1_amd64.deb has this insufficient dependency: libpe-rules2 (>= 1.0.10) has caused the Debian Bug report #893500, regarding pacemaker_1.1.16-1~bpo8+1_amd64.deb has this insufficient dependency: libpe-rules2 (>= 1.0.10) 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 [email protected] immediately.) -- 893500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893500 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: pacemaker Version: 1.1.16-1~bpo8+1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrade from Debian wheezy to Debian jessie (with backports) * What exactly did you do (or not do) that was effective (or ineffective)? apt-get dist-upgrade * What was the outcome of this action? a pacemaker installation wich failes to start because libpe-rules2 was kept in an outdates version due to this dependency: libpe-rules2 (>= 1.0.10) * What outcome did you expect instead? a pacemaker installation wich starts * solution upgrade libpe-rules2 to 1.1.16-1~bpo8+1 *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.10 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-5-amd64 (SMP w/24 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pacemaker depends on: ii corosync 2.4.2-3~bpo8+1 ii dbus 1.8.22-0+deb8u1 ii init-system-helpers 1.22 ii libc6 2.19-18+deb8u10 ii libcfg6 2.4.2-3~bpo8+1 ii libcib4 1.1.16-1~bpo8+1 ii libcmap4 2.4.2-3~bpo8+1 ii libcorosync-common4 2.4.2-3~bpo8+1 ii libcpg4 2.4.2-3~bpo8+1 ii libcrmcluster4 1.1.16-1~bpo8+1 ii libcrmcommon3 1.1.16-1~bpo8+1 ii libcrmservice3 1.1.16-1~bpo8+1 ii libglib2.0-0 2.42.1-1+b1 ii libgnutls-deb0-28 3.3.8-6+deb8u7 ii liblrmd1 1.1.16-1~bpo8+1 ii libpam0g 1.1.8-3.1+deb8u2+b1 ii libpe-rules2 1.1.16-1~bpo8+1 ii libpe-status10 1.1.16-1~bpo8+1 ii libpengine10 1.1.16-1~bpo8+1 ii libqb0 1.0.1-1~bpo8+1 ii libquorum5 2.4.2-3~bpo8+1 ii libstonithd2 1.1.16-1~bpo8+1 ii libtransitioner2 1.1.16-1~bpo8+1 ii lsb-base 4.1+Debian13+nmu1 ii pacemaker-common 1.1.16-1~bpo8+1 ii pacemaker-resource-agents 1.1.16-1~bpo8+1 ii perl 5.20.2-3+deb8u9 Versions of packages pacemaker recommends: ii fence-agents 4.0.25-1~bpo8+1 ii pacemaker-cli-utils 1.1.16-1~bpo8+1 Versions of packages pacemaker suggests: ii cluster-glue 1.0.12~rc1+hg2777-1.2 ii crmsh 2.3.2-4~bpo8+1 ii pcs 0.9.155+dfsg-2~bpo8+1 -- Configuration Files: /etc/init.d/pacemaker changed: desc="Pacemaker Cluster Manager" prog="pacemakerd" PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/sbin" success() { echo -ne "[ OK ]\r" } failure() { echo -ne "[FAILED]\r" } status() { pid=$(pidof $1 2>/dev/null) rtrn=$? if [ $rtrn -ne 0 ]; then echo "$1 is stopped" else echo "$1 (pid $pid) is running..." fi return $rtrn } if [ -d /etc/sysconfig ]; then [ -f /etc/init.d/functions ] && . /etc/init.d/functions [ -f /etc/sysconfig/pacemaker ] && . /etc/sysconfig/pacemaker [ -z "$LOCK_FILE" ] && LOCK_FILE="/var/lock/subsys/pacemaker" fi if [ -d /etc/default ]; then [ -f /etc/default/pacemaker ] && . /etc/default/pacemaker [ -z "$LOCK_FILE" ] && LOCK_FILE="/var/lock/pacemaker" fi start() { echo -n "Starting $desc: " # most recent distributions use tmpfs for $/var/run # to avoid to clean it up on every boot. # they also assume that init scripts will create # required subdirectories for proper operations mkdir -p /var/run if status $prog > /dev/null 2>&1; then success else $prog > /dev/null 2>&1 # Time to connect to corosync and fail sleep 5 if status $prog > /dev/null 2>&1; then touch $LOCK_FILE pidof $prog > /var/run/$prog.pid success else failure rtrn=1 fi fi echo } stop() { ! status $prog > /dev/null 2>&1 && return echo -n "Signaling $desc to terminate: " kill -TERM $(pidof $prog) > /dev/null 2>&1 success echo echo -n "Waiting for cluster services to unload:" while status $prog > /dev/null 2>&1; do sleep 1 echo -n "." done rm -f $LOCK_FILE rm -f /var/run/$prog.pid success echo } restart() { stop start } rtrn=0 case "$1" in start) start ;; restart|reload|force-reload) restart ;; condrestart|try-restart) if status $prog > /dev/null 2>&1; then restart fi ;; status) status $prog rtrn=$? ;; stop) stop ;; *) echo "usage: $0 {start|stop|restart|reload|force-reload|condrestart|try-restart|status}" rtrn=2 ;; esac exit $rtrn -- no debconf information
--- End Message ---
--- Begin Message ---Control: reassign -1 libpe-rules2 Control: retitle -1 libpe-rules2 misses dependency on libcrmcommon2 Control: found -1 1.1.7-1 Control: fixed -1 1.1.13-1 Andreas Papst <[email protected]> writes: > * What led up to the situation? > > Upgrade from Debian wheezy to Debian jessie (with backports) > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > apt-get dist-upgrade > > * What was the outcome of this action? > > a pacemaker installation wich failes to start > because libpe-rules2 was kept in an outdates version > due to this dependency: > libpe-rules2 (>= 1.0.10) > > * What outcome did you expect instead? > > a pacemaker installation wich starts > > * solution > > upgrade libpe-rules2 to 1.1.16-1~bpo8+1 Hi Andreas, Thanks for the report. Strictly speaking this isn't a problem of the pacemaker package, but that of the old libpe-rules2, which misses a dependency on libcrmcommon2. This was fixed by the full repackaging of Pacemaker in 1.1.13-1. While we could add strict versioned dependencies for each component library, I'd like to avoid that if possible (for being overly strict and requiring more careful maintenance). So I'm inclined to leave this as-is for the time being. Please reopen this bug if you disagree. -- Regards, Feri
--- End Message ---
