November 2013 - Aur-dev - lists.archlinux.org

[aur-dev] No recipient addresses found in message header
by Pierre Schmitz 11 Jan '14

11 Jan '14

Hi, I see a couple of these errors in our log. I assume we try to send a mail without any or an empty recipient. > postfix/sendmail[3523]: fatal: php-aur(992): No recipient addresses found in message header -- Pierre Schmitz, https://pierre-schmitz.com

2 2

Re: [aur-dev] Add a VCS field in the package details page
by Yardena Cohen 30 Nov '13

30 Nov '13

01walid <01walid at gmail.com> wrote: >> Just an *optional* field to be added when submitting the package, where -if >> available- the package submitter can add the PKGBUILD repo link (on Github, >> bitbucket ..etc) Dustin Falgout <dustin at falgout.us> wrote: > I'm not sure that github is the right solution > as we would be relying on an outside service that could possibly change > or disappear at any time in the future. Perhaps something similar to > how wikis allow revisions to be made and viewed by anyone but don't > replace the original content until approved? > > I don't see a way to do anything about this issue that wouldn't be > considered a new feature to the AUR I think this proposal is something simpler, almost akin to url= in a PKGBUILD. I too keep my PKGBUILDs in a git repo, and sometimes I've even put the github link as the upstream URL. It would be nice if there was a more correct place for that. Maintainers can use their own host, doesn't have to be github. Obviously we're responsible for avoiding dead links, just as in url= and source= etc.

2 1

[aur-dev] Add a VCS field in the package details page
by 01walid 28 Nov '13

28 Nov '13

Greetings, I'm new to this mailing list. and first of all, sorry if the idea I'm about to introduce is repeated or annoying (discussed before), I just want to suggest it. *What I noticed:* - Many AUR package maintainers/submitter are developers, or at least have a VCS knowledge (and a Github, Bitbucket ..etc account) - Almost all AUR comments are just PKGBUILDs adjustments, suggestions, enhancement, fixes, new links/md5's or bug reports, written in the comment itself. - Many updated PKGBUILDs do just what suggested in comments (not so DRY), just a copy and a past (the community is helping). - Many outdated PKGBUILDs are just outdated because the package owner is too busy to update it. *What I suggest:* Just an *optional* field to be added when submitting the package, where -if available- the package submitter can add the PKGBUILD repo link (on Github, bitbucket ..etc), the link is visible in the package details page. so when the PKGBUILD is outdated or has a problem, the community can suggest pull requests directly to the repo, and make the life easier for the package maintainer. If you want to go further (and I don't know how's that technically feasible right now), you can make something that automatically pull the PKGBUILD directly from the repo link (or the PKGBUILD file direct link from that repo) That's it, correct me if I'm just talking nonsense. Thanks.

3 2

[aur-dev] [PATCH] don't treat colon as part of package dependency name
by Daniel Albers 26 Nov '13

26 Nov '13

Dependencies can have a description appended, separated by a colon. Don't treat this colon as part of the dependency name. Signed-off-by: Daniel Albers <daniel(a)lbe.rs> --- web/html/pkgsubmit.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/web/html/pkgsubmit.php b/web/html/pkgsubmit.php index d2fe512..305acc7 100644 --- a/web/html/pkgsubmit.php +++ b/web/html/pkgsubmit.php @@ -421,7 +421,7 @@ if ($uid): } if (!empty($depends)) { foreach ($depends as $dep) { - $deppkgname = preg_replace("/(<|<=|=|>=|>).*/", "", $dep); + $deppkgname = preg_replace("/(<|<=|=|>=|>|:).*/", "", $dep); $depcondition = str_replace($deppkgname, "", $dep); if ($deppkgname == "") { -- 1.8.4.2

3 3