Re: [gentoo-user] OT: latest longterm kernel.org patches are unsigned
On August 20, 2018 9:33:03 PM UTC, james wrote: >On 8/17/18 12:07 PM, Ian Zimmerman wrote: >> If you browse this URL: >> >> https://cdn.kernel.org/pub/linux/kernel/v4.x/ >> >> you'll see that for each 4.14 patch up to 4.14.58 there is a >> cooresponding GPG signature file: >> >> patch-4.14.58.sign 25-Jul-2018 09:28 833 >> patch-4.14.58.xz 25-Jul-2018 09:28 1M >> >> etc. >> >> But starting with 4.14.59, there are no .sign files. Why? Is this a >> bug, and if so, where do I report it? >> >> This breaks my lovingly duct-taped kernel update infrastructure ... >> > >Ian, > >Not sure this is related to your problem but it's an interesting read >about (intel) microcodes and current blocks being enforced by Gentoo, >clandestinely? > > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906158 > >https://bugs.gentoo.org/664134 > > >Apologies if I research is fragmented or flawed... > >hth, >James Interesting read. Can't update the bug at the moment, but downloading the microcode file worked and I didn't see any license agreement. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] OT: latest longterm kernel.org patches are unsigned
On 8/17/18 12:07 PM, Ian Zimmerman wrote: > If you browse this URL: > > https://cdn.kernel.org/pub/linux/kernel/v4.x/ > > you'll see that for each 4.14 patch up to 4.14.58 there is a > cooresponding GPG signature file: > > patch-4.14.58.sign 25-Jul-2018 09:28 833 > patch-4.14.58.xz 25-Jul-2018 09:28 1M > > etc. > > But starting with 4.14.59, there are no .sign files. Why? Is this a > bug, and if so, where do I report it? > > This breaks my lovingly duct-taped kernel update infrastructure ... > Ian, Not sure this is related to your problem but it's an interesting read about (intel) microcodes and current blocks being enforced by Gentoo, clandestinely? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906158 https://bugs.gentoo.org/664134 Apologies if I research is fragmented or flawed... hth, James
Re: [gentoo-user] python-3.6.5 rebuild fails on new install
On Mon, Aug 20, 2018 at 08:46:22AM +0300, Franz Fellner wrote > Seems to be a known issue and probably fixed in gcc-7.4.0: > https://bugs.gentoo.org/662208 > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83317 > > This error is also used in the Gentoo gcc internal compiler error > reporting wiki page: > https://wiki.gentoo.org/wiki/Gcc-ICE-reporting-guide Would it cause problems if I built python 3.6 with -mfpmath=387 as a temporary workaround? -- Walter Dnes I don't run "desktop environments"; I run useful applications
[gentoo-user] Re: Valgrind not seeing debug symbols
> On Aug 19, 2018, at 12:21, Andrew Udvare wrote: > > Hi all, > > I have this project https://github.com/Tatsh/gcrud and it uses a very > standard build process with CMake, but for some reason Valgrind never > sees the debug symbols. I created a basic Gentoo machine with a Vagrant box and set up a mini environment to test if it is just my machine. The symbols show up on the Vagrant box. It could be a bad version of Valgrind on my end but I haven’t compared the environments. My main system has something wrong. — Andrew
