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

[arch-dev-public] libarchive 3.1.1 upgrade
by Dave Reisner 04 Feb '13

04 Feb '13

I noticed last week that we're a bit out of date on libarchive, and started looking into why. There's 3 things that immediately came up: 1) There's a soname bump. The list isn't huge though (15 packages) 2) bsdtar's mtree file generation explodes. This is relevant for pacman 4.1. I've already filed a bug and proposed a patch[1]. 3) There's a test suite failure in bsdcpio for lzo extraction. This turned out to be a missing dep. libarchive now handles lzo via lzo2 so we'd need to add it to depends. No big deal as lzo2 is already in [core]. Other than this, I've been running 3.1.1 without problems for roughly a week now (logs say since 1/28) and haven't had any other issues. Mostly aiming this at Dan and Allan, but once we have an upstream fix for the legit bug here, is anyone opposed to doing this upgrade/rebuild? I know we want to release pacman 4.1 soon, and it'd be probably be good not to have these overlap too much. d [1] http://code.google.com/p/libarchive/issues/detail?id=301

3 4

[arch-dev-public] Signoff report for [testing]
by Arch Website Notification 03 Feb '13

03 Feb '13

=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 9 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 14 fully signed off packages * 17 packages missing signoffs * 2 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == New packages in [testing] in last 24 hours (9 total) == * licenses-20130203-1 (any) * btrfs-progs-0.20rc1.1-1 (i686) * libksba-1.2.0-3 (i686) * ncurses-5.9-4 (i686) * perl-5.16.2-3 (i686) * btrfs-progs-0.20rc1.1-1 (x86_64) * libksba-1.2.0-3 (x86_64) * ncurses-5.9-4 (x86_64) * perl-5.16.2-3 (x86_64) == Incomplete signoffs for [core] (9 total) == * btrfs-progs-0.20rc1.1-1 (i686) 0/2 signoffs * libksba-1.2.0-3 (i686) 0/2 signoffs * ncurses-5.9-4 (i686) 0/2 signoffs * perl-5.16.2-3 (i686) 1/2 signoffs * syslinux-5.01-1 (i686) 1/2 signoffs * btrfs-progs-0.20rc1.1-1 (x86_64) 0/2 signoffs * libksba-1.2.0-3 (x86_64) 0/2 signoffs * ncurses-5.9-4 (x86_64) 0/2 signoffs * perl-5.16.2-3 (x86_64) 0/2 signoffs == Incomplete signoffs for [extra] (8 total) == * hwdetect-2013.02-1 (any) 0/2 signoffs * seabios-1.7.2-1 (any) 0/2 signoffs * qemu-1.3.1-2 (i686) 0/2 signoffs * wpa_supplicant_gui-2.0-1 (i686) 0/2 signoffs * xf86-video-intel-2.21.0-1 (i686) 0/2 signoffs * qemu-1.3.1-2 (x86_64) 0/2 signoffs * wpa_supplicant_gui-2.0-1 (x86_64) 0/2 signoffs * xf86-video-intel-2.21.0-1 (x86_64) 0/2 signoffs == Completed signoffs (14 total) == * licenses-20130203-1 (any) * e2fsprogs-1.42.7-1 (i686) * iproute2-3.7.0-1 (i686) * iw-3.8-1 (i686) * lvm2-2.02.98-3 (i686) * openvpn-2.3.0-1 (i686) * wpa_supplicant-2.0-1 (i686) * e2fsprogs-1.42.7-1 (x86_64) * iproute2-3.7.0-1 (x86_64) * iw-3.8-1 (x86_64) * lvm2-2.02.98-3 (x86_64) * openvpn-2.3.0-1 (x86_64) * syslinux-5.01-1 (x86_64) * wpa_supplicant-2.0-1 (x86_64) == All packages in [testing] for more than 14 days (2 total) == * lvm2-2.02.98-3 (i686), since 2012-11-03 * lvm2-2.02.98-3 (x86_64), since 2012-11-03 == Top five in signoffs in last 24 hours == 1. allan - 4 signoffs 2. dan - 1 signoffs

1 0

[arch-dev-public] Signoff report for [testing]
by Arch Website Notification 02 Feb '13

02 Feb '13

=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 7 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 12 fully signed off packages * 11 packages missing signoffs * 2 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == New packages in [testing] in last 24 hours (7 total) == * syslinux-5.01-1 (i686) * syslinux-5.01-1 (x86_64) * hwdetect-2013.02-1 (any) * qemu-1.3.1-2 (i686) * xf86-video-intel-2.21.0-1 (i686) * qemu-1.3.1-2 (x86_64) * xf86-video-intel-2.21.0-1 (x86_64) == Incomplete signoffs for [core] (3 total) == * e2fsprogs-1.42.7-1 (i686) 1/2 signoffs * iproute2-3.7.0-1 (i686) 1/2 signoffs * syslinux-5.01-1 (i686) 1/2 signoffs == Incomplete signoffs for [extra] (8 total) == * hwdetect-2013.02-1 (any) 0/2 signoffs * seabios-1.7.2-1 (any) 0/2 signoffs * qemu-1.3.1-2 (i686) 0/2 signoffs * wpa_supplicant_gui-2.0-1 (i686) 0/2 signoffs * xf86-video-intel-2.21.0-1 (i686) 0/2 signoffs * qemu-1.3.1-2 (x86_64) 0/2 signoffs * wpa_supplicant_gui-2.0-1 (x86_64) 0/2 signoffs * xf86-video-intel-2.21.0-1 (x86_64) 0/2 signoffs == Completed signoffs (12 total) == * mkinitcpio-0.13.0-1 (any) * iw-3.8-1 (i686) * lvm2-2.02.98-3 (i686) * openvpn-2.3.0-1 (i686) * wpa_supplicant-2.0-1 (i686) * e2fsprogs-1.42.7-1 (x86_64) * iproute2-3.7.0-1 (x86_64) * iw-3.8-1 (x86_64) * lvm2-2.02.98-3 (x86_64) * openvpn-2.3.0-1 (x86_64) * syslinux-5.01-1 (x86_64) * wpa_supplicant-2.0-1 (x86_64) == All packages in [testing] for more than 14 days (2 total) == * lvm2-2.02.98-3 (i686), since 2012-11-03 * lvm2-2.02.98-3 (x86_64), since 2012-11-03 == Top five in signoffs in last 24 hours == 1. foutrelis - 9 signoffs 2. eric - 4 signoffs

1 0

[arch-dev-public] sysvinit vs. sysvinit-compat
by Tobias Powalowski 01 Feb '13

01 Feb '13

Hi guys, Those packages have conflicts on each other, sysvinit-compat is in base group, so shouldn't sysvinit moved to extra? greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

3 2

Re: [arch-dev-public] syslinux update to 5.01
by Tobias Powalowski 01 Feb '13

01 Feb '13

Am 01.02.2013 03:40, schrieb Matthew Gyurgyik: > On 01/31/2013 12:49 PM, Tobias Powalowski wrote: >> Am 31.01.2013 18:43, schrieb Pierre Schmitz: >>> Am 31.01.2013 16:09, schrieb Tobias Powalowski: >>>> Hi, >>>> ok syslinux 5.0 series should come to testing again. >>>> The problem with this release: >>>> You need to copy all .c32 modules to your /boot/syslinux path. >>>> - Those who used our shipped install script, will end up in a none >>>> menu >>>> based syslinux shell. >>> As long as we ship this install script we should maintain it. So this >>> script needs to be altered to copy the needed files. >>> >> The script has already been modified to at least to syslinux shell. >> If it should do more, Pyther needs to change it. >> >> greetings >> tpowa >> > > I'll copy and paste from my previous message (Re: [arch-dev-public] > syslinux 5.00 in [testing]). > > ----- > > Below you will find the links to the patches for the > syslinux-install_update script, PKGBUILD, and syslinux.cfg > > During an install, the syslinux-install_update script will copy all > .c32 modules to /boot/syslinux. This is recommended by upstream [1]. > The size cost is minimal, 996K. For updates, I added an array called > core_modules. During an update, we only copy modules that already > exist in /boot/syslinux. However, if any core_module does not exist in > /boot/syslinux it will be copied/symlinked. > > With these modifications, when a user upgrades from 4.06 -> 5.00, > ldlinux.c32 will be copied/symlinked to /boot/syslinux as it is > core_module. Other modules such as libutil_com.c32 and libcom32.c32 > will not be copied/linked. > > On boot, if a menu is being used, the menu will fail to load (missing > depends: libutil_com.c32, etc...). However, the user will be given a > syslinux shell they can boot by entering a label that corresponds to a > defined label in syslinux.cfg. > > A post_install message or a news item suggesting users to copy / > symlink all modules to /boot/syslinux would be ideal. Users who miss > this message, will still be able to boot, but instead of the menu > loading, they will be dropped to a syslinux shell (as explained above). > > cp /usr/lib/syslinux/*.c32 /boot/syslinux (/ and /boot on seperate fs) > > or > > ln -s /usr/lib/syslinux/*.c32 /boot/syslinux (/ and /boot on same fs) > > In my opinion, we shouldn't add new modules during an update to > /boot/syslinux unless, without the module, the system becomes > unbootable. The rational here being - the user knows best. > > Lastly, since com modules are no longer supported and no one has > ported poweroff.com, I have removed the poweroff section from the > syslinux.cfg [2]. > > Patches: > http://pyther.net/a/syslinux-5.00-patches-v1/PKGBUILD.diff > http://pyther.net/a/syslinux-5.00-patches-v1/syslinux-install_update.patch > > http://pyther.net/a/syslinux-5.00-patches-v1/syslinux.cfg.patch > > [1] "In general, unless you have a reason *not* to install all the .c32 > files, it is probably a good idea." - hpa > > [2] #syslinux @freenode: > pyther : Hello. Is there a poweroff module for syslinux 5? > Ady2 : pyther: no. all .com modules are not supported in 5.00. someone > needs to create a new poweroff.c32 compatible with 5.00. > > > Regards, > Matthew Gyurgyik > I already implemented your patches, the problem is that it leaves people with a menuless system. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

1 0

[arch-dev-public] Signoff report for [testing]
by Arch Website Notification 01 Feb '13

01 Feb '13

=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 5 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 7 fully signed off packages * 19 packages missing signoffs * 2 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == New packages in [testing] in last 24 hours (5 total) == * mkinitcpio-0.13.0-1 (any) * cairo-1.12.12-1 (i686) * qemu-1.3.1-1 (i686) * cairo-1.12.12-1 (x86_64) * qemu-1.3.1-1 (x86_64) == Incomplete signoffs for [core] (6 total) == * mkinitcpio-0.13.0-1 (any) 1/2 signoffs * e2fsprogs-1.42.7-1 (i686) 1/2 signoffs * iproute2-3.7.0-1 (i686) 0/2 signoffs * iw-3.8-1 (i686) 1/2 signoffs * iproute2-3.7.0-1 (x86_64) 1/2 signoffs * iw-3.8-1 (x86_64) 1/2 signoffs == Incomplete signoffs for [extra] (13 total) == * seabios-1.7.2-1 (any) 0/2 signoffs * cairo-1.12.12-1 (i686) 0/2 signoffs * ntfs-3g_ntfsprogs-2013.1.13-1 (i686) 0/2 signoffs * qemu-1.3.1-1 (i686) 0/2 signoffs * testdisk-6.13-4 (i686) 0/2 signoffs * wpa_supplicant_gui-2.0-1 (i686) 0/2 signoffs * xf86-video-ati-1:7.1.0-1 (i686) 0/2 signoffs * cairo-1.12.12-1 (x86_64) 0/2 signoffs * ntfs-3g_ntfsprogs-2013.1.13-1 (x86_64) 0/2 signoffs * qemu-1.3.1-1 (x86_64) 0/2 signoffs * testdisk-6.13-4 (x86_64) 1/2 signoffs * wpa_supplicant_gui-2.0-1 (x86_64) 0/2 signoffs * xf86-video-ati-1:7.1.0-1 (x86_64) 1/2 signoffs == Completed signoffs (7 total) == * lvm2-2.02.98-3 (i686) * openvpn-2.3.0-1 (i686) * wpa_supplicant-2.0-1 (i686) * e2fsprogs-1.42.7-1 (x86_64) * lvm2-2.02.98-3 (x86_64) * openvpn-2.3.0-1 (x86_64) * wpa_supplicant-2.0-1 (x86_64) == All packages in [testing] for more than 14 days (2 total) == * lvm2-2.02.98-3 (i686), since 2012-11-03 * lvm2-2.02.98-3 (x86_64), since 2012-11-03 == Top five in signoffs in last 24 hours == 1. foutrelis - 2 signoffs 2. fyan - 1 signoffs 3. pierre - 1 signoffs

1 0