On Tue, Nov 29, 2005 at 10:54:41PM -0500, Chris Lawrence wrote:
I am confused as to why you have rated this bug as important. As
you point out, there is no real way to make this determination in
software without breaking the automated sid-etch migration process;
the best that can be hoped for
Patches are, as always, welcome. But maintaining a separate etch
branch of the lsb package (or of base-files) is unrealistic, and
almost certainly would not be approved by the release managers.
More importantly, there is no real heuristic for figuring out whether
or not a system is testing or
On Wed, Nov 30, 2005 at 09:20:36AM -0500, Chris Lawrence wrote:
More importantly, there is no real heuristic for figuring out whether
or not a system is testing or unstable. Even if
/etc/debian_version was modified in etch, that's no guarantee the
system is actually etch - and no guarantee
Package: lsb-release
Version: 3.11
Priority: important
The lsb_release is currently useless in 'etch' because it will always return
'sid' as the codename for the distribution when it's not. This is because it
depends on the /etc/debian_version to determine if it's etch or not, and
because the
I am confused as to why you have rated this bug as important. As
you point out, there is no real way to make this determination in
software without breaking the automated sid-etch migration process;
the best that can be hoped for is an educated guess based on
apt-policy, but even that could be
5 matches
Mail list logo
