Hi Anibal,

On Sat, Jul 12, 2008 at 2:07 PM, Aníbal Monsalve Salazar
<[EMAIL PROTECTED]> wrote:
> Package: claws-mail-extra-plugins
> Severity: serious
> Version: 3.5.0-1
> Tags: sid
> Justification: fails to build from source
>
> There was an error while trying to autobuild your package:
>
> Automatic build of claws-mail-extra-plugins_3.5.0-1 on goetz by sbuild/alpha 
> 99.999
> Build started at 20080703-0638
>
> [...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 5), quilt, libglib2.0-dev, libgtk2.0-dev, 
> libclaws-mail-dev (>= 3.5.0), flex, bison, libcurl-dev, autotools-dev, 
> pkg-config, libetpan-dev (>= 0.52), libperl-dev (>= 5.8.0), perl (>= 5.8.0), 
> docbook-to-man, libxml2-dev, libkrb5-dev, libgpgme11-dev (>= 1.1.1), 
> libgtkhtml2-dev (>= 2.6), libsynce0-dev, librapi2-dev, libnotify-dev, 
> libytnef0-dev
>
> [...]
> Package libcurl-dev is a virtual package provided by:
>  libcurl4-openssl-dev 7.18.2-5
>  libcurl4-gnutls-dev 7.18.2-5
> You should explicitly select one to install.
> E: Package libcurl-dev has no installation candidate

I wonder why that sbuild doesn't behave like others (pasted from ia64 log [0]):

,-------
| Building dependency tree...
| Package libcurl-dev is a virtual package provided by:
|   libcurl4-gnutls-dev 7.18.2-6
|   libcurl4-openssl-dev 7.18.2-6
| You should explicitly select one to install.
| E: Package libcurl-dev has no installation candidate
| libcurl-dev is a virtual package provided by: libcurl4-gnutls-dev
libcurl4-openssl-dev
| Using libcurl4-gnutls-dev (no default, using first one)
`-------

Any reason?
Anyway I think the right dependency is already provided by
libetpan-dev, so this may be removed as well. Will take some time to
fix, because it will pass through new queue (new plugin on this
release).

regards,

[0] 
http://buildd.debian.org/fetch.cgi?&pkg=claws-mail-extra-plugins&ver=3.5.0-1&arch=ia64&stamp=1215793395&file=log
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Too much is just enough. -- Mark Twain, on whiskey»

Reply via email to