[Bug 1650207] [NEW] original lsb-release file should be preserved for classic mode
Oliver Grawert
ogra at ubuntu.com
Thu Dec 15 10:35:34 UTC 2016
Public bug reported:
when installing the classic snap the modified /etc/lsb-release and /etc
/os-release are used inside the tarball. when compiling code that uses
the content of these files at build time they get the wrong info:
DISTRIB_ID="Ubuntu Core"
DISTRIB_RELEASE=16
DISTRIB_DESCRIPTION="Ubuntu Core 16"
vs:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
we should preserve the original data for these two files and use it
inside the classic container when the classic snap is installed, so
build environments can match against the correct data.
** Affects: snappy
Importance: Undecided
Status: New
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1650207
Title:
original lsb-release file should be preserved for classic mode
Status in Snappy:
New
Status in livecd-rootfs package in Ubuntu:
New
Bug description:
when installing the classic snap the modified /etc/lsb-release and
/etc/os-release are used inside the tarball. when compiling code that
uses the content of these files at build time they get the wrong info:
DISTRIB_ID="Ubuntu Core"
DISTRIB_RELEASE=16
DISTRIB_DESCRIPTION="Ubuntu Core 16"
vs:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
we should preserve the original data for these two files and use it
inside the classic container when the classic snap is installed, so
build environments can match against the correct data.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1650207/+subscriptions
More information about the foundations-bugs
mailing list