Commit 485e2f18 authored by Santiago Vila's avatar Santiago Vila Committed by Jonas Smedegaard
Browse files

Import Debian version 9.8

base-files (9.8) unstable; urgency=medium

  * Release candidate for stretch as stable:
  - Use "9" as version in /etc/issue and /etc/issue.net.
    (never expected to change after stretch is released)
  - Use 9.0 as version in /etc/debian_version.
    (expected to change at every point release)
  - Change PRETTY_NAME in /usr/lib/os-release, adding 9 as version number
    and "(stretch)" as codename. Add also VERSION_ID and VERSION.
    (never expected to change)
  - Update README (stretch -> buster).
  * Standards-Version: 3.9.8 (no special changes for this).
parent 45cb33df
......@@ -4,10 +4,10 @@ Frequently Asked Questions about base-files
* Questions about /etc/issue and /etc/debian_version:
Q. I upgraded my system to the testing distribution and now my /etc/issue
says "stretch/sid". Should it not read "stretch" or "testing"?
says "buster/sid". Should it not read "buster" or "testing"?
Q. I upgraded my system to the unstable distribution and now my /etc/issue
says "stretch/sid". Should it not read "sid" or "unstable"?
says "buster/sid". Should it not read "sid" or "unstable"?
A. That would be nice, but it is not possible because of the way the
testing distribution works. Packages uploaded for unstable reach
......@@ -17,9 +17,9 @@ testing. You should consider the testing and unstable distributions as
two sides of the same coin. Since the base-files package in testing
was initially uploaded for unstable, the only sensible /etc/issue to
have is one that is both valid for testing and unstable, hence
"stretch/sid" (or whatever is appropriate).
"buster/sid" (or whatever is appropriate).
Q. Why "stretch/sid" and not "testing/unstable" as it used to be?
Q. Why "buster/sid" and not "testing/unstable" as it used to be?
A. The codename is a little bit more informative, as the meaning of
"testing" changes over time.
......
base-files (9.8) unstable; urgency=medium
* Release candidate for stretch as stable:
- Use "9" as version in /etc/issue and /etc/issue.net.
(never expected to change after stretch is released)
- Use 9.0 as version in /etc/debian_version.
(expected to change at every point release)
- Change PRETTY_NAME in /usr/lib/os-release, adding 9 as version number
and "(stretch)" as codename. Add also VERSION_ID and VERSION.
(never expected to change)
- Update README (stretch -> buster).
* Standards-Version: 3.9.8 (no special changes for this).
-- Santiago Vila <sanvila@debian.org> Sun, 15 Jan 2017 23:00:02 +0100
base-files (9.7) unstable; urgency=medium
* Do not care about /etc/nsswitch.conf anymore, as the file has been
......
......@@ -2,7 +2,7 @@ Source: base-files
Section: admin
Priority: required
Maintainer: Santiago Vila <sanvila@debian.org>
Standards-Version: 3.9.7
Standards-Version: 3.9.8
Build-Depends: debhelper (>= 9)
Package: base-files
......
Debian #OSNAME# stretch/sid \n \l
Debian #OSNAME# 9 \n \l
Debian #OSNAME# stretch/sid
Debian #OSNAME# 9
PRETTY_NAME="Debian #OSNAME# stretch/sid"
PRETTY_NAME="Debian #OSNAME# 9 (stretch)"
NAME="Debian #OSNAME#"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment