- Arch-general - lists.archlinux.org

[arch-general] pacman changes libcrypt.so.1 symlink
by Lukáš Jirkovský 08 May '08

08 May '08

Hi I don't know if it's bug or feature, but it makes me crazy. It begun probably after some pacman upgrade. I'm using blowfish passwords with my archlinux, so my /lib/libcrypt.so.1 points to libxcrypt.so.1 instead of libcrypt-2.7.so from glibc. In my pacman.conf I have NoExtract = lib/libcrypt.so.1. But even though I've made this arrangements everytime when I run pacman -S some_interesting_package (it doesn't have to be glibc, eg libpng is enough) the link gets changed. Any suggestions? Best regards, Lukas '6xx' Jirkovsky

5 7

[arch-general] netcfg2 error
by ponto 06 May '08

06 May '08

my wireless router is using wpa2-personal with aes encryption. root /etc/network.d # iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:28:34:A3:E8:1B ESSID:"casa" Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Quality=92/100 Signal level=-39 dBm Noise level=-127 dBm Encryption key:on IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=000000c77415d93a root /etc/network.d # cat casa-wireless CONNECTION="casa-wireless" INTERFACE=wlan0 HOSTNAME=pc-no-quarto IP="static" IFOPTS="192.168.1.8 netmask 255.255.255.0 broadcast 192.168.1.255" GATEWAY="192.168.1.1" # DNS Settings (optional) # DOMAIN=localdomain DNS1=195.23.129.126 # DNS2= # SEARCH= ESSID="casa" SECURITY="wpa" KEY="yZAwO6XNOyvPtCImzSEi5gZQ8uO31rhdnFjYu7QDNZNmf9uud48P3qqcsIZywgT" SCAN="YES" TIMEOUT=20 and netfg2 outputs this: root /etc/network.d # netcfg2 casa-wireless > casa-wireless is not a valid connection, check spelling or look at examples what am i doing wrong? halp plz

2 1

[arch-general] rdup: orphan request
by Jan Spakula 06 May '08

06 May '08

Hello, I would like to ask for rdup in AUR to be orphaned, so that I can maintain it: 1) it's out-of-date (version 0.5.2, current 0.5.7; considerable (for me) improvements) 2) the maintainer (dice) has the last appearance in AUR on 1/14/2008 3) he does not respond to comments in AUR and his e-mail address does not work (tried couple of days ago, mail returned as undeliverable). 4) there's a perl dep of this package that needs to be taken care of. Thank you, -- Jan

2 3

[arch-general] ClamAV should be update to 0.93
by Tino Reichardt 05 May '08

05 May '08

Hello list, clamav should be updated. -- regards, TR

8 21

Re: [arch-general] [arch-dev-public] ATTN: Kernel maintainers (tpowa, brain0): libcap
by Michal Soltys 05 May '08

05 May '08

Travis Willard wrote: > Hey guys, > > I just realized that, for some squirrely reason, I am currently > "maintaining" libcap. I have no freakin' clue what libcap even is. I > just got a flag-out-of-date version asking if we should update it to > libcap2, which seems reasonable, as it's nice and shiny-new. Looking > around, however, libcap seems tied to kernel releases, so maybe it'd > make more sense for someone more in-the-know with kernel.org stuff to > take it on? > Version 2.x works pretty fine - I've been using it for a while, but you will need some simple and straightforward patches for e.g. samba (it assumes ancient lack of header declarations, should be fixed in .29) and vsftpd (doesn't look for 2.x at all, but otherwise compiles and works perfectly fine). From other notable things - ntpd requires linking to libcap, if you want to run it with privilege separation. > Basically, if someone out there knows WTF libcap is for, and how to > test, etc., then let me know and you can grab it. > In short - it's overbloated suid ;) http://www.friedhoff.org/posixfilecaps.html Sorry for crossposting, but I though I'd be good to mention samba / vsftpd stuff. Cheers

2 1

[arch-general] Spellcheck in Firefox3
by Jackson Alley 05 May '08

05 May '08

Hey, I know it's still in beta, but for me everything works except for spell check. I was wondering if anyone has figured out how to get spell check working in the latest beta? J

2 1

[arch-general] AUR Cleanup
by Allan McRae 05 May '08

05 May '08

The AUR has a large number of obsolete packages which could use cleaning up. Examples of packages that may be cleaned up are: - packages that have been renamed or replaced - old and unmaintained developmental (cvs/svn/etc) packages This is where you can help. Post suggestions of packages in the AUR Cleanup wiki page (http://wiki.archlinux.org/index.php/AUR_CleanUp_Day) TUs will get together and go though the list in a couple of weeks and confirm which packages should be removed. Please do not remove suggestions from the wiki page but add a comment on why it should be kept instead. TUs will take great care not to delete any useful package. Cheers, Allan -- Allan McRae Arch Linux Trusted User

1 0

[arch-general] Status of linux 2.6.25 kernel
by Hussam Al-Tayeb 03 May '08

03 May '08

What's the status of the 2.6.25 kernel in testing? Any showstoppers left? Regards, Hussam Al-Tayeb.

1 0

[arch-general] Upstream bugs, patches
by Nagy Gabor 02 May '08

02 May '08

Hi! I'm new to this list, and my English is far from perfect, please tolerate it ;-) I am/was a big fan of ArchLinux, I'm using it from 0.5 version, I also made some little contributions to pacman, but now I noticed some tendencies which I cannot accept. So I would like to hear the official "standpoint" about a certain question, before I may drop my good old distro. I also think that this question is important to all end-users. (Aaron:) I know that I'm not popular here, but I hope that you won't answer "against me" ;-) Some foreword (sorry, maybe off, I would like to manipulate thoughts :-D): Basically I think that principles are _not_ rules. So things like KISS and "vanilla packages" are good for defining ourselves in one sentence (in wikipedia for example), but I don't really understand reasoning like "foo violates KISS" (IMHO the reasoning should say, _why_ it worth applying KISS here.). When I _describe_ myself as liberal, I won't deduce my acts from this "rule"... (theoretical example). So the question: Do/Should Archlinux packagers apply unofficial or merged-but-not-yet-released patches to fix an existing _bug_ of a released package? An example: http://bugs.archlinux.org/task/5861 This is quite an old bug, and we are just waiting and waiting... If the answer no, do packagers forward the bug to the official developer or the end-user should forward his discovered bug? An other small example, which is much less important; but I think this belongs to the same "category", the reasoning is much more mysterious to me, since the "patch" clearly cannot break anything here: http://bugs.archlinux.org/task/10307 This was closed 4 minutes after opening, so I couldnot discuss it (I wanted to revert my last sentence there, this is not true now, I didn't want to lie). Evince developers like that option, and they don't want to change it. (But I don't agree with them here, of course). I simply cannot imagine any reason for "won't fix" (apart from "lazyness" :-P). I'm pretty sure that "implementing" it has _no drawback_, and at least 6 users (from the number of requests) would like it. Again, it is a marginal issue (I put my evince.desktop to NoUpgrade of pacman), but I would like to understand the reason of close. Bye I hope, that I didn't hurt anybody, overall I think that AL is still one of best distros around, and I must say a big "thank you" for your work.

5 10

[arch-general] Info for tellico users
by Attila 02 May '08

02 May '08

Hi, i recognized that libxslt makes the step to 1.1.23 but if you use tellico (http://periapsis.org/tellico/) than there could be a problem with it: http://www.periapsis.org/archives/2008/05/01/tellico_not_showing_most_value… See this please only as an information because it seems that at the moment the author of tellico don't know what is the reason (tellico or libxslt). See you, Attila

1 0