[Debian-ha-maintainers] Comments regarding pacemaker_1.1.8+git20121009-1_amd64.changes

Martin Gerhard Loschwitz martin.loschwitz at gmail.com
Wed Mar 6 12:12:47 UTC 2013


Hello there,

Am 20.10.2012 um 11:37 schrieb Luca Falavigna <ftpmaster at debian.org>:
       ^^^^^^^^^^

> Hi!
> 
> this is a quick update on what's going on with your package in NEW.
> 
> We're holding it due to a potential transition which would affect some reverse
> dependencies. As Wheezy is frozen, Release Team asked us to refrain from
> processing packages which introduce unplanned transitions, as this could delay
> the Wheezy release even further.
> 
So what's the status on this? that was 3.5 months ago and Linux-HA development
has almost completely come to a stop in Debian meanwhile; the Pacemaker 1.1.7
package has a security issue (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700923)
that needs fixing.

> If you think your package should be targeted Wheezy, please let Release Team
> know and discuss with them about the best way to handle the transition. If that
> is not the case, your package will be processed after Wheezy release. If you
> want to give it broader testing, there is another option: we can reject it from
> the NEW queue, and let you upload it to experimental instead.
> 
No, I don't think the package should be targeted Wheezy. I just didn't know that
"Freeze" for Wheezy would mean that Unstable development comes to a stop as
well.

Quite frankly, I am not completely sure that I understand what "transition" you are 
talking about; to the best of my knowledge, there are some packages depending on 
Pacemaker (mostly anything related to DLM) but the stack as it currently is in 
wheezy is very much "done" and I don't see how updating Pacemaker in Unstable
would change that.

> Thanks, and keep up the good work!

Looking forward to your answers,
Martin


More information about the Debian-ha-maintainers mailing list