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

Re: [arch-dev-public] [arch-general] Make arch-announce read only?
by Aaron Griffin 03 Apr '09

03 Apr '09

On Tue, Mar 31, 2009 at 8:30 PM, pyther <pyther(a)pyther.net> wrote: > > I was wondering if we could make arch-announce a read only list. Sort of > like the dev mailing list. Anyone who tries to respond to an announcement > could get an email saying something along the lines of "If you have a > comment about an announcement, please post it on the arch-general list. > Thank you." > > I do not filter the arch-announce mailings for obvious reason and I do not > think I am alone. It is very annoying to see replies in my inbox. Forwarding to the dev list - what do you guys think? I think it's a good idea

2 2

Re: [arch-dev-public] KOffice 1.9.99.0 RC1 uploaded
by Ronald van Haren 03 Apr '09

03 Apr '09

On 4/3/09, Pierre Schmitz <pierre(a)archlinux.de> wrote: > Hi Ronald (and others), > > this mail is quite interesting. Especially that we still ship lcms without > the > security patch. Imho we should update to lcms 1.18. I hope it does not > introduce a so name bump...but I think it will. :-( > > Pierre > replied from arch-dev mailing list. I think we're safe just updating lcms without rebuilding anything. Everything seems to remain in working order and lddd also does not find anything lcms related after a local version bump. When nobody bumped the repo version at the end of the weekend I should have time to do so. @Pierre: which mailing list is that you get those messages from so I can subscribe? Ronald

3 2

[arch-dev-public] [signoff] mysql, mysql-clients and libmysqlclient
by Douglas Soares de Andrade 03 Apr '09

03 Apr '09

Hi, I have just updated mysql to 5.1.33 and it has been working great here - thanks for everyone that helped in the process. I want to move the asap to extra. Any cons here ? Thanks a lot =)

3 4

[arch-dev-public] WTF? i686 support?
by Aaron Griffin 02 Apr '09

02 Apr '09

I specifically told you guys that we were NOT dropping the i686 port, and you guys went and voted on it without me? This is the last straw. If you guys don't fix this now, consider this my last email.

11 13

[arch-dev-public] [signoff] crda 1.0.1-2, wireless-regdb 2009.03.09-1
by Thomas Bächler 02 Apr '09

02 Apr '09

Changes compared to 1.0.1-1: - Split crda into crda and wireless-regdb (as it is done by all other distros that already include it) The regdb will probably be updated more often than crda - If crda is installed, the integrity of the regdb is now verified on build and install time (if not, a warning is issued on build time, and nothing happens on install time) A warning is issued if the database is corrupted. - The file /etc/conf.d/wireless-regdom moved from crda to wireless-regdb. If the user has already set the domain there, the .pacorig file overwrites the one from wireless-regdb. This is safe, as the only changes that may be in the stock file are newly added domains, which are commented - It is not necessary to add wireless-regdom to DAEMONS any more. As soon as cfg80211 is loaded, the regdom is set (if one is specified in /etc/conf.d/wireless-regdom) This is not only more convenient, but also ensures the regdom is still set correctly after rmmod cfg80211; modprobe cfg80211 Please sign off. Note that with 2.6.29-ARCH and newer, you will only get access to the "World" regdom (channels 1-11, plus some 5GHz channels with passive scanning only) if you don't install crda and set your regdom. (With 2.6.28-ARCH and older, the "US" regdom was enabled by default, and you could set "EU" and "JP" domains with a module parameter) Signoff procedure: 1) If crda is already installed, wireless-regdb will issue a warning on installation if anything is corrupted. (You can also run regdbdump /usr/lib/crda/regulatory.bin manually, if that shows you a bunch of data instead of an error, all is fine). 2) After a you reboot, reload cfg80211 or "/etc/rc.d/wireless-regdb start", "iw list" should show you the proper channels. You will also see messages in your syslog if you change the regdom. Pending issues: Updates for BN (missing two 5GHz bands) and KR, see http://permalink.gmane.org/gmane.linux.kernel.wireless.general/30811 DE domains misses some 5GHz bands due to confusing documents from the Bundesnetzagentur: http://permalink.gmane.org/gmane.linux.kernel.wireless.general/30803

2 2

[arch-dev-public] x86_64 machines for Arch devs
by Dusty Phillips 01 Apr '09

01 Apr '09

Hey guys, I know we all agreed to drop i686 support, but it leaves me with a small problem -- I'm one of the few devs not yet blessed with a 64 bit machine. I was thinking maybe we could use the donation funding to buy x86_64 build boxes for each of us. We've got a lot of donation funding and the income from Schwag would of course help, but we'd probably have to do a donation drive to raise about half the funds. It seems like a good use of the funding to me, and our community is totally awesome, I'm sure it won't be hard to raise it. What do you guys think? In the meantime, I'm going to continue maintaining an i686 repo of my own for a few weeks, but lets face it: this machine is a dinosaur, its time to upgrade! Dusty

5 4

[arch-dev-public] [signoff] gettext-0.17-2
by Allan McRae 01 Apr '09

01 Apr '09

Added cvs optdep for autopoint Install script for info pages. Allan

3 4

[arch-dev-public] [signoff] xinetd-2.3.14-5
by Allan McRae 01 Apr '09

01 Apr '09

Signoff for xinetd-2.3.14-5 - License rebuild - Fix man page location - Add optdepends on perl (xconv.pl script) I needs someone to build for x86_64. Allan

2 1

[arch-dev-public] [signoff] mdadm-2.6.9-1
by Tobias Powalowski 01 Apr '09

01 Apr '09

Hi http://bugs.archlinux.org/task/10651 http://bugs.archlinux.org/task/9122 both states raid is broken for more complex setups. According to my earlier mail about assembling raid arrays i wrote a new hook and install file. It uses mdassemble.static from mdadm tarball which is smaller than mdadm.static and does the assembling job and loading of the needed raid module. How does it work: - If a an array is defined on users system /etc/mdadm.conf, the file will be added to initramfs and used for the assembling things. - If no array was defined it falls back to commandline assembling and a madm.conf file will be created on the fly during bootup. Old command line syntax wasn't changed, uuid support is added (eg. md=0,0900878d:f95f6057:c39a36e9:55efa61b) Last Fix: -fixed booting from partitionable raid, by loading md_mod before assembling. Passed Tests: - Tested normal raid 1 setup with and without mdadm.conf modified. - Tested raid1 partitionable raid with extended and without extended partition. - Tested uuid assembling from commandline I think this is ready to move to core, please signoff. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

3 2

[arch-dev-public] [signoff] acl-2.2.47-2
by Allan McRae 01 Apr '09

01 Apr '09

Fixes the RPATH issue: http://bugs.archlinux.org/task/13891

2 1