[Pkg-clamav-devel] Another upload to unstable, freeze exception?

[Scott Kitterman]

"Michael Tautschnig" <mt at debian.org> wrote:

>> On Saturday, September 25, 2010 03:40:33 pm Michael Tautschnig wrote:
>> > Hi all,
>> > 
>> > I'm considering to do another upload to unstable with the most recent
>> > changes; is there anything that should stop me from doing so?
>> > 
>> > Furthermore, it would IMHO make sense to ask for a freeze exception to get
>> > that version into Squeeze. I'm not sure whether the release time will like
>> > this, but we could ask at least. In fact, this is the foremost reason for
>> > me for doing another upload to unstable, even though the previous version
>> > wasn't even sitting in there for a week.
>> > 
>> > Do people have any opinions on those two points? Especially Stephen, what
>> > would you think?
>> 
>> May understanding is that for Squeeze, they will accept post release updates 
>> to a new version, so I think a freeze exception to at least release with the 
>> current one is a very good idea.
>> 
>> What's in your queue for the next upload?
>> 
>
>Ah, yes, it might have been nice to include the current status of the changelog
>entry:
>
>clamav (0.96.3+dfsg-2) unstable; urgency=low
>
>  [ Stephen Gran ]
>  * Add NotifyClamd only if set to nonempty value.
>  
>  [ Michael Tautschnig ]
>  * Cherry-pick from upstream: Only enable RLIMIT_DATA warning on *BSD 
>    (already included in Ubuntu's 1ubuntu3).
>  * Do rmdir /etc/clamav, /var/log/clamav, /var/lib/clamav in all postrms as
>    we cannot count on clamav-base's postrm to be the last one being called
>    (thanks piuparts).
>  
Yes. I think you should upload that and then ask the release team to let it into Squeeze.

Scott K