[aur-general] AUR upgraded to 2.0.0
Hi, everybody! The official Arch Linux AUR setup has been upgraded to 2.0.0. For a list of changes, you can read the release announcements [1], [2], [3] and the Git log [4]. Please report any issues on the AUR bug tracker [5]. [1] https://mailman.archlinux.org/pipermail/aur-dev/2012-October/002175.html [2] https://mailman.archlinux.org/pipermail/aur-dev/2012-October/002220.html [3] https://mailman.archlinux.org/pipermail/aur-dev/2012-November/002236.html [4] https://projects.archlinux.org/aur.git/log/?id=v2.0.0 [2] https://bugs.archlinux.org/index.php?project=2
Op zondag 4 november 2012 12:09:37 schreef Lukas Fleischer:
Hi, everybody!
The official Arch Linux AUR setup has been upgraded to 2.0.0. For a list of changes, you can read the release announcements [1], [2], [3] and the Git log [4].
Please report any issues on the AUR bug tracker [5].
[1] https://mailman.archlinux.org/pipermail/aur-dev/2012-October/002175.html [2] https://mailman.archlinux.org/pipermail/aur-dev/2012-October/002220.html [3] https://mailman.archlinux.org/pipermail/aur-dev/2012-November/002236.html [4] https://projects.archlinux.org/aur.git/log/?id=v2.0.0 [2] https://bugs.archlinux.org/index.php?project=2
massive great update, thx for all the work everyone has put into it. --Ike
The new AUR is awesome! Regarding voting, I saw some fixes listed in the log, but I think I may have accidentally voted for some packages more than once, because the page indicated I hadn't voted, which seems to be the bug that was fixed in 2.0.0. One of my packages, qt-at-spi-git, which I specifically remember voting for, shows I haven't voted. Could someone take a look at my votes and be sure I haven't voted for anything more than once, and if possible, fix the packages I have voted for so that I don't accidentally vote more than once? Thanks. ~Kyle http://kyle.tk
On Sun, Nov 04, 2012 at 09:01:33AM -0500, Kyle wrote:
The new AUR is awesome! Regarding voting, I saw some fixes listed in the log, but I think I may have accidentally voted for some packages more than once, because the page indicated I hadn't voted, which seems to be the bug that was fixed in 2.0.0. One of my packages, qt-at-spi-git, which I specifically remember voting for, shows I haven't voted. Could someone take a look at my votes and be sure I haven't voted for anything more than once, and if possible, fix the packages I have voted for so that I don't accidentally vote more than once? Thanks. ~Kyle http://kyle.tk
You can't possibly vote more than once -- it would violate the constrants on the PackageVotes table: CREATE UNIQUE INDEX VoteUsersIDPackageID ON PackageVotes (UsersID, PackageID); This was the case in 1.9.1 as well. If the AUR says you haven't voted, then I'd say it means you haven't voted. d
According to Dave Reisner: # CREATE UNIQUE INDEX VoteUsersIDPackageID ON PackageVotes (UsersID, # PackageID); # # This was the case in 1.9.1 as well. If the AUR says you haven't voted, # then I'd say it means you haven't voted. Ah OK. The fix in the log made me just a little nervous. Maybe I didn't vote for that package after all, although I thought for sure I did. Thanks for the explanation. ~Kyle http://kyle.tk
Hi, Thanks for the new AUR! It looks great, and I've already discovered new functionality that I found useful. GJ -- Best regards, Alexander Rødseth xyproto / TU
On Sun, Nov 4, 2012 at 12:09 PM, Lukas Fleischer <archlinux@cryptocrack.de> wrote:
Hi, everybody!
The official Arch Linux AUR setup has been upgraded to 2.0.0. For a list of changes, you can read the release announcements [1], [2], [3] and the Git log [4].
Please report any issues on the AUR bug tracker [5].
[1] https://mailman.archlinux.org/pipermail/aur-dev/2012-October/002175.html [2] https://mailman.archlinux.org/pipermail/aur-dev/2012-October/002220.html [3] https://mailman.archlinux.org/pipermail/aur-dev/2012-November/002236.html [4] https://projects.archlinux.org/aur.git/log/?id=v2.0.0 [2] https://bugs.archlinux.org/index.php?project=2
The new AUR is awesome! I have updated PKGBUILDer to work with it earlier today, and am working to bring it to my new project, aurqt (a desktop AUR client in {Py,}Qt; but it is broken on python 3.3 because of 3rd-party libs). But I think that two things need improvement: 1. I tried to insert the key ID (4 chars) instead of the fingerprint (40.) A hint (like <tt>gpg --fingerprint</tt>) would be useful. 2. Cannot unflag a package unless you’re the maintainer — sometimes, flags are made errorneously and you need to revert it. -- Kwpolska <http://kwpolska.tk> stop html mail | always bottom-post www.asciiribbon.org | www.netmeister.org/news/learn2quote.html GPG KEY: 5EAAEA16
According to Kwpolska: # 2. Cannot unflag a package unless you’re the maintainer — sometimes, # flags are made errorneously and you need to revert it. +1 here. It's great that not just anyone can unflag a package, but if I inadvertently flag a package, it's better if I can revert the flag myself rather than having to add a comment for the maintainer to remove the flag or send a message to this list to get a TU to do it. ~Kyle http://kyle.tk -- Linux killed Kenny, bastard! --Subject of a real e-mail to the Linux kernel mailing list 12 January, 2009
On Sun, Nov 4, 2012 at 1:55 PM, Kwpolska <kwpolska@gmail.com> wrote: <snip>
But I think that two things need improvement: 1. I tried to insert the key ID (4 chars) instead of the fingerprint (40.) A hint (like <tt>gpg --fingerprint</tt>) would be useful.
The input box is labeled "PGP Key Fingerprint" not "PGP Key ID". A bit more verbosity on the error message probably wouldn't hurt though.
2. Cannot unflag a package unless you’re the maintainer — sometimes, flags are made errorneously and you need to revert it.
The problem with the flagger being able to unflag a package is they can repeatedly flag/unflag. This would make the maintainer receive a ton of e-mails. Unfortunately, that has happened before and was a big factor in the change. An alternative would be to add a small separate flagging page (similar to the main site) to reduce the number of erroneously flagged packages, while still preventing the flag/unflag abuse. That could also fix a CSRF issue that was re-introduced with the routing changes. Thanks for your suggestions.
Awesome, thank you very much for your work. We really have good people around arch community. My two cents, I have finished and uploaded to www.transifex.com the catalan translation. I though that there will be a notice in arch-general. But I guess that it was done in aur-dev which I was not subscribed to. Anyway here it is so catalan can be properly incorporated in a future release. Thanks, Hector 2012/11/4 Lukas Fleischer <archlinux@cryptocrack.de>
Hi, everybody!
The official Arch Linux AUR setup has been upgraded to 2.0.0. For a list of changes, you can read the release announcements [1], [2], [3] and the Git log [4].
Please report any issues on the AUR bug tracker [5].
[1] https://mailman.archlinux.org/pipermail/aur-dev/2012-October/002175.html [2] https://mailman.archlinux.org/pipermail/aur-dev/2012-October/002220.html [3] https://mailman.archlinux.org/pipermail/aur-dev/2012-November/002236.html [4] https://projects.archlinux.org/aur.git/log/?id=v2.0.0 [2] https://bugs.archlinux.org/index.php?project=2
-- Hector Martínez-Seara Monné mail: hseara@gmail.com Tel: +34656271145 Tel: +358442709253
participants (8)
-
Alexander Rødseth
-
canyonknight＠gmail.com
-
Dave Reisner
-
Hector Martinez-Seara
-
Ike Devolder
-
Kwpolska
-
Kyle
-
Lukas Fleischer