I am curious as to how to handle this situation: shorewall-lite and
shorewall6-lite are both stuck from migrating. The excuses look like
this:
roberto@miami:~$ grep-excuses shorewall-lite
shorewall-lite (4.4.11.6-1+squeeze1 to 4.4.17-1)
Maintainer: Roberto C. Sanchez
10 days old (needed 10 days)
shorewall-lite (source, i386, amd64, armel, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc) has new bugs!
Updating shorewall-lite introduces new bugs: #610314
Not considered
roberto@miami:~$ grep-excuses shorewall6-lite
shorewall6-lite (4.4.11.6-1+squeeze1 to 4.4.17-1)
Maintainer: Roberto C. Sanchez
10 days old (needed 10 days)
shorewall6-lite (source, i386, amd64, armel, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc) has new bugs!
Updating shorewall6-lite introduces new bugs: #610327
Not considered
I think that this is because the bug was fixed in sid in version
4.4.16-1 (uploaded on January 15), but the bug was reported against
Squeeze version 4.4.11.6-1 on January 17). I uploaded version
4.4.11.6-1+squeeze1 later that same day (on January 17). Of course,
since 4.4.16-1 also corrected the problem but the problem had not yet
been reported, there was no reason to expect it to be mentioned in the
changelog.
Do I need to mention it in a future changelog (4.4.18 should be released
in a few weeks), or does get solved by manual hinting or some other way?
Regards,
-Roberto
--
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
Attachment:
signature.asc
Description: Digital signature