Reverts permissions on milter socket on upgrade

[Ryan Lovett]

Binary package hint: clamav

We have been using clamav-milter with postfix and had set the socket to 775 which group ownership of postfix. With a recent upgrade in Hardy, the clamav-milter package introduced the variable SOCKET_RWGROUP which does this for you. However, the package upgrade didn't check to see that we had manually set the permissions already and with the variable unset the milter init script changed the ownership so that postfix couldn't read it. On upgrade, the package should check the permissions on the socket and automatically set the SOCKET_RWGROUP variable in the defaults file if you require it.

[Scott Kitterman (kitterman)]

Is this with 0.95.2 from hardy-backports?

[Ryan Lovett (ryan-spacecoaster)]

On Wed, Sep 16, 2009 at 09:37:00PM -0000, Scott Kitterman wrote:
> Is this with 0.95.2 from hardy-backports?

Yes, 0.95.2+dfsg-4ubuntu1.1~hardy1.

Ryan

[Scott Kitterman (kitterman)]

I discussed this with the Debian clamav maintainer and he is going to have a look at this, possibly over the weekend.

[Scott Kitterman (kitterman)]

We just discussed this with him again:

<sgran> the problem is that currently there is no upgrade handling of the /etc/default file
<sgran> I'm not convinced I'm all that happy about introducing it, to be honest
<sgran> right now, people will get a normal dpkg prompt about it, telling them that file shipped in the .deb has changed but they have local changes and should do something about it
<sgran> I think that it's maybe not the friendliest way, but it is the safest and sanest way to do it
<sgran> (and it saves an awful lot of hassle on upgrade handling moving it from a config file shipped in the .deb to a conf file managed with ucf)

Is there some chance you were prompted on upgrade and accepted the new version?

[Ryan Lovett (ryan-spacecoaster)]

On Sat, Nov 07, 2009 at 07:10:57PM -0000, Scott Kitterman wrote:
> We just discussed this with him again:
>
> <sgran> the problem is that currently there is no upgrade handling of the /etc/default file
> <sgran> I'm not convinced I'm all that happy about introducing it, to be honest
> <sgran> right now, people will get a normal dpkg prompt about it, telling them that file shipped in the .deb has changed but they have local changes and should do something about it
> <sgran> I think that it's maybe not the friendliest way, but it is the safest and sanest way to do it
> <sgran> (and it saves an awful lot of hassle on upgrade handling moving it from a config file shipped in the .deb to a conf file managed with ucf)
>
> Is there some chance you were prompted on upgrade and accepted the new
> version?

It was a while ago, but I don't recally being prompted at the time.

Ryan

[Scott Kitterman (kitterman)]

There's a clamav update coming out soon. When it does, please keep an eye
out for this and let us know.

[Launchpad Janitor (janitor)]

[Expired for clamav (Ubuntu) because there has been no activity for 60 days.]