Vcs-Git: git://anonscm.debian.org/collab-maint/lsb.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/lsb.git
+Package: lsb-core
+Architecture: any
+Depends: lsb-release (>= ${source:Version}),
+ ${glibc},
+ libz1,
+ libncurses5,
+ libpam0g,
+ lsb-invalid-mta (>= ${source:Version}) | mail-transport-agent,
+ at,
+ bc,
+ binutils,
+ bsdmainutils,
+ bsdutils,
+ cpio,
+ cron | cron-daemon,
+ ed,
+ file,
+ libc6-dev | libc-dev,
+ locales,
+ cups-bsd | lpr,
+ lprng | cups-client,
+ m4,
+ mailutils | mailx,
+ make,
+ man-db,
+ mawk | gawk,
+ ncurses-term,
+ passwd,
+ patch,
+ pax,
+ procps,
+ psmisc,
+ rsync,
+ alien (>= 8.36),
+ ${python3:Depends},
+ ${misc:Depends},
+ ${depends},
+ lsb-base (>= ${source:Version}),
+ lsb-security (>= ${source:Version}),
+ time
+Provides: lsb-core-noarch, ${provides}
+Description: Linux Standard Base 4.1 core support package
+ The Linux Standard Base (http://www.linuxbase.org/) is a standard
+ core system that third-party applications written for Linux can
+ depend upon.
+ .
+ This package provides an implementation of the core of version 4.1 of
+ the Linux Standard Base for Debian on the Intel x86, Intel ia64
+ (Itanium), IBM S390, and PowerPC 32-bit architectures with the Linux
+ kernel. Future revisions of the specification and this package may
+ support the LSB on additional architectures and kernels.
+ .
+ The intent of this package is to provide a best current practice way
+ of installing and running LSB packages on Debian GNU/Linux. Its
+ presence does not imply that Debian fully complies
+ with the Linux Standard Base, and should not be construed as a
+ statement that Debian is LSB-compliant.
+
Package: lsb-base
Architecture: all
Multi-Arch: foreign
--- /dev/null
+#!/bin/sh
+
+set -e
+
+. /usr/share/debconf/confmodule
+
+if [ ! -e /etc/shadow ]; then
+ db_input medium lsb/shadowconfig || true
+fi
+db_go
+
+#DEBHELPER#
--- /dev/null
+usr/lib/lsb
+var/lib/lsb
+etc/profile.d
--- /dev/null
+test/init-skeleton
--- /dev/null
+initdutils.py /usr/lib/lsb
+install_initd /usr/lib/lsb
+remove_initd /usr/lib/lsb
+lsbinstall /usr/lib/lsb
--- /dev/null
+# The purpose of LSB is to ensure that those packages are present. Being explicit cannot hurt.
+depends-on-essential-package-without-using-version depends: bsdutils
--- /dev/null
+#!/bin/sh
+
+set -e
+
+setup_ldso_symlink () {
+ ARCH=$DPKG_MAINTSCRIPT_ARCH
+ if [ -z "$ARCH" ]; then
+ ARCH=$(dpkg --print-architecture)
+ fi
+ case "$ARCH" in
+ s390|ppc64|sparc|sparc64|alpha|hppa|m68k|mipsel)
+ ln -sf ld.so.1 /lib/ld-lsb-$ARCH.so.1
+ ln -sf ld.so.1 /lib/ld-lsb-$ARCH.so.2
+ ln -sf ld.so.1 /lib/ld-lsb-$ARCH.so.3
+ ;;
+ powerpc)
+ ln -sf ld.so.1 /lib/ld-lsb-ppc32.so.1
+ ln -sf ld.so.1 /lib/ld-lsb-ppc32.so.2
+ ln -sf ld.so.1 /lib/ld-lsb-ppc32.so.3
+ ;;
+ i386)
+ ln -sf ld-linux.so.2 /lib/ld-lsb.so.1
+ ln -sf ld-linux.so.2 /lib/ld-lsb.so.2
+ ln -sf ld-linux.so.2 /lib/ld-lsb.so.3
+ ;;
+ amd64)
+ ln -sf ld-linux.so.2 /lib/ld-lsb.so.1
+ ln -sf ld-linux.so.2 /lib/ld-lsb.so.2
+ ln -sf ld-linux.so.2 /lib/ld-lsb.so.3
+ ln -sf ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.2
+ ln -sf ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3
+ ;;
+ ia64)
+ ln -sf ld-linux-ia64.so.2 /lib/ld-lsb-ia64.so.1
+ ln -sf ld-linux-ia64.so.2 /lib/ld-lsb-ia64.so.2
+ ln -sf ld-linux-ia64.so.2 /lib/ld-lsb-ia64.so.3
+ ;;
+ *)
+ echo "ld-lsb-*.so.1 symlink for $ARCH is unknown!"
+ ;;
+ esac
+}
+
+PATH=/sbin:/usr/sbin:$PATH
+export PATH
+
+. /usr/share/debconf/confmodule
+
+case "$1" in
+ configure)
+ if [ ! -e /etc/shadow ]; then
+ db_get lsb/shadowconfig
+ if [ "$RET" = "true" ]; then
+ shadowconfig on >&2 || true
+ fi
+ fi
+ if dpkg --compare-versions "$2" lt "3.2+Debian30" ; then
+ [ -L /lib/ld-lsb-x86-64.so.2 ] && rm /lib/ld-lsb-x86-64.so.2 || true
+ [ -L /lib/ld-lsb-x86-64.so.3 ] && rm /lib/ld-lsb-x86-64.so.3 || true
+ fi
+ setup_ldso_symlink
+ ;;
+ abort-upgrade|abort-remove|abort-deconfigure)
+ ;;
+ *)
+ echo "postinst called with unknown argument \`$1'" >&2
+ exit 1
+ ;;
+esac
+
+#DEBHELPER#
--- /dev/null
+#!/bin/sh
+
+set -e
+
+remove_ldso_symlink () {
+ ARCH=$DPKG_MAINTSCRIPT_ARCH
+ if [ -z "$ARCH" ]; then
+ ARCH=$(dpkg --print-architecture)
+ fi
+ case "$ARCH" in
+ s390|ia64|ppc64|sparc|sparc64|alpha|hppa|m68k|mipsel)
+ rm -f /lib/ld-lsb-$ARCH.so.[123]
+ ;;
+ powerpc)
+ rm -f /lib/ld-lsb-ppc32.so.[123]
+ ;;
+ i386)
+ rm -f /lib/ld-lsb.so.[123]
+ ;;
+ amd64)
+ rm -f /lib/ld-lsb.so.[123] /lib64/ld-lsb-x86-64.so.[23]
+ ;;
+ *)
+ echo "ld-lsb-*.so.1 symlink for $ARCH is unknown; not removed."
+ ;;
+ esac
+}
+
+PATH=/sbin:/usr/sbin:$PATH
+export PATH
+
+case "$1" in
+ remove)
+ remove_ldso_symlink
+ rm -f /var/lib/lsb/facilities
+ rm -f /var/lib/lsb/depends
+ ;;
+ failed-upgrade|upgrade|deconfigure)
+ ;;
+ *)
+ echo "prerm called with unknown argument \`$1'" >&2
+ exit 1
+ ;;
+esac
+
+
+#DEBHELPER#
--- /dev/null
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# for an advice to debian-l10n-english@lists.debian.org
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
+Template: lsb/shadowconfig
+Type: boolean
+Default: true
+_Description: Enable shadow passwords?
+ The Linux Standard Base requires that certain features of adduser(8)
+ be available to conforming applications (such as password
+ aging). These features are only provided when shadow passwords are
+ enabled, while this system has them disabled.
+ .
+ Most LSB applications will work fine with either setting, but complete
+ conformance requires shadow passwords to be enabled.
+ .
+ Generally speaking, it is considered good practice to enable shadow
+ passwords. However, there are some situations in which shadow passwords
+ may not work properly (most notably, if non-root users need to
+ check passwords against /etc/passwd).
projects / lsb.git / commitdiff