Re: [aur-general] Misspelled email on account registration
On 29/11/14 03:15, Sergio Baldovi wrote: > Hi, some days ago I register an account (serbalgi) on AUR with a > misspelled email address. The activation mail has not arrived and the > account has not been validated. Anyone know if there is an expiration > timeout? > > I've also tried a password reset (d'oh!) and a random login states: > "Your password has been reset. If you just created a new account, please > use the link from the confirmation email to set an initial password. > Otherwise, please request a reset key on the Password Reset page." > > I think I'm sort of stuck with the activation. I've corrected your email address; try resetting your password again.
[aur-general] Misspelled email on account registration
Hi, some days ago I register an account (serbalgi) on AUR with a misspelled email address. The activation mail has not arrived and the account has not been validated. Anyone know if there is an expiration timeout? I've also tried a password reset (d'oh!) and a random login states: "Your password has been reset. If you just created a new account, please use the link from the confirmation email to set an initial password. Otherwise, please request a reset key on the Password Reset page." I think I'm sort of stuck with the activation.
Re: [aur-general] Package promotion process
On 28/11, Daniel Micay wrote: On 28/11/14 12:32 PM, Dave Reisner wrote: It shall never return. Never say never, the rules could be revisited one day :P. It makes sense to forbid automatic installation, but it's a bit silly to forbid search / downloading from the AUR when we permit it for other third party dumping grounds like PyPi. Especially when burp is allowed to be in there too. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ pgpyajY8MYeaD.pgp Description: PGP signature
Re: [aur-general] Package promotion process
On 28/11/14 12:47 PM, Troy Engel wrote:
> On Fri, Nov 28, 2014 at 11:38 AM, Daniel Micay wrote:
>> On 28/11/14 12:32 PM, Dave Reisner wrote:
>>>
>>> It shall never return.
>>
>> Never say never, the rules could be revisited one day :P. It makes sense
>> to forbid automatic installation, but it's a bit silly to forbid search
>> / downloading from the AUR when we permit it for other third party
>> dumping grounds like PyPi.
>>
>
> Yeah, I mean no offense to the current rule, but AUR is a fantastic
> part of Arch and not having *anything* which can install an AUR
> package in Community seems... disingenuous to the adoption of AUR from
> a fresh install. I understand this can be a political battle ("which
> AUR helper is best") but cower sure seems like a great candidate to
> just help people get started.
>
> $0.02,
> -te
Not having a way to install an AUR package draws a clear line between
supported packages and unsupported ones. Anyone can upload an AUR
package so pretending it's anything but untrusted, totally arbitrary
code would be dangerous.
However, cower *does not* support installing AUR packages, only
downloading and searching them. That's why I think we could revisit this
rule in the future and refine it.
However, the status quo is that it's not permitted in [community].
signature.asc
Description: OpenPGP digital signature
Re: [aur-general] Package promotion process
On Fri, Nov 28, 2014 at 11:38 AM, Daniel Micay wrote:
> On 28/11/14 12:32 PM, Dave Reisner wrote:
>>
>> It shall never return.
>
> Never say never, the rules could be revisited one day :P. It makes sense
> to forbid automatic installation, but it's a bit silly to forbid search
> / downloading from the AUR when we permit it for other third party
> dumping grounds like PyPi.
>
Yeah, I mean no offense to the current rule, but AUR is a fantastic
part of Arch and not having *anything* which can install an AUR
package in Community seems... disingenuous to the adoption of AUR from
a fresh install. I understand this can be a political battle ("which
AUR helper is best") but cower sure seems like a great candidate to
just help people get started.
$0.02,
-te
Re: [aur-general] Package promotion process
On 28/11/14 12:32 PM, Dave Reisner wrote: > > It shall never return. Never say never, the rules could be revisited one day :P. It makes sense to forbid automatic installation, but it's a bit silly to forbid search / downloading from the AUR when we permit it for other third party dumping grounds like PyPi. signature.asc Description: OpenPGP digital signature
Re: [aur-general] Package promotion process
On Fri, Nov 28, 2014 at 11:29:45AM -0600, Troy Engel wrote: > When a package has hundreds of votes, what keeps it from getting > promoted into Community? I'm talking specifically about cower: > > https://aur.archlinux.org/packages/cower/ > > Bootstrapping AUR on fresh installs is manual, what's the reason cower > hasn't been promoted to Community so it's easy to install with pacman > and have AUR usable out-of-the-box? (apologies if this has been > discussed before and I'm opening some sort of hornet's nest) > > -te It appears that there are intentionally no AUR helpers in the official repo. https://wiki.archlinux.org/index.php/AUR: > Warning: There is not and will never be an official mechanism for > installing build material from the AUR. All AUR users should be familiar > with the build process. Cower is a little different since it does not automate the building, but the idea seems to apply.
Re: [aur-general] Package promotion process
On Fri, Nov 28, 2014 at 11:29:45AM -0600, Troy Engel wrote: > When a package has hundreds of votes, what keeps it from getting > promoted into Community? I'm talking specifically about cower: > > https://aur.archlinux.org/packages/cower/ > > Bootstrapping AUR on fresh installs is manual, what's the reason cower > hasn't been promoted to Community so it's easy to install with pacman > and have AUR usable out-of-the-box? (apologies if this has been > discussed before and I'm opening some sort of hornet's nest) > > -te Fun fact, cower *was* in [community] for a very short period of time: https://lists.archlinux.org/pipermail/arch-dev-public/2010-December/018893.html It shall never return.
[aur-general] Package promotion process
When a package has hundreds of votes, what keeps it from getting promoted into Community? I'm talking specifically about cower: https://aur.archlinux.org/packages/cower/ Bootstrapping AUR on fresh installs is manual, what's the reason cower hasn't been promoted to Community so it's easy to install with pacman and have AUR usable out-of-the-box? (apologies if this has been discussed before and I'm opening some sort of hornet's nest) -te
Re: [aur-general] Delete request: meld-beta
On Fri, Nov 28, 2014, 10:29 Marcel Korpel wrote: > * Taylor Lookabaugh (Fri, 28 Nov 2014 > 08:20:07 +): > > On Fri, Nov 28, 2014, 02:13 Gary van der Merwe > > wrote: > > > > Please delete meld-beta. The new gtk3 port is now available in extra, > > so I don't plan on maintaining this package further. Those who want to > > use dev versions should rather use meld-git. > > > > https://aur.archlinux.org/packages/meld-beta/ > > > > Thanks, > > > > Gary > > > > Use the file request on the package's page via the web interface. > > Also, use quotation marks (>'s) to quote other people's text, now it's > as if you wrote everything. ;) > > Regards, > Marcel > Google's inbox app, I'm not near a computer til Monday. ;)
Re: [aur-general] Moving opensc from community to AUR
On 11/27/2014 09:56 PM, Sébastien Luttringer wrote: > On 26/11/2014 15:09, Timothy M. Redaelli wrote: >> On 08/06/2014 02:09 AM, Sébastien Luttringer wrote: >>> Hello, >>> >>> I'm not using opensc anymore, is there a Dev/Tu interested by taking >>> care of it? >>> >>> I will move it to AUR if nobody is interested. >> >> Hi, >> I'd like to maintain it, but it's already moved to AUR and it doesn't >> have 10 votes. >> Should I wait for 10 votes to re-move it into community? >> >> Thanks >> > Let's go. Move it back. Done, thanks -- Timothy M. Redaelli Arch Linux Trusted User signature.asc Description: OpenPGP digital signature
Re: [aur-general] Delete request: meld-beta
* Taylor Lookabaugh (Fri, 28 Nov 2014 08:20:07 +): > On Fri, Nov 28, 2014, 02:13 Gary van der Merwe > wrote: > > Please delete meld-beta. The new gtk3 port is now available in extra, > so I don't plan on maintaining this package further. Those who want to > use dev versions should rather use meld-git. > > https://aur.archlinux.org/packages/meld-beta/ > > Thanks, > > Gary > > Use the file request on the package's page via the web interface. Also, use quotation marks (>'s) to quote other people's text, now it's as if you wrote everything. ;) Regards, Marcel
[aur-general] Signoff report for [community-testing]
=== 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 * 13 packages missing signoffs * 3 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == Incomplete signoffs for [community] (11 total) == * freevo-1.9.0-14 (any) 0/2 signoffs * gdal-1.11.1-3 (i686) 0/1 signoffs * performous-1.0-1 (i686) 0/1 signoffs * python-h5py-2.3.1-3 (i686) 0/1 signoffs * python-pytables-3.1.1-4 (i686) 0/1 signoffs * vtk-6.1.0-1 (i686) 0/1 signoffs * gdal-1.11.1-3 (x86_64) 0/2 signoffs * performous-1.0-1 (x86_64) 0/2 signoffs * python-h5py-2.3.1-3 (x86_64) 0/2 signoffs * python-pytables-3.1.1-4 (x86_64) 0/2 signoffs * vtk-6.1.0-1 (x86_64) 0/2 signoffs == Incomplete signoffs for [unknown] (2 total) == * packagekit-qt-0.9.2-2 (i686) 0/1 signoffs * packagekit-qt-0.9.2-2 (x86_64) 0/2 signoffs == All packages in [community-testing] for more than 14 days (3 total) == * freevo-1.9.0-14 (any), since 2014-08-27 * packagekit-qt-0.9.2-2 (i686), since 2014-09-29 * packagekit-qt-0.9.2-2 (x86_64), since 2014-09-29 == Top five in signoffs in last 24 hours == 1. fyan - 3 signoffs 2. bpiotrowski - 2 signoffs
Re: [aur-general] Delete request: meld-beta
On Fri, Nov 28, 2014, 02:34 Gary van der Merwe wrote: Sorry guys. I was not aware if this new feature. Thanks. On Fri, Nov 28, 2014 at 10:19 AM, G. Schlisio wrote: > hey pal, > i'm sorry to inform you that you are doing it wrong. > please go to the aur interface and use the button "file a request" to > get this deleted. > regards Also, for future reference, it's best to bottom post in your reply, or simply refrain from top posting.
Re: [aur-general] Delete request: meld-beta
Sorry guys. I was not aware if this new feature. Thanks. On Fri, Nov 28, 2014 at 10:19 AM, G. Schlisio wrote: > hey pal, > i'm sorry to inform you that you are doing it wrong. > please go to the aur interface and use the button "file a request" to > get this deleted. > regards
Re: [aur-general] Delete request: meld-beta
On Fri, Nov 28, 2014, 02:13 Gary van der Merwe wrote: Please delete meld-beta. The new gtk3 port is now available in extra, so I don't plan on maintaining this package further. Those who want to use dev versions should rather use meld-git. https://aur.archlinux.org/packages/meld-beta/ Thanks, Gary Use the file request on the package's page via the web interface.
Re: [aur-general] Delete request: meld-beta
Am 28.11.2014 um 09:13 schrieb Gary van der Merwe: > Please delete meld-beta. The new gtk3 port is now available in extra, > so I don't plan on maintaining this package further. Those who want to > use dev versions should rather use meld-git. > > https://aur.archlinux.org/packages/meld-beta/ > > > Thanks, > > Gary hey pal, i'm sorry to inform you that you are doing it wrong. please go to the aur interface and use the button "file a request" to get this deleted. regards
[aur-general] Delete request: meld-beta
Please delete meld-beta. The new gtk3 port is now available in extra, so I don't plan on maintaining this package further. Those who want to use dev versions should rather use meld-git. https://aur.archlinux.org/packages/meld-beta/ Thanks, Gary
