Hello !

when attempting to install kde, apt listbugs flags some bugs. some of them looking prerry bad ones.

Why has it been included into stable ?

Works here.
Maybe attach some errors your getting or the buglist for kde

My impression is that apt-listbugs is only useful when you run sid or etch? I'd be interested in seeing a report on what's so broken then in sarge. You'd expect sarge to not have really big errors. Anyway if this is the case and it aren't security risks (which will get updates) you're out of luck. Then you just have to install it or not.

Are you sure it is looking at Sarge? Check your source.list and make sure you do not have it pointed to Testing or Unstable.

Other than bugs still in KDE3.4; I don't think there are bugs in 3.3.2.

Better yet save the ram and install IceWM or XFCE.

Just because there's open bugs that doesn't mean it's broken, are you experiencing a specific problem or are you just scared to install because of the apt-listbugs output?

Here's the result from apt listbugs after running

# apt-get install kde

when retrieving the files it does pick them up from stable.

critical bugs of cvs (-> 1:1.12.9-13) <done>
#320019 - cvs import forgets files
grave bugs of kdenetwork (-> 4:3.3.2-5) <done>
#317087 - kdenetwork: upgrade causes a segmentation fault in KMail
grave bugs of xscreensaver (-> 4.21-3) <done>
#94300 - <TITLE>404 Not Found</TITLE>
Merged with: </BODY></HTML>
grave bugs of imagemagick (-> 6:6.0.6.2-2.4) <done>
#315013 - display command fails with "error while loading shared libraries"
critical bugs of libmailtools-perl (-> 1.62-1) <open>
#168381 - libmailtools-perl: mailx called from libmailtools-perl processes comm
ands in emails
critical bugs of ssh (-> 1:3.8.1p1-8.sarge.4) <open>
#314645 - /usr/sbin/sshd: time delay of password check proves account existence
to attackers
grave bugs of vim (-> 1:6.3-071+1) <open>
#320017 - vim: Arbitrary code execution in modelines
grave bugs of quanta (-> 1:3.3.2-6) <open>
#318658 - quanta truncates targets of symlinks to empty files (0 bytes)
grave bugs of kdebase (-> 4:3.3.2-1) <open>
#194248 - kde startup finishes at frozen root window
grave bugs of xscreensaver (-> 4.21-3) <open>
#319319 - xscreensaver: does not start: 'couldn't setgroups ... not permitted'
grave bugs of ssh (-> 1:3.8.1p1-8.sarge.4) <open>
#314289 - ssh: unable to login after upgrade to 4.1p1-3
grave bugs of kmail (-> 4:3.3.2-3) <open>
#315392 - kmail tries to access $HOME/Mail literally, and so fails to start
#317098 - Kmail segfaults at startup after minor upgrade of kdelibs4
#319135 - kmail: SIGSEGV QString::QString () from /usr/lib/libqt-mt.so.3
grave bugs of imagemagick (-> 6:6.0.6.2-2.4) <open>
#268357 - imagemagick: Buffer overflows in several coders (fixed in unstable).
#302093 - CAN-2005-0762: buffer overflow, code execution
grave bugs of juk (-> 4:3.3.2-1) <open>
#317423 - Juk crashes at startup
Summary:
kdenetwork(1 bug), vim(1 bug), quanta(1 bug), kdebase(1 bug), cvs(1 bug), xscre
ensaver(2 bugs), libmailtools-perl(1 bug), ssh(2 bugs), kmail(3 bugs), imagemagi
ck(3 bugs), juk(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]


does it look like minor bugs ??
i don't think so

Any ideas about what will be done ? and why they ended up in stable?

None of them are RC bugs, some of them only apply to testing and unstable.Security problems will get fixed by the Security Team.

Most of the open bugs are from unstable. And if they're marked done they've either been fixed or found to be a problem somewhere else.

This is a security problem not a functionality one, unless you have any custom mail tools using this perl library it won't affect you.

This is a security problem not a functionality one, it's a little easier for attackers to figure out what accounts are real and what aren't. If SSH is properly setup and your passwords are good this won't be an issue for you.

This is a security problem not a functionality one and the patch has been applied and a new version uploaded.

Don't use quanta to edit files via symlinks.

This bug is from 2003, I don't know why it got reopened.

xscreensaver works fine here, I suspect he has a problem with something else.

That appears to be a PAM problem, as long as you haven't messed with your PAM setup you should be fine.

These all appear to only affect unstable.

Security problems, I didn't read the specifics.

This appears to only affect unstable.

Did you actually read any of the bug reports?

Hello!

Thanks for the clarifications, I do read them but this still helps as I am might not always measure complely the impact they might have.

However, my point is I run apt-get install to pick up kde from stable. and when retrieving the packages it was picking up from ftp://...... stable.

So why do listbug quotes bugs from unstable ? what's the point of having listbugs if it doesn't actually flag the bugs for the package revision that you are actually going to install?!

How then, can we make sure when installing from stable/testing/unstable, which bug belongs to which? and which one would affect installation...

Thanks for clarifying this because I find this a bit confusing...

It's because listbugs is meant only for etch and sid. It's simple. Bugs that are in stable don't get fixed anymore unless it's a security fix.

i see...

- then, if apt listbug doesn't work for stable, why does it just remain quiet when installing from stable ??

- If installing from testing, would listbug still quote bugs from unstable as well?

- so how can we find out what bugs are left in stable before installing a package? - so that we can decide whether it is worth using testing instead (for a particular package) for example.

- also, is it one reason to use testing instead then ?


- is there any reason why to have listbug has not been implement to report correctly from stable instead of reporting bugs in testing and unstable when installing from stable ?

thanks for your help, i admit i don't understand this...

Maybe you should file a bug =)

maybe !

thanks anyway for the clues that you all provided. if you hear anything else related to this then let me know!

cheers.