Arch Linux User Repository

@markzz wrote an email to the current maintainer

Here is a suggested PKGBUILD to get this built with the po4a issue: https://gist.github.com/markzz/2af364ac26179713608264abd257e442

As per [1], building packages from prebuilt binaries is not allowed without the package being a pkgname-bin package. What is the reason that you cannot build the source?

EDIT: I can confirm that just changing the pkgver to 2.1.1 from the previous commit does compile just fine. You should change back to building from source. In order to build, po4a must be downgraded or version 0.27 must be made available or disable documentation generation.

[1] https://wiki.archlinux.org/index.php/AUR_submission_guidelines#Rules_of_submission

Getting CMake error on linking

collect2: error: ld returned 1 exit status
make[2]: *** [test/libapt/CMakeFiles/libapt_test.dir/build.make:554: test/libapt/libapt_test] Error 1
make[2]: Leaving directory '/home/terabyte/.cache/pacaur/apt/src/apt'
make[1]: *** [CMakeFiles/Makefile2:1576: test/libapt/CMakeFiles/libapt_test.dir/all] Error 2
make[1]: Leaving directory '/home/terabyte/.cache/pacaur/apt/src/apt'
make: *** [Makefile:158: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
:: failed to build apt package(s)

The very first error i am getting is

/usr/bin/ld: /usr/local/lib/libgtest.a(gtest-all.cc.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE

Definitely something up, the repository no longer has tags / code. Checking https://packages.debian.org/sid/apt, you can always click on the developer information hyperlink. From there, click on the Git link. This now points to https://salsa.debian.org/apt-team/apt. Updated package.

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

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
    Aborting...
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:

source=("git+https://anonscm.debian.org/git/apt/apt.git#tag=${pkgver}")

That URL points to an empty repo. There's nothing at all in https://anonscm.debian.org/git/apt/apt.git, 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.

-- 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!

Thank you!

@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.