Package Details: python2-dulwich 0.19.11-1

Git Clone URL: (read-only, click to copy)
Package Base: python2-dulwich
Description: Pure-Python implementation of the Git file formats and protocols
Upstream URL:
Licenses: GPL2
Submitter: felipec
Maintainer: drrossum
Last Packager: drrossum
Votes: 104
Popularity: 0.000000
First Submitted: 2013-09-22 18:00
Last Updated: 2019-02-07 14:04

Latest Comments

1 2 3 4 5 Next › Last »

polyzen commented on 2018-12-28 05:45

Note: python-dulwich (Python 3 package) has been added to the repos.

polyzen commented on 2018-04-10 05:50

Of course, but it's not just one person who has to then manually update the python-dulwich pkgbuild. It's at least two assuming the person who voted on the xandikos package uses it ;). I also of course understand the reluctance to adding a co-maintainer.

drrossum commented on 2018-04-09 07:01

You can always modify the PKGBUILD, right? I don't understand why you would not be able to bump any package's version anytime you want.

polyzen commented on 2018-04-08 01:03

May I co-maintain this package? Dulwich's upstream maintainer has another project called Xandikos that I have packaged, but I can't bump its version until this has also been updated (at least for changes like this).

andybz commented on 2017-11-24 02:38

@drrossum: Just noticed the new version today as I was updating one of my machines. Changes look great. Thanks very much for your efforts!

drrossum commented on 2017-11-16 07:28

@andybz I have adopted your suggestions and renamed the python2-dulwich binaries to avoid the conflict

andybz commented on 2017-11-15 22:21

Hi effeeffe,

When building this package in a clean chroot (using clean-chroor-manager from AUR), I get an error that python2 isn't available. You need to list this as a build dependency because you're using it in the build() stage of your PKGBUILD.

It's also helpful to be able to install the python2/3 versions together sometimes when other python packages depend on it. Other packages will require the Python libraries (which wouldn't conflict between py2/3) so you should consider renaming the bins from the python2 version so they don't conflict (which seems to be the standard). See the python2 build stage of for an example.

I'm building python-reno and am running into issues because of this.


polyzen commented on 2017-10-31 03:34

Please use the ``dulwich-$pkgver`` releases:

> 2017-04-11 19:18:31 dmc jelmer, could you explain what those other tags are?
> 2017-04-11 19:18:38 dmc upstream/0_git20170328 and such
> 2017-04-11 19:19:45 jelmer dmc: they're used by the debian packaging - the snapshots of the upstream branch that the debian versions are based off

MadMe commented on 2017-10-28 12:34

PGP Signature Problem
==> Verifying source file signatures with gpg...
dulwich-0.18.3.tar.gz ... FAILED
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build python2-dulwich.

when i try:

gpg --recv-keys 1DF7EADF3B648883
key 00806F2BD729A457:
1400 signatures not checked due to missing keys
gpg: key 00806F2BD729A457: "Jelmer Vernoo\xc4\xb3 <>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

any hint?

effeeffe commented on 2017-09-19 10:02

This is a split package, it contains two packages that conflicts with each other, and this NOT is by mistake (see previous comments). No need to change the PKGBUILD as suggested by some comments: after building (makepkg) simply install only the package you need (pacman -U), which can be either python-dulwich or python2-dulwich. makepkg -i will try to install both, failing because of the conflict.

At least, this is my understanding. If this is correct, maybe it is worth a pinned comment.