Is it safe to upgrade to KDE 3.3 with this apt-listbugs report?
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is it safe to upgrade to KDE 3.3 with this apt-listbugs report?
Here is the report:
critical bugs of gcc-3.3 (1:3.3.4-13 -> 1:3.3.5-5) <done>
#286239 - gcc-3.3: I think sizeof(struct xxx) return wrong size
critical bugs of perl (5.8.4-3 -> 5.8.4-5) <done>
#263759 - perl: [5.8.4] "Bizarre copy of ARRAY in aassign" for empty scoped arr
ay initilisation
Merged with: 275298
grave bugs of libgcc1 (1:3.4.2-2 -> 1:3.4.3-6) <done>
#283031 - libgcc1: Missing Depends: libunwind7 [ia64] breaks many things
grave bugs of gcc-3.3 (1:3.3.4-13 -> 1:3.3.5-5) <done>
#286500 - gcc-3.3: gcc is not able to find any .h file that resides in a dir un
der /usr/include
critical bugs of libc6 (2.3.2.ds1-18 -> 2.3.2.ds1-20) <open>
#288948 - libc6: Bug (+fix) in readdir() due to getdents()
critical bugs of perl (5.8.4-3 -> 5.8.4-5) <open>
#286905 - perl-modules: File::Path::rmtree makes setuid
Merged with: 286922
grave bugs of libc6 (2.3.2.ds1-18 -> 2.3.2.ds1-20) <open>
#279680 - libc6: CAN-2004-0968 not fixed in woody
grave bugs of imagemagick (6:6.0.6.2-1.5 -> 6:6.0.6.2-1.6) <open>
#268357 - imagemagick: Buffer overflows in several coders (fixed in unstable).
grave bugs of perl (5.8.4-3 -> 5.8.4-5) <open>
#231082 - spamassassin: spamc hangs since most recent perl package updates for
stable
#283320 - perl FTBFS on mipsel/lasat, but not on mipsel/cobalt
#285435 - perl: silent write error can lead to data loss, with patch
grave bugs of libstdc++5 (1:3.3.4-13 -> 1:3.3.5-5) <open>
#288817 - apt-get and aptitude segfault on hppa
Summary:
libgcc1(1 bug), libc6(2 bugs), imagemagick(1 bug), gcc-3.3(2 bugs), perl(5 bugs
), libstdc++5(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
Will my system brake with critical bugs on gcc-3.3 and libc6 ? Should I wait till this is fixed or is there a way to upgrade without upgrading these ( I think they are depends. though..)
I don't know for sure but I think that bugs marked as <done> should be safe to install while bugs that are still marked as <open> are the ones to be avoided.
I wouldn't install ANY packages that are reported to contain critical or grave bugs -- unless I think it's abolutely necessary, or if it's obvious to me that those bugs won't actually affect my system (some bugs may only affect some specific architecture, for example).
In time all reported bugs will get fixed and apt-listbugs will stop warning about them. However, if you get impatient and install packages that are known to contain bugs... well, at least you have been warned.
Are you saying that apt-get dist-upgrade removed your kde installation? You know, apt-get prints a warning message before installing, upgrading, or removing any packages. Usually apt-get also asks your permission before proceeding. These messages are well worth reading.
Personally I use aptitude (with the ncurses menu interface) to manage installing/upgrading/removing packages because aptitude will always show the list of planned changes before it proceeds to execute them. I find that I get better control over any possible changes using aptitude.
Actually I sometimes use also apt-get but only for a special purpose. Apt-get installs by default only the depends while the default action for aptitude is to install also the recommends. Now, if aptitude shows that some package has tons of recommends (like gdeskcal has just two python depends but aptitude wants to install also gdesklets plus lots of useless gnome libraries as recommends), then I install the package with apt-get. But I always use aptitude (with the menu interface) for upgrading and removing packages.
Debian has some really smart tools for package management (apt-get, apt-listbugs, aptitude). Learn to use them and there'll be less nasty surprises.
Thanks for the info. I think I will wait for the packages to be fixed, then upgrade. I am glad there is such a thing as apt-listbugs or I would be installing critical bugged packages all the time
Is there a difference between syanptic and aptitude. I like both but synaptic makes it easier to highlight multiple packages at a time instead of going through one by one. (take forever if you try to install kde and don't know how to highlight multiple packages)
Some time ago I used to use Synaptic, too, but back then Synaptic tended to crash quite often. And the search function is very slow in Synaptic. On the other hand, Synaptic has some nice features, like editor for sources.list. It's a matter of taste which you happen to prefer -- both are very nice tools.
yeah, it removed my kde installation, I thought it was going to update it, it was installing kde packages and I assumed it was re-installing but aperently not.
Just did a dist-upgrade (3.2 - 3.3) with Synaptic and it was a flawless transition -- no broken packages. Started kdm, logged in to my profile, and all was good.
3.3 seems as solid and with a few cosmetic differences. Konqueror renders pages it choked on before and RSS now appears in the status bar as it should. Actually, there was a boatload of updates so I have yet to try all of the new K apps. Finally, K3B 0.11.18! I'm very pleased.
As an aside, I had installed Xfce 4.2 RC3 from oscillation's debian repo to do the upgrade. I had no idea what a marvelous light-weight desktop Xfce now is. It's definitely going on those Win98 rejects piling up in the basement.
yeah, just updated again (i used dselect this time, chose kde-core, etc.) and now it looks like I have a working kde again, I haven't tried it yet, but I didn't get any dependancy errors so...
Originally posted by towjamb Just did a dist-upgrade (3.2 - 3.3) with Synaptic and it was a flawless transition -- no broken packages. Started kdm, logged in to my profile, and all was good.
3.3 seems as solid and with a few cosmetic differences. Konqueror renders pages it choked on before and RSS now appears in the status bar as it should. Actually, there was a boatload of updates so I have yet to try all of the new K apps. Finally, K3B 0.11.18! I'm very pleased.
As an aside, I had installed Xfce 4.2 RC3 from oscillation's debian repo to do the upgrade. I had no idea what a marvelous light-weight desktop Xfce now is. It's definitely going on those Win98 rejects piling up in the basement.
Three cheers for the Debian team. Sarge rocks!
How did you just upgrade kde by itself in synaptic? I have just started using it and I found I had to go through and check every individual kde package and uncheck the regular upgrades not of kde.
I simply updated my entire system, as I do most every week, and KDE was part of it. However, one could just update kdelibs and only KDE and its dependencies would be upgraded.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.