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
