On 18/06/23 12:58, Harshula wrote:
Perhaps the best option is to refer this to the Technical Committee to
see if there's a way we can move forward?
Hi Harshula,
there are three open questions here:
1) should Debian provide a way to distinguish between the two
similar-but-not-identical,
Hi Gioele,
From a user perspective, the transition from the previous Python based
lsb_release to the new lsb_release contains this regression.
A solution does not appear to be forthcoming after approx. 9 months of
user reports.
Perhaps the best option is to refer this to the Technical
unblock 1020893 by 1021663
thanks
El 18/6/23 a las 1:56, Harshula escribió:
Hi Santiago,
On 18/6/23 03:04, Gioele Barabucci wrote:
One can use the mechanism discussed in section 5.14.3 of the Developer's
Reference [1]:
1) Block the automatic migration via britney/excuses.
2) When a new
Hi Santiago,
On 18/6/23 03:04, Gioele Barabucci wrote:
One can use the mechanism discussed in section 5.14.3 of the Developer's
Reference [1]:
1) Block the automatic migration via britney/excuses.
2) When a new version is released, dput two different versions: one into
unstable and one into
On 17/06/23 16:53, Harshula wrote:
On 17/6/23 23:26, Gioele Barabucci wrote:
I understand your request and I fully support having better OS
information in unstable and testing (see my request to base-files in
bug #1021663 [1]).
Since package updates transition from unstable to testing, can
Hi Gioele,
On 17/6/23 23:26, Gioele Barabucci wrote:
I understand your request and I fully support having better OS
information in unstable and testing (see my request to base-files in bug
#1021663 [1]).
Since package updates transition from unstable to testing, can you
please elaborate on
Control: severity -1 wishlist
Control: tags -1 wontfix
Control: merge 1020893 -1
On 17/06/23 13:54, Harshula wrote:
The old lsb_release.py script contains the function
guess_release_from_apt(). Can you please add similar functionality to
lsb-release to fix the regression?
Dear Harshula,
I
At the moment, Debian Testing:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux trixie/sid
Release:n/a
Codename: trixie
The previous Python based lsb_release:
testing
---
$ ./lsb_release -a
No LSB modules are available.
Package: lsb-release
Version: 12.0-1
Severity: important
Hi Gioele,
The old lsb_release.py script contains the function
guess_release_from_apt(). Can you please add similar functionality to
lsb-release to fix the regression?
Thanks,
Harshula
9 matches
Mail list logo
