12 Sep
2022
12 Sep
'22
midnight
I have acquired a used HP Probook 440 G5, on which I have installed Devuan Chimaera.
The
Chimaera installer balked at adding
| deb http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
| deb-src http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
which continue to fail to work after the install completed; I'm not sure just what
they
provide and if they are really necessary; I couldn't find any useful information
about
them in a web search.
Perhaps these need to be working before installing Trinity? I followed the install
instructions in the Trinity Wiki page
<https://wiki.trinitydesktop.org/Devuan_Trinity_Repository_Installation_Instructions>,
but
| apt-get update
fails with 'E: The repository ... does not have a Release file.' (see attached
command
output, etc.).
Since all of my experience with Linux has been with openSUSE and RedHat, I'm not
sure
what to do to resolve these issues. Help!? :-)
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
12 Sep
12 Sep
12:53 a.m.
On Sunday 11 September 2022 17:00:52 J Leslie Turriff wrote:
I have acquired a used HP Probook 440 G5, on which I
have installed Devuan
Chimaera. The Chimaera installer balked at adding
| deb http://pkgmaster.devuan.org/merged chimaera-security main contrib
| non-free deb-src http://pkgmaster.devuan.org/merged chimaera-security
| main contrib non-free
which continue to fail to work after the install completed; I'm not sure
just what they provide and if they are really necessary; I couldn't find
any useful information about them in a web search.
Perhaps these need to be working before installing Trinity? I followed
the install instructions in the Trinity Wiki page
<https://wiki.trinitydesktop.org/Devuan_Trinity_Repository_Installation_Ins
tructions>, but
| apt-get update
fails with 'E: The repository ... does not have a Release file.' (see
attached command output, etc.).
Since all of my experience with Linux has been with openSUSE and RedHat,
I'm not sure what to do to resolve these issues. Help!? :-)
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
You might need to add or update the keyring for Trinity. Otherwise, if this is
only a problem getting your machine to recognize these repos, then you can do
this:
# Trinity - TDE - ### Acquire::AllowInsecureRepositories
# sudo torify apt-get -o Acquire::AllowInsecureRepositories=true update
# sudo apt-get -o Acquire::AllowInsecureRepositories=true update
(copied from my own sources list)
torify = only if you do everything over Tor
This is not a permanent solution, by any means, and I'm not sure if that's
your problem. In any case, security-minded persons will probably raise a
ruckus and tell you NOT TO DO THIS!!!!!! They will also tell you not to run
with scissors, and not to direct the laser point into your remaining good
eye. But if you just need to get started, try that, as a temporary fix.
Bill
P.S. I changed my TDE repositories to Debian names rather than Devnuan,
because for TDE itself I don't think it matters; I think references to Devuan
packages in the Trinity repos just redirect to give you Debian packages. For
the most part, Debian and Devuan are identical; just not when you are
actually installing from the non-TDE Debian or Devuan repositories. Then you
must choose correctly. But TDE might work better if you specify Debian
instead.
1:40 a.m.
On 2022-09-11 19:53:24 William Morder via tde-users wrote:
On Sunday 11 September 2022 17:00:52 J Leslie Turriff
wrote:
I didn't include that
step in the output above because it worked correctly, creating
| trinity-keyring.deb
in root's directory.
I have acquired a used HP Probook 440 G5, on
which I have installed
Devuan Chimaera. The Chimaera installer balked at adding
| deb http://pkgmaster.devuan.org/merged chimaera-security main contrib
| non-free deb-src http://pkgmaster.devuan.org/merged chimaera-security
| main contrib non-free
which continue to fail to work after the install completed; I'm not sure
just what they provide and if they are really necessary; I couldn't find
any useful information about them in a web search.
Perhaps these need to be working before installing Trinity? I followed
the install instructions in the Trinity Wiki page
<https://wiki.trinitydesktop.org/Devuan_Trinity_Repository_Installation_I
ns tructions>, but
| apt-get update
fails with 'E: The repository ... does not have a Release file.' (see
attached command output, etc.).
Since all of my experience with Linux has been with openSUSE and RedHat,
I'm not sure what to do to resolve these issues. Help!? :-)
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
You might need to add or update the keyring for Trinity. Otherwise, if this is only a problem getting your
machine to recognize these repos, then
you can do this:
# Trinity - TDE - ### Acquire::AllowInsecureRepositories
# sudo torify apt-get -o Acquire::AllowInsecureRepositories=true update
# sudo apt-get -o Acquire::AllowInsecureRepositories=true update
I guess the ###
should be separate lines? and this might correct the '... does not have a
Release file.'?
(copied from my own sources list)
torify = only if you do everything over Tor
This is not a permanent solution, by any means, and I'm not sure if that's
your problem. In any case, security-minded persons will probably raise a
ruckus and tell you NOT TO DO THIS!!!!!! They will also tell you not to run
with scissors, and not to direct the laser point into your remaining good
eye. But if you just need to get started, try that, as a temporary fix.
Okay,
I'll give it a try.
Bill
P.S. I changed my TDE repositories to Debian names rather than Devnuan,
because for TDE itself I don't think it matters; I think references to
Devuan packages in the Trinity repos just redirect to give you Debian
packages. For the most part, Debian and Devuan are identical; just not when
you are actually installing from the non-TDE Debian or Devuan repositories.
Then you must choose correctly. But TDE might work better if you specify
Debian instead.
I guess this is just a matter of changing .devuan.org to
.debian.org in the offending
lines? (Sorry; this is my first time experience with non-RPM based Linux.)
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
2:01 a.m.
# Trinity -
TDE - ### Acquire::AllowInsecureRepositories
# sudo torify apt-get -o Acquire::AllowInsecureRepositories=true update
# sudo apt-get -o Acquire::AllowInsecureRepositories=true update
I guess the ### should be separate lines? and this might correct the '...
does not have a Release file.'?
3:31 a.m.
On 2022-09-11 21:01:49 William Morder via tde-users wrote:
No, I just commented out these lines because they would only screw up apt
or aptitude or whatever you use to download packages and src files. I just
put the notes in my sources list so that I have them for reference, because
about every third or fourth time I install a new system, the TDE
repositories aren't accepted. Instead of screwing round endlessly, this
line gets me started:
sudo [torify] apt-get -o Acquire::AllowInsecureRepositories=true update
instead of
sudo [torify] apt-get update
I included the lines from my own sources.list. It works for me; that's the
only promise I make. Other people do things differently, and they may know
better. You will note that I have identical lines for chimaera and
bullseye, but one or the other is commented out; that's because chimaera
wasn't being recognized (when I tried to download the Trinity packages),
but bullseye was.
It doesn't matter for TDE (I believe; if I'm wrong, please correct me!):
they will work equally under either Debian or Devuan. Trinity desktop is
not part of either Debian or Devuan (or SUSE or whatever). The packages
ought to be the same for Debian/Devuan. Use whatever lines work.
Only when you decide to install either Devuan or Debian, then it matters a
great deal. Again, most of the packages are identical, or at least ought to
work; but those that don't work will maybe mess up your system and you'll
need to start over. So make sure you get your Devuan/Debian lines right,
whatever you choose to install.
Bill
Heh. I got my Trinity repositories working by changing ...-r14.0.12 to ..-r14.0.x, which
I should have remembered, having made the same mistake with the openSUSE repositories
long ago. :-)
Changing
| http://deb.devuan.org/merged
| http://pkgmanager.devuan.org/merged
to
| https://deb.devuan.org/merged
| https://pkgmanager.devuan.org/merged
got me further, but the first one gets a bad certificate error (that it tells me will be
valid in 6min 36secs).
Aaaand...eight minutes later it says it will be valid in 3h 58min 18s. I'll try
substituting debian for devuan...
The deb repository is what provides the base OS binaries, right? If so, there's no
way to
install or upgrade the OS on the machine until I get it working?
Leslie
--
# Trinity - TDE - ###
Acquire::AllowInsecureRepositories
# sudo torify apt-get -o Acquire::AllowInsecureRepositories=true update
# sudo apt-get -o Acquire::AllowInsecureRepositories=true update
I guess the ### should be separate lines? and this might correct
the '... does not have a Release file.'?
3:54 a.m.
On 2022-09-11 22:31:59 J Leslie Turriff wrote:
Heh. I got my Trinity repositories working by
changing
...-r14.0.12 to ..-r14.0.x, which I should have remembered, having made the
same mistake with the openSUSE repositories long ago. :-)
Changing
| http://deb.devuan.org/merged
| http://pkgmanager.devuan.org/merged
to
| https://deb.devuan.org/merged
| https://pkgmanager.devuan.org/merged
got me further, but the first one gets a bad certificate error (that it
tells me will be valid in 6min 36secs).
Aaaand...eight minutes later it says it will be valid in 3h 58min
18s. I'll try substituting debian for devuan...
The deb repository is what provides the base OS binaries, right? If so,
there's no way to install or upgrade the OS on the machine until I get it
working?
Leslie
But it turns out that deb.debian.org/debian/ doesn't have a merge/ subdirectory,
only
| debian/
| debian-debug/
| debian-ports/
| debian-security/
so I have no idea what to use instead. The Debian Administrator's Handbook has no
information about repository tree structures.
And pkgmaster.devuan.org/merged still has a bad certificate, and there is no
pkgmaster.debian.org.
Having exhausted these possibilities, I tried your apt-get -o Acquire::... method, but
that failed, too. See attached.
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
4:08 a.m.
On Sunday 11 September 2022 20:54:41 J Leslie Turriff wrote:
For the official Debian or Devuan repositories (whatever one's choice to
install), do not mix packages. Choose one or the other, then (since you're
picking Devuan) choose Devuan repositories.
I tend to use pkgmaster repos; I forget why, but you see that I have both
here, just commented out the devuan.org lines.
Most Debian packages (I hear) are, or used to be, interchangeable with Devuan;
originally only those that were connected with systemd were different, but
I've heard that it's best not to mix them.
For TDE repositories (and probably for other special repos, too, desktops or
multimedia, etc.) it does not matter, as far as I know. Those are mostly
interchangeable, I think, at least for TDE. But Slavek and others will know;
I am just repeating what I've heard.
Here are my lines for the Devuan repositories:
# deb cdrom:[Devuan GNU/Linux 3.0 (chimaera) i386 - netinstall 20200526]/
chimaera main contrib non-free
#deb http://deb.devuan.org/merged chimaera main
#deb http://deb.devuan.org/merged chimaera-updates main
#deb http://deb.devuan.org/merged chimaera-security main
#deb http://deb.devuan.org/devuan experimental main
#deb-src http://deb.devuan.org/devuan experimental main
deb http://pkgmaster.devuan.org/merged chimaera main
deb-src http://pkgmaster.devuan.org/merged chimaera main
deb http://pkgmaster.devuan.org/merged chimaera-security main
deb-src http://pkgmaster.devuan.org/merged chimaera-security main
# chimaera-updates, previously known as 'volatile'
deb http://pkgmaster.devuan.org/merged chimaera-updates main
deb-src http://pkgmaster.devuan.org/merged chimaera-updates main
deb http://pkgmaster.devuan.org/merged chimaera-backports main
deb-src http://pkgmaster.devuan.org/merged chimaera-backports main
|
http://deb.devuan.org/merged
| http://pkgmanager.devuan.org/merged
to
| https://deb.devuan.org/merged
| https://pkgmanager.devuan.org/merged
got me further, but the first one gets a bad certificate error (that it
tells me will be valid in 6min 36secs).
��������Aaaand...eight minutes later it says it will be valid in
3h 58min 18s. �I'll try substituting debian for devuan...
The deb repository is what provides the base OS binaries, right? �If so,
there's no way to install or upgrade the OS on the machine until I get it
working?
Leslie
But it turns out that deb.debian.org/debian/ doesn't have a merge/
subdirectory, only
| debian/
| debian-debug/
| debian-ports/
| debian-security/
so I have no idea what to use instead. The Debian Administrator's Handbook
has no information about repository tree structures.
And pkgmaster.devuan.org/merged still has a bad certificate, and there is
no pkgmaster.debian.org.
Having exhausted these possibilities, I tried your apt-get -o Acquire::...
method, but that failed, too. See attached.
Leslie 
4:25 a.m.
On Sun September 11 2022 21:08:08 William Morder via tde-users wrote:
Most Debian packages (I hear) are, or used to be,
interchangeable with
Devuan; originally only those that were connected with systemd were
different, but I've heard that it's best not to mix them.
For TDE repositories (and probably for other special repos, too, desktops
or multimedia, etc.) it does not matter, as far as I know. Those are mostly
interchangeable, I think, at least for TDE. But Slavek and others will
know; I am just repeating what I've heard.
Different Debian releases are different snapshots in time. (Snapshots that
evolve over time but "snapshot" is close enough.)
Each Devuan release is mostly based on a particular Debian release but there
are more differences than you want to try to think about. Ubuntu releases
are even further from Debian - second cousins maybe.
So you want to choose precisely one Debian/Devuan/Ubuntu release and use the
matching TDE release that was compiled with the appropriate library versions.
--Mike
6:57 a.m.
Anno domini 2022 Sun, 11 Sep 21:08:08 -0700
William Morder via tde-users scripsit:
On Sunday 11 September 2022 20:54:41 J Leslie Turriff wrote:
For the official Debian or Devuan repositories (whatever one's choice to
install), do not mix packages. Choose one or the other, then (since you're
picking Devuan) choose Devuan repositories.
I tend to use pkgmaster repos; I forget why, but you see that I have both
here, just commented out the devuan.org lines.
Most Debian packages (I hear) are, or used to be, interchangeable with Devuan;
originally only those that were connected with systemd were different, but
I've heard that it's best not to mix them.
For TDE repositories (and probably for other special repos, too, desktops or
multimedia, etc.) it does not matter, as far as I know. Those are mostly
interchangeable, I think, at least for TDE. But Slavek and others will know;
I am just repeating what I've heard.
Here are my lines for the Devuan repositories:
# deb cdrom:[Devuan GNU/Linux 3.0 (chimaera) i386 - netinstall 20200526]/
chimaera main contrib non-free
#deb http://deb.devuan.org/merged chimaera main
#deb http://deb.devuan.org/merged chimaera-updates main
#deb http://deb.devuan.org/merged chimaera-security main
#deb http://deb.devuan.org/devuan experimental main
#deb-src http://deb.devuan.org/devuan experimental main
deb http://pkgmaster.devuan.org/merged chimaera main
deb-src http://pkgmaster.devuan.org/merged chimaera main
deb http://pkgmaster.devuan.org/merged chimaera-security main
deb-src http://pkgmaster.devuan.org/merged chimaera-security main
# chimaera-updates, previously known as 'volatile'
deb http://pkgmaster.devuan.org/merged chimaera-updates main
deb-src http://pkgmaster.devuan.org/merged chimaera-updates main
deb http://pkgmaster.devuan.org/merged chimaera-backports main
deb-src http://pkgmaster.devuan.org/merged chimaera-backports main
+1 Don't ever mix devuan with debian - ok, you can if you feel bored and need a
challenging day and playing with nukes does not fit the bill.
On a sidenote, I'd replace "chimera" with "daedalus". My
/etc/apt/sourcec.list is like this:
deb http://mirror.ppa.trinitydesktop.org/trinity-testing daedalus deps extra main
deb http://pkgmaster.devuan.org/merged daedalus main contrib non-free
If you wonder which devuan repostitories exist, take alook here:
http://pkgmaster.devuan.org/merged/dists/
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
|
http://deb.devuan.org/merged
| http://pkgmanager.devuan.org/merged
to
| https://deb.devuan.org/merged
| https://pkgmanager.devuan.org/merged
got me further, but the first one gets a bad certificate error (that it
tells me will be valid in 6min 36secs).
��������Aaaand...eight minutes later it says it will be valid in
3h 58min 18s. �I'll try substituting debian for devuan...
The deb repository is what provides the base OS binaries, right? �If so,
there's no way to install or upgrade the OS on the machine until I get it
working?
Leslie
But it turns out that deb.debian.org/debian/ doesn't have a merge/
subdirectory, only
| debian/
| debian-debug/
| debian-ports/
| debian-security/
so I have no idea what to use instead. The Debian Administrator's Handbook
has no information about repository tree structures.
And pkgmaster.devuan.org/merged still has a bad certificate, and there is
no pkgmaster.debian.org.
Having exhausted these possibilities, I tried your apt-get -o Acquire::...
method, but that failed, too. See attached.
Leslie
7:46 a.m.
On Sunday 11 September 2022 23:57:44 Dr. Nikolaus Klepp wrote:
+1 Don't ever mix devuan with debian - ok, you can if you feel bored and
need a challenging day and playing with nukes does not fit the bill.
You don't want to let us have any fun at all. I think it was you who told me
not to direct the laser pointer into my good eye.
I agree, of course, about not mixing Debian and Devuan. I was referring to
third-party repositories. You will find that nearly all offer packages made
for Debian, not Devuan. (TDE is just such a third-party repository; also,
examples from my sources.list: vivaldi, signal, seamonkey, gnu.org,
firstlookmedia, vivaldi, videolan, and Apache Open Office.) In those cases,
Debian packages work just fine, at least for me; they don't make Devuan
packages. But as for getting packages from the official Debian or Devuan
repositories: definitely NO.
On a sidenote, I'd replace "chimera"
with "daedalus". My
/etc/apt/sourcec.list is like this:
Is daedalus a LTR? I think maybe that's partly why Leslie chose chimaera (just
guessing). It's in the middle of the pack of stable releases with long-term
support, not close to retirement, not brand-new and unstable.
deb
http://mirror.ppa.trinitydesktop.org/trinity-testing daedalus deps
extra main deb http://pkgmaster.devuan.org/merged daedalus main contrib
non-free
If you wonder which devuan repostitories exist, take alook here:
http://pkgmaster.devuan.org/merged/dists/
This link is very useful. Thanks, Nik!
Nik
13 Sep
13 Sep
9:48 a.m.
Anno domini 2022 Mon, 12 Sep 00:46:44 -0700
William Morder via tde-users scripsit:
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
[...]
Not exactly, it's the next comming stable. People with a bad mouth would call it
"bleeding edge", but it's the equivalent of the current debian stable, so
I'd say it's stable enough for me. But the new kernel 5.19 dmi module causes GPU
hangs on i915 GPUs and old AMD - these are the GPUs found in T60/T61/X61 and a lot of
other laptops of that era. If you have these you need this tiny config to put things
right:
# joe /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "NoAccel" "True"
Option "DRI" "False"
EndSection
Oh, to upgrade from chimera to daedalus just replace "chimaera" with
"daedalus" in the sources.list and do the upgrade (there's no
"updates" or "security-updates" as it's not officially released
yet, so comment these lines if present)
Nik
On a sidenote, I'd replace
"chimera" with "daedalus". My
/etc/apt/sourcec.list is like this:
Is daedalus a LTR? I think maybe that's partly why Leslie chose chimaera
(just
guessing). It's in the middle of the pack of stable releases with long-term
support, not close to retirement, not brand-new and unstable. deb
http://mirror.ppa.trinitydesktop.org/trinity-testing daedalus deps
extra main deb http://pkgmaster.devuan.org/merged daedalus main contrib
non-free
If you wonder which devuan repostitories exist, take alook here:
http://pkgmaster.devuan.org/merged/dists/
This link is very useful. Thanks, Nik!
Nik
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
12 Sep
12 Sep
10:57 p.m.
On 2022-09-12 01:57:44 Dr. Nikolaus Klepp wrote:
On a sidenote, I'd replace "chimera"
with "daedalus". My
/etc/apt/sourcec.list is like this:
deb http://mirror.ppa.trinitydesktop.org/trinity-testing daedalus deps
extra main deb http://pkgmaster.devuan.org/merged daedalus main contrib
non-free
If you wonder which devuan repostitories exist, take alook here:
http://pkgmaster.devuan.org/merged/dists/
Nik
It's a bit late for that; it took me several days just to get chimaera to install,
and
unless up(?)grading to daedalus (the devuan website doesn't list it) fixes the
weirdness
with pkgmaster.devuan.org and deb.devuan.org, I'm reluctant to do it.
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
13 Sep
13 Sep
12:18 a.m.
On Monday 12 September 2022 15:57:19 J Leslie Turriff wrote:
It's a bit late for that; it took me several days just to get chimaera to
install, and unless up(?)grading to daedalus (the devuan website doesn't
list it) fixes the weirdness with pkgmaster.devuan.org and deb.devuan.org,
I'm reluctant to do it.
Leslie
What kind of "weirdness"? Just trying to understand what's going on there.
Devuan/Debian is bit harder than something like Ubuntu, but easier than
Slackware (in my experience). It's not for newbies, but it's not like
visiting an alien planet.
It was difficult to get through the first couple days, but after I copied over
my TDE settings, then things started to get better.
There are lots of Devuan and Debian users on the list, some who have been
running it for decades, so somebody here can probably walk you through the
necessary steps.
Bill
8:46 a.m.
On 2022-09-12 19:18:09 William Morder via tde-users wrote:
Well, I don't have a screen capture of the messages that came up during the
installation,
but the installer couldn't find the resources it wanted in pkgmaster.devuan.org and
deb.devuan.org, so it marked them inaccessible in source.list.
Lines originally commented out by installer because they failed to verify:
| # deb http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
| # deb-src http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
When I run apt-get update (with or without -o Acquire::AllowInsecureRepositories=true)
using https, I get
| Err:1 https://deb.devuan.org/merged chimaera-updates InRelease
| Certificate verification failed: The certificate is NOT trusted. The name in the
certificate does not match the expected. Could not handshake: Error in the certificate
verification. [IP: 158.69.153.121 443]
and using http, I get
| E: Release file for
https://pkgmaster.devuan.org/merged/dists/chimaera-security/InRelease is not valid yet
(invalid for another 3h 35min 7s). Updates for this repository will not be applied.
Looks like the Trinity repositories are working okay, but without
https://deb.devuan.org/merged, is it safe to install Trinity?
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
It's
a bit late for that; it took me several days just to get
chimaera to install, and unless up(?)grading to daedalus (the devuan
website doesn't list it) fixes the weirdness with pkgmaster.devuan.org
and deb.devuan.org, I'm reluctant to do it.
Leslie
What kind of "weirdness"? Just trying to understand what's going on there.
9:26 a.m.
Anno domini 2022 Tue, 13 Sep 03:46:56 -0500
J Leslie Turriff scripsit:
On 2022-09-12 19:18:09 William Morder via tde-users
wrote:
Well, I don't have a screen capture of the messages that came up during the
installation,
but the installer couldn't find the resources it wanted in pkgmaster.devuan.org and
deb.devuan.org, so it marked them inaccessible in source.list.
Lines originally commented out by installer because they failed to verify:
| # deb http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
| # deb-src http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
Just uncomment these lines and rerun the update. Probably a network hickup.
It's a bit late for that; it took me several days just to get
chimaera to install, and unless up(?)grading to daedalus (the devuan
website doesn't list it) fixes the weirdness with pkgmaster.devuan.org
and deb.devuan.org, I'm reluctant to do it.
Leslie
What kind of "weirdness"? Just trying to understand what's going on there.
When I run apt-get update (with or without -o
Acquire::AllowInsecureRepositories=true)
using https, I get
| Err:1 https://deb.devuan.org/merged chimaera-updates InRelease
| Certificate verification failed: The certificate is NOT trusted. The name in the
certificate does not match the expected. Could not handshake: Error in the certificate
verification. [IP: 158.69.153.121 443]
and using http, I get
| E: Release file for
https://pkgmaster.devuan.org/merged/dists/chimaera-security/InRelease is not valid yet
(invalid for another 3h 35min 7s). Updates for this repository will not be applied.
Your system clock is off. Either correct the time in the BIOS or run
"ntpdate-debain" - that is, if that package got installed.
Just in case you run into the expired root key (when your installer is from prior 4th
sept.) install the key manually (https://dev1galaxy.org/viewtopic.php?id=5213):
# wget
http://deb.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2022…
# sha256sum devuan-keyring_2022.09.04_all.deb
96c4a206e8dfdc21138ec619687ef9acf36e1524dd39190c040164f37cc3468d
# dpkg -i devuan-keyring_2022.09.04_all.deb
Looks like the Trinity repositories are working okay,
but without
https://deb.devuan.org/merged, is it safe to install Trinity?
You won't be able to perform the actual update, but you will be able to download the
packages. On a later run - when your time and network is fixed - they will be installed.
Nik
Leslie
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
14 Sep
14 Sep
2:25 a.m.
On 2022-09-13 04:26:17 Dr. Nikolaus Klepp wrote:
Hm. there is no ntpdate-debain (debian?) installed, and it seems, no way to install it
at the moment. I'll see what I can do with the BIOS.
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
Anno domini 2022 Tue, 13 Sep 03:46:56 -0500
J Leslie Turriff scripsit:
> On 2022-09-12 19:18:09 William Morder via tde-users wrote:
[snip]
https://pkgmaster.devuan.org/merged/dists/chimaera-security/InRelease is
not valid yet (invalid for another 3h 35min 7s). Updates for this
repository will not be applied.
Your system clock is off. Either correct the time in the BIOS or run
"ntpdate-debain" - that is, if that package got installed.
Nik
> Leslie
13 Sep
13 Sep
9:36 a.m.
On Tuesday 13 September 2022 01:46:56 J Leslie Turriff wrote:
Lines originally commented out by installer
because they failed to
verify:
| # deb http://pkgmaster.devuan.org/merged chimaera-security main contrib
non-free
| # deb-src http://pkgmaster.devuan.org/merged chimaera-security main contrib
non-free
These should not be commented out! otherwise the system will ignore them.
| Err:1 https://deb.devuan.org/merged chimaera-updates InRelease
| Certificate verification failed: The certificate is NOT trusted. The
| name in the
certificate does not match the expected. Could not handshake: Error in the
certificate verification. [IP: 158.69.153.121 443]
and using http, I get
| E: Release file for
https://pkgmaster.devuan.org/merged/dists/chimaera-security/InRelease is
not valid yet (invalid for another 3h 35min 7s). Updates for this
repository will not be applied.
Looks like the Trinity repositories are working okay, but without
https://deb.devuan.org/merged, is it safe to install Trinity?
Leslie
Could you please attach a copy of your sources.list? (or just copy and paste
the lines from it); I wonder if you have it set up correctly. Those lines
should not be commented out; even if they are not working, they ought to be
uncommented, otherwise the system will ignore them. (You may already know
this, and I am misreading what you write; but I'm just trying to hit the
obvious points.)
I seem to recall seeing error messages like that in the not-too-distant past,
and now I have managed to get everything installed, and updates work fine
without doing anything special (such as allowing insecure repositories), so
it is possible to get there.
Bill
14 Sep
14 Sep
2:33 a.m.
On 2022-09-13 04:36:08 William Morder via tde-users wrote:
I have attached the sources.list in its current state, and
the output from apt-get
update. (This is before setting the clock via the BIOS.)
On Tuesday 13 September 2022 01:46:56 J Leslie Turriff
wrote:
Of
course. :-)
Lines originally commented out by installer
because they failed to
verify:
| # deb http://pkgmaster.devuan.org/merged chimaera-security main
| contrib
non-free
| # deb-src http://pkgmaster.devuan.org/merged chimaera-security main
| contrib
non-free
These should not be commented out! otherwise the system will ignore them. | Err:1 https://deb.devuan.org/merged
chimaera-updates InRelease
| Certificate verification failed: The certificate is NOT trusted. The
| name in the
certificate does not match the expected. Could not handshake: Error in
the certificate verification. [IP: 158.69.153.121 443]
and using http, I get
| E: Release file for
https://pkgmaster.devuan.org/merged/dists/chimaera-security/InRelease is
not valid yet (invalid for another 3h 35min 7s). Updates for this
repository will not be applied.
Looks like the Trinity repositories are working okay, but without
https://deb.devuan.org/merged, is it safe to install Trinity?
Leslie
Could you please attach a copy of your sources.list? (or just copy and
paste the lines from it); I wonder if you have it set up correctly. Those
lines should not be commented out; even if they are not working, they ought
to be uncommented, otherwise the system will ignore them. (You may already
know this, and I am misreading what you write; but I'm just trying to hit
the obvious points.)
I seem to recall seeing error messages like that in the not-too-distant
past, and now I have managed to get everything installed, and updates work
fine without doing anything special (such as allowing insecure
repositories), so it is possible to get there.
Bill
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
2:53 a.m.
On Tuesday 13 September 2022 19:33:18 J Leslie Turriff wrote:
On 2022-09-13 04:36:08 William Morder via tde-users
wrote:
I have attached the sources.list in its current state, and the output from
apt-get update. (This is before setting the clock via the BIOS.)
Okay, this may sound crazy, but when I open the text file of your
sources.list, there is this YUUUUGGGE gaping hole in the middle of the lines,
between "merged" and "chimaera": I attached a screenshot to show what
I mean.
Could it be as simple as a problem in typesetting? Maybe those holes don't
show up for you, for some reason. I am using an old version of leafpad,
simple text editor, to open it up.
So apt-get update never quite completes. (The output from my own apt-get
update is as appended below as a P.S.) I have lines that you don't need, of
course, at least not yet; but this is how it looks for me.
Most obvious is that I don't see gpg for any of these, so I ask again if you
downloaded and installed the keyrings. You should be able to bypass that
problem (temporarily!) with that "authenticate insecure repositories"
command, but that's definitely not a good long-term plan.
My guess is, if it's not those holes in your sources.list, then you're missing
your keyrings.
Bill
P.S. apt-get update
output
Get:1 http://pkgmaster.devuan.org/merged chimaera InRelease [33.5 kB]
Ign:3 https://repo.vivaldi.com/snapshot/deb stable InRelease
Get:4 http://pkgmaster.devuan.org/merged chimaera-security InRelease [26.2 kB]
Get:6 https://repo.vivaldi.com/snapshot/deb stable Release [3,840 B]
Get:7 http://pkgmaster.devuan.org/merged chimaera-updates InRelease [26.1 kB]
Get:8 https://repo.vivaldi.com/snapshot/deb stable Release.gpg [833 B]
Get:9 http://pkgmaster.devuan.org/merged chimaera-backports InRelease [26.2
kB]
Hit:2 http://ftp.fau.de/trinity/deb/trinity-r14.0.x bullseye InRelease
Get:11 http://pkgmaster.devuan.org/merged chimaera-security/main Sources [110
kB]
Get:13 http://pkgmaster.devuan.org/merged chimaera-security/main amd64
Packages [185 kB]
Get:14 https://repo.vivaldi.com/snapshot/deb stable/main amd64 Packages [1,371
B]
Hit:5 http://ftp.fau.de/trinity/deb/trinity-builddeps-r14.0.x bullseye
InRelease
Get:15 http://pkgmaster.devuan.org/merged chimaera-backports/main Sources [286
kB]
Get:16 http://pkgmaster.devuan.org/merged chimaera-backports/main amd64
Packages [334 kB]
Get:10 http://tde-mirror.yosemite.net/trinity/deb/trinity-sb bullseye
InRelease [36.2 kB]
Get:12 https://apt.signalsciences.net/release/debian bullseye InRelease [24.8
kB]
Get:17 http://tde-mirror.yosemite.net/trinity/deb/trinity-sb bullseye/main-r14
Sources [64.2 kB]
Get:18 http://tde-mirror.yosemite.net/trinity/deb/trinity-sb bullseye/main-r14
amd64 Packages.diff/Index [3,764 B]
Ign:18 http://tde-mirror.yosemite.net/trinity/deb/trinity-sb bullseye/main-r14
amd64 Packages.diff/Index
Get:19 http://tde-mirror.yosemite.net/trinity/deb/trinity-sb bullseye/main-r14
amd64 Packages [256 kB]
Get:20 https://apt.signalsciences.net/release/debian bullseye/main amd64
Packages [8,124 B]
Fetched 1,427 kB in 10s (139 kB/s)
On Tuesday 13 September 2022 01:46:56 J Leslie
Turriff wrote:
Of course. :-)
Lines originally commented out by installer
because they failed
to
verify:
| # deb http://pkgmaster.devuan.org/merged chimaera-security main
| contrib
non-free
| # deb-src http://pkgmaster.devuan.org/merged chimaera-security main
| contrib
non-free
These should not be commented out! otherwise the system will ignore them. | Err:1
https://deb.devuan.org/merged chimaera-updates InRelease
| Certificate verification failed: The certificate is NOT trusted.
| The name in the
certificate does not match the expected. Could not handshake: Error in
the certificate verification. [IP: 158.69.153.121 443]
and using http, I get
| E: Release file for
https://pkgmaster.devuan.org/merged/dists/chimaera-security/InRelease
is not valid yet (invalid for another 3h 35min 7s). Updates for this
repository will not be applied.
Looks like the Trinity repositories are working okay, but without
https://deb.devuan.org/merged, is it safe to install Trinity?
Leslie
Could you please attach a copy of your sources.list? (or just copy and
paste the lines from it); I wonder if you have it set up correctly. Those
lines should not be commented out; even if they are not working, they
ought to be uncommented, otherwise the system will ignore them. (You may
already know this, and I am misreading what you write; but I'm just
trying to hit the obvious points.) I seem to recall seeing error messages like that
in the not-too-distant
past, and now I have managed to get everything installed, and updates
work fine without doing anything special (such as allowing insecure
repositories), so it is possible to get there.
Bill
Leslie 
3:02 a.m.
On 2022-09-13 21:33:18 J Leslie Turriff wrote:
On 2022-09-13 04:36:08 William Morder via tde-users
wrote:
I have attached the sources.list in its current state, and the output from
apt-get update. (This is before setting the clock via the BIOS.)
And after updating the clock in the BIOS, apt-get update appears to have succeeded.
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
On Tuesday 13 September 2022 01:46:56 J Leslie
Turriff wrote:
Of course. :-)
Lines originally commented out by installer
because they failed
to
verify:
| # deb http://pkgmaster.devuan.org/merged chimaera-security main
| contrib
non-free
| # deb-src http://pkgmaster.devuan.org/merged chimaera-security main
| contrib
non-free
These should not be commented out! otherwise the system will ignore them. | Err:1
https://deb.devuan.org/merged chimaera-updates InRelease
| Certificate verification failed: The certificate is NOT trusted.
| The name in the
certificate does not match the expected. Could not handshake: Error in
the certificate verification. [IP: 158.69.153.121 443]
and using http, I get
| E: Release file for
https://pkgmaster.devuan.org/merged/dists/chimaera-security/InRelease
is not valid yet (invalid for another 3h 35min 7s). Updates for this
repository will not be applied.
Looks like the Trinity repositories are working okay, but without
https://deb.devuan.org/merged, is it safe to install Trinity?
Leslie
Could you please attach a copy of your sources.list? (or just copy and
paste the lines from it); I wonder if you have it set up correctly. Those
lines should not be commented out; even if they are not working, they
ought to be uncommented, otherwise the system will ignore them. (You may
already know this, and I am misreading what you write; but I'm just
trying to hit the obvious points.) I seem to recall seeing error messages like that
in the not-too-distant
past, and now I have managed to get everything installed, and updates
work fine without doing anything special (such as allowing insecure
repositories), so it is possible to get there.
Bill
Leslie
3:36 a.m.
On 2022-09-13 22:06:37 William Morder via tde-users wrote:
On Tuesday 13 September 2022 20:02:32 J Leslie Turriff
wrote:
Until I noticed that the Devuan install webpage says there should be three entries, for
|devuan
|devuan-update
|devuan-security
and I had left out the first one. After adding it, once again I'm getting the
'...is not
valid...' messages. I tried installing ntpdate-deb??n, but both spellings fail
with 'Unable to locate package ntpdate-deb??n'
On the other hand, apt-get install tde-trinity is proceeding without errors, with the
side effect of loading many packages from http://deb.devuan.org/merged apparently without
problems; so perhaps this clock thing is actually a problem with the repository server?
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
On 2022-09-13 21:33:18 J Leslie Turriff wrote:
And after updating the clock in the BIOS, apt-get update appears to have
succeeded.
Leslie
YAY!!!!
Bill
6:08 a.m.
On Tue September 13 2022 20:36:44 J Leslie Turriff wrote:
and I had left out the first one. After adding it,
once again I'm getting
the '...is not valid...' messages. I tried installing ntpdate-deb??n, but
both spellings fail with 'Unable to locate package ntpdate-deb??n'
The package you need is just "ntp" so "apt-get install ntp".
On the other hand, apt-get install tde-trinity is
proceeding without
errors, with the side effect of loading many packages from
http://deb.devuan.org/merged apparently without problems; so perhaps this
clock thing is actually a problem with the repository server?
It's "random" in that it depends on whether your PC's erroneous clock
lies
within the validity window of the validation criteria. "ntp" - maybe after
ten or twenty minutes depending how bad it is - will adjust your clock. You
don't need to run any commands. It starts working upon installation and
after every reboot.
--Mike
9:28 a.m.
Anno domini 2022 Tue, 13 Sep 22:36:44 -0500
J Leslie Turriff scripsit:
On 2022-09-13 22:06:37 William Morder via tde-users
wrote:
The package with "ntpdate-debian" is called "ntpsec-ntpdate" - sound
obvious, doesn't it? You can search for it with these commands - that is, if
"aptitude" and/or "apt-file" are installed (which they are not, by
default, but the packages providing these commands are called "aptitude" and
"apt-file"):
aptitude search ntpsec-ntpdate
apt-file search ntpsec-ntpdate
Nik
On Tuesday 13 September 2022 20:02:32 J Leslie
Turriff wrote:
Until I noticed that the Devuan install webpage says there should be three entries, for
|devuan
|devuan-update
|devuan-security
and I had left out the first one. After adding it, once again I'm getting the
'...is not
valid...' messages. I tried installing ntpdate-deb??n, but both spellings fail
with 'Unable to locate package ntpdate-deb??n'
On the other hand, apt-get install tde-trinity is proceeding without errors, with the
side effect of loading many packages from http://deb.devuan.org/merged apparently
without
problems; so perhaps this clock thing is actually a problem with the repository server?
On 2022-09-13 21:33:18 J Leslie Turriff wrote:
And after updating the clock in the BIOS, apt-get update appears to have
succeeded.
Leslie
YAY!!!!
Bill
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
9:37 a.m.
oops, typos ...
Anno domini 2022 Wed, 14 Sep 11:28:01 +0200
Dr. Nikolaus Klepp scripsit:
Anno domini 2022 Tue, 13 Sep 22:36:44 -0500
[...]
The package with "ntpdate-debian" is called "ntpsec-ntpdate" - sound
obvious, doesn't it? You can search for it with these commands - that is, if
"aptitude" and/or "apt-file" are installed (which they are not, by
default, but the packages providing these commands are called "aptitude" and
"apt-file"):
aptitude search ntpsec-ntpdate
apt-file search ntpsec-ntpdate
Ok, this was a copy&past error. You can search for the package containing a cerain
file with apt-file, not aptitude:
$ apt-file search ntpdate-debian
ntpsec-ntpdate: /usr/sbin/ntpdate-debian
ntpsec-ntpdate: /usr/share/man/man8/ntpdate-debian.8.gz
Nik
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
11:06 a.m.
On Wednesday 14 September 2022 02:37:01 Dr. Nikolaus Klepp wrote:
oops, typos ...
Anno domini 2022 Wed, 14 Sep 11:28:01 +0200
Dr. Nikolaus Klepp scripsit:
You know, it occurs to me that there are many on this list who would advise
that everybody without exception ought to use aptitude instead of apt-get.
Indeed, I was going to say this earlier, and held my tongue,
Some of us old guys are used to apt-get, but this might be a good move, as it
will basically do it all for you, and could possibly give you more
information, if not actually resolve your issues by some automagical method,
inscrutable to us mortals.
Bill
Anno domini 2022 Tue, 13 Sep 22:36:44 -0500
[...]
The package with "ntpdate-debian" is called "ntpsec-ntpdate" - sound
obvious, doesn't it? You can search for it with these commands - that is,
if "aptitude" and/or "apt-file" are installed (which they are not,
by
default, but the packages providing these commands are called "aptitude"
and "apt-file"):
aptitude search ntpsec-ntpdate
apt-file search ntpsec-ntpdate
Ok, this was a copy&past error. You can search for the package containing a
cerain file with apt-file, not aptitude:
$ apt-file search ntpdate-debian
ntpsec-ntpdate: /usr/sbin/ntpdate-debian
ntpsec-ntpdate: /usr/share/man/man8/ntpdate-debian.8.gz
Nik
2:57 p.m.
Anno domini 2022 Wed, 14 Sep 04:06:27 -0700
William Morder via tde-users scripsit:
On Wednesday 14 September 2022 02:37:01 Dr. Nikolaus Klepp wrote:
Oh yes ... but I would suggest to use both (ugh, heresy, light the torches, get the
forks!). Especially when you do some interesting stuff - like upgrading from beowulf to
daedalus 'cause you forgot chimera and you are already knee deep in semifluid brown
stuff ...
oops, typos ...
Anno domini 2022 Wed, 14 Sep 11:28:01 +0200
Dr. Nikolaus Klepp scripsit:
You know, it occurs to me that there are many on this list who would advise
that everybody without exception ought to use aptitude instead of apt-get. Anno domini 2022 Tue, 13 Sep 22:36:44 -0500
[...]
The package with "ntpdate-debian" is called "ntpsec-ntpdate" - sound
obvious, doesn't it? You can search for it with these commands - that is,
if "aptitude" and/or "apt-file" are installed (which they are not,
by
default, but the packages providing these commands are called "aptitude"
and "apt-file"):
aptitude search ntpsec-ntpdate
apt-file search ntpsec-ntpdate
Ok, this was a copy&past error. You can search for the package containing a
cerain file with apt-file, not aptitude:
$ apt-file search ntpdate-debian
ntpsec-ntpdate: /usr/sbin/ntpdate-debian
ntpsec-ntpdate: /usr/share/man/man8/ntpdate-debian.8.gz
Nik Indeed, I was going to say this earlier, and held my
tongue,
Some of us old guys are used to apt-get, but this might be a good move, as it
will basically do it all for you, and could possibly give you more
information, if not actually resolve your issues by some automagical method,
inscrutable to us mortals.
The resolver is what makes me use both - each one has it's ups and downs and both work
in general very reliable as long as you are not too creative :)
Nik
Bill
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
11:09 p.m.
On 2022-09-14 06:06:27 William Morder via tde-users wrote:
You know, it occurs to me that there are many on this
list who would advise
that everybody without exception ought to use aptitude instead of apt-get.
Indeed, I was going to say this earlier, and held my tongue,
Some of us old guys are used to apt-get, but this might be a good move, as
it will basically do it all for you, and could possibly give you more
information, if not actually resolve your issues by some automagical
method, inscrutable to us mortals.
Bill
I'm just following what I see in the Debian Handbook. :-)
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
829
days inactive
831
days old
27 comments
4 participants
participants (4)
-
Dr. Nikolaus Klepp -
J Leslie Turriff -
Mike Bird -
William Morder