FS#19327 - JSON reports different file extension than actual
Attached to Project:
AUR web interface
Opened by Dave Reisner (falconindy) - Sunday, 02 May 2010, 14:46 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 21 February 2011, 09:51 GMT
Opened by Dave Reisner (falconindy) - Sunday, 02 May 2010, 14:46 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 21 February 2011, 09:51 GMT
|
Details
The JSON reply for the package 'clipf' reports a .tgz
extension, but the AUR has repackaged the file as tar.gz.
The AUR's actual page for this package isn't bothered, but
AUR agents looking to fetch the file are disappointed. There
may be others affected but this is the only one I've found
thus far.
I assume this occurs when someone uploads a .tgz (and blatantly avoids using makepkg --source). |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Monday, 21 February 2011, 09:51 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 1.8.0.
Monday, 21 February 2011, 09:51 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 1.8.0.
I have an instance of the AUR code running on my local machine, and I
can't reproduce it. Finally, is this issue related to
FS#15308?Notice the .tgz extension.
entries are just bad.
When you upload to the current version of the AUR, the PKGBUILD tarball
is saved as $pkgname.tar.gz, regardless of the extension that you used
when uploading it.
[1] http://git.cryptocrack.de/aur.git/commit/?id=556de318aeeef6019bb7628389beee1358de93f8
[1] http://projects.archlinux.org/aur.git/commit/?id=556de318aeeef6019bb7628389beee1358de93f8