[CLAM] Is this project still active (and still no Lucid packages)?

[Vincent Meyer]

Hi David,

That was it! It all worked well now. Big thanks from cold & rainy
Switzerland!
Since I have those maverick amd64 deb files on my computer (see below), and
you don't have any mean to generate them yourself, would it be useful to
anybody if I put them at your disposal?
If so, just let me know exactly what you need, and I'll send you a link to
fetch them, so that you can add them to the svn repo page (
http://clam-project.org/download/linux-ubuntu-maverick/svnsnapshots/).

clam-chordata_1.1.0~svn14674-1_amd64.deb
clam-networkeditor-examples_1.4.1-1_all.deb
clam-networkeditor_1.4.1-1_amd64.deb
clam-tools_1.4.1~svn14674-1_all.deb
libclam-doc_1.4.1~svn14674-1_all.deb
libclam-plugins1.4-dbg_1.4.1~svn14674-1_amd64.deb
libclam-plugins1.4-dev_1.4.1~svn14674-1_amd64.deb
libclam-plugins1.4_1.4.1~svn14674-1_amd64.deb
libclam-qtmonitors-dev_1.4.1-1_amd64.deb
libclam-qtmonitors1.4_1.4.1-1_amd64.deb
libclam1.4-dbg_1.4.1~svn14674-1_amd64.deb
libclam1.4-dev_1.4.1~svn14674-1_amd64.deb
libclam1.4_1.4.1~svn14674-1_amd64.deb

Cheers,

Vincent


On Fri, Feb 25, 2011 at 14:17, David García Garzón <
david.garcia at barcelonamedia.org> wrote:

> On Friday 25 February 2011 11:34:39 Vincent Meyer wrote:
> > Hi David,
> >
> > My bad: indeed, I did not pay attention to the platform dependence. On my
> > home computer, running a 32-bit version, I could install everything
> > smoothly yesterday evening. Thanks!
> >
> > Now, on the 64-bit system, I just tried the series of commands you
> > recommended. While part of it did run smoothly, I also had some
> dependency
> > issues like:
>
> > dpkg: dependency problems prevent configuration of
> libclam-plugins1.4-dev:
> >  libclam-plugins1.4-dev depends on clam-devel; however:
> >  Package clam-devel is not installed.
>
> What a weird dependency name, clam-devel should be libclam1.4-dev or at it
> most virtual libclam-dev. Fixed on subversion. I wont regenerate packages
> until i have some spare time. Anyway, it is unlikely you need such a
> package.
> You can just use the plugins from the network editor without the -dev
> package.
>
> > E: Unable to find a source package for clam-network
>
> yep, that's another typo in the script i sent you. The source package in
> the
> 'for/in' sentence should be clam-networkeditor not clam-network.
>
> > E: Build-Depends dependency for clam-chordata cannot be satisfied because
> > the package libclam-qtmonitors-dev cannot be found
>
> Yep, that missing package is generated by teh clam-networkeditor source. As
> you get it compiled then this one should work as well.
>
>
> > (I might have missed some others in the list...)
> >
> > At the end of the process, I end up with the following deb packages being
> > successfully built:
> >
> > clam-tools_1.4.1~svn14674-1_all.deb
> > libclam-doc_1.4.1~svn14674-1_all.deb
> > libclam1.4_1.4.1~svn14674-1_amd64.deb
> > libclam-plugins1.4_1.4.1~svn14674-1_amd64.deb
> > libclam1.4-dbg_1.4.1~svn14674-1_amd64.deb
> > libclam-plugins1.4-dbg_1.4.1~svn14674-1_amd64.deb
> > libclam1.4-dev_1.4.1~svn14674-1_amd64.deb
> > libclam-plugins1.4-dev_1.4.1~svn14674-1_amd64.deb
> >
> > Is there some other thing I can configure to get access to the missing
> > clam-devel and solve the dependency problems?
> >
> > Big thanks again to you for the support.
>
> No problem. Thank you for the report. It is helping to get a cleaner
> package
> building and installation. Cheers.
>
> David.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clam-project.org/pipermail/clam-users-clam-project.org/attachments/20110225/18dc1d32/attachment-0003.htm>