October 2007 - Arch-projects - lists.archlinux.org

[arch-projects] AUR and Repoman development updates
by Paul Mattal 10 Oct '07

10 Oct '07

For this week: Essentially, there is no update. I'm scrambling toward my third busy weekend in a row this weekend, and so I'm unlikely to get things merged until next week. That said, I will do 1.4.1 early next week, and look toward merging features for 1.5.0 by 10/20. After 10/20, it will be testing and bugfixes until we're ready for release (1 or 2 weeks). In spite of the busy weekends, I have made some substantial headway on repoman. Not ready for public consumption yet, but getting there. I hope to kick an initial implementation out the door next week for comment and tinkering; it will be far from even alpha at that point, but the framework will be in place and we'll be ready for the serious work to begin. - P

1 0

[arch-projects] October 76% OFF
by VIAGRA � Official Site 08 Oct '07

08 Oct '07

1 0

[arch-projects] AUR: Some markup templates
by Loui 08 Oct '07

08 Oct '07

If you tried to cherry pick commit 2e27c1f695c42408efb6a77d464331ab9440e604 from me and tested the site you might get a fatal T_STRING error. Solution: In php.ini set "short_open_tag = Off" Short tags are deprecated and they've all been replaced with long tags in AUR code. Hmm maybe we should put a .htaccess file with that parameter to make sure of the environment. Please check out the templates any how! Thanks.

3 6

[arch-projects] New PKGBUILD parsing php script
by tardo 07 Oct '07

07 Oct '07

Greetings, I'm really tired so I'll try to keep this as short as possible. Instead of working on things I should be working on, like my AUR 1.5 goals, or my homework or my research project, I decided to write a new parsing algorithm that hopefully gets adopted into AUR code. Using PHP_LexerGenerator from the PEAR library, I was able to automagically create a php class that parses the entire PKGBUILD for sanity, according to current arch pkgbuild standards. I wrote a quick script to actually test the algorithm and have been finding bugs here and there, but I need a broader audience, and many more test cases. So without further ado, the test site: http://nagi-fanboi.net/arch/pkgbuild/parser.php Usage is simple; click browse, locate a PKGBUILD, click submit. If parsing is successful, you'll see the variables relevant to AUR displayed, else you'll get a meaningless error. There are two possible ways to get an error currently, one is to ignore the current arch pkgbuild standards (which I will highlight common mistakes below), and one is to have an actual bug in my code which overlooks some regex. In the case yours falls in the latter category, please email me your PKGBUILD so I can patch it up (or you can post it on this ML by replying to this email). I should mention that the parsing algorithm is a lexical scanner, and if you don't know what that is, just remember that it's very strict. The smallest mistake will lead to an error. Here are some common errors I found in random PKGBUILDs: - license is always an array - pkgname is always small letters - pkgver cannot have '-' - no arch=() array - no license=() array - custom variables always must start with a _ - (empty variables, while not a standard helps reduce clutter) ... and so on. I've tested many PKGBUILDs locally, but I don't think I've covered every case, which is why I'm now posting on the ML for testing. Here are some of the benefits to using this script: - every variable in the PKGBUILD is properly parsed, and checked for sanity - url is properly displayed properly even if custom variables are used (which is a problem with the current script) - the script uses a decent OOP structure, hence every variable is readily available once parsed (including arch, groups, even the entire build function) - this script will definitely help enforce pkgbuild standards Of course, I have bigger goals for this. I plan to completely rewrite the pkgsubmit.php script that is currently in use. Using Archive::Tar and this lexical scanner should make the pkg submission process less of a pain than the current hackish script (no offence). Long story short, I need testers. If you have PKGBUILDs laying around and free time, please help me test it. Thank you. - tardo

1 0

[arch-projects] [AUR] More AUR bugs that can be closed
by tardo 04 Oct '07

04 Oct '07

2 1

Re: [arch-projects] [tur-users] AUR 1.4.0
by Joerie de Gram 04 Oct '07

04 Oct '07

On 10/3/07, Grigorios Bouzakis <grbzks(a)gmail.com> wrote: > RSS doesnt seem to be working atm. dont know if its supposed to.. There seems to be a missing directory (aur/web/html/xml). It should be created and chmodded so the webserver is able to write to it. Joerie

4 4

[arch-projects] AUR: Account creation/editing fixes
by Loui 04 Oct '07

04 Oct '07

I fixed a bunch of things in web/lib/acctfuncs.inc I had committed this awhile ago but found problems. It should all be good now (hopefully I tested it thoroughly this time) Please check it out http://louipc.dontexist.org/cgi-bin/gitweb.cgi?p=aur/.git;a=commitdiff;h=b7…

1 0

[arch-projects] [AUR] Login timout issue (discuss)
by tardo 03 Oct '07

03 Oct '07

Does anyone know the reason why this was implemented? If so, any objections to completely removing it? - tardo

3 4

[arch-projects] [AUR2] "Upstream" git repo
by Xilon 03 Oct '07

03 Oct '07

I made an "upstream"/central repo on repo.or.cz: http://repo.or.cz/w/aur2.git Currently only Thralas and I have push access. I think it might be a good idea to go the Linux kernel way and have a few people with push access who have to sign off any contributions and then push.

1 0

Re: [arch-projects] [tur-users] Proposal of changes for AUR
by Paul Mattal 02 Oct '07

02 Oct '07

> Sorry it's just a giant list, I basically just copy/pasted out of my > chat with louipc on irc. Thanks for creating this list! I would like to request that folks test against the test site: https://subzero.elys.com I have merged the pending changes for 1.4.0 into the git master. You can look at the detailed change list at: http://projects.archlinux.org/git/?p=aur.git;a=shortlog;h=master Please let me know if you see anything broken or not working. I plan to release 1.4.0 either tomorrow or Monday! At this point, the only other things I will merge into master before the release are bigfixes or regressions to the current material. So send me a patch or a commit ID if you think there's a patch I should include before release. Thanks! - P

6 7