[Bug 1370416] Re: Security updates are not marked as security

2018-04-08 Thread Bug Watch Updater
** Changed in: aptitude (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to muon in Ubuntu. https://bugs.launchpad.net/bugs/1370416 Title: Security updates are not marked as security To manage

[Bug 1370416] Re: Security updates are not marked as security

2018-04-08 Thread Axel Beckert
** Bug watch added: Debian Bug tracker #895217 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895217 ** Also affects: aptitude (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895217 Importance: Unknown Status: Unknown -- You received this bug notification

Re: [Bug 1370416] Re: Security updates are not marked as security

2018-04-08 Thread Axel Beckert
Hi, Rolf Leggewie wrote: > I would look into pinning, can this possibly help here? No, this has nothing to do with pinning at all. This is a known issue with aptitude. Have a look at the function is_security() in src/generic/apt/apt.cc: aptitude only regards as security update if the repository

[Bug 1370416] Re: Security updates are not marked as security

2018-04-08 Thread Rolf Leggewie
I would look into pinning, can this possibly help here? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to muon in Ubuntu. https://bugs.launchpad.net/bugs/1370416 Title: Security updates are not marked as security To manage notifications

[Bug 1370416] Re: Security updates are not marked as security

2014-10-05 Thread Vdragon
@xor Hi, my theory is it's probably not possible for the apt and its front-ends to determine which update was security update after the update has been moved to -updates channel(until the developers decided to change the 'move-to-updates' policy), I suggest you to upgrade all packages no matter