Package Details: apt 2.0.1-1

Git Clone URL: https://aur.archlinux.org/apt.git (read-only, click to copy)
Package Base: apt
Description: Command-line package manager used on Debian-based systems
Upstream URL: https://packages.debian.org
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: TheGoliath
Last Packager: TheGoliath
Votes: 35
Popularity: 0.000019
First Submitted: 2013-01-27 01:20
Last Updated: 2020-04-01 15:55

Pinned Comments

ProfessorKaos64 commented on 2016-12-13 18:46

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

Latest Comments

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

JonnyJD commented on 2014-03-03 16:19

@tlunter: you can also submit a patch to
https://github.com/JonnyJD/PKGBUILDs/blob/master/_debian/apt/PKGBUILD

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

pkgver=0.9.15.5

New provides

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

New md5sum

md5sums=('9c1cd103474c312604e8c430399509f1')

New lines under libapt-pkg symlinking in package()

# libapt-private
install bin/libapt-private.so.0.0.0 $libdir/
ln -s -r $libdir/libapt-private.so.0.0.0 $libdir/libapt-private.so.0.0
ln -s -r $libdir/libapt-private.so.0.0.0 $libdir/libapt-private.so

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 0.9.15.2 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 0.9.14.2 is no longer available.

I am unable to get the 0.9.15.1 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

0.9.7.9+deb7u1 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:
https://github.com/JonnyJD/PKGBUILDs/blob/master/_debian/apt/PKGBUILD

piquer commented on 2013-11-14 08:58

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

JonnyJD commented on 2013-09-04 15:09

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

I update to 0.9.7.9 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 0.9.7.8 is out of date.
The new version is 0.9.7.9 and the corresponding md5sum is 4b992b556ad179d51ab524befc09d182

JonnyJD commented on 2013-05-02 23:33

@OrdinaryMagician:
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).