Re: X server does not start after upgrading to Debian 10

Felix Miata composed on 2019-07-08 23:21 (UTC-0400): > ISTR your experience is known to upstream, but I get lost trying to > find anything I want in their tracking systems. :-P https://gitlab.freedesktop.org/xorg/xserver/issues/542 might be what I was thinking of. -- Evolution as taught in publi

Re: X server does not start after upgrading to Debian 10

Teemu Likonen composed on 2019-07-07 15:13 (UTC+0300): > Solved. The X server chooses automatically some wrong graphics module > ("modeset" I guess). If I force it to use "intel" module the X server > works again. The Intel DDX hasn't had an official release since five years ago: https://cgit.fre

Re: Check your signing key expiration dates!

* On 2019 08 Jul 04:01 -0500, Brad Rogers wrote: > Just updated it here, and there were changes, 16 signatures cleaned, but > nothing other than that. However, I know the last key refresh I did was > a few months ago. With the DoS attack, I'm not likely to be refreshing > keys wholesale any more,

Re: [i3] [xrandr] xrandr cannot find output modes when execed on startup by i3

Jakub Alba composed on 2019-07-09 00:45 (UTC+0200) ... Which DDX is your i3 using? Whichever, switch to the other. Does it still happen? Try adding one or two empty xrandr lines before your real one in default.sh. I had something similar happen 2-3 years ago, before I discovered the modesetting

Re: Upgrading to Buster but keeping Postgresql-9.6

On 9/07/19 9:24 AM, Phil Endecott wrote: > Andrei POPESCU wrote: >> On Lu, 08 iul 19, 20:02:36, Phil Endecott wrote: >>> Dear Experts, >>> >>> Does anyone have any advice about the possibility of upgrading >>> systems from Stretch to Buster, but keeping Postgresql-9.6 for >>> the time being? >> >>

Re: fix for no ssh

On Mon 08 Jul 2019 at 19:21:37 (+0300), Andrei POPESCU wrote: > On Lu, 08 iul 19, 10:19:35, Curt wrote: > > > > I thought you were saying that > > '/etc/udev/rules.d/70-persistent-net.rules' remains a valid mechanism > > for defining interface names in Buster (fixed). But the release-notes > > (hm

Re: fix for no ssh

On Mon, Jul 8, 2019 at 6:15 PM John Hasler wrote: > Andy Smith writes: > > To arrive > > at a situation where the entirety of the CPU was open to inspection > > would probably require a complete reworking of the modern economy, > > i.e. make it less purely capitalist for a start. > > More capital

Re: fix for no ssh

On Mon, 08 Jul 2019, Andrei POPESCU wrote: > In my understanding what sysv-init does (crediting entropy over reboots) > is not secure for various reasons. Writes to /dev/urandom using dd *DOES NOT* and *NEVER HAS* credited any entropy to the pool. Which is what sysvinit (actually, initscripts) d

Re: fix for no ssh

Andy Smith writes: > I think if we stopped using Intel and AMD then there would be some > other near-monopoly manufacturer that would arise and embed > unauditable blobs so we'd be in exactly the same position. To arrive > at a situation where the entirety of the CPU was open to inspection > would

Re: etiquette of sharing executable files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Greg Wooledge wrote: > On Sun, Jul 07, 2019 at 12:06:36PM +0200, Nicolas George wrote: >> DO NOT TRY TO SECOND-GUESS THE USER. > > While I absolutely agree with that, I would also add: > > DO SENSIBLE THINGS BY DEFAULT. > > That is, if the user doesn

[i3] [xrandr] xrandr cannot find output modes when execed on startup by i3

I've just upgraded from Stretch to Buster. I use a xrandr script invoked by i3 on startup to set screen layout. Here is the fragment of my config responsible for that: # set multimonitor screen layout & background exec --no-startup-id setscreenlayout && setbg `setscreenlayout`

Re: Fwd: fix for no ssh

Hi Nicholas, On Mon, Jul 08, 2019 at 04:49:00PM -0500, Nicholas Geovanis wrote: > On Mon, Jul 8, 2019 at 3:45 PM Andy Smith wrote: > > Flash forward to 2017 and T'so himself wrote a patch to add a > > configure option to allow RDRAND to be used early on to bootstrap > > entropy. Thereafter it wou

Fwd: fix for no ssh

On Mon, Jul 8, 2019 at 3:45 PM Andy Smith wrote: > Hello, > > Flash forward to 2017 and T'so himself wrote a patch to add a > configure option to allow RDRAND to be used early on to bootstrap > entropy. Thereafter it would not be the exclusive source of entropy. > That is what has been enabl

Re: Upgrading to Buster but keeping Postgresql-9.6

Andrei POPESCU wrote: On Lu, 08 iul 19, 20:02:36, Phil Endecott wrote: Dear Experts, Does anyone have any advice about the possibility of upgrading systems from Stretch to Buster, but keeping Postgresql-9.6 for the time being? Is upgrading to buster a necessity? Stretch will be supported by D

Re: Assorted arm-buster problems - network configuration

On 7/8/19, Gene Heskett wrote: > On Monday 08 July 2019 14:48:59 Lee wrote: > >> On 7/8/19, Andrei POPESCU wrote: >> > On Lu, 08 iul 19, 13:37:26, Lee wrote: >> >> On 7/7/19, andreimpope...@gmail.com > wrote: >> >> > The dangers are not at all obvious to me, possibly because I >> >> > haven't us

Re: Upgrading to Buster but keeping Postgresql-9.6

On Lu, 08 iul 19, 20:02:36, Phil Endecott wrote: > Dear Experts, > > Does anyone have any advice about the possibility of upgrading > systems from Stretch to Buster, but keeping Postgresql-9.6 for > the time being? Is upgrading to buster a necessity? Stretch will be supported by Debian for one m

Re: fix for no ssh

Sorry for replying to myself. On Lu, 08 iul 19, 23:50:02, Andrei POPESCU wrote: > > On the other hand Debian felt like from the moment I started with it and home > I was happy to be able to return to it once it gained su

Re: fix for no ssh

On Lu, 08 iul 19, 14:50:18, Gene Heskett wrote: > > But I must say even I was surprised by the near total bailout when I > mentioned that it was raspian. Obviously in retrospect, there is bad > blood? Not from me. I was very much happy with Raspbian when I my Raspberry Pis were still in use.

Re: fix for no ssh

Hello, On Mon, Jul 08, 2019 at 02:50:18PM -0400, Gene Heskett wrote: > On Monday 08 July 2019 14:14:10 Andy Smith wrote: > > On Mon, Jul 08, 2019 at 05:48:24PM -, Curt wrote: > > > it "amounts to trusting that CPU manufacturer (perhaps with the > > > insistence or mandate of a Nation State's i

Re: Problem Installing DiscoveryStudio2019 in Buster

On Mon 08 Jul 2019 at 16:13:56 (-0400), Greg Wooledge wrote: > On Mon, Jul 08, 2019 at 03:09:45PM -0500, David Wright wrote: > > On Mon 08 Jul 2019 at 14:55:45 (-0400), Greg Wooledge wrote: > > > On Mon, Jul 08, 2019 at 02:49:40PM -0400, Stephen P. Molnar wrote: > > > > It came from the Biovia web

Re: Problem Installing DiscoveryStudio2019 in Buster

On Mon, Jul 08, 2019 at 03:09:45PM -0500, David Wright wrote: > On Mon 08 Jul 2019 at 14:55:45 (-0400), Greg Wooledge wrote: > > On Mon, Jul 08, 2019 at 02:49:40PM -0400, Stephen P. Molnar wrote: > > > It came from the Biovia web site. > > > > Like I know what a "Biovia" is. > > It looks like a c

Re: Problem Installing DiscoveryStudio2019 in Buster

On Mon 08 Jul 2019 at 14:55:45 (-0400), Greg Wooledge wrote: > On Mon, Jul 08, 2019 at 02:49:40PM -0400, Stephen P. Molnar wrote: > > It came from the Biovia web site. > > Like I know what a "Biovia" is. It looks like a company to me. > I'm guessing it has something to do with "Molecular-Modelin

Re: Upgrading to Buster but keeping Postgresql-9.6

Phil Endecott: > > Does anyone have any advice about the possibility of upgrading > systems from Stretch to Buster, but keeping Postgresql-9.6 for > the time being? With previous Debian releases you always had to migrate your cluster to the new Postgres version manually. The new packages are inst

Re: Assorted arm-buster problems - network configuration

On Monday 08 July 2019 14:48:59 Lee wrote: > On 7/8/19, Andrei POPESCU wrote: > > On Lu, 08 iul 19, 13:37:26, Lee wrote: > >> On 7/7/19, andreimpope...@gmail.com wrote: > >> > The dangers are not at all obvious to me, possibly because I > >> > haven't used it much (if at all). > >> > >> Read th

Upgrading to Buster but keeping Postgresql-9.6

Dear Experts, Does anyone have any advice about the possibility of upgrading systems from Stretch to Buster, but keeping Postgresql-9.6 for the time being? This is for a couple of cloud servers that are running Postgresql with streaming replication from one to the other. I guess my questions ar

Re: Assorted arm-buster problems - network configuration

On Mon 08 Jul 2019 at 13:37:26 -0400, Lee wrote: > On 7/7/19, andreimpope...@gmail.com wrote: > > On Sb, 06 iul 19, 15:36:37, Lee wrote: > >> > >> "an accident waiting to happen" was from me and I also gave the rfc > >> for mdns, so that's hardly "nothing of substance to support that > >> view."

Re: Problem Installing DiscoveryStudio2019 in Buster

On 07/08/2019 02:55 PM, Greg Wooledge wrote: On Mon, Jul 08, 2019 at 02:49:40PM -0400, Stephen P. Molnar wrote: It came from the Biovia web site. -- Stephen P. Molnar, Ph.D.Life is a fuzzy set http://www.Molecular-Modeling.net Multivariate and stochastic Like I know what a "Bi

Re: Problem Installing DiscoveryStudio2019 in Buster

On 07/08/2019 02:46 PM, Erwan David wrote: Le 08/07/2019 ?? 20:40, Stephen P. Molnar a ??crit : I have just installed Buster and have encountereda a problem attempting the installation of biovia_2019_.ds2019client.bin: comp@AbNormal:~/Downloads/DiscoveryStudio$ ./biovia_2019.ds2019client.bi

Re: Problem Installing DiscoveryStudio2019 in Buster

On 2019-07-08 20:46 +0200, Erwan David wrote: > Le 08/07/2019 à 20:40, Stephen P. Molnar a écrit : >> I have just installed Buster and have encountereda  a problem >> attempting the installation of biovia_2019_.ds2019client.bin: >> >> comp@AbNormal:~/Downloads/DiscoveryStudio$ ./biovia_2019.ds2019

Re: Problem Installing DiscoveryStudio2019 in Buster

On Mon, Jul 08, 2019 at 02:49:40PM -0400, Stephen P. Molnar wrote: > It came from the Biovia web site. > > -- > Stephen P. Molnar, Ph.D.Life is a fuzzy set > http://www.Molecular-Modeling.net Multivariate and stochastic Like I know what a "Biovia" is. I'm guessing it has something

Re: Problem Installing DiscoveryStudio2019 in Buster

On Mon, Jul 08, 2019 at 08:46:30PM +0200, Erwan David wrote: > bash ./biovia_2019.ds2019client.bin to force bash interpreter That won't work, because... > Le 08/07/2019 à 20:40, Stephen P. Molnar a écrit : > > comp@AbNormal:~/Downloads/DiscoveryStudio$ ./biovia_2019.ds2019client.bin > > Verifying

Re: fix for no ssh

On Monday 08 July 2019 14:14:10 Andy Smith wrote: > Hi Curt, > > On Mon, Jul 08, 2019 at 05:48:24PM -, Curt wrote: > > it "amounts to trusting that CPU manufacturer (perhaps with the > > insistence or mandate of a Nation State's intelligence or law > > enforcement agencies) has not installed a

Re: Problem Installing DiscoveryStudio2019 in Buster

On 07/08/2019 02:44 PM, Greg Wooledge wrote: On Mon, Jul 08, 2019 at 02:40:18PM -0400, Stephen P. Molnar wrote: I have just installed Buster and have encountereda a problem attempting the installation of biovia_2019_.ds2019client.bin: comp@AbNormal:~/Downloads/DiscoveryStudio$ ./biovia_2019

Re: Assorted arm-buster problems - network configuration

On 7/8/19, Andrei POPESCU wrote: > On Lu, 08 iul 19, 13:37:26, Lee wrote: >> On 7/7/19, andreimpope...@gmail.com wrote: >> >> > The dangers are not at all obvious to me, possibly because I haven't >> > used it much (if at all). >> >> Read the first three paragraph of the "Security Considerations"

Re: Problem Installing DiscoveryStudio2019 in Buster

Le 08/07/2019 à 20:40, Stephen P. Molnar a écrit : > I have just installed Buster and have encountereda  a problem > attempting the installation of biovia_2019_.ds2019client.bin: > > comp@AbNormal:~/Downloads/DiscoveryStudio$ ./biovia_2019.ds2019client.bin > Verifying archive integrity...  100%  

Re: Problem Installing DiscoveryStudio2019 in Buster

On Mon, Jul 08, 2019 at 02:40:18PM -0400, Stephen P. Molnar wrote: > I have just installed Buster and have encountereda a problem attempting the > installation of biovia_2019_.ds2019client.bin: > > comp@AbNormal:~/Downloads/DiscoveryStudio$ ./biovia_2019.ds2019client.bin > Verifying archive integ

Problem Installing DiscoveryStudio2019 in Buster

I have just installed Buster and have encountereda a problem attempting the installation of biovia_2019_.ds2019client.bin: comp@AbNormal:~/Downloads/DiscoveryStudio$ ./biovia_2019.ds2019client.bin Verifying archive integrity... 100% All good. Uncompressing 'DS Client and extracting files, pl

Re: DPMS ( OT: Jonas)

Jonas, Weird I got your reply via the website but I never got a reply via email. Sorry for the triple send.. I wasnt sure if my messages were going through or not.. I never got a reply back saying my messages went through. Chris

Re: Assorted arm-buster problems - network configuration

On Sat 06 Jul 2019 at 18:14:04 -0400, Gene Heskett wrote: > So I now have a working network. Free of the bogus inventions of dhcpd5 > and avahi. That _was_ the point of all this hoopla in the first place. > > Now, I have learned what works to _my_ satisfaction. > > Have you? Or did you quit re

RE: DPMS ( I had to rejoin the group hopefully my message goes through this time )

Quoting Christopher M (2019-07-08 14:52:54) > I am not sure if my message came through so I am sending it again: Three duplicates is enough, thanks: https://lists.debian.org/6565230fbe88f8f6db08b7ded2f149b7c6f8d37f.ca...@cwm030.com https://lists.debian.org/fecde663e12ddafc9f02ba23b01b3eb15e434b36

Re: aptitude new packages list forgets old

On 2019-07-08 19:21 +0200, Matus UHLAR - fantomas wrote: > I am trying to look which packages are new in buster that were not in > stretch. I am using aptitude since it't great tool for browsing packages. Beware that the list of new packages in buster is way too large to browse casually. In main

Re: fix for no ssh

Hi Curt, On Mon, Jul 08, 2019 at 05:48:24PM -, Curt wrote: > it "amounts to trusting that CPU manufacturer (perhaps with the > insistence or mandate of a Nation State's intelligence or law > enforcement agencies) has not installed a hidden back door to > compromise the CPU's random number gene

Re: Assorted arm-buster problems - network configuration

On Lu, 08 iul 19, 13:37:26, Lee wrote: > On 7/7/19, andreimpope...@gmail.com wrote: > > > The dangers are not at all obvious to me, possibly because I haven't > > used it much (if at all). > > Read the first three paragraph of the "Security Considerations" section > https://tools.ietf.org/html

RE: DPMS ( I had to rejoin the group hopefully my message goes through this time )

--- Begin Message --- I am not sure if my message came through so I am sending it again: Hi, In Deb 9 KDE on Deb 9 as soon as I logged in DPMS would be disabled and my screen would not turn off. I would have to manually go into the command line and run a line ( I forget what it was I ran) but

Re: buster changes vim mouse behavior again...

On Lu, 08 iul 19, 08:48:15, Dave Sherohman wrote: > > Today I did a test install of buster, however, and found a new problem: > It seems that buster's vim detects the middle-click and "helpfully" goes > immediately into insert mode, meaning that ":set paste" and "O" are > entered as part of the fi

Re: Assorted arm-buster problems - network configuration

On 7/7/19, Curt wrote: > On 2019-07-06, Lee wrote: >> >> "an accident waiting to happen" was from me and I also gave the rfc >> for mdns, so that's hardly "nothing of substance to support that > > I see. So the totality of the mdns rfc (*somewhat* more succinct than a > 19th century Russian novel

Re: fix for no ssh

On 2019-07-08, Andrei POPESCU wrote: > >> Well, at the very least people should be informed who is likely to be >> affected by the bug > > In my understanding a lot of daemons are affected. Would it make sense > to (try to) list them all? Well, then, you should make that explicit, viz. that almos

Re: Assorted arm-buster problems - network configuration

On 7/7/19, andreimpope...@gmail.com wrote: > On Sb, 06 iul 19, 15:36:37, Lee wrote: >> >> "an accident waiting to happen" was from me and I also gave the rfc >> for mdns, so that's hardly "nothing of substance to support that >> view." If you're having trouble finding the rfc, it's here >> http

aptitude new packages list forgets old

Hello, I am trying to look which packages are new in buster that were not in stretch. I am using aptitude since it't great tool for browsing packages. until now it was easy: do 'f'orget new packages in aptitude change sources.list to point to new release do 'u'pdate packages list ... voila but

Re: fix for no ssh

Hello, On Mon, Jul 08, 2019 at 04:18:28PM -, Curt wrote: > Well, looking at Ted Ts'o short patch, where he mentions the security > implications of the thing at some length, *twice* I think that some of Ted's stance might not be because Ted thinks it is dangerous but because there has been in

Re: fix for no ssh

On Lu, 08 iul 19, 10:19:35, Curt wrote: > > I thought you were saying that > '/etc/udev/rules.d/70-persistent-net.rules' remains a valid mechanism > for defining interface names in Buster (fixed). But the release-notes > (hmm, I think they've been modified since I last looked and now state > that

Re: fix for no ssh

On 2019-07-08, Greg Wooledge wrote: > > I don't have any opinions at this time about the trustworthiness of > various x86 CPU RDRAND instructions, but... Well, looking at Ted Ts'o short patch, where he mentions the security implications of the thing at some length, *twice*---once in the "intro" I

Re: fix for no ssh

Hello, On Mon, Jul 08, 2019 at 02:40:16PM -, Curt wrote: > But as an innate altruist (just kidding), I'm wondering whether the > regular user is aware of the implications of all this. What about people > in Nation States ... Well, you get the idea. Thing is, if you can't trust that your CPU'

Re: Failed to fetch http://ftp.us.debian.org/debian/dists/buster/InRelease:

Quoting local10 (2019-07-08 12:49:19) > Jul 8, 2019, 11:27 AM by mailingli...@mattcrews.com: > > > Use "apt update" instead of "aptitude update" or "apt-get update" > > > > Specifically you want to: > > > > # apt update && apt upgrade && apt full-upgrade > > > > I normally use aptitude instead of

Re: [OT] Trustfulness. Was: Re: fix for no ssh

Hi. On Mon, Jul 08, 2019 at 05:57:49PM +0200, Thomas Schmitt wrote: > Hi, > > Curt quoted: > > This will prevent getrandom(2) from blocking, if there is a > > willingness to trust the CPU manufacturer. > > Signed-off-by: Theodore Ts'o > > Apropos trusting strange allies: > > # mou

[RESOLVED] Re: Failed to fetch http://ftp.us.debian.org/debian/dists/buster/InRelease:

Jul 8, 2019, 11:55 AM by svenj...@gmx.de: > You only have to run "apt update" once and affirm the questions it asks, > then aptitude will run fine again. See bug #915246[1] and its siblings. > That resolved the issue for me. Thanks to everyone who responded.

[OT] Trustfulness. Was: Re: fix for no ssh

Hi, Curt quoted: > This will prevent getrandom(2) from blocking, if there is a > willingness to trust the CPU manufacturer. > Signed-off-by: Theodore Ts'o Apropos trusting strange allies: # mount debian-10.0.0-amd64-netinst.iso /mnt/iso mount: /dev/loop0 is write-protected, mounting read

Re: Failed to fetch http://ftp.us.debian.org/debian/dists/buster/InRelease:

On 2019-07-08 17:49 +0200, local10 wrote: > Jul 8, 2019, 11:27 AM by mailingli...@mattcrews.com: > >> Use "apt update" instead of "aptitude update" or "apt-get update" >> >> Specifically you want to: >> >> # apt update && apt upgrade && apt full-upgrade >> > > I normally use aptitude instead of ap

Re: Failed to fetch http://ftp.us.debian.org/debian/dists/buster/InRelease:

On Mon, Jul 08, 2019 at 05:49:19PM +0200, local10 wrote: > I normally use aptitude instead of apt and would prefer to continue using it, > if possible. aptitude was working fine until July 7 or so. Also, I'm already > running Buster so "full-upgrade" shouldn't be necessary for me. Tried > "full-

Re: Failed to fetch http://ftp.us.debian.org/debian/dists/buster/InRelease:

Jul 8, 2019, 11:27 AM by mailingli...@mattcrews.com: > Use "apt update" instead of "aptitude update" or "apt-get update" > > Specifically you want to: > > # apt update && apt upgrade && apt full-upgrade > I normally use aptitude instead of apt and would prefer to continue using it, if possible.

Re: fix for no ssh

On Mon, Jul 08, 2019 at 02:40:16PM -, Curt wrote: > Earlier I thought bullseye was some sort of idiom for Buster going live. > Color me ignorant. Bullseye will be the next version of Debian after buster, probably in 2-3 years. Cue the confusion about two similar-looking release names back to

Re: Failed to fetch http://ftp.us.debian.org/debian/dists/buster/InRelease:

On 7/8/19 8:23 AM, local10 wrote: > Hi, > > Debian Buster updates started failing for me about a couple of days ago. I > understand it may be related to  Buster being moved from testing to stable > but that shouldn't have affected me as I specifically target buster instead > of testing. > > An

Failed to fetch http://ftp.us.debian.org/debian/dists/buster/InRelease:

Hi, Debian Buster updates started failing for me about a couple of days ago. I understand it may be related to  Buster being moved from testing to stable but that shouldn't have affected me as I specifically target buster instead of testing. Any ideas? Thanks # aptitude update && aptitude sa

Displaylink issue after upgrading to Buster

Hi One of my monitors is connected via Displaylink, USB 2.0. This has always worked perfectly but on upgrading to Buster, that monitor now only comes up with screen corruption. Error messages from journalctl: jul 08 15:46:14 debian kernel: udl 3-1.4.1:1.0: swiotlb buffer is full (sz: 360448 by

Re: fix for no ssh

On 2019-07-08, Andrei POPESCU wrote: > > The timing was also not very good for the buster release cycle. > Hopefully this will be sorted out properly in time for bullseye. Earlier I thought bullseye was some sort of idiom for Buster going live. Color me ignorant. But concerning the currently pr

Re: Assorted arm-buster problems - network configuration

On Mon 08 Jul 2019 at 08:36:38 (-0400), Greg Wooledge wrote: > On Sat, Jul 06, 2019 at 08:46:19AM -0500, David Wright wrote: > > On Fri 05 Jul 2019 at 20:10:42 (-0400), Gene Heskett wrote: > > > But that begs another question Greg. If it hasn't anything to do with > > > avahi-daemon, whyinhell di

buster changes vim mouse behavior again...

Last time around, stretch changed mouse behavior in vim by setting "mouse=a" by default. To deal with this, my checklist for stretch updates/installs includes --- vi /etc/vim/vimrc.local :set mouse= :set paste O " Don't silently ignore these settings in favor of those in default.vim let g:skip_de

Re: From Buster RC2 to Buster stable

On Sun, Jul 07, 2019 at 11:51:56AM +1200, Richard Hector wrote: > E: Repository 'http://security.debian.org/debian-security buster/updates > InRelease' changed its 'Suite' value from 'testing' to 'stable' > N: This must be accepted explicitly before updates for this repository > can be applied. See

Re: xfce4-screenshooter does not copy images to clipboard

On 2019-07-07, Erik Dobák wrote: > > same behavior with xclip -o --selection clip-board > clip10.txt > I think you must pipe the primary to the clipboard before redirecting the clipboard to a file. xclip -o | xclip -sel clip > clip10.txt https://github.com/astrand/xclip I was unaware of this p

Re: etiquette of sharing executable files

On Sun, Jul 07, 2019 at 12:06:36PM +0200, Nicolas George wrote: > DO NOT TRY TO SECOND-GUESS THE USER. While I absolutely agree with that, I would also add: DO SENSIBLE THINGS BY DEFAULT. That is, if the user doesn't tell you what to do, try to do the most common, or the safest, thing. But if t

Re: Assorted arm-buster problems - network configuration

On Monday 08 July 2019 08:36:38 Greg Wooledge wrote: > On Sat, Jul 06, 2019 at 08:46:19AM -0500, David Wright wrote: > > On Fri 05 Jul 2019 at 20:10:42 (-0400), Gene Heskett wrote: > > > But that begs another question Greg. If it hasn't anything to do > > > with avahi-daemon, whyinhell did purgin

Re: will Release come back for testing/updates at security.debian.org?

Andrei POPESCU wrote: > On Du, 07 iul 19, 08:23:59, songbird wrote: >> with the change to testing the past day the error message pops up: >>=20 >> E: The repository 'http://security.debian.org/debian-security testing/upd= > ates Release' no longer has a Release file. > > Not sure why you even hav

Re: Assorted arm-buster problems - network configuration

On Sat, Jul 06, 2019 at 08:46:19AM -0500, David Wright wrote: > On Fri 05 Jul 2019 at 20:10:42 (-0400), Gene Heskett wrote: > > But that begs another question Greg. If it hasn't anything to do with > > avahi-daemon, whyinhell did purging avahi-daemon take the libnsswitch > > package with it? >

Re: [OT] send all email from certain From: addresses into a spam

On Sun, 7 Jul 2019 09:00:05 +0300 Reco wrote: > Hi. > > On Sat, Jul 06, 2019 at 11:09:36PM -0400, Celejar wrote: > > On Fri, 5 Jul 2019 09:35:46 +0300 > > Reco wrote: > > > > ... > > > > > time. For instance, outlook.com sents nothing but spam to this maillist, > > > so any e-mails from

libvirt - Problem with encrypted QEMU-VM after upgrade to buster

After upgrading to busters, my VMs fail to start:  virsh --connect qemu:///system start Feigenbaum error: Failed to start domain Feigenbaum error: internal error: process exited while connecting to monitor: 2019-07-08T11:32:00.290494Z qemu-system-x86_64: --object secret,id=sec0,file=/etc/libvir

Re: READY! Tomas Ukkonen: Genocide. SOS.

Hi Someone seemed to have modified the previous email I send to you. The sentence should have been "Title seem to have lost full  lenght." Fix the title as soon as possible. Tomas Erno Ukkonen, M. Sc.Sent from ProtonMail, encrypted email. ‐‐‐ Original Message ‐‐‐ On Saturday, 6th Julyt

Re: fix for no ssh

On 2019-07-08, Andrei POPESCU wrote: > > The timing was also not very good for the buster release cycle. > Hopefully this will be sorted out properly in time for bullseye. That would be great. Then if they could resuscitate ecryptfs-utils I would be a happy camper. ;-) > Kind regards, > Andrei

Re: fix for no ssh

On 2019-07-08, Andrei POPESCU wrote: > > > On Lu, 08 iul 19, 09:44:51, Curt wrote: >> On 2019-07-08, Andrei POPESCU wrote: >> > >> > On Lu, 08 iul 19, 09:06:33, Curt wrote: >> >> On 2019-07-08, Andrei POPESCU wrote: >> >> > >> >> > This was fixed before the release. >> >> What? >> > >> > Is the

Re: fix for no ssh

On Lu, 08 iul 19, 09:01:36, Curt wrote: > On 2019-07-08, Andrei POPESCU wrote: > > > >> Wow. Another reason to love systemd :-( > > > > Not clear to me why you are blaming systemd here. > > Because systemd is to blame (at least in the opinion of some people in the > know, like Stefan Frisch, for

Re: fix for no ssh

On Lu, 08 iul 19, 09:44:51, Curt wrote: > On 2019-07-08, Andrei POPESCU wrote: > > > > On Lu, 08 iul 19, 09:06:33, Curt wrote: > >> On 2019-07-08, Andrei POPESCU wrote: > >> > > >> > This was fixed before the release. > > >> What? > > > > Is there something wrong with the current wording? > > I

Re: No jigdo images yet?

On Mon, Jul 08, 2019 at 11:08:15AM +0200, Thomas Schmitt wrote: > it is an old bug of jigdo-lite that it cannot download .jigdo and > .template files via https: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865864 > > So manually download the .template file too and then run jigdo-lite agai

Re: fix for no ssh

On 2019-07-08, Andrei POPESCU wrote: > > On Lu, 08 iul 19, 09:06:33, Curt wrote: >> On 2019-07-08, Andrei POPESCU wrote: >> > >> > This was fixed before the release. >> What? > > Is there something wrong with the current wording? I guess, as I thought I was referring to the release-notes, which

Re: will Release come back for testing/updates at security.debian.org?

On Mon, Jul 08, 2019 at 11:54:01AM +0300, Andrei POPESCU wrote: > On Lu, 08 iul 19, 03:10:53, Dave Sherohman wrote: > > On Sun, Jul 07, 2019 at 03:22:40PM +0200, Salvatore Bonaccorso wrote: > > > That will be actually a permanent change, see > > > https://lists.debian.org/debian-security/2019/06/ms

Re: fix for no ssh

On Lu, 08 iul 19, 09:06:33, Curt wrote: > On 2019-07-08, Andrei POPESCU wrote: > > > > This was fixed before the release. > > What? Is there something wrong with the current wording? > > You are aware that the Release Notes are work in progress as long as the > > corresponding Debian release i

Re: Check your signing key expiration dates!

On Mon, 8 Jul 2019 12:07:38 +0300 Andrei POPESCU wrote: Hello Andrei, >Apparently we should only be using full fingerprints only: >https://gwolf.org/node/4070 Thanks for that. Good to know. -- Regards _ / ) "The blindingly obvious is / _)radnever immediat

Re: 70-persistent-net-rules no longer supported? (Was Re: Document removal of ecryptfs-utils from Buster)

On Ma, 02 iul 19, 08:02:22, The Wanderer wrote: > On 2019-07-01 at 03:47, Curt wrote: > > > > https://www.debian.org/releases///buster/s390x/release-notes/ch-information.en.html#migrate-interface-names > > I'm skeptical as to whether this is (still/currently) accurate. This was fixed in the mean

Re: fix for no ssh

On 2019-07-08, Andrei POPESCU wrote: > > This was fixed before the release. What? > You are aware that the Release Notes are work in progress as long as the > corresponding Debian release is still in testing, right? > How will the mistakes be fixed if no one points them out? >> misleading (if

Re: Check your signing key expiration dates!

On Lu, 08 iul 19, 10:00:20, Brad Rogers wrote: > On Mon, 8 Jul 2019 10:03:36 +0300 > Andrei POPESCU wrote: > > >B7A15F455B287F384174D5E9E5EC4AC9BD627B05 (Donald Norwood's key used to > >sign the release announcement). > > Probably only need the last eight chars of that fingerprint. Of course,

Re: No jigdo images yet?

Hi, it is an old bug of jigdo-lite that it cannot download .jigdo and .template files via https: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865864 So manually download the .template file too and then run jigdo-lite again. There is hope that the new system can install jigdo-lite without t

Re: fix for no ssh

On 2019-07-08, Andrei POPESCU wrote: > >> Wow. Another reason to love systemd :-( > > Not clear to me why you are blaming systemd here. > Because systemd is to blame (at least in the opinion of some people in the know, like Stefan Frisch, for instance): https://qa.debian.org/developer.php?login=

Re: Check your signing key expiration dates!

On Mon, 8 Jul 2019 10:03:36 +0300 Andrei POPESCU wrote: Hello Andrei, >B7A15F455B287F384174D5E9E5EC4AC9BD627B05 (Donald Norwood's key used to >sign the release announcement). Probably only need the last eight chars of that fingerprint. Of course, with cut 'n' paste, it matters little. >gpg

Re: fix for no ssh

On Lu, 08 iul 19, 08:40:06, Curt wrote: > > I guess I would not be affected because I'm not running an entropy-hungry > service (or any services at all), but what a PITA to have gone on this wild > goose chase to finally find that out (if true). These release-notes for > Buster, > as they stand,

Re: will Release come back for testing/updates at security.debian.org?

On Lu, 08 iul 19, 03:10:53, Dave Sherohman wrote: > On Sun, Jul 07, 2019 at 03:22:40PM +0200, Salvatore Bonaccorso wrote: > > That will be actually a permanent change, see > > https://lists.debian.org/debian-security/2019/06/msg00015.html . The > > intention was actually do to it already in earlier

Re: will Release come back for testing/updates at security.debian.org?

On Du, 07 iul 19, 08:23:59, songbird wrote: > with the change to testing the past day the error message pops up: > > E: The repository 'http://security.debian.org/debian-security testing/updates > Release' no longer has a Release file. Not sure why you even have 'security' for testing in your

Re: fix for no ssh

On 2019-07-07, Andrei POPESCU wrote: > > It sounds a lot like this issue: > https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#entropy-starvation Due to systemd needing entropy during boot and the kernel treating such calls as blocking when available entropy is

No jigdo images yet?

Back from the weekend, and now I'm trying to do a jigdo download of the new buster install image, but having no luck. Are the jigdo files not up yet (although they seem to be there when I access them with other tools instead of jigdo-lite), or are the instructions on debian.org wrong, or am I some

Re: will Release come back for testing/updates at security.debian.org?

On Sun, Jul 07, 2019 at 03:22:40PM +0200, Salvatore Bonaccorso wrote: > That will be actually a permanent change, see > https://lists.debian.org/debian-security/2019/06/msg00015.html . The > intention was actually do to it already in earlier cycle, but was not > possible (cf. > https://lists.debian

Re: Check your signing key expiration dates!

Andrei POPESCU [2019-07-08T10:28:59+03] wrote: > What would be the alternative to SKS keyservers? Not "the" alternative but keyserver-wise there is which I mentioned and which uses different software. There are also other key delivery methods like WKD or just publish y

Re: How Buster release may affect Unstable?

On Fri, Jul 05, 2019 at 10:35:05AM -0300, Francisco M Neto wrote: > On Tue, 2019-07-02 at 12:23 -0400, Default User wrote: > > On Tue, Jul 2, 2019, 05:38 Dave Sherohman wrote: > > > I think the core misunderstanding here is that you seem to be assuming > > > that, when a new stable comes out, a ne

Re: Check your signing key expiration dates!

On Du, 07 iul 19, 21:11:06, Teemu Likonen wrote: > Andrei POPESCU [2019-07-07T20:31:23+03] wrote: > > > My gpg.conf has: > > > > keyserver hkps://hkps.pool.sks-keyservers.net > > SKS keyservers can be risky because they allow anybody to submit any > number of key signatures to other people's

  1   2   >