Frozen Squeeze, broken packages and bug reports

Squeeze is frozen for some time now and will be released when it’s ready, of course. Currently, I have at least two packages that have reported bugs, but it seems that they are making no progress. The first package is BackupPC.One of the bugs is #600654 and the other is #601843. Where as the first is just a cosmetic bug displaying filesystem usage of the backup volume, the other seems to have a functional impact: the backup pool doesn’t get cleaned up properly each night.

Sadly the maintainer seems a little bit absent, so maybe someone else can do a NMU to get BackupPC into shape for release? Would be nice, though… ๐Ÿ˜‰ 

The other package is spamassassin or more exactly libnetaddr-ip-perl and bug #601601. Whereas the BackupPC maintainer is rather quiet, there’s lot of activity for the other bug but still I get these errors when running Spamassassin by cron: 

netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included
netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included

Although I’m confident that #601601 will be solved soon, I don’t really know about the BackupPC bugs, except writing additional info mails to those bugs with "add me!" comment.

UPDATE 17.11.2010:
libnetaddr-ip-perl (#601601) seems to be fixed now.



  1. #601601 should be fixed in
    #601601 should be fixed in 4.035+dfsg-3 (in experimental) and 4.035+dfsg-4 (uploaded to unstable some minutes ago). if you still see the problems please shout ๐Ÿ™‚

    (BTW: the bug doesn’t affect the version in testing, AFAIK.)

    1. Ah, great!
      And yes, I’m

      Ah, great!

      And yes, I’m using unstable, but I wanted to take care that these bugs are fixed in testing/squeeze before it is released. ๐Ÿ™‚

    2. I’ve upgraded my system just
      I’ve upgraded my system just a few minutes ago and confirm, that the bug in libnetaddr-ip-perl has gone away. At least on my system! Thanks! ๐Ÿ™‚

Comments are closed.