April 2008 - Arch-dev-public - lists.archlinux.org

[arch-dev-public] Database breakage - again!
by Thomas Bächler 22 Apr '08

22 Apr '08

Okay, I am pissed right now. bzip2 (x86_64) had version 1.0.5-1 in the database, while the version in the package and the filename are 1.0.5-2. I tried to fix it, and found out what happened in the first place: [x86_64][17:21:48][thomas@artin trunk]$ archrelease testing-x86_64 svnmerge: no integration info available ~/arch/repos/svn-packages/bzip2 ~/arch/repos/svn-packages/bzip2/trunk Nothing to commit ~/arch/repos/svn-packages/bzip2/trunk However, the PKGBUILD in testing-x86_64 was the old one. This is clearly a problem in the archrelease script. AND in our db scripts. I fixed it this time, however, people should actually look at the output of the scripts. It's not like we're monkeys.

3 5

[arch-dev-public] SVN packaging workflow
by Thomas Bächler 21 Apr '08

21 Apr '08

I promised to do this a while ago. This is how you work with the new SVN layout: UPDATE PACKAGES --------------- Check out the package: $ archco pkgname $ cd pkgname/trunk/ If the package is already checked out: $ cd pkgname $ svn up $ cd trunk/ This is important so there won't be any conflicts later! If you forget to svn up, you can still solve the problems that may occur, but this is way easier. Now do whatever you have to do and run makepkg, namcap etc. Now run {core,extra,testing}pkg. This uploads the package, checks the integrity and runs 'archrelease repo-arch'. archrelease seems to be buggy sometimes, so make sure it actually adds files to repos/repo-arch - you can see that from the output (something like "Sending repos/repo-arch/PKGBUILD" I thknk). The db scripts look inside pkgname/repos/repo-arch to find the right PKGBUILD! Now you're done. Log on to gerolde and run the db scripts as usual. MODIFY A PACKAGE WITHOUT CHANGING trunk/ ---------------------------------------- When a package is in testing, the files in trunk pretty much reflect the stuff in testing. What if you want to update the package in core/extra without changing trunk/testing? Just $ cd repos/extra-i686 edit the files, build and so on. However, devtools won't help you now. You have to upload the file yourself using scp and $ svn commit -m "some commit message" Then you can run the db script. ADD A NEW PACKAGE ----------------- You don't want to check out the whole tree, it's huge. Therefore, you just $ svn co -N svn+ssh://archlinux.org/home/svn-packages somedir $ cd somedir $ mkdir -p pkgname/{trunk,repos} $ svn add pkgname/{,trunk,repos} $ cd pkgname/ $ svn commit -m "Add package pkgname" $ cd trunk/ Now add all the files like the PKGBUILD, don't forget to run $ svn add PKGUILD pkgname.install somefile1 somefile2 Now proceed like above. ALTERNATIVE WAY OF CHECKING OUT DELETING A PACKAGE ------------------------------- I didn't test this, but Aaron tells me it'll work. Instead of using archco, you can do a non-recursive checkout like above: $ svn co -N svn+ssh://archlinux.org/home/svn-packages somedir $ cd somedir Now you can checkout single packages, too: $ svn up pkgname Or delete a package $ svn up pkgname $ svn rm pkgname Or add one like I showed above. This will make the archco script obsolete, maybe you like this method better. MAKING IT FASTER ---------------- extrapkg establishes many ssh connections during your work. This always takes a few seconds and thus slows you down. You may even have to type your password many times. This will help: Add the following lines to ~/.ssh/config: ControlPath /home/youruser/.ssh/master-%h-%p-%r Host gerolde HostName archlinux.org Host cvs.archlinux.org HostName archlinux.org Host svn.archlinux.org HostName archlinux.org The last few lines are aliases, so the hosts gerolde, archlinux.org, cvs.archlinux.org and svn.archlinux.org are treated as if they all were "archlinux.org". Now establish one connection with $ ssh -M archlinux.org The -M option creates a socket in the ControlPath and other ssh clients connecting to the same host and port will use this socket instead, and be tunneled through the master connection. Thus, you never have to enter your password again until you close the connection. Even better, establishing a connection (like scp, svn etc do) is much faster.

1 0

[arch-dev-public] please help rebuilding (gnome) for i686
by Andreas Radke 20 Apr '08

20 Apr '08

please someone with some time left rebuild packages for i686. difflist is getting a bit too long these days: http://dev.archlinux.org/~andyrtr/pkg_diff.html some of my packages depend on new gnome stuff. the build order should be in our public wiki and Jan also uses version related dependencies. so it shouldn't be that hard. thanks Andy

1 0

[arch-dev-public] Added b43-fwcutter to core
by Thomas Bächler 20 Apr '08

20 Apr '08

The bcm43xx driver is being replaced with b43 and b43legacy. bcm43xx will be removed in 2.6.26. Thus, I added b43-fwcutter to core. This replaces bcm43xx-fwcutter, which should be deleted when 2.6.26 is out.

1 0

[arch-dev-public] [signoff] ntfs-3g 1.2412-1
by Thomas Bächler 19 Apr '08

19 Apr '08

The usual.

1 0

[arch-dev-public] [signoff] lvm2 2.02.35-1
by Thomas Bächler 19 Apr '08

19 Apr '08

Yet another minor update.

1 0

[arch-dev-public] New extra/unstable package: compat-wireless
by Thomas Bächler 19 Apr '08

19 Apr '08

I just built the compat-wireless package and I must say it's a cool thing. It's a snapshot of the current wireless-testing tree with extra patches added for compatibility to older kernels. The modules are in the /lib/modules/VERSION/updates directory, which is somehow magically preferred over the rest, and thus there is no conflict with our stock modules. I'd like to add this package to extra or unstable (preferably extra, as the drivers may indeed be more stable than the stock ones). Thomas - happy to have his wireless LED again.

4 5

[arch-dev-public] ABS and community
by Travis Willard 19 Apr '08

19 Apr '08

Hey, Can I get someone with super-powers on gerolde to update abs to 2.1-1, and add the following line to /etc/cron.daily/update-abs.sh after the existing /usr/bin/svn2abs line? /usr/bin/community2abs /home/abs/rsync /home/cvs-community This will ensure people can also get community through ABS Thanks! -- Travis

2 1

[arch-dev-public] SVN $Id$ tags
by Aaron Griffin 18 Apr '08

18 Apr '08

Just a note for you all. If you want svn to modify the $Id$ tags the way SVN does, you need to enable it for the PKGBUILD. This is done like so: svn propset svn:keywords Id <filename> The available keywords for replacement are: LastChangedDate LastChangedRevision LastChangedBy HeadURL Id Please keep in mind the above is a "set" operation, not an "append" operation - if I later set svn:keywords to HeadURL, it overwrites the previous setting. You can do the following to set multiple keywords: svn propset svn:keywords "Id HeadURL LastChangedBy" <filename> If you guys like, we can run this once across the whole repo for all PKGBUILDs. find . -name PKGBUILD -exec svn propset svn:keywords Id {} \; What do you think?

3 3

[arch-dev-public] The move to SVN
by Aaron Griffin 18 Apr '08

18 Apr '08

For the rest of the week, I am going to be concentrating on one big thing: moving our repos to SVN. Why is this important, after all the stuff I've been griping about, you may ask? Because it's a 'blocker'. It's the most low-level building block for a lot of the other changes I'd like to see done regarding our repository management So, here's the plan. I need one day where we make the switch over. It will be rocky and annoying for that day, but it is also a break for all of you Here are the steps that this will involve: Set all the cvs repos to RO, so that we don't have any accidents Convert everything to svn Make the necessary structure changes Make devtools changes * Make abs changes * Make db-scripts changes * Make changes to community ** * Can be done before hand, without a new package release ** Paul and Simo, in need your input regarding doing this for community as well. I have not looked at the scripts in a long time, but how much effort do you think this would take? Here is the end result, repo created ages ago by Jason[1]: http://projects.xennet.org/svnarch/ It is a tad large, but SVN is nice in that it allows us to only check out subdirs we want, so you can checkout just your packages (see jason's archco tool[1]) We *will* lose history during this transition. It's something I'm willing to live with, as this is not code history. We will still archive CVS for posterity. So, what do I need from you? Nothing. I'm making this easy in that I will do all the work. I just need one thing: give me a day when it is best. When you all want to take a mini-vacation and do no packaging at all. If no one has a good day for this, I will probably do it on Thursday or Friday. Thanks, Aaron 1: http://archlinux.org/pipermail/arch-dev-public/2007-October/002308.html

17 93