Discussion:
[aur-general] Automatic package version
Shay Gover via aur-general
2018-10-26 16:26:43 UTC
Permalink
Hi,

I have a pakage in AUR that uses an automatic package versioning. I use a
pkgver() and pkgrel().
However I just noticed that the package version in AUR is old. I checked
the functions and everything is OK. Running makepkg gives the correct
version.

The package is:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=virtualbox-ck-modules

Ideas?

Thanks,

Shay Gover
Michael Kogan
2018-10-26 16:29:59 UTC
Permalink
First thing coming to mind: Did you possibly forget to update the .SRCINFO
file?

Am Fr., 26. Okt. 2018 um 18:27 Uhr schrieb Shay Gover via aur-general <
Post by Shay Gover via aur-general
Hi,
I have a pakage in AUR that uses an automatic package versioning. I use a
pkgver() and pkgrel().
However I just noticed that the package version in AUR is old. I checked
the functions and everything is OK. Running makepkg gives the correct
version.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=virtualbox-ck-modules
Ideas?
Thanks,
Shay Gover
Doug Newgard via aur-general
2018-10-26 16:30:56 UTC
Permalink
On Fri, 26 Oct 2018 19:26:43 +0300
Post by Shay Gover via aur-general
Hi,
I have a pakage in AUR that uses an automatic package versioning. I use a
pkgver() and pkgrel().
However I just noticed that the package version in AUR is old. I checked
the functions and everything is OK. Running makepkg gives the correct
version.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=virtualbox-ck-modules
Ideas?
Thanks,
Shay Gover
You didn't update .SRCINFO
Eli Schwartz via aur-general
2018-10-26 16:34:44 UTC
Permalink
Post by Shay Gover via aur-general
Hi,
I have a pakage in AUR that uses an automatic package versioning. I use a
pkgver() and pkgrel().
However I just noticed that the package version in AUR is old. I checked
the functions and everything is OK. Running makepkg gives the correct
version.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=virtualbox-ck-modules
Are you Tharbad on the AUR? If so, you're using multiple email addresses...

As for the package itself, fake news! The package is not *supposed* to
show an updated version in the AUR, that's the whole point of a pkgver()
function.

P.S. There's no such thing as a pkgrel() function.
--
Eli Schwartz
Bug Wrangler and Trusted User
Shay Gover via aur-general
2018-10-26 18:07:35 UTC
Permalink
Message: 1
Date: Fri, 26 Oct 2018 18:29:59 +0200
To: "Discussion about the Arch User Repository (AUR)"
Subject: Re: [aur-general] Automatic package version
<
Content-Type: text/plain; charset="UTF-8"
First thing coming to mind: Did you possibly forget to update the .SRCINFO
file?
Hoe do I update it from the PKGBUILD itself?
Message: 3
Date: Fri, 26 Oct 2018 12:34:44 -0400
Subject: Re: [aur-general] Automatic package version
Content-Type: text/plain; charset="utf-8"
Post by Shay Gover via aur-general
Hi,
I have a pakage in AUR that uses an automatic package versioning. I use a
pkgver() and pkgrel().
However I just noticed that the package version in AUR is old. I checked
the functions and everything is OK. Running makepkg gives the correct
version.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=virtualbox-ck-modules
Are you Tharbad on the AUR? If so, you're using multiple email addresses...
As for the package itself, fake news! The package is not *supposed* to
show an updated version in the AUR, that's the whole point of a pkgver()
function.
So how does the automatic versioning suppose to work?
P.S. There's no such thing as a pkgrel() function.
Good to know. Since I need it, What can I do?
--
Eli Schwartz
Bug Wrangler and Trusted User
Konstantin Gizdov
2018-10-26 18:09:36 UTC
Permalink
Post by Shay Gover via aur-general
Message: 1
Date: Fri, 26 Oct 2018 18:29:59 +0200
To: "Discussion about the Arch User Repository (AUR)"
Subject: Re: [aur-general] Automatic package version
<
Content-Type: text/plain; charset="UTF-8"
First thing coming to mind: Did you possibly forget to update the .SRCINFO
file?
Hoe do I update it from the PKGBUILD itself?
I normally have an alias like this:

$ which updpkgs
updpkgs: aliased to 'updpkgsums && makepkg --printsrcinfo > .SRCINFO'
Post by Shay Gover via aur-general
Message: 3
Date: Fri, 26 Oct 2018 12:34:44 -0400
Subject: Re: [aur-general] Automatic package version
Content-Type: text/plain; charset="utf-8"
Post by Shay Gover via aur-general
Hi,
I have a pakage in AUR that uses an automatic package versioning. I use a
pkgver() and pkgrel().
However I just noticed that the package version in AUR is old. I checked
the functions and everything is OK. Running makepkg gives the correct
version.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=virtualbox-ck-modules
Are you Tharbad on the AUR? If so, you're using multiple email addresses...
As for the package itself, fake news! The package is not *supposed* to
show an updated version in the AUR, that's the whole point of a pkgver()
function.
So how does the automatic versioning suppose to work?
P.S. There's no such thing as a pkgrel() function.
Good to know. Since I need it, What can I do?
--
Eli Schwartz
Bug Wrangler and Trusted User
Eli Schwartz via aur-general
2018-10-26 18:14:06 UTC
Permalink
Post by Shay Gover via aur-general
Post by Michael Kogan
First thing coming to mind: Did you possibly forget to update the .SRCINFO
file?
Hoe do I update it from the PKGBUILD itself?
The PKGBUILD format is by definition separate from the .SRCINFO, you
don't update it automatically by the PKGBUILD.

You update it separately. The general process is described here:
https://wiki.archlinux.org/index.php/Arch_User_Repository#Uploading_packages

The "aurpublish" package available in the community repositories can do
this for you.
Post by Shay Gover via aur-general
Post by Michael Kogan
The package is not *supposed* to
show an updated version in the AUR, that's the whole point of a pkgver()
function.
So how does the automatic versioning suppose to work?
It already does work. You download the PKGBUILD from the AUR, and use it
to build a package. A pkgver() function *allows* the package to be newer
than advertised in the AUR.

It's okay for a package to be newer than advertised. That's how all
*-git packages work, by design.
Post by Shay Gover via aur-general
Post by Michael Kogan
P.S. There's no such thing as a pkgrel() function.
Good to know. Since I need it, What can I do?
I assert that you do not need it.

The pkgver is supposed to be set by the version of the software itself.
The pkgrel is supposed to be the version of the PKGBUILD, and every time
the pkgver gets updated, the pkgrel resets back to "1".

See https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel

An "automatic" pkgrel violates the fundamental purpose of having a
pkgrel in the first place.
--
Eli Schwartz
Bug Wrangler and Trusted User
Shay Gover via aur-general
2018-10-26 18:33:12 UTC
Permalink
Date: Fri, 26 Oct 2018 19:09:36 +0100
Subject: Re: [aur-general] Automatic package version
Content-Type: text/plain; charset="utf-8"
Post by Shay Gover via aur-general
Message: 1
Date: Fri, 26 Oct 2018 18:29:59 +0200
To: "Discussion about the Arch User Repository (AUR)"
Subject: Re: [aur-general] Automatic package version
<
Content-Type: text/plain; charset="UTF-8"
First thing coming to mind: Did you possibly forget to update the
.SRCINFO
Post by Shay Gover via aur-general
file?
Hoe do I update it from the PKGBUILD itself?
$ which updpkgs
updpkgs: aliased to 'updpkgsums && makepkg --printsrcinfo > .SRCINFO'
That's from outside the PKGBUILD. I already did that when I uploaded the
package a month ago. But since then the package was updated. It's not
automatic versioning if I need to update SRCINFO every time.
Post by Shay Gover via aur-general
First thing coming to mind: Did you possibly forget to update the
.SRCINFO
Post by Shay Gover via aur-general
file?
Hoe do I update it from the PKGBUILD itself?
The PKGBUILD format is by definition separate from the .SRCINFO, you
don't update it automatically by the PKGBUILD.
https://wiki.archlinux.org/index.php/Arch_User_Repository#Uploading_packages
The "aurpublish" package available in the community repositories can do
this for you.
OK. But I'll still need to create a local script that will do that, right?
Post by Shay Gover via aur-general
The package is not *supposed* to
show an updated version in the AUR, that's the whole point of a pkgver()
function.
So how does the automatic versioning suppose to work?
It already does work. You download the PKGBUILD from the AUR, and use it
to build a package. A pkgver() function *allows* the package to be newer
than advertised in the AUR.
It's okay for a package to be newer than advertised. That's how all
*-git packages work, by design.
Post by Shay Gover via aur-general
P.S. There's no such thing as a pkgrel() function.
Good to know. Since I need it, What can I do?
I assert that you do not need it.
The pkgver is supposed to be set by the version of the software itself.
The pkgrel is supposed to be the version of the PKGBUILD, and every time
the pkgver gets updated, the pkgrel resets back to "1".
See https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel
An "automatic" pkgrel violates the fundamental purpose of having a
pkgrel in the first place.
You're correct. My fault. :/
Doug Newgard via aur-general
2018-10-26 18:36:49 UTC
Permalink
On Fri, 26 Oct 2018 21:33:12 +0300
Date: Fri, 26 Oct 2018 19:09:36 +0100
Subject: Re: [aur-general] Automatic package version
Content-Type: text/plain; charset="utf-8"
Post by Shay Gover via aur-general
Message: 1
Date: Fri, 26 Oct 2018 18:29:59 +0200
To: "Discussion about the Arch User Repository (AUR)"
Subject: Re: [aur-general] Automatic package version
<
Content-Type: text/plain; charset="UTF-8"
First thing coming to mind: Did you possibly forget to update the
.SRCINFO
Post by Shay Gover via aur-general
file?
Hoe do I update it from the PKGBUILD itself?
$ which updpkgs
updpkgs: aliased to 'updpkgsums && makepkg --printsrcinfo > .SRCINFO'
That's from outside the PKGBUILD. I already did that when I uploaded the
package a month ago. But since then the package was updated. It's not
automatic versioning if I need to update SRCINFO every time.
If that's what you're looking for, this is simple.

There is no automatic versioning at all.
Eli Schwartz via aur-general
2018-10-26 18:41:37 UTC
Permalink
That's from outside the PKGBUILD. I already did that when I uploaded the
package a month ago. But since then the package was updated. It's not
automatic versioning if I need to update SRCINFO every time.
You what now? Why do you need to update the .SRCINFO at all? The
PKGBUILD is not updated in the AUR, therefore the .SRCINFO is not
updated in the AUR either.

.SRCINFO is not used by makepkg at all, in any way, shape or form, so
there's simply nothing to discuss about that.

This is simply how git packages work. Stop trying to automatically
version it, because there's no such thing as automatic versioning.

There is only automatic updating.
Post by Michael Kogan
Post by Shay Gover via aur-general
Post by Michael Kogan
First thing coming to mind: Did you possibly forget to update the
.SRCINFO
Post by Shay Gover via aur-general
Post by Michael Kogan
file?
Hoe do I update it from the PKGBUILD itself?
The PKGBUILD format is by definition separate from the .SRCINFO, you
don't update it automatically by the PKGBUILD.
https://wiki.archlinux.org/index.php/Arch_User_Repository#Uploading_packages
The "aurpublish" package available in the community repositories can do
this for you.
OK. But I'll still need to create a local script that will do that, right?
aurpublish *is* a local script to do that.

...

I'm still rather unclear on what your goal is.
--
Eli Schwartz
Bug Wrangler and Trusted User
Michael Kogan
2018-10-26 18:48:29 UTC
Permalink
I would also mention that frequent version bumping is quite disturbing.
Imho, git packages should not be updated by the package maintainer (unless
there are some very significant changes involved) - this way every user can
decide when to update while fresh installs will get the most recent git
revision anyway.
Eli Schwartz via aur-general
2018-10-26 18:59:36 UTC
Permalink
Post by Michael Kogan
I would also mention that frequent version bumping is quite disturbing.
Imho, git packages should not be updated by the package maintainer (unless
there are some very significant changes involved) - this way every user can
decide when to update while fresh installs will get the most recent git
revision anyway.
(I often version bump my git packages for the stable release.)
--
Eli Schwartz
Bug Wrangler and Trusted User
Continue reading on narkive:
Loading...