You are not logged in.

#1 2013-08-13 20:42:51

roelof
Member
Registered: 2009-08-07
Posts: 99

[solved] Git modyfing question,

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

#2 2013-08-13 21:03:52

Trilby
Forum Moderator
From: Massachusetts, USA
Registered: 2011-11-29
Posts: 14,191
Website

Re: [solved] Git modyfing question,

roelof wrote:

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.


InterrobangSlider
• How's my coding? See this page.
• How's my moderating? Feel free to email any concerns, complaints, or objections.

Offline

#3 2013-08-13 21:03:55

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 5,121

Re: [solved] Git modyfing question,

Depends on the package and what they're doing in the pkgver() function.

Offline

#4 2013-08-13 21:05:03

karol
Archivist
Registered: 2009-05-06
Posts: 25,432

Re: [solved] Git modyfing question,

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

#5 2013-08-14 06:11:38

roelof
Member
Registered: 2009-08-07
Posts: 99

Re: [solved] Git modyfing question,

Im talking about the Cinnamon-git package from AUR.

Roelof

Offline

#6 2013-08-14 11:05:32

Trilby
Forum Moderator
From: Massachusetts, USA
Registered: 2011-11-29
Posts: 14,191
Website

Re: [solved] Git modyfing question,

The "major version" number there is the commit number.


InterrobangSlider
• How's my coding? See this page.
• How's my moderating? Feel free to email any concerns, complaints, or objections.

Offline

#7 2013-08-14 14:00:55

roelof
Member
Registered: 2009-08-07
Posts: 99

Re: [solved] Git modyfing question,

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

#8 2013-08-14 14:03:00

Trilby
Forum Moderator
From: Massachusetts, USA
Registered: 2011-11-29
Posts: 14,191
Website

Re: [solved] Git modyfing question,

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)


InterrobangSlider
• How's my coding? See this page.
• How's my moderating? Feel free to email any concerns, complaints, or objections.

Offline

#9 2013-08-14 14:15:40

roelof
Member
Registered: 2009-08-07
Posts: 99

Re: [solved] Git modyfing question,

I checked and you are all right. I have now the newest version.
Thanks for the explanation.

Roelof

Offline

#10 2013-08-14 15:40:28

karol
Archivist
Registered: 2009-05-06
Posts: 25,432

Re: [solved] Git modyfing question,

Please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309

Offline

Board footer

Powered by FluxBB