[aur-general] Signoff report for [community-testing]

2014-07-05 Thread Arch Website Notification
=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 0 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 0 fully signed off packages * 8 packages missing signoffs * 0 packages older than 14 days

[aur-general] AUR 3.3.0 released

2014-07-05 Thread Lukas Fleischer
Hello, I am pleased to announce that AUR 3.3.0 has just been released. The official AUR setup [1] has already been updated. This release includes several improvements to the package request feature and a couple of bug fixes. For a comprehensive list of changes, please consult the Git log [2].

Re: [aur-general] AUR 3.3.0 released

2014-07-05 Thread Steven Honeyman
Does anyone else think there is now just one thing missing from the request feature (or a different link)? I keep thinking this package is broken or this package needs attention (for reasons other than being out of date or abandoned), and there isn't a suitable button! Yes, the maintainer *should*

Re: [aur-general] AUR 3.3.0 released

2014-07-05 Thread Carl Schaefer
On Sat, 2014-07-05 at 18:29 +0100, Steven Honeyman wrote: Does anyone else think there is now just one thing missing from the request feature (or a different link)? I keep thinking this package is broken or this package needs attention (for reasons other than being out of date or abandoned),

Re: [aur-general] AUR 3.3.0 released

2014-07-05 Thread A Rojas
Carl Schaefer wrote: How about adding a needs attention checkbox when submitting a comment that, when checked, would email the maintainer and raise an attention requested flag on the package display page? The maintainer could check an AR reset checkbox when submitting his/her own comment,

Re: [aur-general] AUR 3.3.0 released

2014-07-05 Thread Steven Honeyman
Wouldn't this push more work towards the AUR maintainers though? What actually happens when someone requests a package is to be orphaned? Can the package maintainer un-request it by doing something? I guess I just assumed (like the ML previously) that a bunch of people would get an email with the