You are not logged in.
The following page of msort in AUR says "Package details could not be found."
http://aur.archlinux.org/packages.php?ID=33319
While one can fetch the package info by
wget 'http://aur.archlinux.org/rpc.php?type=search&arg=msort' -q -O-And also the tarball is available at http://aur.archlinux.org/packages/msort/msort.tar.gz
Any thoughts?
This silver ladybug at line 28...
Offline
Send an e-mail to aur-general. That's where AUR devs and TUs read stuff.
Last edited by Nezmer (2010-01-03 21:28:42)
English is not my native language .
Offline
Or file a bug report in the AUR section
Offline
There may be other causes, but this happens to me when I submit a brand new package without giving it a category. I'm not sure if the web form has internal checks to prevent this, but I know for sure that it can be done via AUR upload helpers. It can be fixed by just uploading it again with a category.
Last edited by tdy (2010-01-04 03:47:08)
Offline
Thanks for all your replies. The issue's gone already.
@tdy
I uploaded three packages using slurpy, all w/o setting category, and the other two both were fine. There was something the msort PKGBUILD was missing though, its pkgdesc was empty at the first commit. But even I reuploaded it with pkgdesc added, the web interface still could not work. Later I did another reupload, and now all seems good. And I see the category is set to system (by someone...)
What bugs me most is the fact that the web and json interface don't use the same method to parse/display PKGBUILD. What good is that?
This silver ladybug at line 28...
Offline
@all, I've replicated this behavior in a test aur. The next version of slurpy will have a proper default category. I'm not sure why some work and some don't, however. It doesn't seem to be related to $pkgdesc.
archlinux - please read this and this — twice — then ask questions.
--
http://rsontech.net | http://github.com/rson
Offline