Re: clamav needs updating
On Mon, Jul 23, 2007 at 04:13:18PM +0000, paddy@panici.net wrote:
> On Mon, Jul 23, 2007 at 02:58:57PM +0100, Stephen Gran wrote:
> > This one time, at band camp, Jim Popovitch said:
> > > On Mon, 2007-07-23 at 10:26 +0100, Stephen Gran wrote:
> > > > This one time, at band camp, Javier Amor Garc?a said:
> > > > > Hello,
> > > > > we are interested in the new version of clamav to use it in the new
> > > > > release of eBox [0].
> > > > > An updated ClamAV is one of the last missing pieces left for the release
> > > > > so we would like to know when the volatile package will be ready.
> > > > > It will be ready in the first half of this week?
> > > >
> > > > No, probably not. As I feared, we have found a piece of software
> > > > (avscan) that is broken by some changes in the clamav public API in this
> > > > release. I have been talking to the maintainer, and he is working on a
> > > > patch with upstream. Once I have some idea of how that's going, I will
> > > > upload to volatile, but not until we have a supportable path that
> > > > doesn't break other software in the archive, sorry.
> > >
> > > How long will you wait on the dependent project avscan before releasing
> > > clamav?
> >
> > My interpretation of volatile's role with regard to the archive means
> > that the only answer possible is "when avscan is ready". Maybe the
> > other volatile team members will have a different opinion.
>
> Can the new clam packages conflict against an avscan version that
> hasn't been released yet but will have the fix in it ?
sorry,
conflict against versions *prior to* an as-yet-unreleased fixed version
Regards,
Paddy
Reply to: