On Thu, Jun 30, 2022 at 04:48:43AM -0700, Simon Chopin wrote:
> Quoting Heinrich Schuchardt (2022-06-29 12:56:57)
> > On 6/29/22 10:33, Simon Chopin wrote:
> > > As part of our efforts to support the Rust toolchain in main, we need to
> > > have libgit2 in main (depend
On Wed, 29 Jun 2022 at 20:33, Simon Chopin
wrote:
> Hi!
>
> As part of our efforts to support the Rust toolchain in main, we need to
> have libgit2 in main (dependency of cargo). However, it currently links
> against mbedTLS for its HTTPS backend rather than OpenSSL, for licensing
Quoting Heinrich Schuchardt (2022-06-29 12:56:57)
> On 6/29/22 10:33, Simon Chopin wrote:
> > Hi!
> >
> > As part of our efforts to support the Rust toolchain in main, we need to
> > have libgit2 in main (dependency of cargo). However, it currently links
> > agai
On 6/29/22 10:33, Simon Chopin wrote:
Hi!
As part of our efforts to support the Rust toolchain in main, we need to
have libgit2 in main (dependency of cargo). However, it currently links
against mbedTLS for its HTTPS backend rather than OpenSSL, for licensing
reasons IIUC. Those reasons would
Hi!
As part of our efforts to support the Rust toolchain in main, we need to
have libgit2 in main (dependency of cargo). However, it currently links
against mbedTLS for its HTTPS backend rather than OpenSSL, for licensing
reasons IIUC. Those reasons would now be invalid with the new OpenSSL
3.0
Hi,
On Fri, 20 Feb 2015 12:00:17 +, Jonathan Riddell wrote:
> I'd say that makes it the responsibility of whatever team cares about
> libgit2-glib and gitg to sort. I'm happy to remove from the archive
> if that means we can get the newer version of libgit in.
As far
On Tue, Feb 17, 2015 at 12:14:02PM +0100, Harald Sitter wrote:
> On Mon, Feb 16, 2015 at 8:14 PM, Jackson Doak wrote:
> > Just looking through upstream logs, this should be as simple as uploading
> > libgit2-glib 0.22.0 and gitg 3.15.1
>
> unfortunately there's symbol
On Mon, Feb 16, 2015 at 8:14 PM, Jackson Doak wrote:
> Just looking through upstream logs, this should be as simple as uploading
> libgit2-glib 0.22.0 and gitg 3.15.1
unfortunately there's symbol retractions without soname change :(
http://paste.ubuntu.com/10271618/
--
ubuntu-de
Just looking through upstream logs, this should be as simple as uploading
libgit2-glib 0.22.0 and gitg 3.15.1
On Tue, Feb 17, 2015 at 2:06 AM, Harald Sitter
wrote:
> it would be very lovely if someone who's interested in gitg could have
> a look at transitioning libgit2 - libgit2-gli
it would be very lovely if someone who's interested in gitg could have
a look at transitioning libgit2 - libgit2-glib - gitg to libgit2 0.22.
0.21 apparently had stability problems in the editor kate so 0.22 is a
minimum requirement there.
cheers
HS
--
ubuntu-devel mailing list
ubuntu-
10 matches
Mail list logo