Package Details: goobook-git 3.5.1-3

Git Clone URL: https://aur.archlinux.org/goobook-git.git (read-only, click to copy)
Package Base: goobook-git
Description: Search your google contacts from the command-line or mutt.
Upstream URL: https://gitlab.com/goobook/goobook
Licenses: GPL
Conflicts: goobook
Provides: goobook
Submitter: firecat53
Maintainer: None
Last Packager: firecat53
Votes: 58
Popularity: 0.000000
First Submitted: 2010-03-29 18:20 (UTC)
Last Updated: 2022-09-25 17:45 (UTC)

Latest Comments

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

simona commented on 2021-07-18 10:17 (UTC)

why now use python-xdg?

merlock commented on 2021-03-15 03:19 (UTC)

@firecat53 - A-OK. Built fine.

Thanks!

firecat53 commented on 2021-03-15 02:20 (UTC)

Ok, fixed now, sorry. Didn't notice the changed man page build at first.

merlock commented on 2021-03-14 20:12 (UTC)

@firecat53 - still same error...normal build or in a clean chroot.

firecat53 commented on 2021-03-14 16:49 (UTC)

@merlock - can you please try again? It seems to be working now when I build from scratch. Thanks!

merlock commented on 2021-02-06 15:41 (UTC)

Latest update (2021-02-06 10:05) fails to build.

http://ix.io/2Owg

firecat53 commented on 2020-12-30 20:17 (UTC) (edited on 2020-12-30 20:19 (UTC) by firecat53)

dno - Again, this is normal for VCS packages. The version is updated only when the package is updated by the maintainer. It does not get updated in the AUR each time a commit is pushed to the upstream repository. When you build the package, the version is updated for that package on your system. Edit: that discussion is 5+ years old.

dno commented on 2020-12-30 17:24 (UTC)

firecat53 - I get that this is a VCS package the issue is moving the version up or not. I think it's at best confusing and at worst breaks the experience for people using AUR helpers to scan for upgradable packages.

There is a lively argument for/against the AUR VCS version update issues here: https://wiki.archlinux.org/index.php/Talk:VCS_package_guidelines#Guidelines_on_updating_version_numbers

For what it's worth, I would like to see the versions of these types of packages moved up periodically.

firecat53 commented on 2020-12-30 16:51 (UTC)

dno - This is the way VCS packages on the AUR work. Any -git package has to check by different means if there is a new commit, or just be rebuilt when you choose.

https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function

dno commented on 2020-12-30 16:44 (UTC)

This package's version is out of sync with the latest tagged version on GitLab. So when you build this Arch package you do indeed get 3.5.1 but the AUR metadata still says 3.3.3.g79ae9a3. Because of this it never shows up as needing update (for example in auracle sync output)