[aur-general] How do I show a AUR Rebuild as a newer build?
Good morning All, I understand that there are 3 version control tags in the PKGBUILD file. pkgver - The Actual Package version pkgrel - The Arch modification/release count - for changes to the patches, install file's. epoch - Special version control number. If I need to rebuild a package due to dependancy rebuilds/changes how do I mark the new package as newer? Do I increase the epoch? Or is there another way? Thanks Macca
On Sat, 20 Oct 2018 08:59:06 +0800, hagar wrote:
If I need to rebuild a package due to dependancy rebuilds/changes how do I mark the new package as newer?
Do I increase the epoch?
No. From 'man PKGBUILD': "This is useful when the version numbering scheme of a package changes (or is alphanumeric), breaking normal version comparison logic."
Or is there another way?
That is what the pkgrel is for. However, AUR provides PKGBUILDs, not packages, so a maintainer doesn't bump the pkgrel each time a PKGBUILD gets edited, but a maintainer might care about the need to build against newer releases of dependencies and increase the pkgrel or the maintainer might ignore it. What ever changed, I bump the pkgrel for my local builds for each package, but that way the pkgrels of my local packages could get out of sync with the pkgrels of some AUR PKGBUILDs. If you dislike this, simply build a new package with the same pkgver-pkgrel or the same epoch:pkgver-pkgrel, if there already should be an epoch.
Hey, On Sat, 2018-10-20 at 08:59 +0800, hagar wrote:
Good morning All,
I understand that there are 3 version control tags in the PKGBUILD file.
pkgver - The Actual Package version
Yes. This is the main control version.
pkgrel - The Arch modification/release count - for changes to the patches, install file's.
This is an extra control version. 1.5.0-2 will be marked as a newer version over 1.5.0-1 and will show up in the updates. That's what you should be bumping if you need to rebuild the package. It will provide a the same version but in a new iteration/build of the package.
epoch - Special version control number.
This is only used if you need to do rollbacks. Here's the version hierarchy: epoch > pkgver > pkgrel The version 2:1.4.0 will be higher in the hierarchy than 1:1.5.0, so pacman will remove 1:1.5.0 and install 2:1.4.0 on system updates.
If I need to rebuild a package due to dependancy rebuilds/changes how do I mark the new package as newer?
Bump the pkgrel.
Do I increase the epoch?
No. You never touch the epoch unless you need to rollback a package.
Or is there another way?
No. Thanks, Filipe Laíns 3DCE 51D6 0930 EBA4 7858 BA41 46F6 33CB B0EB 4BF2
On 10/20/18 7:27 AM, Filipe Laíns via aur-general wrote:
epoch - Special version control number.
This is only used if you need to do rollbacks.
Rollbacks are but one of many reasons to use an epoch, take a look at blender which has 17 of them and I don't think it's ever been rolled back once. Among other things, not much you can do when upstream releases version "1a" as an *update* to version "1", when pacman considers "1a" to be a beta/prerelease of "1". -- Eli Schwartz Bug Wrangler and Trusted User
On 10/19/18 8:59 PM, hagar wrote:
Good morning All,
I understand that there are 3 version control tags in the PKGBUILD file.
pkgver - The Actual Package version
https://wiki.archlinux.org/index.php/PKGBUILD#pkgver
pkgrel - The Arch modification/release count - for changes to the patches, install file's.
https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel
epoch - Special version control number.
https://wiki.archlinux.org/index.php/PKGBUILD#epoch
If I need to rebuild a package due to dependancy rebuilds/changes how do I mark the new package as newer?
Do I increase the epoch?
Or is there another way?
One of these three descriptions explicitly describes itself as "differentiate between consecutive builds of the same version of a package" Rebuilding for a dependency update does, I suppose, qualify as a consecutive rebuild of the same version of a package. :) The fact that it then describes a non-exhaustive list of things which result in consecutive rebuilds (those things being "fixes and additional features"), should not be taken to mean those are the *only* things. -- Eli Schwartz Bug Wrangler and Trusted User
participants (4)
-
Eli Schwartz
-
Filipe Laíns
-
hagar
-
Ralf Mardorf