Package Details: libgit2-git 2:1.1.0.r279.g935f85131-1

Git Clone URL: https://aur.archlinux.org/libgit2-git.git (read-only, click to copy)
Package Base: libgit2-git
Description: A linkable library for Git
Upstream URL: https://libgit2.github.com/
Licenses: GPL2
Conflicts: libgit2
Provides: libgit2
Submitter: herve
Maintainer: None
Last Packager: Nukesor
Votes: 10
Popularity: 0.000000
First Submitted: 2009-09-13 14:25 (UTC)
Last Updated: 2021-02-16 22:33 (UTC)

Dependencies (5)

Required by (130)

Sources (1)

Latest Comments

1 2 3 Next › Last »

Scimmia commented on 2018-01-16 12:48 (UTC)

You can package it for yourself, you can't put it in the AUR just because you want a newer version, and you certainly can't destroy a -git package to do it.

Anyway, fixed

albfan commented on 2018-01-16 12:34 (UTC)

strictly prohibited? So I cannot have a package libgit2-0.24 or libgit2-0.21 if I needed? Is this policy for real?

By the time ABS was 0.21 I (and I suppose others) need 0.25 (ahead from ABS). Should I provide a unstable version instead of a tar (iirc at that time git master fails compiling)

I don't need this package ahead of ABS anymore, so I will abbandon it so you can do whatever you want with it.

Scimmia commented on 2018-01-16 12:31 (UTC)

Or the original contributors, epoch, provides, conflicts, ...

eschwartz commented on 2018-01-16 11:53 (UTC)

You still have not restored the old pkgver() function.

Scimmia commented on 2018-01-15 23:32 (UTC)

Do you know what git is? Do you know what the -git at the end of the pkgname means? Go read the VCS package wiki page if you don't. As it is, you've destroyed this package. Reverting commits has nothing to do with rewriting history.

As for "policy to provide stable versions ahead from ABS", there is, it is strictly prohibited.

albfan commented on 2018-01-15 21:01 (UTC)

I receive this package to update to a version higher that 0.21, but stable. It do his work for a while.

@Scimmia is there a policy to provide stable versions ahead from ABS? If not then libgit2-git with an stable tar seems a good option.

There's no way to rewrite history, and I refuse to revert commits. You should know that.

Scimmia commented on 2018-01-15 17:19 (UTC)

Hint: start by reverting your last 2 commits, they are completely and totally wrong.

albfan commented on 2018-01-15 13:43 (UTC)

I will rework this to use git in a while

codyps commented on 2016-02-19 16:19 (UTC) (edited on 2016-02-19 16:19 (UTC) by codyps)

check() fails due to libgit2_clar failing. Adding CTEST_OUTPUT_ON_FAILURE=1 (which should be enabled by default in the PKGBUILD) tells me: online::clone::bitbucket_style [/tmp/pacaurtmp-cody/libgit2-git/src/libgit2/tests/online/clone.c:348] Function call failed: (git_clone(&g_repo, "https://libgit3@bitbucket.org/libgit2/testgitrepository.git", "./foo", &g_options)) error -1 - HTTP parser error: unexpected content-length header Unclear what the cause is.

rafi commented on 2014-07-02 18:13 (UTC)

Failed to checkout: fatal: ambiguous argument 'development': unknown revision or path not in the working tree.

1 2 3 Next › Last »