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

[arch-dev-public] inkscape rebuilds ?
by Tobias Kieslich 23 Apr '08

23 Apr '08

Hi guys, what is the state of the inkscape package? It's my package but I kinda lost track in the big move. SVN history says it gots rebuild for poppler which is in extra and later against imagemagick which is in testing. How ever none of those ever made it to extra, henci it is broken. Any ideas? -Tobias

3 3

[arch-dev-public] [signoff] texinfo 4.12-1
by Eric Belanger 23 Apr '08

23 Apr '08

In testing for both arches. changes: - minor upstream update - updated license: GPL -> GPL3 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

[arch-dev-public] The /lib/modules/$(uname -r)/updates directory - and how great it is
by Thomas Bächler 22 Apr '08

22 Apr '08

The module-init-tools have had this feature for a while and I just wanted to tell you about how we can use it: The modules contained in the updates/ subdirectory in your module directory are always preferred over any other modules. Thus, you can put updated modules into it which supercede the ones installed by our kernel. This is great, I'll just give some examples: - The compat-wireless package uses it That's how I know about it. compat-wireless puts a complete new mac80211 tree with drivers into updates/. This means it is easy to get updated wireless drivers without conflicting with the stock kernel and without having to rebuild the whole kernel. - ALSA updates ALSA has been known to be a bitch. Sometimes the drivers in the stock Linux kernel are out of date and an updated driver will help. Now, we could provide a PKGBUILD via AUR which installs the latest ALSA drivers to updates/ - this would give a user the possibility to use an updated alsa without having to rebuild the kernel, conflict with the kernel or having to delete files and confuse pacman. - Random patches to drivers It has happened that users wanted a particular feature enabled or changed in a particular driver. There is the phc undervolt patch and there is some toshiba-bluetooth patch still in our kernel. Now I don't like forcing patched drivers on people who don't need it, and generally, our community likes vanilla kernels more. With the updates/ directory it is possible to provide these special cases via PKGBUILDs/AUR - provided the change is only in the module(s) in question, one could patch it, build it and put it into the updates/ directory. Without having a patched kernel, the users could be happy - again, no kernel rebuilding or hacky conflicting. (In the above cases, only the acpi-cpufreq resp. the toshiba-acpi modules are modified ... nothing is modified in the kernel itself). I already plan to maintain compat-wireless as a binary package. I will also put an alsa-driver-updates package into the AUR. And I will try to package the modified toshiba-acpi module so I can drop the patch from the kernel (I will also put this in AUR then). I hope this will make life easier for us and for many users in our community - it is a much cleaner thing than patching the kernel all the time.

3 2

[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