Package Details: python2-dulwich 0.19.11-1

Git Clone URL: https://aur.archlinux.org/python2-dulwich.git (read-only, click to copy)
Package Base: python2-dulwich
Description: Pure-Python implementation of the Git file formats and protocols
Upstream URL: https://www.dulwich.io/
Licenses: GPL2
Submitter: felipec
Maintainer: drrossum
Last Packager: drrossum
Votes: 107
Popularity: 0.000310
First Submitted: 2013-09-22 18:00
Last Updated: 2019-02-07 14:04

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

tobias.bln commented on 2017-09-16 15:48

1. gpg --recv-keys 1DF7EADF3B648883

2. +++ Edited PKGBUILD for python2-dulwich Version 0.18.3 +++

# Maintainer: Timothée Ravier <tim@siosm.fr>

pkgname=(python2-dulwich)
pkgver=0.18.3
pkgrel=1
pkgdesc='Pure-Python implementation of the Git file formats and protocols'
arch=('any')
url='https://www.dulwich.io/'
license=('GPL2')
depends=()
options=(!emptydirs)
source=("https://www.dulwich.io/releases/dulwich-${pkgver}.tar.gz"{,.asc})
validpgpkeys=('DC837EE14A7E37347E87061700806F2BD729A457') # Jelmer Vernooij
sha256sums=('d34c2628f89a5ac632fa462b2edd5afcfbf512793cfa14452d4c52f786962a8a'
'SKIP')

build() {
cd "dulwich-${pkgver}"
python2 setup.py build
}

package_python2-dulwich() {
depends=('python2')
conflicts=('python-dulwich')
cd "dulwich-${pkgver}"
python2 setup.py install --root="$pkgdir/" --skip-build --optimize=1
}

# vim:set ts=2 sw=2 et:

gokkep commented on 2017-09-16 11:06

Trying to install package rabbitcvs-nemo on 4.12.13-1-ARCH.
Get a conflict with this package.
When doing: packer python-dulwich I get,

loading packages...
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: python2-dulwich and python-dulwich are in conflict

Okay solved by using the comment on 2017-08-08 11:24. During the build I edited the PKGBUILD and removed the original content with the content of that comment and could install!!
I am not able to solve this, what can I do?

nobicycle commented on 2017-08-13 03:22

Regarding 9A2D24A504D1E9F8 ...

Where to go to "verify the authenticity of the retrieved public key by comparing its fingerprint with one that the owner published on an independent source(s) (i.e., contacting the person directly)"
https://wiki.archlinux.org/index.php/GnuPG

Even if the security check above is ignored, it seems the keyservers don't work anyway:

$ gpg --recv-keys 9A2D24A504D1E9F8
gpg: keyserver receive failed: Server indicated a failure
$ gpg --keyserver pool.sks-keyservers.net --recv-keys 9A2D24A504D1E9F8
gpg: keyserver receive failed: Connection closed in DNS
$ gpg --keyserver ha.pool.sks-keyservers.net --recv-keys 9A2D24A504D1E9F8
gpg: keyserver receive failed: Connection closed in DNS

tobias.bln commented on 2017-08-08 11:24

+++ Edited PKGBUILD for python2-dulwich +++

# Maintainer: Timothée Ravier <tim@siosm.fr>

pkgname=(python2-dulwich)
pkgver=0.17.2
pkgrel=1
pkgdesc='Pure-Python implementation of the Git file formats and protocols'
arch=('any')
url='https://www.dulwich.io/'
license=('GPL2')
depends=()
options=(!emptydirs)
source=("https://www.dulwich.io/releases/dulwich-${pkgver}.tar.gz"{,.asc})
validpgpkeys=('DC837EE14A7E37347E87061700806F2BD729A457') # Jelmer Vernooij
sha256sums=('90b5c1025f60c68b98980f85950860b980692053c7c5dd93c19cc3cb87f186b2'
'SKIP')

build() {
cd "dulwich-${pkgver}"
python2 setup.py build
}

package_python2-dulwich() {
depends=('python2')
conflicts=('python-dulwich')
cd "dulwich-${pkgver}"
python2 setup.py install --root="$pkgdir/" --skip-build --optimize=1
}

# vim:set ts=2 sw=2 et:

electricprism commented on 2017-07-25 16:58

gpg --recv-keys 9A2D24A504D1E9F8

cocoche007 commented on 2017-07-22 23:54

gpg --keyserver pool.sks-keyservers.net --recv-keys 9A2D24A504D1E9F8
didn't work

gpg --keyserver ha.pool.sks-keyservers.net --recv-keys 9A2D24A504D1E9F8
is OK for me

JohnRobson commented on 2017-07-17 22:29

Please, FIX the PKGBUILD file, python2 and python3 packages are mutually exclusive.

drrossum commented on 2017-07-17 19:37

The python2 and python3 packages are mutually exclusive because of the scripts in /usr/bin. I added conflicts to the PKGBUILD to prevent users from accidentally installing both versions

mrapp commented on 2017-07-17 18:11

I am unable to update this package since weeks because of conflicting files as pointed out by mani.zaeim. Will this package be fixed anytime soon?

drrossum commented on 2017-07-04 10:05

You should probably choose which package you want to provide the scripts in /usr/bin and modify the package() function of the other.