Packagers gcc/glibc update information

[blackhole]

uuuuuu ..... yeah !!
Thank you tex. Time to play with kmplayer and kdebluetooth4 ....

[daniel]

Question  Roll Eyes
Only for kde4 or for 3.5 also?

its for all apps in the repository ..that includes both kde4 and kde3..

..... and lxde and gnome and ...............

Really?
Really, really?
etc...
Great news and thanks for replay, and and and  

[gseaman]

These are exciting days!!

Galen

[newmikey]

YES!!!

I can finally use RawTherapee 2.4.1 ! (and a whole sh!tload of other stuff that needed an updated libstdc++)

It just goes to show that good things come to those who wait patiently. Cannot begin to tell you how much I appreciate this!

[Old-Polack]

does this mean it will be possible to do an upgrade without wiping out the current install and install 2010? what technical problem will prevent this from happening? applications compiled against the current glibc/gcc should be able to work with the new set

Yes

is it ok to update these two packages now on a "production" machine? ..any particular reason why not if the answer is no?

Not sure just yet. Still testing on various installs. So far all apps work fine. Only issue I think so far is if you don't have your box set to localtime an incorrect symlink is set in /etc folder.  Locales also need to be checked.

For what it's worth, I updated to jrd's gcc 4.3.2 and glibc 2.9 back on July 4, and ran until yesterday with that, without any problems whatever, on my main desktop. Updated again yesterday, to gcc 4.4.1 and glibc 2.10.1. Update went smoothly, and so far haven't had any issues with any installed applications. Seems very solid.

[coffeetime]

For what it's worth, I updated to jrd's gcc 4.3.2 and glibc 2.9 back on July 4, and ran until yesterday with that, without any problems whatever, on my main desktop. Updated again yesterday, to gcc 4.4.1 and glibc 2.10.1. Update went smoothly, and so far haven't had any issues with any installed applications. Seems very solid.

O-P!!

It's always very good to hear something like this. You guys are awesome.

[gseaman]

Ok, I'm jumping in with one of my older computers and if all is well I'm upgrading my laptop. This is another great technical achievement in Linux history, right up there with installable LiveCD's.

Galen

[Old-Polack]

For what it's worth, I updated to jrd's gcc 4.3.2 and glibc 2,9 back on July 4, and ran until yesterday with that, without any problems whatever, on my main desktop. Updated again yesterday, to gcc 4.4.1 and glibc 2.10.1. Update went smoothly, and so far haven't had any issues with any installed applications. Seems very solid.

O-P!!

It's always very good to hear something like this. You guys are awesome.

Just to clarify, I have 9 PCLOS installations on this machine, all completely backed up with rsync, so if I blow one up, it's no big deal to boot to another, and rsync the backup copy to the partition that went pear shaped.

If someone does want to test this, it's still recommended to do so on a separate test installation, rather than on one's only stable installation. The test installation can be a fresh installation from an official released, or a remastered disk, or an rsynced copy, of one's main installation, done from the liveCD on the non running main installation.

The more installations the rolling upgrade of the PCLOS core is tried on, the more chances of any problems being detected, and on what specific hardware those problems might show up on, should any be reported. Only by testing, and the reporting of any problems, can any bugs found be addressed and fixed.

For the record this installation is a fully upgraded TR6 installation, with the testing section always enabled, on the following hardware; (Not a VM)

Gigabyte GA-MA770-DSP3 motherboard with AMD/ATI chipset
AMD 64 x2 5200+ CPU
4GB RAM
500 watt PS
1 IDE hard drive
2 SATA hard drives
1 IDE optical device (DVD +/- R/RW writer)

[coffeetime]

If someone does want to test this, it's still recommended to do so on a separate test installation, rather than on one's only stable installation.

Some of us have testing puters 

For the record this installation is a fully upgraded TR6 installation, with the testing section always enabled, on the following hardware; (Not a VM)

Voodoo?

[Joble]

I think TR6 was actually better than 2009.  I used it for a long time.  Of course 2009.1 put it to shame.

Uh, now I'm using 2010, of course.  Would you expect any less from me?

[gseaman]

If someone does want to test this, it's still recommended to do so on a separate test installation, rather than on one's only stable installation.

I'll only test on systems I can afford to lose. If I have a problem, I'll test again with a clean install just to be sure.

Galen

[Old-Polack]

I think TR6 was actually better than 2009.  I used it for a long time.  Of course 2009.1 put it to shame.

Uh, now I'm using 2010, of course.  Would you expect any less from me?

I like seeing this part. 

[root@fatman ~]# cat /etc/release
PCLinuxOS release 2010 (PCLinuxOS) for i586

[Hootiegibbon]

I think TR6 was actually better than 2009.  I used it for a long time.  Of course 2009.1 put it to shame.

Uh, now I'm using 2010, of course.  Would you expect any less from me?

I like seeing this part. 

[root@fatman ~]# cat /etc/release
PCLinuxOS release 2010 (PCLinuxOS) for i586

O-P

$ cat /etc/release
PCLinuxOS release 2010 (PCLinuxOS) for i586

...........yup it does provide a good buzz......

only issue I have come across is loosing wireless (looks like looses connection tio the wpa_supplicant socket when leaving sleep mode) but I can look at that another time.

Jase

[Joble]

Did you say wireless Hootiegibbon?  Let's do this thang!

[Hootiegibbon]

Did you say wireless Hootiegibbon?  Let's do this thang!

Joble!!,

Looks like the wpa_supplicant socket 'connection' gets 'lost' either as it goes to sleep or wakes up - all ok after a reboot - have seen this behavior before in the forums - just need to find the thread - may have been davecs that noted it last.

I suspect that on sleeping it breaks the connection to the wpa_supplicant socket, but leaves the socket there so that on wake up it see's there is an existing wpa_supplicant process running, so the new one fails. will investigate to see if this a one off

Jase