[Pkg-clamav-devel] OK, is it just me?

[Scott Kitterman]

On Thursday 04 September 2008 14:28:20 Scott Kitterman wrote:
> On Thursday 04 September 2008 10:24, Stephen Gran wrote:
> > This one time, at band camp, Stephen Gran said:
> > > Oh, and the question that occurs to me is, how do we get the contents
> > > of the test branch back into debian/unstable in such a way that people
> > > who have already cloned it can pull cleanly?  The only thing I can come
> > > up with is running git revert $patch until I've rewound HEAD back to
> > > where the 0.93 and 0.94 branches diverge, then git merge test.  This
> > > will result in some really awful looking history, so if there's a
> > > better way I'd like to know about it.
> >
> > In the absence of a better plan presenting itself, this is what I've gone
> > ahead and done.  I've also merged into volatile, so the two branches are
> > basically in sync now, modulo normal changelog differences.  An upload
> > to volatile is underway.  Luk is looking at getting 0.93.3 unblocked and
> > migrated to testing (hopefully :), and once it does, we can upload 0.94.
> > There is a soname change in libclamav, so we'll need to start working
> > on making sure the rdepends still build and work.
> >
> > Scott, I know you work on klamav - can you take a look at that?  For the
> > rest, here's a dd-list:
>
> Yes.  I'll look at that.
>
> > Cédric Delfosse <cedric at debian.org>
> >    python-clamav
> >
> > Jonas Genannt <jonas.genannt at capi2name.de>
> >    php-clamavlib
> >
> > Bart Martens <bartm at debian.org>
> >    gurlchecker
> >
> > Rene Mayrhofer <rene.mayrhofer at gibraltar.at>
> >    havp
> >
> > Alexander Wirt <formorer at debian.org>
> >    dansguardian
> >
> > It would be nice if we could either work with those maintainers, or
> > bring them into the team and maintain the packages collectively - this
> > sort of thing happens every other release of clamav, it seems, so it
> > would be nice to be able to have a sensible workflow.
> >
> > Does someone feel like volunteering to start checking the affected
> > packages?  Or contacting the maintainers to let them know there are
> > changes coming?
>
> Once I have the source package for 0.94~dsfg-1 (I assume that's what it
> will be) I'll throw it and and all the rdpends into an Ubuntu Personal
> Package Archive (PPA) and see what builds and what doesn't.  Note that
> because these PPA repositories are not signed and the recent uptick in DNS
> cache poisoning attacks I will not leave these in the PPA for people to use
> for testing.
>
> If I find problems, I'll be glad to pass the information on here and to the
> affected maintainers.  I'll also see if I can get Ubuntu people working on
> patching if needed since some of the maintainers are more responsive than
> others.
>
> I know I'll be building on the Ubuntu Intrepid toolchain instead of
> Lenny/Sid, but so far, for clamav integration issues that's never been a
> problem.

My initial assessment is that it's another round of "Oh, gee, nothing builds, 
let's go patch everything".  I think the way you did it last time (IIRC, 
binnmu everything and then there's a real issue to deal with if it fails) 
seemed to work fine.

I started to look into Klamav, but haven't got it figured yet.

Scott K