Re: [aur-general] AUR rate limiting

2018-12-22 Thread hagar
On 23/12/18 7:13 am, Eli Schwartz via aur-general wrote: On 12/22/18 5:40 PM, hagar wrote: On 23/12/18 2:40 am, Florian Pritz via aur-general wrote: On Fri, Dec 21, 2018 at 04:41:28PM +0800, hagar wrote: Is there anything wrong with creating a pertner file to the packages file that has the

Re: [aur-general] AUR rate limiting

2018-12-22 Thread Eli Schwartz via aur-general
On 12/22/18 5:40 PM, hagar wrote: > On 23/12/18 2:40 am, Florian Pritz via aur-general wrote: >> On Fri, Dec 21, 2018 at 04:41:28PM +0800, hagar >> wrote: >>> Is there anything wrong with creating a pertner file to the packages >>> file >>> that has the pkgname, provides, description and git

Re: [aur-general] AUR rate limiting

2018-12-22 Thread hagar
On 23/12/18 2:40 am, Florian Pritz via aur-general wrote: On Fri, Dec 21, 2018 at 04:41:28PM +0800, hagar wrote: Is there anything wrong with creating a pertner file to the packages file that has the pkgname, provides, description and git address in it. Not sure what 'pertner' is supposed to

Re: [aur-general] AUR rate limiting

2018-12-22 Thread Florian Pritz via aur-general
On Fri, Dec 21, 2018 at 04:41:28PM +0800, hagar wrote: > Is there anything wrong with creating a pertner file to the packages file > that has the pkgname, provides, description and git address in it. Not sure what 'pertner' is supposed to mean, but I'd say sure, we could offer a database dump.

Re: [aur-general] AUR rate limiting

2018-12-21 Thread hagar
On 21/12/18 5:21 am, Florian Pritz via aur-general wrote: On Thu, Dec 20, 2018 at 11:02:31PM +0200, Jerome Leclanche wrote: That should probably be fixed as well, but I agree with making the rate limit window 1 hour, at most. A 24 hour API restriction on the AUR API is really nasty imo. So

Re: [aur-general] AUR rate limiting

2018-12-20 Thread Florian Pritz via aur-general
On Thu, Dec 20, 2018 at 11:02:31PM +0200, Jerome Leclanche wrote: > That should probably be fixed as well, but I agree with making the rate > limit window 1 hour, at most. A 24 hour API restriction on the AUR API is > really nasty imo. So is running cower -u in conky every 5 seconds and not

Re: [aur-general] AUR rate limiting

2018-12-20 Thread Jerome Leclanche
On Thu, Dec 20, 2018 at 9:45 PM Jelle van der Waa wrote: > On 12/21/18 at 03:40am, Macca wrote: > > > > On 21 Dec. 2018, 3:26 am, at 3:26 am, Drew DeVault via aur-general < > aur-general@archlinux.org> wrote: > > >Following up from IRC. Hello! > > > > > >I run a public build service which has

Re: [aur-general] AUR rate limiting

2018-12-20 Thread Jelle van der Waa
On 12/21/18 at 03:40am, Macca wrote: > > On 21 Dec. 2018, 3:26 am, at 3:26 am, Drew DeVault via aur-general > wrote: > >Following up from IRC. Hello! > > > >I run a public build service which has Arch Linux support and uses yay > >to install AUR packages when requested. I recently had some

Re: [aur-general] AUR rate limiting

2018-12-20 Thread Macca
I have personally run afoul of the rate limit. I have gotten around it by downloading the package list file. And then by using the got versions of the pkgbuilds. Once you have the pkgbuild tree you only have to update it once and build m any times. You shouldn't have to download it. Some of

[aur-general] AUR rate limiting

2018-12-20 Thread Drew DeVault via aur-general
Following up from IRC. Hello! I run a public build service which has Arch Linux support and uses yay to install AUR packages when requested. I recently had some users running up against the AUR rate limit. The current rate limit window (1 day) seems a bit strict. Would it be possible to apply