Package Details: xournalpp-git 1.1.0.r104.gc6ae5c7fc-1

Git Clone URL: https://aur.archlinux.org/xournalpp-git.git (read-only, click to copy)
Package Base: xournalpp-git
Description: Xournal++ is a handwriting Notetaking software with PDF annotation support. Supports Pen input like Wacom Tablets.
Upstream URL: https://github.com/xournalpp/xournalpp
Keywords: annotation notebook pdf tablet
Licenses: GPL2
Conflicts: xournalpp
Submitter: ridikulusrat
Maintainer: youduda
Last Packager: youduda
Votes: 22
Popularity: 0.039759
First Submitted: 2015-10-18 01:29
Last Updated: 2021-11-17 00:44

Latest Comments

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

MithicSpirit commented on 2021-07-20 14:20

Because upstream has changed their versioning scheme, pkgver() now returns nightly.r2.gb24535541, which is interpreted as a downgrade from 1.0.15.r715.g8f83a043, which is what the PKGBUILD reports as the version. This causes issues with AUR helpers which can check for updates as they think that the version that is built is always older than the version available from the AUR. It would be nice if the pkgver was updated to the current value, or, better yet, was updated to a generic value like latest, or maybe even set to 0, as suggested in the forums.

youduda commented on 2021-03-21 15:36

My local git clone is quite extensive, which is why pkgver generates this version number. Anyway, I removed the extra zero.

langfingaz commented on 2021-03-21 15:01

I have a similar problem when using aurutils: It thinks that there is an update, probably because of the additional zero at then end:

$ aur sync -c -u

  -> xournalpp-git: 1.0.15.r715.g8f83a043-1 -> 1.0.15.r715.g8f83a0430-1
[...]
==> WARNING: build: skipping existing package (use -f to overwrite)
/home/custompkgs/xournalpp-git-1.0.15.r715.g8f83a043-1-x86_64.pkg.tar.zst

marmistrz commented on 2021-03-19 07:18

The hash doesn't match, after installing yay still reports an update available:

:: 1 Packages to upgrade.
1  aur/xournalpp-git  1.0.15.r715.g8f83a043-1 -> 1.0.15.r715.g8f83a0430-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)

Looks like the extra 0 is the culprit.

youduda commented on 2021-03-18 16:40

Thanks for sharing, I added aarch64 to the supported architectures.

Valenoern commented on 2021-03-18 06:21

I successfully built this package on aarch64 (arm 64) and would like to add it to the architecture list. Is there any more direct way than leaving a comment here?

youduda commented on 2020-11-23 15:56

The package version number always matches the latest tag of the branch which is currently 1.0.15 in the default branch (master). That's just how the *-git packages should generate their version number see here for more details. The stable package is built using another branch with newer tags which are not present in the master branch. IMHO we should not create a workaround for this because what would be the benefit of a slightly higher version number while the -git suffix makes it clear that this is the latest version.

archisman commented on 2020-11-21 04:41

Update the version number to something like 1.1.0+dev. This AUR does install the latest version, but the version number shown in the package manager (1.0.15.r460.gcf4000cf-1) is lagging behind that of the stable package xournalpp

youduda commented on 2019-10-28 17:33

Thanks for the remark, issue is fixed.

FYI: Upstream build behavior has changed to not generate translation files when building default target.

guraltsev commented on 2019-10-25 19:34

The package fails to build with this message:

-- Installing: /home/guraltsev/.cache/pikaur/build/xournalpp-git/pkg/xournalpp-git/usr/share/metainfo/com.github.xournalpp.xournalpp.appdata.xml
CMake Error at po/cmake_install.cmake:41 (file):
  file INSTALL cannot find
  "/home/guraltsev/.cache/pikaur/build/xournalpp-git/src/xournalpp/build/po/cs.gmo".
Call Stack (most recent call first):
  cmake_install.cmake:102 (include)

Unfortunately I am at loss as to how to fix this. The various language localizations (po) seem to be there, however there is something wrong in the build process.