Geoff

$ apt-cache policy 'lsb-release'
lsb-release:
  Installed: 9.20150917
  Candidate: 9.20150917
  Version table:
 *** 9.20150917 100
        100 /var/lib/dpkg/status
     4.1+devuan2 500
        500 https://pkgmaster.devuan.org/merged ascii/main amd64 Packages

while the desktop only knows about 4.1+devuan2. I wonder whether this is from the history as the laptop went from Debian testing to Devuan ASCII, while the desktop went from Debian Jessie to Devuan Jessie to ASCII. /usr/bin/lsb_release on the laptop dates from Aug 2015.

Geoff

#! /usr/bin/python -Es

while my laptop has :-

#! /usr/bin/python3 -Es

I wonder why they are different! And which is the correct one! Presumably the one which gives the correct answer, which is the one that runs Python 2.7 rather than 3.

Geoff

python -v /usr/bin/lsb_release -a

fails to run, while

python3 -v /usr/bin/lsb_release -a

does work, using /usr/lib/python3/dist-packages/lsb_release.py

This version 3 version does not appear to be Devuan specific and returns :-

No LSB modules are available.
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 9 (n/a)
Release:	9
Codename:	n/a

Geoff

python -v /usr/bin/lsb_release -a

then you can see the bits that get pulled in, which includes

/usr/lib/python2.7/dist-packages/lsb_release.pyc matches /usr/lib/python2.7/dist-packages/lsb_release.py

Looking at /usr/lib/python2.7/dist-packages/lsb_release.py

it seems that the mapping of release number to codename is hard coded for jessie and ascii, so that if it were to find version 9 then it would think it is unknown. I have not yet figured out how it discovers the version number.

Geoff

Geoff

Distributor ID:	Devuan
Description:	Devuan GNU/Linux testing/unstable
Release:	testing/unstable
Codename:	n/a

Get:1 http://pkgmaster.devuan.org/merged ascii InRelease [22.2 kB]
Get:2 http://pkgmaster.devuan.org/merged ascii-updates InRelease [22.2 kB]
Get:3 http://pkgmaster.devuan.org/merged ascii-security InRelease [21.6 kB]
Get:4 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages [7,239 kB]
Get:5 http://pkgmaster.devuan.org/merged ascii-security/main amd64 Packages [357 kB]
Fetched 7,662 kB in 5s (1,525 kB/s)
Reading package lists...

After update/dist-upgrade

Distributor ID:	Devuan
Description:	Devuan GNU/Linux 2.0 (ascii)
Release:	2.0
Codename:	ascii

After adding beowulf and doing another update

Distributor ID:	Devuan
Description:	Devuan GNU/Linux 3.0 (n/a)
Release:	3.0
Codename:	n/a

I don't know where your 9 is coming from. I've got a 9 in /etc/debian_version, but it doesn't seem to be interfering.

/etc/devuan_version says "ascii/ceres"
/etc/issue says "Devuan GNU/Linux ascii/ceres \n \l"

/etc/os-release

PRETTY_NAME="Devuan GNU/Linux ascii/ceres"
NAME="Devuan GNU/Linux"
ID=devuan
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://www.devuan.org/support/"
BUG_REPORT_URL="https://bugs.devuan.org/"

I don't know where else to look.

@fungus: I didn't edit any relase files, if that's what you were thinking. I might have added the beowulf line and not run an update until after the change.

# apt-get update
Get:1 https://pkgmaster.devuan.org/merged ascii InRelease [22.2 kB]
Get:2 https://pkgmaster.devuan.org/merged ascii-backports InRelease [22.3 kB]
Get:3 https://pkgmaster.devuan.org/merged ascii-proposed-updates InRelease [22.3 kB]
Get:4 https://pkgmaster.devuan.org/merged ascii-security InRelease [21.6 kB]
Get:5 https://pkgmaster.devuan.org/merged ascii-updates InRelease [22.2 kB]
Get:6 https://pkgmaster.devuan.org/merged ascii-backports/main amd64 Packages [359 kB]
Get:7 https://pkgmaster.devuan.org/merged ascii-security/main amd64 Packages [357 kB]
Fetched 827 kB in 0s (841 kB/s)                             
Reading package lists... Done

# lsb_release -a
No LSB modules are available.
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 9 (n/a)
Release:	9
Codename:	n/a

Neither of the machines is a fresh install and have come via Debian originally, although by different routes. It looks as though there is still some hangover from Debian on the laptop.

Geoff

Dear D1rs, as of yesterday, the "Origin:" field in the Release and InRelease files on pkgmaster.devuan.org and deb.devuan.org has been set to "Devuan" (it was empty before). This should most probably solve several issues related to incomplete or wrong information retrieved (openly or silently) by lsb_release. This includes also a few cases in which Devuan is not correctly "recognised" as a host system.

The change seems to be seamless, even if some users have reported that apt in Beowulf would issue a warning about that: you can safely ignore the warning, and ask apt to continue. Please report any issue with this change. HND KatolaZ

Obviously it is not seamless and you can't just ignore it with apt, you have to say yes for every repository in order to continue, OR YOU CAN NOT continue.  On apt-get it is not even telling you what to adjust and where, just DOES NOT continue and there is NO WAY to continue.

Just so we can set the record straight with what is what!

This practice of "setting things" then make an announcement days later is a pattern with Devuan as it is making announcements on the list pretending there was no issue brought up on the forum.

Why is this like de-ja-vue to me?
FSMR, are you implying those two other users are making it up?  The error messages I mean?

I'm not implying anything, and there's nothing in my posts to even remotely suggest that. Most of this thread consists of reporting and comparing observations, with documentation. This is normal problem-solving behavior. Jumping to conclusions doesn't solve anything.

jimmyjhn suggested in his last post that there was a recent change in the repo. He's right.
Here's the answer: https://dev1galaxy.org/viewtopic.php?pid=9636#p9636

I can also state that I recall someone bringing this to our attention in irc a few days ago.

1 possible scenario is that they are running beowulf, and you are running ascii, so is it possible that your apt and apt-get is a different version than theirs (and corresponding libraries maybe?)
2 I have a feeling this is a mixup in the ascii (testing --> stable) beowulf (unstable --> testing) buster (testing) transition.
3  Your implication that the same repositories, the same procedure, returns different results is a serious one.  I think you should look into it.  I would say no more!

deb http://pkgmaster.devuan.org/merged beowulf main contrib non-free

and then I also tried https:

deb https://pkgmaster.devuan.org/merged beowulf main contrib non-free

I also have ascii, ascii-security and ascii-updates with same address (pkgmaster). The system is ascii. Beowulf is only used to check versions, but I did install something from beowulf as a test. No errors with apt-get update or apt update.