Re: safe to upgrade sid?
I had this problem on a newly installed machine, but I solved it by downgrading kdelibs4 and kdelibs-bin to 3.3.2-6.1. kmail now does not segfault. I await 3.4.1 with interest. David On Saturday 16 July 2005 02:16, Tim Folger wrote: > Has anyone upgraded sid within the last few days without encountering the > segfault with kmail? Does the upgrade still break kmail? > > Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OT: Package stability (was: Re: safe to upgrade sid?)
On Sunday 17 July 2005 11:35 am, Anders Breindahl wrote: ... > All that is well known. The morale is, that I still shouldn't suggest > Unstable to users I help install, and that I really should consider > Testing myself. I assume that such ``errors'' as kmail breaking would be > considered rather important to fix straightaway, if they should emerge in > Testing..? > > Regards, Anders Breindahl. Well, if such an error emerged in testing, it would take even longer to fix, as the fix would first have to go through unstable. This is exactly the reason testing is often considered safer in regard to package stability, though - hopefully all errors such as this will turn up in unstable and therefore the broken package will not make it into testing. Josh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
OT: Package stability (was: Re: safe to upgrade sid?)
On Saturday 16 July 2005 21:00, Adeodato Simó wrote: > * Anders Breindahl [Sat, 16 Jul 2005 19:37:40 +0200]: > > It is rather disturbing, that errors in libraries in unstable is not > > prioritized any higher than the ongoing transitions. > > Sorry, but if this fuckup has not been fixed already is because it > can't be fixed without major pain, due to GCC 4 being the default > compiler now. Thanks to those who pointed this out. That had passed my attention. I was merely providing the (thought-up) view of a user, who didn't understand how his or her system broke because of a software update. The frustration is real, but if I worried about stability of packages, I shouldn't have gone with Unstable. I know that fact, but I just didn't know that I worried about the stability of packages. As is, I have become afraid of dist-upgrading: What is going to break this time? And I suppose that I am not the only wannabe-dev, who runs Unstable simply because of the version numbers it supplies. All that is well known. The morale is, that I still shouldn't suggest Unstable to users I help install, and that I really should consider Testing myself. I assume that such ``errors'' as kmail breaking would be considered rather important to fix straightaway, if they should emerge in Testing..? Regards, Anders Breindahl. pgp6LchxHU8Pb.pgp Description: PGP signature
Re: safe to upgrade sid?
* Anders Breindahl [Sat, 16 Jul 2005 19:37:40 +0200]: > It is rather disturbing, that errors in libraries in unstable is not > prioritized any higher than the ongoing transitions. Sorry, but if this fuckup has not been fixed already is because it can't be fixed without major pain, due to GCC 4 being the default compiler now. HTH, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 In my opinion, the most fruitful and natural play of the mind is in conversation. I find it sweeter than any other action in life; and if I were forced to choose, I think I would rather lose my sight than my hearing and voice. -- Michel de Montaigne -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: safe to upgrade sid?
On Saturday 16 July 2005 01:37 pm, Anders Breindahl wrote: > On Saturday 16 July 2005 05:11, Josh Metzler wrote: > > There is also the gcc 4.0 transition going on and the xfree86 -> x.org > > transition. The current plan is that qt3 and then kde 3.4 will be > > uploaded once x.org has built on all architectures. I plan to wait on > > upgrading anything x or kde related until kde 3.4 is available, > > assuming that that will indicate the transitions that affect me will > > be made. You may want to do the same. > > It is rather disturbing, that errors in libraries in unstable is not > prioritized any higher than the ongoing transitions. As I understand it, it isn't a matter of priorities, but that it is not possible to get a fixed kdelibs4 3.3.2 packages into sid. Since a number of the libraries that kdelibs depends on have made the gcc 4.0 transition already, kdelibs would be building against a mix of packages compiled with gcc 4.0 and others with 3.3. > You can of course upgrade, but you'll need to manually install the old > kdelibs-packages (-6.1). They'll be upgraded next time too, AFAIK. I did: # echo "kdelibs4 hold" | dpkg --set-selections # echo "kdelibs-data hold" | dpkg --set-selections Then once the transition is over, I will echo "kdelibs4 install" | dpkg --set-selections, and the same for kdelibs-data. That way I don't need to worry about forgetting and upgrading them. > Annoying. But then again, that's ``unstable'' for you. Actually, I haven't said yes to apt-get -u upgrade for a few weeks now, with all the transitions that are going on. I've been picking and choosing individual packages. It is a pain, but I chose it, I guess. Josh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: safe to upgrade sid?
Well, there is a certain logic to it. Sid is explicitly not intended for "production use" (although many, including myself, get away with it without too man problems). So, if given the choice between these two options: - Upgrade package XYZ - Switch to gcc 4 - Recompile/debug package XYZ under gcc 4 - Switch to Xorg - Recompile/debug package XYZ for Xorg -or- - Switch to gcc 4 - Switch to Xorg - Recompile/debug package XYZ for Xorg and gcc 4 It makes perfect sense that the Debian maintainers would go with the option that means less work for them but ends up in the same place in the end. The whole point of Sid is that they make that decision rather than the other way around. That's what "unstable" means in practice: Unsupported, bugs will get fixed when convenient for the maintainer, not when convenient for the user. On Saturday 16 July 2005 12:37 pm, Anders Breindahl wrote: > On Saturday 16 July 2005 05:11, Josh Metzler wrote: > > There is also the gcc 4.0 transition going on and the xfree86 -> x.org > > transition. The current plan is that qt3 and then kde 3.4 will be > > uploaded once x.org has built on all architectures. I plan to wait on > > upgrading anything x or kde related until kde 3.4 is available, assuming > > that that will indicate the transitions that affect me will be made. > > You may want to do the same. > > It is rather disturbing, that errors in libraries in unstable is not > prioritized any higher than the ongoing transitions. > > You can of course upgrade, but you'll need to manually install the old > kdelibs-packages (-6.1). They'll be upgraded next time too, AFAIK. > > Annoying. But then again, that's ``unstable'' for you. > > Regards, Anders Breindahl. -- Larry Garfield AIM: LOLG42 [EMAIL PROTECTED] ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: safe to upgrade sid?
On Saturday 16 July 2005 05:11, Josh Metzler wrote: > There is also the gcc 4.0 transition going on and the xfree86 -> x.org > transition. The current plan is that qt3 and then kde 3.4 will be > uploaded once x.org has built on all architectures. I plan to wait on > upgrading anything x or kde related until kde 3.4 is available, assuming > that that will indicate the transitions that affect me will be made. You > may want to do the same. It is rather disturbing, that errors in libraries in unstable is not prioritized any higher than the ongoing transitions. You can of course upgrade, but you'll need to manually install the old kdelibs-packages (-6.1). They'll be upgraded next time too, AFAIK. Annoying. But then again, that's ``unstable'' for you. Regards, Anders Breindahl. pgpKci2C1kdoX.pgp Description: PGP signature
Re: safe to upgrade sid?
Thanks for the advice, Josh and Larry. I think I will hold off on upgrading. Tim On Friday 15 July 2005 09:11 pm, Josh Metzler wrote: > On Friday 15 July 2005 09:16 pm, Tim Folger wrote: > > Has anyone upgraded sid within the last few days without encountering the > > segfault with kmail? Does the upgrade still break kmail? > > > > Tim > > There hasn't been any change in sid regarding kde libraries or kmail - the > kdelibs version that causes some people kmail segfaults is still there. > So, I would recommend you wait. > > There is also the gcc 4.0 transition going on and the xfree86 -> x.org > transition. The current plan is that qt3 and then kde 3.4 will be uploaded > once x.org has built on all architectures. I plan to wait on upgrading > anything x or kde related until kde 3.4 is available, assuming that that > will indicate the transitions that affect me will be made. You may want to > do the same. > > Josh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: safe to upgrade sid?
On Friday 15 July 2005 09:16 pm, Tim Folger wrote: > Has anyone upgraded sid within the last few days without encountering the > segfault with kmail? Does the upgrade still break kmail? > > Tim There hasn't been any change in sid regarding kde libraries or kmail - the kdelibs version that causes some people kmail segfaults is still there. So, I would recommend you wait. There is also the gcc 4.0 transition going on and the xfree86 -> x.org transition. The current plan is that qt3 and then kde 3.4 will be uploaded once x.org has built on all architectures. I plan to wait on upgrading anything x or kde related until kde 3.4 is available, assuming that that will indicate the transitions that affect me will be made. You may want to do the same. Josh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: safe to upgrade sid?
KMail is behaving itself for me (Sid + Alioth), but right now konq-plugins and kdeaddons are conflicting with each other, even though kdeaddons requires konq-plugins. :-) (I think it's because for some reason apt-get show gives konq-plugins 3.4.0pre2 while apt-get install gives konq-plugins 3.3.something. Not sure why). My sound system is also very jerky all of a sudden. I think at the moment, best advice is to not upgrade Sid until it has settled down more, unless you're fixing a specific problem. (Of course I now have several of my own doing. ) On Friday 15 July 2005 08:16 pm, Tim Folger wrote: > Has anyone upgraded sid within the last few days without encountering the > segfault with kmail? Does the upgrade still break kmail? > > Tim -- Larry Garfield AIM: LOLG42 [EMAIL PROTECTED] ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
safe to upgrade sid?
Has anyone upgraded sid within the last few days without encountering the segfault with kmail? Does the upgrade still break kmail? Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
