Public bug reported:

Binary package hint: kpackagekit

In Lucid kpackagekit shows a fix in the wrong group from time to time.
This is difficult to reproduce, because it depends on the package
versions installed and on the package versions available from the repos.
So in normal usage (i.e. if you don't downgrade packages) the same
problem will never appear twice.

Today I happen to have the issue for linux-generic:

$ apt-cache policy linux-generic
linux-generic:
  Installed: 2.6.32.24.25
  Candidate: 2.6.32.25.27
  Version table:
     2.6.32.25.27 0
        500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
 *** 2.6.32.24.25 0
        500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
        100 /var/lib/dpkg/status
     2.6.32.21.22 0
        500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages
$

The candidate version comes from lucid-updates, not from lucid security.
Still kpackagekit shows it as a security fix. See attached screen shot.
Note  that the version numbers in kpackagekit are equal to those shown
by apt-cache.

I will apport-collect this report ASAP in order to provide necessary version 
info.
--- 
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
Package: kpackagekit 0.5.4-0ubuntu4.3
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: kpackagekit (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-collected kubuntu

-- 
kpackagekit shows incorrect security classification
https://bugs.launchpad.net/bugs/649284
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kpackagekit in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

Reply via email to