- Arch-general - lists.archlinux.org

[arch-general] xdelta3 not updated for i686
by Karol Blazewicz 13 Jul '13

13 Jul '13

https://www.archlinux.org/packages/differences/ says that xdelta3 has not been updated for 32-bit - why? https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packag… https://www.archlinux.org/packages/community/i686/xdelta3/ BTW, if Allan is not the maintainer anymore, the PKGBUILD should be updated to reflect this: https://projects.archlinux.org/svntogit/community.git/plain/trunk/PKGBUILD?…

2 3

[arch-general] gcc 4.8 breaking libdrm for me
by Andreas Radke 13 Jul '13

13 Jul '13

This is just a heads up notice. I've found gcc 4.8 breaking libdrm on my nouveau nv44 device. When compiled with gcc 4.8 I'm faced with random nouveau related error messages in dmesg. Using new google maps quickly leads to Xorg hanging and finally to Xorg freezing or even crashing. I've seen other Arch people also claiming about random X crashes. Recompiling libdrm with -O0 or other new optimizaions disabled didn't solve it for me so far. But recompiling with a local gcc 4.7.3 makes it stable again. I'm asking for help in tracking this down. We need to find out if a certain part of libdrm has broken code that needs to be fixed. Please everybody with random Xorg crashes try to downgrade to libdrm 2.4.43 (the last one that was built with gcc 4.7) and post your gfx card. And this could also be a gcc 4.8 bug or regression. I've seen almost the same behavior with kernel xfs file system code leading to fs corruption under heavy load: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57436 Then we need to compare assembler code created by gcc 4.7 vs. 4.8. Any suggestion and help is welcome. -Andy

2 2

Re: [arch-general] does using kms mean that you're stick to a framebuffer with specific resolution that you can't change?
by Jan Alexander Steffens 13 Jul '13

13 Jul '13

On Sat, Jul 13, 2013 at 7:19 AM, Xeslaro <bfsc.yb(a)gmail.com> wrote: > the maximum resolution of my laptop is 1366x768, that's also the > framebuffer size with kms enabled. the problem is when i attach a > monitor with resolution 1920x1080 to it, the video output is at the > top-left corner of the monitor. and i found myself unable to change > the framebuffer size, appending video= option to the kernel command > line doesn't take any effect. so, i wonder is there anyway to get a > framebuffer with resolution 1920x1080 so i can benefit from the big > monitor while still with kms enabled? > > kernel version : 3.10.0+ > graphic card : intel hd4000 AFAIK this is not possible, as for VTs there is only one framebuffer mirrored to all monitors. Enabling framebuffers per monitor (fbpercrtc) would just result in the VTs using the boot monitor only. Use X.

2 1

[arch-general] Texlive 2013 packages releases to [testing]
by Rémy Oudompheng 12 Jul '13

12 Jul '13

Hello, I have pushed TeXLive 2013 packages to [testing]. The main difference with the 2012 packages is that /etc/texmf files are now in texlive-core rather than texlive-bin. The texlive-bin package now contains almost only binaries, and texlive-core contains all basic data files including the ones in /etc/texmf. Feel free to report any issues you encounter. If you have an existing installation, the upgrade might install new versions of /etc/texmf/ files as *.pacnew. It is unlikely that things work properly if you don't handle the pacnew files unless you realy know what you are doing. If pacnew files appear (notably texmf.cnf and fmtutil.cnf), and the installation reports a failure in regenerating formats (which you will know by not being able to use an engine), you will need to handle the pacnew files, and run "fmtutil-sys --all" by hand. If this situation reaches a high level of absurdity, and if possible considering pacman's behaviour, new packages not behaving like this might be built later before going to [extra]. Regards, Rémy.

4 9

[arch-general] Apache 2.4 revisited
by Armin K. 11 Jul '13

11 Jul '13

Hello, I've wondered why no one upgraded Apache to 2.4 after being available for so long. Then I stumbled upon an answer on this list where it has been said that 2.4 breaks too many packages [1]. I've taken some time to verify what does it break, and fixed all packages from [extra] and [community] which had direct dependency on the "apache" package (mod_whatever ones). The mod_fcgid, mod_wsgi2 and mod_wsgi just need simple rebuilds against newer versions. PHP case was somehow strange. I had to modify some configure switches. Without --disable-cgi I'd get undefined references at build time and without --with-apsx=/usr/bin/apsx I'd get undefined references at run time. For other ones, I've found patches online and assembled them for direct applying in Archlinux svn (I used svn add and svn diff) In case someone is interested, patches can be found at [2]. It's free hosting, so it might "suck" sometimes. I've tested the packages against apache24 package from AUR. By tested, I mean compiled, loaded into httpd and checked that httpd doesn't fail to start. As a side note, apache24 uses event_mpm by default, but you might need to change to prefork one to use PHP module. Also, with apache 2.4 you can use php-fpm via mod_proxy as described at [3] As for the perl module, I had to use svn checkout of the httpd24 branch. Patch was getting way to big to ship in package. Regards [1] https://mailman.archlinux.org/pipermail/arch-general/2012-October/031777.ht… [2] http://blackprince.net63.net/apache24/ [3] https://wiki.apache.org/httpd/PHP-FPM

3 4

[arch-general] Question regarding virt-manager-tui in ArchLinux
by An Nguyen 08 Jul '13

08 Jul '13

Hello, I would like to know what happened to virt-manager-tui in Arch. I searched but couldn't find any information about whether it was dropped or moved. By virt-manager-tui, I mean the Text User Interface, ncurses based of Virt-Manager. Please let me know. Regards. An. -- Nguyễn Châu An || An NGUYEN Linux Technician & FOSS Advocate ------- OpenPGP KeyID 2048R/8F77A48C Key Fingerprint 7652 B403 749F F173 227D 4865 FB71 EC95 8F77 A48C

2 1

[arch-general] syslinux 6.01-1 issues
by Karol Blazewicz 06 Jul '13

06 Jul '13

I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a 32-bit system. After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in /boot/syslinux didn't get updated and still point to /usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32 -> /usr/lib/syslinux/menu.c32 which prevents the syslinux menu from appearing on boot (modules not found). Running '# /usr/bin/syslinux-install_update -i -a -m' doesn't help. Should I remove all the symlinks from /boot/syslinux and only copy the needed files back? I didn't install syslinux manually so i don't know why should I have to do this. Did I miss / misunderstand something?

4 8

[arch-general] patch for syslinux install script
by Matthew Gyurgyik 06 Jul '13

06 Jul '13

There is a slight change in behaviour. When preforming an update, all c32 modules in /usr/lib/syslinux/bios/ will get copied/symlinked. Previously we only updated/copied modules that were already in /boot/syslinux. Patches can also be found here: http://pyther.net/archlinux/syslinux/6/20130706/ Matthew Gyurgyik PKGBUILD: --- /tmp/syslinux/PKGBUILD 2013-07-06 08:55:21.000000000 -0400 +++ syslinux/PKGBUILD 2013-07-06 07:45:18.811510802 -0400 @@ -4,7 +4,7 @@ pkgname="syslinux" pkgver="6.01" -pkgrel="2" +pkgrel="3" arch=('x86_64' 'i686') pkgdesc="Collection of boot loaders that boot from FAT, ext2/3/4 and btrfs filesystems, from CDs and via PXE" url="http://syslinux.zytor.com/" @@ -29,62 +29,62 @@ source=("https://www.kernel.org/pub/linu sha1sums=('d7bc1b188677f77ac2d7060d25491dc29877a9c4' 'b0f174bcc0386fdf699e03d0090e3ac841098010' - 'b1d915045fe3094f5359df043c53e73a4dc32745') + '2a7c1abe9816f6f702f425499a10582eebf94632') _build_syslinux_bios() { - + rm -rf "${srcdir}/${pkgname}-${pkgver}-bios/" || true cp -r "${srcdir}/${pkgname}-${pkgver}" "${srcdir}/${pkgname}-${pkgver}-bios" cd "${srcdir}/${pkgname}-${pkgver}-bios/" - + ## Do not try to build syslinux with our default LDFLAGS, it will fail unset LDFLAGS - + make PYTHON="python2" bios make PYTHON="python2" bios installer - + } _build_syslinux_efi64() { - + rm -rf "${srcdir}/${pkgname}-${pkgver}-efi64/" || true cp -r "${srcdir}/${pkgname}-${pkgver}" "${srcdir}/${pkgname}-${pkgver}-efi64" cd "${srcdir}/${pkgname}-${pkgver}-efi64/" - + ## Unset all compiler FLAGS for efi64 build unset CFLAGS unset CPPFLAGS unset CXXFLAGS unset LDFLAGS unset MAKEFLAGS - + make PYTHON="python2" efi64 make PYTHON="python2" efi64 installer - + } _build_syslinux_efi32() { - + rm -rf "${srcdir}/${pkgname}-${pkgver}-efi32/" || true cp -r "${srcdir}/${pkgname}-${pkgver}" "${srcdir}/${pkgname}-${pkgver}-efi32" cd "${srcdir}/${pkgname}-${pkgver}-efi32/" - + ## Unset all compiler FLAGS for efi32 build unset CFLAGS unset CPPFLAGS unset CXXFLAGS unset LDFLAGS unset MAKEFLAGS - + make PYTHON="python2" efi32 make PYTHON="python2" efi32 installer - + } build() { - + cd "${srcdir}/${pkgname}-${pkgver}/" - + ## Do not try to build the Windows or DOS installers and DIAG files sed 's|diag libinstaller dos win32 win64 dosutil txt|libinstaller txt|g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true sed 's|win32/syslinux.exe win64/syslinux64.exe||g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true @@ -92,73 +92,73 @@ build() { sed 's|dos/syslinux.com||g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true sed 's|INSTALLSUBDIRS = com32 utils dosutil|INSTALLSUBDIRS = com32 utils|g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true sed 's|install -m 644 -c $(INSTALL_DIAG) $(INSTALLROOT)$(DIAGDIR)|# install -m 644 -c $(INSTALL_DIAG) $(INSTALLROOT)$(DIAGDIR)|g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true - + ## Fix FHS manpage path sed 's|/usr/man|/usr/share/man|g' -i "${srcdir}/${pkgname}-${pkgver}/mk/syslinux.mk" || true - + ## Build syslinux-efi if [[ "${CARCH}" == "x86_64" ]]; then _build_syslinux_efi64 fi - + if [[ "${CARCH}" == "i686" ]]; then _build_syslinux_efi32 fi - + ## Build syslinux-bios _build_syslinux_bios - + } _package_syslinux_bios() { - + cd "${srcdir}/${pkgname}-${pkgver}-bios/" - + ## Install Syslinux bios make INSTALLROOT="${pkgdir}/" AUXDIR="/usr/lib/syslinux/bios/" bios install - + ## Remove syslinux.exe,syslinux64.exe,syslinux.com and dosutil dir rm "${pkgdir}/usr/lib/syslinux/bios"/syslinux.{com,exe} || true rm "${pkgdir}/usr/lib/syslinux/bios/syslinux64.exe" || true rm -rf "${pkgdir}/usr/lib/syslinux/bios/dosutil/" || true - + ## Remove com32 and diag dirs rm -rf "${pkgdir}/usr/lib/syslinux/bios/diag/" || true rm -rf "${pkgdir}/usr/lib/syslinux/bios/com32/" || true - + ## Move extlinux binary to /usr/bin install -d "${pkgdir}/usr/bin" mv "${pkgdir}/sbin/extlinux" "${pkgdir}/usr/bin/extlinux" rm -rf "${pkgdir}/sbin/" - + ## Install docs install -d "${pkgdir}/usr/share/doc" cp -ar "${srcdir}/${pkgname}-${pkgver}/doc" "${pkgdir}/usr/share/doc/syslinux" - + ## Install the default configuration install -D -m0644 "${srcdir}/syslinux.cfg" "${pkgdir}/boot/syslinux/syslinux.cfg" - + ## Install the installation and update script ## This script is maintained at git://gist.github.com/772138.git ## Script not yet updated for syslinux-efi install -D -m0755 "${srcdir}/syslinux-install_update" "${pkgdir}/usr/bin/syslinux-install_update" - + } package() { - + cd "${srcdir}/${pkgname}-${pkgver}/" - + if [[ "${CARCH}" == "x86_64" ]]; then cd "${srcdir}/${pkgname}-${pkgver}-efi64/" make INSTALLROOT="${pkgdir}/" AUXDIR="/usr/lib/syslinux/" efi64 install fi - + if [[ "${CARCH}" == "i686" ]]; then cd "${srcdir}/${pkgname}-${pkgver}-efi32/" make INSTALLROOT="${pkgdir}/" AUXDIR="/usr/lib/syslinux/" efi32 install fi - + _package_syslinux_bios - + } syslinux-install_update: --- /tmp/syslinux/syslinux-install_update 2013-07-06 08:55:11.000000000 -0400 +++ syslinux/syslinux-install_update 2013-07-06 07:42:58.931760621 -0400 @@ -1,7 +1,7 @@ #!/bin/bash # # Sylinux Installer / Updater Scripts -# Copyright (C) 2011 Matthew Gyurgyik <pyther(a)pyther.net> +# Copyright (C) 2013 Matthew Gyurgyik <pyther(a)pyther.net> # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License @@ -293,13 +293,13 @@ install_mbr() { return 0 } -_install() { +install_modules() { # Copy all com32 files to /boot for file in "${libpath}"/*.c32; do file=${file##*/} # Symlink files if /boot resides on the same partition as root if [[ "$boot" = root ]]; then - ln -s "${libpath#$CHROOT}/$file" "$bootpath/$file" &> /dev/null + ln -sf "${libpath#$CHROOT}/$file" "$bootpath/$file" &> /dev/null elif [[ "$boot" = boot ]]; then cp "$libpath/$file" "$bootpath/$file" fi @@ -313,59 +313,43 @@ _install() { cp "$pciids_file" "$bootpath/pci.ids" &> /dev/null fi fi +} + +_install() { + install_modules if device_is_raid "$bootpart"; then - echo "Detected RAID on /boot - installing Syslinux with --raid" + echo "Detected RAID on /boot" "$extlinux" --install "$bootpath" -r > /dev/null 2>&1 else "$extlinux" --install "$bootpath" > /dev/null 2>&1 fi if (( $? )); then - echo "Syslinux install failed" + echo "syslinux install failed" exit 2 else - echo "Syslinux install successful" + echo "syslinux install successful" fi touch "$CHROOT/$autoupdate_file" } update() { - # Update c32 files in /boot, if /boot is not on same fs - if [[ "$boot" = boot ]]; then - for file in "$bootpath"/*.c32; do - file=${file##*/} - cp "$libpath/$file" "$bootpath/$file" &> /dev/null - done - if [[ -f "$bootpath/pci.ids" ]]; then - cp "$pciids_file" "$bootpath/pci.ids" &> /dev/null - fi - fi - - # Ensure core modules exist and if not install them - for file in "${core_modules[@]}"; do - if [[ ! -f $bootpath/$file ]]; then - if [[ "$boot" = root ]]; then - ln -s "${libpath#$CHROOT}/$file" "$bootpath/$file" &> /dev/null - elif [[ "$boot" = boot ]]; then - cp "$libpath/$file" "$bootpath/$file" - fi - fi - done + install_modules if device_is_raid $bootpart; then - echo "Detected RAID on /boot - installing Syslinux with --raid" + echo "Detected RAID on /boot" "$extlinux" --update "$bootpath" -r &> /dev/null else "$extlinux" --update "$bootpath" &> /dev/null fi if (($?)); then - echo "Syslinux update failed" + echo "syslinux update failed" exit 2 else - echo "Syslinux update successful" + echo "syslinux update successful" fi }

2 1

Re: [arch-general] [arch-dev-public] Bootstrap images for installing Arch from another system
by Romain Labolle 05 Jul '13

05 Jul '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30/06/2013 02:00, Thomas Bächler wrote: > Am 28.06.2013 20:02, schrieb Thomas Bächler: >> Am 22.06.2013 21:19, schrieb Pierre Schmitz: >>>>> I'd say we include this script into the releng scripts >>>>> (either archiso or create a nwe package; atm I use some >>>>> additional script for releasing an ISO image) and upload >>>>> such a tar at the same time as the ISO image. >>>> >>>> I was thinking about including this into >>>> arch-install-scripts, but I am unsure if it really fits in >>>> there. >>> >>> Yes, seems difficult. As I said, I also have other scripts >>> like creating torrents etc. that are used for a realease. Maybe >>> we can create a releng repo/package for these. >> >> Regardless of where the scripts end up, should we publish these >> images with the July ISO? I can write a short README for it. > > Script is here for the moment: > https://github.com/brain0/genbootstrap > Just to point out something: when using arch-chroot, the following command is executed (with $1=/tmp/root.x86_64/): mountpoint -q "$1" || track_mount "$1" "$1" --bind; Since /tmp/root.x86_64/ is not a mountpoint, we got /tmp/root.x86_64/ binded on itself, which override any previous mount points under /tmp/root.x86_64/, especially /tmp/root.x86_64/mnt. So if you install arch that way, you install it on your /tmp, and not on the mounted partition. So you need to either mount your partition after entering the chroot or bind /tmp/root.x86_64/ before mounting it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR1tGBAAoJENjIqLe6T5zr7ccQAJrgXj44s9Tx3zHPLgmJOtBn ZB3cEDB9odujJyRbUiYdNUBplgxpPAnIO4wpZRBSxe298JuVzf10vR4UzEChQ2xN M/WYrFBdzy4DYbuo4akamN1eutA98tF4tbHSvToPa/gxQmEgq6mXBPdhaE8R94+j qg44W0gPmvMkndNDzbDGcFaoggaOi6zJ9T6vWdpD5H0T/2My078MR7nQ1Njtf5Rr W85UjQTAJ/WI1+ziYU/Aor1U15yqtoVRUfzkloGbHErZgQIjrU3rlQTu4Wqh72ZX b2rW3rygJFrGzh1TDYCkFK+0D6fx5ALnA5kdtXdQyv80Mgnql3r0TYoT0DhAEewe Ql4MV29+LNaPZFFxQfsdxf2GxicxJk+RUcBZPrEDTMEvchLFmI5+d6NmtETcj35n Wv5lDuv8fTpaPfsmGQTHpEcRNkoHNNkEt6IzyJLtRoJjgwsf6cwSyNIwzrQQ7QNv Tj4CY7pmWgto2HGP5vO5AhOaI7LXzynPS9EZRJ2Bz2MQtH0tTKX2vUDWWgd3nLHH MCpwLL/1jErrs7sQEiEeHTP9AEGQtevPIEmTL4EA4isey0rzEuuDJQfR0pbFIERK Yob06gnmSUEC/vBIBE4HAUAqga3y/oP788xSaDBndeVcprkBdM+wPIhsDymFtA9M IrEQk7ETVD3HcnDpX52W =SsUr -----END PGP SIGNATURE-----

1 0

[arch-general] reading messages during shutdown
by F. Gr. 05 Jul '13

05 Jul '13

Hi, I've noticed that there are some warning during the halt/reboot process. How can I read these messages?

3 2