Package Details: apt 1.6.1-1

Git Clone URL: (read-only)
Package Base: apt
Description: Command-line package manager used on Debian-based systems
Upstream URL:
Keywords: apt debian lib management package
Licenses: GPL2
Conflicts: apt-git
Provides: apt-utils, libapt-inst, libapt-pkg, libapt-pkg-dev
Replaces: apt-git
Submitter: JonnyJD
Maintainer: ProfessorKaos64
Last Packager: ProfessorKaos64
Votes: 36
Popularity: 0.801060
First Submitted: 2013-01-27 01:20
Last Updated: 2018-05-18 02:44

Pinned Comments

ProfessorKaos64 commented on 2016-12-13 18:46

Adopted. PKGBUILD now uses cmake. Please report any issues here.

Latest Comments

ProfessorKaos64 commented on 2018-05-18 02:46

Definitely something up, the repository no longer has tags / code. Checking, you can always click on the developer information hyperlink. From there, click on the Git link. This now points to Updated package.

sergey.orloff commented on 2018-05-14 21:09

:: Работа послеоперационных перехватов... (1/1) Arming ConditionNeedsUpdate... ==> Получение исходных файлов... -> Клонирование репозитория 'apt' (git)... Клонирование в голый репозиторий «/build/apt/apt»… warning: Похоже, что вы клонировали пустой репозиторий. ==> Проверка файлов source с использованием sha256sums... apt ... Пропущено ==> Распаковка исходных файлов... -> Создание рабочей копии репозитория 'apt' (git)... Клонирование в «apt»… warning: Похоже, что вы клонировали пустой репозиторий. готово. fatal: «1.5.1» не является коммитом, поэтому невозможно создать из него ветку «makepkg» ==> ОШИБКА: Ошибка при создании рабочей копии репозитория 'apt' (git) Прерывание...

ArchRob commented on 2018-05-08 16:38

Trying to install this via aurman, and I keep getting:

==> Extracting sources...
  -> Creating working copy of apt git repo...
fatal: '1.5.1' is not a commit and a branch 'makepkg' cannot be created from it
==> ERROR: Failure while creating working copy of apt git repo
2018-05-08 11:17:18,981 - wrappers - makepkg - ERROR - makepkg query makepkg -cf --noconfirm failed

I poked around in the PKGBUILD, and checked on the source:


That URL points to an empty repo. There's nothing at all in, which breaks this build AFAICT. Some quick googling around about changes to the project turned up nothing (and no alternative repos), so I think this package is broken / out of date.

simona commented on 2018-02-25 16:37

-- Building libapt-pkg 5.0 (release 2) -- Found Doxygen: /bin/doxygen (found version "1.8.14") found components: doxygen dot -- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY) -- Found GTest at /usr/src/gtest, headers at GTEST_INCLUDE_DIRS-NOTFOUND CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: /home/simona/.cache/pacaur/apt/src/apt/test/libapt/GTEST_INCLUDE_DIRS used as include directory in directory /home/simona/.cache/pacaur/apt/src/apt/test/libapt

-- Configuring incomplete, errors occurred!

dylan commented on 2017-04-07 00:44

Thank you!

ProfessorKaos64 commented on 2017-04-06 12:01

@dylan, I will do this today. Thank you. Generally, if I forget (I have so many projects, busy work life etc...), just flag the package out of date if that is all is wrong. If there isn't I probably should add a -git version to always track latest.

dylan commented on 2017-04-05 22:42

Any idea on when this package will be updated to 1.4?

ProfessorKaos64 commented on 2016-12-13 18:46

Adopted. PKGBUILD now uses cmake. Please report any issues here.

markzz commented on 2016-08-27 15:43

Okay, since the 1.3 prereleases are obviously not working well, I moved it back to 1.2.14 from Debian's GitHub mirror instead of Debian's regular place.

markzz commented on 2016-08-27 15:09

m3thodic: I get to the apt-man section and it fails.

m3thodic commented on 2016-08-26 08:04

This PKGBUILD succeeds in building apt with their new cmake build setup

markzz commented on 2016-08-19 13:56

I did update the package to 1.3~rc2 and didn't test it then noticed that cmake is now used, so I'm in the process of changing this so that it will work. Sorry for this...

chungy commented on 2016-07-26 12:26

pacman will consider 1.3~pre2 to be a newer version than 1.3, this would make updating the package difficult in the future. See the "vercmp" utility for testing version comparisons.

As a workaround, pacman understands 1.3pre2 as an older version than 1.3, and you might want to change to that.

Nickellick commented on 2016-07-22 11:17

Hi guys!
Source of package (1.2.14) is outdated, it's not avaliable now.
So, yaourt can't make package (error 404)
When i tried to change source link in PKGBUILD, makepkg says that checksums do not match.
Sorry for my English!
And, I'm newbie here, so maybe I do something wrong. :(

markzz commented on 2016-07-11 21:26

monochromec: That's a good thing to talk to upstream about. This package builds fine and runs as expected (I can still build things against the library). The "missing" localization files is a minor thing and all goes well in the end. Since v1.3 is still in the prerelease stage, I'm not going to upgrade this to that version and I have therefore unflagged the package.

This package builds on a clean Arch system and is in no need of changing.

monochromec commented on 2016-07-11 13:51

In case you come across coopstah13 observation in version 2.1.14 of the package wrt to the missing language subdirectories in doc, simply add the following
line to the PKGBUILD:

sed -i -e 's|for dir in en $(dir $(DOCDIRLIST))|for dir in en|' doc/makefile

before the configure invocation in build(). This will remove the additional languages from the makefile creation process and only build the English one.

rpodgorny commented on 2016-05-16 09:13

please update or orphan. thank you...

markzz commented on 2016-03-15 14:10

ProfessorKaos64: Just mark it out-of-date and I'll take care of it.

ProfessorKaos64 commented on 2016-03-15 12:25

Out of date, as apt 1.2.6 is out, 1.2.5 is no longer in the pool, hard stops build.

markzz commented on 2015-12-29 23:33

Just to be clear, this package should not be used to replace pacman in any way.

markzz commented on 2015-10-08 01:29

Adopted and fixed. Be sure to flag this package if anything goes outdated and I don't notice.

yurikoles commented on 2015-10-07 21:51

You are welcome

max-k commented on 2015-10-07 20:01

I'm OK to adopt it if needed.

libraries versions has been updated :

JonnyJD commented on 2015-05-07 09:34

Nobody wants to adopt the package?

The package works well currently so updating the PKGBUILD shouldn't be much more work than flagging the package as outdated.

JonnyJD commented on 2015-04-14 17:46

updated to

This package updates frequently and updates break our package because the old version is not available at the debian servers anymore.
I didn't use the package anymore for quite some time now.

I disowned the package in the hope that you can adopt it and keep it updated.

The complete package history can be found here:

JonnyJD commented on 2015-02-11 12:45

I've updated the PKGBUILD with the workaround by mbunkus, using /bin/dash instead of /bin/sh (symlinked to bash).
That workaround somewhat makes sense, since dash is also what Debian is using as a /bin/sh symlink.

Please do keep me updated on this bash issue though. Bash (invoked as sh) and automake generated files should work together. So this is probably a bug in one of the tools and is either fixed soon or should be reported.
I can't hunt that down myself ATM though.

And also keep me updated why an "outside build" makes any difference. Even when bash 4-3.33 is a problem, it would be used by an inside and outside build as the /bin/sh -> bash link is system wide.
Unless of course you run "dash configure" or something similar.

mbunkus commented on 2015-02-11 12:15

For me I could fix it by using dash for configure instead of bash. This addition in PKGBUILD right before ./configure --prefix… fixed it:

sed -i -e 's|#! /bin/sh|#! /bin/dash|' configure

JonnyJD commented on 2015-02-11 12:03

I am still at bash 4.3.30(1) and I can't do an update right now (important stuff going on on the system).

Could you be more explicit with "I can build the package outside of the PKGBUILD"?
Just running
$ ./configure && make
fails with
configure: error: cannot run /bin/sh buildlib/config.sub
(having automake 1.14.1)

When I do the automake step before:
$ automake --add-missing --no-force -W none
$ ./configure --prefix=/usr && make

I do get this:

warning: failed to load external entity "/usr/share/xml/docbook/stylesheet/docbook-xsl/xhtml-1_1/chunk.xsl"
compilation error: file ./docbook-html-style.xsl line 5 element import
xsl:import : unable to load /usr/share/xml/docbook/stylesheet/docbook-xsl/xhtml-1_1/chunk.xsl
../buildlib/docbook.mak:35: die Regel für Ziel „/var/abs/local/_src/_debian/apt/apt-“ scheiterte

That is the reason I do that sed parts to just fix the docs target.
I do have these installed:
docbook-xml 4.5-6
docbook-xsl 1.78.1-1
(again, I can't run a full upgrade just now)

So please do be more specific with "I've just build it".
There is no big difference of build() to an outside build in general. I don't see why an outside build works better for you than just changing the build() part of the PKGBUILD.

eomarjee commented on 2015-02-11 11:41

I'm on zsh too. But I manage to fix the problem using a workaround. It happens that I can build the package outside the PKGBUILD. So I've just build it, comment out the build function in PKGBUILD and run makepkg it to package it. Not the best way to do it, but it works. Hope this helps those who got the same issue.

mbunkus commented on 2015-02-11 09:29

I have the same problem eomarjee has. My /bin/sh is a symlink to bash, bash is v4.3.33(1)-release.

My user's shell is zsh, but it happens even if I change it to bash.

JonnyJD commented on 2015-02-04 23:18

I can't reproduce your problem. Maybe you have a "weird" shell variant?

I have
$ ls -lh `/bin/sh`
lrwxrwxrwx 1 root root 4 6. Okt 08:06 /bin/sh -> bash
$ bash --version
GNU bash, Version 4.3.30(1)-release (x86_64-unknown-linux-gnu)

Or maybe it is test?
what does that give:
$ test -n "" && echo not empty
(should be no output)

Can anybody else reproduce that behavior?

eomarjee commented on 2015-02-03 13:47

configure: WARNING: unrecognized options:
./configure: line 9574: syntax error near unexpected token `fi'
./configure: line 9574: `fi'
==> ERROR: A failure occurred in build().

eomarjee commented on 2015-02-03 13:41

./configure: line 9574: syntax error near unexpected token `fi'
./configure: line 9574: `fi'
==> ERROR: A failure occurred in build().

conormanning commented on 2014-06-27 13:37

Package on the server is out of date again. 1.0.5 works with SHA256sum 'eb88a82e2a044c1612c6d6aadf7cc0b5587298df3352e9755f5420be8abd62d7'.

There is also a 1.1 but I haven't tried it.

JonnyJD commented on 2014-05-30 00:58

Updated to 1.0.3.
This depends on "gtest" now for the build, even if it didn't with 1.0.
Also note that gtest is not only needed for the tests, but also for the non-test build.

littledude commented on 2014-05-29 21:24

Could you update to 1.0.3 please ? The 1.0 is not available for download anymore :
-> Downloading apt_1.0.tar.xz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading apt_1.0.tar.xz
==> ERROR: Makepkg was unable to build .

After tried to edit the pkgbuild (changinthe the version and the md5sum), but I cannot build it after that :
/tmp/corentih/yaourt-tmp-corentih/aur-apt/src/upstream.git/test/libapt/ fatal error: gtest/gtest.h: No such file or directory
#include <gtest/gtest.h>
compilation terminated.

JonnyJD commented on 2014-04-06 14:25

Updated to apt 1.0.

Please note that we are still not shipping the "apt" binary since that would conflict with
where also an "apt" (annotation processing tool) binary is shipped.
(The java "apt" is deprecated though)

Debian/Ubuntu does ship the "apt" binary.
Please report when you run into any problems with this.

tlunter commented on 2014-03-03 21:22

Wasn't sure about the provides but saw the other libraries so just figured I'd add them. Thanks for updating it.

JonnyJD commented on 2014-03-03 20:00

updated, also including libapt-private library and italian manpage.

Looks like I already have lots of provide. Not sure why I thought it is necessary.
I didn't add libapt-private to the provides because well: it is private.

Thanks for the notice.

JonnyJD commented on 2014-03-03 16:19

@tlunter: you can also submit a patch to

but, I'll have a look at it later this day probably.

What are the provides needed for and why can't the package needing these just depend on "apt"?
I understand that this is a bit more detailed in Debian, but debian is based on apt packaging and Arch is not.

At least "libapt-private" is something we probably shouldn't "provide".

tlunter commented on 2014-03-03 16:09

New package version


New provides

provides=('libapt-inst' 'libapt-pkg' 'libapt-pkg-dev' 'libapt-private' "apt-utils")

New md5sum


New lines under libapt-pkg symlinking in package()

# libapt-private
install bin/ $libdir/
ln -s -r $libdir/ $libdir/
ln -s -r $libdir/ $libdir/

coopstah13 commented on 2014-02-13 16:50

I'm guessing somehow my directory wasn't clean when I was trying to get it to work. It was fine now.

JonnyJD commented on 2014-02-13 12:27

I updated the package. This will be outdated again soon, since is already "in the pipeline".

I can't reproduce your error. Maybe you can paste your whole build log somewhere and link it here (please don't include the full log here).
Possibly there is some hidden dependency.

I always clean the build directory with "makepkg -c".
When you don't do that, you will run into problems since the current source is "upstream.git" rather than "$pkgname-$pkgver" (not my fault really, see 2 comments below).

Can you reproduce it every time? Maybe the package isn't fully multi-threaded make enabled (though I do use make -j4).
Another possibility is some general permission/disk space on your machine.

coopstah13 commented on 2014-02-12 20:41

Package is no longer available.

I am unable to get the package to build though...

Installing man page apt.8 to /tmp/yaourt-tmp-ccooper/aur-apt/src/upstream.git/docs
Note: Writing apt-sortpkgs.1
Note: Writing apt-key.8
Note: Writing apt-mark.8
Note: Writing apt-cache.8
Note: Writing apt-get.8
make[3]: *** ja/: No such file or directory. Stop.
make[3]: *** pt/: No such file or directory. Stop.
make[3]: *** es/: No such file or directory. Stop.
make[3]: *** pl/: No such file or directory. Stop.
make[3]: *** fr/: No such file or directory. Stop.
make[3]: *** it/: No such file or directory. Stop.
make[3]: *** pt_BR/: No such file or directory. Stop.
make[3]: *** de/: No such file or directory. Stop.
makefile:43: recipe for target 'manpages/subdirs' failed
make[2]: *** [manpages/subdirs] Error 2
Makefile:14: recipe for target 'startup' failed
make[1]: *** [startup] Error 2
makefile:33: recipe for target 'dirs' failed
make: *** [dirs] Error 2
Installing man page apt.8 to /tmp/yaourt-tmp-ccooper/aur-apt/src/upstream.git/docs
make[3]: *** ja/: No such file or directory. Stop.
make[3]: *** pt/: No such file or directory. Stop.
make[3]: *** es/: No such file or directory. Stop.
make[3]: *** pl/: No such file or directory. Stop.
make[3]: *** fr/: No such file or directory. Stop.
make[3]: *** it/: No such file or directory. Stop.
make[3]: *** pt_BR/: No such file or directory. Stop.
make[3]: *** de/: No such file or directory. Stop.
makefile:43: recipe for target 'manpages/subdirs' failed
make[2]: *** [manpages/subdirs] Error 2
Makefile:14: recipe for target 'startup' failed
make[1]: *** [startup] Error 2
makefile:18: recipe for target 'all' failed
make: *** [all] Error 2 seems to be working ok

JonnyJD commented on 2014-01-14 09:33

Updated. Again the "old" tarball didn't stay longer on the server than 1-2 month.
Additionally I would call the tarball "broken", extracting to an "upstream.git/" directory in contrast to the usual "pkgname-pkgver/".

Possibly it might be easier to maintain an "apt-git" package.
So if anybody is interested, go ahead and link it here. Can't be much worse than this "stable".

If anybody has improvements for this package, there is a repository:

piquer commented on 2013-11-14 08:58

apt_0.9.11.4 is not available on the debian ftp anymore. Using with md5sum d0cf3377f6a99ca7a9ce9df0977cf3a5 works.

JonnyJD commented on 2013-09-04 15:09

Thanks. Actually the current version is, but this needs an updated (+tested) PKGBUILD.

I update to for now and I hope I can do the other update later today or at least soon.

qgeissmann commented on 2013-09-04 07:00

The version is out of date.
The new version is and the corresponding md5sum is 4b992b556ad179d51ab524befc09d182

JonnyJD commented on 2013-05-02 23:33

This is probably because you have multiple versions of automake installed and I used "automake-*" to copy config.{guess,sub}.

I use automake now, which copies these files, but fails otherwise (which I ignore).

OrdinaryMagician commented on 2013-05-01 20:16

cp: will not overwrite just-created ‘buildlib/config.guess’ with ‘/usr/share/automake-1.13/config.guess’

First time I see this sort of error message in my entire life.

JonnyJD commented on 2013-02-18 16:14


Patched so it doesn't depend on the docbook-xsl version anymore and also added 2 makedepends that are not pulled by dpkg.

dlin commented on 2013-02-18 15:11

Can not build, log here

JonnyJD commented on 2013-01-29 16:45

Fixed. Thx for reporting. I (obviously) can't chrootbuild ATM. (no systemd system)

By the way, I personally only use this as dependency for python2-apt and that for bzr builddeb. No actual package management in arch with apt ;-)

FYI: This package is now in

Anonymous comment on 2013-01-29 11:18

It's not buildable unless you have installed dpkg first because dpkg-architecture is missing otherwise.

.configure output:
checking bzlib.h presence... yes
checking for bzlib.h... yes
checking debian architecture... ./configure: line 4652: dpkg-architecture: command not found
configure: error: failed: use --host= or output from dpkg-architecture

JonnyJD commented on 2013-01-27 05:22

Why would "install -d" be better than "mkdir -p"? (I guess "makepkg -p" is a typo on your end)

I could use "install -D" at two places, but at the other places I want the last part to be a directory where I can drop my file in (which doesn't work if that directory isn't previously created).
I could actually use "cp" at most of the places, but with install a make sure that the mode really is correct.

gtmanfred commented on 2013-01-27 03:29

it you are really going to do this... at least use install -D and -d instead of all those makepkg -p commands