Re: How Buster release may affect Unstable?

On Mon, Jul 1, 2019, 13:51 Brian wrote: > On Mon 01 Jul 2019 at 13:24:48 -0400, Default User wrote: > > > Hi. > > > > Easy question, maybe hard to answer . . . > > > > Is someone has an existing conventional Unstable setup (nothing exotic in > > hardware

Re: How Buster release may affect Unstable?

On Mon 01 Jul 2019 at 13:24:48 -0400, Default User wrote: > Hi. > > Easy question, maybe hard to answer . . . > > Is someone has an existing conventional Unstable setup (nothing exotic in > hardware or software), what if any special actions should be taken before,

How Buster release may affect Unstable?

Hi. Easy question, maybe hard to answer . . . Is someone has an existing conventional Unstable setup (nothing exotic in hardware or software), what if any special actions should be taken before, during, or after the impending release of the new Stable? (inb4: 1 - RTFM 2 - RTF release notes)

Re: Welke paketten komen uit unstable?

overigens wel op het scherm voorbij komen als ik een pakket installeer, ik zie daar dan zoiets: Ophalen:1 http://ftp.nl.debian.org/debian buster/main amd64 hello amd64 2.10-1+b1 [55,9 kB] Voor unstable + experimental ... # aptitude versions '~VCURRENT (~Aunstable|~Aexperimental) !~Atesting' --group

Re: Welke paketten komen uit unstable?

overigens wel op het scherm voorbij komen als ik een >> pakket installeer, ik zie daar dan zoiets: >> Ophalen:1 http://ftp.nl.debian.org/debian buster/main amd64 hello >> amd64 2.10-1+b1 [55,9 kB] > > Voor unstable + experimental ... > > # aptitude versions '~VCURRENT

Re: Welke paketten komen uit unstable?

daar dan zoiets: > Ophalen:1 http://ftp.nl.debian.org/debian buster/main amd64 hello > amd64 2.10-1+b1 [55,9 kB] Voor unstable + experimental ... # aptitude versions '~VCURRENT (~Aunstable|~Aexperimental) !~Atesting' --group-by=none Met vriendelijke groet, -- Frans van Berckel Media En

Re: Welke paketten komen uit unstable?

gt; > Ik zie het overigens wel op het scherm voorbij komen als ik een > > pakket installeer, ik zie daar dan zoiets: > > Ophalen:1 http://ftp.nl.debian.org/debian buster/main amd64 hello > > amd64 2.10-1+b1 [55,9 kB] > > Voor unstable + experimental ... > > # apt

Re: Welke paketten komen uit unstable?

Op 23-02-19 om 18:32 schreef Luuk: > > On 22-2-2019 13:30, Paul van der Vlis wrote: >> Hoi, >> >> Ik ben op zoek naar een commando om er achter te komen welke pakketten >> op mijn systeem uit unstable komen. Weet iemand hier dat misschien? >> >> Ach

Re: Welke paketten komen uit unstable?

On 22-2-2019 13:30, Paul van der Vlis wrote: Hoi, Ik ben op zoek naar een commando om er achter te komen welke pakketten op mijn systeem uit unstable komen. Weet iemand hier dat misschien? Achtergrond: ik heb op een computer Debian 10 geinstalleerd, en een paar pakketten uit unstable. Ik

Welke paketten komen uit unstable?

Hoi, Ik ben op zoek naar een commando om er achter te komen welke pakketten op mijn systeem uit unstable komen. Weet iemand hier dat misschien? Achtergrond: ik heb op een computer Debian 10 geinstalleerd, en een paar pakketten uit unstable. Ik denk het niet, maar misschien is er bij het upgraden

Re: Unstable update ridiculousness

On Thu, Sep 20, 2018, 18:39 Ben Caradoc-Davies wrote: > On 21/09/2018 07:51, Default User wrote: > > Using advice given, using apt-listings and aptitude full-update, l was > able > > to update everything except the 3 packages in question, which are now > > "pinned", with a priority of 3000. > >

Re: Unstable update ridiculousness

On 21/09/2018 07:51, Default User wrote: Using advice given, using apt-listings and aptitude full-update, l was able to update everything except the 3 packages in question, which are now "pinned", with a priority of 3000. I find apt-mark hold more convenient than pinning. I do have both cron

Re: Unstable update ridiculousness

> > > Hi guys. Thank you for your replies. Please note that I am really not familiar with either cron or (especially) with package pinning. Using advice given, using apt-listings and aptitude full-update, l was able to update everything except the 3 packages in question, which are now "pinned",

Re: Unstable update ridiculousness

On Thu, Sep 20, 2018 at 08:17:51AM -0500, John Hasler wrote: > didier gaumet writes: > > Please note that security updates for "unstable" distribution are not > > managed by the security team. Hence, "unstable" does not get security > > updates in

Re: Unstable update ridiculousness

didier gaumet writes: > Please note that security updates for "unstable" distribution are not > managed by the security team. Hence, "unstable" does not get security > updates in a timely manner. There is no promise of security updates to Unstable but in practice the

Re: Unstable update ridiculousness

On Thu, 20 Sep 2018 13:26:05 +1200 Ben Caradoc-Davies wrote: > Read the bug reports and decide whether any of them will hurt you: > > On 20/09/2018 12:54, Default User wrote: > > grave bugs of libtracker-sparql-2.0-0 (2.0.3-3 → 2.1.4-1) > > b1 - #908800 - nautilus: can't use nautilus without >

Re: Unstable update ridiculousness

On Wed, 19 Sep 2018 21:16:30 -0400 Default User wrote: > On Wed, Sep 19, 2018 at 9:05 PM John Hasler > wrote: > > > You are running Unstable. It can be like that. > > -- > > John Hasler > > jhas...@newsguy.com > > Elmwood, WI USA > > >

Re: Unstable update ridiculousness

Le 20/09/2018 à 03:16, Default User a écrit : >  182 packages? from https://www.debian.org/releases/sid/ : "The unstable distribution ("sid") The code name for Debian's development distribution is "sid", aliased to "unstable". Most of the development wo

Re: Unstable update ridiculousness

Read the bug reports and decide whether any of them will hurt you: On 20/09/2018 12:54, Default User wrote: grave bugs of libtracker-sparql-2.0-0 (2.0.3-3 → 2.1.4-1) b1 - #908800 - nautilus: can't use nautilus without tracker If you use nautilus, "apt-get install tracker". serious bugs

Re: Unstable update ridiculousness

On Wed, Sep 19, 2018 at 9:05 PM John Hasler wrote: > You are running Unstable. It can be like that. > -- > John Hasler > jhas...@newsguy.com > Elmwood, WI USA > > 182 packages?

Re: Unstable update ridiculousness

You are running Unstable. It can be like that. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Unstable update ridiculousness

Hey guys, running Debian Unstable. This is ridiculous: --- user@user:~$ sudo aptitude -Pvv update [sudo] password for user: Get: 1 http://ftp.us.debian.org/debian unstable InRelease [233 kB] Get: 2 http

Re: Getting packages from stable again instead of unstable

On 7/21/2018 11:14 PM, Rick Macdonald wrote: On 19/07/18 12:19 PM, Dan Ritter wrote: I would do the downgrades. Then do an "apt-get clean", and after that, re-install firefox-esr. If you want an up-to-date firefox, install it directly from Mozilla in /opt/firefox. Thanks to Dan, Jochen and

Re: Getting packages from stable again instead of unstable

On 19/07/18 12:19 PM, Dan Ritter wrote: I would do the downgrades. Then do an "apt-get clean", and after that, re-install firefox-esr. If you want an up-to-date firefox, install it directly from Mozilla in /opt/firefox. Thanks to Dan, Jochen and songbird for the advice to do the downgrade. I

Re: Getting packages from stable again instead of unstable

Rick Macdonald wrote: > I'm going to pose my question here at the top in case it can be answered > without wading through all the details that follow: > > Now that I have removed unstable form sources.list and preferences > (pinning), won't my packages from unstable eventually b

Re: Getting packages from stable again instead of unstable

rom stable as the stable versions become newer than the unstable packages that I currently have installed? Or might I hit some dependency problems along the way? Should I instead do the downgrades now by pinning stable to priority 1001 (with I'm guessing is a one-time thing to do, and then remove t

Re: Getting packages from stable again instead of unstable

Rick Macdonald: > > Now that I have removed unstable form sources.list and preferences > (pinning), won't my packages from unstable eventually be upgraded from > stable as the stable versions become newer than the unstable packages that I > currently have installed? Yes, "

Re: Getting packages from stable again instead of unstable

On Thu, Jul 19, 2018 at 10:43:51AM -0600, Rick Macdonald wrote: > I'm going to pose my question here at the top in case it can be answered > without wading through all the details that follow: > > Now that I have removed unstable form sources.list and preferences > (pinning), wo

Getting packages from stable again instead of unstable

I'm going to pose my question here at the top in case it can be answered without wading through all the details that follow: Now that I have removed unstable form sources.list and preferences (pinning), won't my packages from unstable eventually be upgraded from stable as the stable versions

Re: KDE 4.4.3 in unstable

Am Donnerstag 06 Mai 2010 schrieb Boyd Stephen Smith Jr.: > > However, whether to ship akonadi trunk/beta/final of the next version > > is another question which is still open. In my opinion, Akonadi > > itself is > > > > pretty mature so it might be doable. > > I didn't complain well. This is

Re: KDE 4.4.3 in unstable

Am Donnerstag 06 Mai 2010 schrieb Modestas Vainius: > Hello, > > On ketvirtadienis 06 Gegužė 2010 23:48:43 Boyd Stephen Smith Jr. wrote: [...] > > > YOU assume that your truth is an ultimate one. > > > > Not really. I made objective statement about KMail based on > > observable facts. I also

Re: color unstable under jessie

On Saturday 05 May 2018 18:11:18 tom arnall wrote: > Greetings! > > over the last few weeks i've been having trouble on my system with > color. the color on the screen becomes very unstable, and keeps going > into a state where most of the color is pink. has anyone else had

Re: color unstable under jessie

On Sat, 5 May 2018 15:11:18 -0700 tom arnall said: > the color on the screen becomes very unstable, and keeps going into a state > where most of the color is pink. My monitor sometimes tends to get fluctuating, weak, or lost blue signal, which results in yellowish tendency. It is pr

Re: color unstable under jessie

On Sat 05 May 2018 at 15:11:18 (-0700), tom arnall wrote: > over the last few weeks i've been having trouble on my system with > color. the color on the screen becomes very unstable, and keeps going > into a state where most of the color is pink. has anyone else had this > probl

Re: color unstable under jessie

tom arnall composed on 2018-05-05 15:11 (UTC-0700): > over the last few weeks i've been having trouble on my system with > color. the color on the screen becomes very unstable, and keeps going > into a state where most of the color is pink. has anyone else had this > problem. IME t

Re: color unstable under jessie

On Sat, May 5, 2018, 6:11 PM tom arnall <kloro2...@gmail.com> wrote: > Greetings! > > over the last few weeks i've been having trouble on my system with > color. the color on the screen becomes very unstable, and keeps going > into a state where most of the color is pink

color unstable under jessie

Greetings! over the last few weeks i've been having trouble on my system with color. the color on the screen becomes very unstable, and keeps going into a state where most of the color is pink. has anyone else had this problem. Regards, Tom Arnall

Re: Hoe kan ik nagaan dat ik iets van unstable heb geïnstalleerd

On woensdag 28 maart 2018 09:59:22 CEST Cecil Westerhof wrote: > Volgens mij heb ik echter niets geïnstalleerd van unstable en zou ik > het dus moeten kunnen verwijderen. Hoe verifieer ik dit? aptitude search '?narrow(~i,?archive(unstable))' signature.asc Description: This is a digitally

Re: Hoe kan ik nagaan dat ik iets van unstable heb geïnstalleerd

Heiko <heiko.noord...@xs4all.nl> writes: > On 2018-03-28 09:59, Cecil Westerhof wrote: >> In mijn sources.list heb ik: >> deb http://deb.debian.org/debian unstable main contrib non-free >> >> Volgens mij heb ik echter niets geïnstalleerd van unstable e

Re: Hoe kan ik nagaan dat ik iets van unstable heb geïnstalleerd

On 2018-03-28 09:59, Cecil Westerhof wrote: In mijn sources.list heb ik: deb http://deb.debian.org/debian unstable main contrib non-free Volgens mij heb ik echter niets geïnstalleerd van unstable en zou ik het dus moeten kunnen verwijderen. Hoe verifieer ik dit? Het eenvoudigst is denk ik

Hoe kan ik nagaan dat ik iets van unstable heb geïnstalleerd

In mijn sources.list heb ik: deb http://deb.debian.org/debian unstable main contrib non-free Volgens mij heb ik echter niets geïnstalleerd van unstable en zou ik het dus moeten kunnen verwijderen. Hoe verifieer ik dit? -- Cecil Westerhof Senior Software Engineer LinkedIn: http

Re: Unstable Wayland in Debian Testing

On Wed, Mar 14, 2018 at 06:22:03PM +, 慕 冬亮 wrote: > Dear all, > > Debian Testing for now has a very unstable wayland. I have encountered > dozens of crashes about current Wayland during those months. > > When I connect or disconnect an external screen monitor, usb driv

Unstable Wayland in Debian Testing

Dear all, Debian Testing for now has a very unstable wayland. I have encountered dozens of crashes about current Wayland during those months. When I connect or disconnect an external screen monitor, usb driver, or even one phone, the desktop environment could crash. And then I login and found

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27/01/2018 22:47, Michael Lange wrote: Hi, On Sat, 27 Jan 2018 22:30:06 +0530 "tv.deb...@googlemail.com" wrote: Hi, you need to read the kernel-package doc, it requires configuration. Read at the minimum /usr/share/doc/kernel-package/README.gz It contains all the

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Hi, On Sat, 27 Jan 2018 22:30:06 +0530 "tv.deb...@googlemail.com" wrote: > Hi, you need to read the kernel-package doc, it requires configuration. > Read at the minimum /usr/share/doc/kernel-package/README.gz > It contains all the info you need, and even gives you

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

and that you are the package maintainer for kernel-source ie make-kpkg etc. within debian. I am running debian unstable (Sid)on an amd64 kaveri box. I installed GCC 8 from the experimental repository. I am trying to use it to compile the kernel 4.14.15 using make-kpkg to use the fixes for the meltdown

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

* Dear Sir, I understand that you are the package maintainer for kernel-source ie make-kpkg etc. within debian. I am running debian unstable (Sid)on an amd64 kaveri box. I installed GCC 8 from the experimental repository. I am trying to use it to compile the kerne

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27 January 2018 at 13:38, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 13:12:13 + > Michael Fothergill wrote: > > > ​I think I will sign up on the gcc gnu help page and ask people if they > > have a test case file I can run to

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

had went away. ​ I think now GCC 8 is close to working OK. Perhaps it needs another little nudge or some other package we don't know about. I have sent the gnu gcc help people the following email: ** Dear All, I am running debian unstable on an amd64 kaveri

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27 January 2018 at 13:17, Michael Lange wrote: > On Sat, 27 Jan 2018 12:32:24 + > Michael Fothergill wrote: > > > On 27 January 2018 at 11:59, Michael Lange wrote: > > > > > Hi, > > > > > > On Sat, 27 Jan 2018

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Hi, On Sat, 27 Jan 2018 13:12:13 + Michael Fothergill wrote: > ​I think I will sign up on the gcc gnu help page and ask people if they > have a test case file I can run to 100% confirm the GCC 8 compiler is > running properly.​ > ​Once I am convinced it is then

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27 January 2018 at 12:43, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 12:12:57 + > Michael Fothergill wrote: > > > > > ​Should the filename be something like linux-image-4.14.14.deb etc? > > With default settings for make-kpkg

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Sat, 27 Jan 2018 12:32:24 + Michael Fothergill wrote: > On 27 January 2018 at 11:59, Michael Lange wrote: > > > Hi, > > > > On Sat, 27 Jan 2018 11:26:25 + > > Michael Fothergill wrote: > > > > > > > >

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

It does seem as if make-kpkg has gone awol here. MF

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27 January 2018 at 12:43, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 12:12:57 + > Michael Fothergill wrote: > > > > > ​Should the filename be something like linux-image-4.14.14.deb etc? > > With default settings for make-kpkg

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27 January 2018 at 11:59, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 11:26:25 + > Michael Fothergill wrote: > > > > > Where would the default location of such a file be if were created using > > the make-kpkg command? > > the

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Hi, On Sat, 27 Jan 2018 12:12:57 + Michael Fothergill wrote: > > ​Should the filename be something like linux-image-4.14.14.deb etc? With default settings for make-kpkg the filename is probably a little longer, here it looks like

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27 January 2018 at 12:12, Michael Fothergill < michael.fotherg...@gmail.com> wrote: > > > On 27 January 2018 at 11:59, Michael Lange wrote: > >> Hi, >> >> On Sat, 27 Jan 2018 11:26:25 + >> Michael Fothergill wrote: >> >> > >> > Where

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27 January 2018 at 11:59, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 11:26:25 + > Michael Fothergill wrote: > > > > > Where would the default location of such a file be if were created using > > the make-kpkg command? > > the

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 27 January 2018 at 11:26, Michael Fothergill < michael.fotherg...@gmail.com> wrote: > When you install the kernel, the following page ( > https://www.debian.org/releases/jessie/i386/ch08s06.html.en) says you > must run the following command: > > *​dpkg -i

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Hi, On Sat, 27 Jan 2018 11:26:25 + Michael Fothergill wrote: > > Where would the default location of such a file be if were created using > the make-kpkg command? the package should be in the source's parent directory, in your case I guess in /usr/src .

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

When you install the kernel, the following page ( https://www.debian.org/releases/jessie/i386/ch08s06.html.en) says you must run the following command: *​dpkg -i ../linux-image-3.16-subarchitecture_1.0.custom_i386.deb*. ​Do I need to run mrproper beforehand? I can't see any linux-image file in

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 25 January 2018 at 23:28, Michael Lange wrote: > Hi, > > On Thu, 25 Jan 2018 22:23:38 + > Michael Fothergill wrote: > > > Dear All, > > > > I am continuing the discussion of the kernel 4.14.15 compilation in the > > Question on

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 26 January 2018 at 22:59, Michael Lange wrote: > On Fri, 26 Jan 2018 23:41:07 +0100 > Michael Lange wrote: > > > When I check /proc/cpuinfo I see that "msr" is listed in the "flags" > > section. So why doesn't the driver load automagically? > > But

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, 26 Jan 2018 23:49:46 +0100 Sven Hartge wrote: > Michael Lange wrote: > > > When I check /proc/cpuinfo I see that "msr" is listed in the "flags" > > section. So why doesn't the driver load automagically? > > It is not programmed to load

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, 26 Jan 2018 23:41:07 +0100 Michael Lange wrote: > When I check /proc/cpuinfo I see that "msr" is listed in the "flags" > section. So why doesn't the driver load automagically? > But then, at least with the version of the checker-script here, it > doesn't seem to

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Michael Lange wrote: > When I check /proc/cpuinfo I see that "msr" is listed in the "flags" > section. So why doesn't the driver load automagically? It is not programmed to load automatically, because writing to MSRs is dangerous and can even damage your computer or CPU.

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, 26 Jan 2018 12:45:13 -0500 Greg Wooledge wrote: > On Fri, Jan 26, 2018 at 06:07:13PM +0100, Michael Lange wrote: > > I am definitely anything but an expert on this; but with sid's 4.14.15 > > (which I assumed was compiled with said gcc-7.2) the script here says: > >

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, 26 Jan 2018 23:25:55 +0100 Sven Hartge wrote: > Do the contents of the /dev/cpu directory change between loaded and > unloaded msr.ko? > > When msr.ko is loaded, there should be directory for each CPU in the > system: > > # ls -ld /dev/cpu/* > drwxr-xr-x 2 root root

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Michael Lange wrote: > Yes, it is the sid kernel, and the module exists. When running the > script as root it is the same. lsmod shows that the msr module is not > loaded. If I load it manually with modprobe it appears to load without > errors, but the output of the

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, 26 Jan 2018 21:28:19 +0100 Sven Hartge wrote: > > Not me, that's the sid kernel :) > > No. The kernel from Sid has support for MSR as module: > > root@host:~# modinfo msr > filename: /lib/modules/4.14.0-3-amd64/kernel/arch/x86/kernel/msr.ko > license:GPL >

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Michael Lange wrote: > On Fri, 26 Jan 2018 18:38:23 +0100 Sven Hartge wrote: >> Michael Lange wrote: >>> Hardware check >>> * Hardware support (CPU microcode) for mitigation techniques >>> * Indirect Branch Restricted

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, 26 Jan 2018 18:38:23 +0100 Sven Hartge wrote: > Michael Lange wrote: > > > Hardware check > > * Hardware support (CPU microcode) for mitigation techniques > > * Indirect Branch Restricted Speculation (IBRS) > > * SPEC_CTRL MSR is

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

​Dear All, I have decided to get rid of GCC8 using ML's helpful command suggestion. I will install gcc 7 again as sid and try again with kernel 4.14.15. ​Cheers MF >

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, Jan 26, 2018 at 06:07:13PM +0100, Michael Lange wrote: > I am definitely anything but an expert on this; but with sid's 4.14.15 > (which I assumed was compiled with said gcc-7.2) the script here says: You shouldn't have to assume. /proc/version tells you which compiler was used.

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Hi, On Fri, 26 Jan 2018 22:48:51 +0530 "tv.deb...@googlemail.com" wrote: > > Tested with upstream vanilla 4.14.15 compiled with current Sid gcc-7.3, > i get a pass for Spectre v2 (full generic retpoline) and Meltdown > (a.k.a. "v3"). > > Spectre v1 is still

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Michael Lange wrote: > Hardware check > * Hardware support (CPU microcode) for mitigation techniques > * Indirect Branch Restricted Speculation (IBRS) > * SPEC_CTRL MSR is available: UNKNOWN (couldn't > read /dev/cpu/0/msr, is msr support enabled in your kernel?)

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 26 January 2018 at 17:18, tv.deb...@googlemail.com < tv.deb...@googlemail.com> wrote: > On 26/01/2018 22:37, Michael Lange wrote: > >> On Fri, 26 Jan 2018 22:19:27 +0530 >> "tv.deb...@googlemail.com" wrote: >> >> >>> gcc-7[.2] was really gcc-7.3-rc for a while, and

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

e: >> >> Hi, sorry to jump into the thread this late, I didn't follow the >>> beginning. You can save yourself quite a bit of hassle by downloading >>> the upstream up-to-date vanilla kernel 4.15-rc9 and compile that with >>> Unstable gcc-7. All you need is t

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 26/01/2018 22:37, Michael Lange wrote: On Fri, 26 Jan 2018 22:19:27 +0530 "tv.deb...@googlemail.com" wrote: gcc-7[.2] was really gcc-7.3-rc for a while, and was doing a good job at enabling Spectre mitigation (as tested by the spectre-meltdown-checker and

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 26 January 2018 at 16:37, Greg Wooledge wrote: > On Fri, Jan 26, 2018 at 04:17:27PM +, Michael Fothergill wrote: > > ​Is the sid gcc now 7.3 as someone said earlier even though it says it is > > 7.2? > > Sid apparently has both "gcc" and "gcc-7" packages. > >

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, 26 Jan 2018 22:19:27 +0530 "tv.deb...@googlemail.com" wrote: > > gcc-7[.2] was really gcc-7.3-rc for a while, and was doing a good job > at enabling Spectre mitigation (as tested by the > spectre-meltdown-checker and /sys/devices/system/cpu/vulnerabilities/* >

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

nto the thread this late, I didn't follow the >>> beginning. >>> You can save yourself quite a bit of hassle by downloading the upstream >>> up-to-date vanilla kernel 4.15-rc9 and compile that with Unstable gcc-7. >>> All you need is there already and you will

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

the upstream up-to-date vanilla kernel 4.15-rc9 and compile that with Unstable gcc-7. All you need is there already and you will get as good a mitigation for Spectre as one can get right now. well, I just saw that gcc-7.3 arrived in sid today, so at least the issues with gcc-8 from experimental se

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

p-to-date vanilla kernel 4.15-rc9 and compile that with > > Unstable gcc-7. All you need is there already and you will get as > > good a mitigation for Spectre as one can get right now. > > > ​Is the 7.2 kernel in sid gcc 7 really gassed up enough to compile the > spectr

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

pstream >> up-to-date vanilla kernel 4.15-rc9 and compile that with Unstable gcc-7. >> All you need is there already and you will get as good a mitigation for >> Spectre as one can get right now. > > > ​Is the 7.2 kernel in sid gcc 7 really gassed up enough to compi

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

e vanilla kernel 4.15-rc9 and compile that with > Unstable gcc-7. All you need is there already and you will get as good > a mitigation for Spectre as one can get right now. well, I just saw that gcc-7.3 arrived in sid today, so at least the issues with gcc-8 from experimental seem to be history

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On Fri, Jan 26, 2018 at 04:17:27PM +, Michael Fothergill wrote: > ​Is the sid gcc now 7.3 as someone said earlier even though it says it is > 7.2? Sid apparently has both "gcc" and "gcc-7" packages. https://packages.debian.org/sid/gcc shows version 7.2.0-1d1.

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

>> > Hi, sorry to jump into the thread this late, I didn't follow the beginning. > You can save yourself quite a bit of hassle by downloading the upstream > up-to-date vanilla kernel 4.15-rc9 and compile that with Unstable gcc-7. > All you need is there already and yo

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

ive term. -- Spock, "Friday's Child", stardate 3499.1 Hi, sorry to jump into the thread this late, I didn't follow the beginning. You can save yourself quite a bit of hassle by downloading the upstream up-to-date vanilla kernel 4.15-rc9 and compile that with Unstable

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Hi, On Fri, 26 Jan 2018 14:05:12 + Michael Fothergill wrote: > > > > "make[2]: Entering directory '/usr/src/linux-4.14.15' > > Makefile:942: *** "Cannot generate ORC metadata for > > CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or > >

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

On 25 January 2018 at 23:28, Michael Lange wrote: > Hi, > > On Thu, 25 Jan 2018 22:23:38 + > Michael Fothergill wrote: > > > Dear All, > > > > I am continuing the discussion of the kernel 4.14.15 compilation in the > > Question on

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......

Hi, On Thu, 25 Jan 2018 22:23:38 + Michael Fothergill wrote: > Dear All, > > I am continuing the discussion of the kernel 4.14.15 compilation in the > Question on CVE-2017-5754 on Debian 8.9 post in a new post. > > The reason I am running with this kernel and

kernel 4.14.15 compilation using GCC 8 in unstable.......

Dear All, I am continuing the discussion of the kernel 4.14.15 compilation in the Question on CVE-2017-5754 on Debian 8.9 post in a new post. The reason I am running with this kernel and not the 4.15.0 rc9 kernel that is now available on kernel.org is that: 1. It is stable 2. I have never

Re: Emacs info documentation missing in Debian Unstable

davidson <david...@freevolt.org> wrote: > On Mon, 22 Jan 2018, davidson wrote: > > > On Mon, 22 Jan 2018, Nishan Singh Mann wrote: > > > >> Hello, on Ubuntu 17.10 which to my knowledge is based on Debian > >> unstable, installing Emacs via $sudo apt install em

Re: Emacs info documentation missing in Debian Unstable

On Mon, 22 Jan 2018, davidson wrote: On Mon, 22 Jan 2018, Nishan Singh Mann wrote: Hello, on Ubuntu 17.10 which to my knowledge is based on Debian unstable, installing Emacs via $sudo apt install emacs and then trying to view the Emacs manual using C-h r fails with error "Info file emacs

Re: Emacs info documentation missing in Debian Unstable

On Mon, 22 Jan 2018, Nishan Singh Mann wrote: Hello, on Ubuntu 17.10 which to my knowledge is based on Debian unstable, installing Emacs via $sudo apt install emacs and then trying to view the Emacs manual using C-h r fails with error "Info file emacs does not exist" Th

Re: Emacs info documentation missing in Debian Unstable

Nishan Singh Mann <nishan.singh.m...@gmail.com> writes: > Hello, on Ubuntu 17.10 which to my knowledge is based on Debian unstable, > installing Emacs via $sudo apt install emacs and then trying to view the > Emacs manual using C-h r fails with error "Info file emacs does not

Re: Emacs info documentation missing in Debian Unstable

On 22/01/18 15:33, Nishan Singh Mann wrote: Hello, on Ubuntu 17.10 which to my knowledge is based on Debian unstable, installing Emacs via $sudo apt install emacs and then trying to view the Emacs manual using C-h r fails with error "Info file emacs does not exist" Th

Emacs info documentation missing in Debian Unstable

Hello, on Ubuntu 17.10 which to my knowledge is based on Debian unstable, installing Emacs via $sudo apt install emacs and then trying to view the Emacs manual using C-h r fails with error "Info file emacs does not exist" The same set of instructions on Ubuntu 16.04 works and o

<    1   2   3   4   5   6   7   8   9   10   >