On 26/10/2018 19:07, Shay Gover via aur-general wrote: >> Message: 1 >> Date: Fri, 26 Oct 2018 18:29:59 +0200 >> From: Michael Kogan <[email protected]> >> To: "Discussion about the Arch User Repository (AUR)" >> <[email protected]> >> Subject: Re: [aur-general] Automatic package version >> Message-ID: >> < >> calsov+bp9ez_v_wfsv5mz9muaringnczxwyyx_1endofkj_...@mail.gmail.com> >> 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' > >> Message: 3 >> Date: Fri, 26 Oct 2018 12:34:44 -0400 >> From: Eli Schwartz <[email protected]> >> To: [email protected] >> Subject: Re: [aur-general] Automatic package version >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> On 10/26/18 12:26 PM, Shay Gover via aur-general wrote: >>> 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 >> >> 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 >> >>
signature.asc
Description: OpenPGP digital signature
