This concerns the aur package mp3cd which is out-of-date. As pkgver should be the developers version number and the result in this case is that AUR sees an older package as newer? Present PKGBUILD pkger;
pkgname=mp3cd pkgver=1.026001 pkgrel=1 ... source=("$url/download/$pkgname-$pkgver.tar.gz") ...
As you can see, pkgver is part of the url, which it should be. But the present dev version is 1.0.27 which leads to the problem that AUR sees version 1.0.26001 as newer than 1.0.27, which it is not. I've tried to search for this but haven't found anything, just a debate about pkgrel.
I could hardcode the url but then I wouldn't be following standards and maybe the PKGBUILD would lead to an upodate to an older version.
AUR sees version 1.0.26001 as newer than 1.0.27
What is this statement based on?
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
The AUR itself does not "see" package versions. Could you please clarify if pacman thinks that 1.0.26001 is newer than 1.0.27? That could be the case.
Well I edited the present AUR PKGBUILD to reflect the new dev version 1.0.27 like this;
... pkgname=mp3cd pkgver=1.027 pkgrel=3 ...
And still yaourt/packer want to update it from thenew dev version 1.027 to version 1.026001. Maybe there's some obvius thing I miss?
Since I like this app I'd like to adopt it but must have a functional PKGBUILD first. It does work on my set up locally, of course. Only have to block it in pacman.conf.
:: Starting full aur upgrade... warning: mp3cd 1.027-3: ignoring package upgrade (1.027-3 => 1.026001-1)
Last edited by swanson (2012-05-15 07:27:24)
That's a problem with yaourt and packer, not with the AUR. Go to their places and report the bug.
Are you sure it's a bug?
It is a bug. Neither yaourt nor packager can deal with unconventionally structured version numbers. If that thing had another dot, like 1.26.9999 and then 1.27, then they would not fail. You could, on the other hand, report the bug upstream to the mp3cd dev, telling him his numbering sucks.
Well, other options might be to get the present package removed, or upload a new package with the name mp3cd-1.027. But the last alternative isn't ok, as far as I understand.
What does pacman say if you install it manually?
This problem comes from the weird versioning change. You'll need to use epoch (man PKGBUILd for more info).