Re: [Trisquel-users] Kernel Source package signature signed with unknown key 0x92D284CF33C66596

2016-02-07 Thread jason
1) Why does apt-get source fetch a different source package to the one named in the arg? Because the name of the source package is usually not the name of the binary package. And one source package could result in many binary packages. For example, when searching for packages on

[Trisquel-users] Kernel Source package signature signed with unknown key 0x92D284CF33C66596

2016-02-07 Thread jah
Two things I don't understand:- 1) Why does apt-get source fetch a different source package to the one named in the arg? 2) Why can't key 0x92D284CF33C66596 be found? $ apt-get source linux-image-3.13.0-76-generic Reading package lists... Done Building dependency tree Reading state

Re: [Trisquel-users] Kernel Source package signature signed with unknown key 0x92D284CF33C66596

2016-02-07 Thread jah
Thanks @jxself, good explanation. Is there a standard procedure for reporting the fact that the package downloaded by `apt-get source linux` (linux_3.13.0-77.121+7.0trisquel2) is signed with a key (0x92D284CF33C66596) for which no public cert appears to be available?