Package Base Details: apt

Git Clone URL: (read-only, click to copy)
Keywords: apt debian lib management package
Submitter: JonnyJD
Maintainer: moe_narrow
Last Packager: TheGoliath
Votes: 37
Popularity: 0.72
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 »

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.