Bug#940312: /etc/issue: /etc/issue is being updated by Debian when it doesn't need to
El 10/7/23 a las 17:57, Ben Wong escribió: Thanks for the tip! I will look into ansible. I had thought it was for large organizations, but if it is what Debian recommends for upgrades, then I am happy to learn it. Ok, just to clarify: ansible was only one of many options available, and also I'm not speaking on behalf of Debian, only based on my personal experience. For upgrading without dpkg questions, you might want to try the "unattended-upgrades" package first, which is quite popular. The reason I suggested ansible is because I have used it in the past to upgrade some servers in my last job, from oldstable to stable, and it worked well enough, but in my case I wanted to do extra steps after the upgrade and ansible was well suited for that. Thanks.
Bug#940312: /etc/issue: /etc/issue is being updated by Debian when it doesn't need to
Oh! I'm sorry. I had expected Debian's official "PRETTY NAME" in
/etc/os-release to be the preferred name for showing to users.
To show it without the code name, but to have it automatically update
whenever /etc/os-release is changed, this works:
\S{NAME} \S{VERSION_ID} \n \l
Thanks,
—Ben
Bug#940312: /etc/issue: /etc/issue is being updated by Debian when it doesn't need to
On Thu, Nov 21, 2019 at 11:22:00AM -0800, Ben Wong wrote: > Hi, I know this is low-priority and everyone is busy on important matters, > but I was wondering if anybody had looked at this yet. The fix I included > is simple and easily verified. I'm hoping that it can be included in Debian > 11 (Bullseye). The suggested change would make /etc/issue to show "buster" in Debian 10. However, Debian has never included the codename in /etc/issue in stable releases. Therefore, we can't just apply the suggested change. Thanks.
Bug#940312: /etc/issue: /etc/issue is being updated by Debian when it doesn't need to
Hi, I know this is low-priority and everyone is busy on important matters, but I was wondering if anybody had looked at this yet. The fix I included is simple and easily verified. I'm hoping that it can be included in Debian 11 (Bullseye). Thanks, —Ben
Bug#940312: /etc/issue: /etc/issue is being updated by Debian when it doesn't need to
Package: base-files
Version: 10.3+deb10u1
Severity: normal
File: /etc/issue
Tags: patch
Dear Maintainer,
When upgrading to Debian Buster, I noticed that Debian had updated
/etc/issue to include the version number ("Debian GNU/Linux 10").
There is no reason for this since that data is already included in
/etc/os-release.
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;
Here is a version of /etc/issue which will show the "PRETTY_NAME":
\S \n \l
Please use that instead of hardcoding it to a specific release. That
way, those of us who like to customize our /etc/issue won't get
conflict errors next time we upgrade.
Thank you.
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages base-files depends on:
ii gawk [awk] 1:4.1.4+dfsg-1
ii mawk [awk] 1.3.3-17+b3
base-files recommends no packages.
base-files suggests no packages.
-- Configuration Files:
/etc/issue changed:
\S (\r)
Welcome to \n.\O \l@\b \t
-- no debconf information
--- issue.dpkg-dist 2019-08-30 05:31:26.0 -0700
+++ issue 2019-09-15 05:47:19.463694363 -0700
@@ -1,2 +1,2 @@
-Debian GNU/Linux 10 \n \l
+\S \n \l
