Re: Bug#931506: linux-base: "are are" in man 1 perf

2019-07-06 Thread Richard Hector
On 7/07/19 9:48 AM, Ivan Kharpalev wrote: > -Performance counters for Linux are are a new kernel\-based subsystem > -that provide a framework for all things performance analysis. It > +Performance counters for Linux are a new kernel\-based subsystem > +that provide a framework for performance ana

linux-image-4.19.0-0.bpo.1-amd64 unsigned only?

2019-01-15 Thread Richard Hector
Sorry if I missed previous discussion on this. I seem to only see linux-image-4.19.0-0.bpo.1-amd64-unsigned (and the virtual package) for this version? Is that deliberate? (There are cloud, rt and dbg packages as well) This seems to also result in the kernel being tainted (8192 - An unsigned mod

Re: Wishlist meta-bug? Explain 'unsigned' in package name

2016-09-29 Thread Richard Hector
On 30/09/16 00:09, Ben Hutchings wrote: >>> Anyway, it seems unfortunate that there now appears to be no >>> trustworthy bpo kernel for those of us with needy hardware :-( > This should get sorted out by the end of the week. Great, thanks :-) Richard

Re: Wishlist meta-bug? Explain 'unsigned' in package name

2016-09-28 Thread Richard Hector
On 29/09/16 01:05, Ben Hutchings wrote: > On Wed, 2016-09-28 at 14:01 +1300, Richard Hector wrote: >> Hi - I can create a bug for this if required, but it seems a bit >> meta and trivial. >> >> Can the description of packages with '-unsigned' in the n

Wishlist meta-bug? Explain 'unsigned' in package name

2016-09-27 Thread Richard Hector
Hi - I can create a bug for this if required, but it seems a bit meta and trivial. Can the description of packages with '-unsigned' in the name include an explanation of what 'unsigned' means in this context? I understand now it relates to Secure Boot, but initially I was worried that I was insta

Old bug returned?

2009-06-23 Thread Richard Hector
Hi, I'm a little out of my depth here, so not jumping in and filing a bug report. I've got a problem that looks very similar to this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336424 which was fixed back in 2005. I tried looking at the diff of what changed then, but it appears that those