15 Nov
2022
15 Nov
'22
10:25 p.m.
Hello all,
I have installed MX-Linux 21 on a laptop (with xfce). For some things I find
xfce quite nice to use, but I decided to install TDE too (actually I have one
user configured to start xfce and another TDE).
I followed the wiki and created a tde.list in /etc/apt/sources.list.d,
downloaded the keyring and apt-get updated.
- Everything installed fine (using the preliminary builds) and TDE is running
OK
- However, when running apt-get update I got this (at the end of the update):
Traceback (most recent call last):
File "/usr/lib/cnf-update-db", line 26, in <module>
col.create(db)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 95,
in create
self._fill_commands(con)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 143,
in _fill_commands
self._parse_single_contents_file(con, f, fp.stdout)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 282,
in _parse_single_contents_file
priority = component_priorities[component]
KeyError: 'deps-r14'
It does not seem to hurt, but I wonder what it is.
Using the regular stable release has the same effect, commenting all lines in
tde.list results in no message, so it's linked to the tde repositories
somehow.
Thierry
16 Nov
16 Nov
3:21 a.m.
On Tuesday 15 November 2022 04:25:42 pm Thierry de Coulon wrote:
Hello all,
I have installed MX-Linux 21 on a laptop (with xfce). For some things I
find xfce quite nice to use, but I decided to install TDE too (actually I
have one user configured to start xfce and another TDE).
I followed the wiki and created a tde.list in /etc/apt/sources.list.d,
downloaded the keyring and apt-get updated.
- Everything installed fine (using the preliminary builds) and TDE is
running OK
- However, when running apt-get update I got this (at the end of the
update):
Traceback (most recent call last):
File "/usr/lib/cnf-update-db", line 26, in <module>
col.create(db)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line
95, in create
self._fill_commands(con)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line
143, in _fill_commands
self._parse_single_contents_file(con, f, fp.stdout)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line
282, in _parse_single_contents_file
priority = component_priorities[component]
KeyError: 'deps-r14'
It does not seem to hurt, but I wonder what it is.
Using the regular stable release has the same effect, commenting all lines
in tde.list results in no message, so it's linked to the tde repositories
somehow.
Hi Thierry,
TDE on an MX/Xfce install has known issues. TDE on MX base (no desktop
installed) works well, but is takes a bit more blind command line to do.
I’ve done both. I very much like the MX/antiX Package Installer (which can
be manually installed on base or comes automatically installed on Xfce).
Did you use the instructions from here?
https://wiki.trinitydesktop.org/MX_Linux_Trinity_Repository_Installation_In…
The attached Tde.xml includes fixes to help TDE co-exist on an MX/Xfce
install. (see section: “tde.pm does”)
Full disclosure: The MX devs and I created it for MX-19(buster)*. And while
I believe it should work for MX-21, I’m probably moving to anitX when my
current MX-19 goes EOL, so I’ve not tested it on MX-21.
Over to Slávek...
Best,
Michael
*
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
System: Kernel: 4.19.0-22-amd64 x86_64 bits: 64 Desktop: Trinity R14.0.13
Distro: MX-19.4_x64 patito feo May 31 2020
5:02 a.m.
Thierry de Coulon composed on 2022-11-15 23:25 (UTC+0100):
Traceback (most recent call last):
File "/usr/lib/cnf-update-db", line 26, in <module>
col.create(db)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 95,
in create
self._fill_commands(con)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 143,
in _fill_commands
self._parse_single_contents_file(con, f, fp.stdout)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 282,
in _parse_single_contents_file
priority = component_priorities[component]
KeyError: 'deps-r14'
It does not seem to hurt, but I wonder what it is.
Using the regular stable release has the same effect,
commenting all lines in
tde.list results in no message, so it's linked to the tde repositories
somehow.
In my limited AntiX/MX experience, trying out AntiX years ago, MX19 only less than
a month ago, they are bigger deviators from a base Debian installation than other
derivatives. Nothing like these errors would surprise me based upon their
interpretation of LSB. I don't anticipate trying AntiX again. MX again would
probably require a bit more ambition than I usually have for exploring new
distros, especially when it comes to TDE. I can't imagine what about TDE on MX
could make it better than TDE on Debian directly for any user with significant
experience with a variety of distros.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
7:38 a.m.
On Wednesday 16 November 2022 06.02:49 Felix Miata wrote:
I can't imagine what about TDE on MX could make it
better than TDE on
Debian directly for any user with significant experience with a variety of
distros.
While I can agree (and my main machine is and remains Debian), I've had to
create a "Linux on a stick" solution for myself and colleagues who had to
cope with a "we'll use MS Office" move at work.
This meant booting a Linux from a USB stick on a Mac Mini (because that's what
we do have installed) and using a Huion Tablet connected to that. Things had
to be simple because the colleagues are Windows/Mac/iPad users.
MX-Linux just did the job: easy to install, easy to setup, correctly sets up
all the hardware and has rolling updates, all that atop what still is Debian
(even if not "pure"). OpenBoard runs from Flatpak, Teams for Linux sort of
works (as we have to use that), Prospect Mail gives access to Outlook (no
choice...).
I may be wrong, but MX being sort of a stable/unstable Debian mix seems a
better choice for people who won't understand the advantages of Debian being
so conservative. On my main machine I am still on Buster, as I did not seen
any major advantage to migrate to Bullseye (and dist-upgrade ended in a
disaster). I do have a bullseye install available, but I am too lazy to
finish the setup :)
Note that so far, the preliminary builds run very well on MX 21, so the error
message does not seem to have any profound meaning.
Thierry
3:32 p.m.
On Wednesday 16 November 2022 01:38:20 am Thierry de Coulon wrote:
I've had to
create a "Linux on a stick" solution for myself and colleagues who had to
cope with a "we'll use MS Office" move at work.
This meant booting a Linux from a USB stick
You're probably best served to create your own MX/TDE ISO (e.g. not installing
Xfce) and if your users need it add the MX tool "MX Package Installer."
You'd need to hit their formus for exact details, but you can start by looking
at "MX Remaster Control Center" (under MX Tools), which "allows you to
rework
an ISO while running Live."
Another (supposed) option is to install into an Oracle VM, configue exactly
how you want the Live USB to end up and create a master Live USB from it.
Based on your users' skill level MX is probably one of the best choices.
Best,
Michael
PS: If your users are going to need to mount their phones on their computers
also add Thunar.
17 Nov
17 Nov
9:43 p.m.
On Wednesday 16 November 2022 06.02:49 Felix Miata wrote:
I can't imagine what about TDE on MX could make it
better than TDE on
Debian directly for any user with significant experience with a variety of
distros.
It's not directly TDE, but I just discovered that Gnome Wireless Display does
work on MX (never managed to get it running on pure Debian).
Thierry
766
days inactive
768
days old
5 comments
3 participants
participants (3)
-
Felix Miata -
Michael -
Thierry de Coulon