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 is from security.debian.org or
security.*.debian.org, at least in Debian.
So I assume that Ubuntu patches those lines towards
security.ubuntu.com as used in his German sources.list.
But his "central" sources.list doesn't have security.ubuntu.com
anywhere. He uses e.g. "deb http://archive.ubuntu.com/ubuntu
trusty-security main restricted" there. And hence it's not recognised.
I thought there was an upstream (Debian) bug report about that (as I
am aware of the issue :-), but I couldn't find it on a first glance.
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 apt/apt. cc: aptitude only regards as *.debian. org, at least in Debian.
is_security() in src/generic/
security update if the repository is from security.debian.org or
security.
So I assume that Ubuntu patches those lines towards
security.ubuntu.com as used in his German sources.list.
But his "central" sources.list doesn't have security.ubuntu.com archive. ubuntu. com/ubuntu
anywhere. He uses e.g. "deb http://
trusty-security main restricted" there. And hence it's not recognised.
I thought there was an upstream (Debian) bug report about that (as I
am aware of the issue :-), but I couldn't find it on a first glance.
Will file one and link it here.
Regards, Axel (with his aptitude hat on) /people. debian. org/~abe/
--
,''`. | Axel Beckert <email address hidden>, https:/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE