Aside from the fact that Debian is designating 3.16+63 as an 11 day old candidate, 3.16-3 isn't really trying to update to 3.16+63. It's already happened. 3.16+63 is already in Testing.
you got it wrong. the candidate is the 4.0 ones. 3.16 is already in testing. note that the package version number and the kernel version is not same. if you take a look into the 4.0 series. the package name is 4.0.0 but the actual version is 4.0.2. the 3.16 name is "linux-image-3.16.0.-4-xxx" but the actual version is 3.16.7
to avoid confusion, let me state that what I mean by candidate is "packages in sid which haven't migrated to testing yet". if you have other definition of "candidate" please tell us to avoid misunderstanding.
I understand that 3.16+63 is designated as the candidate. My point is that it shouldn't be. 3.16+63 is already in Testing. If linux-tools was running behind the 4.0.2 kernel candidate (which is impossible, but just for argument's sake, let's say that was the case) and, say, 3.16+64 was the candidate, I would understand. In my mind, linux-tools 4.0+64 should be the candidate (from sid).
with my definition of candidate 3.16 isn't a testing candidate. 3.16+63 already in testing long time ago. the candidate is 4.0+64, not 3.16+64. 3.16+64 didn't exist on debian realm. here's the proof
Code: Select all
apt-cache policy linux-tools
Package pin: 3.16+63
*** 4.0+64 650
50 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
Perhaps because of the severity of the bug, the Debian "migration team" has forced 3.16+63 to be the candidate so as to make sure kernel 4.0.2 doesn't drop into Testing?
3.16 actually migrated into testing before stretch so that won't be the case.
I'm not quite sure why did this page https://release.debian.org/migration/te ... inux-tools
said that linux tools want to upgrade from 3.16-3 to 3.16+63. 3.16-3 is the version of the source code while the actual package is 3.16+63. 3.16-3 to 3.16+63 means no upgrade at all. it might caused by a mechanism to forcefully hold a package so that it won't move into testing. if you take a look into this page https://tracker.debian.org/pkg/linux-tools
linux-tools 4.0.2 is a valid candidate to migrate into testing. however, it must migrate into testing at exact same time with linux-kernel. if linux-tool 4.0.2 migrated into testing then it will broke the entire system. thus, the system overwrite the mechanism and stated that the next linux-tools candidate is 3.16+63 (which means no update at all). it's simply a mechanism crated to prevent a valid candidate to broke "testing" system.