[arch-general] Arch doc inclusion policy
Hey everybody, looking through my /usr/share/doc today I noticed that there were surprisingly few packages that actually installed their documentation there. Not even the SDL package installed its docs in there. I don't mind this too much as I carry all kinds of library documentation in my home directory with me at all times to have it accessible when I have no Internet connection available. This left me wondering, though, what Arch's general policy is on inclusion/exclusion of library/tool/package documentation for /usr/share/doc and if this policy should be generally applied to AUR packages as well. -- Sven-Hendrik
Re: [arch-general] ext3 driver for windows
I'm more concerned about compatibility between mac and ext3. Anyone have tried before ?
Re: [arch-general] Arch doc inclusion policy
On Sat, Aug 1, 2009 at 9:39 AM, Sven-Hendrik Haases...@lutzhaase.com wrote: Hey everybody, looking through my /usr/share/doc today I noticed that there were surprisingly few packages that actually installed their documentation there. Not even the SDL package installed its docs in there. I don't mind this too much as I carry all kinds of library documentation in my home directory with me at all times to have it accessible when I have no Internet connection available. This left me wondering, though, what Arch's general policy is on inclusion/exclusion of library/tool/package documentation for /usr/share/doc and if this policy should be generally applied to AUR packages as well. -- Sven-Hendrik The policy is to include them unless they are very, very big. In that case, they can be excluded and, sometimes, provided in a separate package at the maintainer's discretion (e.g. qt and qt-doc). In the past, we were removing the docs systemtically, so packages that have not been rebuilt since then might be missing their docs.
Re: [arch-general] [arch-dev-public] news item draft: /dev layout cleanup
Allan McRae (2009-08-01 22:33): Hi all, Getting around to this again [draft] /dev layour cleanup The /dev layout has been cleaned up to comply to the device names specified in the Linux kernel documentation. We had some legacy left from our devfs days, which has now been removed. The most obvious change from a users perspective is the vc/*-tty* transition. The initscripts-2007.08 update requires adjusting the /etc/inittab file to refer to tty* instead of vc/*. Due to severe system breakages if this file is not updated, this change will be automatically handled by pacman. The original /etc/inittab file is saved as /etc/inittab.pacsave. To be clear: package /etc/inittab - inittab.pacnew (if needed) system /etc/inittab - inittab.pacsave system /etc/inittab --sed-- inittab Make sure to check these files after the update and do any merging that is required. [/draft] Finally, are we going to do a quick update to initscripts and filesystem before this is moved? There have been a few patches push to get for these. I can do that tomorrow if people agree? Allan As someone has already mentioned, it would be nice to mention the reasons for this (vc/*-tty*) change to please curious users... Why is this needed? Are /dev/vc/* going away? -- -- Rogutės Sparnuotos
Re: [arch-general] [arch-dev-public] news item draft: /dev layout cleanup
On Sat, Aug 1, 2009 at 1:07 PM, Rogutės Sparnuotosrogu...@googlemail.com wrote: Allan McRae (2009-08-01 22:33): Hi all, Getting around to this again [draft] /dev layour cleanup The /dev layout has been cleaned up to comply to the device names specified in the Linux kernel documentation. We had some legacy left from our devfs days, which has now been removed. The most obvious change from a users perspective is the vc/*-tty* transition. The initscripts-2007.08 update requires adjusting the /etc/inittab file to refer to tty* instead of vc/*. Due to severe system breakages if this file is not updated, this change will be automatically handled by pacman. The original /etc/inittab file is saved as /etc/inittab.pacsave. To be clear: package /etc/inittab - inittab.pacnew (if needed) system /etc/inittab - inittab.pacsave system /etc/inittab --sed-- inittab Make sure to check these files after the update and do any merging that is required. [/draft] Finally, are we going to do a quick update to initscripts and filesystem before this is moved? There have been a few patches push to get for these. I can do that tomorrow if people agree? Allan As someone has already mentioned, it would be nice to mention the reasons for this (vc/*-tty*) change to please curious users... Why is this needed? Are /dev/vc/* going away? It's in the first paragraph
Re: [arch-general] [arch-dev-public] news item draft: /dev layout cleanup
Allan McRae wrote: Hi all, Getting around to this again [draft] /dev layour cleanup The /dev layout has been cleaned up to comply to the device names specified in the Linux kernel documentation. We had some legacy left from our devfs days, which has now been removed. The most obvious change from a users perspective is the vc/*-tty* transition. The initscripts-2007.08 update requires adjusting the /etc/inittab file to refer to tty* instead of vc/*. Due to severe system breakages if this file is not updated, this change will be automatically handled by pacman. The original /etc/inittab file is saved as /etc/inittab.pacsave. To be clear: package /etc/inittab - inittab.pacnew (if needed) system /etc/inittab - inittab.pacsave system /etc/inittab --sed-- inittab Make sure to check these files after the update and do any merging that is required. [/draft] * If and only if, user touched /etc/securetty (from 'filesystem'), also must be edit manually it again to match /etc/securetty.pacnew, so I think that is more safe to add to the announce mail. * Also note the importance of update all packages 'initscripts' 'filesystem' 'udev' 'syslog-ng' at the same time. -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
[arch-general] Xorg broken after last update
Hello. The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. Anyone experienced the same thing? Best regards, Luís Moreira.
Re: [arch-general] Xorg broken after last update
Luís Moreira lmm1...@gmail.com: Anyone experienced the same thing? No, work's without any problems here. I have the same setting as you: x86_64 without testing. -- Gruß, Johannes Täglich http://blog.hehejo.de und du fühlst dich gut. Mast und Schotbruch mit dem http://segelsport-blog.de. signature.asc Description: PGP signature
Re: [arch-general] Xorg broken after last update
On Sat, Aug 1, 2009 at 6:01 PM, Johannes Held m...@hehejo.de wrote: Luís Moreira lmm1...@gmail.com: Anyone experienced the same thing? No, work's without any problems here. I have the same setting as you: x86_64 without testing. -- Gruß, Johannes Täglich http://blog.hehejo.de und du fühlst dich gut. Mast und Schotbruch mit dem http://segelsport-blog.de. Just as a note, there's a forum thread marked with this same issue. Thought I'd link it so that any definitive solution might be shouted over there as well. I think the OP has 32 bit. I have i686 and did not have a problem with the upgrade, but I am running testing. http://bbs.archlinux.org/viewtopic.php?id=77119
[arch-general] postgresql 8.4
what's the status of getting this into extra's? all it seems to require is a typical version bump (outside of the xml bug). It appears to work ok on x86_64 on my system. although I haven't done super thorough testing. -- Caleb Cushing http://xenoterracide.blogspot.com
Re: [arch-general] Xorg broken after last update
2009/8/1, Luís Moreira lmm1...@gmail.com: Hello. The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. Anyone experienced the same thing? It works fine here. I'm using x86_64, nvidia, without testing. -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
Re: [arch-general] Xorg broken after last update
Hi, I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you. Edgar Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís Moreira: Hello. The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. Anyone experienced the same thing? Best regards, Luís Moreira. signature.asc Description: This is a digitally signed message part.
Re: [arch-general] Xorg broken after last update
If notebook includes HP Pavilion dv8000 laptop with GEFORCE GO 7600 NVIDIA graphics card (why do they capitalize *everything*?), and you're asking referring to i686, then yes, it seems to be fine, for me. :-) On Sat, Aug 1, 2009 at 6:28 PM, Edgar Kalkowski em...@edgar-kalkowski.dewrote: Hi, I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you. Edgar Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís Moreira: Hello. The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. Anyone experienced the same thing? Best regards, Luís Moreira.
Re: [arch-general] Xorg broken after last update
2009/8/1, Luís Moreira lmm1...@gmail.com: nvidia Are you using nvidia-185.18.31-1? -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
Re: [arch-general] postgresql 8.4
Em Sábado 01 Agosto 2009, às 19:12:27, Caleb Cushing escreveu: what's the status of getting this into extra's? all it seems to require is a typical version bump (outside of the xml bug). It appears to work ok on x86_64 on my system. although I haven't done super thorough testing. Hi, Im working on it.
Re: [arch-general] Xorg broken after last update
Yes. I believe that is the latest one, since pacman -Syu shows nothing needs updates. Correct? On Sat, Aug 1, 2009 at 6:33 PM, Giovanni Scafora giova...@archlinux.orgwrote: 2009/8/1, Luís Moreira lmm1...@gmail.com: nvidia Are you using nvidia-185.18.31-1? -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
Re: [arch-general] Xorg broken after last update
2009/8/1, Muhammad Qadri muhammad.a.qa...@gmail.com: Yes. I believe that is the latest one, since pacman -Syu shows nothing needs updates. Correct? Yeah, nvidia-185.18.31-1 is the latest one. I am also using x86_64 (without testing) and kernel 2.6.30.4-1 -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
Re: [arch-general] Xorg broken after last update
On Sun, 2 Aug 2009 00:28:42 +0200 Edgar Kalkowski em...@edgar-kalkowski.de wrote: Hi, I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you. Edgar Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís Moreira: Hello. The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. Anyone experienced the same thing? Best regards, Luís Moreira. Correct, I'm using a laptop with a NVIDIA GEFORCE GO 7300 graphics card. On Sat, 1 Aug 2009 15:33:33 -0700 Giovanni Scafora giova...@archlinux.org wrote: 2009/8/1, Luís Moreira lmm1...@gmail.com: nvidia Are you using nvidia-185.18.31-1? Yes, I updated to that version, the latest ones. Best regards, Luís Moreira.
Re: [arch-general] Xorg broken after last update
On Sunday 02 August 2009 00:28:42 Edgar Kalkowski wrote: Hi, I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. This bug was related only to nvidia-beta, release 190.16 and it was fixed in version 190.18. It has never touched the stable drivers. (Btw I was trying to track down some informations now abput 190.16, but it seems guys from nVidia removed the announcement thread from nvnews.net and nvidia.com drivers pages are out of order (E404) :-) ) I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you. Edgar Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís Moreira: Hello. The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. Anyone experienced the same thing? Best regards, Luís Moreira. -- - Dan Vrátil vra...@progdansoft.com ICQ 249163429 Jabber prog...@jabber.cz Tel. +420 732 326 870 http://www.progdan.homelinux.net signature.asc Description: This is a digitally signed message part.
Re: [arch-general] Xorg broken after last update
Am oder ungefähr am Sonntag, 02. August 2009, um 02:02:21 schrieb Dan Vratil: I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. This bug was related only to nvidia-beta, release 190.16 and it was fixed in version 190.18. It has never touched the stable drivers. That is good to hear. In this case I’ll upgrade my drivers right away. :) Edgar signature.asc Description: This is a digitally signed message part.
Re: [arch-general] Xorg broken after last update
I can confirm this issue for my notebook. Downgrading to the previous version of nvidia and nvidia-utils (version 185.18.14-1) fixed the issue. Graphics Processor: Quadro NVS 140M -Tim Edgar Kalkowski wrote: Hi, I somewhere read something about the latest nvidia driver being broken for notebook chips. I’m not sure if this is correct or was just an issue with the beta drivers but especially as you mention that it worked again after changing to vesa drivers I thought this might be the case here. I’m using nvidia drivers for my notebook as well but have not yet updated them because I read that it might cause problems. Are you, too, running a notebook? If so I’d be interested to hear if the latest nvidia drivers work ok for you. Edgar Am oder ungefähr am Samstag, 01. August 2009, um 23:58:58 schrieb Luís Moreira: Hello. The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. Anyone experienced the same thing? Best regards, Luís Moreira. signature.asc Description: OpenPGP digital signature
