=== 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
* 19 packages missing signoffs
* 0 packages older than 14
* brent timothy saner brent.sa...@gmail.com (Sun, 24 May 2015
21:05:22 -0400):
But for now, I think it's not necessary, as the new site will be
wiped before the mail will be sent, as far as I did understand
earlier mails about AUR 4.0.0. Or isn't it?
I'd have to check again- anyone else know
Also I noticed that aur4.archlinux.org is working here. but the main page
lack of a link that specificaly mention that intructions for uloading
packager are here, they links only are guideliness for packaging for TU aur
user, for user itself and bugtracker.
I son't know if is time but why not add
On 25-05-2015 17:49, Pablo Lezaeta Reyes wrote:
Also I noticed that aur4.archlinux.org is working here. but the main page
lack of a link that specificaly mention that intructions for uloading
packager are here, they links only are guideliness for packaging for TU aur
user, for user itself and
* Pablo Lezaeta Reyes prfl...@gmail.com (Mon, 25 May 2015 17:49:56
-0300):
Also I noticed that aur4.archlinux.org is working here. but the main
page lack of a link that specificaly mention that intructions for
uloading packager are here, they links only are guideliness for
packaging for TU aur
Hi,
As described in the proposal to the notification I changed the hostname
in ~/.ssh/config so that that file now reads:
Host aur4.archlinux.org
IdentityFile ~/.ssh/id_rsa-aur
User aur
Port 22
And I tried to pull from and push to that server from an existing
aur-dev repository. However, that
https://gist.github.com/taylorchu/76bee1ed238cb79cc444
This helps me a lot :)
On Mon, May 25, 2015 at 7:15 PM, Doug Newgard scim...@archlinux.info wrote:
On Mon, 25 May 2015 17:19:07 -0700
Kyle Terrien kyleterr...@gmail.com wrote:
1. Is there any way to generate the .SRCINFO file without
I just submitted my first package, so I'm still learning. However,
because I forgot to include a .SRCINFO file until the last commit (i.e
several commits including the first did not have .SRCINFO), AUR4 refused
to accept anything altogether.
kyle@landru ~/builds/aur4/wmload :(
$ git push -v
On Mon, 25 May 2015 17:19:07 -0700
Kyle Terrien kyleterr...@gmail.com wrote:
1. Is there any way to generate the .SRCINFO file without doing the
tar/untar workaround?
mksrcinfo from pkgbuild-introspection-git. You can easily use it to add it to
all commmits with git filter-branch
On 05/25/2015 07:15 PM, Doug Newgard wrote:
On Mon, 25 May 2015 17:19:07 -0700
Kyle Terrien kyleterr...@gmail.com wrote:
1. Is there any way to generate the .SRCINFO file without doing the
tar/untar workaround?
mksrcinfo from pkgbuild-introspection-git. You can easily use it to add it to
I can see that .SRCINFO is completely different from the fields in
PKGBUILD after all. It isn't just the spaces left and right of the =
sign as I first thought. Apparently it doesn't show arrays in the same
way either, instead putting the same key on multiple lines with one
value per key. So this
On Tue, 26 May 2015 01:28:33 -0300
Pablo Lezaeta Reyes prfl...@gmail.com wrote:
Now how is possible to detect and ask for deletion for a ssh'd repo (you
setup-repo 'd the package but the setup'r never upload the git thing)
the server will refuce to setup-repoed if exist.
or what if someone
According to Doug Newgard:
# There are no decent bash parsers out there. To get real info, they
would have
# to be sourced/executed, which is a huge security risk.
In that case, why can PKGBUILD, which is already a bash script, not just
source .SRCINFO, which has its fields in roughly the same
although I still think there would have to be a way to keep from having to
duplicate metadata,
I had similar discussion before. Putting the whole build script in one
file is a very simple and convenient design. If we want to ensure
safety and don't want to duplicate meta data, splitting
IMHO, the ability to run complex script to generate metadata in PKGBUILD is
important.
Consider the pkgver field for most VCS packages (ex. -git ones) that use
VCS command
with text manipulation tools (sed, awk, etc.) to extract current version
from VCS repositories.
The corresponding field in the
Now how is possible to detect and ask for deletion for a ssh'd repo (you
setup-repo 'd the package but the setup'r never upload the git thing)
the server will refuce to setup-repoed if exist.
or what if someone take ounership on a package (aur4) previously owned by
other packager (aur3) and that
On Mon, 25 May 2015 23:05:11 -0400
Kyle k...@gmx.ca wrote:
According to Doug Newgard:
# There are no decent bash parsers out there. To get real info, they
would have
# to be sourced/executed, which is a huge security risk.
In that case, why can PKGBUILD, which is already a bash script, not
17 matches
Mail list logo
