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

Re: [arch-general] [arch-dev-public] makepkg.conf settings - Was:[signoff] pacman 3.3.0
by Gerardo Exequiel Pozzi 03 Aug '09

03 Aug '09

Allan McRae wrote: > Dan McGee wrote: >> Allan (and others)- I added a carbon copy version of makepkg.conf to >> SVN. Do we want to establish (1) Arch LDFLAGS or (2) Arch integrity >> check policy? >> > > Here go my recommendations: > > 1) Arch LDFLAGS: -Wl,--hash-style=gnu -Wl,--as-needed > There are very few problems with --as-needed these days and several > other distros are using it to. You can always do an somthing like > export LDFLAGS="" if it fails (much like is done when our CFLAGS cause > issues. The -Wl,--hash-style=gnu will cause us not to have sysv > hashes in our packages (we currently patch gcc to have both so > building without makepkg will be unaffected). > > For LDFLAGS agree with you, but maybe is secure to also add -Wl,--no-undefined , so I guess the linked can report undefined symbols in regular object files. (I can't remember now, but without this flag and with --as-needed some packages not build, but this was before the recent as-needed patch to binutils) I think that is sane to add to CFLAGS -Wall (and with more reason with latest gcc, and only produce more/equal build msg output), why this? Many apps already setup this flag in Makefiles, but others no. Do you remember the issue with mysql corruption because strict-aliasing? This can be detected at build time if -Wall was present. Of course at this time many packages are rebuilded, but only god knows what os these have an strict-aliasing issue, and is problematic. My two cents, -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D

1 0

Re: [arch-general] [arch-dev-public] [signoff] pacman 3.3.0
by Gerardo Exequiel Pozzi 03 Aug '09

03 Aug '09

Dan McGee wrote: > Signoff for pacman/makepkg 3.3.0. Notable things: > > * once this goes in, we can officially start doing split packaging and > build()/package() usage in our PKGBUILDs. > * this is basically a signoff for libfetch too, and you can remove > libdownload from your system. > > Allan (and others)- I added a carbon copy version of makepkg.conf to > SVN. Do we want to establish (1) Arch LDFLAGS or (2) Arch integrity > check policy? > > -Dan > > oops! pacman-3.3.0-1-i686 : makepkg.conf looks bad CARCH="x86_64" CHOST="x86_64-unknown-linux-gnu" CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe" CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe" -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D

1 0

Re: [arch-general] How does pacbuild work?
by Dominik Schips 02 Aug '09

02 Aug '09

Hello Allan, Am Sonntag, den 02.08.2009, 19:45 +1000 schrieb Allan McRae: > > Maybe I can make it direct accessible but first I want to know > > if it is really necessary. > > FYI, I have not seen talk about this in a couple of years. So I guess > this project got disbanded. Ok, thank you for this information and the fast reply. Thought Arch Linux is using build farms for all the packages to build after I read about pacbuild in the wiki. -- Best regards Dominik Schips

1 0

[arch-general] How does pacbuild work?
by Dominik Schips 02 Aug '09

02 Aug '09

Hello, I want to know if it is necessary for pacbuild (strawberry daemon) to be accessible direct by IP/DNS of the apple daemon? As I read here http://wiki.archlinux.org/index.php/Pacbuild_Explained I thing it should be direct acessible but I am not sure. "Apple is the main server. PKGBUILDs are submitted here, and apple does the dirty work of contacting build machines and telling them to do work." The problem is that the possible build machine (x86_64) I want to offer the project is in a DMZ which is not direct accessible. Only outgoing traffic is allowed. Maybe I can make it direct accessible but first I want to know if it is really necessary. -- Best regards Dominik Schips

2 1

Re: [arch-general] Xorg broken after last update
by Luís Moreira 01 Aug '09

01 Aug '09

On Sun, 2 Aug 2009 00:28:42 +0200 Edgar Kalkowski <eMail(a)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 <giovanni(a)archlinux.org> wrote: > 2009/8/1, Luís Moreira <lmm1987(a)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.

1 0

[arch-general] postgresql 8.4
by Caleb Cushing 01 Aug '09

01 Aug '09

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

2 1

Re: [arch-general] [arch-dev-public] news item draft: /dev layout cleanup
by Gerardo Exequiel Pozzi 01 Aug '09

01 Aug '09

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

1 0

Re: [arch-general] [arch-dev-public] news item draft: /dev layout cleanup
by Rogutės Sparnuotos 01 Aug '09

01 Aug '09

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

2 1

[arch-general] Arch doc inclusion policy
by Sven-Hendrik Haase 01 Aug '09

01 Aug '09

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

2 1

[arch-general] how to migrate installs between hard drives?
by Will Siddall 01 Aug '09

01 Aug '09

I know this isn't particularly an arch question, but I know Arch people are better off to ask then most. I'm in the process of upgrading my hard drive in my laptop but with the amounts of customizations I've done to my setup, I don't want to have to set it all up again. I know about running dd to copy the partition information, but the problem with that is that it also copies that partition information over. So, if I copy my root partition that started as a 40G partition with 90% used and now I have a 60G parition, the used portion will be kept at 90% so, it'll show something like 50G of data... which doesn't make sense. I've also just tried copying the partitions to an external, mount the iso's in a livecd session then copy the data over, but for some reason after I modified the menu.lst and fstab files to match my new setup and then restart, the computer doesn't boot. Is there something I'm missing in the second instance that I didn't change a file that should be changed? Is there a better way of copying the partitions so I don't run into this problem? Thanks, Will

26 44