Re: debian testing, confusing message during upgrade openjdk-17-jre-headless

Jonathan Dowland wrote: > On Wed Jan 29, 2025 at 10:52 AM GMT, songbird wrote: >> Setting up openjdk-17-jre-headless:amd64 (17.0.14+7-1) ... >> update-binfmts: warning: current package is openjdk-21, but binary format >> already installed by openjdk-9 > > What do you have in /usr/share/binfmts ?

Re: debian testing, confusing message during upgrade openjdk-17-jre-headless

On Wed Jan 29, 2025 at 10:52 AM GMT, songbird wrote: Setting up openjdk-17-jre-headless:amd64 (17.0.14+7-1) ... update-binfmts: warning: current package is openjdk-21, but binary format already installed by openjdk-9 What do you have in /usr/share/binfmts ? -- Please do not CC me for listmail

Re: debian testing, confusing message during upgrade openjdk-17-jre-headless

Cindy Sue Causey wrote: ... > In my case these days, I have two things I would do to take a poke at > this in hopes something obvious presents itself: > > $ apt-cache policy openjdk-9 > > I might even try the much busier "apt-cache policy openjdk-*" to see if > anything else is lingering. My setup

Re: debian testing, confusing message during upgrade openjdk-17-jre-headless

On 29/01/2025 17:52, songbird wrote: update-binfmts: warning: current package is openjdk-21, but binary format already installed by openjdk-9 Likely it is related to running of .jar files without explicit java command. In a similar way wine may install a handler for .exe files in addition to

Re: debian testing, confusing message during upgrade openjdk-17-jre-headless

On Wed, 2025-01-29 at 12:10 +, Brad Rogers wrote: > On Wed, 29 Jan 2025 05:52:34 -0500 > songbird wrote: > > Hello songbird, > > > warning: current package is openjdk-21, but binary format already > > installed by openjdk-9 > > I've seen similar messages.  Certainly about openjdk, maybe oth

Re: debian testing, confusing message during upgrade openjdk-17-jre-headless

On Wed, 29 Jan 2025 05:52:34 -0500 songbird wrote: Hello songbird, >warning: current package is openjdk-21, but binary format already >installed by openjdk-9 I've seen similar messages. Certainly about openjdk, maybe others, I can't recall. As everything seems to be working as expected, I don

Re: Debian testing is very slow on statup (boot), after upgrade to bookworm

On 16/11/2021 16:40, Marcelo Laia wrote: Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] vendor: Dell driver: amdgpu v: kern

Re: Debian testing (buster), "vfat not found"

On Sb, 12 ian 19, 17:11:11, Dan Marshall wrote: > Hi, first time caller... I know it's been several months... > Originally posted this is Linux Questions' Hardware subforum. Copying and > pasting the tasty bits: > > Trying to mount a thumb drive and an mp3 player under Debian testing > (buster)

Re: Debian testing - release number

On Wed 11 Jul 2018 at 11:53:29 (+), Curt wrote: > On 2018-07-10, David Wright wrote: Yes, I wrote a post on 2018-07-10 but you haven't quoted any of it here. > You following up to Woole[d]ge: > > Hmm, I struggle to see the connection between what I asked for and > what you wrote. From you

Re: Debian testing - release number

On 2018-07-10, David Wright wrote: You following up to Woolege: Hmm, I struggle to see the connection between what I asked for and what you wrote. From your later post, I guess the answer is that editing /etc/debian_version risks provoking expletives from other users of the system. That s

Re: Debian testing - release number

On Fri 06 Jul 2018 at 08:41:58 (+), Curt wrote: > On 2018-07-06, David Wright wrote: > > > Hmm, I struggle to see the connection between what I asked for and > > what you wrote. From your later post, I guess the answer is that > > editing /etc/debian_version risks provoking expletives from ot

Re: debian/testing repo question

On 7/10/18, The Wanderer wrote: > > (I'm really surprised to see someone with an @debian.org address > advising people to run unstable for any other reason than helping with > developing Debian. Cherry-picking a single package from unstable for > new-version reasons may be one thing, but tracking

Re: debian/testing repo question

On Tue, Jul 10, 2018 at 04:10:22PM +0200, Hans wrote: > > Most users I am supporting are using stable, but some are using testing. > Should I advise them to upgrade tu unstable? > For non-production use, unstable or testing should be fine. Both will be broken from time-to-time. The question is

Re: debian/testing repo question

On Tue, Jul 10, 2018 at 10:27:19AM -0400, The Wanderer wrote: > > (I'm really surprised to see someone with an @debian.org address > advising people to run unstable for any other reason than helping with > developing Debian. I say that because testing gets "stuck" in various ways. In particular,

Re: debian/testing repo question

> > For myself, I track stable+testing, dist-upgrade on at least a weekly > basis, and deal with occasional breakage when it happens. So do I. But in the past I (some years agho) I ran unstable but never got iun big trouble (I believe, I wa just luicky, wasn't I?) Best Hans

Re: debian/testing repo question

On 2018-07-10 at 10:10, Hans wrote: > Hi Robert, > > thanks for your quick response. So, doi I see this correct and can I > say: There is an automatismn for a package removal, which will be > interrupted, when the maintainer is responding within a period of > time and the reason for the removal w

Re: debian/testing repo question

Hi Robert, thanks for your quick response. So, doi I see this correct and can I say: There is an automatismn for a package removal, which will be interrupted, when the maintainer is responding within a period of time and the reason for the removal was eliminated (i.e. fixed a bug or uploaded a

Re: debian/testing repo question

On Tue, Jul 10, 2018 at 03:31:09PM +0200, Hans wrote: > Hi folks, > > I know, I had discussed a similar question ago, but testing is still a > miracle > for me. > > Is there an automatism, why or when packages got removed from testing or ist > this always done manually by the developers? > >

Re: Debian testing - release number

On 2018-07-09, Greg Wooledge wrote: > On Sat, Jul 07, 2018 at 07:55:26AM +, Curt wrote: >> On 2018-07-07, davidson wrote: >> > Speculation: I suspect that the listserv software escapes "From" after >> > a newline, and that its chosen escape is synonymous with the embedded >> > quote character

Re: Debian testing - release number

On Sat, Jul 07, 2018 at 07:55:26AM +, Curt wrote: > On 2018-07-07, davidson wrote: > > Speculation: I suspect that the listserv software escapes "From" after > > a newline, and that its chosen escape is synonymous with the embedded > > quote character.[1] > The culprit is therefore Wooledge h

Re: Debian testing - release number

On 2018-07-07, davidson wrote: > On Fri, 6 Jul 2018, Curt wrote: > >> On 2018-07-06, Greg Wooledge wrote: >>> From this, I conclude that Joey Hess is a skilled manipulator. >>> >> >> (I didn't say this.) > > Observation: That line begins with "From". > > Speculation: I suspect that the lists

Re: Debian testing - release number

On Fri, 6 Jul 2018, Curt wrote: On 2018-07-06, Greg Wooledge wrote: From this, I conclude that Joey Hess is a skilled manipulator. (I didn't say this.) Observation: That line begins with "From". Speculation: I suspect that the listserv software escapes "From" after a newline, and that

Re: Debian testing - release number

On 2018-07-06, The Wanderer wrote: > > On 2018-07-05 at 17:29, Nicholas Geovanis wrote: > >> But what I'm trying to point out here is that there seems to be no >> such canonical (sic) Debian tool which CAN tell me what release and >> version I'm running. > > That's not true. /etc/debian_version, i

Re: Debian testing - release number

On 2018-07-05 at 17:29, Nicholas Geovanis wrote: > But what I'm trying to point out here is that there seems to be no > such canonical (sic) Debian tool which CAN tell me what release and > version I'm running. That's not true. /etc/debian_version, if not modified by the sysadmin, should always

Re: Debian testing - release number

On 2018-07-06, Greg Wooledge wrote: > >>From this, I conclude that Joey Hess is a skilled manipulator. > (I didn't say this.)

Re: Debian testing - release number

On Fri, Jul 06, 2018 at 08:41:58AM +, Curt wrote: > So, Joey Hess is a crazy idiot, for instance? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81249 That was written in 2001. One hopes that he has learned something in the 17 years since then. I certainly have. Reading along to the

Re: Debian testing - release number

On 2018-07-06, David Wright wrote: > Hmm, I struggle to see the connection between what I asked for and > what you wrote. From your later post, I guess the answer is that > editing /etc/debian_version risks provoking expletives from other > users of the system. > > That said, I do agree with what

Re: Debian testing - release number

On Thu 05 Jul 2018 at 14:08:21 (-0400), Greg Wooledge wrote: > On Thu, Jul 05, 2018 at 12:57:34PM -0500, David Wright wrote: > > On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote: > > > On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote: > > > > But if you're a sysadmin who has

Re: Debian testing - release number

On Thu 05 Jul 2018 at 16:29:30 (-0500), Nicholas Geovanis wrote: > On Thu, Jul 5, 2018 at 3:46 PM Greg Wooledge wrote: > > > > On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote: > > > (1) You foolishly relied on the value in /etc/debian_version when > > > > It is not a fucking conf

Re: Debian testing - release number

On Thu, Jul 5, 2018 at 3:46 PM Greg Wooledge wrote: > > On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote: > > (1) You foolishly relied on the value in /etc/debian_version when > > It is not a fucking configuration file that you edit. > It is supposed to be read only. > Only a craz

Re: Debian testing - release number

On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote: > (1) You foolishly relied on the value in /etc/debian_version when It is not a fucking configuration file that you edit. It is supposed to be read only. Only a crazy idiot would manually edit the file that tells you what version

Re: Debian testing - release number

On Thu, 5 Jul 2018 14:57:03 -0500 Nicholas Geovanis wrote: > I am rightly accused of relying too heavily on /etc/debian_version to > detect my running release. But it seems clear > to me that the "right", canonical way to detect this is to query the > installed package base to extract a version/r

Re: Debian testing - release number

On Thu, Jul 5, 2018 at 3:16 PM Greg Wooledge wrote: > > On Thu, Jul 05, 2018 at 02:57:03PM -0500, Nicholas Geovanis wrote: > > So surely there is an > > "approved" tool for doing that. Hopefully OTHER THAN > > apt, aptitude, synaptic or apt-get; ideally simpler and easier to > > script than that.

Re: Debian testing - release number

On Thu, Jul 05, 2018 at 02:57:03PM -0500, Nicholas Geovanis wrote: > I am rightly accused of relying too heavily on /etc/debian_version to > detect my running release. But it seems clear > to me that the "right", canonical way to detect this is to query the > installed package base to extract a ver

Re: Debian testing - release number

I am rightly accused of relying too heavily on /etc/debian_version to detect my running release. But it seems clear to me that the "right", canonical way to detect this is to query the installed package base to extract a version/release number from a package name and/or version. So surely there is

Re: Debian testing - release number

On Thu, Jul 05, 2018 at 12:57:34PM -0500, David Wright wrote: > On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote: > > On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote: > > > But if you're a sysadmin who has a script that wants/needs a version > > > *number* for any reason, th

Re: Debian testing - release number

On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote: > On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote: > > But if you're a sysadmin who has a script that wants/needs a version > > *number* for any reason, then /etc/debian_version is the safest file > > to modify. > > I strong

Re: Debian testing - release number

On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote: > But if you're a sysadmin who has a script that wants/needs a version > *number* for any reason, then /etc/debian_version is the safest file > to modify. I strongly disagree. The safest file to modify would be the broken shell script

Re: Debian testing - release number

On Thu 05 Jul 2018 at 11:53:45 (+0100), Joe wrote: > On Thu, 5 Jul 2018 10:09:36 + (UTC) > Curt wrote: > > > > > > The problem I'm looking at is that the Debian testing/unstable > > releases do not have a version number and are not going to be > > receiving one any time soon (the tradition

Re: Debian testing - release number

On Thu 05 Jul 2018 at 12:58:21 (+1200), Richard Hector wrote: > On 05/07/18 03:53, David Wright wrote: > > On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote: > >> On 02/07/18 05:31, David Wright wrote: > >>> On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote: > On 28/06/18

Re: Debian testing - release number

On Wed, Jul 04, 2018 at 10:09:29AM -0500, David Wright wrote: > On Wed 04 Jul 2018 at 09:55:54 (+0900), John Crawley wrote: > > Sorry, but I thought a "configuration file" was supposed to > > influence the behaviour of _software_ in some way. Are files which > > only provide info for humans also co

Re: Debian testing - release number

On 2018-07-05, Joe wrote: > On Thu, 5 Jul 2018 10:09:36 + (UTC) > Curt wrote: > > >> >> The problem I'm looking at is that the Debian testing/unstable >> releases do not have a version number and are not going to be >> receiving one any time soon (the tradition of not according a number >> t

Re: Debian testing - release number

On Thu, 5 Jul 2018 10:09:36 + (UTC) Curt wrote: > > The problem I'm looking at is that the Debian testing/unstable > releases do not have a version number and are not going to be > receiving one any time soon (the tradition of not according a number > to these two releases being of the utmo

Re: Debian testing - release number

On 2018-07-05, Richard Hector wrote: > > Equally, if I want to know what the time is, I can ask you. > If you don't know, I can tell you. > Then I can ask you, and now you'll know, and I'll find out. > > Right? > > We must be looking at different problems. > > I'm assuming that if you're trying to

Re: Debian testing - release number

On 2018-07-05 09:58, Richard Hector wrote: On 05/07/18 03:53, David Wright wrote: On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote: On 02/07/18 05:31, David Wright wrote: On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote: On 28/06/18 16:40, David Wright wrote: On Wed 2

Re: Debian testing - release number

On 05/07/18 03:53, David Wright wrote: > On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote: >> On 02/07/18 05:31, David Wright wrote: >>> On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote: On 28/06/18 16:40, David Wright wrote: > On Wed 27 Jun 2018 at 19:49:13 (+0200)

Re: Debian testing - release number

On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote: > On 02/07/18 05:31, David Wright wrote: > > On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote: > >> On 28/06/18 16:40, David Wright wrote: > >>> On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote: > I am wonderi

Re: Debian testing - release number

On Wed 04 Jul 2018 at 09:55:54 (+0900), John Crawley wrote: > On 2018-07-02 02:31, David Wright wrote: > >What seems to be lost on people who feel a pressing need for > >/etc/debian_version to contain a number to satisfy some script that > >they have written (which seems to be the usual reason) is

Re: Debian testing - release number

On 02/07/18 05:31, David Wright wrote: > On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote: >> On 28/06/18 16:40, David Wright wrote: >>> On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote: I am wondering if it is possible to get the debian release number for debian te

Re: Debian testing - release number

On 2018-07-02 02:31, David Wright wrote: What seems to be lost on people who feel a pressing need for /etc/debian_version to contain a number to satisfy some script that they have written (which seems to be the usual reason) is that /etc/debian_version is a configuration file. I don't know of

Re: Debian testing - release number

On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote: > On 28/06/18 16:40, David Wright wrote: > > On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote: > >> I am wondering if it is possible to get the debian release number > >> for debian testing (and maybe sid) from command line? >

Re: Debian testing - release number

On 28/06/18 16:40, David Wright wrote: > On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote: >> I am wondering if it is possible to get the debian release number >> for debian testing (and maybe sid) from command line? > > Yes. > > # cat > /etc/debian_version > Write whatever you want he

Re: Debian testing - release number

On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote: > I am wondering if it is possible to get the debian release number > for debian testing (and maybe sid) from command line? Yes. # cat > /etc/debian_version Write whatever you want here ^D Job done. (That's a control-D.) Whether it's

Re: Debian testing - release number

On Wed, Jun 27, 2018 at 03:03:45PM -0500, Nicholas Geovanis wrote: > On Wed, Jun 27, 2018 at 12:49 PM Martin Krämer wrote: > > > > I am wondering if it is possible to get the debian release number for > > debian testing (and maybe sid) from command line? > > I know that current testing is codenam

Re: Debian testing - release number

On Wed, Jun 27, 2018 at 12:49 PM Martin Krämer wrote: > > I am wondering if it is possible to get the debian release number for debian > testing (and maybe sid) from command line? > I know that current testing is codename buster, while its release number is > 10. > I can get the codename from co

Re: Debian testing - release number

On Wed, 27 Jun 2018 19:49:13 +0200 Martin Krämer wrote: Hello Martin, >I know that current testing is codename buster, while its release >number is 10. My (possibly mistaken) understanding is that it will get the official release number 10 when buster becomes the stable branch of Debian. See h

Re: Debian testing not receivng packages at least in gnome.

On Wed, 16 May 2018 16:53:57 -0400 Cindy-Sue Causey wrote: > On 5/16/18, Matthew wrote: > > Afternoon all. > > > > > > A very strange problem that is very strange. I have two debian > > machines both with the testing repo as the sources from which I am > > using. One is using mate desktop and

Re: Debian testing not receivng packages at least in gnome.

On 5/16/18, Matthew wrote: > Afternoon all. > > > A very strange problem that is very strange. I have two debian machines > both with the testing repo as the sources from which I am using. One is > using mate desktop and the other is using gnome. I have the sources > list pointing to the testin

Re: Debian testing randomly freezes

Guilherme Vieira composed on 2016-10-06 01:23 (UTC-0300): Is this not the right list for these kinds of questions? 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 08) Have you seen anything like any of these? http://arstechnica.com/gadgets/2016/01/intel-skyl

Re: Debian testing randomly freezes

Is this not the right list for these kinds of questions? Atenciosamente / Sincerely, Guilherme Prá Vieira On Tue, Oct 4, 2016 at 2:49 AM, Guilherme Vieira wrote: > Hello. > > I've been using Debian testing for over a year without problems, but 5 or > 6 mont

Re: Debian Testing Cannot be installed on Hyper-V 2012 R2

On Thu, 2016-06-23 at 13:45 +0800, Larry Sevilla wrote: > Package: debian-installer > Version: debian-testing-i386-netinst.iso  dated 2016-06-20 07:33 > 391Mb > > I'm trying to install Debian Testing under Hyper-V Windows Server > 2012 R2. > > mem: Start-up 1024Mb Dynamic Min 512Mb Max 3584 > pro

Re: Debian Testing Cannot be installed on Hyper-V 2012 R2

On Tue, 21 Jun 2016, Larry Sevilla wrote: > I'm trying to install Debian Testing under Hyper-V Windows Server 2012 R2. > > iso file: debian-testing-i386-netinst.iso dated 2016-06-20 07:33 391Mb > > mem: Start-up 1024Mb Dynamic Min 512Mb Max 3584 > proc: 2 > vhd: 10Gb > > Install it using non-GU

Re: Debian Testing Cannot be installed on Hyper-V 2012 R2

On 6/20/16, Larry Sevilla wrote: > I'm trying to install Debian Testing under Hyper-V Windows Server 2012 R2. > > iso file: debian-testing-i386-netinst.iso dated 2016-06-20 07:33 391Mb > > mem: Start-up 1024Mb Dynamic Min 512Mb Max 3584 > proc: 2 > vhd: 10Gb > > Install it using non-GUI. > > Then

Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

Hello, El 29 de marzo de 2016 9:16:09 CEST, Sergei Petrunin escribió: >Thanks for response! > >Unfortunately, I have to report that doing > >sudo install-grub /dev/sda#/dev/sda is by device for hard-drive >with >lvm, may be I need some specific options here? >sudo upgrade-grub > >do not cure

Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

Thanks for response! Unfortunately, I have to report that doing sudo install-grub /dev/sda#/dev/sda is by device for hard-drive with lvm, may be I need some specific options here? sudo upgrade-grub do not cure boot for 4.4.0 kernel - same problem persists, still 4.3.0 kernel (in "Advanced GR

Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

On 2016-03-28 11:46:46 PM, Sergei Petrunin wrote: During the system boot I get the following message: Begin: Running /scripts/local-block ... lvmetad is not active yet sysinit Volume group "strog-vg" not found Cannot process volume group strog-vg done. --- several times message like this --- -

Re: Debian "testing" is looking really great on my new "Skylake" PC

On Jan 21, 2016 9:45 PM, "Patrick Bartek" wrote: > > Thanks. Based on your input (and others), I'm eliminated Acer from my > list. I, too, have experience with Thinkpads and Asus notebooks, and > have had few problems installing Linux on them. Since Dell has their > Ubuntu option, I'm thinking

Re: Debian "testing" is looking really great on my new "Skylake" PC

On Thu, 21 Jan 2016 00:30:03 +0100 Lisi Reisz wrote: > On Wednesday 20 January 2016 22:25:55 Charles Kroeger wrote: > > On Wed, 20 Jan 2016 08:50:02 +0100 > > > > Jarle Aase wrote: > > > I just wanted to share > > > > Where's Stan Hooper when you need him? I miss your hardware critiques Stan > >

Re: Debian "testing" is looking really great on my new "Skylake" PC

On Wed, 20 Jan 2016, Jarle Aase wrote: > > > Den 01/20/16 18:56, skrev Patrick Bartek: > > What if anything special like disabling Secureboot did you do to > > facilitate this painless install? > Nothing really. I specified "Other OS" and enabled virtualization - > that's all that I changed in

Re: Debian "testing" is looking really great on my new "Skylake" PC

On Wednesday 20 January 2016 22:25:55 Charles Kroeger wrote: > On Wed, 20 Jan 2016 08:50:02 +0100 > > Jarle Aase wrote: > > I just wanted to share > > Where's Stan Hooper when you need him? I miss your hardware critiques Stan > better weigh in here. Maybe we've lost him? I do hope not! But he d

Re: Debian "testing" is looking really great on my new "Skylake" PC

On Wed, 20 Jan 2016 08:50:02 +0100 Jarle Aase wrote: > I just wanted to share Where's Stan Hooper when you need him? I miss your hardware critiques Stan better weigh in here. -- CK

Re: Debian "testing" is looking really great on my new "Skylake" PC

On Wed, 2016-01-20 at 09:36 +0200, Jarle Aase wrote: > I built myself a new PC with an Intel i7-6700K ("Skylake" > architecture)  > - and I was prepared for lots of grief and trouble. However, > installing  > Debian "testing" yesterday, from the latest Amd64 snapshot, was  > absolutely painless. I

Re: Debian "testing" is looking really great on my new "Skylake" PC

Den 01/20/16 18:56, skrev Patrick Bartek: What if anything special like disabling Secureboot did you do to facilitate this painless install? Nothing really. I specified "Other OS" and enabled virtualization - that's all that I changed in the BIOS setup. I'm buying a new notebook as a replac

Re: Debian "testing" is looking really great on my new "Skylake" PC

On Wed, 20 Jan 2016, Jarle Aase wrote: > I built myself a new PC with an Intel i7-6700K ("Skylake" > architecture) > - and I was prepared for lots of grief and trouble. However, > installing Debian "testing" yesterday, from the latest Amd64 > snapshot, was absolutely painless. > > I'm using kde

Re: Debian testing crashes

On Wednesday 18 November 2015 16:06:12 Shaolintl . wrote: > Dear Debian users, > > Due to problems with my wifi card (Intel Corporation Wireless 7265) when > using the stable version of Debian, I have installed the testing version. > Since then, the system crashes randomly on an almost daily basis.

Re: debian/testing philosophie?

On Sat, Jan 10, 2015 at 02:09:02PM +0100, Hans wrote: > To all these thoughts, what do you advice me to install? Better unstable than > testing? I know, youi will now say "stable" but stable is sometimes just too > old for a desktop (for example I had problems with the installation on > notebook

Re: debian/testing philosophie?

Hans wrote: > I understand, that during freeze packages might disappear (due to > bugs). This can be an exception, when there is no time to fix a bug to > the release date, > But I watched this behaviour not only at the freeze period, this > happens unregularly. > Sometimes I found no reason, w

Re: debian/testing philosophie?

Hi Sven, the Wanderer! I understand, that during freeze packages might disappear (due to bugs). This can be an exception, when there is no time to fix a bug to the release date, But I watched this behaviour not only at the freeze period, this happens unregularly. Sometimes I found no reason, w

Re: debian/testing philosophie?

Hans wrote: > over the years i noticed, that from time to time packages disappearing > from the testing repo, but that packages are then still in stable and > in unstable. > That is weired for me, as I would suppose, that a package disappearing > in testin would also not to be found in unstable

Re: debian/testing philosophie?

On 01/10/2015 at 07:21 AM, Hans wrote: > Hi folks, > > over the years i noticed, that from time to time packages > disappearing from the testing repo, but that packages are then still > in stable and in unstable. > > That is weired for me, as I would suppose, that a package > disappearing in tes

Re: Debian Testing Jess: Server Randomly Reboots - No Logs / Indication - Rsyslog Issue?

Adam Brenner wrote: > The issue I am facing is that at random, unrepeatable times, the server > locks up and requires a reboot. However, none of the system generated > logs in /var/logs/ report any kernel panic or memory dump. I have ran a > number of grep commands and even manually spent time trac

Re: Debian Testing Jess: Server Randomly Reboots - No Logs / Indication - Rsyslog Issue?

On 06/04/2014 11:07 PM, Adam Brenner wrote: > Howdy List, > > I am a recent "convert" from the RHEL/CentOS community and I am running > a server of Debian Testing "Jess." I am running the latest 3.14.4-1 > kernel and apt-get update && apt-get upgrade have no pending installs. > > The issue I am f

Re: Debian Testing Gnome Wallpaper Missing #731239

On 21/03/14 02:03, Hörmetjan Yiltiz wrote: > Hi, > > I know this annoyed quite a lot of people, and now the bug report has > been closed. Bug number: #731239 > > But when exactly do you think this patch should be released in Debian > testing branch? No idea. Ask the upstream developers? > It i

Re: Debian Testing Gnome Wallpaper Missing #731239

On Thu 20 Mar 2014 at 23:03:25 +0800, Hörmetjan Yiltiz wrote: > I know this annoyed quite a lot of people, and now the bug report has been > closed. Bug number: #731239 #731239 is still open. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Tro

Re: Debian Testing VMWare-Tools Bad Variable Name

On Mon, Dec 9, 2013 at 11:13 AM, Helmar Gerloni wrote: >> >> Starting VMware Tools services in the virtual machine: >>Switching to guest configuration: [71G done >> >> /etc/init.d/vmware-tools: 1090: local: ': bad variable name >> /etc/init.d/vmware-tools: 1090: local: ': bad variable name >>

Re: Debian Testing VMWare-Tools Bad Variable Name

Hi, > Starting VMware Tools services in the virtual machine: >Switching to guest configuration: done > > /etc/init.d/vmware-tools: 1090: local: ': bad variable name > /etc/init.d/vmware-tools: 1090: local: ': bad variable name > >Blocking file system:failed > > /etc/init.d/vmw

Re: Debian Testing/Jessie and OpenGL

Message- From: steef [mailto:debian.li...@home.nl] Sent: Tuesday, September 10, 2013 11:52 AM To: debian Subject: Re: Debian Testing/Jessie and OpenGL On 10-09-13 13:30, Stephen P, Molnar wrote: I have installed jessie in an Oracle VBox on my laptop tp use as a test bed for new applications

Re: Debian Testing/Jessie and OpenGL

Message- From: steef [mailto:debian.li...@home.nl] Sent: Tuesday, September 10, 2013 11:52 AM To: debian Subject: Re: Debian Testing/Jessie and OpenGL On 10-09-13 13:30, Stephen P, Molnar wrote: I have installed jessie in an Oracle VBox on my laptop tp use as a test bed for new applications

RE: Debian Testing/Jessie and OpenGL

...@home.nl] Sent: Tuesday, September 10, 2013 11:52 AM To: debian Subject: Re: Debian Testing/Jessie and OpenGL On 10-09-13 13:30, Stephen P, Molnar wrote: > I have installed jessie in an Oracle VBox on my laptop tp use as a > test bed for new applications software without jeopardizing my

Re: Debian Testing/Jessie and OpenGL

<.> it seems to be a known issue. look at: http://www.salome-platform.org/forum/forum_10/826530538 regards, steef Very Interesting. Many thanks for the reference. I'll try it in a new implementation in VBox you are welcome, hope it helps. reg., steef -- To UNSUBSCRIBE,

Re: Debian Testing/Jessie and OpenGL

) Skype: smolnar1 -Original Message- From: steef [mailto:debian.li...@home.nl] Sent: Tuesday, September 10, 2013 11:52 AM To: debian Subject: Re: Debian Testing/Jessie and OpenGL On 10-09-13 13:30, Stephen P, Molnar wrote: I have installed jessie in an Oracle VBox on my laptop tp use as a

Re: Debian Testing/Jessie and OpenGL

On 10-09-13 13:30, Stephen P, Molnar wrote: I have installed jessie in an Oracle VBox on my laptop tp use as a test bed for new applications software without jeopardizing my native Linux production computer. Unfortunately, some of the candidate software I wish to evaluate appear to require OpenG

Re: Debian Testing VMWare-Tools Bad Variable Name

Chris Bannister, 25.07.2013: > On Mon, Jul 22, 2013 at 09:31:34AM -0500, Selim T. Erdogan wrote: > > This is a long shot but for some reason I was reminded of > > having trouble with a non-debian script a few months ago, that > > also asked to be run by /bin/sh (as your attachment did). > > > > A

Re: Debian Testing VMWare-Tools Bad Variable Name

On Mon, Jul 22, 2013 at 09:31:34AM -0500, Selim T. Erdogan wrote: > This is a long shot but for some reason I was reminded of > having trouble with a non-debian script a few months ago, that > also asked to be run by /bin/sh (as your attachment did). > > At the time, on my wheezy system (while it

Re: Debian Testing VMWare-Tools Bad Variable Name

On Mon, 22 Jul 2013 09:31:34 -0500 "Selim T. Erdogan" wrote: > This is a long shot but for some reason I was reminded of > having trouble with a non-debian script a few months ago, that > also asked to be run by /bin/sh (as your attachment did). > > At the time, on my wheezy system (while it wa

Re: Debian Testing VMWare-Tools Bad Variable Name

This is a long shot but for some reason I was reminded of having trouble with a non-debian script a few months ago, that also asked to be run by /bin/sh (as your attachment did). At the time, on my wheezy system (while it was still in testing), /bin/sh pointed to dash, not bash, so the script di

Re: Debian Testing VMWare-Tools Bad Variable Name

On 07/22/13 at 08:23am, Stephen P. Molnar wrote: > > > 2013/7/22 emmanuel segura > > >> 2013/7/21 William Hopkins > > >>> On 07/21/13 at 04:09pm, Stephen P. Molnar wrote: > > >>> > In the case of Debian 7.1.0 the vmware tools installed without > > >>> > any > > >>> problems. > > >>> > > > >>> > U

Re: Debian Testing VMWare-Tools Bad Variable Name

On Mon, 22 Jul 2013 11:23:00 +0200 emmanuel segura wrote: > Hello List > > I try to figure out i what i think, get_version_integer function get 3 > parameters > + > # Get the running k

Re: Debian Testing VMWare-Tools Bad Variable Name

Hello List I try to figure out i what i think, get_version_integer function get 3 parameters + # Get the running kernel integer version get_version_integer() { local version_uts loca

Re: Debian Testing VMWare-Tools Bad Variable Name

Sorry Forgot the previous mail 2013/7/22 emmanuel segura > Hello List > > Maybe i wrong but i think the error is local > run_kver=`get_version_integer` the script calls get_version_integer like > external command, but it's a function > > Thanks > > > 2013/7/21 William Hopkins > >> On 07/21/1

  1   2   3   >