You are not logged in.
Hello,
Is it right that the pkgver is not always the commit number from upstream.,
And if so, how can I check which revision I have on my machine.
Roelof
Last edited by roelof (2013-08-14 15:44:56)
Offline
Is it right that the pkgver is not always the commit number from upstream.
It should always be (or at least the minor version number should be). But in practice some -git PKGBUILDs have not yet been updated to this standard.
Previously the pkgver would be the build date. So if your installed version looks like a date, then you can check if there have been commits since that date - if there have, you don't have the most recent code. If it doesn't look like a date, then the minor version number should be the commit number.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Online
Depends on the package and what they're doing in the pkgver() function.
Offline
That depends on the PKGBUILD e.g. https://aur.archlinux.org/packages/lc/lc-git/PKGBUILD updates the pkgver
[lc-git]$ makepkg -si
==> Making package: lc-git 79da758-1 (Tue Aug 13 23:00:44 CEST 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating lc git repo...
Fetching origin
remote: Counting objects: 11, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 10 (delta 3), reused 9 (delta 2)
Unpacking objects: 100% (10/10), done.
From git://github.com/xyproto/lc
79da758..6942649 master -> master
==> Validating source files with md5sums...
lc ... Skipped
==> Extracting sources...
-> Creating working copy of lc git repo...
Cloning into 'lc'...
done.
Checking connectivity... done
==> Starting pkgver()...
==> Updated version: lc-git 6942649-1
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
-> Purging unwanted files...
-> Compressing man and info pages...
-> Stripping unneeded symbols from binaries and libraries...
==> Creating package "lc-git"...
-> Generating .PKGINFO file...
-> Adding install file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: lc-git 6942649-1 (Tue Aug 13 23:00:48 CEST 2013)
==> Installing package lc-git with pacman -U...
loading packages...
resolving dependencies...
looking for inter-conflicts...
Packages (1):
Name Old Version New Version Net Change
lc-git 79da758-1 6942649-1 0.00 MiB
Total Installed Size: 0.03 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [########################################################] 100%
(1/1) checking package integrity [########################################################] 100%
(1/1) loading package files [########################################################] 100%
(1/1) checking for file conflicts [########################################################] 100%
(1/1) checking available disk space [########################################################] 100%
(1/1) upgrading lc-git
Offline
Im talking about the Cinnamon-git package from AUR.
Roelof
Offline
The "major version" number there is the commit number.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Online
Oke,
It seems that 39fc3a7 is a existing commit. Then the PKGBUILD is some 20 days old with a lot of new commits.
I can try to update it all but then I have to know how I must change the pkgver to the new commit which is 72642a.
Maybe then Cinnamon will start with exec gnome-session-cinnamon but I made a another topic about that.
Roelof
Offline
No, you don't change the pkgver.
Just run makepkg. I think there may be a more basic misunderstanding about using PKGBUILDs here. When you run makepkg on a -git PKGBUILD, you will get the most recent code (up to the second).
Last edited by Trilby (2013-08-14 15:19:19)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Online
I checked and you are all right. I have now the newest version.
Thanks for the explanation.
Roelof
Offline
Please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309
Offline