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 http://packages.trisquel.info/ this  
is why you have the option to search for "source package names."


Or why, when viewing a binary package, there is a link to the (differently  
named) source package. For example: Notice how  
http://packages.trisquel.info/belenos/emacs has a link called: [ Source:  
emacs-defaults  ] in the upper left.


So when you use apt-get source you should be plugging in the name of the  
source package but it seems smart enough to figure out the proper thing when  
you don't. :)


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?