On Wed, 6 Mar 2019 at 18:04, Brett Cornwall via aur-general
wrote:
> I feel that by conflating applicant vetting with political correctness
> you're letting your own political viewpoints get in the way of a proper
> applicant screening. Some of the criteria of a TU involve interfacing
> with the
On 2019-03-06 17:27, Christos Nouskas wrote:
This thread has started giving political correctness the bad name it
deserves. Not so long ago another applicant had to go through a humiliating
interrogation, strong words and insults included, and not many apologies
were issued by his accusers; now
I had the following sitting in my drafts and, after seeing Mr DeVault's TU
application withdrawal, regretted not having sent it. Edited to refer to
the unfortunate conclusion.
On Wed, Feb 27, 2019, 16:10 Darren Wu via aur-general <
aur-general@archlinux.org> wrote:
>
> Instead I'd like to ask
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
Hey Drew,
I wanted to poke you how things are going? Would love to see my review
being incorporated, it took quite a while to look everything up.
This applies to the first batch as well, not just the list you wanted to
look up later. For example python-sshpubkeys build issue, the FHS
changes and
On 2/28/19 4:49 PM, Drew DeVault via aur-general wrote:
> 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
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
On Thu, Feb 28, 2019 at 02:58:06PM +0100, Jerome Leclanche wrote:
> No, it is not, and please don't expect this of volunteers.
Right, I don't expect that from AUR volunteers, but that doesn't mean the AUR
shouldn't be taken seriously. If the maitainer has not interest in updating
and seeking out
On 2/28/19 3:43 PM, Jerome Leclanche wrote:
> On Thu, Feb 28, 2019 at 3:36 PM Levente Polyak via aur-general
> wrote:
>>
>> On 2/28/19 3:33 PM, Jerome Leclanche wrote:
>>>
>>> We have TUs with hundreds of packages. Beyond automatic checks, do you
>>> really expect they keep up with every single
On Thu, Feb 28, 2019 at 3:36 PM Levente Polyak via aur-general
wrote:
>
> On 2/28/19 3:33 PM, Jerome Leclanche wrote:
> >
> > We have TUs with hundreds of packages. Beyond automatic checks, do you
> > really expect they keep up with every single release?
> > I've myself updated several packages
On 2/28/19 3:33 PM, Jerome Leclanche wrote:
>
> We have TUs with hundreds of packages. Beyond automatic checks, do you
> really expect they keep up with every single release?
> I've myself updated several packages that were out of date (and
> unflagged) in [community]. I'm not saying the attitude
On 2/28/19 9:26 AM, Levente Polyak via aur-general wrote:
> On 2/28/19 2:58 PM, Jerome Leclanche wrote:
>> On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
>>> Although I don't have high expectations when dealing with AUR packages, it
>>> is absolutely the maintainers job to keep track of
On Thu, Feb 28, 2019 at 3:26 PM Levente Polyak via aur-general
wrote:
>
> On 2/28/19 2:58 PM, Jerome Leclanche wrote:
> > On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
> >> Although I don't have high expectations when dealing with AUR packages, it
> >> is absolutely the maintainers job to
On 2/28/19 8:58 AM, Jerome Leclanche wrote:
> On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
>> Although I don't have high expectations when dealing with AUR packages, it
>> is absolutely the maintainers job to keep track of upstream updates. This
>> mindset is probably the reason why
On 2/28/19 2:58 PM, Jerome Leclanche wrote:
> On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
>> Although I don't have high expectations when dealing with AUR packages, it
>> is absolutely the maintainers job to keep track of upstream updates. This
>> mindset is probably the reason why
On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
> Although I don't have high expectations when dealing with AUR packages, it is
> absolutely the maintainers job to keep track of upstream updates. This
> mindset is probably the reason why there is so much out of date stuff on the
> AUR. It
Am 28.02.2019 um 04:25 schrieb Drew DeVault via aur-general:
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
> From: Drew DeVault via aur-general
> Sent: Thu Feb 28 04:25:10 CET 2019
> To: Discussion about the Arch User Repository (AUR)
>
> Cc: Drew DeVault
> Subject: Re: [aur-general] Trusted user application: Drew DeVault
>
>
> On 2019-02-28 2:22 AM, Levente P
Hello Drew,
I am a fan of your work on Sway and wlroots, but some of your statements left
me pretty disappointed.
>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
On February 27, 2019 10:47:59 PM EST, Drew DeVault via aur-general
wrote:
>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
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
On 2/27/19 10:25 PM, Drew DeVault via aur-general wrote:
> Aye, this is first I've heard of namcap. Is there a reason that this
> isn't included with makepkg by default?
It brings a hard dependency on python, and its output is often useful
but also often not -- for example when it tries to
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
On 2/25/19 5:55 PM, Drew DeVault wrote:
> 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.
>
You're welcome, but from me this was just the travel version... here
comes the full
Em fevereiro 27, 2019 10:53 Drew DeVault via aur-general escreveu:
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
Hey,
let me just quickly thank all people who have participated in this
thread thus far.
I'm seeing a very polite, respectful and constructive discussion from
all sides, which I very much enjoyed reading.
On 27.02.19 08:53, Drew DeVault via aur-general wrote:
> Instead I'd like to ask this: if
On 2/27/19 3:10 PM, Darren Wu via aur-general wrote:
> As a complete newbie I might not have the rights to chime in here.
As a member of the community, regardless of how long you've been around, you are
absolutely entitled to post to threads on aur-general :) All we ask is everyone
keeps things
As a complete newbie I might not have the rights to chime in here.
But isn't it never too late if Mr. DeVault may add an apologetic comment to
@noobpurple under https://github.com/swaywm/sway/issues/1227 now?
Sincerely yours,
Darren Wu
On Wed, Feb 27, 2019, 21:53 Drew DeVault via aur-general <
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 Wed, Feb 27, 2019 at 4:47 AM Giancarlo Razzolini via aur-general <
aur-general@archlinux.org> wrote:
> Em fevereiro 27, 2019 3:56 Eli Schwartz via aur-general escreveu:
> >
> > If the only thing we can find to complain about is his attitude towards
> > Manjaro, then we obviously cannot find
On Wed, Feb 27, 2019 at 11:47 AM Giancarlo Razzolini via aur-general
wrote:
>
> Em fevereiro 27, 2019 3:56 Eli Schwartz via aur-general escreveu:
> >
> > If the only thing we can find to complain about is his attitude towards
> > Manjaro, then we obviously cannot find anything to complain about.
Em fevereiro 27, 2019 3:56 Eli Schwartz via aur-general escreveu:
If the only thing we can find to complain about is his attitude towards
Manjaro, then we obviously cannot find anything to complain about. :)
I was surprised by this attitude since all my interactions with Drew in the
past
Am 27.02.2019 um 07:56 schrieb Eli Schwartz via aur-general:
On 2/27/19 1:37 AM, Brett Cornwall via aur-general wrote:
On 2019-02-27 02:09, alad via aur-general wrote:
Considering some recent issues regarding team behavior [1] in Arch, I'm
going to have to ask on some of your previous
On 2/27/19 1:37 AM, Brett Cornwall via aur-general wrote:
> On 2019-02-27 02:09, alad via aur-general wrote:
>> Considering some recent issues regarding team behavior [1] in Arch, I'm
>> going to have to ask on some of your previous interactions with the
>> community, and open-source in general. I
On 2019-02-27 02:09, alad via aur-general wrote:
Considering some recent issues regarding team behavior [1] in Arch, I'm
going to have to ask on some of your previous interactions with the
community, and open-source in general. I had two examples in particular,
the MineTest community [2], and
Am 27.02.2019 um 02:30 schrieb Drew DeVault:
> 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
>
Am 27.02.2019 um 02:17 schrieb Jerome Leclanche:
> On Wed, Feb 27, 2019 at 2:10 AM alad via aur-general
> wrote:
>> I haven't read all the documentation for this project, but noticed some
>> oddities. Your build service appears to build AUR packages in full
>> automation using "yay -Syu
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]
>
On Wed, Feb 27, 2019 at 2:10 AM alad via aur-general
wrote:
> I haven't read all the documentation for this project, but noticed some
> oddities. Your build service appears to build AUR packages in full
> automation using "yay -Syu --noconfirm". [4] While I'm sure you took the
> necesseary
Am 25.02.2019 um 00:24 schrieb Drew DeVault via aur-general:
> 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:
>
>
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
On Sun, Feb 24, 2019 at 06:24:59PM -0500, Discussion about the Arch User
Repository (AUR) wrote:
> Hiya! Jerome convinced me to finally apply for TU, and Sven-Hendrik
> agreed to co-sponsor my application (both Cc'd).
> [...]
> As a long time fan and user of Arch Linux, I'm looking forward to the
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
On 25/02/2019 00.23, Drew DeVault wrote:
> 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:
>
>
Hi,
Your build script on the CI does not produce reproducible packages as it uses a
own simple wrapper to call makepkg. F.e. If there is no SOURCE_DATE_EPOCH
defined to now or the value already passed it does not create uniform mtimes.
What I have noticed as well, f.e where you are upstream
On Sun, Feb 24, 2019 at 06:40:13PM -0700, Brett Cornwall via aur-general wrote:
> Here's a PKGBUILD review:
Some additional points!
> ## madonctl
* This package needs to drop `go get` as we have vendored deps.
> ## python-activipy-git
* "v" should be removed from the pkgver as we are dealing
On 2/24/19 8:40 PM, Brett Cornwall via aur-general wrote:
> Here's a PKGBUILD review:
>
> ## In general
> * Prefer sha256sums over sha1sums and md5sums [1]
> * "$srcdir" can often be omitted as the PKGBUILD functions all begin in
> "$srcdir" already - this will make PKGBUILDs much more readable
On 2019-02-24 18:24, Drew DeVault via aur-general wrote:
Hiya! Jerome convinced me to finally apply for TU, and Sven-Hendrik
agreed to co-sponsor my application (both Cc'd).
I must jokingly admit that my first instinct is to vote against your
application so that you'd spend more time on
On Mon, Feb 25, 2019 at 12:23 AM Drew DeVault wrote:
>
> 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:
>
>
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
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 2/24/19 6:24 PM, Drew DeVault via aur-general wrote:
> 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:
>
>
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=sircmpwn
I also maintain a third-party
53 matches
Mail list logo
