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

[arch-dev-public] [signoff] udev/klibc-udev 139-1
by Thomas Bächler 09 Mar '09

09 Mar '09

Another upstream update. This has mostly been done by tpowa, I only fixed and refined the /lib/udev/devices/ handling. The major change is that the device nodes /dev/loop*, /dev/net/tun, /dev/ppp and /dev/fuse now always exist, even if the modules are not loaded. That will bring back some nice autoloading behaviour that was there with static /dev filesystems and was lost when udev was introduced (it should also reduce the number of "arch does not support loop mounts" complaints). The latest initscripts package is also needed for this to work completely. Package is in testing for both architectures, tested on x86_64, please sign off.

3 3

[arch-dev-public] fakeroot sysv ipc bugs
by Xavier 09 Mar '09

09 Mar '09

On Mon, Mar 9, 2009 at 6:44 PM, Tobias Powalowski <t.powa(a)gmx.de> wrote: > Am Montag 09 März 2009 schrieb Andreas Radke: >> Am Mon, 09 Mar 2009 10:00:16 +1000 >> >> schrieb Allan McRae <allan(a)archlinux.org>: >> > Dan McGee wrote: >> > > On Sun, Mar 8, 2009 at 4:44 AM, Tobias Powalowski <t.powa(a)gmx.de> >> > > >> > > wrote: >> > >> Am Sonntag 08 März 2009 schrieb Andreas Radke: >> > >>> This is a minor update to 1.12.2 - the major change I've done is >> > >>> the switch to --with-ipc=tcp communication way that should solve >> > >>> some issues that have come up with recent kde builds. please test >> > >>> if you can still build all your other stuff with it. >> > >>> >> > >>> >> > >>> Attention: Please also take care off all packages that install >> > >>> files with setuid bit set. Take a look at >> > >>> http://bugs.archlinux.org/task/13444 ! >> > >>> >> > >>> I could not track down where the issue is and the upstream Debian >> > >>> developer can't reproduce it while Tpowa and some other could. >> > >>> Only x86_64 is affected and sometimes files with setuid set don't >> > >>> get that permission when the pkg gets installed. >> > >>> >> > >>> -Andy >> > >>> >> > >>> >> > >>> upstream changelog: >> > >>> >> > >>> fakeroot (1.12.2) unstable; urgency=low >> > >>> >> > >>> * Replace and (hopefully) fix broken alpha stat version hack in >> > >>> fts_read. >> > >>> >> > >>> -- Clint Adams <schizo(a)debian.org> Sun, 01 Mar 2009 15:17:31 >> > >>> -0500 >> > >> >> > >> no signoff, i can'T build kernel and syslog-ng anymore, >> > >> somehow it creates zombie processes on my system, downgrading to >> > >> core fakeroot solved the issue. >> > > >> > > Completely broken. I can't even make it through a build without >> > > fakeroot hanging and having to kill -9 the makepkg process. >> > >> > Me too. I guess it is best to wait for the next pacman release to >> > fix this as building can then be done outside the fakeroot. >> > >> > Allan >> >> I reverted back to use sysv ipc and added the README file + install msg >> about sysv/tcp usage. >> >> Please signoff -2 release. >> >> -Andy > signoff works again to compile things :D > greetings > tpowa > Just out of curiosity, none of the devs are affected by the issues with fakeroot sysv ipc, as described here : http://bugs.archlinux.org/task/13375 ?

2 1

[arch-dev-public] Dbus on archlinux and permissions
by Jan de Groot 09 Mar '09

09 Mar '09

I'm planning to update dbus to the latest release. Reading the releasenotes, I found this: Due to a security issue (CVE-2008-4311) for which a large number of system services need fixes, the dbus 1.2 stable branch has been split into two streams. The "1.2.4Xpermissive" branch originates from 1.2.4, and maintains the unintended permissive default for messages. Releases 1.2.6 and later have a default deny. It is intended that the permissive branch only be used temporarily by vendors. For more information, see this mail: http://lists.freedesktop.org/archives/dbus/2008-December/010769.html I would like to package the 1.2.4.4permissive release now. As soon as it's moved into core, I would like to add the non-permissive version to testing and see what breaks. Doing so, we can close down this security leak in dbus and have all affected services fixed.

2 2

[arch-dev-public] [signoff] kernel26 2.6.28.7-2
by Tobias Powalowski 09 Mar '09

09 Mar '09

Hi guys, new kernel adresses the following things: - changes for better customizing the default kernel included http://bugs.archlinux.org/task/12384 --> firmware needed to be split off the package. It is now called kernel26-firmware - config features added: http://bugs.archlinux.org/task/13128 http://bugs.archlinux.org/task/12584 bug fixes: - http://bugs.archlinux.org/task/12826 please signoff for both arches. I haven't had issues with nvidia driver here, but please report issues if binary modules break, thanks. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

4 6

[arch-dev-public] [signoff] device-mapper-1.02.31-1 & lvm2-2.02.45-1
by Eric Bélanger 09 Mar '09

09 Mar '09

Hi, device-mapper-1.02.31-1 and lvm2-2.02.45-1 are now in testing for both arches. It's a minor upstream update. Please signoff. As few devs use this (I think I'm the only one using lvm on i686), signoff from users would be appreciated. Eric

2 1

[arch-dev-public] udev changes - and the comeback of a long lost feature
by Thomas Bächler 08 Mar '09

08 Mar '09

tpowa did some work today updating udev to 139, cleaning up the rules and fixing some small bugs. With it comes the implementation of a recommendation of the udev team: We now have a directory /lib/udev/devices/ which contains a number of static devices nodes which are always present. A udev rule also makes sure that none of these devices is deleted even if udev normally would do so (the stock udev rule for that is broken, but I fixed it). This simplifies our rc.sysinit a bit: http://projects.archlinux.org/?p=initscripts.git;a=commitdiff;h=623e3fac060… In that context, I thought of an old feature: "module autoloading" as Linux 2.4 understood it: Imagine you have a static /dev, and you try to open a device: 1) /dev/XYZ is a block/char device with major X and minor Y 2) the kernel looks it up, but doesn't find it 3) the kernel issues "modprobe block-major-X-Y" or "modprobe char-major-X-Y" 4) the kernel looks up the device again, it can now find it Note that step 1 requires that /dev/XYZ exists! This feature completely broke with the introduction of udev. This feature is obsolete for most devices, but there are those devices that are not bound to physical hardware - best examples here are tun and loop. I am going to add the loop and tun (any maybe fuse) devices to the static device list that we now support. That means that you can use loop mounts again without running "modprobe loop" manually, the module will be loaded as soon as you access /dev/loopX. Same goes for /dev/net/tun or /dev/fuse. This basically works with all modules that have a block-major-X-* or char-major-X-* alias, so if you think of any more modules that do this, we could add them too.

2 1

[arch-dev-public] [signoff] tar 1.22-1
by Andreas Radke 08 Mar '09

08 Mar '09

new version that brings xz-support. please signoff. -Andy version 1.22 - Sergey Poznyakoff, 2009-03-05 * Support for xz compression Tar uses xz for compression if one of the following conditions is met: 1. The option --xz or -J (see below) is used. 2. The xz binary is set as compressor using --use-compress-program option. 3. The file name of the archive being created ends in `.xz' and auto-compress option (-a) is used. Xz is used for decompression if one of the following conditions is met: 1. The option --xz or -J is used. 2. The xz binary is set as compressor using --use-compress-program option. 3. The file is recognized as xz compressed stream data. * Short option -J reassigned as a short equivalent of --xz * New option -I The -I option is assigned as a short equivalent for --use-compress-program. * The --no-recursive option works in incremental mode.

2 1

[arch-dev-public] Integrity Check i686 06-03-2009
by repomaint＠archlinux.org 06 Mar '09

06 Mar '09

====================================== = Integrity Check i686 of core,extra = ====================================== Performing integrity checks... ==> parsing pkgbuilds ==> checking mismatches ==> checking archs ==> checking dependencies ==> checking makedepends ==> checking for circular dependencies Missing Dependencies ---------------------- archboot --> 'netkit-telnet>=0.17-8' archboot --> 'wlan-ng26>=0.2.9-2' archboot --> 'atl2>=2.0.5-2' Missing Makedepends --------------------- crda --> 'python-m2crypto' wpa_supplicant --> 'kernel26<2.6.28' gnome-speech --> 'espeak' Repo Hierarchy for Makedepends -------------------------------- core/sqlite3 depends on extra/tcl core/iputils depends on extra/opensp core/iputils depends on extra/libxslt core/iputils depends on extra/docbook-xsl core/madwifi-utils depends on extra/sharutils core/e2fsprogs depends on extra/bc core/ca-certificates depends on extra/ruby core/madwifi depends on extra/sharutils Circular Dependencies ----------------------- gcc-gcj>eclipse-ecj>gcc-gcj Summary --------- Missing PKGBUILDs: 0 Invalid PKGBUILDs: 0 Mismatching PKGBUILD names: 0 Duplicate PKGBUILDs: 0 Invalid archs: 0 Missing (make)dependencies: 6 Repo hierarchy problems: 8 Circular dependencies: 1

1 0

[arch-dev-public] new syslog-ng 3.x opinions?
by Tobias Powalowski 06 Mar '09

06 Mar '09

Hi guys while looking at those 2 bugs, i just bumped to new syslog-ng 3.x series. http://bugs.archlinux.org/task/6980 http://bugs.archlinux.org/task/10776 Changes: - adopted new syntax to config file - disable stats logging by default, it just floods everything with useless stats. Main issue: The syntax of config slightly changed and all users with modified syslog-ng files need to manually move in the changes from .pacnew file. Aaron are you fine with bumping it? Do we need a install message here? greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

2 1

[arch-dev-public] [signoff] dash 0.5.5.1-1 in testing repo
by Eric Bélanger 06 Mar '09

06 Mar '09

Hi, I just noticed that there is a dash 0.5.5.1-1 package in testing. I couldn't find a signoff thread so i guess it was forgotten. Anyway, I've noticed that the man page isn't gzipped. Dan: Can you fix that so we can start signoffs? Thanks Eric

1 0