Package Details: dpkg 1.18.10-3

Git Clone URL: https://aur.archlinux.org/dpkg.git (read-only)
Package Base: dpkg
Description: The Debian Package Manager. Don't use it instead of Arch's 'pacman'.
Upstream URL: https://tracker.debian.org/pkg/dpkg
Licenses: GPL
Submitter: Xavion
Maintainer: Alad
Last Packager: Alad
Votes: 401
Popularity: 5.740329
First Submitted: 2009-03-11 21:51
Last Updated: 2016-09-15 23:41

Latest Comments

Alad commented on 2016-09-15 23:41

Well, at least it will prevent the package from breaking on version bumps. Updated, thanks.

ProfessorKaos64 commented on 2016-09-15 18:42

It may be good to use https://anonscm.debian.org/git/dpkg/dpkg.git/ as a source so this can be tracked with the git protocol, and users can pass --devel to their AUR helpers to grab the latest (if they wish). You can still tag whatever release target of course (#tag=v${pkgver}").

Alad commented on 2016-09-04 18:55

Not sure how devscripts and debian-archive-keyring issues are relevant to dpkg, as those are separate packages.

ProfessorKaos64 commented on 2016-08-17 12:34

Package works, but utilizing dget is missing some key files. This makes you have to untar files yourself. This is ok, but for automated scripts, annoying, especially for backporting packages with multiple bz2 archives. dget also applies patches. Keyrings from /debian-archive-keyring are installed to /usr/share/keyrings, which is not recognized by dscverify.

Error using dget:

dpkg-vendor: error: vendor default doesn't exist in /etc/dpkg/origins/
dscverify: can't find any system keyrings On my Debian VPS, this is the contents of the origins/ folder:

debian: http://sprunge.us/OLUO
default: http://sprunge.us/XBUK

Alad commented on 2016-07-22 12:24

No issues here.

llama47 commented on 2016-07-18 17:42

upgrade hangs on downloading dpkg_1.18.9.tar.xz

bertptrs commented on 2016-07-17 10:02

Updated to upstream version 1.18.9. Let me know if there are any problems.

neta540 commented on 2016-06-26 11:56

requires patch

technic93 commented on 2016-06-19 23:21

Ok, it seems that replacing pkgver=1.17.27 in the header fixes the issue.

technic93 commented on 2016-06-19 23:19

I encountered that issue today. Please update PKGBUILD. Does anyone have updated PKGBUILD already?

All comments