You are not logged in.
Hello. I want to understand package versions. The one puzzling me is tilde. Why does its version end with hyphen? I can't see why from the PKGBUILD file. The upstream code lives in git, if that helps. Thanks.
Offline
If I had to guess, it would be because the maintainer isn't creating the source tarball correctly.
Offline
Hmm, seems unlikely. He packages for other distros, mainly. The tarballs must work. I don't think he knows AUR very well yet. What about this PKGBUILD line,
install=''
Offline
Hmm, seems unlikely. He packages for other distros, mainly.... I don't think he knows the AUR very well yet.
This does not follow - how does having no experince with packing for archlinux make it less lilkely that he did something wrong?
The tarballs must work.
What do you mean? Many aur packages do not 'work'. This is unfortunate, but we can't pretend that it is not true. For this one, does the built package end with a hyphen, or is it just on the web interface? I was going to check this myself, but it has two dependencies from the AUR only, and one of those has several AUR-only dependencies. I stopped at that point, it's not worth the effort for me just to find out if this builds a package with a odd version number. It looks to me like it should be a normally numbered package and the error is only on the web interface.
What about this PKGBUILD line,
install=''
That is unneeded, but perfectly fine. It is just an empty variable.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
It looks to me like it should be a normally numbered package and the error is only on the web interface.
The problem is the .AURINFO. It contains pkgver and pkgrel in a merged format, but it should be separate. It would also be better to use .SRCINFO
wrong:
pkgver = 0.3.4-1right:
pkgver = 0.3.4
pkgrel = 1| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Ha, it contains both .AURINFO and .SRCINFO. Definitely creating it wrong.
Offline
I guess progandy isolated the cause. Thanks.
Trilby you misread me; we agree. I felt an AUR mistake from ignorance more likely than a tarball glitch, since the same tarballs work for other distros. That's all I meant about tarballs working.
Pacman reports a good version number after install. What the glitch affects is how AUR helpers upgrade. It makes them think a newer version is available that isn't. For now I use IgnorePkg to skip re-installs of the same version over and over. Thanks.
Offline
Trilby you misread me; we agree. I felt an AUR mistake from ignorance more likely than a tarball glitch, since the same tarballs work for other distros. That's all I meant about tarballs working.
So you were talking about different tarballs. As you say, a tarball that is only listed by name in the source array in the PKGBUILD is unlikely to affect the AUR meta in this way. What was meant by "the source tarball" is the output of `makepkg --source` that gets uploaded to the AUR.
Offline