Package Base Details: apt

Git Clone URL: https://aur.archlinux.org/apt.git (read-only, click to copy)
Keywords: apt debian lib management package
Submitter: JonnyJD
Maintainer: moe_narrow (TheGoliath)
Last Packager: TheGoliath
Votes: 36
Popularity: 0.196489
First Submitted: 2013-01-27 01:20
Last Updated: 2020-07-21 14:00

Packages (2)

Latest Comments

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

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
Aborting...
==> 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/gtest_runner.cc:1:25: 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 https://www.archlinux.org/packages/extra/x86_64/jdk7-openjdk/
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
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.