Your message dated Tue, 31 Aug 2010 18:08:02 +0200
with message-id <20100831160802.gb6...@inutil.org>
and subject line Re: Bug#589130: SPAM, Re: Bug#589130: keepalived: Upgrade to 
1.2 breaks package
has caused the Debian Bug report #589130,
regarding keepalived: Upgrade to 1.2 breaks package
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 ow...@bugs.debian.org
immediately.)


-- 
589130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: keepalived
Version: 1.1.19-1
Severity: grave
Justification: renders package unusable


after an upgrade from :

1.1.19 to 1.2.0-1

Keepalived doesn't work !



Other messages :


Starting keepalived: keepalived+ log_daemon_msg_post 'Starting
keepalived' keepalived
+ :
+ for file in '$TMPFILES'
+ test -e /tmp/.vrrp
+ for file in '$TMPFILES'
+ test -e /tmp/.healthcheckers
+ start-stop-daemon --start --quiet --pidfile /var/run/keepalived.pid
--exec /usr/sbin/keepalived
+ log_end_msg 0
+ '[' -z 0 ']'
+ retval=0
+ log_end_msg_pre 0
+ :
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ '[' -t 1 ']'
+ '[' xxterm '!=' x ']'
+ '[' xxterm '!=' xdumb ']'
+ '[' -x /usr/bin/tput ']'
+ '[' -x /usr/bin/expr ']'
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ '[' -z ']'
+ FANCYTTY=1
+ case "$FANCYTTY" in
+ true
++ /usr/bin/tput setaf 1
+ RED=''
++ /usr/bin/tput setaf 3                                                        
                                                         
+ YELLOW=''                                                                     
                                                         
++ /usr/bin/tput op                                                             
                                                         
+ NORMAL=''                                                                     
                                                         
+ '[' 0 -eq 0 ']'
+ echo .
.
+ log_end_msg_post 0
+ :
+ return 0
+ exit 0










-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core)
Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages keepalived depends on:
ii  iproute                       20080725-2 networking and traffic control too
ii  ipvsadm                       1:1.24-2.1 Linux Virtual Server support progr
ii  libc6                         2.9-23     GNU C Library: Shared libraries
ii  libpopt0                      1.16-1     lib for parsing cmdline parameters
ii  libssl0.9.8                   0.9.8o-1   SSL shared libraries

keepalived recommends no packages.

keepalived suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1:1.1.20-1

On Fri, Aug 13, 2010 at 04:30:08PM +0200, Alexander Wirt wrote:
> Remigiusz Świc schrieb am Friday, den 13. August 2010:
> 
> > Hi!
> > 
> > I have one question to package maintainer. Why have you uploaded
> > release 1.2 to Debian? In changelog we can read that this branch is
> > for development purposes (http://keepalived.org/changelog.html -
> > "Branch 1.2.0 created. This branch will host all new developments on
> > Keepalived. New code will be added in here only."). In sid it doesn't
> > matter, but in testing (which is now freezed) it is a big problem I
> > think.
> > 
> > Could you consider reverting package in testing to 1.1.20? By doing
> > this we can avoid a lot of problems in a future. I think that a lot of
> > users will be appreciated, not only me. :-)
> You are right, I'm working on it. 

This was done already, but apparently w/o a bug closer, closing it now.

Cheers,
        Moritz


--- End Message ---

Reply via email to