Commit 162994a4 authored by Jonathan Carter's avatar Jonathan Carter
Browse files

Update base-files

parent 346fc5bd
dh_update_autotools_config
dh_auto_configure
dh_auto_build
dh_auto_test
dh_prep
dh_installdirs
dh_auto_install
dh_installdocs
dh_installchangelogs
dh_installman
dh_lintian
dh_perl
override_dh_link dh_link
dh_link
dh_strip_nondeterminism
override_dh_compress dh_compress
dh_compress
override_dh_fixperms dh_fixperms
dh_fixperms
dh_strip
dh_makeshlibs
dh_shlibdeps
dh_installdeb
dh_gencontrol
dh_md5sums
override_dh_builddeb dh_builddeb.pkgbinarymangler
override_dh_builddeb dh_builddeb.pkgbinarymangler
override_dh_builddeb dh_builddeb
dh_builddeb
/etc/debian_version
/etc/dpkg/origins/aims
/etc/dpkg/origins/debian
/etc/host.conf
/etc/issue
......
Package: base-files
Version: 2016.1
Version: 2018.01.1
Architecture: amd64
Essential: yes
Maintainer: Santiago Vila <sanvila@debian.org>
Installed-Size: 289
Installed-Size: 221
Pre-Depends: awk
Breaks: initscripts (<< 2.88dsf-13.3), sendfile (<< 2.1b.20080616-5.2~)
Replaces: base, dpkg (<= 1.15.0), miscutils
......
cfc6e8d37b8355d6c08a8036844c368e usr/lib/os-release
e12f5739f81b08c470f20890304bf53e usr/share/base-files/dot.bashrc
6a2016f81a78931dfc368a6761bc11ae usr/lib/os-release
b2c97d2d5d8f19ab3fedbd94d5ee3489 usr/share/base-files/dot.bashrc
46438b614dcb2175148fa7e0bdc604a4 usr/share/base-files/dot.profile
6db82730e03aaeeecb8fee76b73d96d4 usr/share/base-files/dot.profile.md5sums
f9128f409878ce10d54d06488e3ce136 usr/share/base-files/info.dir
9830e3dbb6a828f2cc824db8db0ceaf7 usr/share/base-files/motd
77bcf5ed9ab1a0e17fb56ad2bba7de7e usr/share/base-files/motd
f8e97bf611374634c7cb3a6085503ab5 usr/share/base-files/nsswitch.conf
79b7eaf9a6f42351a5b61ca2b9c0a79e usr/share/base-files/nsswitch.conf.md5sums
2255054e61cee1a99dbe893377820dde usr/share/base-files/profile
......@@ -20,8 +20,3 @@ d32239bcb673463ab874e80d47fae504 usr/share/common-licenses/GPL-3
5f30f0716dfdd0d91eb439ebec522ec2 usr/share/common-licenses/LGPL-2
4fbd65380cdd255951079008b364516c usr/share/common-licenses/LGPL-2.1
e6a600fd5e1d9cbde2d983680233ad02 usr/share/common-licenses/LGPL-3
4e6d5278ce754ce7b82a80e4339d7503 usr/share/doc/base-files/README
fbd937e067f0a83fb9422713a6b84a8a usr/share/doc/base-files/README.FHS
6439abe741cb0adc2a2a55b939de16d9 usr/share/doc/base-files/changelog.gz
c686090b1ff44554e2d6c541280a55b1 usr/share/doc/base-files/copyright
07223424da25c119e376b74f04a1cb2b usr/share/lintian/overrides/base-files
AIMS Desktop 2017.1 (Debian 9.0)
AIMS Desktop 2018.1 (Debian 9.4)
AIMS Desktop 2017.1 (Debian 9.0)
AIMS Desktop 2018.1 (Debian 9.4)
PRETTY_NAME="AIMS Desktop 2017.1"
PRETTY_NAME="AIMS Desktop 2018.1"
NAME="AIMS Dekstop GNU/Linux"
ID=debian
ID=aims
HOME_URL="https://help.aims.ac.za/"
SUPPORT_URL="https://help.aims.ac.za"
BUG_REPORT_URL="https://help.aims.ac.za/"
......@@ -6,13 +6,19 @@
# umask 022
# You may uncomment the following lines if you want `ls' to be colorized:
# export LS_OPTIONS='--color=auto'
# eval "`dircolors`"
# alias ls='ls $LS_OPTIONS'
# alias ll='ls $LS_OPTIONS -l'
# alias l='ls $LS_OPTIONS -lA'
#
export LS_OPTIONS='--color=auto'
eval "`dircolors`"
alias ls='ls $LS_OPTIONS'
alias ll='ls $LS_OPTIONS -l'
alias l='ls $LS_OPTIONS -lA'
# Some more alias to avoid making mistakes:
# alias rm='rm -i'
# alias cp='cp -i'
# alias mv='mv -i'
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
# This is needed if you use the terminix shell
# See https://github.com/gnunn1/terminix/wiki/VTE-Configuration-Issue
if [[ $TERMINIX_ID ]]; then
source /etc/profile.d/vte-2.91.sh
fi
The programs included with the Debian GNU/Linux system are free software;
The programs included with the AIMS Desktop system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
AIMS Desktop is based on Debian, for more information, see:
http://debian.org
This software comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
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"?
Q. I upgraded my system to the unstable distribution and now my /etc/issue
says "stretch/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
testing after ten days, provided they are built for every released
architecture, have no RC-bugs and their dependencies may be met in
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).
Q. Why "stretch/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.
Q. Ok, but how do I know which distribution I'm running?
A. If you are running testing or unstable, then /etc/debian_version is
not a reliable way to know that anymore. Looking at the contents of
your /etc/apt/sources.list file is probably a much better way.
Q. There is a new point release and I've just upgraded my system.
The /etc/debian_version file now says 8.x but /etc/issue still says 8.
Is this ok?
A. Yes. The release managers asked me not to touch /etc/issue, as that's
a file which is often customized by the user. The /etc/debian_version file,
on the other side, is updated at every point release, so that the exact
Debian version is shown when used by tools like reportbug.
* Other questions:
Q. After upgrading my system recently, I noticed that some files from
base-files do not match the ones which are installed on a fresh install
of squeeze. Should I not be warned about that?
A. Those files are configuration files, so they are completely under
the control of the system admin. The files installed by base-files are
just defaults. Changes in the default files are not important enough
to warn the user, as it is also policy that prompting should be
reduced to a minimum. This is also the reason they are not handled via
dpkg's conffile mechanism.
In either case, if you want to "upgrade" those files, just look at the
postinst for base-files (i.e. /var/lib/dpkg/info/base-files.postinst)
and you will see how they are created and where their master copies are:
install_from_default /usr/share/base-files/nsswitch.conf /etc/nsswitch.conf
install_from_default /usr/share/base-files/dot.profile /root/.profile
install_from_default /usr/share/base-files/dot.bashrc /root/.bashrc
install_from_default /usr/share/base-files/profile /etc/profile
install_from_default /usr/share/base-files/motd /etc/motd
So, if you want your system to be as similar as possible to a newly
installed squeeze system, you might want to sync these files manually.
Note 1: Since base-files version 6.10, /etc/profile is automatically
upgraded if it has not been modified from a previous default.
Note 2: The file /etc/nsswitch.conf is going to be moved to libc-bin.
Q. Why isn't license "foo" included in common-licenses?
A. I delegate such decisions to the policy group. If you want to
propose a new license you should make a policy proposal to modify the
paragraph in policy saying "Packages distributed under the Apache
license (version 2.0), the Artistic license, the GNU GPL (versions 1,
2, or 3), the GNU LGPL (versions 2, 2.1, or 3), and the GNU FDL
(versions 1.2 or 1.3) should refer to the corresponding files under
/usr/share/common-licenses". The way of doing this is explained in the
debian-policy package. As usual, you should always take a look at
already reported bugs against debian-policy before submitting a new
one.
Q. I upgraded from woody to sarge. Should my system be FHS-compliant now?
A. Achieving FHS compliance by upgrading would be tricky and prone to
error in certain cases, so it is not a goal of base-files, nor it is
planned to be. By default, some "mandatory" directories (like /opt,
/srv or /media) are only created in the first install (performed by
debootstrap), to keep the code as simple as possible, follow the
principle of least surprise on upgrades, and also to give people the
freedom to remove those directories without them being created again
when base-files is upgraded. Therefore, if you are running any sort of
compliance tests, you should do it on newly installed systems only.
Santiago Vila <sanvila@debian.org>
The FHS standard specifies /var/mail as the mail spool, but it also says
/var/mail may be a symbolic link to another directory, and there is no
requirement to physically move the mail spool to this location.
Therefore, no package will move files around from one location to another
on upgrades, and /var/mail will be the real directory only in newly
installed systems.
Since /var/spool/mail has been in use for several years now, we need
also to provide backwards compatibility for some time yet.
So, to summarize:
* New systems (Debian 2.2 or later) will have /var/mail as a real
directory and /var/spool/mail as a symlink to it.
* Upgraded systems will have /var/spool/mail as the real directory
and /var/mail as a symlink to it.
People upgrading from previous releases who prefer the new physical
location /var/mail over the old one may do the required changes in their
systems if they do it with extreme care and know what they are doing. The
packages in charge of ensuring that /var/mail exists (currently, libc6 and
base-files) will not touch it at all if it already exists as a directory
or a symlink.
Santiago Vila <sanvila@debian.org>
This is the Debian GNU/Linux prepackaged version of the Debian Base System
Miscellaneous files. These files were written by Ian Murdock
<imurdock@debian.org> and Bruce Perens <bruce@pixar.com>.
This package was first put together by Bruce Perens <Bruce@Pixar.com>,
from his own sources.
The GNU Public Licenses in /usr/share/common-licenses were taken from
ftp.gnu.org and are copyrighted by the Free Software Foundation, Inc.
The Artistic License in /usr/share/common-licenses is the one coming
from Perl and its SPDX name is "Artistic License 1.0 (Perl)".
Copyright (C) 1995-2011 Software in the Public Interest.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
On Debian GNU/Linux systems, the complete text of the GNU General
Public License can be found in `/usr/share/common-licenses/GPL'.
#
# Permissions 0700 on /root are intentional as people expect
# the /root directory to be more private than /home/* directories.
#
base-files: non-standard-dir-perm root/ 0700 != 0755
#
# The /etc/os-release symlink is relative on purpose to avoid breaking dracut.
# See Bug #755394 for details.
#
base-files: symlink-should-be-absolute etc/os-release ../usr/lib/os-release
#
# The purpose of having licenses here is precisely to allow
# other packages to reference them.
#
base-files: extra-license-file usr/share/common-licenses/Artistic
base-files: extra-license-file usr/share/common-licenses/BSD
base-files: extra-license-file usr/share/common-licenses/GPL-1
base-files: extra-license-file usr/share/common-licenses/GPL-2
base-files: extra-license-file usr/share/common-licenses/GPL-3
base-files: extra-license-file usr/share/common-licenses/LGPL-2
base-files: extra-license-file usr/share/common-licenses/LGPL-2.1
base-files: extra-license-file usr/share/common-licenses/LGPL-3
Supports Markdown
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