[DNG] Beowulf 3.0.0 won't update

2021-04-09 Thread dvalin

 Before installing stuff on my new beowulf 3.0.0, I've run:
root@greipner:~# apt-get update
Get:1 http://deb.devuan.org/merged beowulf InRelease [33.2 kB]
Get:2 http://deb.devuan.org/merged beowulf-updates InRelease [26.1 kB]
Get:3 http://deb.devuan.org/merged beowulf-security InRelease [25.7
kB]
Reading package lists... Done  
E: Repository 'http://deb.devuan.org/merged beowulf InRelease' changed
its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository
can be applied. See apt-secure(8) manpage for details.
E: Repository 'http://deb.devuan.org/merged beowulf-updates InRelease'
changed its 'Suite' value from 'testing-updates' to 'stable-updates'
N: This must be accepted explicitly before updates for this repository
can be applied. See apt-secure(8) manpage for details.
E: Repository 'http://deb.devuan.org/merged beowulf-security
InRelease' changed its 'Suite' value from 'testing-security' to
'stable-security'
N: This must be accepted explicitly before updates for this repository
can be applied. See apt-secure(8) manpage for details.

Unfortunately, the manpage only says:
INFORMATION CHANGES
   A Release file contains beside the checksums for the
files in the repository also general
   information about the repository like the origin,
codename or version number of the release.

   This information is shown in various places so a
repository owner should always ensure correctness.
   Further more user configuration like apt_preferences(5)
can depend and make use of this information.
   Since version 1.5 the user must therefore explicitly
confirm changes to signal that the user is
   sufficiently prepared e.g. for the new major release of
the distribution shipped in the repository
   (as e.g. indicated by the codename).

I.E. the secret method for explicit acceptance is not made explicit
AFAICT.
OK, there wasn't time to code the flinging up of a query for a [Y/n]
response in real time,but what on earth is the current work-around?
I'm quite content to try a dist upgrade, to 3.1.1 or whatever is the
state of the art, if thatcan safely be done with this brittle 3.0.0
version.

Erik

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] SSL certificate or host mapping for ASCII updates for APT

2021-04-09 Thread onefang
On 2021-04-09 18:40:16, Olaf Meeuwissen via Dng wrote:
> Hi Chris,
> 
> crich...@blackfoot.net writes:
> 
> > On 2021-04-08 15:32, Joril wrote:
> >> On 08/04/21 16:40, crichmon@??? wrote:
> >> > I'm trying to 'apt update' an ascii box, and the repos in the
> >> > aptsource list point here:
> >> >
> >> > deb http://us.deb.devuan.org/merged ascii main non-free contrib
> >>
> >> I think that "country mirrors" are deprecated, try using just
> >> deb.devuan.org

Correct, country codes like that are deprecated, but I'm working on
bringing them back.  Do not use them now.

> > Actually, I did already try that after reading the docs on the web again,
> > and get the same problems using the same debugging tools.
> > Sparing the details.
> > /tmp# host deb.devuan.org
> > deb.devuan.org is an alias for deb.roundr.devuan.org.
> > 
> > Trying to browse http://deb.devuan.org/ still fails.
> 
> The package repositories aren't really meant for browser-based perusal
> but http://deb.devuan.org/ displays fine, as in an Apache/2.4 directory
> listing, for me.  That may be because I chanced upon an IP address that
> supports that but if you *really* have SSL certificate issues, I guess
> your browser is *forcing* HTTPS upon you.  Regular HTTP URLs don't use
> certificates.

Apt still uses HTTP if you ask it to use that, so the web servers don't
act any different, it's all HTTP protocol.  So you CAN browse mirrors
using a web browser, so long as they are HTTP mirrors.  There are also
FTP and RSYNC mirrors, but they all support HTTP at least.

> # You might want to make sure you add that http:// at the beginning of
> # that URL in your browser's location bar.
> 
> > What I hadn't tried was 'apt update', which I'm doing now after
> > updating sources.list, and it is working, so apt doesn't exactly have
> > the same cert issues.
> 
> That's because APT uses HTTP, not HTTPS, per your URL.
> APT downloads a signed InRelease file and checks that using GnuPG keys
> from the devuan-keyring package.  If that checks out fine, the checksums
> in that file are used to verify the Packages and Sources files which, in
> turn contain checksums for the individual packages that are verified
> before `apt` goes ahead and install things.
> 
> That is to say, APT doesn't rely on SSL certificates but on GnuPG keys
> to make sure you get exactly what the package maintainers intended.
> 
> Hope this helps,

You are mostly correct.  Apt CAN use https, but didn't by default, coz
the apt HTTPS transport isn't installed by default.  I think it is
installed by default in Beowulf.  However, it still only uses HTTPS if
the URLs in sources are https.

As for the deb.devuan.org round robin DNS, it picks one of our Devuan
package mirrors (at random I think) to send apt and http requests to. 
Those mirrors do not have valid certificates for deb.devuan.org, but may
have valid certificates for whatever that servers actual domain name is. 
If you really want to use HTTPS for apt, pick a nearby one from -

https://pkgmaster.devuan.org/mirror_list.txt

There is a further complication in some mirror servers auto convert HTTP
to HTTPS, which they should not do if they are responding to
deb.devuan.org, or if they are not redirecting to a Debian mirror.  Coz
they have no idea if the Debian mirror round robin DNS system will send
the request to a Debian mirror that doesn't support a proper HTTPS cert
for the round robin DNS name.



TL;DR - don't use the CC.deb.devuan.org names, don't use https for
deb.devuan.org, do use https only with those mirrors that support HTTPS.



-- 
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] Script to migrate buster GNOME DE to beowulf

2021-04-09 Thread tito via Dng
Hi,
attached you will find a proof of concept script for
a buster to beowulf migration. It is tested only in a
standard install (plus gnome DE and ssh) buster Virtualbox 6.1 vm
fully updated to version 10.9. 

USE AT YOUR OWN RISK!!!
DON'T USE IN PRODUCTION!!!

Bold testers, hints and improvements  are welcome.
Some hacks are ugly (I know but didn't knew better ones).
To test:

copy migration.sh to the new system
chmod +x migration.sh
# as root
./migration.sh

I've tested it from within the DE but it
could be used from the console (I suppose).

It works in two stages with minimal interaction.
After reboot remove references to debian buster
from /etc/apt/sources.list
and run: 
apt purge -y systemd
apt install --reinstall elogind
apt update
apt upgrade
apt dist-upgrade
apt autoremove
apt install slim (and select slim as display manager)
reboot

Enjoy.

Ciao,
Tito


migration.sh
Description: application/shellscript
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] help: pyton script problem (after package upg?)

2021-04-09 Thread Ludovic Bellière
You problem seems to be solved upstream. See
https://github.com/sivel/speedtest-cli/releases/tag/v2.1.3

You can always install speedtest in a virtual env.

On ven, 09 avr 2021, al3xu5 wrote:

> Hi all
> 
> Today, after last apt-get upgrade, the `speedtest` python script
> (package is `speedtest-cli`) returns errors:
> 
> ~~~
> $ speedtest
> Retrieving speedtest.net configuration...
> Traceback (most recent call last):
>   File "/usr/bin/speedtest", line 11, in 
> load_entry_point('speedtest-cli==2.0.2', 'console_scripts',
> 'speedtest')()
>   File "/usr/lib/python3/dist-packages/speedtest.py", line 1887, in main
> shell()
>   File "/usr/lib/python3/dist-packages/speedtest.py", line 1783, in shell
> secure=args.secure
>   File "/usr/lib/python3/dist-packages/speedtest.py", line 1027, in
> __init__
> self.get_config()
>   File "/usr/lib/python3/dist-packages/speedtest.py", line 1113, in
> get_config
> map(int, server_config['ignoreids'].split(','))
> ValueError: invalid literal for int() with base 10: ''
> ~~~
> 
> 
> I am not sure the problem is related to the last apt-get upgrade...
> Anyway, could anyone help me to fix this issue, please?
> 
> Thanks in advance
> al3xu5
> 



signature.asc
Description: PGP signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] help: pyton script problem (after package upg?)

2021-04-09 Thread Dimitris via Dng

already reported : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986637

d.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] help: pyton script problem (after package upg?)

2021-04-09 Thread Nick Rickard



On 9 April 2021 20:18:22 BST, al3xu5  wrote:
>Hi all
>
>Today, after last apt-get upgrade, the `speedtest` python script
>(package is `speedtest-cli`) returns errors:
>
>~~~
>$ speedtest
>Retrieving speedtest.net configuration...
>Traceback (most recent call last):
>  File "/usr/bin/speedtest", line 11, in 
>load_entry_point('speedtest-cli==2.0.2', 'console_scripts',
>'speedtest')()
>  File "/usr/lib/python3/dist-packages/speedtest.py", line 1887, in main
>shell()
>  File "/usr/lib/python3/dist-packages/speedtest.py", line 1783, in shell
>secure=args.secure
>  File "/usr/lib/python3/dist-packages/speedtest.py", line 1027, in
>__init__
>self.get_config()
>  File "/usr/lib/python3/dist-packages/speedtest.py", line 1113, in
>get_config
>map(int, server_config['ignoreids'].split(','))
>ValueError: invalid literal for int() with base 10: ''
>~~~
>
>The apt-get log shows:
>~~~
>Start-Date: 2021-04-07  20:19:56
>Commandline: /usr/sbin/synaptic
>Requested-By: alexus (1000)
>Upgrade: libldb1:amd64 (2:1.5.1+really1.4.6-3,
>2:1.5.1+really1.4.6-3+deb10u1), libopenjp2-7:amd64 (2.3.0-2+deb10u1,
>2.3.0-2+deb10u2), libcurl4:amd64 (7.64.0-4+deb10u1, 7.64.0-4+deb10u2),
>libjs-underscore:amd64 (1.9.1~dfsg-1, 1.9.1~dfsg-1+deb10u1),
>libcurl4-gnutls-dev:amd64 (7.64.0-4+deb10u1, 7.64.0-4+deb10u2),
>python-lxml:amd64 (4.3.2-1+deb10u2, 4.3.2-1+deb10u3), curl:amd64
>(7.64.0-4+deb10u1, 7.64.0-4+deb10u2), libcurl3-gnutls:amd64
>(7.64.0-4+deb10u1, 7.64.0-4+deb10u2) End-Date: 2021-04-07  20:20:10 ~~~
>
>I am not sure the problem is related to the last apt-get upgrade...
>Anyway, could anyone help me to fix this issue, please?
>
>Thanks in advance
>al3xu5
>

I can't offer a fix, but can confirm the same problem here after apt update (on 
chimaera system) with no other config changes so it's caused by something 
that's come through the updates in the last couple of days.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] help: pyton script problem (after package upg?)

2021-04-09 Thread al3xu5
Hi all

Today, after last apt-get upgrade, the `speedtest` python script
(package is `speedtest-cli`) returns errors:

~~~
$ speedtest
Retrieving speedtest.net configuration...
Traceback (most recent call last):
  File "/usr/bin/speedtest", line 11, in 
load_entry_point('speedtest-cli==2.0.2', 'console_scripts',
'speedtest')()
  File "/usr/lib/python3/dist-packages/speedtest.py", line 1887, in main
shell()
  File "/usr/lib/python3/dist-packages/speedtest.py", line 1783, in shell
secure=args.secure
  File "/usr/lib/python3/dist-packages/speedtest.py", line 1027, in
__init__
self.get_config()
  File "/usr/lib/python3/dist-packages/speedtest.py", line 1113, in
get_config
map(int, server_config['ignoreids'].split(','))
ValueError: invalid literal for int() with base 10: ''
~~~

The apt-get log shows:
~~~
Start-Date: 2021-04-07  20:19:56
Commandline: /usr/sbin/synaptic
Requested-By: alexus (1000)
Upgrade: libldb1:amd64 (2:1.5.1+really1.4.6-3,
2:1.5.1+really1.4.6-3+deb10u1), libopenjp2-7:amd64 (2.3.0-2+deb10u1,
2.3.0-2+deb10u2), libcurl4:amd64 (7.64.0-4+deb10u1, 7.64.0-4+deb10u2),
libjs-underscore:amd64 (1.9.1~dfsg-1, 1.9.1~dfsg-1+deb10u1),
libcurl4-gnutls-dev:amd64 (7.64.0-4+deb10u1, 7.64.0-4+deb10u2),
python-lxml:amd64 (4.3.2-1+deb10u2, 4.3.2-1+deb10u3), curl:amd64
(7.64.0-4+deb10u1, 7.64.0-4+deb10u2), libcurl3-gnutls:amd64
(7.64.0-4+deb10u1, 7.64.0-4+deb10u2) End-Date: 2021-04-07  20:20:10 ~~~

I am not sure the problem is related to the last apt-get upgrade...
Anyway, could anyone help me to fix this issue, please?

Thanks in advance
al3xu5

-- 
Say NO to copyright, patents, trademarks and industrial design
restrictions!


Public GPG/PGP key: 8FC2 3121 2803 86E9 F7D8  B624 DA50 835B 2624 A36B
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBGA33HkBEADFmx3R2dWhG3Zf2/jwNiUZBtxAJ96bX+JDIdDUHlbmyPVPvi6T
hIFPD7AA1m6h3ydA2WkbrwhchJJ/xi3LJF8eWE8mUu2HiVXsn3cC9NwRo7tSlq2Z
LqsLrsnBWHNk3Q4cRHolq8/gQvZJ8Z4dd7olhzajNY8sTRB4EXe7vQQ1KI5erEQe
S1a6PY1cq8jiNcAQYwl5JrkKQYf3r3ZjCeswx3Fu8D6QU2IZTTBRt0iyZ85wEgiu
EgvOfdidmX7EEZ/H1jxMoJH/irNvO6u9iRNuJWzIUR7VLcagckdl60htAgfPvyqJ
q/B7BsAs6UmWs0dZ+fX4f69w3L1MQjf0U6KVmjcHwr7pUvNfzN6z/qtVYc0ZH3KI
JFMMhlDMu8xXnsM0Xu9tnXa2KT+Mjj9njKkTUb1YLi8OEqHvF05XkK+P9C1EgNW3
PKrPrZDbgs1adXWmqf67Ndxcu9l6aXp3Lcm4ImdOztLVcN09H6z1elD+3Q4iyIP1
SVFOQkZylqXHPISPqbW432lMXrQ+PoOU6z7/COClkbsmfPfoFG9kSDb1f6awSoTU
hmC6Dt1ZT471A5KWGzxLZr1amBYAybo5KxdWaCSx+tlx7Gu9EeC8djzox5lQ9kQY
4rVRTy2alVC/OZf+mNdq8DRZgCazEw08Nb2Ti0gJbS/odgI+zr4vNKCB0QARAQAB
tCRhbGV4dXMgKEEpIDxkb3Rjb21tb25AYXV0aXN0aWNpLm9yZz6JAk4EEwEKADgW
IQSPwjEhKAOG6ffYtiTaUINbJiSjawUCYDfceQIbAwULCQgHAgYVCgkICwIEFgID
AQIeAQIXgAAKCRDaUINbJiSjaxaUEACukthCkgxgLwZ51KXUOQWNQu70kZVI/6ZT
JrrjfZhQfg4kPfAHxLR2wYFEx9y/kIvLUtEI/tVNjTWi4INCuQuF05+qu73JNPqe
ZQLY0bNybiyBtywzxlC0G8MU/UeNrydg7sPaCXDHBbsXDQslLR1ZU4DdQZUWIVLd
GD7rBnqGQZUgxzP918dmXCT2eIdZT6dkBZzKAPJh6KL0RYBjlWKvmD7jOkaP+EC/
jIXBXKlQkXyOlLaaYXVUQPREY+doXAgdIhq1SOlgnNZexqcJLUtqZJOBI4GFuaEN
2EQHtJ8MmafPXfAy9ZW/UtYMb1L4AvgGY4G6bWj4PItxdrtCW9Ylzx7EarWYPgzn
wRssH64XDRhNe6+1jy8tIpEor/mg//kPCxD1xEObds6jLqc6n4nqrqfLu8DRN30y
NmKsQAmv7KiB5T6yjCse5qkNaKaKatBjkL6ZDpIi5EZQke6ArF5H5En81g0sYHH1
tw7pD5NPulLLCasaXyjdyu5oE93dHRSG8nXzVUWvgIhdr2fUOhD2LtOUO0wa03be
e3qaMRjmjf5YHX/ciG7IXctuhGCboLp/wEk56bia4+EOXilKI9XmyEjQbR1zblx1
zLDEvCA3MibRqHa4YUf5xqfovENj8kKfhz4AfrRGk0QuWb/xF+36XgxK9zqz38ka
remBGY6KcbkCDQRgN9x5ARAA3E/Ro6CCqmvSupoXmVZ1yyDe1EdSce23B4LwatvQ
dUrMeVhey7BfSlK3eLpR8yfQLQvO3WOlETRyHRKlJIs14hQXjWZ/zzFU5QI/MBkP
EwhfwqtPto0xrOTDyBhdaJsIrajrdR2mYG9UzRL6M4d0HsuSW+cUzhF1fAiVWZM3
p3G8wtcDqoBYu93M4JpSuFOyjpxeeSLOi+WffXkKjF1MLUG07lfoCAdgsaBcsxgY
cmvldcSooRNYX7Q+49sKYDj7cIlW2/WqMRNPaqE4YAWg/NxEYS3BqSLlQ9u1QNbF
VRIrt1Y+4l9HD15dmVR79/EvtQ23XDSlBtmv+eEQnkLbYaG1THYJsxyEdBEytHLu
7hmkAoY+jCJlduBl26GRXFCOqmOQjXo9IaEUrDs0HY5R+VP3U2JDhqwUXsbg0awY
glGHrLiRfhHBIiHImSm/BJCfkYrkgHoxl+XumTPC6XtYs0THv0BtMUlJGUE8rwg+
fLwpemavNxrJKYR3K2/SRlMzLJlIF1uE1JsTGsKyTvEB9IX6I8/4kBLv82WF3tHt
foY8kjb8NUhBcqzGDWCPLifktCmiWiKCHUdgceNbA2lGKGJ0eUfrmThQQQVi1Lry
FW5aaUY6xZhoZMeh8n3iY4w8Arv+jcO41lZynv2VGeLDEUakkheE7jt1NC1oHmwS
PScAEQEAAYkCNgQYAQoAIBYhBI/CMSEoA4bp99i2JNpQg1smJKNrBQJgN9x5AhsM
AAoJENpQg1smJKNrFikQAMOfCgHf83HSYoYJ/PSS0fMJeQgiyBDxxulsHynfOp24
tyFBBVNS/6XZ5eoGHVenLLAjST1x62GsZRmz3L19+vbekEDtefC1IeYLWliqd5x/
h2JG6U8NRW24iGdO70Ii9500zsNKkMmQ/4huLHWHvLUvzfLw06/xI3f/8+kyrs/6
o2eWe0U6/u9C5Kiz5wYMt4Ko8vAFZQgX4p7uC7KI/gax3v0mB+cRqpFY/fxPwOlM
mtTcDq4Kid+5mGeX8bsb8rgIzjglhW9ojIg+pplx+8LgLesNbU1SMTPyqvpClltc
InWyVyj78Gkq9PS2yhVKdmZrlhR8QKc+iDr2+2vv30Z9idA2+siL4HCbYHE4tNdZ
1OM4V5nFYOcBzwj675CcdWxtOxvah7dsSjPX5Pbgy416j5/rgS4l8oP3g+KW9u1F
D8ZXNhRH0tPnS+cY0NFKUNp6D2vA67/fCBOD+nkWU/8f7x2Lo1VeDefDlxPiDrp9
k7yk74ZR3xyRKZGP8PMMmBdmrYJqDaylMtC+yIElYoOF6svlokiHueulKzoLZNZC
F2q7n8mEIFkyqObsXeQRDpQc+PskGXWcBY/fssE7cnuqWyUb9xGkEvl8V6k83YXP
Hp4kKPLhBzoblS+01HEZ4leTkjbW9fIfiyygDlP+8mtxgjCCcfRSRDBXD7eb8Zmo
=3LGw
-END PGP PUBLIC KEY BLOCK-


pgprvjhWGOs1C.pgp
Description: Firma digitale 

Re: [DNG] Gnome 3 Status

2021-04-09 Thread Steve Litt
Olaf Meeuwissen said on Fri, 09 Apr 2021 19:59:26 +0900

>Hi Steve,
>
>Steve Litt writes:
>
>> Mate via Dng said on Fri, 09 Apr 2021 00:23:29 +0300
>>
>>  
>>>My own preference is 3rd Gnome.  
>>
>> What would Gnome give you that you can't get from other Window
>> Managers and Desktop Environments (WM/DE)?  
>
>A familiar work environment, perhaps?

That's always nice, but for a person not wanting systemd, in the long
run Gnome is a dead end. I was wondering about specific features and
elements of workflow.

>
>I ditched GNOME a long while ago myself and did the same with KDE but
>somehow can't get myself to ditch Xfce and get back to a hand-rolled
>.xinitrc like I used to use a couple of decades ago ... go figure.

There's a lot less reason to ditch xfce: It still (AFAIK) works well
with sysvinit and runit and s6 and openrc, without doing anything
special.

>
>It's all really a matter of inertia.

I'm a big fan of inertia. Life's too short to change your workflow
every month. But when you see a dead end coming down the road, or when
the status quo is getting too difficult, sometimes its best to make
your move earlier rather than later.

>Or muscle memory.

I'm a big fan of muscle memory. I use Vim. Nuff said?

But sometimes there are compelling reasons to move to other software
and relearn your muscle memory. Heck, if I never changed muscle memory,
I'd still be using Wordstar :-)

>
>Going off-topic
>
>> By the way, are you a touch typist who can type over 35 wpm?  
>
>In what language?  And what educational level of prose?
>
>I am a touch typist, certified, mind you, and hit somewhere between 135
>and 140 cpm (including spaces and punctuation but no funny accents) on
>a mechanical typewriter way back in secondary school at the exam.  In
>my native language, that works out to about 17 or 18 words for a normal
>newspaper article.  In English, I thinks it's more like 20.  In German
>it'd be even less, probably around 15.  In Japanese ... who knows.

What I was getting at is that the 35 wpm typist, assuming a word is 5
characters and 1 space, is probably better off using a user interface
like I have (simple window manager + dmenu + UMENU2, or XFCE + dmenu
but no UMENU2) rather than a more mousy UI. At 20 WPM, I could make a
case for your using a UI like mine, or make a case for your using a
mouse driven one. My understanding is that Gnome3 has some great
workflow features for the mouse-centric user, but other WM/DEs (Window
Manager or Desktop Environments) are also very performant for the mouse
centric.

>
># And let's not add predictive input methods to the mix ;-)
># Me very much dislikes those.

If you mean these things that guess the word you mean and finish it for
you, yeah, those are horrible.

Anyway, the bottom line is that Gnome is nice and all that, but it's
not the end of the world if you don't use it, and the way things are
going, sooner or later you won't be able to use it, and perhaps it's
better to change your muscle memory at your leisure than to
unexpectedly be forced to do it after an upgrade.

Also, for anyone typing 35 WPM or more, life is more productive when
you use the keyboard more and the mouse less, and that can be
accomplished by adding dmenu, and possibly UMENU2, to any WM/DE.

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Gnome 3 Status

2021-04-09 Thread Olaf Meeuwissen via Dng
Hi Steve,

Steve Litt writes:

> Mate via Dng said on Fri, 09 Apr 2021 00:23:29 +0300
>
>
>>My own preference is 3rd Gnome.
>
> What would Gnome give you that you can't get from other Window Managers
> and Desktop Environments (WM/DE)?

A familiar work environment, perhaps?

I ditched GNOME a long while ago myself and did the same with KDE but
somehow can't get myself to ditch Xfce and get back to a hand-rolled
.xinitrc like I used to use a couple of decades ago ... go figure.

It's all really a matter of inertia.
Or muscle memory.

Going off-topic

> By the way, are you a touch typist who can type over 35 wpm?

In what language?  And what educational level of prose?

I am a touch typist, certified, mind you, and hit somewhere between 135
and 140 cpm (including spaces and punctuation but no funny accents) on a
mechanical typewriter way back in secondary school at the exam.  In my
native language, that works out to about 17 or 18 words for a normal
newspaper article.  In English, I thinks it's more like 20.  In German
it'd be even less, probably around 15.  In Japanese ... who knows.

# And let's not add predictive input methods to the mix ;-)
# Me very much dislikes those.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] SSL certificate or host mapping for ASCII updates for APT

2021-04-09 Thread Olaf Meeuwissen via Dng
Hi Chris,

crich...@blackfoot.net writes:

> On 2021-04-08 15:32, Joril wrote:
>> On 08/04/21 16:40, crichmon@??? wrote:
>> > I'm trying to 'apt update' an ascii box, and the repos in the
>> > aptsource list point here:
>> >
>> > deb http://us.deb.devuan.org/merged ascii main non-free contrib
>>
>> I think that "country mirrors" are deprecated, try using just
>> deb.devuan.org
>
> Actually, I did already try that after reading the docs on the web again,
> and get the same problems using the same debugging tools.
> Sparing the details.
> /tmp# host deb.devuan.org
> deb.devuan.org is an alias for deb.roundr.devuan.org.
> 
> Trying to browse http://deb.devuan.org/ still fails.

The package repositories aren't really meant for browser-based perusal
but http://deb.devuan.org/ displays fine, as in an Apache/2.4 directory
listing, for me.  That may be because I chanced upon an IP address that
supports that but if you *really* have SSL certificate issues, I guess
your browser is *forcing* HTTPS upon you.  Regular HTTP URLs don't use
certificates.

# You might want to make sure you add that http:// at the beginning of
# that URL in your browser's location bar.

> What I hadn't tried was 'apt update', which I'm doing now after
> updating sources.list, and it is working, so apt doesn't exactly have
> the same cert issues.

That's because APT uses HTTP, not HTTPS, per your URL.
APT downloads a signed InRelease file and checks that using GnuPG keys
from the devuan-keyring package.  If that checks out fine, the checksums
in that file are used to verify the Packages and Sources files which, in
turn contain checksums for the individual packages that are verified
before `apt` goes ahead and install things.

That is to say, APT doesn't rely on SSL certificates but on GnuPG keys
to make sure you get exactly what the package maintainers intended.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Screen flickering

2021-04-09 Thread Arnt Karlsen
On Thu, 8 Apr 2021 17:32:30 +0200, Antony wrote in message 
<202104081732.30426.antony.st...@devuan.open.source.it>:

> On Thursday 08 April 2021 at 17:26:42, Bernard Rosset via Dng wrote:
> 
> > >> I would boot from an installation USB / CD (preferably the one
> > >> you set the
> > >> machine up from) and go into Rescue Mode, and see whether the
> > >> hardware still
> > >> continues behaving the same way.  
> > > 
> > > I just did that on the latest Devuan Beowulf Live distro (kernel
> > > 4.19.0-14), and... no flickering!  
> > 
> > Booting back on the internal disk... No flickering.
> > I just don't get it. Would it be hardware/cable-related in the end?
> > *sighs*  
> 
> I would say yes, it sounds like a dodgy cable / solder joint /
> connector to me.

..it could quite simply be dust collected inside your machine causing
overheating triggering hardware trottling to near your power grid
frequency, e.g. down from say 60Hz in a 50Hz country like France, to
say 42Hz, which mould have your screen flicker at say 8Hz.

..fix is easy in this case, open your machine and clean it out with
e.g. pressurized air in a well ventilated area.

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng