February 2009 - Arch-general - lists.archlinux.org

[arch-general] Perhaps a bug on the dependences of KDE 4.2
by Christian Leng 07 Feb '09

07 Feb '09

Greetings to all. Last night I tried to install KDE on my system. I had not had any version of KDE installed before. I simply used "pacman -S kde" to install the complete KDE from the REPO. Of course, "kde" was a package group: [rookie@DROWNWESTLAKE ~]$ pacman -Qg kde kde kdeaccessibility kde kdeadmin kde kdeartwork kde kdebase kde kdebase-runtime kde kdebase-workspace kde kdeedu kde kdegames kde kdegraphics kde kdelibs kde kdemultimedia kde kdenetwork kde kdepim kde kdepimlibs kde kdeplasma-addons kde kdesdk kde kdetoys kde kdeutils kde kdewebdev After the installation, I edited /etc/rc.conf and added the kdm to the daemons. Then I was desperated to find that KDM couldn't be launched correctly(but "startkde" worked well). A message box was displayed on the screen, saying "can't open file: /usr/share/apps/kdm/themes/archlinux-soft-grey". Then I searched the packages and installed the package 'archlinux-themes-kdm' and everything went well. It seems that the default kdm theme is set to 'archlinux-soft-grey' but the proper package can't be retrieved and installed automatically, i.e. a bug on the dependences of kde.

2 2

Re: [arch-general] [arch-dev-public] Official Installation guide needs your help!
by Grigorios Bouzakis 06 Feb '09

06 Feb '09

On Fri, Feb 06, 2009 at 03:33:49PM -0500, Dusty Phillips wrote: > 2009/2/6 Aaron Griffin <aaronmgriffin(a)gmail.com>: > > Hey guys, > > I wanted to make you aware of the following: > > http://bugs.archlinux.org/task/13140 > > > > The "Official Installation Guide" is severely outdated (the wiki page > > still mentions "i686 optimized"). > > As one of the two people who was once on Arch's only attempt at an > official documentation team, and as one of several people who > contributed many of the first articles to the wiki, I have this to say > on the topic: > > Drop the official install guide. > > We know our wiki is well-maintained and well organized, and it seems > to do that by itself without much developer interference. Go wiki! > Originally, when we first set the wiki up Dennis, Judd, and I felt > that the official install guide should be more... well... official. > But its out of date, its always out of date, and there are wiki texts > that are not out of date. Now, seeing how our wiki experiment has > exceeded our hopes and expectations, I'd say that the install guide > (drop the 'official') should be community maintained as are all our > wiki pages. It will improve. When its time for a release, "somebody > official" should read through it, ensure its accurate, convert it to > plaintext and put it on the iso. > > Dusty I agree with the above for the most part. The only "problems" with the Beginners Guide, which is the only up to date and worth of being included anywhere guide is that its too "wikified". eg. references "go here" with a link to another wiki page. It would definately take less time to convert it into something less dependant on the wiki than refactoring the official guide. Also theres references to eg. like Loui said yaourt which should probably go (?) Also the official guide is linked from all over the place. archlinux.org wiki.archlinux.org + its part of the iso. Should those change to link the beginners guide? Should the Beginners Guide change its name to the Arch Linux Handbook for example? FTR I had always been in favour of maintaining 1 guide from the beginning. -- Greg what to do and what not to do in public :o) http://linux.sgms-centre.com/misc/netiquette.php

2 2

[arch-general] FSC Amilo Pro 2030 - Fan control
by Strika 06 Feb '09

06 Feb '09

Greetings to all, I found a way to control fan speed on FSC Amilo Pro 2030. I found some articles on Ubuntu forum, and I used some stuff from arch wiki. Should I put solution on forum or on wiki, maybe? I will anyway put it on my blog. I'm new in this way of contributing, so I'm asking this so I would now what to do with similar stuff in future. Thanks for answer, Nebojša Stričević

2 1

[arch-general] hwdetect with kernel upgrade?
by Shridhar Daithankar 03 Feb '09

03 Feb '09

Hello, A long time ago, I posted that with kernel upgrade, the module insertion hangs till I hit enter. I ran hwdetect and updated the modules array, sans the standard acpi modules and it now works reliably every time. It can boot unattended now. AFAIK, the module-names and functionality is prone to changes from kernel to kernel. Should we automatically run hwdetect or advise users to check it in case of kernel upgrade? -- Shridhar

4 3

[arch-general] [signoff] kernel26 2.6.28.3-1
by Tobias Powalowski 02 Feb '09

02 Feb '09

Hi guys, new kernel adresses the following things: - bump to latest version - changed to new btusb - removed buggy-acpi-patch please signoff for both arches greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

1 0

[arch-general] [signoff] lvm2 2.02.44-1 & device-mapper 1.02.30-1
by Eric Bélanger 02 Feb '09

02 Feb '09

Hi, Updated packages for lvm2 and device-mapper are now in testing. The changes are: * lvm2 2.02.44-1 * Upstream update * Added bash depends * device-mapper 1.02.30-1 * Upstream update * Added readline depends * Added pkgconfig file Please signoff. Two signoff for i686 would be nice has I don't use lvm2 on my i686 system so I could only do some simple sanity tests. As very few devs uses this, signoffs from users would be appreciated. Eric

1 0

[arch-general] Having trouble compileing a2ps
by Baho Utot 01 Feb '09

01 Feb '09

Using: gcc version 4.3.2 default build falgs in makepkg pkgname=a2ps pkgver=4.13c pkgrel=1 pkgdesc="a2ps is an Any to PostScript filter /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -DSYSCONFFILE=\"/etc/a2ps/a2ps.cfg\" -I. -I.. -I.. -I../intl -I. -march=i686 -mtune=generic -O2 -pipe -MT hashtab.lo -MD -MP -MF .deps/hashtab.Tpo -c -o hashtab.lo hashtab.c libtool: compile: gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -DSYSCONFFILE=\"/etc/a2ps/a2ps.cfg\" -I. -I.. -I.. -I../intl -I. -march=i686 -mtune=generic -O2 -pipe -MT hashtab.lo -MD -MP -MF .deps/hashtab.Tpo -c hashtab.c -o hashtab.o mv -f .deps/hashtab.Tpo .deps/hashtab.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -DSYSCONFFILE=\"/etc/a2ps/a2ps.cfg\" -I. -I.. -I.. -I../intl -I. -march=i686 -mtune=generic -O2 -pipe -MT path-concat.lo -MD -MP -MF .deps/path-concat.Tpo -c -o path-concat.lo path-concat.c libtool: compile: gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -DSYSCONFFILE=\"/etc/a2ps/a2ps.cfg\" -I. -I.. -I.. -I../intl -I. -march=i686 -mtune=generic -O2 -pipe -MT path-concat.lo -MD -MP -MF .deps/path-concat.Tpo -c path-concat.c -o path-concat.o In file included from path-concat.c:30: /usr/include/string.h:234: error: expected identifier or '(' before 'void' /usr/include/string.h:234: error: expected ')' before '(' token make[3]: *** [path-concat.lo] Error 1 make[3]: Leaving directory `/srv/http/Build/BUILD.i686/extra/a2ps/src/a2ps-4.13/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/srv/http/Build/BUILD.i686/extra/a2ps/src/a2ps-4.13/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/srv/http/Build/BUILD.i686/extra/a2ps/src/a2ps-4.13' make: *** [all] Error 2 ==> ERROR: Build Failed. Is this a gcc issue?

4 6