Bug#896672: marked as done (lsb-release: Do not use APT source to guess codenames)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Bug#896672: marked as done (lsb-release: Do not use APT source to guess codenames)

Debian Bug Tracking System
Your message dated Mon, 23 Apr 2018 20:00:33 +0100
with message-id <[hidden email]>
and subject line Re: Bug#896672: lsb-release: Do not use APT source to guess codenames
has caused the Debian Bug report #896672,
regarding lsb-release: Do not use APT source to guess codenames
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [hidden email]
immediately.)


--
896672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896672
Debian Bug Tracking System
Contact [hidden email] with problems

Package: lsb-release
Version: 4.1+devuan2
Severity: normal

Dear Maintainer,

-- Package-specific info:


The lsb_release -c invocation yields results that are dependent on one's
APT sources.list.  Absence of the Origin: field in some of the Devuan
package repository mirrors means that on some systems people see `n/a`
as the codename.  When switching mirrors *and without changing installed
packages*, the output suddenly becomes `ascii`.

# I have only tested this on ascii systems.

I have submitted an issue against the mirrors psuedo-package to get the
Origin: field added, but all the same, I think that lsb_release should
not consult whatever happens to be in the systems /var/lib/apt/lists/
directory as that may have next to no bearing on what is actually
installed when the command is issued.

Inspection of /usr/share/pyshared/lsb_release.py strongly hints that
this behaviour is Devuan specific.  I don't know if it is and, if so,
why it got in but I think it should be removed.

See also
  https://lists.dyne.org/lurker/message/20180420.115057.d298af7b.en.html

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

Architecture: x86_64

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lsb-release depends on:
ii  python  2.7.13-2

Versions of packages lsb-release recommends:
ii  apt  1.4.8

Versions of packages lsb-release suggests:
pn  lsb  <none>

-- no debconf information

Hope this helps,
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Software                        https://my.fsf.org/donate
 Join the Free Software Foundation              https://my.fsf.org/join

On Mon, 2018-04-23 at 21:06 +0900, Olaf Meeuwissen wrote:
> Package: lsb-release
> Version: 4.1+devuan2
>
[...]
> Inspection of /usr/share/pyshared/lsb_release.py strongly hints that
> this behaviour is Devuan specific.  I don't know if it is and, if so,
> why it got in but I think it should be removed.
>

In that case, this should be filed in Devuan's bug tracker, not
Debian's.

Regards,

Adam

attachment0 (1K) Download Attachment