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

[arch-dev-public] [signoff] pacman 3.1.4, libarchive 2.4.17
by Dan McGee 03 Apr '08

03 Apr '08

Signoffs for both architectures needed, as well as a build of pacman for x86_64 (since pacman depends on the new libarchive, I can't build with satisfied deps as I don't have sudo, and I really can't do anything without sudo including installing a package in my chroot). pacman changes: http://www.archlinux.org/pipermail/pacman-dev/2008-April/011561.html libarchive changes: who knows, but 3 minor versions in like 2 days. It should be plenty stable though, I promise. -Dan

4 6

[arch-dev-public] licenses: GPL permutations
by Paul Mattal 02 Apr '08

02 Apr '08

What is the right way to list all the various contortions you can now have of GPL in the license array? There's: GPL - any version of GPL GPL2 - only version 2 GPL2+ - version 2 or later GPL3 - version 3 only GPL3+ - version 3 or later These are all substantively different (except the last two.. for now) so how do we express these? Should we actually create common licenses GPL2+ and GPL3+ which reference the other two, and make GPL reference them all? Do we need a GPL1 and GPL1+? - P

3 5

[arch-dev-public] [signoff] tzdata 2008b-1
by Andreas Radke 02 Apr '08

02 Apr '08

minor update. in testing for both arches. please signoff. -Andy

3 2

[arch-dev-public] [signoff] man-pages 2.79-1
by Andreas Radke 02 Apr '08

02 Apr '08

minor update. in testing for both arches. please signoff. -Andy

3 2

[arch-dev-public] [signoff] mkinitcpio 0.5.18.1
by Thomas Bächler 02 Apr '08

02 Apr '08

Quick bugfix. I have no idea why the bug didn't occur yesterday and all the days before (on an identical filelist), but today, the use of sort -u in mkinitcpio broke my image: /lib/modules/2.6.25-rc8 was added before /lib/modules and thus extraction failed (cpio is very bitchy about this). The only change is: http://projects.archlinux.org/git/?p=mkinitcpio.git;a=commitdiff;h=45a9fab4… Please sign off quickly, before nobody can boot their arch anymore.

2 2

[arch-dev-public] request/question: archboot isos hosting directory
by Tobias Powalowski 31 Mar '08

31 Mar '08

Hi archboot isos are now well tested and work as they should, i would like to put them in ftp/iso directory that other mirrors will sync them too. Which directory whould be fine for you? ftp/iso/archboot/2008.03 ? or something else? thanks for input. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

5 7

[arch-dev-public] Dropping ipw3945 from core
by Thomas Bächler 31 Mar '08

31 Mar '08

After I discovered that my problems with the new Intel driver where related to dhclient and fixed the bug, I am now successfully using iwl3945 on my machine. It seems to be working perfectly, so I am considering dropping ipw3945 from core/support with the 2.6.25 release (so there will be no new package versions after ipw3945-1.2.2-8). This is intended as a warning, but also as a question: Is there anyone who cannot use iwl3945 instead of ipw3945?

1 0

[arch-dev-public] [signoff] kernel26 2.6.24.4-1, support/atl2 2.0.4-1
by Thomas Bächler 30 Mar '08

30 Mar '08

Changes to the latest kernel by tpowa: - All patches have been collapsed into a single patch-2.6.24.4-1. Patch generation is done by abuse of makepkg now and nothing is done inside a SCM, but that will be fixed. Currently, everything is in http://dev.archlinux.org/~thomas/kernel26/linux-2.6-ARCH.tar.bz2. - removed pre-2.6.24.4 patch and updated to 2.6.24.4 - updated unionfs to 2.3.1 (according to simo this fixes some race conditions) - removed the aufs splice patch due to incompatibility with unionfs. This breaks aufs, but Simo promised to fix it (ping Simo) - removed the atl2 patch and moved it to a separate package in core/support due to the many complaints by developers. - Some PKGBUILD stupidity cleanup: Remove /boot/kconfig26, because it is the most unnecessary file in the history of unnecessary files - Removed /etc/mkinitcpio.d/kernel26-fallback.conf, because the default fallback image doesn't need a separate config file anymore Please sign off. We need to move some kernel to core fast, because applications built with gcc 4.3 might be broken with any other kernel. (At the time I am posting this, only x86_64 is uploaded and tested, i686 will be uploaded in a few minutes, but untested).

4 5

[arch-dev-public] [signoff] glib2 2.16.1-1
by Jan de Groot 30 Mar '08

30 Mar '08

For GNOME 2.22, I need glib2 updated to 2.16.1, which is in testing for a while now. Please signoff for both architectures so GNOME can get moved too this week.

3 2

[arch-dev-public] dhclient: fixed two bugs in extra
by Thomas Bächler 30 Mar '08

30 Mar '08

I uploaded dhclient 3.0.6-2 which fixes two bugs: - fix-broken-resolvconf.patch dhclient-script only generates a new resolv.conf if the DHCP server transmits a domain name. However, the DHCP specifications don't require a DHCP server to do that. This was reported to ISC in 2004 IIRC and they never even looked at it. This patch fixes resolv.conf generation, such that resolv.conf is always generated if the DHCP server transmits at least one DNS server. I actually fixed this half a year ago, and didn't upload it. - fix-mac80211-wireless.patch I was trying to find this bug for over half a year and just now found out it is dhclient's fault (partially). dhclient/dhclient-script brings the interface down and up again on several occasions. This was never a problem in the past, but with a mac80211 driver, this results in an unusable interface until you reassociate (the RUNNING flag in ifconfig is missing). The interface was brought by dhclient-script down on occasions where bringing it down isn't even necessary, but it suffices to simply delete the ipv4 data (which was done anyway). This patch fixes the problem by removing the "down" keyword from all ifconfig lines in dhclient-script, as the script is never required to actually bring the interface down. One of the occasions when dhclient would bring the interface down and up again was a DHCPNAK. As a NAK is very common when you switch between several wireless networks, as you may try to REQUEST a lease which has not expired yet and get a NAK as the network you are on now is different. This essentially broke all mac80211 driver when using wireless roaming with dhclient and long lease times.

1 0