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

[arch-dev-public] libdrm / mesa / nouveau
by Andreas Radke 08 Jun '12

08 Jun '12

We run into an ugly situation here. Another libdrm release is out - 2.4.35. And because current stable Mesa release won't compile with nouveau changes in libdrm 2.4.34 I can't bump libdrm. So currently nouveau-dri from stable Mesa release holds back all other graphics drivers. I suggest to go on and bump libdrm, remove ugly libdrm-new/nouveau and disable nouveau-dri in our stable Mesa. And then live without 3d nouveau in our repos until upstream nouveau suckers start to care about distributions or add mesa nouveau git stuff back to our mesa like Fedora often does. But I'd prefer to point nouveau users to build Mesa-git from AUR in a cleas way. Opinions? -Andy

2 1

[arch-dev-public] Signoff report for [testing]
by Arch Website Notification 08 Jun '12

08 Jun '12

=== 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 * 12 fully signed off packages * 21 packages missing signoffs * 10 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) == * nilfs-utils-2.1.2-1 (i686) * nilfs-utils-2.1.2-1 (x86_64) * libva-driver-intel-1.0.18-1 (i686) * libva-1.1.0-1 (x86_64) * libva-driver-intel-1.0.18-1 (x86_64) == Incomplete signoffs for [core] (5 total) == * bison-2.5.1-1 (i686) 1/2 signoffs * dnsutils-9.9.1.P1-1 (i686) 1/2 signoffs * linux-lts-3.0.33-1 (i686) 0/2 signoffs * nilfs-utils-2.1.2-1 (i686) 0/2 signoffs * nilfs-utils-2.1.2-1 (x86_64) 0/2 signoffs == Incomplete signoffs for [extra] (16 total) == * bind-9.9.1.P1-1 (i686) 0/2 signoffs * dbus-python-1.1.0-1 (i686) 0/2 signoffs * fcpci-31107-75 (i686) 0/2 signoffs * fcpcmcia-31107-70 (i686) 0/2 signoffs * gc-7.2-1 (i686) 0/2 signoffs * libva-driver-intel-1.0.18-1 (i686) 0/2 signoffs * lirc-1:0.9.0-18 (i686) 0/2 signoffs * nvidia-295.53-2 (i686) 0/2 signoffs * bind-9.9.1.P1-1 (x86_64) 0/2 signoffs * dbus-python-1.1.0-1 (x86_64) 0/2 signoffs * fcpci-31107-75 (x86_64) 0/2 signoffs * fcpcmcia-31107-70 (x86_64) 0/2 signoffs * gc-7.2-1 (x86_64) 0/2 signoffs * libva-1.1.0-1 (x86_64) 0/2 signoffs * libva-driver-intel-1.0.18-1 (x86_64) 0/2 signoffs * lirc-1:0.9.0-18 (x86_64) 0/2 signoffs == Completed signoffs (12 total) == * initscripts-2012.06.1-1 (any) * linux-3.4.1-1 (i686) * pam-1.1.5-4 (i686) * psmisc-22.17-1 (i686) * bison-2.5.1-1 (x86_64) * dnsutils-9.9.1.P1-1 (x86_64) * linux-3.4.1-1 (x86_64) * linux-lts-3.0.33-1 (x86_64) * pam-1.1.5-4 (x86_64) * psmisc-22.17-1 (x86_64) * nvidia-295.53-2 (x86_64) * pambase-20120602-1 (any) == All packages in [testing] for more than 14 days (10 total) == * gc-7.2-1 (i686), since 2012-05-18 * gc-7.2-1 (x86_64), since 2012-05-18 * nvidia-295.53-2 (i686), since 2012-05-21 * nvidia-295.53-2 (x86_64), since 2012-05-21 * lirc-1:0.9.0-18 (i686), since 2012-05-22 * lirc-1:0.9.0-18 (x86_64), since 2012-05-22 * fcpcmcia-31107-70 (i686), since 2012-05-24 * fcpci-31107-75 (i686), since 2012-05-24 * fcpcmcia-31107-70 (x86_64), since 2012-05-24 * fcpci-31107-75 (x86_64), since 2012-05-24 == Top five in signoffs in last 24 hours == 1. stephane - 3 signoffs

1 0

[arch-dev-public] [RFC] another base cleanup
by Tom Gundersen 08 Jun '12

08 Jun '12

Hi guys, We have been discussing on IRC on and off that we should cleanup our base group. I thought I'd make a suggestion, this should clearly be improved upon, but my main goal is to get the discussion going on the ML. It seems to me that the base group has several purposes, so to make things simpler I suggest splitting it up into several sub-groups, each with a specific purpose. In the end we might want to merge some/all of these together, or even drop some of them completely, but I thought presenting it in this way made the most sense: We have: base: things needed by everyone everywhere, including in build chroots base-boot: needed to boot a standard arch system, but not needed if all you want is a build chroot base-network: needed to connect to the internet in order to upgrade our machine further, but most people probably want to select the tools they want themselves rather than installing this group. not needed in a build chroot base-storage: some of this might be needed to mount your filesystems at boot, depending on your setup. most people probably want to select the tools they need, rather than install the whole group. not needed in a build chroot base-utils: a sensible set of tools an admin would expect to have at his/hers disposal after installation, needed to configure the machine or install further packages. never needed on a machine/chroot where the admin won't log in to configure it drop: keep in core (for now, removing it would be a different discussion), but remove from base. this would be stuff that don't deserve being in base in its own right (but were pulled in as deps by others) or stuff that, while generally useful is not needed by everyone, and those who need it can install it. My initial suggestion (with some input from people on IRC): base === util-linux bash coreutils man-pages shadow glibc filesystem gettext licenses base-boot ====== initscripts linux grub (drop this in favor of syslinux? it would still be in core of course) syslinux (new) mkinitcpio (new) base-network ======== wpa_supplicant dhcpcd inetutils iputils iproute2 (new) ppp pcmciautils (not strictly speaking networking, but might be needed by some networking devices) base-storage ======== cryptsetup device-mapper e2fsprogs lvm2 xfsprogs jfsutigls reiserfsprogs mdadm base-utils ====== vi wget which procps-ng tar sed bzip2 diffutils file findutils gawk grep gzip less nano pacman psmisc dropped ===== pciutils (usb pulls in hwids) usbutils (same as pciutils) syslog-ng (not necessary on all systems) sysvinit (pulled in by initscripts, no use on its own) udev/systemd-tools (alreday gone, pulled in by systemd or initscripts) man-db (pulled in by man-pages, no use on its own) perl (not necessary on its own, pulled in by whatever needs it) cronie (not needed by everyone) heirloom-mailx (not needed by everyone) logrotate (not needed by everyone) gcc-libs (pulled in by whatever needs it, no good on its own) texinfo (no good on its own, whatever needs it should pull it in) sysfsutils (no good on its own, whatever needs it should pul it in) FYI, this is a link to a previous cleanup (sorry if I missed some other wikipages that I should have linked to): <https://wiki.archlinux.org/index.php/User:Allan/Base_Cleanup>. Cheers, Tom

10 11

[arch-dev-public] Removing gimp-devel from [extra]
by Daniel Isenmann 07 Jun '12

07 Jun '12

Hi, I would like to move gimp-devel to AUR. At the moment, I'm the maintainer of gimp and gimp-devel, but I don't see any reason for the devel package in our repository. These are not the development files for gimp, it's the next devel branch for the next version (just for clarification). I will move it tomorrow, if no objections appears. Daniel

1 1

[arch-dev-public] [RFC] filesystem-2012.3-1
by Tom Gundersen 07 Jun '12

07 Jun '12

Hi guys, We want to tidy up the /var/{lock,run} situation. They should be symlinks to /run{,/lock}. Currently they are shipped as regular directories in the filesystem package, and on the next boot they are replaced by symlinks (by initscripts). It has been like this for about a year, and I'd like to fix this up properly by shipping the symlinks in the filesystem package. The upgrade requires user intervention: # rm /var/{lock,run} ; pacman -Syu Deleting these symlinks/folders on a running system might have unintended side effects, but as far as we have been able to figure out nothing fatal. To be on the safe side, I think we should (in a news item) advice users to shut down anything going on in the background to the extent possible before doing the upgrade and reboot after the upgrade is finished. Any thoughts on this? A request: it would be really ideal if we could roll a new installer release as soon as this is out, so people don't have to deal with these sorts of things on their first upgrade after install. Would that be possible? Cheers, Tom

3 8

Re: [arch-dev-public] [arch-general] [signoff] linux-3.3.8-1
by Tobias Powalowski 07 Jun '12

07 Jun '12

Am 06.06.2012 17:13, schrieb Sudaraka Wijesinghe: > On 06/06/12 18:31, Tobias Powalowski wrote: >> Hi guys, >> please signoff 3.3.8 series for both arches. >> package is not in testing, please grab it from here: >> http://dev.archlinux.org/~tpowa/linux/ >> >> This will move to [core] directly, because 3.4.1 is in [testing]. >> >> greetings >> tpowa >> > Just installed and rebooted x86_64, all seem to be good. > anyone for i686? -- 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 07 Jun '12

07 Jun '12

=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 4 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 16 fully signed off packages * 17 packages missing signoffs * 10 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 (4 total) == * filesystem-2012.6-2 (any) * initscripts-2012.06.1-1 (any) * psmisc-22.17-1 (i686) * psmisc-22.17-1 (x86_64) == Incomplete signoffs for [core] (4 total) == * bison-2.5.1-1 (i686) 1/2 signoffs * dnsutils-9.9.1.P1-1 (i686) 1/2 signoffs * linux-lts-3.0.33-1 (i686) 0/2 signoffs * bison-2.5.1-1 (x86_64) 1/2 signoffs == Incomplete signoffs for [extra] (13 total) == * bind-9.9.1.P1-1 (i686) 0/2 signoffs * dbus-python-1.1.0-1 (i686) 0/2 signoffs * fcpci-31107-75 (i686) 0/2 signoffs * fcpcmcia-31107-70 (i686) 0/2 signoffs * gc-7.2-1 (i686) 0/2 signoffs * lirc-1:0.9.0-18 (i686) 0/2 signoffs * nvidia-295.53-2 (i686) 0/2 signoffs * bind-9.9.1.P1-1 (x86_64) 0/2 signoffs * dbus-python-1.1.0-1 (x86_64) 0/2 signoffs * fcpci-31107-75 (x86_64) 0/2 signoffs * fcpcmcia-31107-70 (x86_64) 0/2 signoffs * gc-7.2-1 (x86_64) 0/2 signoffs * lirc-1:0.9.0-18 (x86_64) 0/2 signoffs == Completed signoffs (16 total) == * filesystem-2012.6-2 (any) * initscripts-2012.06.1-1 (any) * krb5-1.10.2-1 (i686) * linux-3.4.1-1 (i686) * pam-1.1.5-4 (i686) * psmisc-22.17-1 (i686) * systemd-185-1 (i686) * dnsutils-9.9.1.P1-1 (x86_64) * krb5-1.10.2-1 (x86_64) * linux-3.4.1-1 (x86_64) * linux-lts-3.0.33-1 (x86_64) * pam-1.1.5-4 (x86_64) * psmisc-22.17-1 (x86_64) * systemd-185-1 (x86_64) * nvidia-295.53-2 (x86_64) * pambase-20120602-1 (any) == All packages in [testing] for more than 14 days (10 total) == * gc-7.2-1 (i686), since 2012-05-18 * gc-7.2-1 (x86_64), since 2012-05-18 * nvidia-295.53-2 (i686), since 2012-05-21 * nvidia-295.53-2 (x86_64), since 2012-05-21 * lirc-1:0.9.0-18 (i686), since 2012-05-22 * lirc-1:0.9.0-18 (x86_64), since 2012-05-22 * fcpcmcia-31107-70 (i686), since 2012-05-24 * fcpci-31107-75 (i686), since 2012-05-24 * fcpcmcia-31107-70 (x86_64), since 2012-05-24 * fcpci-31107-75 (x86_64), since 2012-05-24 == Top five in signoffs in last 24 hours == 1. eric - 13 signoffs 2. tpowa - 9 signoffs 3. bisson - 8 signoffs 4. lcarlier - 5 signoffs 5. allan - 5 signoffs

1 0

[arch-dev-public] [signoff] [NACK] linux 3.4-1
by Florian Pritz 06 Jun '12

06 Jun '12

Hi, Starting with linux 3.4-1 I'm getting random corruptions when reading files from my file server over nfs and we've also seen problems with packages downloaded from our mirror on brynhild. The files on disk validate just fine (md5sum), it's just the transfer that seems to break. linux-lts 3.032-1 and linux 3.3.7-1 are good. -- Florian Pritz

3 4

[arch-dev-public] [signoff] linux-3.3.8-1
by Tobias Powalowski 06 Jun '12

06 Jun '12

Hi guys, please signoff 3.3.8 series for both arches. package is not in testing, please grab it from here: http://dev.archlinux.org/~tpowa/linux/ This will move to [core] directly, because 3.4.1 is in [testing]. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

2 1

[arch-dev-public] Signoff report for [testing]
by Arch Website Notification 06 Jun '12

06 Jun '12

=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 8 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 7 fully signed off packages * 29 packages missing signoffs * 6 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 (8 total) == * bison-2.5.1-1 (i686) * linux-3.4.1-1 (i686) * linux-lts-3.0.33-1 (i686) * bison-2.5.1-1 (x86_64) * linux-3.4.1-1 (x86_64) * linux-lts-3.0.33-1 (x86_64) * dbus-python-1.1.0-1 (i686) * dbus-python-1.1.0-1 (x86_64) == Incomplete signoffs for [core] (15 total) == * bison-2.5.1-1 (i686) 0/2 signoffs * dnsutils-9.9.1.P1-1 (i686) 0/2 signoffs * krb5-1.10.2-1 (i686) 1/2 signoffs * linux-3.4.1-1 (i686) 1/2 signoffs * linux-lts-3.0.33-1 (i686) 0/2 signoffs * pam-1.1.5-4 (i686) 1/2 signoffs * pinentry-0.8.1-4 (i686) 1/2 signoffs * systemd-185-1 (i686) 0/2 signoffs * bison-2.5.1-1 (x86_64) 0/2 signoffs * dnsutils-9.9.1.P1-1 (x86_64) 0/2 signoffs * krb5-1.10.2-1 (x86_64) 1/2 signoffs * linux-3.4.1-1 (x86_64) 1/2 signoffs * linux-lts-3.0.33-1 (x86_64) 0/2 signoffs * pam-1.1.5-4 (x86_64) 1/2 signoffs * systemd-185-1 (x86_64) 1/2 signoffs == Incomplete signoffs for [extra] (13 total) == * bind-9.9.1.P1-1 (i686) 0/2 signoffs * dbus-python-1.1.0-1 (i686) 0/2 signoffs * fcpci-31107-75 (i686) 0/2 signoffs * fcpcmcia-31107-70 (i686) 0/2 signoffs * gc-7.2-1 (i686) 0/2 signoffs * lirc-1:0.9.0-18 (i686) 0/2 signoffs * nvidia-295.53-2 (i686) 0/2 signoffs * bind-9.9.1.P1-1 (x86_64) 0/2 signoffs * dbus-python-1.1.0-1 (x86_64) 0/2 signoffs * fcpci-31107-75 (x86_64) 0/2 signoffs * fcpcmcia-31107-70 (x86_64) 0/2 signoffs * gc-7.2-1 (x86_64) 0/2 signoffs * lirc-1:0.9.0-18 (x86_64) 0/2 signoffs == Incomplete signoffs for [unknown] (1 total) == * libusbx-1.0.11-2 (i686) 1/2 signoffs == Completed signoffs (7 total) == * filesystem-2012.6-1 (any) * fakeroot-1.18.4-1 (i686) * fakeroot-1.18.4-1 (x86_64) * pinentry-0.8.1-4 (x86_64) * nvidia-295.53-2 (x86_64) * pambase-20120602-1 (any) * libusbx-1.0.11-2 (x86_64) == All packages in [testing] for more than 14 days (6 total) == * gc-7.2-1 (i686), since 2012-05-18 * gc-7.2-1 (x86_64), since 2012-05-18 * nvidia-295.53-2 (i686), since 2012-05-21 * nvidia-295.53-2 (x86_64), since 2012-05-21 * lirc-1:0.9.0-18 (i686), since 2012-05-22 * lirc-1:0.9.0-18 (x86_64), since 2012-05-22 == Top five in signoffs in last 24 hours == 1. thomas - 4 signoffs 2. foutrelis - 2 signoffs

4 3