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 the
Hiya! Jerome convinced me to finally apply for TU, and Sven-Hendrik
agreed to co-sponsor my application (both Cc'd).
I'm a generalist that works on free software full time. I maintain the
following AUR packages:
https://aur.archlinux.org/packages/?SeB=m&K=sircmpwn
I also maintain a third-party A
On 2019-02-24 7:01 PM, Eli Schwartz via aur-general wrote:
> Your application sounds interesting and I generally admire your
> open-source work.
Thank you!
> What is samurai, exactly? It claims to be "a ninja-compatible build
> tool" but I'm not sure what the comparative advantages are supposed
On 2019-02-24 7:09 PM, Drew DeVault wrote:
> P.S. You pointed out on IRC that my first email wasn't signed, so I
> signed this one to be sure.
Man. I have this habit of writing the whole email, then reading through
and making edits and forgetting about any important promsises I made
like signatur
Thanks for all the feedback! I went through and cleaned up all of my AUR
packages - something a wiser man would have done before submitting the
TU application.
Note that in some cases I disowned packages I was no longer interested
in maintaining, and in the case of vgo both disowned and filed a
de
Hey Christian!
On 2019-02-25 6:21 PM, Christian Rebischke via aur-general wrote:
> 1. Can you describe in a few sentences how you build your packages for
> the AUR and for your own repository?
For the AUR: I just run makepkg -i and makepkg --printsrcinfo >
.SRCINFO. I keep it pretty casual for t
On 2019-02-27 2:09 AM, alad via aur-general wrote:
> [2] https://news.ycombinator.com/item?id=18156980
I said my piece in the thread and I encourage anyone concerned to read
through the comments here. For what it's worth, the concerns are over
incidents which occured 4-5 years ago.
> [3]
> http
On 2019-02-26 11:37 PM, Brett Cornwall via aur-general wrote:
> I would also chip in with the following from early 2017:
>
> https://github.com/swaywm/sway/issues/1227
>
> (I am also not in any sort of witch hunt, just thought this would be
> relevant.)
It should go without saying that I regret
On 2019-02-28 2:22 AM, Levente Polyak via aur-general wrote:
> > For the AUR I don't keep up with upstream releases, I just wait for
> > someone to mark the package as outdated. For Alpine Linux I use a
> > combination of subscribing to the upstream -announce mailing list and
> > subscribing to Gi
On 2019-02-27 10:42 PM, Eli Schwartz via aur-general wrote:
> I guess the difference between PyPI and Github sources could be
> clarified, but really I'd much rather upstreams would get in the habit
> of using a MANIFEST.in which ensured the license and testsuite was
> correctly included in the sou
The AUR is not community. The expectations are higher for trusted users
- hence the trust. Naturally responding to emails, keeping up with new
releases, etc, is part of the role. That's why it's a *role* - it serves
to define the responsibilities. There is no role for AUR package
maintainer outside
A week of discussion and time to reflect later, and I'd like to withdraw
my application for trusted user.
I had hesitated to apply to become a TU for some time due to various
personal concerns, some of which were reaffirmed during the ensuing
discussion, and those which weren't directly reaffirmed
Note: your email reminded me to commit to what I had been preparing to
do for a while, but was not the reason I withdrew my TU application.
On 2019-03-04 , Levente Polyak via aur-general wrote:
> I wanted to poke you how things are going? Would love to see my review
> being incorporated, it took q
13 matches
Mail list logo
