Thanks.
Muon is the default package manager and there's an update tray icon alert
thing in Kubuntu, so you might want to judge the priority which is not set yet
upon that.
FYI the issue still applies, today is day 3, so I would assume it really
is not a package server synchronization issue.
--
Thanks.
It has been 2 days now, and the package is still showed as NON-security on the
machine even though I have updated the package list just now.
No matter what possible technical explanations are, from a system
administrator's perspective, it is a bug if a security update is marked as
You will only see a security update in -security in the first few hours
after publication; depending upon a large number of variables it might
be visible in a mirror's -updates pocket within minutes or maybe a day
later. This is a one-way transition -- there's no point in checking
again once the
Ok I think I finally know where we are misunderstanding each other: I
am *NOT* using the URL to determine whether it is a security update!
I am talking about the fact that the user interface of aptitude has a
category Security updates and Upgradable packages. The package is
displayed at
Ah! That's the missing piece indeed. I've never used aptitude or muon so
I've never noticed the discrepancy.
Thanks
** Changed in: ubuntu
Status: Invalid = Confirmed
** Package changed: ubuntu = aptitude (Ubuntu)
** Also affects: muon (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Private Security to Public Security
** Changed in: ubuntu
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370416
Title:
Central and
Thanks for your concern; this is standard and expected behaviour. The
security.ubuntu.com server farm is fairly small and on limited bandwidth
compared to the wider Ubuntu mirror network so our security updates are
periodically copied into the -updates pocket for wider distribution and
mirroring.
Thanks but I don't quite understand what you're trying to say.
There are two interpretations of what you said:
1) Did you misread my report and thought I was complaining that one
machine does not see a security update yet while the other sees it?
That is NOT the case. They both see the same
It is normal for security updates to be copied to the -updates pocket of
the mirror network in order to provide better update availability and
speed to everyone.
We don't expect users to determine if an update is a security update
based on the URL where the package can be found.
Instead, our
