From: Ed Tomlinson <tomlins@cam.org>
To: Marco Roeland <marco.roeland@xs4all.nl>
Cc: Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: GIT 0.99.8d
Date: Sun, 16 Oct 2005 18:15:33 -0400 [thread overview]
Message-ID: <200510161815.33833.tomlins@cam.org> (raw)
In-Reply-To: <20051016185540.GA27162@fiberbit.xs4all.nl>
Hi,
This explains things. I am not building via the debian package. What happened is that
sid (amd64) dropped libcurl3-dev and I did not add one of the other packages...
Thanks
Ed
On Sunday 16 October 2005 14:55, Marco Roeland wrote:
> On Sunday October 16th 2005 Junio C Hamano wrote:
>
> > > Debian users beware. This version introduces a dependency - package:
> > > libcurl3-gnutls-dev
> > > is now needed to build git.
> >
> > Is this really true? The one I uploaded was built on this
> > machine:
> >
> > : siamese; dpkg -l libcurl\* | sed -ne 's/^ii //p'
> > libcurl3 7.14.0-2 Multi-protocol file transfer library, now wi
> > libcurl3-dev 7.14.0-2 Development files and documentation for libc
> >
> > Having said that, a tested patch to debian/control to adjust
> > Build-Depends is much appreciated.
>
> The present line is correct. In 'debian/control' the line reads
> (word-wrapped here):
>
> Build-Depends-Indep: libz-dev, libssl-dev,
> libcurl3-dev|libcurl3-gnutls-dev|libcurl3-openssl-dev, asciidoc (>=
> 6.0.3), xmlto, debhelper (>= 4.0.0), bc
>
> So it works correct on 'stable' versions ('libcurl3-dev') and
> latest 'unstable' as well, where you have the choice of either
> 'libcurl3-gnutls-dev' or 'libcurl3-openssl-dev'.
next prev parent reply other threads:[~2005-10-16 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-16 5:41 GIT 0.99.8d Junio C Hamano
2005-10-16 14:24 ` Ed Tomlinson
2005-10-16 18:22 ` Junio C Hamano
2005-10-16 18:55 ` Marco Roeland
2005-10-16 22:15 ` Ed Tomlinson [this message]
2005-10-17 5:29 ` David Lang
2005-10-18 5:53 ` GIT 0.99.8e Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510161815.33833.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.roeland@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).