ubuntu-policy/0000755000175000017500000000000011216714641014142 5ustar cjwatsoncjwatsonubuntu-policy/ubuntu-perl-policy.desc0000644000175000017500000000116411061226146020557 0ustar cjwatsoncjwatsonDocument: ubuntu-perl-policy Title: Ubuntu Perl Policy Manual Author: The Debian Policy Mailing list Abstract: This manual describes the policy requirements for the Perl system in the Ubuntu distribution, describing the rules regulating the building and installation of packages providing and using Perl and Perl modules. Section: Ubuntu Format: debiandoc-sgml Files: /usr/share/doc/ubuntu-policy/perl-policy.sgml.gz Format: text Files: /usr/share/doc/ubuntu-policy/perl-policy.txt.gz Format: HTML Index: /usr/share/doc/ubuntu-policy/perl-policy.html/index.html Files: /usr/share/doc/ubuntu-policy/perl-policy.html/*.html ubuntu-policy/fhs-2.3.html0000644000175000017500000054630711054263224016123 0ustar cjwatsoncjwatson Filesystem Hierarchy Standard

Filesystem Hierarchy Standard

Filesystem Hierarchy Standard Group

Edited by

Rusty Russell

Daniel Quinlan

Christopher Yeoh

Copyright © 1994-2004 Daniel Quinlan

Copyright © 2001-2004 Paul 'Rusty' Russell

Copyright © 2003-2004 Christopher Yeoh

This standard consists of a set of requirements and guidelines for file and directory placement under UNIX-like operating systems. The guidelines are intended to support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems.

All trademarks and copyrights are owned by their owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark.

Permission is granted to make and distribute verbatim copies of this standard provided the copyright and this permission notice are preserved on all copies.

Permission is granted to copy and distribute modified versions of this standard under the conditions for verbatim copying, provided also that the title page is labeled as modified including a reference to the original standard, provided that information on retrieving the original standard is included, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.

Permission is granted to copy and distribute translations of this standard into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the copyright holder.

Table of Contents
1. Introduction
Purpose
Conventions
2. The Filesystem
3. The Root Filesystem
Purpose
Requirements
Specific Options
/bin : Essential user command binaries (for use by all users)
Purpose
Requirements
Specific Options
/boot : Static files of the boot loader
Purpose
Specific Options
/dev : Device files
Purpose
Specific Options
/etc : Host-specific system configuration
Purpose
Requirements
Specific Options
/etc/opt : Configuration files for /opt
/etc/X11 : Configuration for the X Window System (optional)
/etc/sgml : Configuration files for SGML (optional)
/etc/xml : Configuration files for XML (optional)
/home : User home directories (optional)
Purpose
Requirements
/lib : Essential shared libraries and kernel modules
Purpose
Requirements
Specific Options
/lib<qual> : Alternate format essential shared libraries (optional)
Purpose
Requirements
/media : Mount point for removeable media
Purpose
Specific Options
/mnt : Mount point for a temporarily mounted filesystem
Purpose
/opt : Add-on application software packages
Purpose
Requirements
/root : Home directory for the root user (optional)
Purpose
/sbin : System binaries
Purpose
Requirements
Specific Options
/srv : Data for services provided by this system
Purpose
/tmp : Temporary files
Purpose
4. The /usr Hierarchy
Purpose
Requirements
Specific Options
/usr/X11R6 : X Window System, Version 11 Release 6 (optional)
Purpose
Specific Options
/usr/bin : Most user commands
Purpose
Specific Options
/usr/include : Directory for standard include files.
Purpose
Specific Options
/usr/lib : Libraries for programming and packages
Purpose
Specific Options
/usr/lib<qual> : Alternate format libraries (optional)
Purpose
/usr/local : Local hierarchy
/usr/local/share
/usr/sbin : Non-essential standard system binaries
Purpose
/usr/share : Architecture-independent data
Purpose
Requirements
Specific Options
/usr/share/dict : Word lists (optional)
/usr/share/man : Manual pages
/usr/share/misc : Miscellaneous architecture-independent data
/usr/share/sgml : SGML data (optional)
/usr/share/xml : XML data (optional)
/usr/src : Source code (optional)
Purpose
5. The /var Hierarchy
Purpose
Requirements
Specific Options
/var/account : Process accounting logs (optional)
Purpose
/var/cache : Application cache data
Purpose
Specific Options
/var/cache/fonts : Locally-generated fonts (optional)
/var/cache/man : Locally-formatted manual pages (optional)
/var/crash : System crash dumps (optional)
Purpose
/var/games : Variable game data (optional)
Purpose
/var/lib : Variable state information
Purpose
Requirements
Specific Options
/var/lib/<editor> : Editor backup files and state (optional)
/var/lib/hwclock : State directory for hwclock (optional)
/var/lib/misc : Miscellaneous variable data
/var/lock : Lock files
Purpose
/var/log : Log files and directories
Purpose
Specific Options
/var/mail : User mailbox files (optional)
Purpose
/var/opt : Variable data for /opt
Purpose
/var/run : Run-time variable data
Purpose
Requirements
/var/spool : Application spool data
Purpose
Specific Options
/var/spool/lpd : Line-printer daemon print queues (optional)
/var/spool/rwho : Rwhod files (optional)
/var/tmp : Temporary files preserved between system reboots
Purpose
/var/yp : Network Information Service (NIS) database files (optional)
Purpose
6. Operating System Specific Annex
Linux
/ : Root directory
/bin : Essential user command binaries (for use by all users)
/dev : Devices and special files
/etc : Host-specific system configuration
/lib64 and /lib32 : 64/32-bit libraries (architecture dependent)
/proc : Kernel and process information virtual filesystem
/sbin : Essential system binaries
/usr/include : Header files included by C programs
/usr/src : Source code
/var/spool/cron : cron and at jobs
7. Appendix
The FHS mailing list
Background of the FHS
General Guidelines
Scope
Acknowledgments
Contributors

Chapter 1. Introduction

Purpose

This standard enables:

  • Software to predict the location of installed files and directories, and

  • Users to predict the location of installed files and directories.

We do this by:

  • Specifying guiding principles for each area of the filesystem,

  • Specifying the minimum files and directories required,

  • Enumerating exceptions to the principles, and

  • Enumerating specific cases where there has been historical conflict.

The FHS document is used by:

  • Independent software suppliers to create applications which are FHS compliant, and work with distributions which are FHS complaint,

  • OS creators to provide systems which are FHS compliant, and

  • Users to understand and maintain the FHS compliance of a system.

The FHS document has a limited scope:

  • Local placement of local files is a local issue, so FHS does not attempt to usurp system administrators.

  • FHS addresses issues where file placements need to be coordinated between multiple parties such as local sites, distributions, applications, documentation, etc.

Conventions

We recommend that you read a typeset version of this document rather than the plain text version. In the typeset version, the names of files and directories are displayed in a constant-width font.

Components of filenames that vary are represented by a description of the contents enclosed in "<" and ">" characters, <thus>. Electronic mail addresses are also enclosed in "<" and ">" but are shown in the usual typeface.

Optional components of filenames are enclosed in "[" and "]" characters and may be combined with the "<" and ">" convention. For example, if a filename is allowed to occur either with or without an extension, it might be represented by <filename>[.<extension>].

Variable substrings of directory names and filenames are indicated by "*".

The sections of the text marked as Rationale are explanatory and are non-normative.

Chapter 2. The Filesystem

This standard assumes that the operating system underlying an FHS-compliant file system supports the same basic security features found in most UNIX filesystems.

It is possible to define two independent distinctions among files: shareable vs. unshareable and variable vs. static. In general, files that differ in either of these respects should be located in different directories. This makes it easy to store files with different usage characteristics on different filesystems.

"Shareable" files are those that can be stored on one host and used on others. "Unshareable" files are those that are not shareable. For example, the files in user home directories are shareable whereas device lock files are not.

"Static" files include binaries, libraries, documentation files and other files that do not change without system administrator intervention. "Variable" files are files that are not static.

TipRationale
 

Shareable files can be stored on one host and used on several others. Typically, however, not all files in the filesystem hierarchy are shareable and so each system has local storage containing at least its unshareable files. It is convenient if all the files a system requires that are stored on a foreign host can be made available by mounting one or a few directories from the foreign host.

Static and variable files should be segregated because static files, unlike variable files, can be stored on read-only media and do not need to be backed up on the same schedule as variable files.

Historical UNIX-like filesystem hierarchies contained both static and variable files under both /usr and /etc. In order to realize the advantages mentioned above, the /var hierarchy was created and all variable files were transferred from /usr to /var. Consequently /usr can now be mounted read-only (if it is a separate filesystem). Variable files have been transferred from /etc to /var over a longer period as technology has permitted.

Here is an example of a FHS-compliant system. (Other FHS-compliant layouts are possible.)

shareableunshareable
static/usr/etc
 /opt/boot
variable/var/mail/var/run
 /var/spool/news/var/lock

Chapter 3. The Root Filesystem

Purpose

The contents of the root filesystem must be adequate to boot, restore, recover, and/or repair the system.

  • To boot a system, enough must be present on the root partition to mount other filesystems. This includes utilities, configuration, boot loader information, and other essential start-up data. /usr, /opt, and /var are designed such that they may be located on other partitions or filesystems.

  • To enable recovery and/or repair of a system, those utilities needed by an experienced maintainer to diagnose and reconstruct a damaged system must be present on the root filesystem.

  • To restore a system, those utilities needed to restore from system backups (on floppy, tape, etc.) must be present on the root filesystem.

TipRationale
 

The primary concern used to balance these considerations, which favor placing many things on the root filesystem, is the goal of keeping root as small as reasonably possible. For several reasons, it is desirable to keep the root filesystem small:

  • It is occasionally mounted from very small media.

  • The root filesystem contains many system-specific configuration files. Possible examples include a kernel that is specific to the system, a specific hostname, etc. This means that the root filesystem isn't always shareable between networked systems. Keeping it small on servers in networked systems minimizes the amount of lost space for areas of unshareable files. It also allows workstations with smaller local hard drives.

  • While you may have the root filesystem on a large partition, and may be able to fill it to your heart's content, there will be people with smaller partitions. If you have more files installed, you may find incompatibilities with other systems using root filesystems on smaller partitions. If you are a developer then you may be turning your assumption into a problem for a large number of users.

  • Disk errors that corrupt data on the root filesystem are a greater problem than errors on any other partition. A small root filesystem is less prone to corruption as the result of a system crash.

Applications must never create or require special files or subdirectories in the root directory. Other locations in the FHS hierarchy provide more than enough flexibility for any package.

TipRationale
 

There are several reasons why creating a new subdirectory of the root filesystem is prohibited:

  • It demands space on a root partition which the system administrator may want kept small and simple for either performance or security reasons.

  • It evades whatever discipline the system administrator may have set up for distributing standard file hierarchies across mountable volumes.

Distributions should not create new directories in the root hierarchy without extremely careful consideration of the consequences including for application portability.

Requirements

The following directories, or symbolic links to directories, are required in /.

DirectoryDescription
binEssential command binaries
bootStatic files of the boot loader
devDevice files
etcHost-specific system configuration
libEssential shared libraries and kernel modules
mediaMount point for removeable media
mntMount point for mounting a filesystem temporarily
optAdd-on application software packages
sbinEssential system binaries
srvData for services provided by this system
tmpTemporary files
usrSecondary hierarchy
varVariable data

Each directory listed above is specified in detail in separate subsections below. /usr and /var each have a complete section in this document due to the complexity of those directories.

Specific Options

The following directories, or symbolic links to directories, must be in /, if the corresponding subsystem is installed:

DirectoryDescription
homeUser home directories (optional)
lib<qual>Alternate format essential shared libraries (optional)
rootHome directory for the root user (optional)

Each directory listed above is specified in detail in separate subsections below.

/bin : Essential user command binaries (for use by all users)

Purpose

/bin contains commands that may be used by both the system administrator and by users, but which are required when no other filesystems are mounted (e.g. in single user mode). It may also contain commands which are used indirectly by scripts. [1]

Requirements

There must be no subdirectories in /bin.

The following commands, or symbolic links to commands, are required in /bin.

CommandDescription
catUtility to concatenate files to standard output
chgrpUtility to change file group ownership
chmodUtility to change file access permissions
chownUtility to change file owner and group
cpUtility to copy files and directories
dateUtility to print or set the system data and time
ddUtility to convert and copy a file
dfUtility to report filesystem disk space usage
dmesgUtility to print or control the kernel message buffer
echoUtility to display a line of text
falseUtility to do nothing, unsuccessfully
hostnameUtility to show or set the system's host name
killUtility to send signals to processes
lnUtility to make links between files
loginUtility to begin a session on the system
lsUtility to list directory contents
mkdirUtility to make directories
mknodUtility to make block or character special files
moreUtility to page through text
mountUtility to mount a filesystem
mvUtility to move/rename files
psUtility to report process status
pwdUtility to print name of current working directory
rmUtility to remove files or directories
rmdirUtility to remove empty directories
sedThe `sed' stream editor
shThe Bourne command shell
sttyUtility to change and print terminal line settings
suUtility to change user ID
syncUtility to flush filesystem buffers
trueUtility to do nothing, successfully
umountUtility to unmount file systems
unameUtility to print system information

If /bin/sh is not a true Bourne shell, it must be a hard or symbolic link to the real shell command.

The [ and test commands must be placed together in either /bin or /usr/bin.

TipRationale
 

For example bash behaves differently when called as sh or bash. The use of a symbolic link also allows users to easily see that /bin/sh is not a true Bourne shell.

The requirement for the [ and test commands to be included as binaries (even if implemented internally by the shell) is shared with the POSIX.2 standard.

Specific Options

The following programs, or symbolic links to programs, must be in /bin if the corresponding subsystem is installed:

CommandDescription
cshThe C shell (optional)
edThe `ed' editor (optional)
tarThe tar archiving utility (optional)
cpioThe cpio archiving utility (optional)
gzipThe GNU compression utility (optional)
gunzipThe GNU uncompression utility (optional)
zcatThe GNU uncompression utility (optional)
netstatThe network statistics utility (optional)
pingThe ICMP network test utility (optional)

If the gunzip and zcat programs exist, they must be symbolic or hard links to gzip. /bin/csh may be a symbolic link to /bin/tcsh or /usr/bin/tcsh.

TipRationale
 

The tar, gzip and cpio commands have been added to make restoration of a system possible (provided that / is intact).

Conversely, if no restoration from the root partition is ever expected, then these binaries might be omitted (e.g., a ROM chip root, mounting /usr through NFS). If restoration of a system is planned through the network, then ftp or tftp (along with everything necessary to get an ftp connection) must be available on the root partition.

/boot : Static files of the boot loader

Purpose

This directory contains everything required for the boot process except configuration files not needed at boot time and the map installer. Thus /boot stores data that is used before the kernel begins executing user-mode programs. This may include saved master boot sectors and sector map files. [2]

Specific Options

The operating system kernel must be located in either / or /boot. [3]

/dev : Device files

Purpose

The /dev directory is the location of special or device files.

Specific Options

If it is possible that devices in /dev will need to be manually created, /dev must contain a command named MAKEDEV, which can create devices as needed. It may also contain a MAKEDEV.local for any local devices.

If required, MAKEDEV must have provisions for creating any device that may be found on the system, not just those that a particular implementation installs.

/etc : Host-specific system configuration

Purpose

The /etc hierarchy contains configuration files. A "configuration file" is a local file used to control the operation of a program; it must be static and cannot be an executable binary. [4]

Requirements

No binaries may be located under /etc. [5]

The following directories, or symbolic links to directories are required in /etc:

DirectoryDescription
optConfiguration for /opt
X11Configuration for the X Window system (optional)
sgmlConfiguration for SGML (optional)
xmlConfiguration for XML (optional)

Specific Options

The following directories, or symbolic links to directories must be in /etc, if the corresponding subsystem is installed:

DirectoryDescription
optConfiguration for /opt

The following files, or symbolic links to files, must be in /etc if the corresponding subsystem is installed: [6]

FileDescription
csh.loginSystemwide initialization file for C shell logins (optional)
exportsNFS filesystem access control list (optional)
fstabStatic information about filesystems (optional)
ftpusersFTP daemon user access control list (optional)
gatewaysFile which lists gateways for routed (optional)
gettydefsSpeed and terminal settings used by getty (optional)
groupUser group file (optional)
host.confResolver configuration file (optional)
hostsStatic information about host names (optional)
hosts.allowHost access file for TCP wrappers (optional)
hosts.denyHost access file for TCP wrappers (optional)
hosts.equivList of trusted hosts for rlogin, rsh, rcp (optional)
hosts.lpdList of trusted hosts for lpd (optional)
inetd.confConfiguration file for inetd (optional)
inittabConfiguration file for init (optional)
issuePre-login message and identification file (optional)
ld.so.confList of extra directories to search for shared libraries (optional)
motdPost-login message of the day file (optional)
mtabDynamic information about filesystems (optional)
mtools.confConfiguration file for mtools (optional)
networksStatic information about network names (optional)
passwdThe password file (optional)
printcapThe lpd printer capability database (optional)
profileSystemwide initialization file for sh shell logins (optional)
protocolsIP protocol listing (optional)
resolv.confResolver configuration file (optional)
rpcRPC protocol listing (optional)
securettyTTY access control for root login (optional)
servicesPort names for network services (optional)
shellsPathnames of valid login shells (optional)
syslog.confConfiguration file for syslogd (optional)

mtab does not fit the static nature of /etc: it is excepted for historical reasons. [7]

/etc/opt : Configuration files for /opt

Purpose

Host-specific configuration files for add-on application software packages must be installed within the directory /etc/opt/<subdir>, where <subdir> is the name of the subtree in /opt where the static data from that package is stored.

Requirements

No structure is imposed on the internal arrangement of /etc/opt/<subdir>.

If a configuration file must reside in a different location in order for the package or system to function properly, it may be placed in a location other than /etc/opt/<subdir>.

TipRationale
 

Refer to the rationale for /opt.

/etc/X11 : Configuration for the X Window System (optional)

Purpose

/etc/X11 is the location for all X11 host-specific configuration. This directory is necessary to allow local control if /usr is mounted read only.

Specific Options

The following files, or symbolic links to files, must be in /etc/X11 if the corresponding subsystem is installed:

FileDescription
XconfigThe configuration file for early versions of XFree86 (optional)
XF86ConfigThe configuration file for XFree86 versions 3 and 4 (optional)
XmodmapGlobal X11 keyboard modification file (optional)

Subdirectories of /etc/X11 may include those for xdm and for any other programs (some window managers, for example) that need them. [8] We recommend that window managers with only one configuration file which is a default .*wmrc file must name it system.*wmrc (unless there is a widely-accepted alternative name) and not use a subdirectory. Any window manager subdirectories must be identically named to the actual window manager binary.

/etc/sgml : Configuration files for SGML (optional)

Purpose

Generic configuration files defining high-level parameters of the SGML systems are installed here. Files with names *.conf indicate generic configuration files. File with names *.cat are the DTD-specific centralized catalogs, containing references to all other catalogs needed to use the given DTD. The super catalog file catalog references all the centralized catalogs.

/etc/xml : Configuration files for XML (optional)

Purpose

Generic configuration files defining high-level parameters of the XML systems are installed here. Files with names *.conf indicate generic configuration files. The super catalog file catalog references all the centralized catalogs.

/home : User home directories (optional)

Purpose

/home is a fairly standard concept, but it is clearly a site-specific filesystem. [9] The setup will differ from host to host. Therefore, no program should rely on this location. [10]

Requirements

User specific configuration files for applications are stored in the user's home directory in a file that starts with the '.' character (a "dot file"). If an application needs to create more than one dot file then they should be placed in a subdirectory with a name starting with a '.' character, (a "dot directory"). In this case the configuration files should not start with the '.' character. [11]

/lib : Essential shared libraries and kernel modules

Purpose

The /lib directory contains those shared library images needed to boot the system and run the commands in the root filesystem, ie. by binaries in /bin and /sbin. [12]

Requirements

At least one of each of the following filename patterns are required (they may be files, or symbolic links):

FileDescription
libc.so.*The dynamically-linked C library (optional)
ld*The execution time linker/loader (optional)

If a C preprocessor is installed, /lib/cpp must be a reference to it, for historical reasons. [13]

Specific Options

The following directories, or symbolic links to directories, must be in /lib, if the corresponding subsystem is installed:

DirectoryDescription
modulesLoadable kernel modules (optional)

/lib<qual> : Alternate format essential shared libraries (optional)

Purpose

There may be one or more variants of the /lib directory on systems which support more than one binary format requiring separate libraries. [14]

Requirements

If one or more of these directories exist, the requirements for their contents are the same as the normal /lib directory, except that /lib<qual>/cpp is not required. [15]

/media : Mount point for removeable media

Purpose

This directory contains subdirectories which are used as mount points for removeable media such as floppy disks, cdroms and zip disks.

TipRationale
 

Historically there have been a number of other different places used to mount removeable media such as /cdrom, /mnt or /mnt/cdrom. Placing the mount points for all removeable media directly in the root directory would potentially result in a large number of extra directories in /. Although the use of subdirectories in /mnt as a mount point has recently been common, it conflicts with a much older tradition of using /mnt directly as a temporary mount point.

Specific Options

The following directories, or symbolic links to directories, must be in /media, if the corresponding subsystem is installed:

DirectoryDescription
floppyFloppy drive (optional)
cdromCD-ROM drive (optional)
cdrecorderCD writer (optional)
zipZip drive (optional)

On systems where more than one device exists for mounting a certain type of media, mount directories can be created by appending a digit to the name of those available above starting with '0', but the unqualified name must also exist. [16]

/mnt : Mount point for a temporarily mounted filesystem

Purpose

This directory is provided so that the system administrator may temporarily mount a filesystem as needed. The content of this directory is a local issue and should not affect the manner in which any program is run.

This directory must not be used by installation programs: a suitable temporary directory not in use by the system must be used instead.

/opt : Add-on application software packages

Purpose

/opt is reserved for the installation of add-on application software packages.

A package to be installed in /opt must locate its static files in a separate /opt/<package> or /opt/<provider> directory tree, where <package> is a name that describes the software package and <provider> is the provider's LANANA registered name.

Requirements

DirectoryDescription
<package>Static package objects
<provider>LANANA registered provider name

The directories /opt/bin, /opt/doc, /opt/include, /opt/info, /opt/lib, and /opt/man are reserved for local system administrator use. Packages may provide "front-end" files intended to be placed in (by linking or copying) these reserved directories by the local system administrator, but must function normally in the absence of these reserved directories.

Programs to be invoked by users must be located in the directory /opt/<package>/bin or under the /opt/<provider> hierarchy. If the package includes UNIX manual pages, they must be located in /opt/<package>/share/man or under the /opt/<provider> hierarchy, and the same substructure as /usr/share/man must be used.

Package files that are variable (change in normal operation) must be installed in /var/opt. See the section on /var/opt for more information.

Host-specific configuration files must be installed in /etc/opt. See the section on /etc for more information.

No other package files may exist outside the /opt, /var/opt, and /etc/opt hierarchies except for those package files that must reside in specific locations within the filesystem tree in order to function properly. For example, device lock files must be placed in /var/lock and devices must be located in /dev.

Distributions may install software in /opt, but must not modify or delete software installed by the local system administrator without the assent of the local system administrator.

TipRationale
 

The use of /opt for add-on software is a well-established practice in the UNIX community. The System V Application Binary Interface [AT&T 1990], based on the System V Interface Definition (Third Edition), provides for an /opt structure very similar to the one defined here.

The Intel Binary Compatibility Standard v. 2 (iBCS2) also provides a similar structure for /opt.

Generally, all data required to support a package on a system must be present within /opt/<package>, including files intended to be copied into /etc/opt/<package> and /var/opt/<package> as well as reserved directories in /opt.

The minor restrictions on distributions using /opt are necessary because conflicts are possible between distribution-installed and locally-installed software, especially in the case of fixed pathnames found in some binary software.

The structure of the directories below /opt/<provider> is left up to the packager of the software, though it is recommended that packages are installed in /opt/<provider>/<package> and follow a similar structure to the guidelines for /opt/package. A valid reason for diverging from this structure is for support packages which may have files installed in /opt/<provider>/lib or /opt/<provider>/bin.

/root : Home directory for the root user (optional)

Purpose

The root account's home directory may be determined by developer or local preference, but this is the recommended default location. [17]

/sbin : System binaries

Purpose

Utilities used for system administration (and other root-only commands) are stored in /sbin, /usr/sbin, and /usr/local/sbin. /sbin contains binaries essential for booting, restoring, recovering, and/or repairing the system in addition to the binaries in /bin. [18] Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. Locally-installed system administration programs should be placed into /usr/local/sbin. [19]

Requirements

The following commands, or symbolic links to commands, are required in /sbin.

CommandDescription
shutdownCommand to bring the system down.

Specific Options

The following files, or symbolic links to files, must be in /sbin if the corresponding subsystem is installed:

CommandDescription
fastbootReboot the system without checking the disks (optional)
fasthaltStop the system without checking the disks (optional)
fdiskPartition table manipulator (optional)
fsckFile system check and repair utility (optional)
fsck.*File system check and repair utility for a specific filesystem (optional)
gettyThe getty program (optional)
haltCommand to stop the system (optional)
ifconfigConfigure a network interface (optional)
initInitial process (optional)
mkfsCommand to build a filesystem (optional)
mkfs.*Command to build a specific filesystem (optional)
mkswapCommand to set up a swap area (optional)
rebootCommand to reboot the system (optional)
routeIP routing table utility (optional)
swaponEnable paging and swapping (optional)
swapoffDisable paging and swapping (optional)
updateDaemon to periodically flush filesystem buffers (optional)

/srv : Data for services provided by this system

Purpose

/srv contains site-specific data which is served by this system.

TipRationale
 

This main purpose of specifying this is so that users may find the location of the data files for particular service, and so that services which require a single tree for readonly data, writable data and scripts (such as cgi scripts) can be reasonably placed. Data that is only of interest to a specific user should go in that users' home directory.

The methodology used to name subdirectories of /srv is unspecified as there is currently no consensus on how this should be done. One method for structuring data under /srv is by protocol, eg. ftp, rsync, www, and cvs. On large systems it can be useful to structure /srv by administrative context, such as /srv/physics/www, /srv/compsci/cvs, etc. This setup will differ from host to host. Therefore, no program should rely on a specific subdirectory structure of /srv existing or data necessarily being stored in /srv. However /srv should always exist on FHS compliant systems and should be used as the default location for such data.

Distributions must take care not to remove locally placed files in these directories without administrator permission. [20]

/tmp : Temporary files

Purpose

The /tmp directory must be made available for programs that require temporary files.

Programs must not assume that any files or directories in /tmp are preserved between invocations of the program.

TipRationale
 

IEEE standard P1003.2 (POSIX, part 2) makes requirements that are similar to the above section.

Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted.

FHS added this recommendation on the basis of historical precedent and common practice, but did not make it a requirement because system administration is not within the scope of this standard.

Chapter 4. The /usr Hierarchy

Purpose

/usr is the second major section of the filesystem. /usr is shareable, read-only data. That means that /usr should be shareable between various FHS-compliant hosts and must not be written to. Any information that is host-specific or varies with time is stored elsewhere.

Large software packages must not use a direct subdirectory under the /usr hierarchy.

Requirements

The following directories, or symbolic links to directories, are required in /usr.

DirectoryDescription
binMost user commands
includeHeader files included by C programs
libLibraries
localLocal hierarchy (empty after main installation)
sbinNon-vital system binaries
shareArchitecture-independent data

Specific Options

DirectoryDescription
X11R6XWindow System, version 11 release 6 (optional)
gamesGames and educational binaries (optional)
lib<qual>Alternate Format Libraries (optional)
srcSource code (optional)

An exception is made for the X Window System because of considerable precedent and widely-accepted practice.

The following symbolic links to directories may be present. This possibility is based on the need to preserve compatibility with older systems until all implementations can be assumed to use the /var hierarchy.

    /usr/spool -> /var/spool
    /usr/tmp -> /var/tmp
    /usr/spool/locks -> /var/lock

Once a system no longer requires any one of the above symbolic links, the link may be removed, if desired.

/usr/X11R6 : X Window System, Version 11 Release 6 (optional)

Purpose

This hierarchy is reserved for the X Window System, version 11 release 6, and related files.

To simplify matters and make XFree86 more compatible with the X Window System on other systems, the following symbolic links must be present if /usr/X11R6 exists:

    /usr/bin/X11 -> /usr/X11R6/bin
    /usr/lib/X11 -> /usr/X11R6/lib/X11
    /usr/include/X11 -> /usr/X11R6/include/X11

In general, software must not be installed or managed via the above symbolic links. They are intended for utilization by users only. The difficulty is related to the release version of the X Window System — in transitional periods, it is impossible to know what release of X11 is in use.

Specific Options

Host-specific data in /usr/X11R6/lib/X11 should be interpreted as a demonstration file. Applications requiring information about the current host must reference a configuration file in /etc/X11, which may be linked to a file in /usr/X11R6/lib. [21]

/usr/bin : Most user commands

Purpose

This is the primary directory of executable commands on the system.

Specific Options

The following directories, or symbolic links to directories, must be in /usr/bin, if the corresponding subsystem is installed:

DirectoryDescription
mhCommands for the MH mail handling system (optional)

/usr/bin/X11 must be a symlink to /usr/X11R6/bin if the latter exists.

The following files, or symbolic links to files, must be in /usr/bin, if the corresponding subsystem is installed:

CommandDescription
perlThe Practical Extraction and Report Language (optional)
pythonThe Python interpreted language (optional)
tclshSimple shell containing Tcl interpreter (optional)
wishSimple Tcl/Tk windowing shell (optional)
expectProgram for interactive dialog (optional)

TipRationale
 

Because shell script interpreters (invoked with #!<path> on the first line of a shell script) cannot rely on a path, it is advantageous to standardize their locations. The Bourne shell and C-shell interpreters are already fixed in /bin, but Perl, Python, and Tcl are often found in many different places. They may be symlinks to the physical location of the shell interpreters.

/usr/include : Directory for standard include files.

Purpose

This is where all of the system's general-use include files for the C programming language should be placed.

Specific Options

The following directories, or symbolic links to directories, must be in /usr/include, if the corresponding subsystem is installed:

DirectoryDescription
bsdBSD compatibility include files (optional)

The symbolic link /usr/include/X11 must link to /usr/X11R6/include/X11 if the latter exists.

/usr/lib : Libraries for programming and packages

Purpose

/usr/lib includes object files, libraries, and internal binaries that are not intended to be executed directly by users or shell scripts. [22]

Applications may use a single subdirectory under /usr/lib. If an application uses a subdirectory, all architecture-dependent data exclusively used by the application must be placed within that subdirectory. [23]

Specific Options

For historical reasons, /usr/lib/sendmail must be a symbolic link to /usr/sbin/sendmail if the latter exists. [24]

If /lib/X11 exists, /usr/lib/X11 must be a symbolic link to /lib/X11, or to whatever /lib/X11 is a symbolic link to. [25]

/usr/lib<qual> : Alternate format libraries (optional)

Purpose

/usr/lib<qual> performs the same role as /usr/lib for an alternate binary format, except that the symbolic links /usr/lib<qual>/sendmail and /usr/lib<qual>/X11 are not required. [26]

/usr/local : Local hierarchy

Purpose

The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated. It may be used for programs and data that are shareable amongst a group of hosts, but not found in /usr.

Locally installed software must be placed within /usr/local rather than /usr unless it is being installed to replace or upgrade software in /usr. [27]

Requirements

The following directories, or symbolic links to directories, must be in /usr/local

DirectoryDescription
binLocal binaries
etcHost-specific system configuration for local binaries
gamesLocal game binaries
includeLocal C header files
libLocal libraries
manLocal online manuals
sbinLocal system binaries
shareLocal architecture-independent hierarchy
srcLocal source code

No other directories, except those listed below, may be in /usr/local after first installing a FHS-compliant system.

Specific Options

If directories /lib<qual> or /usr/lib<qual> exist, the equivalent directories must also exist in /usr/local.

/usr/local/etc may be a symbolic link to /etc/local.

TipRationale
 

The consistency of /usr/local/etc is beneficial to installers, and is already used in other systems. As all of /usr/local needs to be backed up to reproduce a system, it introduces no additional maintenance overhead, but a symlink to /etc/local is suitable if systems want alltheir configuration under one hierarchy.

Note that /usr/etc is still not allowed: programs in /usr should place configuration files in /etc.

/usr/local/share

The requirements for the contents of this directory are the same as /usr/share. The only additional constraint is that /usr/local/share/man and /usr/local/man directories must be synonomous (usually this means that one of them must be a symbolic link). [28]

/usr/sbin : Non-essential standard system binaries

Purpose

This directory contains any non-essential binaries used exclusively by the system administrator. System administration programs that are required for system repair, system recovery, mounting /usr, or other essential functions must be placed in /sbin instead. [29]

/usr/share : Architecture-independent data

Purpose

The /usr/share hierarchy is for all read-only architecture independent data files. [30]

This hierarchy is intended to be shareable among all architecture platforms of a given OS; thus, for example, a site with i386, Alpha, and PPC platforms might maintain a single /usr/share directory that is centrally-mounted. Note, however, that /usr/share is generally not intended to be shared by different OSes or by different releases of the same OS.

Any program or package which contains or requires data that doesn't need to be modified should store that data in /usr/share (or /usr/local/share, if installed locally). It is recommended that a subdirectory be used in /usr/share for this purpose.

Game data stored in /usr/share/games must be purely static data. Any modifiable files, such as score files, game play logs, and so forth, should be placed in /var/games.

Requirements

The following directories, or symbolic links to directories, must be in /usr/share

DirectoryDescription
manOnline manuals
miscMiscellaneous architecture-independent data

Specific Options

The following directories, or symbolic links to directories, must be in /usr/share, if the corresponding subsystem is installed:

DirectoryDescription
dictWord lists (optional)
docMiscellaneous documentation (optional)
gamesStatic data files for /usr/games (optional)
infoGNU Info system s primary directory (optional)
localeLocale information (optional)
nlsMessage catalogs for Native language support (optional)
sgmlSGML data (optional)
terminfoDirectories for terminfo database (optional)
tmactroff macros not distributed with groff (optional)
xmlXML data (optional)
zoneinfoTimezone information and configuration (optional)

It is recommended that application-specific, architecture-independent directories be placed here. Such directories include groff, perl, ghostscript, texmf, and kbd (Linux) or syscons (BSD). They may, however, be placed in /usr/lib for backwards compatibility, at the distributor's discretion. Similarly, a /usr/lib/games hierarchy may be used in addition to the /usr/share/games hierarchy if the distributor wishes to place some game data there.

/usr/share/dict : Word lists (optional)

Purpose

This directory is the home for word lists on the system; Traditionally this directory contains only the English words file, which is used by look(1) and various spelling programs. words may use either American or British spelling.

TipRationale
 

The reason that only word lists are located here is that they are the only files common to all spell checkers.

Specific Options

The following files, or symbolic links to files, must be in /usr/share/dict, if the corresponding subsystem is installed:

FileDescription
wordsList of English words (optional)

Sites that require both American and British spelling may link words to ­/usr/share/dict/american-english or ­/usr/share/dict/british-english.

Word lists for other languages may be added using the English name for that language, e.g., /usr/share/dict/french, /usr/share/dict/danish, etc. These should, if possible, use an ISO 8859 character set which is appropriate for the language in question; if possible the Latin1 (ISO 8859-1) character set should be used (this is often not possible).

Other word lists must be included here, if present.

/usr/share/man : Manual pages

Purpose

This section details the organization for manual pages throughout the system, including /usr/share/man. Also refer to the section on /var/cache/man.

The primary <mandir> of the system is /usr/share/man. /usr/share/man contains manual information for commands and data under the / and /usr filesystems. [31]

Manual pages are stored in <mandir>/<locale>/man<section>/<arch>. An explanation of <mandir>, <locale>, <section>, and <arch> is given below.

A description of each section follows:

  • man1: User programs Manual pages that describe publicly accessible commands are contained in this chapter. Most program documentation that a user will need to use is located here.

  • man2: System calls This section describes all of the system calls (requests for the kernel to perform operations).

  • man3: Library functions and subroutines Section 3 describes program library routines that are not direct calls to kernel services. This and chapter 2 are only really of interest to programmers.

  • man4: Special files Section 4 describes the special files, related driver functions, and networking support available in the system. Typically, this includes the device files found in /dev and the kernel interface to networking protocol support.

  • man5: File formats The formats for many data files are documented in the section 5. This includes various include files, program output files, and system files.

  • man6: Games This chapter documents games, demos, and generally trivial programs. Different people have various notions about how essential this is.

  • man7: Miscellaneous Manual pages that are difficult to classify are designated as being section 7. The troff and other text processing macro packages are found here.

  • man8: System administration Programs used by system administrators for system operation and maintenance are documented here. Some of these programs are also occasionally useful for normal users.

Specific Options

The following directories, or symbolic links to directories, must be in /usr/share/<mandir>/<locale>, unless they are empty: [32]

DirectoryDescription
man1User programs (optional)
man2System calls (optional)
man3Library calls (optional)
man4Special files (optional)
man5File formats (optional)
man6Games (optional)
man7Miscellaneous (optional)
man8System administration (optional)

The component <section> describes the manual section.

Provisions must be made in the structure of /usr/share/man to support manual pages which are written in different (or multiple) languages. These provisions must take into account the storage and reference of these manual pages. Relevant factors include language (including geographical-based differences), and character code set.

This naming of language subdirectories of /usr/share/man is based on Appendix E of the POSIX 1003.1 standard which describes the locale identification string — the most well-accepted method to describe a cultural environment. The <locale> string is:

<language>[_<territory>][.<character-set>][,<version>]

The <language> field must be taken from ISO 639 (a code for the representation of names of languages). It must be two characters wide and specified with lowercase letters only.

The <territory> field must be the two-letter code of ISO 3166 (a specification of representations of countries), if possible. (Most people are familiar with the two-letter codes used for the country codes in email addresses.) It must be two characters wide and specified with uppercase letters only. [33]

The <character-set> field must represent the standard describing the character set. If the ­<character-set> field is just a numeric specification, the number represents the number of the international standard describing the character set. It is recommended that this be a numeric representation if possible (ISO standards, especially), not include additional punctuation symbols, and that any letters be in lowercase.

A parameter specifying a <version> of the profile may be placed after the ­<character-set> field, delimited by a comma. This may be used to discriminate between different cultural needs; for instance, dictionary order versus a more systems-oriented collating order. This standard recommends not using the <version> field, unless it is necessary.

Systems which use a unique language and code set for all manual pages may omit the <locale> substring and store all manual pages in <mandir>. For example, systems which only have English manual pages coded with ASCII, may store manual pages (the man<section> directories) directly in /usr/share/man. (That is the traditional circumstance and arrangement, in fact.)

Countries for which there is a well-accepted standard character code set may omit the ­<character-set> field, but it is strongly recommended that it be included, especially for countries with several competing standards.

Various examples:

LanguageTerritoryCharacter SetDirectory
English—ASCII/usr/share/man/en
EnglishUnited KingdomISO 8859-15/usr/share/man/en_GB
EnglishUnited StatesASCII/usr/share/man/en_US
FrenchCanadaISO 8859-1/usr/share/man/fr_CA
FrenchFranceISO 8859-1/usr/share/man/fr_FR
GermanGermanyISO 646/usr/share/man/de_DE.646
GermanGermanyISO 6937/usr/share/man/de_DE.6937
GermanGermanyISO 8859-1/usr/share/man/de_DE.88591
GermanSwitzerlandISO 646/usr/share/man/de_CH.646
JapaneseJapanJIS/usr/share/man/ja_JP.jis
JapaneseJapanSJIS/usr/share/man/ja_JP.sjis
JapaneseJapanUJIS (or EUC-J)/usr/share/man/ja_JP.ujis

Similarly, provision must be made for manual pages which are architecture-dependent, such as documentation on device-drivers or low-level system administration commands. These must be placed under an <arch> directory in the appropriate man<section> directory; for example, a man page for the i386 ctrlaltdel(8) command might be placed in /usr/share/man/<locale>/man8/i386/ctrlaltdel.8.

Manual pages for commands and data under /usr/local are stored in /usr/local/man. Manual pages for X11R6 are stored in /usr/X11R6/man. It follows that all manual page hierarchies in the system must have the same structure as /usr/share/man.

The cat page sections (cat<section>) containing formatted manual page entries are also found within subdirectories of <mandir>/<locale>, but are not required nor may they be distributed in lieu of nroff source manual pages.

The numbered sections "1" through "8" are traditionally defined. In general, the file name for manual pages located within a particular section end with .<section>.

In addition, some large sets of application-specific manual pages have an additional suffix appended to the manual page filename. For example, the MH mail handling system manual pages must have mh appended to all MH manuals. All X Window System manual pages must have an x appended to the filename.

The practice of placing various language manual pages in appropriate subdirectories of /usr/share/man also applies to the other manual page hierarchies, such as /usr/local/man and /usr/X11R6/man. (This portion of the standard also applies later in the section on the optional /var/cache/man structure.)

/usr/share/misc : Miscellaneous architecture-independent data

This directory contains miscellaneous architecture-independent files which don't require a separate subdirectory under /usr/share.

Specific Options

The following files, or symbolic links to files, must be in /usr/share/misc, if the corresponding subsystem is installed:

FileDescription
asciiASCII character set table (optional)
magicDefault list of magic numbers for the file command (optional)
termcapTerminal capability database (optional)
termcap.dbTerminal capability database (optional)

Other (application-specific) files may appear here, but a distributor may place them in /usr/lib at their discretion. [34]

/usr/share/sgml : SGML data (optional)

Purpose

/usr/share/sgml contains architecture-independent files used by SGML applications, such as ordinary catalogs (not the centralized ones, see /etc/sgml), DTDs, entities, or style sheets.

Specific Options

The following directories, or symbolic links to directories, must be in /usr/share/sgml, if the corresponding subsystem is installed:

DirectoryDescription
docbookdocbook DTD (optional)
teitei DTD (optional)
htmlhtml DTD (optional)
mathmlmathml DTD (optional)

Other files that are not specific to a given DTD may reside in their own subdirectory.

/usr/share/xml : XML data (optional)

Purpose

/usr/share/xml contains architecture-independent files used by XML applications, such as ordinary catalogs (not the centralized ones, see /etc/sgml), DTDs, entities, or style sheets.

Specific Options

The following directories, or symbolic links to directories, must be in /usr/share/xml, if the corresponding subsystem is installed:

DirectoryDescription
docbookdocbook XML DTD (optional)
xhtmlXHTML DTD (optional)
mathmlMathML DTD (optional)

/usr/src : Source code (optional)

Purpose

Source code may be place placed in this subdirectory, only for reference purposes. [35]

Chapter 5. The /var Hierarchy

Purpose

/var contains variable data files. This includes spool directories and files, administrative and logging data, and transient and temporary files.

Some portions of /var are not shareable between different systems. For instance, /var/log, /var/lock, and /var/run. Other portions may be shared, notably /var/mail, /var/cache/man, /var/cache/fonts, and /var/spool/news.

/var is specified here in order to make it possible to mount /usr read-only. Everything that once went into /usr that is written to during system operation (as opposed to installation and software maintenance) must be in /var.

If /var cannot be made a separate partition, it is often preferable to move /var out of the root partition and into the /usr partition. (This is sometimes done to reduce the size of the root partition or when space runs low in the root partition.) However, /var must not be linked to /usr because this makes separation of /usr and /var more difficult and is likely to create a naming conflict. Instead, link /var to /usr/var.

Applications must generally not add directories to the top level of /var. Such directories should only be added if they have some system-wide implication, and in consultation with the FHS mailing list.

Requirements

The following directories, or symbolic links to directories, are required in /var.

DirectoryDescription
cacheApplication cache data
libVariable state information
localVariable data for /usr/local
lockLock files
logLog files and directories
optVariable data for /opt
runData relevant to running processes
spoolApplication spool data
tmpTemporary files preserved between system reboots

Several directories are `reserved' in the sense that they must not be used arbitrarily by some new application, since they would conflict with historical and/or local practice. They are:

    /var/backups
    /var/cron
    /var/msgs
    /var/preserve

Specific Options

The following directories, or symbolic links to directories, must be in /var, if the corresponding subsystem is installed:

DirectoryDescription
accountProcess accounting logs (optional)
crashSystem crash dumps (optional)
gamesVariable game data (optional)
mailUser mailbox files (optional)
ypNetwork Information Service (NIS) database files (optional)

/var/account : Process accounting logs (optional)

Purpose

This directory holds the current active process accounting log and the composite process usage data (as used in some UNIX-like systems by lastcomm and sa).

/var/cache : Application cache data

Purpose

/var/cache is intended for cached data from applications. Such data is locally generated as a result of time-consuming I/O or calculation. The application must be able to regenerate or restore the data. Unlike /var/spool, the cached files can be deleted without data loss. The data must remain valid between invocations of the application and rebooting the system.

Files located under /var/cache may be expired in an application specific manner, by the system administrator, or both. The application must always be able to recover from manual deletion of these files (generally because of a disk space shortage). No other requirements are made on the data format of the cache directories.

TipRationale
 

The existence of a separate directory for cached data allows system administrators to set different disk and backup policies from other directories in /var.

Specific Options

DirectoryDescription
fontsLocally-generated fonts (optional)
manLocally-formatted manual pages (optional)
wwwWWW proxy or cache data (optional)
<package>Package specific cache data (optional)

/var/cache/fonts : Locally-generated fonts (optional)

Purpose

The directory /var/cache/fonts should be used to store any dynamically-created fonts. In particular, all of the fonts which are automatically generated by mktexpk must be located in appropriately-named subdirectories of /var/cache/fonts. [36]

Specific Options

Other dynamically created fonts may also be placed in this tree, under appropriately-named subdirectories of /var/cache/fonts.

/var/cache/man : Locally-formatted manual pages (optional)

Purpose

This directory provides a standard location for sites that provide a read-only /usr partition, but wish to allow caching of locally-formatted man pages. Sites that mount /usr as writable (e.g., single-user installations) may choose not to use /var/cache/man and may write formatted man pages into the cat<section> directories in /usr/share/man directly. We recommend that most sites use one of the following options instead:

  • Preformat all manual pages alongside the unformatted versions.

  • Allow no caching of formatted man pages, and require formatting to be done each time a man page is brought up.

  • Allow local caching of formatted man pages in /var/cache/man.

The structure of /var/cache/man needs to reflect both the fact of multiple man page hierarchies and the possibility of multiple language support.

Given an unformatted manual page that normally appears in <path>/man/<locale>/man<section>, the directory to place formatted man pages in is /var/cache/man/<catpath>/<locale>/cat<section>, where <catpath> is derived from <path> by removing any leading usr and/or trailing share pathname components. (Note that the <locale> component may be missing.) [37]

Man pages written to /var/cache/man may eventually be transferred to the appropriate preformatted directories in the source man hierarchy or expired; likewise formatted man pages in the source man hierarchy may be expired if they are not accessed for a period of time.

If preformatted manual pages come with a system on read-only media (a CD-ROM, for instance), they must be installed in the source man hierarchy (e.g. /usr/share/man/cat<section>). /var/cache/man is reserved as a writable cache for formatted manual pages.

TipRationale
 

Release 1.2 of the standard specified /var/catman for this hierarchy. The path has been moved under /var/cache to better reflect the dynamic nature of the formatted man pages. The directory name has been changed to man to allow for enhancing the hierarchy to include post-processed formats other than "cat", such as PostScript, HTML, or DVI.

/var/crash : System crash dumps (optional)

Purpose

This directory holds system crash dumps. As of the date of this release of the standard, system crash dumps were not supported under Linux but may be supported by other systems which may comply with the FHS.

/var/games : Variable game data (optional)

Purpose

Any variable data relating to games in /usr should be placed here. /var/games should hold the variable data previously found in /usr; static data, such as help text, level descriptions, and so on, must remain elsewhere, such as /usr/share/games.

TipRationale
 

/var/games has been given a hierarchy of its own, rather than leaving it merged in with the old /var/lib as in release 1.2. The separation allows local control of backup strategies, permissions, and disk usage, as well as allowing inter-host sharing and reducing clutter in /var/lib. Additionally, /var/games is the path traditionally used by BSD.

/var/lib : Variable state information

Purpose

This hierarchy holds state information pertaining to an application or the system. State information is data that programs modify while they run, and that pertains to one specific host. Users must never need to modify files in /var/lib to configure a package's operation.

State information is generally used to preserve the condition of an application (or a group of inter-related applications) between invocations and between different instances of the same application. State information should generally remain valid after a reboot, should not be logging output, and should not be spooled data.

An application (or a group of inter-related applications) must use a subdirectory of /var/lib for its data. There is one required subdirectory, /var/lib/misc, which is intended for state files that don't need a subdirectory; the other subdirectories should only be present if the application in question is included in the distribution. [38]

/var/lib/<name> is the location that must be used for all distribution packaging support. Different distributions may use different names, of course.

Requirements

The following directories, or symbolic links to directories, are required in /var/lib:

DirectoryDescription
miscMiscellaneous state data

Specific Options

The following directories, or symbolic links to directories, must be in /var/lib, if the corresponding subsystem is installed:

DirectoryDescription
<editor>Editor backup files and state (optional)
<pkgtool>Packaging support files (optional)
<package>State data for packages and subsystems (optional)
hwclockState directory for hwclock (optional)
xdmX display manager variable data (optional)

/var/lib/<editor> : Editor backup files and state (optional)

Purpose

These directories contain saved files generated by any unexpected termination of an editor (e.g., elvis, jove, nvi).

Other editors may not require a directory for crash-recovery files, but may require a well-defined place to store other information while the editor is running. This information should be stored in a subdirectory under /var/lib (for example, GNU Emacs would place lock files in /var/lib/emacs/lock).

Future editors may require additional state information beyond crash-recovery files and lock files — this information should also be placed under /var/lib/<editor>.

TipRationale
 

Previous Linux releases, as well as all commercial vendors, use /var/preserve for vi or its clones. However, each editor uses its own format for these crash-recovery files, so a separate directory is needed for each editor.

Editor-specific lock files are usually quite different from the device or resource lock files that are stored in /var/lock and, hence, are stored under /var/lib.

/var/lib/hwclock : State directory for hwclock (optional)

Purpose

This directory contains the file /var/lib/hwclock/adjtime.

TipRationale
 

In FHS 2.1, this file was /etc/adjtime, but as hwclock updates it, that was obviously incorrect.

/var/lib/misc : Miscellaneous variable data

Purpose

This directory contains variable data not placed in a subdirectory in /var/lib. An attempt should be made to use relatively unique names in this directory to avoid namespace conflicts. [39]

/var/lock : Lock files

Purpose

Lock files should be stored within the /var/lock directory structure.

Lock files for devices and other resources shared by multiple applications, such as the serial device lock files that were originally found in either /usr/spool/locks or /usr/spool/uucp, must now be stored in /var/lock. The naming convention which must be used is "LCK.." followed by the base name of the device. For example, to lock /dev/ttyS0 the file "LCK..ttyS0" would be created. [40]

The format used for the contents of such lock files must be the HDB UUCP lock file format. The HDB format is to store the process identifier (PID) as a ten byte ASCII decimal number, with a trailing newline. For example, if process 1230 holds a lock file, it would contain the eleven characters: space, space, space, space, space, space, one, two, three, zero, and newline.

/var/log : Log files and directories

Purpose

This directory contains miscellaneous log files. Most logs must be written to this directory or an appropriate subdirectory.

Specific Options

The following files, or symbolic links to files, must be in /var/log, if the corresponding subsystem is installed:

FileDescription
lastlogrecord of last login of each user
messagessystem messages from syslogd
wtmprecord of all logins and logouts

/var/mail : User mailbox files (optional)

Purpose

The mail spool must be accessible through /var/mail and the mail spool files must take the form <username>. [41]

User mailbox files in this location must be stored in the standard UNIX mailbox format.

TipRationale
 

The logical location for this directory was changed from /var/spool/mail in order to bring FHS in-line with nearly every UNIX implementation. This change is important for inter-operability since a single /var/mail is often shared between multiple hosts and multiple UNIX implementations (despite NFS locking issues).

It is important to note that there is no requirement to physically move the mail spool to this location. However, programs and header files must be changed to use /var/mail.

/var/opt : Variable data for /opt

Purpose

Variable data of the packages in /opt must be installed in /var/opt/<subdir>, where <subdir> is the name of the subtree in /opt where the static data from an add-on software package is stored, except where superseded by another file in /etc. No structure is imposed on the internal arrangement of /var/opt/<subdir>.

TipRationale
 

Refer to the rationale for /opt.

/var/run : Run-time variable data

Purpose

This directory contains system information data describing the system since it was booted. Files under this directory must be cleared (removed or truncated as appropriate) at the beginning of the boot process. Programs may have a subdirectory of /var/run; this is encouraged for programs that use more than one run-time file. [42] Process identifier (PID) files, which were originally placed in /etc, must be placed in /var/run. The naming convention for PID files is <program-name>.pid. For example, the crond PID file is named /var/run/crond.pid.

Requirements

The internal format of PID files remains unchanged. The file must consist of the process identifier in ASCII-encoded decimal, followed by a newline character. For example, if crond was process number 25, /var/run/crond.pid would contain three characters: two, five, and newline.

Programs that read PID files should be somewhat flexible in what they accept; i.e., they should ignore extra whitespace, leading zeroes, absence of the trailing newline, or additional lines in the PID file. Programs that create PID files should use the simple specification located in the above paragraph.

The utmp file, which stores information about who is currently using the system, is located in this directory.

System programs that maintain transient UNIX-domain sockets must place them in this directory.

/var/spool : Application spool data

Purpose

/var/spool contains data which is awaiting some kind of later processing. Data in /var/spool represents work to be done in the future (by a program, user, or administrator); often data is deleted after it has been processed. [43]

Specific Options

The following directories, or symbolic links to directories, must be in /var/spool, if the corresponding subsystem is installed:

DirectoryDescription
lpdPrinter spool directory (optional)
mqueueOutgoing mail queue (optional)
newsNews spool directory (optional)
rwhoRwhod files (optional)
uucpSpool directory for UUCP (optional)

/var/spool/lpd : Line-printer daemon print queues (optional)

Purpose

The lock file for lpd, lpd.lock, must be placed in /var/spool/lpd. It is suggested that the lock file for each printer be placed in the spool directory for that specific printer and named lock.

Specific Options

DirectoryDescription
printerSpools for a specific printer (optional)

/var/spool/rwho : Rwhod files (optional)

Purpose

This directory holds the rwhod information for other systems on the local net.

TipRationale
 

Some BSD releases use /var/rwho for this data; given its historical location in /var/spool on other systems and its approximate fit to the definition of `spooled' data, this location was deemed more appropriate.

/var/tmp : Temporary files preserved between system reboots

Purpose

The /var/tmp directory is made available for programs that require temporary files or directories that are preserved between system reboots. Therefore, data stored in /var/tmp is more persistent than data in /tmp.

Files and directories located in /var/tmp must not be deleted when the system is booted. Although data stored in /var/tmp is typically deleted in a site-specific manner, it is recommended that deletions occur at a less frequent interval than /tmp.

/var/yp : Network Information Service (NIS) database files (optional)

Purpose

Variable data for the Network Information Service (NIS), formerly known as the Sun Yellow Pages (YP), must be placed in this directory.

TipRationale
 

/var/yp is the standard directory for NIS (YP) data and is almost exclusively used in NIS documentation and systems. [44]

Chapter 6. Operating System Specific Annex

This section is for additional requirements and recommendations that only apply to a specific operating system. The material in this section should never conflict with the base standard.

Linux

This is the annex for the Linux operating system.

/ : Root directory

On Linux systems, if the kernel is located in /, we recommend using the names vmlinux or vmlinuz, which have been used in recent Linux kernel source packages.

/bin : Essential user command binaries (for use by all users)

Linux systems which require them place these additional files into /bin:

  • setserial

/dev : Devices and special files

The following devices must exist under /dev.

/dev/null

All data written to this device is discarded. A read from this device will return an EOF condition.

/dev/zero

This device is a source of zeroed out data. All data written to this device is discarded. A read from this device will return as many bytes containing the value zero as was requested.

/dev/tty

This device is a synonym for the controlling terminal of a process. Once this device is opened, all reads and writes will behave as if the actual controlling terminal device had been opened.

TipRationale
 

Previous versions of the FHS had stricter requirements for /dev. Other devices may also exist in /dev. Device names may exist as symbolic links to other device nodes located in /dev or subdirectories of /dev. There is no requirement concerning major/minor number values.

/etc : Host-specific system configuration

Linux systems which require them place these additional files into /etc.

  • lilo.conf

/lib64 and /lib32 : 64/32-bit libraries (architecture dependent)

The 64-bit architectures PPC64, s390x, sparc64 and AMD64 must place 64-bit libraries in /lib64, and 32-bit (or 31-bit on s390) libraries in /lib.

The 64-bit architecture IA64 must place 64-bit libraries in /lib.

TipRationale
 

This is a refinement of the general rules for /lib<qual> and /usr/lib<qual>. The architectures PPC64, s390x, sparc64 and AMD64 support support both 32-bit (for s390 more precise 31-bit) and 64-bit programs. Using lib for 32-bit binaries allows existing binaries from the 32-bit systems to work without any changes: such binaries are expected to be numerous. IA-64 uses a different scheme, reflecting the deprecation of 32-bit binaries (and hence libraries) on that architecture.

/proc : Kernel and process information virtual filesystem

The proc filesystem is the de-facto standard Linux method for handling process and system information, rather than /dev/kmem and other similar methods. We strongly encourage this for the storage and retrieval of process information as well as other kernel and memory information.

/sbin : Essential system binaries

Linux systems place these additional files into /sbin.

  • Second extended filesystem commands (optional):

    • badblocks

    • dumpe2fs

    • e2fsck

    • mke2fs

    • mklost+found

    • tune2fs

  • Boot-loader map installer (optional):

    • lilo

Optional files for /sbin:

  • Static binaries:

    • ldconfig

    • sln

    • ssync

    Static ln (sln) and static sync (ssync) are useful when things go wrong. The primary use of sln (to repair incorrect symlinks in /lib after a poorly orchestrated upgrade) is no longer a major concern now that the ldconfig program (usually located in /usr/sbin) exists and can act as a guiding hand in upgrading the dynamic libraries. Static sync is useful in some emergency situations. Note that these need not be statically linked versions of the standard ln and sync, but may be.

    The ldconfig binary is optional for /sbin since a site may choose to run ldconfig at boot time, rather than only when upgrading the shared libraries. (It's not clear whether or not it is advantageous to run ldconfig on each boot.) Even so, some people like ldconfig around for the following (all too common) situation:

    1. I've just removed /lib/<file>.

    2. I can't find out the name of the library because ls is dynamically linked, I'm using a shell that doesn't have ls built-in, and I don't know about using "echo *" as a replacement.

    3. I have a static sln, but I don't know what to call the link.

  • Miscellaneous:

    • ctrlaltdel

    • kbdrate

    So as to cope with the fact that some keyboards come up with such a high repeat rate as to be unusable, kbdrate may be installed in /sbin on some systems.

    Since the default action in the kernel for the Ctrl-Alt-Del key combination is an instant hard reboot, it is generally advisable to disable the behavior before mounting the root filesystem in read-write mode. Some init suites are able to disable Ctrl-Alt-Del, but others may require the ctrlaltdel program, which may be installed in /sbin on those systems.

/usr/include : Header files included by C programs

These symbolic links are required if a C or C++ compiler is installed and only for systems not based on glibc.

    /usr/include/asm -> /usr/src/linux/include/asm-<arch>
    /usr/include/linux -> /usr/src/linux/include/linux

/usr/src : Source code

For systems based on glibc, there are no specific guidelines for this directory. For systems based on Linux libc revisions prior to glibc, the following guidelines and rationale apply:

The only source code that should be placed in a specific location is the Linux kernel source code. It is located in /usr/src/linux.

If a C or C++ compiler is installed, but the complete Linux kernel source code is not installed, then the include files from the kernel source code must be located in these directories:

    /usr/src/linux/include/asm-<arch>
    /usr/src/linux/include/linux

<arch> is the name of the system architecture.

NoteNote
 

/usr/src/linux may be a symbolic link to a kernel source code tree.

TipRationale
 

It is important that the kernel include files be located in /usr/src/linux and not in /usr/include so there are no problems when system administrators upgrade their kernel version for the first time.

/var/spool/cron : cron and at jobs

This directory contains the variable data for the cron and at programs.

Chapter 7. Appendix

The FHS mailing list

The FHS mailing list is located at <freestandards-fhs-discuss@lists.sourceforge.net>. You can subscribe to the mailing list at this page http://sourceforge.net/projects/freestandards/.

Thanks to Network Operations at the University of California at San Diego who allowed us to use their excellent mailing list server.

As noted in the introduction, please do not send mail to the mailing list without first contacting the FHS editor or a listed contributor.

Background of the FHS

The process of developing a standard filesystem hierarchy began in August 1993 with an effort to restructure the file and directory structure of Linux. The FSSTND, a filesystem hierarchy standard specific to the Linux operating system, was released on February 14, 1994. Subsequent revisions were released on October 9, 1994 and March 28, 1995.

In early 1995, the goal of developing a more comprehensive version of FSSTND to address not only Linux, but other UNIX-like systems was adopted with the help of members of the BSD development community. As a result, a concerted effort was made to focus on issues that were general to UNIX-like systems. In recognition of this widening of scope, the name of the standard was changed to Filesystem Hierarchy Standard or FHS for short.

Volunteers who have contributed extensively to this standard are listed at the end of this document. This standard represents a consensus view of those and other contributors.

General Guidelines

Here are some of the guidelines that have been used in the development of this standard:

  • Solve technical problems while limiting transitional difficulties.

  • Make the specification reasonably stable.

  • Gain the approval of distributors, developers, and other decision-makers in relevant development groups and encourage their participation.

  • Provide a standard that is attractive to the implementors of different UNIX-like systems.

Scope

This document specifies a standard filesystem hierarchy for FHS filesystems by specifying the location of files and directories, and the contents of some system files.

This standard has been designed to be used by system integrators, package developers, and system administrators in the construction and maintenance of FHS compliant filesystems. It is primarily intended to be a reference and is not a tutorial on how to manage a conforming filesystem hierarchy.

The FHS grew out of earlier work on FSSTND, a filesystem organization standard for the Linux operating system. It builds on FSSTND to address interoperability issues not just in the Linux community but in a wider arena including 4.4BSD-based operating systems. It incorporates lessons learned in the BSD world and elsewhere about multi-architecture support and the demands of heterogeneous networking.

Although this standard is more comprehensive than previous attempts at filesystem hierarchy standardization, periodic updates may become necessary as requirements change in relation to emerging technology. It is also possible that better solutions to the problems addressed here will be discovered so that our solutions will no longer be the best possible solutions. Supplementary drafts may be released in addition to periodic updates to this document. However, a specific goal is backwards compatibility from one release of this document to the next.

Comments related to this standard are welcome. Any comments or suggestions for changes may be directed to the FHS editor (Daniel Quinlan <quinlan@pathname.com>) or the FHS mailing list. Typographical or grammatical comments should be directed to the FHS editor.

Before sending mail to the mailing list it is requested that you first contact the FHS editor in order to avoid excessive re-discussion of old topics.

Questions about how to interpret items in this document may occasionally arise. If you have need for a clarification, please contact the FHS editor. Since this standard represents a consensus of many participants, it is important to make certain that any interpretation also represents their collective opinion. For this reason it may not be possible to provide an immediate response unless the inquiry has been the subject of previous discussion.

Acknowledgments

The developers of the FHS wish to thank the developers, system administrators, and users whose input was essential to this standard. We wish to thank each of the contributors who helped to write, compile, and compose this standard.

The FHS Group also wishes to thank those Linux developers who supported the FSSTND, the predecessor to this standard. If they hadn't demonstrated that the FSSTND was beneficial, the FHS could never have evolved.

Contributors

Brandon S. Allbery<bsa@kf8nh.wariat.org>
Keith Bostic<bostic@cs.berkeley.edu>
Drew Eckhardt<drew@colorado.edu>
Rik Faith<faith@cs.unc.edu>
Stephen Harris<sweh@spuddy.mew.co.uk>
Ian Jackson<ijackson@cus.cam.ac.uk>
Andreas Jaeger<aj@suse.de>
John A. Martin<jmartin@acm.org>
Ian McCloghrie<ian@ucsd.edu>
Chris Metcalf<metcalf@lcs.mit.edu>
Ian Murdock<imurdock@debian.org>
David C. Niemi<niemidc@clark.net>
Daniel Quinlan<quinlan@pathname.com>
Eric S. Raymond<esr@thyrsus.com>
Rusty Russell<rusty@rustcorp.com.au>
Mike Sangrey<mike@sojurn.lns.pa.us>
David H. Silber<dhs@glowworm.firefly.com>
Thomas Sippel-Dau<t.sippel-dau@ic.ac.uk>
Theodore Ts'o<tytso@athena.mit.edu>
Stephen Tweedie<sct@dcs.ed.ac.uk>
Fred N. van Kempen<waltje@infomagic.com>
Bernd Warken<bwarken@mayn.de>
Christopher Yeoh<cyeoh@samba.org>

Notes

[1]

Command binaries that are not essential enough to place into /bin must be placed in /usr/bin, instead. Items that are required only by non-root users (the X Window System, chsh, etc.) are generally not essential enough to be placed into the root partition.

[2]

Programs necessary to arrange for the boot loader to be able to boot a file must be placed in /sbin. Configuration files for boot loaders must be placed in /etc.

The GRUB bootloader reads its configurations file before booting, so that must be placed in /boot. However, it is a configuration file, so should be in /etc. The answer here is a symbolic link such as /etc/grub/menu.lst -> /boot/menu.lst.

[3]

On some i386 machines, it may be necessary for /boot to be located on a separate partition located completely below cylinder 1024 of the boot device due to hardware constraints.

Certain MIPS systems require a /boot partition that is a mounted MS-DOS filesystem or whatever other filesystem type is accessible for the firmware. This may result in restrictions with respect to usable filenames within /boot (only for affected systems).

[4]

The setup of command scripts invoked at boot time may resemble System V, BSD or other models. Further specification in this area may be added to a future version of this standard.

[5]

It is recommended that files be stored in subdirectories of /etc rather than directly in /etc.

[6]

Systems that use the shadow password suite will have additional configuration files in /etc (/etc/shadow and others) and programs in /usr/sbin (useradd, usermod, and others).

[7]

On some Linux systems, this may be a symbolic link to /proc/mounts, in which case this exception is not required.

[8]

/etc/X11/xdm holds the configuration files for xdm. These are most of the files previously found in /usr/lib/X11/xdm. Some local variable data for xdm is stored in /var/lib/xdm.

[9]

Different people prefer to place user accounts in a variety of places. This section describes only a suggested placement for user home directories; nevertheless we recommend that all FHS-compliant distributions use this as the default location for home directories.

On small systems, each user's directory is typically one of the many subdirectories of /home such as /home/smith, /home/torvalds, /home/operator, etc. On large systems (especially when the /home directories are shared amongst many hosts using NFS) it is useful to subdivide user home directories. Subdivision may be accomplished by using subdirectories such as /home/staff, /home/guests, /home/students, etc.

[10]

If you want to find out a user's home directory, you should use the getpwent(3) library function rather than relying on /etc/passwd because user information may be stored remotely using systems such as NIS.

[11]

It is recommended that apart from autosave and lock files programs should refrain from creating non dot files or directories in a home directory without user intervention.

[12]

Shared libraries that are only necessary for binaries in /usr (such as any X Window binaries) must not be in /lib. Only the shared libraries required to run binaries in /bin and /sbin may be here. In particular, the library libm.so.* may also be placed in /usr/lib if it is not required by anything in /bin or /sbin.

[13]

The usual placement of this binary is /usr/bin/cpp.

[14]

This is commonly used for 64-bit or 32-bit support on systems which support multiple binary formats, but require libraries of the same name. In this case, /lib32 and /lib64 might be the library directories, and /lib a symlink to one of them.

[15]

/lib<qual>/cpp is still permitted: this allows the case where /lib and /lib<qual> are the same (one is a symbolic link to the other).

[16]

A compliant implementation with two CDROM drives might have /media/cdrom0 and /media/cdrom1 with /media/cdrom a symlink to either of these.

[17]

If the home directory of the root account is not stored on the root partition it will be necessary to make certain it will default to / if it can not be located.

We recommend against using the root account for tasks that can be performed as an unprivileged user, and that it be used solely for system administration. For this reason, we recommend that subdirectories for mail and other applications not appear in the root account's home directory, and that mail for administration roles such as root, postmaster, and webmaster be forwarded to an appropriate user.

[18]

Originally, /sbin binaries were kept in /etc.

[19]

Deciding what things go into "sbin" directories is simple: if a normal (not a system administrator) user will ever run it directly, then it must be placed in one of the "bin" directories. Ordinary users should not have to place any of the sbin directories in their path.

For example, files such as chfn which users only occasionally use must still be placed in /usr/bin. ping, although it is absolutely necessary for root (network recovery and diagnosis) is often used by users and must live in /bin for that reason.

We recommend that users have read and execute permission for everything in /sbin except, perhaps, certain setuid and setgid programs. The division between /bin and /sbin was not created for security reasons or to prevent users from seeing the operating system, but to provide a good partition between binaries that everyone uses and ones that are primarily used for administration tasks. There is no inherent security advantage in making /sbin off-limits for users.

[20]

This is particularly important as these areas will often contain both files initially installed by the distributor, and those added by the administrator.

[21]

Examples of such configuration files include Xconfig, XF86Config, or system.twmrc)

[22]

Miscellaneous architecture-independent application-specific static files and subdirectories must be placed in /usr/share.

[23]

For example, the perl5 subdirectory for Perl 5 modules and libraries.

[24]

Some executable commands such as makewhatis and sendmail have also been traditionally placed in /usr/lib. makewhatis is an internal binary and must be placed in a binary directory; users access only catman. Newer sendmail binaries are now placed by default in /usr/sbin. Additionally, systems using a sendmail-compatible mail transfer agent must provide /usr/sbin/sendmail as a symbolic link to the appropriate executable.

[25]

Host-specific data for the X Window System must not be stored in /usr/lib/X11. Host-specific configuration files such as Xconfig or XF86Config must be stored in /etc/X11. This includes configuration data such as system.twmrc even if it is only made a symbolic link to a more global configuration file (probably in /usr/X11R6/lib/X11).

[26]

The case where /usr/lib and /usr/lib<qual> are the same (one is a symbolic link to the other) these files and the per-application subdirectories will exist.

[27]

Software placed in / or /usr may be overwritten by system upgrades (though we recommend that distributions do not overwrite data in /etc under these circumstances). For this reason, local software must not be placed outside of /usr/local without good reason.

[28]

/usr/local/man may be deprecated in future FHS releases, so if all else is equal, making that one a symlink seems sensible.

[29]

Locally installed system administration programs should be placed in /usr/local/sbin.

[30]

Much of this data originally lived in /usr (man, doc) or /usr/lib (dict, terminfo, zoneinfo).

[31]

Obviously, there are no manual pages in / because they are not required at boot time nor are they required in emergencies. Really.

[32]

For example, if /usr/local/man has no manual pages in section 4 (Devices), then /usr/local/man/man4 may be omitted.

[33]

A major exception to this rule is the United Kingdom, which is `GB' in the ISO 3166, but `UK' for most email addresses.

[34]

Some such files include: airport, birthtoken, eqnchar, getopt, gprof.callg, gprof.flat, inter.phone, ipfw.samp.filters, ipfw.samp.scripts, keycap.pcvt, mail.help, mail.tildehelp, man.template, map3270, mdoc.template, more.help, na.phone, nslookup.help, operator, scsi_modes, sendmail.hf, style, units.lib, vgrindefs, vgrindefs.db, zipcodes

[35]

Generally, source should not be built within this hierarchy.

[36]

This standard does not currently incorporate the TeX Directory Structure (a document that describes the layout TeX files and directories), but it may be useful reading. It is located at ftp://ctan.tug.org/tex/

[37]

For example, /usr/share/man/man1/ls.1 is formatted into /var/cache/man/cat1/ls.1, and /usr/X11R6/man/<locale>/man3/XtClass.3x into /var/cache/man/X11R6/<locale>/cat3/XtClass.3x.

[38]

An important difference between this version of this standard and previous ones is that applications are now required to use a subdirectory of /var/lib.

[39]

This hierarchy should contain files stored in /var/db in current BSD releases. These include locate.database and mountdtab, and the kernel symbol database(s).

[40]

Then, anything wishing to use /dev/ttyS0 can read the lock file and act accordingly (all locks in /var/lock should be world-readable).

[41]

Note that /var/mail may be a symbolic link to another directory.

[42]

/var/run should be unwritable for unprivileged users (root or users running daemons); it is a major security problem if any user can write in this directory.

[43]

UUCP lock files must be placed in /var/lock. See the above section on /var/lock.

[44]

NIS should not be confused with Sun NIS+, which uses a different directory, /var/nis.

ubuntu-policy/debian/0000755000175000017500000000000011216715405015363 5ustar cjwatsoncjwatsonubuntu-policy/debian/control0000644000175000017500000000254611216714127016775 0ustar cjwatsoncjwatsonSource: ubuntu-policy Section: doc Priority: optional Maintainer: Ubuntu Core Developers XSBC-Original-Maintainer: Debian Policy List Uploaders: Manoj Srivastava , Russ Allbery , Colin Watson , Bill Allombert Standards-Version: 3.8.1 Build-Depends-Indep: sgml-data (>= 2.0), debiandoc-sgml (>= 1.1.47), texlive, texlive-latex-extra, groff, bsdmainutils, pstoedit, jade, docbook-xml (>= 3.1.1), docbook-dsssl, tidy, links (>= 0.90) | elinks XS-Debian-Vcs-Browser: http://git.debian.org/?p=dbnpolicy/policy.git XS-Debian-Vcs-Git: git://git.debian.org/git/dbnpolicy/policy.git Vcs-Bzr: http://bazaar.launchpad.net/~ubuntu-core-dev/debian-policy/ubuntu Package: ubuntu-policy Architecture: all Suggests: doc-base Conflicts: dpkg-dev (<< 1.4.0.9), doc-base (<< 0.6), packaging-manual Replaces: packaging-manual Description: Debian Policy Manual and related documents This package contains: - Debian Policy Manual - Linux Filesystem Hierarchy Standard (FHS) - Authoritative list of virtual package names - Paper about libc6 migration - Policy checklist for upgrading your packages It also replaces the old Packaging Manual; most of the still-relevant content is now included as appendices to the Policy Manual. ubuntu-policy/debian/copyright0000644000175000017500000000444711175362266017336 0ustar cjwatsoncjwatsonThis is the Debian package of Debian Policy Manual, the Filesystem Hierarchy Standard, the Linux Filesystem Standard and related documents. It was originally assembled by Christian Schwarz and is now maintained by the Debian Policy Group . The FHS documents were downloaded from http://www.pathname.com/fhs/. ------------------------------------------------------------------------------ Copyright of the Debian Policy Manual: Copyright (C) 1996 Ian Jackson. This manual is free software; you may 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, or (at your option) any later version. This 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. You should have received a copy of the GNU General Public License with your Debian GNU/Linux system, in /usr/share/common-licenses/GPL-2, or with the dpkg source package as the file COPYING. If not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA ------------------------------------------------------------------------------ Copyright of the Filesystem Hierarchy Standard (FHS) Copyright © 1994-2004 Daniel Quinlan Copyright © 2001-2004 Paul 'Rusty' Russell Copyright © 2003-2004 Christopher Yeoh Permission is granted to make and distribute verbatim copies of this standard provided the copyright and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this standard under the conditions for verbatim copying, provided also that the title page is labeled as modified including a reference to the original standard, provided that information on retrieving the original standard is included, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this standard into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the copyright holder. ubuntu-policy/debian/changelog0000644000175000017500000032171011216715403017237 0ustar cjwatsoncjwatsonubuntu-policy (3.8.2.0ubuntu1) karmic; urgency=low * Resynchronise with Debian. Remaining changes: - Rebrand as "Ubuntu Policy Manual", preserving acknowledgements. - Document Ubuntu Maintainer field handling. - The Breaks field may safely be used in Ubuntu packages. - Document requirement to update the icon cache when installing files into subdirectories of /usr/share/icons. - Document the layout of the Ubuntu archive. - Describe Ubuntu version number conventions. - Document the changelog conventions for closing bugs in Launchpad, and the Launchpad-Bugs-Fixed .changes field. - Recommend that Standards-Version not be adjusted for Ubuntu revisions of this manual, and in general that Standards-Version should not be changed in Ubuntu for packages originating in Debian. - Recommend discussion on ubuntu-devel rather than debian-devel. - Document the special semantics of packages in the "metapackages" section. See: https://lists.ubuntu.com/archives/ubuntu-devel/2008-September/026523.html - Note that Maintainer field changes for Ubuntu do not generally need to be documented in debian/changelog. -- Colin Watson Fri, 19 Jun 2009 15:04:49 +0100 debian-policy (3.8.2.0) unstable; urgency=low [ Russ Allbery ] * Policy: Mandate debconf or equivalent for user prompting Wording: Andrew McMillan Seconded: Russ Allbery Seconded: Holger Levsen Seconded: Bill Allombert Seconded: Julien Cristau Closes: #206684 * Policy: Remove /etc/X11/XF86Config-4 FHS exception Wording: Julien Cristau Seconded: Russ Allbery Seconded: Bill Allombert Closes: #522219 * Policy: Remove obsolete /var/mail transition requirement Wording: Russ Allbery Seconded: Julien Cristau Seconded: Andrew McMillan Closes: #522364 * Policy: Move Speedo fonts into the deprecated category Wording: Julien Cristau Seconded: Russ Allbery Seconded: Julien Danjou Closes: #522218 * Housekeeping (resynchronizing lists maintained elsewhere): - Add GFDL 1.3 to the common-licenses list. - Update the list of archive sections. (Closes: #519835) * Set the release date of the 3.8.1 upgrading-checklist entry. (Closes: #519706) [ Colin Watson ] * The FHS is the "Filesystem Hierarchy Standard", regardless of our preferred spelling of "file system" elsewhere. Fix this and a nearby search-and-replace capitalisation bug. * Build-depend on texlive-latex-extra, which is needed by debiandoc2latexps and isn't included in texlive's dependencies. Closes: #533257 * Policy: State requirements for source package names Wording: Colin Watson Seconded: Russ Allbery Seconded: Julien Cristau Closes: #525151 * Add myself to Uploaders. [ Bill Allombert ] * Add myself to Uploaders. * Update Standards-Version to 3.8.1 (no changes required). * debian/rules: - use `dpkg --print-architecture' instead of obsolete form `dpkg --print-installation-architecture'. - fix a race condition while generating DEBIAN/md5sums. -- Bill Allombert Tue, 16 Jun 2009 21:42:53 +0200 ubuntu-policy (3.8.1.0ubuntu1) karmic; urgency=low * Resynchronise with Debian. Remaining changes: - Rebrand as "Ubuntu Policy Manual", preserving acknowledgements. - Document Ubuntu Maintainer field handling. - The Breaks field may safely be used in Ubuntu packages. - Document requirement to update the icon cache when installing files into subdirectories of /usr/share/icons. - Document the layout of the Ubuntu archive. - Describe Ubuntu version number conventions. - Document the changelog conventions for closing bugs in Launchpad, and the Launchpad-Bugs-Fixed .changes field. - Recommend that Standards-Version not be adjusted for Ubuntu revisions of this manual, and in general that Standards-Version should not be changed in Ubuntu for packages originating in Debian. - Recommend discussion on ubuntu-devel rather than debian-devel. - Document the special semantics of packages in the "metapackages" section. See: https://lists.ubuntu.com/archives/ubuntu-devel/2008-September/026523.html - Note that Maintainer field changes for Ubuntu do not generally need to be documented in debian/changelog. -- Colin Watson Mon, 27 Apr 2009 20:30:48 +0100 debian-policy (3.8.1.0) unstable; urgency=low * Policy: Clarify what "sensible behavior" is for init scripts Wording: Steve Langasek Seconded: Raphaël Hertzog Seconded: Russ Allbery Closes: #426877 * Policy: Remove alternative changelog formats from main manual Wording: Russ Allbery Seconded: Ben Pfaff Seconded: Guillem Jover Closes: #489460 * Policy: Mandate UTF-8 for changelog files Wording: Russ Allbery Seconded: Guillem Jover Seconded: Kurt Roeckx Closes: #241333 * Policy: Mandate UTF-8 for control files Wording: Russ Allbery Seconded: Kurt Roeckx Seconded: Raphaël Hertzog Closes: #143941 * Policy: New option in DEB_BUILD_OPTIONS to avoid running test-suites Wording: Russ Allbery Seconded: Guillem Jover Seconded: Raphaël Hertzog Closes: #416450 * Policy: Expand expected capabilities for local in /bin/sh scripts Wording: Russ Allbery Seconded: Guillem Jover Seconded: Raphaël Hertzog Closes: #473019 * Policy: Clarify Essential definition and caution when adding to it Wording: Russ Allbery Seconded: Jörg Sommer Seconded: Guillem Jover Closes: #479080 * Policy: Allow user mail spools to be mode 0600 or 0660 Wording: Russ Allbery Seconded: Kurt Roeckx Seconded: Andrew McMillan Closes: #470994 * Policy: Remove special handling of init scripts ending in .sh Wording: Kel Modderman Seconded: Russ Allbery Seconded: Henrique de Moraes Holschuh Closes: #513955 * Policy: /var/run and /var/lock may be volatile Wording: Colin Watson Seconded: Russ Allbery Seconded: Bill Allombert Closes: #514326 * Policy: debian/control allows comments starting with # Wording: Russ Allbery Seconded: Julien Cristau Seconded: Adeodato Simó Seconded: Guillem Jover Closes: #446712 * Improve the documentation of maintainer script actions for diversions in the informative appendix to allow for addition of a new diversion on upgrade and handle error cases correctly. Thanks to Olivier Berger for the report and Raphaël Hertzog for the review. (Closes: #483418) * Clarify the meaning of architecture restrictions on build dependencies in the presence of alternatives. Thanks to Guillem Jover for the explanation and review and Emilio Pozuelo Monfort and Don Armstrong for wording review. (Closes: #163666) * Change the term "category" to "archive area" when referring to main, contrib, and non-free. This is closer to the wording of the Social Contract. (Closes: #473439) * Use : notation rather than . notation in multiple places. Thanks, Kurt Roeckx. (Closes: #488039) * Fix typo in 3.8.0.0 upgrading-checklist entry. Patch from Kobayashi Noritada. (Closes: #487701) * Mention debugging packages as an explicit example of packages with extra priority. Thanks, Charles Plessy. (Closes: #491985) * Clarify that translation is only required for user-visible debconf messages. Capitalize "Debian Configuration Management Specification" uniformly. Thanks, Julian Andres Klode. (Closes: #492624) * Add --wildcards to the sample tar command in appendix B.1 for extracting the package copyright file, adjusting for new tar option behavior. Thanks, Yan Morin. (Closes: #503685) * Reword the requirement that maintainer scripts exit with a zero status on success to avoid double-negatives. * Include the full name of each menu category rather than only the portion relative to the parent heading to be clearer in long category lists. Thanks, Christoph Berg. (Closes: #511804) * Build-Depend on texlive rather than tetex-extra. texlive appears to be sufficient for how Policy uses debiandoc-sgml and pulls in far fewer packages. * Remove the postinst and prerm scripts. doc-base registration is now handled by triggers and no longer required and removal of /usr/doc links was completed long ago. * Reference GPL-2 rather than the GPL symlink in debian/copyright. -- Russ Allbery Wed, 11 Mar 2009 20:50:52 -0700 ubuntu-policy (3.8.0.1ubuntu4) intrepid; urgency=low [ Matt Zimmerman ] * Note that Maintainer field changes for Ubuntu do not generally need to be documented in debian/changelog. -- Colin Watson Sun, 19 Oct 2008 09:08:38 +0100 ubuntu-policy (3.8.0.1ubuntu3) intrepid; urgency=low * Recommend discussion on ubuntu-devel rather than debian-devel. * Document the special semantics of packages in the "metapackages" section. See: https://lists.ubuntu.com/archives/ubuntu-devel/2008-September/026523.html -- Colin Watson Mon, 22 Sep 2008 12:24:59 +0100 ubuntu-policy (3.8.0.1ubuntu2) intrepid; urgency=low * Rename to ubuntu-policy so that the original debian-policy can remain in the archive. This involves some slightly awkward document name changes, since this package ships files in /usr/share/doc-base/ as well as the actual documentation and we'd rather not have to conflict. * Set Vcs-Bzr for Ubuntu. -- Colin Watson Mon, 08 Sep 2008 15:32:02 +0100 debian-policy (3.8.0.1ubuntu1) intrepid; urgency=low * Rebrand as "Ubuntu Policy Manual", preserving acknowledgements. * Document Ubuntu Maintainer field handling. * The Breaks field may safely be used in Ubuntu packages. * Document requirement to update the icon cache when installing files into subdirectories of /usr/share/icons. * Document the layout of the Ubuntu archive. * Describe Ubuntu version number conventions. * Document the changelog conventions for closing bugs in Launchpad, and the Launchpad-Bugs-Fixed .changes field. * Recommend that Standards-Version not be adjusted for Ubuntu revisions of this manual, and in general that Standards-Version should not be changed in Ubuntu for packages originating in Debian. * Note that /var/run is a tmpfs in Ubuntu and that init.d scripts must therefore create subdirectories of /var/run dynamically. -- Colin Watson Fri, 22 Aug 2008 18:14:50 +0100 debian-policy (3.8.0.1) unstable; urgency=low * Don't attempt to register the non-existent debian-policy-process document. Thanks, Adrian von Bidder. (Closes: #484706) -- Russ Allbery Thu, 05 Jun 2008 13:13:01 -0700 debian-policy (3.8.0.0) unstable; urgency=low * Bug fix: "[PROPOSAL] "debian/README.source" file for packages with non-trivial source", thanks to Wouter Verhelst, Jörg Sommer, Colin Watson, and Junichi Uekawa (Closes: #250202). * Bug fix: "[AMENDMENT 11/02/2008] Manual page encoding", thanks to Colin Watson (Closes: #440420). * Bug fix: "[PROPOSAL] common interface for parallel building in DEB_BUILD_OPTIONS", thanks to Loïc Minier, Peter Samuelson, and Robert Millan (Closes: #209008). * Bug fix: "Please clarify splitting/syntax of DEB_BUILD_OPTIONS", thanks to Loïc Minier, Peter Samuelson, Robert Millan, and Guillem Jover (Closes: #430649). * Bug fix: "Documentation for Breaks in dpkg", thanks to Ian Jackson (Closes: #379150). * Bug fix: "support for wrapped Uploaders should now be mandatory" (Closes: #431813). * Bug fix: "[PROPOSAL] Add should not embed code from other packages", thanks to Neil McGovern, Colin Watson, Bill Allombert, Steve Langasek, Kurt Roeckx, and others (Closes: #392362). * Bug fix: "Homepage field in debian/control undocumented", thanks to Mario Iseli (Closes: #452105). * Bug fix: "Policy inconsistent with reality: base subsection no longer used", thanks to Magnus Holmgren, Bernd Zeimetz, and Colin Watson (Closes: #442070). * Bug fix: "Inclusion of Apache Software License versions in /usr/share/common-licenses", thanks to Barry Hawkins (Closes: #291460). * Bug fix: "[Amended] copyright should include notice if a package is not a part of Debian distribution", thanks to Taketoshi Sano (Closes: #65577). * Bug fix: "scripts as configuration files: should vs. must", thanks to Frank Küster (Closes: #403391). * Bug fix: "debconf specification should allow underscores in template names", thanks to Colin Watson (Closes: #473761). * Bug fix: "clarify handling of run-time and compile-time support programs", thanks to Goswin Brederlow and Raphael Hertzog (Closes: #367984). * Policy: better document version ranking and empty Debian revisions Wording: Russ Allbery Seconded: Raphaël Hertzog Seconded: Manoj Srivastava Seconded: Guillem Jover Closes: #186700, #458910 * Policy: remove obsolete app-defaults and Xresources provisions Wording: Julien Cristau Seconded: Russ Allbery Closes: #480551 * Bug fix: "Examples of dpkg frontends should mention apt now", thanks to Josh Triplett (Closes: #455602). * Bug fix: "Minor typos and wording suggestions", thanks to Michael Tautschnig (Closes: #422552). * Bug fix: "substvar reference moved from dpkg-source(1) to deb-substvars(5)", thanks to Ian Beckwith (Closes: #475731). * Policy: bugs fixed in NMUs are now closed rather than marked fixed Wording: Russ Allbery (thanks, Sandro Tosi) Closes: #481640 * Policy: C.1.4, C.1.8: minor typos Wording: Sandro Tosi Closes: #481954 * Remove the now-obsolete policy-process document. * Add an md5sums control file. * Add Vcs-Browser and Vcs-Git control fields. * Remove build system support for FHS 2.1 and FSSTND, mostly commented out. * Remove more temporary files created by the build. * Remove the FSSTND license from debian/copyright; no FSSTND files are currently part of policy. * Update FHS copyright dates in debian/copyright. * Standardize the spacing around headings in upgrading-checklist.html. * Remove old ChangeLog files and metadata headers in maintainer scripts and debian/rules. -- Russ Allbery Wed, 04 Jun 2008 15:53:27 -0700 debian-policy (3.7.3.0) unstable; urgency=low * Bug fix: "FTBFS if built twice in a row" (Closes: #424212). * Bug fix: "[PROPOSAL] Document ~ behavior in version numbers", thanks to Nicolas François and Marc Brockschmidt (Closes: #382612). * Bug fix: "Please add 'local' to list of supra-POSIX features that /bin/sh can be expected to offer". Also add test -a/-o binary logical operators and change references from POSIX to SUSv3 (Closes: #294962). * Bug fix: "[Proposal] new Debian menu structure", thanks to Bill Allombert (Closes: #361418). * Bug fix: "typo: "must not be not world-writable"", thanks to Sam Hocevar (Closes: #392594). * Bug fix: "debian-policy: recommend binary:Version substvar instead", thanks to Guillem Jover (Closes: #418444). * Bug fix: "New virtual package: dictd-dictionary", thanks to Tatsuya Kinoshita (Closes: #413575). * The virtual package in use is inet-superserver, not inetd-superserver. Adjust the virtual package list to match. Thanks, Tatsuya Kinoshita and Marco d'Itri. * Wrapped, cleaned up trailing whitespace, and alphabetized the list of virtual packages. * Bug fix: "Small spelling errors and erratic sentences in debian-policy", thanks to Michiel de Boer. (Closes: #435207). * Bug fix: "Source field of .changes files may contain a version number" (Closes: #431813). * Bug fix: "822-date is deprecated (use date -R instead)" (Closes: #448035). * Bug fix: "5.6.17 (Urgency) should list emergency, maybe a normative list?" (Closes: #412634). * Bug fix: "[PROPOSAL] Document support of package types in shlibs files", thanks to Franz Pop and Raphaël Hertzog (Closes: #363133). * Bug fix: "Introduce a requirement for internationalisation of debconf templates", thanks to Christian Perrier (Closes: #402975). * Bug fix: "GFDL is now in common-licenses". Also add the rest of the specific license versions and the GPLv3 (Closes: #420701). * Bug fix: "Virtual package for Japanese font packages (ttf-japanese-mincho and ttf-japanese-gothic)", thanks to Nobuhiro Iwamatsu (Closes: #440931). * Drop unsupported docbook-xml format from the doc-base file for the debconf specification. * Remove inactive uploaders and add Russ Allbery. * Update Standards-Version to 3.7.3 (no changes required). -- Russ Allbery Sun, 02 Dec 2007 22:33:55 -0800 debian-policy (3.7.2.2) unstable; urgency=low * Bug fix: "clarify 12.3 Additional documentation", thanks to Peter Eisentraut (Closes: #367697). * Bug fix: "debian-policy: s/dependcy/dependency/", thanks to Justin Pryzby (Closes: #375508). * Bug fix: "various spelling mistakes", thanks to Nico Golde (Closes: #375728). * Bug fix: "debian-policy: typo", thanks to Peter Samuelson (Closes: #376104). * Bug fix: "debian-policy: [PROPOSAL] maintainer scripts must not be world writable", thanks to Kari Pahula (Closes: #376438). * Bug fix: "policy-process: s/ a a / a /; s/peoples/people's/; s/intiated/initiated/; s/participattion the/participation in the/? add quotes; s/was a larger/a larger/?", thanks to Justin Pryzby (Closes: #377215). * Bug fix: "[PROPOSAL] Include the GFDL in the set shipped in /usr/share/common-licenses", thanks to Adeodato Simó. However, it is premature to tell packages to use the common licenses file until we actually ship the license in /usr/share/common-licenses/ (Closes: #378386). * Bug fix: "circular dependencies, improved guarantees", thanks to Ian Jackson (Closes: #379630). * Bug fix: "section on invoke-rc.d doesn't make sense", thanks to Peter Eisentraut (Closes: #380692). * Bug fix: "policy: postinst doesn't document typical abort-remove case", thanks to Justin Pryzby. Removed all such comments. This is not the place to document such material. (Closes: #373212). * Bug fix: "use of "invoke-rc.d $PACKAGE stop || exit $?" in prerm scripts", thanks to Lars Wirzenius (Closes: #370471). * Bug fix: "debian-policy: Inconsistent requirements wrt bashisms", thanks to Frank Küster (Closes: #367531). * Bug fix: "debian-policy: s/with With/with /", thanks to Justin Pryzby (Closes: #379974). * Bug fix: "debian-policy: "$RET" not "RET"", thanks to Justin Pryzby (Closes: #386178). * Bug fix: "debian-policy: Spelling error in chapter 9.1.1: exceptiions", thanks to Andreas Janssen (Closes: #388302). * Bug fix: "[PROPOSAL] Document ~ behavior in version numbers", thanks to Jakob Bohm (Closes: #382612). * Bug fix: "debian-policy: [ACCEPTED] Request for the 'stardict'", thanks to Andrew Lee (Closes: #385935). * Bug fix: "[ACCEPTED] virtual package 'lzh-archiver' -- an LZH archiver package", thanks to Ying-Chun Liu (PaulLiu) (Closes: #387027). -- Manoj Srivastava Mon, 2 Oct 2006 17:31:23 -0500 debian-policy (3.7.2.1) unstable; urgency=low * Bug fix: "debian-policy: s/control are/&a/; s/stats/status/; s/and/an/; s/'/"/; s/rewind/unwind/; s/fact/& that/; s/like like/look like/;", thanks to Justin Pryzby (Closes: #372147). * Bug fix: "debian-policy: Minor typo in footnote 53", thanks to Jordà Polo (Closes: #372497). * Bug fix: "debian-policy: Typo in 9.1.1: "'..' character" should be "'.' character"", thanks to Matt Zagrabelny (Closes: #372522). * Bug fix: "debian-policy: More typos in upgrading-checklist.txt", thanks to Kevin B. McCarty (Closes: #366466). * Bug fix: "typo: package remains in and "Installed' state", thanks to Sam Hocevar \(Debian packages\) (Closes: #369413). * Bug fix: "debian-policy: Cleanup build-dependencies", thanks to Stefan Huehner (Closes: #366032). * Bug fix: "debian-policy: 2.2 should be named 'categories'", thanks to Thomas Weber (Closes: #369912). * Bug fix: "debian-policy: old postinst abort-upgrade, not new", thanks to Justin Pryzby. The fix was thanks to Margarita Manterola (Closes: #372148). * Bug fix: "policy: please say which control fields can line-wrap", thanks to Peter Samuelson (Closes: #372731). * Bug fix: "debian/copyright should be mentioned in source section", thanks to Ian Jackson (Closes: #369011). * Bug fix: "GNU office not on Temple Place anymore", thanks to Dan Jacobson (Closes: #366889). -- Manoj Srivastava Tue, 20 Jun 2006 00:18:19 -0500 debian-policy (3.7.2.0) unstable; urgency=low * Revert the cgi-lib change. * Bug fix: "Clarification for difference between Build-Depends and Build-Depends-Indep (Section 7.6)", thanks to Christoph Berg Note that this is not part of policy, just an informative footnote. (Closes: #328951). * Bug fix: "debian-policy: Typo in policy 5.6.3: semantic meaning", thanks to Thijs Kinkhorst (Closes: #365907). -- Manoj Srivastava Wed, 3 May 2006 18:07:19 -0500 debian-policy (3.7.1.0) unstable; urgency=low * Bug fix: "[PROPOSAL] 11.9: document handling of directories permission when upgrading", thanks to Bill Allombert (Closes: #136318). * Bug fix: "[DISCUSS] documentation of the "-fPIC" constraint", thanks to Loïc Minier. Clarified when it may be reasonable to violate the standard directive that shared libraries must be compiled with -fPIC, and static libraries without, added the protocol to be followed when doing so. (Closes: #329762). * Bug fix: "Minor typo in upgrading checklist", thanks to David Weinehall (Closes: #364982). * Bug fix: "Typo in upgrading-checklist", thanks to David Weinehall (Closes: #364983). * Bug fix: "typo in debian policy section 10.9.1", thanks to Miguel Gea Milvaques (Closes: #365058). * Bug fix: "debian-policy: The section 11.8.5 needs some clarifications", thanks to Robert Luberda (Closes: #365356). * Bug fix: "11.8.7: X11R7 puts headers in /usr/include/X11", thanks to Drew Parsons (Closes: #365510). * Bug fix: "debian-policy: typo in policy-process: "Guideliens"", thanks to Lars Wirzenius (Closes: #360518). * Bug fix: "debian-policy: repeated word in section 10.4", thanks to Russ Allbery (Closes: #364985). * Bug fix: "typo in debian-policy", thanks to Miguel Gea Milvaques (Closes: #365323). -- Manoj Srivastava Wed, 3 May 2006 11:17:42 -0500 debian-policy (3.7.0.0) unstable; urgency=low * Bug fix: "[PENDING AMENDMENT 20/01/2000] Splitting cgi-bin", thanks to Brian White. (Closes: #32263). * Bug fix: "debian-policy: [PROPOSAL] Should update to Filesystem Hierarchy Standard FHS 2.3", thanks to Tobias Burnus (Closes: #230217, #212434, #344158). * Bug fix: "[AMENDMENT 11/04/2006] Permit multi-line fields in debian/control", thanks to John R. Daily. Mention that all fields, except the Uploaders, are supposed to be a single logical line, which may be spread over multiple physical lines (newline followed by space is elided). Also mention that anything parsing the control file must allow for a multi-line uploaders field. (Closes: #148194). * Bug fix: "[AMENDMENT 12/04/2004] frown on programs in PATH with language extentions", thanks to Joey Hess. (Closes: #190753). * Bug fix: "init script stop example should use --oknodo", thanks to Matt Kraai. Removed the example entirely. (Closes: #346598). * Bug fix: "policy 12.5: Please recommend a sane practice WRT different gpl versions (was: Re: RFC/RFS: beef - a flexible BrainFuck interpreter)", thanks to Justin Pryzby. The subject leaves something to be desired, but polic should not attempt to enumerate all common licenses. (Closes: #355263). * Bug fix: "debian-policy: Conflicting Architecture definitions", thanks to Hans Ulrich Niedermann. Punt to dpkg-architecture to providing legal architecture strings, since that's what is used by everyone anyway. The version in policy was wrong, but that s=does not seem to have hindered anyone, which indicates that this policy directive was uneeded. Now the dpkg-architecture list is deemed authoritative, which it is, but the format for the string is defined by policy, and the current list of architecture strings is in an informative foot note. (Closes: #357613). * Bug fix: "[AMENDMENT 06/04/2006] Make use of invoke-rc.d, if available, mandatory", thanks to Lars Wirzenius. (Closes: #361137). * Bug fix: "no longer current regarding X font paths", thanks to Joey Hess (Closes: #362247). * Bug fix: "debian-policy: please prohibit circular dependencies, or mention that dependencies won't be respected during prerm remove", thanks to Justin Pryzby. Well, we did not prohibit circular dependencies. But we do now have a warning that In case of circular dependencies, since installation or removal order honoring the dependency order can't be established, dependency loops are broken at some random point, and some packages may not be able to rely on their dependencies being present when being installed or removed, depending on which side of the break of the circular dependcy loop they happen to be on. (Closes: #362975). * Bug fix: "8.6.4. Providing a `shlibs' file: s/should create/must provide/", thanks to Christoph Berg. Clarified the wording. (Closes: #341232). * Bug fix: "debian-policy: Chapter 6 - Package maintainer scripts: redundant info about exit status", thanks to Daniel Bonniot (Closes: #349010). * Bug fix: "debian-policy: Refers to upgrading-checklist.txt instead of upgrading-checklist.txt.gz", thanks to Matt Kraai (Closes: #349775). * Bug fix: "debian-policy: dpkg-gencontrol now uses -isp by default", thanks to Guillem Jover (Closes: #359817). * Bug fix: "[PROPOSAL] unclear recommendation for debconf w/ dpkg-statoverride", thanks to Eduard Bloch (Closes: #199849). * debian-policy: please support Watch file as recommendation, thanks to Bluefuture (Closes: #342611). * Bug fix: "[PROPOSED] Mandate http servers to provide httpd-cgi as relevenat", thanks to Uwe Hermann. This is already supported by the http servers out there. (Closes: #117916). -- Manoj Srivastava Tue, 25 Apr 2006 23:56:16 -0500 debian-policy (3.6.2.2) unstable; urgency=low [ Manoj ] * Bug fix: "policy is out of date re tasks and tasksel", thanks to Joey Hess. Removed the section from policy. (Closes: #344310). * Bug fix: "debian-policy: Please remove virtual package cron-daemon", thanks to Steve Greenland (Closes: #257726). * Bug fix: "debian-policy: incorrect tar example deb manipulation", thanks to Bob Proulx (Closes: #224770). * Bug fix: "Probable typo in 10.1 install -s miss INSTALL =", thanks to Bill Allombert (Closes: #341992). * Bug fix: "debian-policy: postinst abort-remove (6.7) not present in summary (6.4)", thanks to Ferenc Wagner (Closes: #338493). * Bug fix: "UTF-8 footnote is out of date (pre-sarge)", thanks to Martin Michlmayr (Closes: #337539). * Bug fix: "debian-policy: Typo in perl-policy", thanks to Tibor Csögör (Closes: #334913). * Bug fix: "debian-policy: Outdated FSF postal address in Copyright Notice", thanks to Jean-Marc Ranger (Closes: #334819). * Bug fix: "debian-policy: §6.5 (3)(1): missing "Error unwind:" for "new-postrm abort-upgrade"", thanks to Henning Makholm (Closes: #321792). * Bug fix: "debian-policy: typo in §5.6.3: co-maintaintainers", thanks to Henning Makholm (Closes: #321790). * Bug fix: "debian-policy: typos in sect 9.3.1: "ends .sh", "rather that"", thanks to Thijs Kinkhorst (Closes: #343933). * Bug fix: "debian-policy: Unclear wording of ldconfig requirements in section 8.1.1", thanks to Ben Finney (Closes: #318214). * Bug fix: "debian-policy: Typo in 8.6.2: ${shlib:Depends} must be ${shlibs:Depends}", thanks to Thijs Kinkhorst (Closes: #318147). * Bug fix: "debian-policy: gzipped fhs-2.3 documentation is corrupt", thanks to Gabor Gombas (Closes: #340189). * Bug fix: "Section 6.3 should reference 3.10.1", thanks to Marc 'HE' Brockschmidt (Closes: #326633). * Bug fix: "debian-policy: section 2.2 refers to no-longer existant non-US repository sections", thanks to Martin-Eric Racine (Closes: #315470). -- Manoj Srivastava Sun, 25 Dec 2005 08:47:52 -0600 debian-policy (3.6.2.1) unstable; urgency=low * Bug fix: "debian-policy: Typo in upgrading-checklist.txt.gz", thanks to Romain Francoise. Added the missing /. (Closes: #314569). * Bug fix: "x-session-manager already in use, so please add to virtual-package-names-list.txt", thanks to Christopher Martin (Closes: #313626). * Bug fix: "[ACCEPTED] SRFI 22 names for Scheme implementations", thanks to Jorgen Schaefer (Closes: #310113). * Bug fix: "debian-policy: please add x-display-manager to virtual-package-names-list.txt", thanks to Jon Dowland (Closes: #294633). -- Manoj Srivastava Sat, 18 Jun 2005 00:48:14 -0500 debian-policy (3.6.2.0) unstable; urgency=low Manoj: * Bug fix: "policy 11.5.3 refers to using the menu package to register docs", thanks to Joey Hess (Closes: #222553). * Bug fix: "[PROPOSAL] Document Uploaders: field in policy", thanks to Andrew Pollock. Andreas Metzler provided the wording, though it was modified during inclusion. (Closes: #203145). * Bug fix: "debian-policy: Minor grammatical correction in section 9.4", thanks to Eric Evans. I rejected the proposed change, instead I went over the whole policy document and removed all he/she/him/her constructs before the gender police jump all over me. (Closes: #273122). * Bug fix: "XSI:ism in prerm and postinst", thanks to David Weinehall (Closes: #260092). * Bug fix: "debian-policy: please clarify section 12.7.", thanks to Adrian Bunk. Added a clarifying footnote that makes it clear that section 12.3 does not allow one to ignore section 12.7 (Closes: #276953). * * Bug fix: "debian-policy: should not ship generated files in source archive, and should clean them from the tree", thanks to Branden Robinson (Closes: #284967). * Bug fix: "debian-policy: Detailed description of maintainer script calls (Section 6.5) is incomplete", thanks to Nikolaus Schulz and Thomas Hood. What happens when error unwinding itself runs into problems is perhaps not discussed as completely as it should be. (Closes: #286549). * Bug fix: "9.3.3.2 "command -v" example needs tweaking", thanks to Thomas Hood. Instead of the massively complex shenanigans suggested in the bug report, just use which. which lives in an essential package, so can be used in the preinst of packages. (Closes: #291026). * Bug fix: "debian-policy: please clarify/loosen the policy on rewriting history", thanks to Frank Küster. Since this was not really a directive, but merely an expression of an opinion, moved it into an informative footnote. (Closes: #290270). * Bug fix: "debian-policy: virtual package request: mpd-client", thanks to Eric Wong (Closes: #270020). * Bug fix: "[ACCEPTED 2005/02/04]: "libexec", or use of "lib" for binaries in lib* packages", thanks to Junichi Uekawa (Closes: #146023). * Bug fix: "debian-policy: virtual package: flexmem", thanks to Bartosz Fenski aka fEnIo (Closes: #239359). * Bug fix: "Please clarify Section 2.5. required <-> essential", thanks to Adrian Bunk. Clarified the section. (Closes: #216104). * Bug fix: "debian-policy: Please remove virtual package aspell-dictionary", thanks to Brian Nelson (Closes: #295939). * Bug fix: "[AMENDMENT 18/02/2002] Where to place web-accessible images", thanks to Tollef Fog Heen (Closes: #89867). * Bug fix: "debian-policy: erroneous enumeration in prebuilt policy.* files", thanks to Nikolaus Schulz. I am hoping that this shall go away when we rebuild. (Closes: #286553). * Bug fix: "please make names of alternate versions links", thanks to Robert Cheramy. Added HTTPPATH elements that should provide the URL's as well as the hyperlinks. (Closes: #308886). * Bug fix: "www.debian.org: Misspelling in Policy Manual", thanks to Roberto C. Sanchez Various spelling errors were also corrected in a spell check run. (Closes: #309162). -- Manoj Srivastava Thu, 16 Jun 2005 20:27:17 -0500 debian-policy (3.6.1.1) unstable; urgency=low Manoj: * [AMENDMENT 15/09/2003] Move documentation of behavior of ancient dpkg in 6.6 to a footnote. closes: Bug#209855 * Fix the outdated link for the mime subpolicy. closes: Bug#212153 * Fix a missing comma in the list of sections closes: Bug#215524 * Fix spelling of sysv-rc closes: Bug#215558 * [AMENDMENT 28/03/2004] ${perl:Depends} documentation incomplete. Added an informative foot note stating that dependencies caused by versioned uses and on separately packaged modules are not included in this variable and must be explicitly included. closes: Bug#202054 * Clarified that section 3.2.1 refers to the date based postion of the version number, if not already clear from the context. This allows developers leeway in selecting date based version numbers for their packages, without loosing the advantages of the format specified in this section. closes: Bug#248618 * Bug fix: "Broken link to virtual-package-names-list.txt in section 3.6", thanks to Carlos O'Donell (Closes: #248786). * Bug fix: "Broken link to debconf_specification.txt.gz in section 3.10.1 of the Debian Policy manual.", thanks to Carlos O'Donell and Scott C.MacCallum (Closes: #248788, 247761). * Bug fix: "missing commas in subsections list", thanks to Filippo Giunchedi (Closes: #236614). * Bug fix: "debian-policy: policy-process, broken URL", thanks to Manoj Srivastava (Closes: #244969). * Bug fix: "bad reference to debconf-devel(8) has to be (7)", thanks to Kevin Price (Closes: #247143). * Bug fix: "debian-policy: Small wording change", thanks to Mike Paul (Closes: #252392). * Bug fix: "debian-policy: broken URL: CSH Programming Considered Harmful", thanks to Steven Augart (Closes: #253324). * Bug fix: "New virtual package: cron-daemon", thanks to Adam Byrtek (Closes: #252086). Josip: * Fixed detection of invoke-rc.d's existence, closes: #218530. * Generalized the dpkg-shlibdeps example and added a current example in a footnote, set proper section ids and linked the d-sd section better, closes: #50565. * Clarified the section about the Architecture field and added footnotes to indicate recommended actions, closes: #51832. * Updated PGP references, closes: #68827. * Linked f-Format in the list of fields of the .dsc file, not mandatory according to my skimming of dpkg-source, closes: #70742. * Fixed the command line required to output the copyright file, closes: #75508. * Removed the long obsolete notion of specific directory names within source tarballs, closes: #79210. Andi: * sgml-dtd was moved, fix FTBFS. Closes: #241683 * fix link to WM specification. Closes: #235484 * manpage -> man page. Closes: #232364, #238958 * language adjustment. Closes: #227762 * added virtual packages stardict-dictionary, inetd-superserver. Closes: #185943, #237049 -- Manoj Srivastava Fri, 25 Jun 2004 16:07:38 -0500 debian-policy (3.6.1.0) unstable; urgency=low Josip: * Removed obsolete section on obsolete constructs and libraries, closes: #193748. Manoj: * Change reference to the debconf introduction from kitenet to a debian hosted server. closes: Bug#187297 * Added myspell-dictionary to the virtual packages list closes: Bug#203728 * Fix the restart action in the init.d/bind example; it now uses --oknodo so that the action does not fail when the service is not running. closes: Bug#187250 * invoke-rc.d and update-rc.d are now in the sysv-rc package instead of the sysvinit package. Fixed a reference in policy. closes: Bug#200440 * Note that postinst abort-remove is called if there is an error while removing the package. closes: Bug#188030 * [AMENDMENT 2003/08/03] Make Debconf the standard for prompting the user closes: Bug#176506 -- Manoj Srivastava Tue, 19 Aug 2003 07:28:10 -0500 debian-policy (3.6.0) unstable; urgency=low Josip: * Restructured Policy, closes: #189306. + Many packaging manual appendices that were integrated into policy sections are now empty, and replaced with links to the Policy. In particular, the appendices that included the list of control fields were updated (new fields like Closes, Changed-By were added) and the list of fields for each of control, .changes and .dsc files is now in Policy, and they're marked mandatory, recommended or optional based on the current practice and the behaviour of the deb-building toolchain. + Elimination of needlessly deep section levels, primarily in the chapter Debian Archive, from which two new chapters were split out, Binary packages and Source packages. What remained was reordered properly, that is, some sect1s became sects etc. + Several sections that were redundant, crufty or simply not designed with any sort of vision, were rearranged according to the formula that everything should be either in the same place or properly interlinked. Some things remained split up between different chapters when they talked about different aspects of files: their content, their syntax, and their placement in the file system. In particular, see the new sections about changelog files. Manoj: * Added Games/Simulation to menu subpolicy closes: Bug#194974 * Added Apps/Education to menu subpolicy closes: Bug#194972 * [ACCEPTED]: Debian changelogs should be UTF-8 encoded. Changed the wording from a should to a may; since a should would make an unknown number of packages insta buggy. A reuest makes all these wishlist bugs; we can raise the severity in a later version of policy. closes: Bug#174982 * Added LANG=C before the debiandoc2X invocations, this ensures that the resulting documents do not get converted to the locale on the building machine. This answers some of the issues mentioned in Bug#175064 * [AMENDMENT 02/05/2003] encourage packagers to systematically prevent mis-linked libraries closes: Bug#191369 * [AMENDMENT 6/6/2003] build-depends-indep need not be satisfied during clean target. closes: Bug#191411, Bug#178809 * Fixed the fact that section 7.5.1 does not describe dpkg's true behavior. Now added a footnote that explains that replaces is a one way relationship. closes: Bug#183195 * Could no longer find the misspelling "seciton", thus this must have been fixed in a previous change in the manual. closes: Bug#193903 * Fixed an incorect /usr/share/common-licences/GPL reference, ensured a consistent spelling across the manuals. closes: Bug#189516 * Removed an extraneous > in menu policy. closes: Bug#187615 * Fixed typos, and part of the report that was deemed valid; the other changes suggested were incorrect, or style issues. closes: Bug#169744 * updated the section numbers in the upgrading checklist for the restructuring -- Josip Rodin Wed, 9 Jul 2003 18:01:35 +0200 debian-policy (3.5.10.0) unstable; urgency=low Josip: * Fixed date, typos and added indentation in the virtual packages list, closes: #182792. * Changed the formatting of the link to the authors section to avoid confusion in the debiandoc2txt output, closes: #185985. * Fixed various typos, closes: #189274, #187418, #187422, #189654. * Removed broken link to csh.whynot on CPAN, closes: #187567. * Updated archive section list, closes: #187420. * Stop attaching byhand tarballs, cf. bug #184082. Manoj: * Clarify x-terminal-emulator virtual package eligibility, in an extention to an informative footnote. closes: Bug#165063 * Add 40 points, not 20, when the window manager is compliant with "The Window Manager Specification Project". closes: Bug#167004 * Fixed reference to the debconf URL (we can change the URL as it changes again, and I don't think any additional load would accrue since people using the old URL were redirected to auric anyway). closes: Bug#184518 * Inserted the word only in the package name section. closes: Bug#184368 * Amended the section about Prompting in maintainer scripts. Added a footnote (quoting from the Jargon File) to explain what "by hand" means in a computer context. closes: Bug#184507 -- Josip Rodin Sat, 10 May 2003 19:13:50 +0200 debian-policy (3.5.9.0) unstable; urgency=low Josip: * Added missing bits of information about Description: fields from the old Packaging manual, closes: #172022 * Fixed a stale reference to the "base system maintainer" to base-passwd maintainer, closes: #174927 * Fixed an accidental change from /usr/share/package to /usr/share/doc in the paragraph about not depending on /usr/share/doc/package, closes: #174048 * Fixed several errors reported by Guenther Palfinger, with some help from Richard Braakman, closes: #177205, #177206, #177207, #177208, #177209 * Added versions to links and docbook-xml source-dependencies, hopefully fixes the bug with potato, and even if it doesn't, I don't care :) closes: #103459 * Fixed typos in the debconf spec noticed by Jay Bonci, closes: #178455 * Clarified that using Build-Depends for build-dependencies is not a "may" but a "should", added proper linking among various sections dealing with the dependencies so that there is no confusion, closes: #87510 If any one of those poor, misguided people ;) still thinks that the requirement should be a "must" (in _our_ meaning, not RFC "MUST"), please file a new bug, as it's quite unproductive to have to sift through a 152-page bug log which mostly goes back-and-forth with explanations how policy should work, occasionally sprinkled with offtopic stuff, too. * When asked to restart a service that isn't already running, the init script should start it, closes: #60979 * Rephrased section on configuration files to remove confusing use of "should", closes: #170019 * Rearranged the shared library information properly, closes: #109166 This change also centralizes the info on how to ship static libraries in one place (hopefully not too ambiguous), closes: #93975 * Allow examples to be placed in /usr/share/doc/package/ in packages that are meant to provide examples, closes: #69864 * Removed several references to the Policy manual etc in the stuff imported from old packaging manual, closes: #181923 * Fixed too greedy wildcard match in the logrotate example, closes: #183544 -- Manoj Srivastava Fri, 7 Mar 2003 12:35:16 -0600 debian-policy (3.5.8.0) unstable; urgency=low Manoj * Added example for why one may call ldconfig anywhere in the postsint. closes: Bug#120585 * Add the modifications about base system, as opposed to the soon to be obsolete base section (I assume it is) closes: Bug#53582 * Rearranged the virtual packages list. closes: Bug#72980 * This is basically an attempt to ratify the current practice of using debhelper in the clean target. Currently, policy does not require debhelper to be installed when the clean target is run, even though it is in the build-depends field. This was a simple oversight. closes: Bug#164035 * No longer depend on fileutils. closes: Bug#167425 * Added the Apps/Science menu section closes: Bug#162812 * Applied text patch from Joey Hess to the debconf spec simply make it conform to the reality of how some things work now. This is part of an effort to make debconf and cdebconf better substitutes for each other. Since it was not an XML patch, no special markup is present in the new content, except where I made guesses. closes: Bug#160776 * Clarify section 13.3. closes: Bug#160248 * Removed the undocumented(7) hack requirement. closes: Bug#39830 Josip * Removed the obsolete notion of documenting changes within the copyright file, closes: Bug#65764 -- Manoj Srivastava Fri, 15 Nov 2002 00:36:54 -0600 debian-policy (3.5.7.1) unstable; urgency=low * Fix the debconf spec to (postinst -> postrm) closes: Bug#129375, Bug#160839 * Fix update-rc.d example, mention that changing run-levels or priority may require removing and re-creating the symbolic links. closes: Bug#149709 * Fix the groff and col -b interaction closes: Bug#164755 * Added section numbers to upgrading checklist closes: Bug#160914 * Fixed typo KB_Backspace -> KB_BackSpace * Clarify wording in the section about ChangeLog files to allow for symbolic links in /usr/share/doc/ directory (was already allowed in a previous section of policy 13.6) closes: Bug#111137 * Removed a spurious + from text. closes: Bug#160908 * Added a note in the debconf spec to consult debconf-devel(8) for details. closes: Bug#133030 * Added a reference to the local copy of the FHS. closes: Bug#122928 * Updated reference to ash (dash). This implements the non controversial parts of Bug#161455. -- Manoj Srivastava Sat, 26 Oct 2002 13:12:49 -0500 debian-policy (3.5.7.0) unstable; urgency=low * Fixed some broken hrefs in links * No longer use local debiandoc stuff (it's been fixed upstream) * Added table of contents (index.html) to policy-process.sgml, fixing the new error reported to bug #137521 closes: Bug#137521 * Fixed a couple of typos closes: Bug#139832 * Ran through the policy document looking for long instances of text in the tag, and changed it to where appropriate. This is since the tag can handle line breaking, but the flag does not. closes: Bug#139820 * Change the requirement to ask permission to make devices to merely requiring a notification. closes: Bug#106280 * Added a build dependson docbook utils. closes: Bug#154660 * Since this is being built with a newer version of debiandoc-sgml, this should display better with lynx. closes: Bug#153704 * Add in the crypto-in-main amendment. closes: Bug#81852, Bug#144411 * we no longer have task packages, instead, we define tasks using a special field in the control file (and these should be added only after discussion on the mailing lists) closes: Bug#97755 * Clarify wording in the section for packages providing fonts. closes: Bug#109672 * Fix the doc base file for policy process closes: Bug#137521, Bug#147554 closes: Bug#146756 * using set -e is not dubious advice. Rejecting this. closes: Bug#139969 * Make the directory one is building under ./debian/ be up to the maintainer, instead of mandating ./debian/tmp/ closes: Bug#144297 * Add a standards version closes: Bug#145067 * Added virtual package debconf-2.0 closes: Bug#151328 * Added The Window Manager Specification Project support to the default window manager selection mechanism closes: Bug#155680 * The confusion between /var/mail and /var/spool/mail seems to have been disambiguated. closes: Bug#114949 * Mention the new Build-Depend-Indep semantic and the new build-indep/build-arch rules in upgrading checklist closes: Bug#116134 * Made package naming rules in policy consistent. I did not eliminate the duplication, since I don't want to make major changes to the flow, since we are supposed to be re-writing policy anyway. closes: Bug#131441 * Clarified wording about cases where we may have concrete and virtual packages with the same name. closes: Bug#134977 * Fixed typo 'be be' closes: Bug#138681 * Fixed typo in appendix G -- example of diversion closes: Bug#140697 * fix typo shlib: -> shlibs: closes: Bug#141903 * Provide a link between two sections dealing with virtual packages. closes: Bug#143770 * Fixed xtifr's email address in the menu policy closes: Bug#152965 * Allow shared library names to be have a hyphen between library name and soversion if the library name ends in a number. closes: Bug#100472 * Permit some libraries to only install static libs. closes: Bug#100346 * Remove the debug option, add noopt closes: Bug#157131, Bug#113525 * provide dhcp-client virtual package. closes: Bug#154142 * We do not need bits in policy that ``should not be enforced''. closes: Bug#150456 * We are building this with the latest debianndoc-sgml. closes: Bug#146703 * Finish incorporating all of the accepted changes in Bug#72335, and this closes: Bug#141307, Bug#156546 * Added virtual package aspell-dictionary closes: Bug#139067 * Added virtual package radius-server closes: Bug#118608 * Clarifying manual pages is not a policy issue. closes: Bug#112828 * Corrected the ldconfig handling instructions. closes: Bug#111025 * Not a policy issue. closes: Bug#106826 * Removed the /usr/doc/ symlink clause. closes: Bug#47298, Bug#69311 -- Manoj Srivastava Sat, 31 Aug 2002 02:18:02 -0500 debian-policy (3.5.6.1) unstable; urgency=low * Set the cotact information for the FHS contact, and add mention of the FHS mailing list. closes: Bug#137172 * ftp://ftp.debian.org/debian/doc/package-developer/ certainly seems to exist, and does contain the menu policy. closes: Bug#110711, Bug#121977 * Added java related virtual packages closes: Bug#110713 * Fixed confusion in appar4ently contradictory wording about /etc/init.d scripts: clarified to emphasize that the init.d files _are_ configuration files, and they _must_ have local changes preserved, either (if they are present in the .deb) by marking them as conffiles or, if they do not exist in the .deb file, by any other means. This does not change any requirements, and should have no affect on any conformant packages. closes: Bug#132621 * Fixed error in doc-base file closes: Bug#137521 * fixed typo in virtual packages list closes: Bug#110446 * Fixed typo in upgrading checklist. closes: Bug#110705 * Fixed typo (dependencies) in the policy closes: Bug#122931 * Fixed grammar errors in the policy closes: Bug#126131 * While I am cleaning out bugs, these are old and the reporter no longer wnats to pursue them, and there was never a consensus reached. If there is interest, new bugs can be filed. closes: Bug#51411, Bug#51412 * Added the virtual package dict-client closes: Bug#122996 * Added the virtual package foomatic-data closes: Bug#123570 * Added the virtual packages {x-}audio-mixer closes: Bug#131781 -- Manoj Srivastava Thu, 14 Mar 2002 12:16:53 -0600 debian-policy (3.5.6.0) unstable; urgency=low * Change footnote about urgency values to the now-current list: low, medium, high, emergency. * Correct note about /etc/default files being conffiles/config files, which I mucked up (sorry Joey) [10.3.2] * [AMENDMENT 2001/06/26] Downgrade emacs/tex to optional closes: Bug#102204, Bug#53849 * [AMENDMENT 2001/06/26] Next stage in usr/doc -> usr/share/doc transition closes: Bug#102199 * [AMENDMENT 09/06/2001] Clarifying FHS policy closes: Bug#98291, Bug#60461 * Spelling correction closes: Bug#105625 * [AMMENDMENT 28/06/2001] Restrict http access to /usr/share/doc closes: Bug#100631 * [AMENDMENT 23/5/2001] Optional build-arch and build-indep targets for debian/rules closes: Bug#72335 * The old packaging manual is included in the policy document as an informative appendix. It is not part of Debian Technical Policy, and its presence is a temporary measure until dpkg documentation includes the information provided. closes: Bug#105535 * Added information about optional blank lines in the chagelog format. closes: Bug#105538 -- Manoj Srivastava Tue, 24 Jul 2001 21:43:22 -0500 debian-policy (3.5.5.0) unstable; urgency=low * Fixed up incorrect entries in the changelog (there was an erroneous 3.5.0.1 revision which never happened; it has now been correctly merged with the 3.5.3.0 changelog entry) * Add section numbers to upgrading-checklist for all revisions from 3.0.0 onwards * Complete rewrite (and renumbering) of sections 9.1 and 9,2 * This time *really* include the HTML version of the FHS * Added doc-base support for all of the HTML files * Added several more files to the byhand list and rewrote chunks of debian/rules to do this * Add patched versions of debiandoc-sgml stuff to source package until patches are incorporated upstream * Versioned Build-Depend on debiandoc-sgml for fixed Text.pm * Improved mkdir example in 10.1.2 closes: Bug#92744 * Made the "where examples live" entry in the upgrading-checklist clearer (add "for use by scripts") * Add a dpkg-statoverride description section closes: Bug#89473 * Fix the ldconfig usage description (remove "only if") closes: Bug#89674 * Clarification of package priority issues vis-a-vis the X Windows system closes: Bug#91249 * Enhanced x-terminal-emulator policy closes: Bug#91252 * Minor changes to X app-defaults policy closes: Bug#91259 * Clarification of X policy in respect to FHS closes: Bug#91260 * OpenMotif has the same rules as OSF/Motif closes: Bug#91261 * The X Font policy rewrite closes: Bug#91257 * The "man" program is no longer guaranteed to read header information to find alternative manpage names closes: Bug#94995 * Correction to meaning of Standards-Version closes: Bug#97072 * Split section 12.8 (X Window System) into subsections for readability * Plug-ins != shared libraries (at last) closes: Bug#66023 * Add packaging manual remnants to policy document as appendices, and mention this in control file closes: Bug#95906 * Clarification in Perl policy closes: Bug#98712 -- Julian Gilbey Fri, 1 Jun 2001 10:37:52 +0100 debian-policy (3.5.4.0) unstable; urgency=low * [ACCEPTED 2/4/01] /var/mail and /var/spool/mail closes: Bug#42052 * [AMENDMENT 26/04/2001] include Perl Policy closes: Bug#83977 * Also incorporates all the improvements that Julian has made to to the grammar and flow of the policy manual. The following are mostly Julian's fixes: * Removed reference to non-extant dpkg documentation * Fixed the confusing self referential language. closes: Bug#85503 * Correct ambiguous kanguage about declaring build dependencies. closes: Bug#86436 * Improved the woding of the footnote about shlibdeps. closes: Bug#87233 -- Manoj Srivastava Sat, 28 Apr 2001 13:30:21 -0500 debian-policy (3.5.3.0) unstable; urgency=low * Removed recommendation on packaging-manual closes: Bug#86507, #93620, #93705 * Also now Conflicts and Replaces packaging-manual * Remove FSSTND from binary package, although retain it in the source package for the time being * Get the version.ent non-compression thingy right this time! * Also install FHS stuff byhand (as requested by webmasters) * Corrected GPL name and location closes: Bug#88788, #93047 * Correct bug severities closes: Bug#91276 * Correct typos etc. in policy-process * Rename all .text files as .txt * Fixed the "to to" typo in policy closes: Bug#87007 * Changed packaging manual ==> dpkg documentation closes: Bug#88651 * [ACCEPTED 14/03/2001] Deprecate confusing closes: Bug#87828 Build-Depends arch syntax * [AMENDMENT 29/03/2001] Clarification of example closes: Bug#87711 configuration files * Undo all renaming to text, since the change had not been propogated to the rules file, which broke badly. This shall have to wait for a later version. * Richard Braakman and Michael Dorman have expressed their resignation from policy maintenance duties. * fixed the date thinko in upgrading checklist. Thanks to Sébastien Montagne closes: Bug#84236 -- Manoj Srivastava Sun, 15 Apr 2001 13:36:19 -0500 debian-policy (3.5.2.0) unstable; urgency=low * Add XFree86 app-defaults ammendment closes: Bug#83069 -- Julian Gilbey Sun, 18 Feb 2001 14:11:49 +0000 debian-policy (3.5.1.0) unstable; urgency=low * Removed deprecated virtual package names closes: Bug#84641 * Changed rmdir postrm example (suggestion on -policy list) * Removed Richard Braakman from list of maintainers at his request * Corrected typos and grammatical errors found by Sean Perry closes: Bug#85501, #85504, #85505, #85506 closes: Bug#85508, #85510, #85511, #85514 closes: Bug#84631, #84636, #85497, #85982 closes: Bug#85986, #85993, #86001 * No longer include the old proposal document closes: Bug#84079 * Update footnote about dpkg-shlibdeps now that it uses objdump; bump up minor version number for this * Updated dpkg-shlibdeps example to use up-to-date package names (and correct dpkg-shlibdeps command line syntax) * Clarify error conditions for package installation (Bug#61801 from packaging-manual) * Add the "main" section of each distribution (got left out by accident!) (Bug#64304, #75955 from packaging-manual) * Clean version numbering string (Bug#73064 from packaging-manual) * Install HTML version of FHS closes: Bug#83487 * Removed bashism from debian/rules -- Julian Gilbey Thu, 15 Feb 2001 12:13:00 +0000 debian-policy (3.5.0.0) unstable; urgency=low * There have been numerous changes since the last major change, and peole have had tiome now to review the recent changes, so I am updating the policy minor version to reflect the quantity and magnitude of changes since 3.2.1 * More spelling corrections, thanks to "Christian T. Steigies" * Added mention of DEB_BUILD_OPTIONS in upgrading checklist. closes: Bug#83924 * Fixed some typos. closes: Bug#83960 * Policy now mentions preinst scripts. closes: Bug#80342 * [AMENDMENT 2000/12/26] allow/document use of Debian Configuration management system (debconf) closes: Bug#80347 * Yet more typo fixes closes: Bug#82743 * Document the fact that X font utilities have moved to the package xutils closes: Bug#82966 * Fixed the date in the virtual package list closes: Bug#83438 * Cleaned up some ephemeral informative foornotes of the polic. Thanks to Branden Robinson closes: Bug#83065 * Corrected reference to the mime policy. closes: Bug#79891 * Corrected reference to the menu policy. closes: Bug#75925 * Added a note to the effect that the example make snippet used to illustrate the DEB_BUILD_OPTIONS environment variable is merely informative, and expanded the example to dismiss any confusion about potential failure due to accidentally trying to strip scripts. closes: Bug#80506 -- Manoj Srivastava Sun, 28 Jan 2001 21:59:16 -0600 debian-policy (3.2.1.2) unstable; urgency=low * The minimal change in version number is so that people can test and root out the bugs in this document before we make everyone change to this version. * Document the Enhances relationship * Removed the restriction that one, and exactly one, person must maintain a package. closes: Bug#51879 * Fixed a typo, and added the nogroup name, in uid/gid section of policy. closes: Bug#53496 * Fixed a misstatement in policy about not needing to depend on packages in the base system (not true -- the Essential tag is significant) closes: Bug#53700 * Clarified update-rc.d stuff closes: Bug#55048 * We have already included the material for shlibdep changes, and most of this is not relevant to policy anyway. closes: Bug#55730 * makedev--> MAKEDEV closes: Bug#57154 * Added restrictions on the files in /usr/share/doc/ closes: Bug#59403 * Changed location of a paragraph about copyright files into the section that deals with copyright files. closes: Bug#65765 * init script configuration variables closes: Bug#66912 * Clarifed language about packages sharing a conffile need to be marked as conflicting closes: Bug#76028 -- Manoj Srivastava Thu, 18 Jan 2001 01:43:58 -0600 debian-policy (3.2.1.1) unstable; urgency=low * Don't compress version.ent in the doc directory (it gets bigger!) * Incorporate the packaging manual into the policy document. The minimal change in version number is because I suspect that this version is going to be buggy. closes: Bug#62943, Bug#72949 * Fixed typo in menu-policy. closes: Bug#70442 * Fixed typo in policy manual closes: Bug#70634, Bug#70643 * Removed extraneous > from policy closes: Bug#77645 * Fixed two typos in upgrading checklist closes: Bug#78809, Bug#78822 * Fixed spelling of utility closes: Bug#82458 * [ACCEPTED 2000/09/08] Free pkgs depending on non-US should go into non-US/{main,contrib} closes: Bug#69229 * Added rsh-server and telnet server to the virtual packages list closes: Bug#77404 * Fixed outdated references to the FHS. closes: Bug#77650 -- Manoj Srivastava Tue, 16 Jan 2001 23:53:31 -0600 debian-policy (3.2.1.0) unstable; urgency=low * [AMENDMENT 15/01/2000] revision of the "to build with X support or not" policy. closes: Bug#53759 * [ACCEPTED 2000/06/06] Must/Should/May in policy This is only a clarifying change, and was not intended to change the intent of policy. closes: Bug#64437 * [ACCEPTED 03/05/2000] About the use of conffiles. closes: Bug#61308 * [AMENDMENT 10/05/2000] s/mail\.mail/root\.mail/ closes: Bug#62668 * [ACCEPTED 04/05/2000] Update for new non-US layout closes: Bug#62946 * [ACCEPTED 04/05/2000] s/debian-devel/debian-legal/ closes: Bug#62947 * [ACCEPTED 04/05/2000] s/bash/base-files/ closes: Bug#62948 * Typo: 1744s/tty/ttyS/ closes: Bug#64516 * proposal for mp3-encoder virtual package closes: Bug#64004 * proposal for mp3-decoder virtual package closes: Bug#64006 * new virtual package time-daemon closes: Bug#69031 * [PATCH] typos in menu-policy.sgml closes: Bug#69424 * [PATCH] typos and awkwardness in policy.sgml closes: Bug#69426 * the example for using nostrip in DEB_BUILD_OPTIONS is incorrect. closes: Bug#69487 * [PATCH] more corrections closes: Bug#69670 * [AMENDMENT 26/10/99] Amend non-free definition closes: Bug#46522 * [AMMENDMENT 29/10/99] /bin/sh needs echo -n closes: Bug#48247 * [AMENDMENT 1999/11/23] Clarify meaning of Essential: yes closes: Bug#50832 * [ACCEPTED] Request for new virtual packages: rsh-client and telnet-client closes: Bug#58759 -- Manoj Srivastava Thu, 24 Aug 2000 02:06:30 -0500 debian-policy (3.2.0.0) unstable; urgency=low * Fixed bugs in debian-policy package: * We have had doc-base support for a while now. closes: Bug#15709 * packaging manual: Added additional clarification on dpkg behaviour. closes: Bug#17369 * [PROPOSAL] Do not make hardlinks to conffiles closes: Bug#22935 * [PROPOSED]: clarification needed about diversions. fixed usage for dpkg-divert closes: Bug#29522 * [OLD PROPOSAL] debian-policy has an unclear statement on dependancies and priorities closes: Bug#39398 * [ACCEPTED 10/26/99] changelog.html.gz sanitization. closes: Bug#40934 * [AMENDED 07/09/1999] policy on -g, a proposal closes: Bug#43787 * Fixed missing tag. closes: Bug#51091 * Correct typo in section 2.3.5 closes: Bug#52225 * Documented that the library before the symlink hack (which dependend on file system specific kinks to work) is no longer required by newer versions of dpkg. closes: Bug#53405 * [ACCEPTED 02/01/2000] policy for usage of "xserver" alternative closes: Bug#53755 * [ACCEPTED 02/01/2000] additions to virtual package list closes: Bug#53756 * [ACCEPTED 02/01/2000] policy for "x-terminal-emulator" virtual package and alternative closes: Bug#53757 * [ACCEPTED 02/01/2000] policy for "x-window-manager" virtual package and alternative closes: Bug#53758 * [ACCEPTED 02/01/2000] revision of X application-defaults policy closes: Bug#53760 * [ACCEPTED 02/01/2000] revision of the Motif/LessTif policy closes: Bug#53761 * [ACCEPTED 02/01/2000] applying the FHS to packages that use X closes: Bug#53762 * [ACCEPTED 02/01/2000] policy for X font packages closes: Bug#53763 * Moved the documents into the Debian/ section, since that is where they belong, really. closes: Bug#54777 * Fixed the ftp location in the manuals. closes: Bug#56407 * Fixed missing urlname entity in the sgml docs (where was it defined before anyway?) closes: Bug#56692 * Fixed bugs in packaging-manual package: * Fixed typo where dpkg-genchanges was used instead of dpkg-gencontrol. closes: Bug#58771 * Other changes: * Added policy-process to document current procedures. * Added a dependency on fileutiles >=4.0, since the package would fail to install with older fileutils. * Installed FHS version 2.1 * Policy recommends packaging manual and vice versa * Added FHS details to copyright file * Updaed the upgrade checklist. Minor changes to the ./debian/rules file. * Added footnotes in the packaging manual warning about the upcoming dpkg-shlibdeps change as in Bug#55730 -- Manoj Srivastava Sun, 30 Jul 2000 17:43:02 -0500 debian-policy (3.1.1.3) unstable; urgency=low * Fixed an upgrade bug when /usr/doc happens to be a symlink, and does not point to /usr/share/doc. A couple of people were bitten by this. -- Manoj Srivastava Mon, 28 Feb 2000 22:27:05 -0600 debian-policy (3.1.1.2) unstable; urgency=low * Correct missing in packaging.sgml (closes: #51091) * Correct typo in policy 2.3.5 (closes: #52225) -- Julian Gilbey Mon, 20 Dec 1999 20:39:57 +0000 debian-policy (3.1.1.1) unstable; urgency=low * Correction to typo in packaging manual, section 6.2. * Correction to typo in packaging manual, section 12.2.5 (closes: #50502) * More corrections to packaging manual typos (closes: #50857) -- Julian Gilbey Mon, 22 Nov 1999 19:23:31 +0000 debian-policy (3.1.1.0) unstable; urgency=low * Correct description of negated architectures in Build-Depends description in Packaging manual (closes: #49901) -- Julian Gilbey Tue, 16 Nov 1999 15:03:48 +0000 debian-policy (3.1.0.0) unstable; urgency=low * Add instructions on /usr/doc -> /usr/share/doc symlinks (closes: #45561, #42447, #48570) * Added source dependencies (closes: #41232) * Deprecated /etc/rc.boot (closes: #32448, #32449) * Update-rc.d now only legal way to automatically access /etc/rc?.d directoried (closes: #41547) * FHS compliant location of examples (closes: #42849) * Added ispell-dictionary to virtual-packages.list (following new suggestions: no objections => accept) (closes: #8221) * Added man-browser to virtual-packages.list (closes: #24695) * Added ident-server to virtual-packages.list (closes: #45307) * Alphabeticised virtual packages list ;) * Corrected GPL reference in proposal.sgml * Clarification of "extra" priority (closes: #33076) * Remove buggy and seriously problematic licenses from list of contrib package criteria (closes: #45318) * Move docs to /usr/share/doc with a compatibility symlink (closes: #41829) * Update to FHS 2.1 draft #3 (for /var/state etc. changes). * Correct /var/lib/games -> /var/games (closes: #42358) * Added MIME subpolicy (closes: #46516) * Added support for VISUAL (closes: #41121) * Clarify non-dependence on /usr/local (closes: #44922) * Modified description of mail spool locking (closes: #43651) * Clarified wording of conffiles and configuration files (closes: #40766, #40767) * Changed description of release numbers (closes: #44620) * Added changelog.html -> changelog requirement (closes: $40934) * packaging-manual now correctly installs its docs (closes: #44643) * The packaging manual now discusses version numbers based on dates (closes: #17621) * Mention ls -f for testing order in which files appear on disk (closes: #19179) * Change order of '.' and '+' in description of version numbers (closes: #41095) * s/fields/field names/ in section 4.1 of packaging manual for clarity * Add Build-Depends-Indep: field to control file -- Julian Gilbey Thu, 4 Nov 1999 23:50:37 +0000 debian-policy (3.0.1.1) unstable; urgency=low * Typo corrected in packaging manual. closes: Bug#40180 * Chnaged rules file to create ps and pdf files. -- Manoj Srivastava Mon, 16 Aug 1999 01:21:09 -0500 debian-policy (3.0.1.0) unstable; urgency=low * A few typos and omissions corrected * Added the pop3-server to the virtual packages list, as decided on the list. * Fix the self reference to a location on the web site. closes: Bug#39408 * Added the clarification that the .la files are essential for the packages using libtool's libltdl library, in which case the .la files must go in the run-time library package. (this is why this is version 3.0.1.0, and not 3.0.0.1) * The virtual package list has new directions (this has been true for a while, I am just closing the bug now). closes: Bug#26159 * Since this package now contains the FHS, this closes: Bug#25533 * The General resolution prototcol handling of the logos closes: Bug#26915 * Inclusion of the Menu policy in the main policy document closes: Bug#30036 * Since proposal submitting guidelines are now in the policy package, this closes: Bug#38612 * Changed a /usr/doc reference to /usr/share/doc which had beeen missed before. closes: Bug#40864 -- Manoj Srivastava Thu, 15 Jul 1999 13:35:11 -0500 debian-policy (3.0.0.0) unstable; urgency=low * This is a test version of the policy package, and shall not be officially uploaded. * Merged in the packaging manual sources (we still have two separate .deb packages) * Multiple minor packaging tweaks. * [ACCEPTED 1998/05/01] Policy clarification about Standards-Version Added the clarifying paragraph (and the rationale in a footnote). closes: Bug#21969 * [ACCEPTED 1999/04/05] Policy note that GPL moved to /usr/share/common-licenses. Again, also added the rationale as a footnote. closes: Bug#28747 * [ACCEPTED 1999/05/04] Libtool archive (*.la) files in -dev' packages closes: Bug#37257, Bug#37338 * [ACCEPTED 1999/04/28] Logrotation. Standardizer on logrotate. closes: Bug# 37342 * [ACCEPTED 1999/05/23] Rewrite of section 5.7 (Programs for the X Window System) closes: Bug#38212 * [ACCEPTED 1999/05/15] Separate menu policy (like virtual package list) closes: Bug#37713 * [ACCEPTED 1999/05/09] Utmp group proposal closes: Bug#37389 * [ACCEPTED 1999/05/09] Adopt the FHS in place of FSSTND Changed all references to the proper FHS versions. This was a first scan, so some references may still need to be changed. closes: Bug#37345 * Updated the upgrading checklist. * updated the proposal for policy update to reflect the latest -- Manoj Srivastava Wed, 30 Jun 1999 22:49:15 -0500 debian-policy (2.5.1.0) unstable; urgency=low * Removed double '>' marks from the policy document. closes: Bug#35095 * Corrected canonical source for "Csh Programming Considered Harmful" closes: Bug#36286 Bug#32499 * Fixed typo in invocation of update-rc.d. closes: Bug#34988 Bug#34543 * Fixed misspelling of accessible. Ran ispell over the rest of the document (painful because of the large number of technical terms in there). closes: Bug#34233 * Make the binary package contain the version.ent as well. closes: Bug#31033 * Fixed typo s/as is/is/. closes: Bug#30302 * AMENDMENT 23/04/1999: changed /etc/nntpserver recommendation to /etc/news/server. closes: Bug#21875 * Added the current list of policy maintainers. closes: Bug#30148 -- Manoj Srivastava Tue, 27 Apr 1999 11:10:29 -0500 debian-policy (2.5.0.0) unstable; urgency=low * AMENDMENT: Added in changes in Bug #25911, which rearranged sections to create a new section 4, namely, files. Section 3.3 ("Files") should become Section 4. The Sections that are currently Section 4 and Section 5 should be moved down to become Section 5 and Section 6 accordingly. What is now Section 5.5 ("Log files") should be moved to be a subsection of the new Section 4 ("Files"), becoming section 4.8, placing it after "Configuration files", moving the would-be Section 4.8 ("Permissions and owners") to Section 4.9. All subsections of the current Section 5 after 5.5 should be accordingly moved down to fill in the number gap. This, along with the next amendment, justifies bumping up the version number. closes: BUG#25911 * AMENDMENT: Added in changes in Bug #21185, about the naming and compression of changelog files. Now, if the upstream changelog file is HTML formatted, it should be accessible as /usr/doc//changelog.html.gz It also allows for this to be a symlink, if the upstream file name does not conform to Debian conventions. closes: BUG#21185 * AMENDMENT: Added in changes in Bug #7890, to make clear that the HTML documents should be supplied in _some_ package, not necessarily in the main binary package (at the discretion of the maintainer). closes: BUG#7890 * AMENDMENT: Added in changes in Bug #26461, which corrects the policy to refer to /usr/doc//copyright, rather than /usr/doc/copyright/. closes: BUG#26461 * AMENDMENT: Added in changes in Bug #25385, which allow the architecture specification strings to be of the form -, where os is one of linux, gnu. Previously, only linux was allowed, now we also cater to the hurd. closes: BUG#25385 * The responsibility of the contents of this package has now passed to the debian-policy mailing list. The packaging details are now being managed by a group of maintainers that do ot won the contents. * Make the package optional, not extra. * Re did the SGML markup. Normalized the document, and undid the omitted and shor tags. Personally, I use too many DTD's in real life to be so converssant with each one to be clever with tag omissions, and, since I have a smart editor, omitting tags does not byuy one much. In the process, I discovered a few errors in the markup (one of my predecessors hasd the unfortunate habit of treating

as a "create some space here" tag, and more often than not put it at the end of a paragraph, rather than using is as a container element (which is what it is, really). * Re did the control files, making them more robust * re did the rules file, making it more general, and easier to maintain by putting in a layer of abstractions. -- Manoj Srivastava Thu, 29 Oct 1998 15:16:52 -0600 debian-policy (2.4.1.4) unstable; urgency=low * New Maintainer -- Philip Hands Sat, 5 Sep 1998 02:41:35 +0100 debian-policy (2.4.1.3) unstable; urgency=low * New maintainer (with changes from Adam P. Harris' proposed NMU) * policy.sgml: some awkward phrasings fixed (closes Bug#22006) * policy.sgml: s/depreciated/deprecated (closes Bug#21831) * debian/control: added conflict doc-base (<< 0.6), which I still am not sure why we need this but hey (closes Bug#21554) * policy.sgml: use new tag where appropriate * policy.sgml, debian/control: always dynamically self reference the current version of policy, that is, do not hard code policy revision or date anywhere * debian/rules: use dpkg-gencontrol -isp * bugs fixed in some unknown previous version (closes Bug#23177) -- Philip Hands Tue, 11 Aug 1998 09:54:17 +0100 debian-policy (2.4.1.2) frozen unstable; urgency=low * non-maintainer release * rebuild package to fix truncated Chapter 3 (Bug#23408, not marked as important but should be, since a gaping hole in policy is very annoying.) * bumped version of policy, within the document, to this version number, but not the date, indicating nothing really changed since then * no content changes * debian/rules: clean is a little cleaner -- Adam P. Harris Tue, 16 Jun 1998 03:15:22 -0400 debian-policy (2.4.1.1) frozen unstable; urgency=low * Orphaned package -- Christian Schwarz Thu, 14 May 1998 21:54:50 +0200 debian-policy (2.4.1.0) frozen unstable; urgency=low * Changes to the Debian Policy Manual: - Updated section 3.1.2 Site-specific programs and section 3.8 Keyboard configuration: + improved wording (fixes:bug#20129) - Updated section 2.1.7 Subsections: + fixed typos (fixes:bug#18145) - Updated section 3.3.5 Symbolic links: + symbolic links within a toplevel directory should be relative, symbolic links between toplevel directories should be absolute (cf., Policy Weekly Issue#6, topic 2) - Updated section 3.4 System run levels: + Intro: mention /etc/rcS.d (links to boot time scripts) + Notes: include rationale why /etc/init.d scripts have to be tagged as conffiles (fixes:bug#16199) + Example: changed example init.d script to handle force-reload and restart options and to comply with the console message standard (fixes:bug#19216) - Updated section 4.8 Emacs lisp programs: + Replaced old section about lisp programs with a reference to the file debian-emacs-policy.gz, installed by the emacsen-common package. - Updated section 4.9 Games: + manpages for games should be installed in /usr/man/man6 (cf., Policy Weekly Issue#6, topic 3) - Removed one example reference to the current standards version - Include manual's date as plain text in the .sgml source so that a recompiled manual uses the same release date * Changes to the authoritative list of virtual package names: - Removed obsolete virtual package `emacs' * New version numbering scheme: - The version numbers are independent of dpkg now, but all policy manuals (the Debian Policy Manual, the Debian Packaging Manual, and the Debian Developer's Reference) share the same version numbering scheme. - The first three digits of the version number specify the `Standards-Version.' This number is incremented with each policy change. The fourth digit represents the `patch-level,' which may differ between the manuals. If only the patch-level digit is incremented, no changes in policy have been made, except bug fixes and clarifications. Packages only have to specify the first three digits of the version number in the `Standards-Version' field of their source packages. * Packaging changes: - Uploaded to frozen and unstable. This is a documentation-only package and the changes to the manual are relevant for hamm. - Fixed FSF's address in copyright file (detected by Lintian) -- Christian Schwarz Tue, 14 Apr 1998 10:08:09 +0200 debian-policy (2.4.0.0) unstable; urgency=low * Changes to the Debian Policy Manual: - Updated section 3.3.4 Scripts: + /bin/sh may be any POSIX compatible shell + scripts including bashisms have to specify /bin/bash as interpreter + scripts which create files in world-writable directories (e.g., in /tmp) should use tempfile or mktemp for creating the directory - Updated section 3.3.5 Symbolic Links: + symbolic links referencing compressed files must have the same file extension as the referenced file - Updated section 3.3.6 Device files: + /dev/tty* serial devices should be used instead of /dev/cu* - Updated section 3.4.2 Writing the scripts [in /etc/init.d]: + all /etc/init.d scripts have to provide the following options: start, stop, restart, force-reload + the reload option is optional and must never stop and restart the service - Updated section 3.5 Cron jobs: + cron jobs that need to be executed more often than daily should be installed into /etc/cron.d - Updated section 3.7 Menus: + removed section about how to register HTML docs to `menu' (the corresponding section in 4.4, Web servers and applications, has been removed in policy 2.2.0.0 already, so this one was obsolete) - New section 3.8 Keyboard configuration: + details about how the backspace and delete keys should be handled - New section 3.9 Environment variables: + no program must depend on environment variables to get a reasonable default configuration - New section 4.6 News system configuration: + /etc/news/organization and /etc/news/server should be supported by all news servers and clients - Updated section 4.7 Programs for the X Windows system: + programs requiring a non-free Motif library should be provided as foo-smotif and foo-dmotif package + if lesstif works reliably for such program, it should be linked against lesstif and not against a non-free Motif library - Updated section 4.9 Games: + games for X Windows have to be installed in /usr/games, just as non-X games - Lots of typos fixed (thanks to Ray Dassen for the patch!) * Changes to the authoritative list of virtual package names: - added `libc-dev' and `emacsen' * Merged `/usr/doc/debian-policy/changelog-policy.gz' into this changelog file * Included `Policy checklist for upgrading your packages' from the Policy Home Page as /usr/doc/debian-policy/upgrading-checklist.text.gz * Added support for doc-base to register the Policy Manual to the online documentation systems dwww and dhelp (fixes:#15710) * Upgraded to standards version 2.4.0.0 (no changes) -- Christian Schwarz Fri, 30 Jan 1998 21:58:25 +0100 debian-policy (2.3.0.1) unstable; urgency=low * Changes in the Debian Policy Manual: - X library package is now called xlib6g * Changes in the authoritative list of virtual package names: - Added emacs, c-compiler, fortran77-compiler, lambdamoo-core, lambdamoo-server * Conflict with old dpkg-dev version that included policy manual (fixes #13790) * Removed `tentative-opt-draft' from package since people considered the draft official policy (which is not the case) * Don't use debstd anymore -- Christian Schwarz Tue, 21 Oct 1997 23:03:52 +0200 debian-policy (2.3.0.0) unstable; urgency=low * Changes in the Debian Policy Manual: - reworked chapter `The Debian Archive' to cover new contrib/non-free policy - call "contrib" and "non-free" a `section' (not `distribution') - refer to license files (GPL, LGPL, etc.) as uncompressed files - changed `/etc/news/server' into `/etc/nntpserver' in example of maintainer scripts (fixes #11517) - new section about `Daemons' - updated section about `Configuration files' - MUAs and MTAs have to use liblockfile - fixed typos and grammatical errors * Changes in the authoritative list of virtual package names: - renamed tcl/tk virtual package names to `tclsh' and `wish' * Paper about libc6 migration: - fixed typos (fixes #11641), thanks to James Troup for the patch! * SGML source code included in package * don't use `2-up' style for PostScript version (fixes #11095) -- Christian Schwarz Mon, 2 Sep 1997 00:54:31 +0200 debian-policy (2.2.0.0) unstable; urgency=low * Changes in the Debian Policy Manual: - completely reworked structure - moved sections about new maintainers, upload procedure, interim releases, and mailing lists into the Developers Reference Manual - moved a few (small) sections into the Debian Packaging Manual - removed all those ugly footnotes - new example for "reload" in section about console messages - mention Artistic License (fixes #9793) - don't mention dpkg's version number in Policy Manual - rewrote abstract and section introductions - mention "orphaned packages" - maintainer is responsible for a package license to comply with the distributions' policy - putting a package into base section requires discussion on debian-devel - rewrote sections about "pre-depends", "essential" and, "base" packages - added note that non-us' maintainers have to live outside the US - added crypto-hook statement (fixes #7257) - added section about arch spec strings - rewrote section about "Site specific programs" (/usr/local) - included Ian's suggestions for user IDs - added section about "menus" - removed section about "web menus" since this will be superseded with the new documentation policy soon - incorporated "Debian Free Software Guidelines" (fixes #9024) - removed note that linking with -g produces large a.out binary (fixes #11008) - added section about editors and pagers - added note about Package priorities and dependencies - added section about cron jobs (fixes #8814) - added section about device files - don't install shared libraries as executable (fixes #7129) - app-defaults files may not be conffiles (cf. #2717) - lots of minor changes not worth mentioning here (typos, formulations, etc.) * Changes in the authoritative list of virtual package names - Removed obsolete virtual packages: xR6shlib, xlibraries, compress, emacs, sgmls, inews, gs_x, gs_svga, gs_both, xpmR6 - Added new section about obsolete names * Added Helmut Geyer's paper about libc5-libc6 migration * Fixed package's description -- Christian Schwarz Sun, 13 Jul 1997 13:25:51 +0200 debian-policy (2.1.3.3) frozen unstable; urgency=low * Mention Artistic License in section 2.5 (bug #9755) -- Christian Schwarz Wed, 14 May 1997 16:53:15 +0200 debian-policy (2.1.3.2) frozen unstable; urgency=low * Fixed an email address, an URL, and several typos in chapter 6 (#9358) * Added new virtual package "wordlist" to list (requested by Joey Hess) * Changed wording in section about "non-free" packages as suggested by Kai Henningsen (#7076) -- Christian Schwarz Mon, 5 May 1997 20:05:39 +0200 debian-policy (2.1.3.1) frozen unstable; urgency=low * Fixed bug in chapter 7: `-ur' should read `-us' (#8874) * Fixed bug in chapter 7: `-rwhatever' also needed for rebuild (#8874) * Create a PS and HTML version of the Policy Manual and upload it "byhand". * Install virtual-package-names-list.text in /usr/doc/debian-policy and upload it "byhand" too. -- Christian Schwarz Tue, 29 Apr 1997 18:02:14 +0200 debian-policy (2.1.3.0) unstable; urgency=low * Initial Release. * New Policy Manager: Christian Schwarz * Added section 2.4 about the "non-us" distribution. * Added section 3.1.1 about the "Package" field in the control file. * Added section 3.2.1 about "Binaries": two programs with different functionality must not have the same name. * Changed headline of section 3.2.6 into "Debian changelog and upstream changelog" as suggested by Santiago Vila Doncel . * Added log-rotating example to section 3.2.9 that tests with `-sf', as suggested by Boris D. Beletsky . * Added section 3.13: "Webstandard 3.0" by Christoph Lameter. * Added section 3.14: "Standard for Console Messages" by Christian Schwarz. * Split section 4.1 into 4.1.1 (Options for binaries) and 4.1.2 (Options for libraries) * Added note to 4.1.2: Libraries should be compiled with `-D_REENTRANT' to make them compatible with LinuxThreads, by Rob Browning . * Added note to 4.1.2: Libraries should be stripped with "strip --strip-unneeded", by Guy Maor . * Section 5.2: Policy changelog is now "/usr/doc/debian-policy/changelog-policy.gz". This fixes bug #6130. * Section 6.2 renamed to "Uploading your first Debian package". This fixes bug #6130. -- Christian Schwarz Sat, 15 Mar 1997 18:08:56 +0100 debian-manuals (2.1.2.2) frozen unstable; * Fixed even more typographical and grammatical errors in Policy and Programmer's manual * Corrected the contact email addresses again. * Added a paragraph to Policy 6.3 on taking over an old package (Guy Maor) * Added a paragraph to Programmer 4.2.14 on listing distributions to load a package into. (Guy Maor) * Further clarification of use of absolute pathnames in scripts in Programmer 6.1. -- David Morris Tue, 3 Dec 1996 23:28:04 -0600 debian-manuals (2.1.2.1) frozen unstable; * Many editorial and formatting revisions with suggestions from Ian Jackson, Guy Maor and others * correction of chiark address in Policy 6.2 * footnote in Programmers chapter 2 pointing to deb(5) manpage for description of deb file format. * addition of more dpkg examples in Programmer chapter 2 * Replace paragraph in Policy 4.1 outlining compiling parameters for shared libraries. * Added paragraph in Programmer 6.1 on paths in maintainer scripts (Bug #2481) * Cleaned up language and formatting of Programmer's 12.2, shlibs * Corrected contact addresses for listmaster and override-change -- David Morris Wed, 27 Nov 1996 08:17:16 -0600 debian-manuals (2.1.2.0) frozen unstable; * Mostly editorial changes in Policy Manual. * Added summary of distribution criteria to Introduction * Added section headings for copyright criteria * Fixed typos (Bugs #4485, #4622) * Added paragraph in Compilation Options related to use of shared and static libraries. (Bug #5299) * Paragraph added about where to find PGP and other export restricted packages in section on Procedure * Change in List administrator and in the contact address for becoming a package maintainer * A paragraph added related to who to contact for package maintainer changes. * Changed where to send upload announcements: uploads destined for unstable, frozen, or experimental go to debian-devel-changes. * Made some mostly editorial changes to Programmers Manual. * Added a recommendation to debmake in Introduction. * A further interpretation of the various Distributions is added with the intent of helping people decide which one to choose. (section 4.2.14) * Section 12 on Shared Libraries expanded with further technical information on various shlib files * Section in 2.2 on format of shlib file moved to new subsection within 12. * Paragraph on adding a symlink without version number added to Shared Library Section (Guy Maor, Bug #5299) -- David Morris Fri, 22 Nov 1996 23:41:39 -0600 debian-manuals (2.1.1.0) unstable; * Hard links are forbidden in source packages (they didn't work anyway, and can't easily be made to work reliably). * Do not use dpkg-divert or update-alternatives without consultation. * Do not need to declare dependencies on Essential packages. * Restrictions on Pre-Depends stated in policy manual. * debian/substvars file is now almost always auto-generated. * Shared libraries must be installed stripped. * Essential and Pre-Depends put together in policy manual. * Explained component-wise (file-wise) vs. package-wise dependencies. -- Ian Jackson Thu, 12 Sep 1996 01:00:41 +0100 debian-manuals (2.1.0.0) unstable; * Upstream changelog must be installed too (was just recommended). * Modification to use dpkg-shlibdeps added to conversion instructions. * Packages which are buggy and orphaned but which are preserved for compatibility go in contrib. * Programmers' manual source package section refers to conversion instructions in policy manual. * Make it clear that recommending a non-free or contrib package puts a package in contrib. -- Ian Jackson Sun, 1 Sep 1996 17:47:18 +0100 debian-manuals (2.0.1.0) unstable; * varargs.h and libtermcap are obsolete - use stdarg.h and ncurses. * Shared library link/library ordering corrected (aargh). * When to byte-compile Elisp files. * Missing final newlines not represented by dpkg-source. * Must post upload announcements to debian-changes. * Moved some sections into new `configuring and building' chapter. * Typo fixes. -- Ian Jackson Sat, 31 Aug 1996 20:07:22 +0100 debian-manuals (2.0.0.0) unstable; * Footnote added OK'ing copyrights which require name changes. * More detail about changelog format names. * Problematic licence restrictions are formatted as lists. * Mentioned 822-date utility as way to generate RFC822 format dates. * Typos corrected. * Released. -- Ian Jackson Mon, 26 Aug 1996 14:27:34 +0100 debian-manuals (0.2.1.1) unstable; * Can't overwrite directories in one package with files in another. -- Ian Jackson Sat, 24 Aug 1996 18:44:54 +0100 debian-manuals (0.2.1.0) unstable; * Policy says when and how to include original source in upload. * Need -sa on dpkg-genchanges/dpkg-buildpackage when converting. * Use minor patchlevel for meaning changes which don't affect packages. * More verbosity about netiquette. * Reorganised participation and upload policy: merged with mailing lists. -- Ian Jackson Fri, 23 Aug 1996 12:48:09 +0100 debian-manuals (0.2.0.1) experimental; * Said that system administrators' manual does not exist. -- Ian Jackson Fri, 23 Aug 1996 04:05:36 +0100 debian-manuals (0.2.0.0) experimental; * Draft releases. -- Ian Jackson Wed, 21 Aug 1996 15:07:53 +0100 ubuntu-policy/debian/rules0000755000175000017500000001334111216714045016444 0ustar cjwatsoncjwatson#!/usr/bin/make -f ifdef ARCH ha:=-a$(ARCH) endif # set the dpkg-architecture vars; but we don't use them, so we'll comment out export DEB_BUILD_ARCH ?= $(shell dpkg-architecture $(ha) -qDEB_BUILD_ARCH) export DEB_BUILD_GNU_CPU ?= $(shell dpkg-architecture $(ha) -qDEB_BUILD_GNU_CPU) export DEB_BUILD_GNU_SYSTEM?= $(shell dpkg-architecture $(ha) -qDEB_BUILD_GNU_SYSTEM) export DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture $(ha) -qDEB_BUILD_GNU_TYPE) export DEB_HOST_ARCH ?= $(shell dpkg-architecture $(ha) -qDEB_HOST_ARCH) export DEB_HOST_GNU_CPU ?= $(shell dpkg-architecture $(ha) -qDEB_HOST_GNU_CPU) export DEB_HOST_GNU_SYSTEM ?= $(shell dpkg-architecture $(ha) -qDEB_HOST_GNU_SYSTEM) export DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture $(ha) -qDEB_HOST_GNU_TYPE) arch := $(shell dpkg --print-architecture) # Basic information package := $(shell grep Source debian/control | sed 's/^Source: //') date := $(shell date +"%Y-%m-%d") version := $(shell awk -F '[()]' '/^$(package)/{ print $$2; exit }' debian/changelog) # Location of the source dir SRCTOP := $(CURDIR) TMPTOP := $(SRCTOP)/debian/tmp DOCDIR := $(TMPTOP)/usr/share/doc/$(package) LIBDIR := $(TMPTOP)/usr/share/doc-base sanitycheck := debian/rules policy.sgml SGML_FILES := policy menu-policy mime-policy perl-policy DESC_FILES := ubuntu-policy ubuntu-menu-policy ubuntu-perl-policy \ ubuntu-mime-policy debconf-spec.ubuntu fhs.ubuntu # While we have two versions of the FHS installed in the source package, # we need to modify this to handle it. This is the easiest way to do it. # FHS_ARCHIVE := $(wildcard fhs*.tar.gz) FHS_ARCHIVE := fhs-2.3-source.tar.gz FHS_HTML := fhs-2.3.html FHS_FILES := fhs-2.3.ps.gz fhs-2.3.txt.gz fhs-2.3.pdf.gz FHS_NEW_ARCHIVE := FHS_NEW_HTML := FHS_NEW_FILES := POLICY_FILES = $(SGML_FILES:=.sgml) $(SGML_FILES:=.txt.gz) \ virtual-package-names-list.txt \ upgrading-checklist.txt libc6-migration.txt version.ent \ debconf_spec/debconf_specification.html \ debconf_spec/debconf_specification.txt.gz \ policy.ps.gz policy.pdf.gz # policy.{pdf,ps,tpt,txt} are generated files FILES_TO_CLEAN = debian/files debian/buildinfo debian/substvars \ debian/postinst debian/prerm \ version.ent upgrading-checklist.txt \ $(SGML_FILES:=.txt.gz) $(SGML_FILES:=.html.tar.gz) \ policy.pdf.gz policy.ps.gz \ debconf_specification.xml.tar.gz \ policy.pdf policy.ps policy.txt policy. \ body.tmp head.tmp policy.tpt STAMPS_TO_CLEAN := stamp-policy stamp-build DIRS_TO_CLEAN := debian/tmp fhs $(SGML_FILES:=.html) install_file := install -p -o root -g root -m 644 install_program := install -p -o root -g root -m 755 make_directory := install -p -d -o root -g root -m 755 all build: stamp-build stamp-build: version.ent $(sanitycheck) $(MAKE) $(SGML_FILES:=.sgml.validate) \ $(SGML_FILES:=.html.tar.gz) \ $(SGML_FILES:=.txt.gz) \ policy.ps.gz policy.pdf.gz links -dump upgrading-checklist.html | perl -pe 's/[\r\0]//g' > \ upgrading-checklist.txt $(MAKE) -C debconf_spec all touch stamp-build configure: version.ent version.ent: debian/changelog rm -f $@ echo "" >> $@ echo "" >> $@ clean: $(sanitycheck) # Undoes the effect of `make -f debian/rules build'. $(MAKE) -C debconf_spec clean rm -f $(FILES_TO_CLEAN) $(STAMPS_TO_CLEAN) rm -rf $(DIRS_TO_CLEAN) rm -f core `find . \( -name '*.orig' -o -name '*.rej' -o \ -name '*~' -o -name '*.bak' -o -name '#*#' -o \ -name '.*.orig' -o -name '.*.rej' -o -name '.SUMS' -o \ -size 0 \) -print` TAGS binary: binary-indep binary-arch binary-arch: build $(sanitycheck) # There are no architecture-dependent files to be uploaded # generated by this package. If there were any they would be # made here. binary-indep: stamp-policy stamp-policy: build $(sanitycheck) @test $$(id | sed -e 's/(.*$$//' -e 's/^uid=//') || \ (echo need root priviledges; exit 1) # This is unnecessary; commenting out # test -f stamp-build || $(MAKE) -f debian/rules build rm -rf $(TMPTOP) $(make_directory) $(TMPTOP)/DEBIAN $(make_directory) $(DOCDIR)/fhs $(make_directory) $(LIBDIR) # create a substvar to reference from debian/control so that # we don't hardcode the policy compliance of the policy # package. I guess some might question this but I take it as # a given that the ubuntu-policy pkg must always comply with # itself... echo "ubuntu-policy:Version=$(version)" > debian/substvars $(install_file) $(POLICY_FILES) $(DOCDIR)/ $(install_file) debian/changelog $(DOCDIR)/ # Be more specific with file compression gzip -f9 $(DOCDIR)/*.txt $(DOCDIR)/*.sgml \ $(DOCDIR)/changelog # These are allready compressed #$(install_file) $(FHS_NEW_FILES) $(DOCDIR)/fhs/ $(install_file) $(FHS_FILES) $(DOCDIR)/fhs/ $(install_file) debian/copyright $(DOCDIR)/ GZIP=-9 cd debconf_spec && \ tar -zcf ../debconf_specification.xml.tar.gz * $(install_file) debconf_specification.xml.tar.gz $(DOCDIR)/ @set -ex; \ for file in $(DESC_FILES); do \ $(install_file) $$file.desc $(LIBDIR)/$$file; \ done @set -ex; \ for file in $(SGML_FILES); do \ tar -C $(DOCDIR) -zxf $$file.html.tar.gz; \ done $(install_file) $(FHS_HTML) $(DOCDIR)/fhs @set -ex; \ cd debian/tmp; \ find . -path "./DEBIAN" -prune -o -type f -printf '%P\0' \ | xargs -r0 md5sum > DEBIAN/md5sums dpkg-gencontrol -p$(package) -Pdebian/tmp -isp chown -R root:root debian/tmp chmod -R go=rX debian/tmp dpkg --build debian/tmp .. touch stamp-policy .PHONY: configure build binary binary-arch binary-indep clean checkroot #Local variables: #mode: makefile #End: ubuntu-policy/menu-policy.sgml0000644000175000017500000004670511175362266017311 0ustar cjwatsoncjwatson %versiondata; ]> The Debian Menu sub-policy Chris Waters Joey Hess Joost Witteveen The Debian Policy mailing List debian-policy@lists.debian.org version &version;, &date; This manual describes the policy requirements for the Menu system used in the Debian GNU/Linux distribution. This document is part of the policy package for Debian. Copyright © 1999 Software in the Public Interest, Inc.

This manual is free software; you may 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, or (at your option) any later version.

This 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.

A copy of the GNU General Public License is available as /usr/doc/copyright/GPL in the Debian GNU/Linux distribution or on the World Wide Web at . You can also obtain it by writing to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.

About this document

This document is distributed as the menu-policy files in the Debian package . It is also available from the Debian web mirrors at .

This document has been extracted and separated from the Menu package to:

Increase the visibility of the Menu sub policy

Reduce the coupling between policy and implementation. If this separation is not made, every time we want to change menu policy, we have to arrange to get the maintainer to release a new version of the package, even if the package has not otherwise changed. It also involves yet another layer, making the policy changes that much harder to implement.

Menu Structure

If you have a package which doesn't fit within the existing menu hierarchy, please bring it up on the debian-devel mailing list. If you have other proposals for changing the menu hierarchy, or making other changes to menu policy, please bring it up on debian-policy.

Preferred menu structure

Here is the authoritative list of Debian's menu structure. Packages must be placed in leaf sections.

Applications

Normal applications

Applications/Accessibility

Tools to aid people with disabilities or for machines lacking usual input devices.

Examples: gok, yasr, dasher.

Applications/Amateur Radio

Anything relating to HAM radio.

Examples: baken, hamsoft, twlog

 Applications/Data Management

Interactive database programs, collection managers, address books, bibliography tools, etc.

gaby, alexandria, mdbtools

 Applications/Editors

Editors, other than office word processors, for text-based information.

Examples: ksubtile, nano, hexedit

 Applications/Education

Educational and training softwares.

Examples: gtypist, gcompris, quiz

 Applications/Emulators

Software that allows you to run non-native software or more than one OS at a time.

Examples: wine, dosemu, qemu

 Applications/File Management

Tools for file management, archiving, searching, CD/DVD burning, backup, etc.

Examples: file-roller, mc, baobab

 Applications/Graphics

2D and 3D graphics manipulation software.

Examples: gimp, inkscape, imagemagick

 Applications/Mobile Devices

Software that allows you to interface with mobile devices (phones, PDAs, etc.).

Examples: kandy, gnokii, gnome-pilot

 Applications/Network Network related software. This is a three-level section, do not put entries directly here. Applications/Network/Communication

Mail, USENET news, chat, instant messaging, IP telephony, video conferencing software, etc.

Examples: xchat, gaim, mutt

 Applications/Network/File Transfer

File transfer software such as download managers, FTP clients, P2P clients, etc.

Examples: amule, gftp, d4x

 Applications/Network/Monitoring

Network monitoring software

Examples: gip, ettercap, iptstate

 Applications/Network/Web Browsing

Web browsers, tools for offline browsing, etc.

Examples: elinks, epiphany-browser, webhttrack

 Applications/Network/Web News

Web feed (RSS, Atom, etc.) and podcast aggregators.

Examples: akregator, kitty, liferea

 Applications/Office

Office suites, word processors, spreadsheets, CRM, ERP, financial sofware, etc.

Examples: openoffice.org, tinyerp-client, gnucash

 Applications/Programming

IDEs, debuggers, etc.

Examples: anjuta, gdb, eclipse

 Applications/Project Management

Timetable managers, group task trackers, bug tracking software, etc.

Examples: planner, bugzilla, gnotime

 Applications/Science Scientific and engineering-related software. Applications/Science/Astronomy

Astronomy-related software.

Examples: celestia, spacechart, stellarium

 Applications/Science/Biology

Biology-related software.

Examples: arb, ncbi-tools-x11, seaview

 Applications/Science/Chemistry

Chemistry-related software.

Examples: chemtool, kalzium, xdrawchem

 Applications/Science/Data Analysis

Software designed for processing, extracting, and presenting generic scientific data.

Examples: fityk, ygraph, mn-fit

 Applications/Science/Electronics

Circuit design tools, simulators and assemblers for microprocessors, etc

Examples: geda, gnucap, tkgate

 Applications/Science/Engineering

CAD, UML tools, diagram-drawing and other engineering-related software.

Examples: tcm, dia, qcad

 Applications/Science/Geoscience

Geoscience-related software.

Examples: earth3d, qgis, therion

 Applications/Science/Mathematics

Mathematics-related software.

Examples: gcalctool, snappea, xeukleides

 Applications/Science/Medicine

Medicine-related software.

Examples: mssstest, gnumed-client, xmedcon

 Applications/Science/Physics

Physics-related software.

Examples: kxterm, ifrit, paw

 Applications/Science/Social

Social sciences-related software.

Examples: gnomesword, hanzim, bibletime

 Applications/Shells

Various shells to be used inside a terminal emulator.

Examples: bash, ksh, zsh

 Applications/Sound

Sound players, editors, and rippers/recorders.

Examples: beep-media-player, grip, audacity

 Applications/System System related software. Applications/System/Administration

Administrative and system configuration utilities, also tools for personal user settings.

Examples: gnome-control-center, configure-debian, gksu

 Applications/System/Hardware

Tools for manipulating specific hardware, especially non-standard laptop hardware.

Examples: toshutils, nvclock-gtk, nvtv

 Applications/System/Language Environment

This section is reserved for language-env as a special case.

 Applications/System/Monitoring

System information and monitoring tools, log viewers, etc.

Examples: top, hal-device-manager, gtkdiskfree

 Applications/System/Package Management

Package managers and related tools.

Examples: aptitude, deborphan, smartpm

 Applications/System/Security

Security, cryptography and privacy related software, antiviruses, tools to track and report bugs, etc.

Examples: gpgkeys, bastille, avscan

 Applications/Terminal Emulators

Graphical terminal emulators.

Examples: xterm, gnome-terminal, rxvt

 Applications/Text

Text oriented tools like dictionaries, OCR, translation, text analysis software, etc.

Examples: kdrill, stardict, turkey

 Applications/TV and Radio

TV-in, TV-out, FM radio, teletext browsers, etc.

Examples: gradio, gatos, alevt

 Applications/Viewers

Software for viewing images, documents and other (non-video) media.

Examples: gqview, evince, gthumb

 Applications/Video

Video players, editors, and rippers/recorders.

Examples: istanbul, totem, kino

 Applications/Web Development

Software for web site editing, web programming, and site administration.

Examples: bluefish, screem, gphpedit

Games Games and recreations Games/Action

Games that involve a lot of action and require fast reflexes.

Examples: xsoldier, supertux, xmoto

 Games/Adventure

Role playing and adventure games, interactive movies and stories, etc.

Examples: beneath-a-steel-sky, egoboo, kq

 Games/Blocks

Tetris-like games involving falling blocks.

Examples: crack-attack, frozen-bubble, netris

 Games/Board

Games played on a board.

Examples: phalanx, xshogi, xboard

 Games/Card

Games involving a deck of cards.

Examples: pysol, ace-of-penguins, xpat2

 Games/Puzzles

Tests of ingenuity and logic.

Examples: xmpuzzles, sgt-puzzles, enigma

 Games/Simulation

Simulations of the real world in all detail and complexity.

Examples: flightgear, torcs

 Games/Strategy

Games involving long-term strategic thinking.

Examples: wesnoth, widelands, netpanzer

 Games/Tools

Server browsers, configurators, editors, and other game-related tools that are not games themselves.

Examples: xqf, crystalspace

 Games/Toys

Amusements, eye-candy, entertaining demos, screen hacks (screensavers), etc.

Examples: xdesktopwaves, xphoon, xpenguins

 Help

programs that provide user documentation

Examples: debian-reference, apt-howto, dhelp

 Screen Programs that affect the whole screen. Screen/Saving

Tools for blanking the screen. Entries of screen hacks and configuration GUIs should go to other appropriate sections.

Examples: xscreensaver, xlockmore

 Screen/Locking

Tools for locking the screen.

Examples: xscreensaver, xlockmore

 Window Managers

X window managers.

Examples: fluxbox, metacity, waimea

 FVWM Modules

FVWM-based window manager modules. As only modules related to the running window-manager are displayed, do not create subsections for specific window-managers.

Examples: fvwm, fvwm-gnome, fvwm95

 Window Maker

This section is reserved for wmaker as a special case.

All wmaker specific entries must go here.

ubuntu-policy/policy.sgml0000644000175000017500000136443011216714224016335 0ustar cjwatsoncjwatson %versiondata; ]> Ubuntu Policy Manual The Debian Policy Mailing List The Ubuntu Developers Mailing List version &version;, &date; This manual describes the policy requirements for the Ubuntu distribution. This includes the structure and contents of the Ubuntu archive and several design issues of the operating system, as well as technical requirements that each package must satisfy to be included in the distribution. It is derived from the Debian Policy Manual. Copyright © 1996,1997,1998 Ian Jackson and Christian Schwarz.

This manual is free software; you may 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, or (at your option) any later version.

This 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.

A copy of the GNU General Public License is available as /usr/share/common-licenses/GPL in the Debian GNU/Linux distribution or on the World Wide Web at . You can also obtain it by writing to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.

About this manual Scope

This manual describes the policy requirements for the Ubuntu distribution. This includes the structure and contents of the Ubuntu archive and several design issues of the operating system, as well as technical requirements that each package must satisfy to be included in the distribution.

This manual also describes Ubuntu policy as it relates to creating Ubuntu packages. It is not a tutorial on how to build packages, nor is it exhaustive where it comes to describing the behavior of the packaging system. Instead, this manual attempts to define the interface to the package management system that the developers have to be conversant with. Informally, the criteria used for inclusion is that the material meet one of the following requirements: Standard interfaces The material presented represents an interface to the packaging system that is mandated for use, and is used by, a significant number of packages, and therefore should not be changed without peer review. Package maintainers can then rely on this interfaces not changing, and the package management software authors need to ensure compatibility with these interface definitions. (Control file and changelog file formats are examples.) Chosen Convention If there are a number of technically viable choices that can be made, but one needs to select one of these options for inter-operability. The version number format is one example. Please note that these are not mutually exclusive; selected conventions often become parts of standard interfaces.

The footnotes present in this manual are merely informative, and are not part of Ubuntu policy itself.

The appendices to this manual are not necessarily normative, either. Please see for more information.

In the normative part of this manual, the words must, should and may, and the adjectives required, recommended and optional, are used to distinguish the significance of the various guidelines in this policy document. Packages that do not conform to the guidelines denoted by must (or required) will generally not be considered acceptable for the Ubuntu distribution. Non-conformance with guidelines denoted by should (or recommended) will generally be considered a bug, but will not necessarily render a package unsuitable for distribution. Guidelines denoted by may (or optional) are truly optional and adherence is left to the maintainer's discretion.

These classifications are roughly equivalent to the bug severities serious (for must or required directive violations), minor, normal or important (for should or recommended directive violations) and wishlist (for optional items). Compare RFC 2119. Note, however, that these words are used in a different way in this document.

Much of the information presented in this manual will be useful even when building a package which is to be distributed in some other way or is intended for local use only.

The Ubuntu distribution differs from its parent Debian distribution in a number of significant ways. In this document, these are marked with the tag Ubuntu:.

New versions of this document

This manual is distributed via the Ubuntu package (packages.ubuntu.com /ubuntu-policy).

The ubuntu-policy package also includes the file upgrading-checklist.txt.gz which indicates policy changes between versions of this document.

Authors and Maintainers

Originally called "Debian GNU/Linux Policy Manual", this manual was initially written in 1996 by Ian Jackson. It was revised on November 27th, 1996 by David A. Morris. Christian Schwarz added new sections on March 15th, 1997, and reworked/restructured it in April-July 1997. Christoph Lameter contributed the "Web Standard". Julian Gilbey largely restructured it in 2001.

Since September 1998, the responsibility for the contents of the Debian version of this document lies on the . Proposals are discussed there and inserted into policy after a certain consensus is established. The actual editing is done by a group of maintainers that have no editorial powers. These are the current maintainers: Julian Gilbey Branden Robinson Josip Rodin Manoj Srivastava

The Ubuntu branch of this manual is maintained by the .

While the authors of this document have tried hard to avoid typos and other errors, these do still occur. If you discover an error in this manual or if you want to give any comments, suggestions, or criticisms please send an email to the Debian Policy List, debian-policy@lists.debian.org, or submit a bug report against the debian-policy package.

Please do not try to reach the individual authors or maintainers of the Policy Manual regarding changes to the Policy.

Related documents

There are several other documents other than this Policy Manual that are necessary to fully understand some Debian policies and procedures.

The external "sub-policy" documents are referred to in:

In addition to those, which carry the weight of policy, there is the Debian Developer's Reference. This document describes procedures and resources for Debian developers, but it is not normative; rather, it includes things that don't belong in the Policy, such as best practices for developers.

The Developer's Reference is available in the developers-reference package. It's also available from the Debian web mirrors at .

Definitions

The following terms are used in this Policy Manual: ASCII The character encoding specified by ANSI X3.4-1986 and its predecessor standards, referred to in MIME as US-ASCII, and corresponding to an encoding in eight bits per character of the first 128 characters, with the eighth bit always zero. UTF-8 The transformation format (sometimes called encoding) of defined by . UTF-8 has the useful property of having ASCII as a subset, so any text encoded in ASCII is trivially also valid UTF-8.

The Ubuntu Archive

The Ubuntu system is maintained and distributed as a collection of packages. Since there are so many of them (currently well over 15000), they are split into sections and given priorities to simplify the handling of them.

The effort of the Ubuntu project is to build a free operating system, but not every package we want to make accessible is free in our sense (see the Ubuntu Licensing Policy, below), or may be imported/exported without restrictions. Thus, the archive is split into areas The Ubuntu archive software uses the term "component" internally and in the Release file format to refer to the division of an archive. The Debian Social Contract simply refers to "areas." This document uses terminology similar to the Social Contract. based on their licenses and other restrictions. We also divide up packages based on whether they are supported or not.

The aims of this are: to allow us to make as much software available as we can to allow us to encourage everyone to write free software, and to allow us to make it easy for people to produce CD-ROMs of our system without violating any licenses, import/export restrictions, or any other laws.

The Ubuntu Licensing Policy

The Ubuntu Licensing Policy forms our definition of "free software". The following guidelines apply to the main and universe categories of the archive: Must include source code. The main and universe categories have a strict and non-negotiable requirement that application software included in them must come with full source code. Must allow modification and distribution of modified copies under the same license. Just having the source code does not convey the same freedom as having the right to change it. Without the ability to modify software, the Ubuntu community cannot support software, fix bugs, translate it, or improve it. The following additional guidelines apply to the main, restricted and universe categories of the archive: Must allow these rights to be passed on along with the software. You should be able to have exactly the same rights to the software as we do. Must not discriminate against persons, groups or against fields of endeavour. The license of software included in Ubuntu can not discriminate against anyone or any group of users and cannot restrict users from using the software for a particular field of endeavour - a business for example. Thus we will not distribute software that is licensed "freely for non-commercial use". Must not be distributed under a license specific to Ubuntu. The rights attached to the software must not depend on the programme's being part of Ubuntu system. So we will not distribute software for which Ubuntu has a "special" exemption or right, and we will not put our own software into Ubuntu and then refuse you the right to pass it on. The following additional guidelines apply to the entire archive: Must allow redistribution. Your right to sell or give away the software alone, or as part of an aggregate software distribution, is important because: You, the user, must be able to pass on any software you have received from Ubuntu in either source code or compiled form. While Ubuntu will not charge license fees for this distribution, you might well want to charge to print Ubuntu CD's, or create your own customized versions of Ubuntu which you sell, and should have the freedom to do so. Must not require royalty payments or any other fee for redistribution or modification. It's important that you can exercise your rights to this software without having to pay for the privilege, and that you can pass these rights on to other people on exactly the same basis. Must not contaminate other software licenses. The license must not place restrictions on other software that is distributed along with it. For example, the license must not insist that all other programmes distributed on the same medium be free software. May require source modifications to be distributed as patches. In some cases, software authors are happy for us to distribute their software and modifications to their software, as long as the two are distributed separately, so that people always have a copy of their pristine code. We are happy to respect this preference. However, the license must explicitly permit distribution of software built from modified source code. The "GPL," "BSD," and "Artistic" licenses are examples of licenses that we consider free.

Ubuntu contains licensed and copyrighted works that are not application software. For example, the default Ubuntu installation includes documentation, images, sounds, video clips and firmware. The Ubuntu community will make decisions on the inclusion of these works on a case-by-case basis, ensuring that these works do not restrict our ability to make Ubuntu available free of charge, and that Ubuntu remains re-distributable by you.

Archive areas The main archive area

Every package in main must comply with the Ubuntu Licensing Policy.

In addition, the packages in main must not require a package outside of main for compilation or execution (thus, the package must not declare a "Depends", "Recommends", or "Build-Depends" relationship on a non-main package), must not be so buggy that we refuse to support them, and must meet all policy requirements presented in this manual.

The restricted archive area

Every package in restricted must comply with the Ubuntu Licensing Policy, with the exceptions that source code may not be available and that modification may not be permitted.

In addition, the packages in restricted must not be so buggy that we refuse to support them, and must meet all policy requirements presented in this manual that it is possible for them to meet. It is possible that there are policy requirements which the package is unable to meet, for example, if the source is unavailable. These situations will need to be handled on a case-by-case basis.

The Ubuntu team recognises that many users have vital hardware in their computer that requires drivers that are currently only available in binary format. We urge all hardware vendors to insist that their suppliers provide open source drivers for their components, but we recognise that in some cases binary drivers are the only way to make your hardware work. As a result, Ubuntu includes several of these drivers on the CD and in the repository, clearly separated from the rest of the software by being placed in the restricted archive area.

Binary drivers are a poor choice, if you have a choice. Without source code, Ubuntu cannot support this software, we only provide it for users who require it to be able to run the Free Software we provide in main. Also, we cannot make binary drivers available on other architectures (such as the Mac or IPAQ) if we don't have the ability to port the software source code ourselves. If your hardware is fully supported with open source drivers you can simply remove the restricted archive area, and we would encourage you to do so.

The restricted archive area may not include application software, only hardware drivers.

The universe archive area

Every package in universe must comply with the Ubuntu Licensing Policy.

Packages in the universe archive area are not supported by the core Ubuntu developers and Canonical Ltd. Packages may be moved between main and universe as their support status changes.

In addition, the packages in universe must not require a package outside of main and universe for compilation or execution (thus, the package must not declare a "Depends", "Recommends", or "Build-Depends" relationship on a non-main and non-universe package), and must meet all policy requirements presented in this manual.

The multiverse archive area

Every package in multiverse must comply with the Ubuntu Licensing Policy, with the exceptions that source code may not be available, that modification may not be permitted, that rights may not be passed on along with the software, that they may discriminate against persons, groups or fields of endeavour, and that their license may be specific to Ubuntu. (In other words, they must be redistributable without a fee and must not contaminate other software licenses.)

Packages must be placed in multiverse if they are not compliant with the parts of the Ubuntu Licensing Policy that cover other categories of the archive, or if they are encumbered by patents or other legal issues that make their distribution problematic.

Packages in the multiverse archive area are not supported by the core Ubuntu developers and Canonical Ltd.

In addition, the packages in multiverse must not be so buggy that we refuse to support them, and must meet all policy requirements presented in this manual that it is possible for them to meet. It is possible that there are policy requirements which the package is unable to meet, for example, if the source is unavailable. These situations will need to be handled on a case-by-case basis.

Copyright considerations

Every package must be accompanied by a verbatim copy of its copyright and distribution license in the file /usr/share/doc/package/copyright (see for further details).

We reserve the right to restrict files from being included anywhere in our archives if their use or distribution would break a law, there is an ethical conflict in their distribution or use, we would have to sign a license for them, or their distribution would conflict with other project policies.

Programs whose authors encourage the user to make donations are fine for the main distribution, provided that the authors do not claim that not donating is immoral, unethical, illegal or something similar; in such a case they must go in multiverse.

Packages whose copyright permission notices (or patent problems) do not even allow redistribution of binaries only, and where no special permission has been obtained, must not be placed on the Ubuntu FTP site and its mirrors at all.

Note that under international copyright law (this applies in the United States, too), no distribution or modification of a work is allowed without an explicit notice saying so. Therefore a program without a copyright notice is copyrighted and you may not do anything to it without risking being sued! Likewise if a program has a copyright notice but no statement saying what is permitted then nothing is permitted.

Many authors are unaware of the problems that restrictive copyrights (or lack of copyright notices) can cause for the users of their supposedly-free software. It is often worthwhile contacting such authors diplomatically to ask them to modify their license terms. However, this can be a politically difficult thing to do and you should ask for advice on the ubuntu-archive mailing list first, as explained below.

When in doubt about a copyright, send mail to ubuntu-archive@lists.ubuntu.com. Be prepared to provide us with the copyright statement. Software covered by the GPL, public domain software and BSD-like copyrights are safe; be wary of the phrases "commercial use prohibited" and "distribution restricted".

Sections

The packages in the archive areas main, restricted, universe and multiverse are grouped further into sections to simplify handling.

The archive area and section for each package should be specified in the package's Section control record (see ). However, the maintainer of the Ubuntu archive may override this selection to ensure the consistency of the Ubuntu distribution. The Section field should be of the form: section if the package is in the main archive area, area/section if the package is in the restricted, universe or multiverse archive areas. Packages that originally came from the Debian archive will often not have Section fields matching the archive area selected for them in Ubuntu. There is no need to change the package just for this; the maintainers of the Ubuntu archive can and will override its placement.

The Ubuntu archive maintainers provide the authoritative list of sections. At present, they are: admin, cli-mono, comm, database, devel, debug, doc, editors, electronics, embedded, fonts, games, gnome, graphics, gnu-r, gnustep, hamradio, haskell, httpd, interpreters, java, kde, kernel, libs, libdevel, lisp, localization, mail, math, metapackages, misc, net, news, ocaml, oldlibs, otherosfs, perl, php, python, ruby, science, shells, sound, tex, text, utils, vcs, video, web, x11, xfce, zope.

Ubuntu: The metapackages section exists for the benefit of package management tools. When removing a package in that section, its dependencies will not be automatically considered for removal by tools which track the distinction between packages that were installed explicitly and packages that were only installed to satisfy dependencies.

Priorities

Each package should have a priority value, which is included in the package's control record (see ). This information is used by the Ubuntu package management tools to separate high-priority packages from less-important packages.

The following priority levels are recognized by the Ubuntu package management tools. required Packages which are necessary for the proper functioning of the system (usually, this means that dpkg functionality depends on these packages). Removing a required package may cause your system to become totally broken and you may not even be able to use dpkg to put things back, so only do so if you know what you are doing. Systems with only the required packages are probably unusable, but they do have enough functionality to allow the sysadmin to boot and install more software. important Important programs, including those which one would expect to find on any Unix-like system. If the expectation is that an experienced Unix person who found it missing would say "What on earth is going on, where is foo?", it must be an important package. This is an important criterion because we are trying to produce, amongst other things, a free Unix. Other packages without which the system will not run well or be usable must also have priority important. This does not include Emacs, the X Window System, TeX or any other large applications. The important packages are just a bare minimum of commonly-expected and necessary tools. standard These packages provide a reasonably small but not too limited character-mode system. This is what will be installed by default if the user doesn't select anything else. It doesn't include many large applications. optional (In a sense everything that isn't required is optional, but that's not what is meant here.) This is all the software that you might reasonably want to install if you didn't know what it was and don't have specialized requirements. This is a much larger system and includes the X Window System, a full TeX distribution, and many applications. Note that optional packages should not conflict with each other. extra This contains all packages that conflict with others with required, important, standard or optional priorities, or are only likely to be useful if you already know what they are or have specialized requirements (such as packages containing only detached debugging symbols).

Packages must not depend on packages with lower priority values (excluding build-time dependencies). In order to ensure this, the priorities of one or more packages may need to be adjusted.

Binary packages

The Ubuntu distribution is based on the Debian package management system, called dpkg. Thus, all packages in the Ubuntu distribution must be provided in the .deb file format.

The package name

Every package must have a name that's unique within the Ubuntu archive.

The package name is included in the control field Package, the format of which is described in . The package name is also included as a part of the file name of the .deb file.

The version of a package

Every package has a version number recorded in its Version control file field, described in .

The package management system imposes an ordering on version numbers, so that it can tell whether packages are being up- or downgraded and so that package system front end applications can tell whether a package it finds available is newer than the one installed on the system. The version number format has the most significant parts (as far as comparison is concerned) at the beginning.

If an upstream package has problematic version numbers they should be converted to a sane form for use in the Version field.

Version numbers based on dates

In general, Ubuntu packages should use the same version numbers as the upstream sources.

However, in some cases where the upstream version number is based on a date (e.g., a development "snapshot" release) the package management system cannot handle these version numbers without epochs. For example, dpkg will consider "96May01" to be greater than "96Dec24".

To prevent having to use epochs for every new upstream version, the date based portion of the version number should be changed to the following format in such cases: "19960501", "19961224". It is up to the maintainer whether they want to bother the upstream maintainer to change the version numbers upstream, too.

Note that other version formats based on dates which are parsed correctly by the package management system should not be changed.

Native Debian or Ubuntu packages (i.e., packages which have been written especially for Debian or Ubuntu) whose version numbers include dates should always use the "YYYYMMDD" format.

The maintainer of a package

Every package must have a Debian maintainer (the maintainer may be one person or a group of people reachable from a common email address, such as a mailing list). The maintainer is responsible for ensuring that the package is placed in the appropriate distributions.

The maintainer must be specified in the Maintainer control field with their correct name and a working email address. If one person maintains several packages, they should try to avoid having different forms of their name and email address in the Maintainer fields of those packages.

The format of the Maintainer control field is described in .

If the maintainer of a package quits from the Debian project, "Debian QA Group" packages@qa.debian.org takes over the maintainer-ship of the package until someone else volunteers for that task. These packages are called orphaned packages. The detailed procedure for doing this gracefully can be found in the Debian Developer's Reference, see .

Ubuntu: Packages that are modified in Ubuntu should have an Ubuntu-specific Maintainer field. This is in response to a poll of Debian maintainers, documented in the . All Ubuntu binary packages, and Ubuntu source packages that are modified relative to Debian (that is, its version number contains the string "ubuntu"), should have their Maintainer field adjusted as follows: If the Maintainer field contains an ubuntu.com email address, or one associated with an Ubuntu developer, then no modifications should be made. If the package is in main or restricted, the Maintainer field should be set to Ubuntu Core Developers ubuntu-devel-discuss@lists.ubuntu.com. If the package is in universe or multiverse, the Maintainer field should be set to Ubuntu MOTU Developers ubuntu-motu@lists.ubuntu.com. If the Maintainer field is modified, then the old value must be saved in a field named XSBC-Original-Maintainer. Because it is mandated and very common, it is not necessary or appropriate to document this change in debian/changelog, unless it is the only change involved in the upload.

The description of a package

Every Ubuntu package must have an extended description stored in the appropriate field of the control record. The technical information about the format of the Description field is in .

The description should describe the package (the program) to a user (system administrator) who has never met it before so that they have enough information to decide whether they want to install it. This description should not just be copied verbatim from the program's documentation.

Put important information first, both in the synopsis and extended description. Sometimes only the first part of the synopsis or of the description will be displayed. You can assume that there will usually be a way to see the whole extended description.

The description should also give information about the significant dependencies and conflicts between this package and others, so that the user knows why these dependencies and conflicts have been declared.

Instructions for configuring or using the package should not be included (that is what installation scripts, manual pages, info files, etc., are for). Copyright statements and other administrivia should not be included either (that is what the copyright file is for).

The single line synopsis

The single line synopsis should be kept brief - certainly under 80 characters.

Do not include the package name in the synopsis line. The display software knows how to display this already, and you do not need to state it. Remember that in many situations the user may only see the synopsis line - make it as informative as you can.

The extended description

Do not try to continue the single line synopsis into the extended description. This will not work correctly when the full description is displayed, and makes no sense where only the summary (the single line synopsis) is available.

The extended description should describe what the package does and how it relates to the rest of the system (in terms of, for example, which subsystem it is which part of).

The description field needs to make sense to anyone, even people who have no idea about any of the things the package deals with. The blurb that comes with a program in its announcements and/or README files is rarely suitable for use in a description. It is usually aimed at people who are already in the community where the package is used.

Dependencies

Every package must specify the dependency information about other packages that are required for the first to work correctly.

For example, a dependency entry must be provided for any shared libraries required by a dynamically-linked executable binary in a package.

Packages are not required to declare any dependencies they have on other packages which are marked Essential (see below), and should not do so unless they depend on a particular version of that package.

Essential is needed in part to avoid unresolvable dependency loops on upgrade. If packages add unnecessary dependencies on packages in this set, the chances that there will be an unresolvable dependency loop caused by forcing these Essential packages to be configured first before they need to be is greatly increased. It also increases the chances that frontends will be unable to calculate an upgrade path, even if one exists.

Also, functionality is rarely ever removed from the Essential set, but packages have been removed from the Essential set when the functionality moved to a different package. So depending on these packages just in case they stop being essential does way more harm than good.

Sometimes, a package requires another package to be installed and configured before it can be installed. In this case, you must specify a Pre-Depends entry for the package.

You should not specify a Pre-Depends entry for a package before this has been discussed on the ubuntu-devel mailing list and a consensus about doing that has been reached.

The format of the package interrelationship control fields is described in .

Virtual packages

Sometimes, there are several packages which offer more-or-less the same functionality. In this case, it's useful to define a virtual package whose name describes that common functionality. (The virtual packages only exist logically, not physically; that's why they are called virtual.) The packages with this particular function will then provide the virtual package. Thus, any other package requiring that function can simply depend on the virtual package without having to specify all possible packages individually.

All packages should use virtual package names where appropriate, and arrange to create new ones if necessary. They should not use virtual package names (except privately, amongst a cooperating group of packages) unless they have been agreed upon and appear in the list of virtual package names. (See also )

The latest version of the authoritative list of virtual package names can be found in the debian-policy package. It is also available from the Debian web mirrors at .

The procedure for updating the list is described in the preface to the list.

Base system

The base system is a minimum subset of the Ubuntu system that is installed before everything else on a new system. Only very few packages are allowed to form part of the base system, in order to keep the required disk usage very small.

The base system consists of all those packages with priority required or important. Many of them will be tagged essential (see below).

Essential packages

Essential is defined as the minimal set of functionality that must be available and usable on the system at all times, even when packages are in an unconfigured (but unpacked) state. Packages are tagged essential for a system using the Essential control file field. The format of the Essential control field is described in .

Since these packages cannot be easily removed (one has to specify an extra force option to dpkg to do so), this flag must not be used unless absolutely necessary. A shared library package must not be tagged essential; dependencies will prevent its premature removal, and we need to be able to remove it when it has been superseded.

Since dpkg will not prevent upgrading of other packages while an essential package is in an unconfigured state, all essential packages must supply all of their core functionality even when unconfigured. If the package cannot satisfy this requirement it must not be tagged as essential, and any packages depending on this package must instead have explicit dependency fields as appropriate.

Maintainers should take great care in adding any programs, interfaces, or functionality to essential packages. Packages may assume that functionality provided by essential packages is always available without declaring explicit dependencies, which means that removing functionality from the Essential set is very difficult and is almost never done. Any capability added to an essential package therefore creates an obligation to support that capability as part of the Essential set in perpetuity.

You must not tag any packages essential before this has been discussed on the ubuntu-devel mailing list and a consensus about doing that has been reached.

Maintainer Scripts

The package installation scripts should avoid producing output which is unnecessary for the user to see and should rely on dpkg to stave off boredom on the part of a user installing many packages. This means, amongst other things, using the --quiet option on install-info.

Errors which occur during the execution of an installation script must be checked and the installation must not continue after an error.

Note that in general applies to package maintainer scripts, too.

You should not use dpkg-divert on a file belonging to another package without consulting the maintainer of that package first.

All packages which supply an instance of a common command name (or, in general, filename) should generally use update-alternatives, so that they may be installed together. If update-alternatives is not used, then each package must use Conflicts to ensure that other packages are de-installed. (In this case, it may be appropriate to specify a conflict against earlier versions of something that previously did not use update-alternatives; this is an exception to the usual rule that versioned conflicts should be avoided.)

Prompting in maintainer scripts

Package maintainer scripts may prompt the user if necessary. Prompting must be done by communicating through a program, such as debconf, which conforms to the Debian Configuration Management Specification, version 2 or higher.

Packages which are essential, or which are dependencies of essential packages, may fall back on another prompting method if no such interface is available when they are executed.

The Debian Configuration Management Specification is included in the debconf_specification files in the debian-policy package. It is also available from the Debian web mirrors at .

Packages which use the Debian Configuration Management Specification may contain an additional config script and a templates file in their control archive The control.tar.gz inside the .deb. See . . The config script might be run before the preinst script, and before the package is unpacked or any of its dependencies or pre-dependencies are satisfied. Therefore it must work using only the tools present in essential packages. Debconf or another tool that implements the Debian Configuration Management Specification will also be installed, and any versioned dependencies on it will be satisfied before preconfiguration begins.

Packages which use the Debian Configuration Management Specification must allow for translation of their user-visible messages by using a gettext-based system such as the one provided by the po-debconf package.

Packages should try to minimize the amount of prompting they need to do, and they should ensure that the user will only ever be asked each question once. This means that packages should try to use appropriate shared configuration files (such as /etc/papersize and /etc/news/server), and shared debconf variables rather than each prompting for their own list of required pieces of information.

It also means that an upgrade should not ask the same questions again, unless the user has used dpkg --purge to remove the package's configuration. The answers to configuration questions should be stored in an appropriate place in /etc so that the user can modify them, and how this has been done should be documented.

If a package has a vitally important piece of information to pass to the user (such as "don't run me as I am, you must edit the following configuration files first or you risk your system emitting badly-formatted messages"), it should display this in the config or postinst script and prompt the user to hit return to acknowledge the message. Copyright messages do not count as vitally important (they belong in /usr/share/doc/package/copyright); neither do instructions on how to use a program (these should be in on-line documentation, where all the users can see them).

Any necessary prompting should almost always be confined to the config or postinst script. If it is done in the postinst, it should be protected with a conditional so that unnecessary prompting doesn't happen if a package's installation fails and the postinst is called with abort-upgrade, abort-remove or abort-deconfigure.

Source packages Standards conformance

Source packages should specify the most recent version number of this policy document with which your package complied when it was last updated.

This information may be used to file bug reports automatically if your package becomes too much out of date.

The version is specified in the Standards-Version control field. The format of the Standards-Version field is described in .

You should regularly, and especially if your package has become out of date, check for the newest Policy Manual available and update your package, if necessary. When your package complies with the new standards you should update the Standards-Version source package field and release it. See the file upgrading-checklist for information about policy which has changed between different versions of this document.

Package relationships

Source packages should specify which binary packages they require to be installed or not to be installed in order to build correctly. For example, if building a package requires a certain compiler, then the compiler should be specified as a build-time dependency.

It is not necessary to explicitly specify build-time relationships on a minimal set of packages that are always needed to compile, link and put in an Ubuntu package a standard "Hello World!" program written in C or C++. The required packages are called build-essential, and an informational list can be found in /usr/share/doc/build-essential/list (which is contained in the build-essential package). Rationale: This allows maintaining the list separately from the policy documents (the list does not need the kind of control that the policy documents do). Having a separate package allows one to install the build-essential packages on a machine, as well as allowing other packages such as tasks to require installation of the build-essential packages using the depends relation. The separate package allows bug reports against the list to be categorized separately from the policy management process in the BTS.

When specifying the set of build-time dependencies, one should list only those packages explicitly required by the build. It is not necessary to list packages which are required merely because some other package in the list of build-time dependencies depends on them. The reason for this is that dependencies change, and you should list all those packages, and only those packages that you need directly. What others need is their business. For example, if you only link against libimlib, you will need to build-depend on libimlib2-dev but not against any libjpeg* packages, even though libimlib2-dev currently depends on them: installation of libimlib2-dev will automatically ensure that all of its run-time dependencies are satisfied.

If build-time dependencies are specified, it must be possible to build the package and produce working binaries on a system with only essential and build-essential packages installed and also those required to satisfy the build-time relationships (including any implied relationships). In particular, this means that version clauses should be used rigorously in build-time relationships so that one cannot produce bad or inconsistently configured packages when the relationships are properly satisfied.

explains the technical details.

Changes to the upstream sources

If changes to the source code are made that are not specific to the needs of the Ubuntu system, they should be sent to the upstream authors in whatever form they prefer so as to be included in the upstream version of the package.

If you need to configure the package differently for Ubuntu or for Linux, and the upstream source doesn't provide a way to do so, you should add such configuration facilities (for example, a new autoconf test or #define) and send the patch to the upstream authors, with the default set to the way they originally had it. You can then easily override the default in your debian/rules or wherever is appropriate.

You should make sure that the configure utility detects the correct architecture specification string (refer to for details).

If you need to edit a Makefile where GNU-style configure scripts are used, you should edit the .in files rather than editing the Makefile directly. This allows the user to reconfigure the package if necessary. You should not configure the package and edit the generated Makefile! This makes it impossible for someone else to later reconfigure the package without losing the changes you made.

Ubuntu changelog: debian/changelog

Changes in the Ubuntu version of the package should be briefly explained in the Ubuntu changelog file debian/changelog.

Mistakes in changelogs are usually best rectified by making a new changelog entry rather than "rewriting history" by editing old changelog entries.

This includes modifications made in the Ubuntu package compared to the upstream one or the Debian package as well as other changes and updates to the package. Although there is nothing stopping an author who is also the Ubuntu maintainer from using this changelog for all their changes, it will have to be renamed if the Ubuntu and upstream maintainers become different people. In such a case, however, it might be better to maintain the package as a non-native package.

The format of the debian/changelog allows the package building tools to discover which version of the package is being built and find out other release-specific information.

That format is a series of entries like this: package (version) distribution(s); urgency=urgency [optional blank line(s), stripped] * change details more change details [blank line(s), included in output of dpkg-parsechangelog] * even more change details [optional blank line(s), stripped] -- maintainer name <email address>[two spaces] date

package and version are the source package name and version number.

distribution(s) lists the distributions where this version should be installed when it is uploaded - it is copied to the Distribution field in the .changes file. See .

urgency is the value for the Urgency field in the .changes file for the upload (see ). It is not possible to specify an urgency containing commas; commas are used to separate keyword=value settings in the dpkg changelog format (though there is currently only one useful keyword, urgency).

The change details may in fact be any series of lines starting with at least two spaces, but conventionally each change starts with an asterisk and a separating space and continuation lines are indented so as to bring them in line with the start of the text above. Blank lines may be used here to separate groups of changes, if desired.

If this upload resolves bugs recorded in the Debian Bug Tracking System (BTS), they may be automatically closed on the inclusion of this package into the Debian archive by including the string: closes: Bug#nnnnn in the change details. To be precise, the string should match the following Perl regular expression: /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i Then all of the bug numbers listed will be closed by the archive maintenance script (katie) using the version of the changelog entry. This information is conveyed via the Closes field in the .changes file (see ).

Ubuntu: If this upload resolves bugs recorded in Launchpad, they may be automatically closed on the inclusion of this package into the Ubuntu archive by including the string: LP: #nnnnn in the change details. To be precise, the string should match the following Perl regular expression: /lp:\s+\#\d+(?:,\s*\#\d+)*/i Then all of the bug numbers listed will be closed by the archive maintenance software using the version of the changelog entry. This information is conveyed via the Launchpad-Bugs-Fixed field in the .changes file (see ).

The maintainer name and email address used in the changelog should be the details of the person uploading this version. They are not necessarily those of the usual package maintainer. The information here will be copied to the Changed-By field in the .changes file (see ), and then later used to send an acknowledgement when the upload has been installed.

The date must be in RFC822 format This is generated by date -R. ; it must include the time zone specified numerically, with the time zone name or abbreviation optionally present as a comment in parentheses.

The first "title" line with the package name must start at the left hand margin. The "trailer" line with the maintainer and date details must be preceded by exactly one space. The maintainer details and the date must be separated by exactly two spaces.

The entire changelog must be encoded in UTF-8.

For more information on placement of the changelog files within binary packages, please see .

Copyright: debian/copyright

Every package must be accompanied by a verbatim copy of its copyright and distribution license in the file /usr/share/doc/package/copyright (see for further details). Also see for further considerations relayed to copyrights for packages.

Error trapping in makefiles

When make invokes a command in a makefile (including your package's upstream makefiles and debian/rules), it does so using sh. This means that sh's usual bad error handling properties apply: if you include a miniature script as one of the commands in your makefile you'll find that if you don't do anything about it then errors are not detected and make will blithely continue after problems.

Every time you put more than one shell command (this includes using a loop) in a makefile command you must make sure that errors are trapped. For simple compound commands, such as changing directory and then running a program, using && rather than semicolon as a command separator is sufficient. For more complex commands including most loops and conditionals you should include a separate set -e command at the start of every makefile command that's actually one of these miniature shell scripts.

Time Stamps

Maintainers should preserve the modification times of the upstream source files in a package, as far as is reasonably possible. The rationale is that there is some information conveyed by knowing the age of the file, for example, you could recognize that some documentation is very old by looking at the modification time, so it would be nice if the modification time of the upstream source would be preserved.

Restrictions on objects in source packages

The source package may not contain any hard links

This is not currently detected when building source packages, but only when extracting them.

Hard links may be permitted at some point in the future, but would require a fair amount of work.

, device special files, sockets or setuid or setgid files. Setgid directories are allowed.

Main building script: debian/rules

This file must be an executable makefile, and contains the package-specific recipes for compiling the package and building binary package(s) from the source.

It must start with the line #!/usr/bin/make -f, so that it can be invoked by saying its name rather than invoking make explicitly.

Since an interactive debian/rules script makes it impossible to auto-compile that package and also makes it hard for other people to reproduce the same binary package, all required targets MUST be non-interactive. At a minimum, required targets are the ones called by dpkg-buildpackage, namely, clean, binary, binary-arch, binary-indep, and build. It also follows that any target that these targets depend on must also be non-interactive.

The targets are as follows (required unless stated otherwise): build

The build target should perform all the configuration and compilation of the package. If a package has an interactive pre-build configuration routine, the Debianized source package must either be built after this has taken place (so that the binary package can be built without rerunning the configuration) or the configuration routine modified to become non-interactive. (The latter is preferable if there are architecture-specific features detected by the configuration routine.)

For some packages, notably ones where the same source tree is compiled in different ways to produce two binary packages, the build target does not make much sense. For these packages it is good enough to provide two (or more) targets (build-a and build-b or whatever) for each of the ways of building the package, and a build target that does nothing. The binary target will have to build the package in each of the possible ways and make the binary package out of each.

The build target must not do anything that might require root privilege.

The build target may need to run the clean target first - see below.

When a package has a configuration and build routine which takes a long time, or when the makefiles are poorly designed, or when build needs to run clean first, it is a good idea to touch build when the build process is complete. This will ensure that if debian/rules build is run again it will not rebuild the whole program. Another common way to do this is for build to depend on build-stamp and to do nothing else, and for the build-stamp target to do the building and to touch build-stamp on completion. This is especially useful if the build routine creates a file or directory called build; in such a case, build will need to be listed as a phony target (i.e., as a dependency of the .PHONY target). See the documentation of make for more information on phony targets.

build-arch (optional), build-indep (optional)

A package may also provide both of the targets build-arch and build-indep. The build-arch target, if provided, should perform all the configuration and compilation required for producing all architecture-dependant binary packages (those packages for which the body of the Architecture field in debian/control is not all). Similarly, the build-indep target, if provided, should perform all the configuration and compilation required for producing all architecture-independent binary packages (those packages for which the body of the Architecture field in debian/control is all). The build target should depend on those of the targets build-arch and build-indep that are provided in the rules file.

If one or both of the targets build-arch and build-indep are not provided, then invoking debian/rules with one of the not-provided targets as arguments should produce a exit status code of 2. Usually this is provided automatically by make if the target is missing.

The build-arch and build-indep targets must not do anything that might require root privilege.

binary, binary-arch, binary-indep

The binary target must be all that is necessary for the user to build the binary package(s) produced from this source package. It is split into two parts: binary-arch builds the binary packages which are specific to a particular architecture, and binary-indep builds those which are not.

binary may be (and commonly is) a target with no commands which simply depends on binary-arch and binary-indep.

Both binary-* targets should depend on the build target, or on the appropriate build-arch or build-indep target, if provided, so that the package is built if it has not been already. It should then create the relevant binary package(s), using dpkg-gencontrol to make their control files and dpkg-deb to build them and place them in the parent of the top level directory.

Both the binary-arch and binary-indep targets must exist. If one of them has nothing to do (which will always be the case if the source generates only a single binary package, whether architecture-dependent or not), it must still exist and must always succeed.

The binary targets must be invoked as root. The fakeroot package often allows one to build a package correctly even without being root.

clean

This must undo any effects that the build and binary targets may have had, except that it should leave alone any output files created in the parent directory by a run of a binary target.

If a build file is touched at the end of the build target, as suggested above, it should be removed as the first action that clean performs, so that running build again after an interrupted clean doesn't think that everything is already done.

The clean target may need to be invoked as root if binary has been invoked since the last clean, or if build has been invoked as root (since build may create directories, for example).

get-orig-source (optional)

This target fetches the most recent version of the original source package from a canonical archive site (via FTP or WWW, for example), does any necessary rearrangement to turn it into the original source tar file format described below, and leaves it in the current directory.

This target may be invoked in any directory, and should take care to clean up any temporary files it may have left.

This target is optional, but providing it if possible is a good idea.

patch (optional)

This target performs whatever additional actions are required to make the source ready for editing (unpacking additional upstream archives, applying patches, etc.). It is recommended to be implemented for any package where dpkg-source -x does not result in source ready for additional modification. See .

The build, binary and clean targets must be invoked with the current directory being the package's top-level directory.

Additional targets may exist in debian/rules, either as published or undocumented interfaces or for the package's internal use.

The architectures we build on and build for are determined by make variables using the utility dpkg-architecture. You can determine the Debian architecture and the GNU style architecture specification string for the build machine (the machine type we are building on) as well as for the host machine (the machine type we are building for). Here is a list of supported make variables: DEB_*_ARCH (the Debian architecture) DEB_*_GNU_TYPE (the GNU style architecture specification string) DEB_*_GNU_CPU (the CPU part of DEB_*_GNU_TYPE) DEB_*_GNU_SYSTEM (the System part of DEB_*_GNU_TYPE) where * is either BUILD for specification of the build machine or HOST for specification of the host machine.

Backward compatibility can be provided in the rules file by setting the needed variables to suitable default values; please refer to the documentation of dpkg-architecture for details.

It is important to understand that the DEB_*_ARCH string only determines which Debian architecture we are building on or for. It should not be used to get the CPU or system information; the GNU style variables should be used for that.

debian/rules and DEB_BUILD_OPTIONS

Supporting the standardized environment variable DEB_BUILD_OPTIONS is recommended. This variable can contain several flags to change how a package is compiled and built. Each flag must be in the form flag or flag=options. If multiple flags are given, they must be separated by whitespace. Some packages support any delimiter, but whitespace is the easiest to parse inside a makefile and avoids ambiguity with flag values that contain commas. flag must start with a lowercase letter (a-z) and consist only of lowercase letters, numbers (0-9), and the characters - and _ (hyphen and underscore). options must not contain whitespace. The same tag should not be given multiple times with conflicting values. Package maintainers may assume that DEB_BUILD_OPTIONS will not contain conflicting tags.

The meaning of the following tags has been standardized: nocheck This tag says to not run any build-time test suite provided by the package. noopt The presence of this tag means that the package should be compiled with a minimum of optimization. For C programs, it is best to add -O0 to CFLAGS (although this is usually the default). Some programs might fail to build or run at this level of optimization; it may be necessary to use -O1, for example. nostrip This tag means that the debugging symbols should not be stripped from the binary during installation, so that debugging information may be included in the package. parallel=n This tag means that the package should be built using up to n parallel processes if the package build system supports this. Packages built with make can often implement this by passing the -jn option to make. If the package build system does not support parallel builds, this string must be ignored. If the package build system only supports a lower level of concurrency than n, the package should be built using as many parallel processes as the package build system supports. It is up to the package maintainer to decide whether the package build times are long enough and the package build system is robust enough to make supporting parallel builds worthwhile.

Unknown flags must be ignored by debian/rules.

The following makefile snippet is an example of how one may implement the build options; you will probably have to massage this example in order to make it work for your package. CFLAGS = -Wall -g INSTALL = install INSTALL_FILE = $(INSTALL) -p -o root -g root -m 644 INSTALL_PROGRAM = $(INSTALL) -p -o root -g root -m 755 INSTALL_SCRIPT = $(INSTALL) -p -o root -g root -m 755 INSTALL_DIR = $(INSTALL) -p -d -o root -g root -m 755 ifneq (,$(filter noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0 else CFLAGS += -O2 endif ifeq (,$(filter nostrip,$(DEB_BUILD_OPTIONS))) INSTALL_PROGRAM += -s endif ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) MAKEFLAGS += -j$(NUMJOBS) endif build: # ... ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) # Code to run the package test suite. endif

Variable substitutions: debian/substvars

When dpkg-gencontrol, dpkg-genchanges and dpkg-source generate control files they perform variable substitutions on their output just before writing it. Variable substitutions have the form ${variable}. The optional file debian/substvars contains variable substitutions to be used; variables can also be set directly from debian/rules using the -V option to the source packaging commands, and certain predefined variables are also available.

The debian/substvars file is usually generated and modified dynamically by debian/rules targets, in which case it must be removed by the clean target.

See for full details about source variable substitutions, including the format of debian/substvars.

 Optional upstream source location: debian/watch

This is an optional, recommended control file for the uscan utility which defines how to automatically scan ftp or http sites for newly available updates of the package. This is used by and other Debian QA tools to help with quality control and maintenance of the distribution as a whole.

Generated files list: debian/files

This file is not a permanent part of the source tree; it is used while building packages to record which files are being generated. dpkg-genchanges uses it when it generates a .changes file.

It should not exist in a shipped source package, and so it (and any backup files or temporary files such as files.new files.new is used as a temporary file by dpkg-gencontrol and dpkg-distaddfile - they write a new version of files here before renaming it, to avoid leaving a corrupted copy if an error occurs. ) should be removed by the clean target. It may also be wise to ensure a fresh start by emptying or removing it at the start of the binary target.

When dpkg-gencontrol is run for a binary package, it adds an entry to debian/files for the .deb file that will be created when dpkg-deb --build is run for that binary package. So for most packages all that needs to be done with this file is to delete it in the clean target.

If a package upload includes files besides the source package and any binary packages whose control files were made with dpkg-gencontrol then they should be placed in the parent of the package's top-level directory and dpkg-distaddfile should be called to add the file to the list in debian/files.

 Convenience copies of code

Some software packages include in their distribution convenience copies of code from other software packages, generally so that users compiling from source don't have to download multiple packages. Ubuntu packages should not make use of these convenience copies unless the included package is explicitly intended to be used in this way. For example, parts of the GNU build system work like this. If the included code is already in the Ubuntu archive in the form of a library, the Ubuntu packaging should ensure that binary packages reference the libraries already in Ubuntu and the convenience copy is not used. If the included code is not already in Ubuntu, it should be packaged separately as a prerequisite if possible. Having multiple copies of the same code in Ubuntu is inefficient, often creates either static linking or shared library conflicts, and, most importantly, increases the difficulty of handling security vulnerabilities in the duplicated code.

Source package handling: debian/README.source

If running dpkg-source -x on a source package doesn't produce the source of the package, ready for editing, and allow one to make changes and run dpkg-buildpackage to produce a modified package without taking any additional steps, creating a debian/README.source documentation file is recommended. This file should explain how to do all of the following: Generate the fully patched source, in a form ready for editing, that would be built to create Ubuntu packages. Doing this with a patch target in debian/rules is recommended; see . Modify the source and save those modifications so that they will be applied when building the package. Remove source modifications that are currently being applied when building the package. Optionally, document what steps are necessary to upgrade the Ubuntu source package to a new upstream version, if applicable. This explanation should include specific commands and mention any additional required Ubuntu packages. It should not assume familiarity with any specific Ubuntu packaging system or patch management tools.

This explanation may refer to a documentation file installed by one of the package's build dependencies provided that the referenced documentation clearly explains these tasks and is not a general reference manual.

debian/README.source may also include any other information that would be helpful to someone modifying the source package. Even if the package doesn't fit the above description, maintainers are encouraged to document in a debian/README.source file any source package with a particularly complex or unintuitive source layout or build system (for example, a package that builds the same source multiple times to generate different binary packages).

Control files and their fields

The package management system manipulates data represented in a common format, known as control data, stored in control files. Control files are used for source packages, binary packages and the .changes files which control the installation of uploaded files dpkg's internal databases are in a similar format. .

Syntax of control files

A control file consists of one or more paragraphs of fields The paragraphs are also sometimes referred to as stanzas. . The paragraphs are separated by blank lines. Some control files allow only one paragraph; others allow several, in which case each paragraph usually refers to a different package. (For example, in source packages, the first paragraph refers to the source package, and later paragraphs refer to binary packages generated from the source.)

Each paragraph consists of a series of data fields; each field consists of the field name, followed by a colon and then the data/value associated with that field. It ends at the end of the (logical) line. Horizontal whitespace (spaces and tabs) may occur immediately before or after the value and is ignored there; it is conventional to put a single space after the colon. For example, a field might be: Package: libc6 the field name is Package and the field value libc6.

Many fields' values may span several lines; in this case each continuation line must start with a space or a tab. Any trailing spaces or tabs at the end of individual lines of a field value are ignored.

In fields where it is specified that lines may not wrap, only a single line of data is allowed and whitespace is not significant in a field body. Whitespace must not appear inside names (of packages, architectures, files or anything else) or version numbers, or between the characters of multi-character version relationships.

Field names are not case-sensitive, but it is usual to capitalize the field names using mixed case as shown below.

Blank lines, or lines consisting only of spaces and tabs, are not allowed within field values or between fields - that would mean a new paragraph.

All control files must be encoded in UTF-8.

Source package control files -- debian/control

The debian/control file contains the most vital (and version-independent) information about the source package and about the binary packages it creates.

The first paragraph of the control file contains information about the source package in general. The subsequent sets each describe a binary package that the source tree builds.

The fields in the general paragraph (the first one, for the source package) are: Source (mandatory) Maintainer (mandatory) Uploaders Section (recommended) Priority (recommended) Build-Depends et al Standards-Version (recommended) Homepage

The fields in the binary package paragraphs are: Package (mandatory) Architecture (mandatory) Section (recommended) Priority (recommended) Essential Depends et al Description (mandatory) Homepage

The syntax and semantics of the fields are described below.

These fields are used by dpkg-gencontrol to generate control files for binary packages (see below), by dpkg-genchanges to generate the .changes file to accompany the upload, and by dpkg-source when it creates the .dsc source control file as part of a source archive. Many fields are permitted to span multiple lines in debian/control but not in any other control file. These tools are responsible for removing the line breaks from such fields when using fields from debian/control to generate other control files.

The fields here may contain variable references - their values will be substituted by dpkg-gencontrol, dpkg-genchanges or dpkg-source when they generate output control files. See for details.

In addition to the control file syntax described above, this file may also contain comment lines starting with # without any preceding whitespace. All such lines are ignored, even in the middle of continuation lines for a multiline field, and do not end a multiline field.

Binary package control files -- DEBIAN/control

The DEBIAN/control file contains the most vital (and version-dependent) information about a binary package.

The fields in this file are: Package (mandatory) Source Version (mandatory) Section (recommended) Priority (recommended) Architecture (mandatory) Essential Depends et al Installed-Size Maintainer (mandatory) Description (mandatory) Homepage

Debian source control files -- .dsc

This file contains a series of fields, identified and separated just like the fields in the control file of a binary package. The fields are listed below; their syntax is described above, in . Format (mandatory) Source (mandatory) Version (mandatory) Maintainer (mandatory) Uploaders Binary Architecture Build-Depends et al Standards-Version (recommended) Files (mandatory) Homepage

The source package control file is generated by dpkg-source when it builds the source archive, from other files in the source package, described above. When unpacking, it is checked against the files and directories in the other parts of the source package.

Debian changes files -- .changes

The .changes files are used by the Ubuntu archive maintenance software to process updates to packages. They contain one paragraph which contains information from the debian/control file and other data about the source package gathered via debian/changelog and debian/rules.

The fields in this file are: Format (mandatory) Date (mandatory) Source (mandatory) Binary (mandatory) Architecture (mandatory) Version (mandatory) Distribution (mandatory) Urgency (recommended) Maintainer (mandatory) Changed-By Description (mandatory) Closes Launchpad-Bugs-Fixed Changes (mandatory) Files (mandatory)

List of fields Source

This field identifies the source package name.

In debian/control or a .dsc file, this field must contain only the name of the source package.

In a binary package control file or a .changes file, the source package name may be followed by a version number in parentheses It is customary to leave a space after the package name if a version number is specified. . This version number may be omitted (and is, by dpkg-gencontrol) if it has the same value as the Version field of the binary package in question. The field itself may be omitted from a binary package control file when the source package has the same name and version as the binary package.

Package names must consist only of lower case letters (a-z), digits (0-9), plus (+) and minus (-) signs, and periods (.). They must be at least two characters long and must start with an alphanumeric character.

Maintainer

The package maintainer's name and email address. The name should come first, then the email address inside angle brackets <> (in RFC822 format).

If the maintainer's name contains a full stop then the whole field will not work directly as an email address due to a misfeature in the syntax specified in RFC822; a program using this field as an address must check for this and correct the problem if necessary (for example by putting the name in round brackets and moving it to the end, and bringing the email address forward).

Uploaders

List of the names and email addresses of co-maintainers of the package, if any. If the package has other maintainers beside the one named in the Maintainer field, their names and email addresses should be listed here. The format is the same as that of the Maintainer tag, and multiple entries should be comma separated. Currently, this field is restricted to a single line of data. This is an optional field.

Any parser that interprets the Uploaders field in debian/control must permit it to span multiple lines. Line breaks in an Uploaders field that spans multiple lines are not significant and the semantics of the field are the same as if the line breaks had not been present.

Changed-By

The name and email address of the person who changed the said package. Usually the name of the maintainer. All the rules for the Maintainer field apply here, too.

Section

This field specifies an application area into which the package has been classified. See .

When it appears in the debian/control file, it gives the value for the subfield of the same name in the Files field of the .changes file. It also gives the default for the same field in the binary packages.

Priority

This field represents how important that it is that the user have the package installed. See .

When it appears in the debian/control file, it gives the value for the subfield of the same name in the Files field of the .changes file. It also gives the default for the same field in the binary packages.

Package

The name of the binary package.

Package names must consist only of lower case letters (a-z), digits (0-9), plus (+) and minus (-) signs, and periods (.). They must be at least two characters long and must start with an alphanumeric character.

Architecture

Depending on context and the control file used, the Architecture field can include the following sets of values: A unique single word identifying a Debian machine architecture, see . all, which indicates an architecture-independent package. any, which indicates a package available for building on any architecture. source, which indicates a source package.

In the main debian/control file in the source package, or in the source package control file .dsc, one may specify a list of architectures separated by spaces, or the special values any or all.

Specifying any indicates that the source package isn't dependent on any particular architecture and should compile fine on any one. The produced binary package(s) will be specific to whatever the current build architecture is. This is the most often used setting, and is recommended for new packages that aren't Architecture: all.

Specifying a list of architectures indicates that the source will build an architecture-dependent package, and will only work correctly on the listed architectures. This is a setting used for a minority of cases where the program is not portable. Generally, it should not be used for new packages.

In a .changes file, the Architecture field lists the architecture(s) of the package(s) currently being uploaded. This will be a list; if the source for the package is also being uploaded, the special entry source is also present.

See for information how to get the architecture for the build process.

Essential

This is a boolean field which may occur only in the control file of a binary package or in a per-package fields paragraph of a main source control data file.

If set to yes then the package management system will refuse to remove the package (upgrading and replacing it is still possible). The other possible value is no, which is the same as not having the field at all.

Package interrelationship fields: Depends, Pre-Depends, Recommends, Suggests, Breaks, Conflicts, Provides, Replaces, Enhances

These fields describe the package's relationships with other packages. Their syntax and semantics are described in .

 Standards-Version

The most recent version of the standards (the policy manual and associated texts) with which the package complies.

The version number has four components: major and minor version number and major and minor patch level. When the standards change in a way that requires every package to change the major number will be changed. Significant changes that will require work in many packages will be signaled by a change to the minor number. The major patch level will be changed for any change to the meaning of the standards, however small; the minor patch level will be changed when only cosmetic, typographical or other edits are made which neither change the meaning of the document nor affect the contents of packages.

Thus only the first three components of the policy version are significant in the Standards-Version control field, and so either these three components or the all four components may be specified. In the past, people specified the full version number in the Standards-Version field, for example "2.3.0.0". Since minor patch-level changes don't introduce new policy, it was thought it would be better to relax policy and only require the first 3 components to be specified, in this example "2.3.0". All four components may still be used if someone wishes to do so.

Ubuntu: Packages should not include the Ubuntu revision of the policy manual (e.g. "ubuntu1" in "3.8.0.1ubuntu1") in their Standards-Version field. This tends to create unnecessary diffs relative to Debian. For the same reason, Ubuntu developers should not generally change the Standards-Version field in packages originating in Debian.

Version

The version number of a package. The format is: [epoch:]upstream_version[-debian_revision]

The three components here are: epoch

This is a single (generally small) unsigned integer. It may be omitted, in which case zero is assumed. If it is omitted then the upstream_version may not contain any colons.

It is provided to allow mistakes in the version numbers of older versions of a package, and also a package's previous version numbering schemes, to be left behind.

upstream_version

This is the main part of the version number. It is usually the version number of the original ("upstream") package from which the .deb file has been made, if this is applicable. Usually this will be in the same format as that specified by the upstream author(s); however, it may need to be reformatted to fit into the package management system's format and comparison scheme.

The comparison behavior of the package management system with respect to the upstream_version is described below. The upstream_version portion of the version number is mandatory.

The upstream_version may contain only alphanumerics Alphanumerics are A-Za-z0-9 only. and the characters . + - : ~ (full stop, plus, hyphen, colon, tilde) and should start with a digit. If there is no debian_revision then hyphens are not allowed; if there is no epoch then colons are not allowed.

debian_revision

This part of the version number specifies the version of the Ubuntu package based on the upstream version. It may contain only alphanumerics and the characters + . ~ (plus, full stop, tilde) and is compared in the same way as the upstream_version is.

It is optional; if it isn't present then the upstream_version may not contain a hyphen. This format represents the case where a piece of software was written specifically to be turned into a Debian or Ubuntu package, and so there is only one "debianisation" of it and therefore no revision indication is required.

It is conventional to restart the debian_revision at 1 each time the upstream_version is increased.

The package management system will break the version number apart at the last hyphen in the string (if there is one) to determine the upstream_version and debian_revision. The absence of a debian_revision is equivalent to a debian_revision of 0.

Ubuntu: The string "ubuntu" in a version number instructs the archive management software not to copy newer versions of the package from Debian automatically. It should therefore be used when modifying packages relative to Debian, taking care that the Ubuntu version number compares less than the next expected version in Debian. For example, the first Ubuntu modification of version 1.0-1 in Debian would be 1.0-1ubuntu1.

When comparing two version numbers, first the epoch of each are compared, then the upstream_version if epoch is equal, and then debian_revision if upstream_version is also equal. epoch is compared numerically. The upstream_version and debian_revision parts are compared by the package management system using the following algorithm:

The strings are compared from left to right.

First the initial part of each string consisting entirely of non-digit characters is determined. These two parts (one of which may be empty) are compared lexically. If a difference is found it is returned. The lexical comparison is a comparison of ASCII values modified so that all the letters sort earlier than all the non-letters and so that a tilde sorts before anything, even the end of a part. For example, the following parts are in sorted order from earliest to latest: ~~, ~~a, ~, the empty part, a. One common use of ~ is for upstream pre-releases. For example, 1.0~beta1~svn1245 sorts earlier than 1.0~beta1, which sorts earlier than 1.0.

Then the initial part of the remainder of each string which consists entirely of digit characters is determined. The numerical values of these two parts are compared, and any difference found is returned as the result of the comparison. For these purposes an empty string (which can only occur at the end of one or both version strings being compared) counts as zero.

These two steps (comparing and removing initial non-digit strings and initial digit strings) are repeated until a difference is found or both strings are exhausted.

Note that the purpose of epochs is to allow us to leave behind mistakes in version numbering, and to cope with situations where the version numbering scheme changes. It is not intended to cope with version numbers containing strings of letters which the package management system cannot interpret (such as ALPHA or pre-), or with silly orderings (the author of this manual has heard of a package whose versions went 1.1, 1.2, 1.3, 1, 2.1, 2.2, 2 and so forth).

Description

In a source or binary control file, the Description field contains a description of the binary package, consisting of two parts, the synopsis or the short description, and the long description. The field's format is as follows:

Description: <single line synopsis> <extended description over several lines>

The lines in the extended description can have these formats:

Those starting with a single space are part of a paragraph. Successive lines of this form will be word-wrapped when displayed. The leading space will usually be stripped off. Those starting with two or more spaces. These will be displayed verbatim. If the display cannot be panned horizontally, the displaying program will line wrap them "hard" (i.e., without taking account of word breaks). If it can they will be allowed to trail off to the right. None, one or two initial spaces may be deleted, but the number of spaces deleted from each line will be the same (so that you can have indenting work correctly, for example). Those containing a single space followed by a single full stop character. These are rendered as blank lines. This is the only way to get a blank line Completely empty lines will not be rendered as blank lines. Instead, they will cause the parser to think you're starting a whole new record in the control file, and will therefore likely abort with an error. . Those containing a space, a full stop and some more characters. These are for future expansion. Do not use them.

Do not use tab characters. Their effect is not predictable.

See for further information on this.

In a .changes file, the Description field contains a summary of the descriptions for the packages being uploaded.

The part of the field before the first newline is empty; thereafter each line has the name of a binary package and the summary description line from that binary package. Each line is indented by one space.

Distribution

In a .changes file or parsed changelog output this contains the (space-separated) name(s) of the distribution(s) where this version of the package should be installed. Valid distributions are determined by the archive maintainers. Current distribution names are: stable This is the current "released" version of Debian GNU/Linux. Once the distribution is stable only security fixes and other major bug fixes are allowed. When changes are made to this distribution, the release number is increased (for example: 2.2r1 becomes 2.2r2 then 2.2r3, etc). unstable This distribution value refers to the developmental part of the Debian distribution tree. New packages, new upstream versions of packages and bug fixes go into the unstable directory tree. Download from this distribution at your own risk. testing This distribution value refers to the testing part of the Debian distribution tree. It receives its packages from the unstable distribution after a short time lag to ensure that there are no major issues with the unstable packages. It is less prone to breakage than unstable, but still risky. It is not possible to upload packages directly to testing. frozen From time to time, the testing distribution enters a state of "code-freeze" in anticipation of release as a stable version. During this period of testing only fixes for existing or newly-discovered bugs will be allowed. The exact details of this stage are determined by the Release Manager. experimental The packages with this distribution value are deemed by their maintainers to be high risk. Oftentimes they represent early beta or developmental packages from various sources that the maintainers want people to try, but are not ready to be a part of the other parts of the Debian distribution tree. Download at your own risk.

You should list all distributions that the package should be installed into.

More information is available in the Debian Developer's Reference, section "The Debian archive".

Date

This field includes the date the package was built or last edited.

The value of this field is usually extracted from the debian/changelog file - see ).

Format

This field specifies a format revision for the file. The most current format described in the Policy Manual is version 1.5. The syntax of the format value is the same as that of a package version number except that no epoch or Debian revision is allowed - see .

Urgency

This is a description of how important it is to upgrade to this version from previous ones. It consists of a single keyword taking one of the values low, medium, high, emergency, or critical Other urgency values are supported with configuration changes in the archive software but are not used in Ubuntu. The urgency affects how quickly a package will be considered for inclusion into the testing distribution and gives an indication of the importance of any fixes included in the upload. Emergency and critical are treated as synonymous. (not case-sensitive) followed by an optional commentary (separated by a space) which is usually in parentheses. For example: Urgency: low (HIGH for users of diversions)

The value of this field is usually extracted from the debian/changelog file - see .

Changes

This field contains the human-readable changes data, describing the differences between the last version and the current one.

There should be nothing in this field before the first newline; all the subsequent lines must be indented by at least one space; blank lines must be represented by a line consisting only of a space and a full stop.

The value of this field is usually extracted from the debian/changelog file - see ).

Each version's change information should be preceded by a "title" line giving at least the version, distribution(s) and urgency, in a human-readable way.

If data from several versions is being returned the entry for the most recent version should be returned first, and entries should be separated by the representation of a blank line (the "title" line may also be followed by the representation of blank line).

Binary

This field is a list of binary packages.

When it appears in the .dsc file it is the list of binary packages which a source package can produce. It does not necessarily produce all of these binary packages for every architecture. The source control file doesn't contain details of which architectures are appropriate for which of the binary packages.

When it appears in a .changes file it lists the names of the binary packages actually being uploaded.

The syntax is a list of binary packages separated by commas A space after each comma is conventional. . Currently the packages must be separated using only spaces in the .changes file.

Installed-Size

This field appears in the control files of binary packages, and in the Packages files. It gives the total amount of disk space required to install the named package.

The disk space is represented in kilobytes as a simple decimal number.

Files

This field contains a list of files with information about each one. The exact information and syntax varies with the context. In all cases the part of the field contents on the same line as the field name is empty. The remainder of the field is one line per file, each line being indented by one space and containing a number of sub-fields separated by spaces.

In the .dsc file, each line contains the MD5 checksum, size and filename of the tar file and (if applicable) diff file which make up the remainder of the source package That is, the parts which are not the .dsc. . The exact forms of the filenames are described in .

In the .changes file this contains one line per file being uploaded. Each line contains the MD5 checksum, size, section and priority and the filename. The section and priority are the values of the corresponding fields in the main source control file. If no section or priority is specified then - should be used, though section and priority values must be specified for new packages to be installed properly.

The special value byhand for the section in a .changes file indicates that the file in question is not an ordinary package file and must by installed by hand by the distribution maintainers. If the section is byhand the priority should be -.

If a new Ubuntu revision of a package is being shipped and no new original source archive is being distributed the .dsc must still contain the Files field entry for the original source archive package-upstream-version.orig.tar.gz, but the .changes file should leave it out. In this case the original source archive on the distribution site must match exactly, byte-for-byte, the original source archive which was used to generate the .dsc file and diff which are being uploaded.

 Closes

A space-separated list of Debian bug report numbers that the upload governed by the .changes file closes.

Launchpad-Bugs-Fixed

A space-separated list of Launchpad bug report numbers that the upload governed by the .changes file closes.

Homepage

The URL of the web site for this package, preferably (when applicable) the site from which the original source can be obtained and any additional upstream documentation or information may be found. The content of this field is a simple URL without any surrounding characters such as <>.

User-defined fields

Additional user-defined fields may be added to the source package control file. Such fields will be ignored, and not copied to (for example) binary or source package control files or upload control files.

If you wish to add additional unsupported fields to these output files you should use the mechanism described here.

Fields in the main source control information file with names starting X, followed by one or more of the letters BCS and a hyphen -, will be copied to the output files. Only the part of the field name after the hyphen will be used in the output file. Where the letter B is used the field will appear in binary package control files, where the letter S is used in source package control files and where C is used in upload control (.changes) files.

For example, if the main source information control file contains the field XBS-Comment: I stand between the candle and the star. then the binary and source package control files will contain the field Comment: I stand between the candle and the star.

Package maintainer scripts and installation procedure Introduction to package maintainer scripts

It is possible to supply scripts as part of a package which the package management system will run for you when your package is installed, upgraded or removed.

These scripts are the files preinst, postinst, prerm and postrm in the control area of the package. They must be proper executable files; if they are scripts (which is recommended), they must start with the usual #! convention. They should be readable and executable by anyone, and must not be world-writable.

The package management system looks at the exit status from these scripts. It is important that they exit with a non-zero status if there is an error, so that the package management system can stop its processing. For shell scripts this means that you almost always need to use set -e (this is usually true when writing shell scripts, in fact). It is also important, of course, that they exit with a zero status if everything went well.

Additionally, packages interacting with users using debconf in the postinst script should install a config script in the control area, see for details.

When a package is upgraded a combination of the scripts from the old and new packages is called during the upgrade procedure. If your scripts are going to be at all complicated you need to be aware of this, and may need to check the arguments to your scripts.

Broadly speaking the preinst is called before (a particular version of) a package is installed, and the postinst afterwards; the prerm before (a version of) a package is removed and the postrm afterwards.

Programs called from maintainer scripts should not normally have a path prepended to them. Before installation is started, the package management system checks to see if the programs ldconfig, start-stop-daemon, install-info, and update-rc.d can be found via the PATH environment variable. Those programs, and any other program that one would expect to be in the PATH, should thus be invoked without an absolute pathname. Maintainer scripts should also not reset the PATH, though they might choose to modify it by prepending or appending package-specific directories. These considerations really apply to all shell scripts.

 Maintainer scripts idempotency

It is necessary for the error recovery procedures that the scripts be idempotent. This means that if it is run successfully, and then it is called again, it doesn't bomb out or cause any harm, but just ensures that everything is the way it ought to be. If the first call failed, or aborted half way through for some reason, the second call should merely do the things that were left undone the first time, if any, and exit with a success status if everything is OK. This is so that if an error occurs, the user interrupts dpkg or some other unforeseen circumstance happens you don't leave the user with a badly-broken package when dpkg attempts to repeat the action.

Controlling terminal for maintainer scripts

The maintainer scripts are guaranteed to run with a controlling terminal and can interact with the user. Because these scripts may be executed with standard output redirected into a pipe for logging purposes, Perl scripts should set unbuffered output by setting $|=1 so that the output is printed immediately rather than being buffered.

Exit status

Each script must return a zero exit status for success, or a nonzero one for failure, since the package management system looks for the exit status of these scripts and determines what action to take next based on that datum.

Summary of ways maintainer scripts are called

new-preinst install new-preinst install old-version new-preinst upgrade old-version old-preinst abort-upgrade new-version

postinst configure most-recently-configured-version old-postinst abort-upgrade new-version conflictor's-postinst abort-remove in-favour package new-version postinst abort-remove deconfigured's-postinst abort-deconfigure in-favour failed-install-package version [removing conflicting-package version]

prerm remove old-prerm upgrade new-version new-prerm failed-upgrade old-version conflictor's-prerm remove in-favour package new-version deconfigured's-prerm deconfigure in-favour package-being-installed version [removing conflicting-package version]

postrm remove postrm purge old-postrm upgrade new-version new-postrm failed-upgrade old-version new-postrm abort-install new-postrm abort-install old-version new-postrm abort-upgrade old-version disappearer's-postrm disappear overwriter overwriter-version

Details of unpack phase of installation or upgrade

The procedure on installation/upgrade/overwrite/disappear (i.e., when running dpkg --unpack, or the unpack stage of dpkg --install) is as follows. In each case, if a major error occurs (unless listed below) the actions are, in general, run backwards - this means that the maintainer scripts are run with different arguments in reverse order. These are the "error unwind" calls listed below. If a version of the package is already installed, call old-prerm upgrade new-version If the script runs but exits with a non-zero exit status, dpkg will attempt: new-prerm failed-upgrade old-version If this works, the upgrade continues. If this does not work, the error unwind: old-postinst abort-upgrade new-version If this works, then the old-version is "Installed", if not, the old version is in a "Failed-Config" state. If a "conflicting" package is being removed at the same time, or if any package will be broken (due to Breaks): If --auto-deconfigure is specified, call, for each package to be deconfigured due to Breaks: deconfigured's-prerm deconfigure \ in-favour package-being-installed version Error unwind: deconfigured's-postinst abort-deconfigure \ in-favour package-being-installed-but-failed version The deconfigured packages are marked as requiring configuration, so that if --install is used they will be configured again if possible. If any packages depended on a conflicting package being removed and --auto-deconfigure is specified, call, for each such package: deconfigured's-prerm deconfigure \ in-favour package-being-installed version \ removing conflicting-package version Error unwind: deconfigured's-postinst abort-deconfigure \ in-favour package-being-installed-but-failed version \ removing conflicting-package version The deconfigured packages are marked as requiring configuration, so that if --install is used they will be configured again if possible. To prepare for removal of each conflicting package, call: conflictor's-prerm remove \ in-favour package new-version Error unwind: conflictor's-postinst abort-remove \ in-favour package new-version If the package is being upgraded, call: new-preinst upgrade old-version If this fails, we call: new-postrm abort-upgrade old-version

If that works, then old-postinst abort-upgrade new-version is called. If this works, then the old version is in an "Installed" state, or else it is left in an "Unpacked" state.

If it fails, then the old version is left in an "Half-Installed" state.

Otherwise, if the package had some configuration files from a previous version installed (i.e., it is in the "configuration files only" state): new-preinst install old-version Error unwind: new-postrm abort-install old-version If this fails, the package is left in a "Half-Installed" state, which requires a reinstall. If it works, the packages is left in a "Config Files" state. Otherwise (i.e., the package was completely purged): new-preinst install Error unwind: new-postrm abort-install If the error-unwind fails, the package is in a "Half Installed" phase, and requires a reinstall. If the error unwind works, the package is in a not installed state.

The new package's files are unpacked, overwriting any that may be on the system already, for example any from the old version of the same package or from another package. Backups of the old files are kept temporarily, and if anything goes wrong the package management system will attempt to put them back as part of the error unwind.

It is an error for a package to contain files which are on the system in another package, unless Replaces is used (see ).

It is a more serious error for a package to contain a plain file or other kind of non-directory where another package has a directory (again, unless Replaces is used). This error can be overridden if desired using --force-overwrite-dir, but this is not advisable.

Packages which overwrite each other's files produce behavior which, though deterministic, is hard for the system administrator to understand. It can easily lead to "missing" programs if, for example, a package is installed which overwrites a file from another package, and is then removed again. Part of the problem is due to what is arguably a bug in dpkg.

A directory will never be replaced by a symbolic link to a directory or vice versa; instead, the existing state (symlink or not) will be left alone and dpkg will follow the symlink if there is one.

If the package is being upgraded, call old-postrm upgrade new-version If this fails, dpkg will attempt: new-postrm failed-upgrade old-version If this works, installation continues. If not, Error unwind: old-preinst abort-upgrade new-version If this fails, the old version is left in an "Half Installed" state. If it works, dpkg now calls: new-postrm abort-upgrade old-version If this fails, the old version is left in an "Half Installed" state. If it works, dpkg now calls: old-postinst abort-upgrade new-version If this fails, the old version is in an "Unpacked" state.

This is the point of no return - if dpkg gets this far, it won't back off past this point if an error occurs. This will leave the package in a fairly bad state, which will require a successful re-installation to clear up, but it's when dpkg starts doing things that are irreversible.

Any files which were in the old version of the package but not in the new are removed. The new file list replaces the old. The new maintainer scripts replace the old. Any packages all of whose files have been overwritten during the installation, and which aren't required for dependencies, are considered to have been removed. For each such package dpkg calls: disappearer's-postrm disappear \ overwriter overwriter-version The package's maintainer scripts are removed. It is noted in the status database as being in a sane state, namely not installed (any conffiles it may have are ignored, rather than being removed by dpkg). Note that disappearing packages do not have their prerm called, because dpkg doesn't know in advance that the package is going to vanish. Any files in the package we're unpacking that are also listed in the file lists of other packages are removed from those lists. (This will lobotomize the file list of the "conflicting" package if there is one.) The backup files made during installation, above, are deleted.

The new package's status is now sane, and recorded as "unpacked".

Here is another point of no return - if the conflicting package's removal fails we do not unwind the rest of the installation; the conflicting package is left in a half-removed limbo.

If there was a conflicting package we go and do the removal actions (described below), starting with the removal of the conflicting package's files (any that are also in the package being installed have already been removed from the conflicting package's file list, and so do not get removed now).

Details of configuration

When we configure a package (this happens with dpkg --install and dpkg --configure), we first update any conffiles and then call: postinst configure most-recently-configured-version

No attempt is made to unwind after errors during configuration. If the configuration fails, the package is in a "Failed Config" state, and an error message is generated.

If there is no most recently configured version dpkg will pass a null argument.

Historical note: Truly ancient (pre-1997) versions of dpkg passed <unknown> (including the angle brackets) in this case. Even older ones did not pass a second argument at all, under any circumstance. Note that upgrades using such an old dpkg version are unlikely to work for other reasons, even if this old argument behavior is handled by your postinst script.

Details of removal and/or configuration purging

prerm remove

If prerm fails during replacement due to conflict conflictor's-postinst abort-remove \ in-favour package new-version Or else we call: postinst abort-remove

If this fails, the package is in a "Failed-Config" state, or else it remains "Installed".

The package's files are removed (except conffiles). postrm remove

If it fails, there's no error unwind, and the package is in an "Half-Installed" state.

All the maintainer scripts except the postrm are removed.

If we aren't purging the package we stop here. Note that packages which have no postrm and no conffiles are automatically purged when removed, as there is no difference except for the dpkg status.

The conffiles and any backup files (~-files, #*# files, %-files, .dpkg-{old,new,tmp}, etc.) are removed.

postrm purge

If this fails, the package remains in a "Config-Files" state.

The package's file list is removed.

Declaring relationships between packages Syntax of relationship fields

These fields all have a uniform syntax. They are a list of package names separated by commas.

In the Depends, Recommends, Suggests, Pre-Depends, Build-Depends and Build-Depends-Indep control file fields of the package, which declare dependencies on other packages, the package names listed may also include lists of alternative package names, separated by vertical bar (pipe) symbols |. In such a case, if any one of the alternative packages is installed, that part of the dependency is considered to be satisfied.

All of the fields except for Provides may restrict their applicability to particular versions of each named package. This is done in parentheses after each individual package name; the parentheses should contain a relation from the list below followed by a version number, in the format described in .

The relations allowed are <<, <=, =, >= and >> for strictly earlier, earlier or equal, exactly equal, later or equal and strictly later, respectively. The deprecated forms < and > were used to mean earlier/later or equal, rather than strictly earlier/later, so they should not appear in new packages (though dpkg still supports them).

Whitespace may appear at any point in the version specification subject to the rules in , and must appear where it's necessary to disambiguate; it is not otherwise significant. All of the relationship fields may span multiple lines. For consistency and in case of future changes to dpkg it is recommended that a single space be used after a version relationship and before a version number; it is also conventional to put a single space after each comma, on either side of each vertical bar, and before each open parenthesis. When wrapping a relationship field, it is conventional to do so after a comma and before the space following that comma.

For example, a list of dependencies might appear as: Package: mutt Version: 1.3.17-1 Depends: libc6 (>= 2.2.1), exim | mail-transport-agent

All fields that specify build-time relationships (Build-Depends, Build-Depends-Indep, Build-Conflicts and Build-Conflicts-Indep) may be restricted to a certain set of architectures. This is indicated in brackets after each individual package name and the optional version specification. The brackets enclose a list of Debian architecture names separated by whitespace. Exclamation marks may be prepended to each of the names. (It is not permitted for some names to be prepended with exclamation marks while others aren't.) If the current Debian host architecture is not in this list and there are no exclamation marks in the list, or it is in the list with a prepended exclamation mark, the package name and the associated version specification are ignored completely for the purposes of defining the relationships.

For example: Source: glibc Build-Depends-Indep: texinfo Build-Depends: kernel-headers-2.2.10 [!hurd-i386], hurd-dev [hurd-i386], gnumach-dev [hurd-i386] requires kernel-headers-2.2.10 on all architectures other than hurd-i386 and requires hurd-dev and gnumach-dev only on hurd-i386.

If the architecture-restricted dependency is part of a set of alternatives using |, that alternative is ignored completely on architectures that do not match the restriction. For example: Build-Depends: foo [!i386] | bar [!amd64] is equivalent to bar on the i386 architecture, to foo on the amd64 architecture, and to foo | bar on all other architectures.

Note that the binary package relationship fields such as Depends appear in one of the binary package sections of the control file, whereas the build-time relationships such as Build-Depends appear in the source package section of the control file (which is the first section).

Binary Dependencies - Depends, Recommends, Suggests, Enhances, Pre-Depends

Packages can declare in their control file that they have certain relationships to other packages - for example, that they may not be installed at the same time as certain other packages, and/or that they depend on the presence of others.

This is done using the Depends, Pre-Depends, Recommends, Suggests, Enhances, Breaks and Conflicts control file fields.

These seven fields are used to declare a dependency relationship by one package on another. Except for Enhances and Breaks, they appear in the depending (binary) package's control file. (Enhances appears in the recommending package's control file, and Breaks appears in the version of depended-on package which causes the named package to break).

A Depends field takes effect only when a package is to be configured. It does not prevent a package being on the system in an unconfigured state while its dependencies are unsatisfied, and it is possible to replace a package whose dependencies are satisfied and which is properly installed with a different version whose dependencies are not and cannot be satisfied; when this is done the depending package will be left unconfigured (since attempts to configure it will give errors) and will not function properly. If it is necessary, a Pre-Depends field can be used, which has a partial effect even when a package is being unpacked, as explained in detail below. (The other three dependency fields, Recommends, Suggests and Enhances, are only used by the various front-ends to dpkg such as apt-get, aptitude, and dselect.)

For this reason packages in an installation run are usually all unpacked first and all configured later; this gives later versions of packages with dependencies on later versions of other packages the opportunity to have their dependencies satisfied.

In case of circular dependencies, since installation or removal order honoring the dependency order can't be established, dependency loops are broken at some point (based on rules below), and some packages may not be able to rely on their dependencies being present when being installed or removed, depending on which side of the break of the circular dependency loop they happen to be on. If one of the packages in the loop has no postinst script, then the cycle will be broken at that package, so as to ensure that all postinst scripts run with the dependencies properly configured if this is possible. Otherwise the breaking point is arbitrary.

The Depends field thus allows package maintainers to impose an order in which packages should be configured.

The meaning of the five dependency fields is as follows: Depends

This declares an absolute dependency. A package will not be configured unless all of the packages listed in its Depends field have been correctly configured.

The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality.

The Depends field should also be used if the postinst, prerm or postrm scripts require the package to be present in order to run. Note, however, that the postrm cannot rely on any non-essential packages to be present during the purge phase. Recommends

This declares a strong, but not absolute, dependency.

The Recommends field should list packages that would be found together with this one in all but unusual installations.

Suggests This is used to declare that one package may be more useful with one or more others. Using this field tells the packaging system and the user that the listed packages are related to this one and can perhaps enhance its usefulness, but that installing this one without them is perfectly reasonable. Enhances This field is similar to Suggests but works in the opposite direction. It is used to declare that a package can enhance the functionality of another package. Pre-Depends

This field is like Depends, except that it also forces dpkg to complete installation of the packages named before even starting the installation of the package which declares the pre-dependency, as follows:

When a package declaring a pre-dependency is about to be unpacked the pre-dependency can be satisfied if the depended-on package is either fully configured, or even if the depended-on package(s) are only unpacked or half-configured, provided that they have been configured correctly at some point in the past (and not removed or partially removed since). In this case, both the previously-configured and currently unpacked or half-configured versions must satisfy any version clause in the Pre-Depends field.

When the package declaring a pre-dependency is about to be configured, the pre-dependency will be treated as a normal Depends, that is, it will be considered satisfied only if the depended-on package has been correctly configured.

Pre-Depends should be used sparingly, preferably only by packages whose premature upgrade or installation would hamper the ability of the system to continue with any upgrade that might be in progress.

Pre-Depends are also required if the preinst script depends on the named package. It is best to avoid this situation if possible.

When selecting which level of dependency to use you should consider how important the depended-on package is to the functionality of the one declaring the dependency. Some packages are composed of components of varying degrees of importance. Such a package should list using Depends the package(s) which are required by the more important components. The other components' requirements may be mentioned as Suggestions or Recommendations, as appropriate to the components' relative importance.

Packages which break other packages - Breaks

Using Breaks may cause problems for upgrades from older versions of Debian and should not be used until the stable release of Debian supports Breaks.

Ubuntu: Breaks may safely be used in Ubuntu packages, as all supported upgrade paths to current releases involve upgrading dpkg to a version that supports Breaks.

When one binary package declares that it breaks another, dpkg will refuse to allow the package which declares Breaks be installed unless the broken package is deconfigured first, and it will refuse to allow the broken package to be reconfigured.

A package will not be regarded as causing breakage merely because its configuration files are still installed; it must be at least half-installed.

A special exception is made for packages which declare that they break their own package name or a virtual package which they provide (see below): this does not count as a real breakage.

Normally a Breaks entry will have an "earlier than" version clause; such a Breaks is introduced in the version of an (implicit or explicit) dependency which violates an assumption or reveals a bug in earlier versions of the broken package. This use of Breaks will inform higher-level package management tools that broken package must be upgraded before the new one.

If the breaking package also overwrites some files from the older package, it should use Replaces (not Conflicts) to ensure this goes smoothly.

Conflicting binary packages - Conflicts

When one binary package declares a conflict with another using a Conflicts field, dpkg will refuse to allow them to be installed on the system at the same time.

If one package is to be installed, the other must be removed first - if the package being installed is marked as replacing (see ) the one on the system, or the one on the system is marked as deselected, or both packages are marked Essential, then dpkg will automatically remove the package which is causing the conflict, otherwise it will halt the installation of the new package with an error. This mechanism is specifically designed to produce an error when the installed package is Essential, but the new package is not.

A package will not cause a conflict merely because its configuration files are still installed; it must be at least half-installed.

A special exception is made for packages which declare a conflict with their own package name, or with a virtual package which they provide (see below): this does not prevent their installation, and allows a package to conflict with others providing a replacement for it. You use this feature when you want the package in question to be the only package providing some feature.

A Conflicts entry should almost never have an "earlier than" version clause. This would prevent dpkg from upgrading or installing the package which declared such a conflict until the upgrade or removal of the conflicted-with package had been completed. Instead, Breaks may be used.

Virtual packages - Provides

As well as the names of actual ("concrete") packages, the package relationship fields Depends, Recommends, Suggests, Enhances, Pre-Depends, Breaks, Conflicts, Build-Depends, Build-Depends-Indep, Build-Conflicts and Build-Conflicts-Indep may mention "virtual packages".

A virtual package is one which appears in the Provides control file field of another package. The effect is as if the package(s) which provide a particular virtual package name had been listed by name everywhere the virtual package name appears. (See also )

If there are both concrete and virtual packages of the same name, then the dependency may be satisfied (or the conflict caused) by either the concrete package with the name in question or any other concrete package which provides the virtual package with the name in question. This is so that, for example, supposing we have Package: foo Depends: bar and someone else releases an enhanced version of the bar package they can say: Package: bar-plus Provides: bar and the bar-plus package will now also satisfy the dependency for the foo package.

If a relationship field has a version number attached then only real packages will be considered to see whether the relationship is satisfied (or the prohibition violated, for a conflict or breakage) - it is assumed that a real package which provides the virtual package is not of the "right" version. So, a Provides field may not contain version numbers, and the version number of the concrete package which provides a particular virtual package will not be looked at when considering a dependency on or conflict with the virtual package name.

It is likely that the ability will be added in a future release of dpkg to specify a version number for each virtual package it provides. This feature is not yet present, however, and is expected to be used only infrequently.

If you want to specify which of a set of real packages should be the default to satisfy a particular dependency on a virtual package, you should list the real package as an alternative before the virtual one.

Overwriting files and replacing packages - Replaces

Packages can declare in their control file that they should overwrite files in certain other packages, or completely replace other packages. The Replaces control file field has these two distinct purposes.

Overwriting files in other packages

Firstly, as mentioned before, it is usually an error for a package to contain files which are on the system in another package.

However, if the overwriting package declares that it Replaces the one containing the file being overwritten, then dpkg will replace the file from the old package with that from the new. The file will no longer be listed as "owned" by the old package.

If a package is completely replaced in this way, so that dpkg does not know of any files it still contains, it is considered to have "disappeared". It will be marked as not wanted on the system (selected for removal) and not installed. Any conffiles details noted for the package will be ignored, as they will have been taken over by the overwriting package. The package's postrm script will be run with a special argument to allow the package to do any final cleanup required. See .

Replaces is a one way relationship -- you have to install the replacing package after the replaced package.

For this usage of Replaces, virtual packages (see ) are not considered when looking at a Replaces field - the packages declared as being replaced must be mentioned by their real names.

Furthermore, this usage of Replaces only takes effect when both packages are at least partially on the system at once, so that it can only happen if they do not conflict or if the conflict has been overridden.

Replacing whole packages, forcing their removal

Secondly, Replaces allows the packaging system to resolve which package should be removed when there is a conflict - see . This usage only takes effect when the two packages do conflict, so that the two usages of this field do not interfere with each other.

In this situation, the package declared as being replaced can be a virtual package, so for example, all mail transport agents (MTAs) would have the following fields in their control files: Provides: mail-transport-agent Conflicts: mail-transport-agent Replaces: mail-transport-agent ensuring that only one MTA can be installed at any one time. Relationships between source and binary packages - Build-Depends, Build-Depends-Indep, Build-Conflicts, Build-Conflicts-Indep

Source packages that require certain binary packages to be installed or absent at the time of building the package can declare relationships to those binary packages.

This is done using the Build-Depends, Build-Depends-Indep, Build-Conflicts and Build-Conflicts-Indep control file fields.

Build-dependencies on "build-essential" binary packages can be omitted. Please see for more information.

The dependencies and conflicts they define must be satisfied (as defined earlier for binary packages) in order to invoke the targets in debian/rules, as follows:

If you make "build-arch" or "binary-arch", you need Build-Depends. If you make "build-indep" or "binary-indep", you need Build-Depends and Build-Depends-Indep. If you make "build" or "binary", you need both.

There is no Build-Depends-Arch; this role is essentially met with Build-Depends. Anyone building the build-indep and binary-indep targets is basically assumed to be building the whole package anyway and so installs all build dependencies. The autobuilders use dpkg-buildpackage -B, which calls build (not build-arch, since it does not yet know how to check for its existence) and binary-arch.

The purpose of the original split, I recall, was so that the autobuilders wouldn't need to install extra packages needed only for the binary-indep targets. But without a build-arch/build-indep split, this didn't work, since most of the work is done in the build target, not in the binary target.

Build-Depends, Build-Conflicts The Build-Depends and Build-Conflicts fields must be satisfied when any of the following targets is invoked: build, clean, binary, binary-arch, build-arch, build-indep and binary-indep. Build-Depends-Indep, Build-Conflicts-Indep The Build-Depends-Indep and Build-Conflicts-Indep fields must be satisfied when any of the following targets is invoked: build, build-indep, binary and binary-indep.

Shared libraries

Packages containing shared libraries must be constructed with a little care to make sure that the shared library is always available. This is especially important for packages whose shared libraries are vitally important, such as the C library (currently libc6).

Packages involving shared libraries should be split up into several binary packages. This section mostly deals with how this separation is to be accomplished; rules for files within the shared library packages are in instead.

Run-time shared libraries

The run-time shared library needs to be placed in a package whose name changes whenever the shared object version changes.

Since it is common place to install several versions of a package that just provides shared libraries, it is a good idea that the library package should not contain any extraneous non-versioned files, unless they happen to be in versioned directories.

The most common mechanism is to place it in a package called librarynamesoversion, where soversion is the version number in the soname of the shared library The soname is the shared object name: it's the thing that has to match exactly between building an executable and running it for the dynamic linker to be able run the program. For example, if the soname of the library is libfoo.so.6, the library package would be called libfoo6. . Alternatively, if it would be confusing to directly append soversion to libraryname (e.g. because libraryname itself ends in a number), you may use libraryname-soversion and libraryname-soversion-dev instead.

If you have several shared libraries built from the same source tree you may lump them all together into a single shared library package, provided that you change all of their sonames at once (so that you don't get filename clashes if you try to install different versions of the combined shared libraries package).

The package should install the shared libraries under their normal names. For example, the libgdbm3 package should install libgdbm.so.3.0.0 as /usr/lib/libgdbm.so.3.0.0. The files should not be renamed or re-linked by any prerm or postrm scripts; dpkg will take care of renaming things safely without affecting running programs, and attempts to interfere with this are likely to lead to problems.

Shared libraries should not be installed executable, since the dynamic linker does not require this and trying to execute a shared library usually results in a core dump.

The run-time library package should include the symbolic link that ldconfig would create for the shared libraries. For example, the libgdbm3 package should include a symbolic link from /usr/lib/libgdbm.so.3 to libgdbm.so.3.0.0. This is needed so that the dynamic linker (for example ld.so or ld-linux.so.*) can find the library between the time that dpkg installs it and the time that ldconfig is run in the postinst script. The package management system requires the library to be placed before the symbolic link pointing to it in the .deb file. This is so that when dpkg comes to install the symlink (overwriting the previous symlink pointing at an older version of the library), the new shared library is already in place. In the past, this was achieved by creating the library in the temporary packaging directory before creating the symlink. Unfortunately, this was not always effective, since the building of the tar file in the .deb depended on the behavior of the underlying file system. Some file systems (such as reiserfs) reorder the files so that the order of creation is forgotten. Since version 1.7.0, dpkg reorders the files itself as necessary when building a package. Thus it is no longer important to concern oneself with the order of file creation.

ldconfig

Any package installing shared libraries in one of the default library directories of the dynamic linker (which are currently /usr/lib and /lib) or a directory that is listed in /etc/ld.so.conf These are currently /usr/local/lib /usr/lib/libc5-compat /lib/libc5-compat must use ldconfig to update the shared library system.

The package maintainer scripts must only call ldconfig under these circumstances: When the postinst script is run with a first argument of configure, the script must call ldconfig, and may optionally invoke ldconfig at other times. When the postrm script is run with a first argument of remove, the script should call ldconfig.

During install or upgrade, the preinst is called before the new files are installed, so calling "ldconfig" is pointless. The preinst of an existing package can also be called if an upgrade fails. However, this happens during the critical time when a shared libs may exist on-disk under a temporary name. Thus, it is dangerous and forbidden by current policy to call "ldconfig" at this time.

When a package is installed or upgraded, "postinst configure" runs after the new files are safely on-disk. Since it is perfectly safe to invoke ldconfig unconditionally in a postinst, it is OK for a package to simply put ldconfig in its postinst without checking the argument. The postinst can also be called to recover from a failed upgrade. This happens before any new files are unpacked, so there is no reason to call "ldconfig" at this point.

For a package that is being removed, prerm is called with all the files intact, so calling ldconfig is useless. The other calls to "prerm" happen in the case of upgrade at a time when all the files of the old package are on-disk, so again calling "ldconfig" is pointless.

postrm, on the other hand, is called with the "remove" argument just after the files are removed, so this is the proper time to call "ldconfig" to notify the system of the fact that the shared libraries from the package are removed. The postrm can be called at several other times. At the time of "postrm purge", "postrm abort-install", or "postrm abort-upgrade", calling "ldconfig" is useless because the shared lib files are not on-disk. However, when "postrm" is invoked with arguments "upgrade", "failed-upgrade", or "disappear", a shared lib may exist on-disk under a temporary filename.

Shared library support files

If your package contains files whose names do not change with each change in the library shared object version, you must not put them in the shared library package. Otherwise, several versions of the shared library cannot be installed at the same time without filename clashes, making upgrades and transitions unnecessarily difficult.

It is recommended that supporting files and run-time support programs that do not need to be invoked manually by users, but are nevertheless required for the package to function, be placed (if they are binary) in a subdirectory of /usr/lib, preferably under /usr/lib/package-name. If the program or file is architecture independent, the recommendation is for it to be placed in a subdirectory of /usr/share instead, preferably under /usr/share/package-name. Following the package-name naming convention ensures that the file names change when the shared object version changes.

Run-time support programs that use the shared library but are not required for the library to function or files used by the shared library that can be used by any version of the shared library package should instead be put in a separate package. This package might typically be named libraryname-tools; note the absence of the soversion in the package name.

Files and support programs only useful when compiling software against the library should be included in the development package for the library. For example, a package-name-config script or pkg-config configuration files.

Static libraries

The static library (libraryname.a) is usually provided in addition to the shared version. It is placed into the development package (see below).

In some cases, it is acceptable for a library to be available in static form only; these cases include: libraries for languages whose shared library support is immature or unstable libraries whose interfaces are in flux or under development (commonly the case when the library's major version number is zero, or where the ABI breaks across patchlevels) libraries which are explicitly intended to be available only in static form by their upstream author(s)

Development files

The development files associated to a shared library need to be placed in a package called librarynamesoversion-dev, or if you prefer only to support one development version at a time, libraryname-dev.

In case several development versions of a library exist, you may need to use dpkg's Conflicts mechanism (see ) to ensure that the user only installs one development version at a time (as different development versions are likely to have the same header files in them, which would cause a filename clash if both were installed).

The development package should contain a symlink for the associated shared library without a version number. For example, the libgdbm-dev package should include a symlink from /usr/lib/libgdbm.so to libgdbm.so.3.0.0. This symlink is needed by the linker (ld) when compiling packages, as it will only look for libgdbm.so when compiling dynamically.

Dependencies between the packages of the same library

Typically the development version should have an exact version dependency on the runtime library, to make sure that compilation and linking happens correctly. The ${binary:Version} substitution variable can be useful for this purpose. Previously, ${Source-Version} was used, but its name was confusing and it has been deprecated since dpkg 1.13.19.

Dependencies between the library and other packages - the shlibs system

If a package contains a binary or library which links to a shared library, we must ensure that when the package is installed on the system, all of the libraries needed are also installed. This requirement led to the creation of the shlibs system, which is very simple in its design: any package which provides a shared library also provides information on the package dependencies required to ensure the presence of this library, and any package which uses a shared library uses this information to determine the dependencies it requires. The files which contain the mapping from shared libraries to the necessary dependency information are called shlibs files.

Thus, when a package is built which contains any shared libraries, it must provide a shlibs file for other packages to use, and when a package is built which contains any shared libraries or compiled binaries, it must run dpkg-shlibdeps on these to determine the libraries used and hence the dependencies needed by this package.

In the past, the shared libraries linked to were determined by calling ldd, but now objdump is used to do this. The only change this makes to package building is that dpkg-shlibdeps must also be run on shared libraries, whereas in the past this was unnecessary. The rest of this footnote explains the advantage that this method gives.

We say that a binary foo directly uses a library libbar if it is explicitly linked with that library (that is, it uses the flag -lbar during the linking stage). Other libraries that are needed by libbar are linked indirectly to foo, and the dynamic linker will load them automatically when it loads libbar. A package should depend on the libraries it directly uses, and the dependencies for those libraries should automatically pull in the other libraries.

Unfortunately, the ldd program shows both the directly and indirectly used libraries, meaning that the dependencies determined included both direct and indirect dependencies. The use of objdump avoids this problem by determining only the directly used libraries.

A good example of where this helps is the following. We could update libimlib with a new version that supports a new graphics format called dgf (but retaining the same major version number). If we used the old ldd method, every package that uses libimlib would need to be recompiled so it would also depend on libdgf or it wouldn't run due to missing symbols. However with the new system, packages using libimlib can rely on libimlib itself having the dependency on libdgf and so they would not need rebuilding.

In the following sections, we will first describe where the various shlibs files are to be found, then how to use dpkg-shlibdeps, and finally the shlibs file format and how to create them if your package contains a shared library.

The shlibs files present on the system

There are several places where shlibs files are found. The following list gives them in the order in which they are read by dpkg-shlibdeps. (The first one which gives the required information is used.)

debian/shlibs.local

This lists overrides for this package. Its use is described below (see ).

/etc/dpkg/shlibs.override

This lists global overrides. This list is normally empty. It is maintained by the local system administrator.

DEBIAN/shlibs files in the "build directory"

When packages are being built, any debian/shlibs files are copied into the control file area of the temporary build directory and given the name shlibs. These files give details of any shared libraries included in the package. An example may help here. Let us say that the source package foo generates two binary packages, libfoo2 and foo-runtime. When building the binary packages, the two packages are created in the directories debian/libfoo2 and debian/foo-runtime respectively. (debian/tmp could be used instead of one of these.) Since libfoo2 provides the libfoo shared library, it will require a shlibs file, which will be installed in debian/libfoo2/DEBIAN/shlibs, eventually to become /var/lib/dpkg/info/libfoo2.shlibs. Then when dpkg-shlibdeps is run on the executable debian/foo-runtime/usr/bin/foo-prog, it will examine the debian/libfoo2/DEBIAN/shlibs file to determine whether foo-prog's library dependencies are satisfied by any of the libraries provided by libfoo2. For this reason, dpkg-shlibdeps must only be run once all of the individual binary packages' shlibs files have been installed into the build directory.

/var/lib/dpkg/info/*.shlibs

These are the shlibs files corresponding to all of the packages installed on the system, and are maintained by the relevant package maintainers.

/etc/dpkg/shlibs.default

This file lists any shared libraries whose packages have failed to provide correct shlibs files. It was used when the shlibs setup was first introduced, but it is now normally empty. It is maintained by the dpkg maintainer.

How to use dpkg-shlibdeps and the shlibs files

Put a call to dpkg-shlibdeps into your debian/rules file. If your package contains only compiled binaries and libraries (but no scripts), you can use a command such as: dpkg-shlibdeps debian/tmp/usr/bin/* debian/tmp/usr/sbin/* \ debian/tmp/usr/lib/* Otherwise, you will need to explicitly list the compiled binaries and libraries. If you are using debhelper, the dh_shlibdeps program will do this work for you. It will also correctly handle multi-binary packages.

This command puts the dependency information into the debian/substvars file, which is then used by dpkg-gencontrol. You will need to place a ${shlibs:Depends} variable in the Depends field in the control file for this to work.

If dpkg-shlibdeps doesn't complain, you're done. If it does complain you might need to create your own debian/shlibs.local file, as explained below (see ).

If you have multiple binary packages, you will need to call dpkg-shlibdeps on each one which contains compiled libraries or binaries. In such a case, you will need to use the -T option to the dpkg utilities to specify a different substvars file.

If you are creating a udeb for use in the Debian Installer, you will need to specify that dpkg-shlibdeps should use the dependency line of type udeb by adding -tudeb as option dh_shlibdeps from the debhelper suite will automatically add this option if it knows it is processing a udeb. . If there is no dependency line of type udeb in the shlibs file, dpkg-shlibdeps will fall back to the regular dependency line.

For more details on dpkg-shlibdeps, please see and .

The shlibs File Format

Each shlibs file has the same format. Lines beginning with # are considered to be comments and are ignored. Each line is of the form: [type: ]library-name soname-version dependencies ...

We will explain this by reference to the example of the zlib1g package, which (at the time of writing) installs the shared library /usr/lib/libz.so.1.1.3.

type is an optional element that indicates the type of package for which the line is valid. The only type currently in use is udeb. The colon and space after the type are required.

library-name is the name of the shared library, in this case libz. (This must match the name part of the soname, see below.)

soname-version is the version part of the soname of the library. The soname is the thing that must exactly match for the library to be recognized by the dynamic linker, and is usually of the form name.so.major-version, in our example, libz.so.1. This can be determined using the command objdump -p /usr/lib/libz.so.1.1.3 | grep SONAME The version part is the part which comes after .so., so in our case, it is 1.

dependencies has the same syntax as a dependency field in a binary package control file. It should give details of which packages are required to satisfy a binary built against the version of the library contained in the package. See for details.

In our example, if the first version of the zlib1g package which contained a minor number of at least 1.3 was 1:1.1.3-1, then the shlibs entry for this library could say: libz 1 zlib1g (>= 1:1.1.3) The version-specific dependency is to avoid warnings from the dynamic linker about using older shared libraries with newer binaries.

As zlib1g also provides a udeb containing the shared library, there would also be a second line: udeb: libz 1 zlib1g-udeb (>= 1:1.1.3)

Providing a shlibs file

If your package provides a shared library, you need to create a shlibs file following the format described above. It is usual to call this file debian/shlibs (but if you have multiple binary packages, you might want to call it debian/shlibs.package instead). Then let debian/rules install it in the control area: install -m644 debian/shlibs debian/tmp/DEBIAN or, in the case of a multi-binary package: install -m644 debian/shlibs.package debian/package/DEBIAN/shlibs An alternative way of doing this is to create the shlibs file in the control area directly from debian/rules without using a debian/shlibs file at all, This is what dh_makeshlibs in the debhelper suite does. If your package also has a udeb that provides a shared library, dh_makeshlibs can automatically generate the udeb: lines if you specify the name of the udeb with the --add-udeb option. since the debian/shlibs file itself is ignored by dpkg-shlibdeps.

As dpkg-shlibdeps reads the DEBIAN/shlibs files in all of the binary packages being built from this source package, all of the DEBIAN/shlibs files should be installed before dpkg-shlibdeps is called on any of the binary packages.

Writing the debian/shlibs.local file

This file is intended only as a temporary fix if your binaries or libraries depend on a library whose package does not yet provide a correct shlibs file.

We will assume that you are trying to package a binary foo. When you try running dpkg-shlibdeps you get the following error message (-O displays the dependency information on stdout instead of writing it to debian/substvars, and the lines have been wrapped for ease of reading): $ dpkg-shlibdeps -O debian/tmp/usr/bin/foo dpkg-shlibdeps: warning: unable to find dependency information for shared library libbar (soname 1, path /usr/lib/libbar.so.1, dependency field Depends) shlibs:Depends=libc6 (>= 2.2.2-2) You can then run ldd on the binary to find the full location of the library concerned: $ ldd foo libbar.so.1 => /usr/lib/libbar.so.1 (0x4001e000) libc.so.6 => /lib/libc.so.6 (0x40032000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) So the foo binary depends on the libbar shared library, but no package seems to provide a *.shlibs file handling libbar.so.1 in /var/lib/dpkg/info/. Let's determine the package responsible: $ dpkg -S /usr/lib/libbar.so.1 bar1: /usr/lib/libbar.so.1 $ dpkg -s bar1 | grep Version Version: 1.0-1 This tells us that the bar1 package, version 1.0-1, is the one we are using. Now we can file a bug against the bar1 package and create our own debian/shlibs.local to locally fix the problem. Including the following line into your debian/shlibs.local file: libbar 1 bar1 (>= 1.0-1) should allow the package build to work.

As soon as the maintainer of bar1 provides a correct shlibs file, you should remove this line from your debian/shlibs.local file. (You should probably also then have a versioned Build-Depends on bar1 to help ensure that others do not have the same problem building your package.)

The Operating System File system hierarchy File System Structure

The location of all installed files and directories must comply with the Filesystem Hierarchy Standard (FHS), version 2.3, with the exceptions noted below, and except where doing so would violate other terms of Ubuntu Policy. The following exceptions to the FHS apply:

The optional rules related to user specific configuration files for applications are stored in the user's home directory are relaxed. It is recommended that such files start with the '.' character (a "dot file"), and if an application needs to create more than one dot file then the preferred placement is in a subdirectory with a name starting with a '.' character, (a "dot directory"). In this case it is recommended the configuration files not start with the '.' character.

The requirement for amd64 to use /lib64 for 64 bit binaries is removed.

The requirement that /usr/local/share/man be "synonymous" with /usr/local/man is relaxed to a recommendation

The requirement that windowmanagers with a single configuration file call it system.*wmrc is removed, as is the restriction that the window manager subdirectory be named identically to the window manager name itself.

The requirement that boot manager configuration files live in /etc, or at least are symlinked there, is relaxed to a recommendation.

The version of this document referred here can be found in the ubuntu-policy package or on alongside this manual (or, if you have the ubuntu-policy installed, you can try ). The latest version, which may be a more recent version, may be found on . Specific questions about following the standard may be asked on the ubuntu-devel mailing list, or referred to the FHS mailing list (see the for more information).

Site-specific programs

As mandated by the FHS, packages must not place any files in /usr/local, either by putting them in the file system archive to be unpacked by dpkg or by manipulating them in their maintainer scripts.

However, the package may create empty directories below /usr/local so that the system administrator knows where to place site-specific files. These are not directories in /usr/local, but are children of directories in /usr/local. These directories (/usr/local/*/dir/) should be removed on package removal if they are empty.

Note, that this applies only to directories below /usr/local, not in /usr/local. Packages must not create sub-directories in the directory /usr/local itself, except those listed in FHS, section 4.5. However, you may create directories below them as you wish. You must not remove any of the directories listed in 4.5, even if you created them.

Since /usr/local can be mounted read-only from a remote server, these directories must be created and removed by the postinst and prerm maintainer scripts and not be included in the .deb archive. These scripts must not fail if either of these operations fail.

For example, the emacsen-common package could contain something like if [ ! -e /usr/local/share/emacs ] then if mkdir /usr/local/share/emacs 2>/dev/null then chown root:staff /usr/local/share/emacs chmod 2775 /usr/local/share/emacs fi fi in its postinst script, and rmdir /usr/local/share/emacs/site-lisp 2>/dev/null || true rmdir /usr/local/share/emacs 2>/dev/null || true in the prerm script. (Note that this form is used to ensure that if the script is interrupted, the directory /usr/local/share/emacs will still be removed.)

If you do create a directory in /usr/local for local additions to a package, you should ensure that settings in /usr/local take precedence over the equivalents in /usr.

However, because /usr/local and its contents are for exclusive use of the local administrator, a package must not rely on the presence or absence of files or directories in /usr/local for normal operation.

The /usr/local directory itself and all the subdirectories created by the package should (by default) have permissions 2775 (group-writable and set-group-id) and be owned by root:staff.

The system-wide mail directory

The system-wide mail directory is /var/mail. This directory is part of the base system and should not owned by any particular mail agents. The use of the old location /var/spool/mail is deprecated, even though the spool may still be physically located there.

Users and groups Introduction

The Ubuntu system can be configured to use either plain or shadow passwords.

Some user ids (UIDs) and group ids (GIDs) are reserved globally for use by certain packages. Because some packages need to include files which are owned by these users or groups, or need the ids compiled into binaries, these ids must be used on any Ubuntu system only for the purpose for which they are allocated. This is a serious restriction, and we should avoid getting in the way of local administration policies. In particular, many sites allocate users and/or local system groups starting at 100.

Apart from this we should have dynamically allocated ids, which should by default be arranged in some sensible order, but the behavior should be configurable.

Packages other than base-passwd must not modify /etc/passwd, /etc/shadow, /etc/group or /etc/gshadow.

UID and GID classes

The UID and GID numbers are divided into classes as follows: 0-99:

Globally allocated by the Debian project, the same on every Debian and Ubuntu system. These ids will appear in the passwd and group files of all Debian and Ubuntu systems, new ids in this range being added automatically as the base-passwd package is updated.

Packages which need a single statically allocated uid or gid should use one of these; their maintainers should ask the base-passwd maintainer for ids.

100-999:

Dynamically allocated system users and groups. Packages which need a user or group, but can have this user or group allocated dynamically and differently on each system, should use adduser --system to create the group and/or user. adduser will check for the existence of the user or group, and if necessary choose an unused id based on the ranges specified in adduser.conf.

1000-29999:

Dynamically allocated user accounts. By default adduser will choose UIDs and GIDs for user accounts in this range, though adduser.conf may be used to modify this behavior.

30000-59999:

Reserved.

 60000-64999:

Globally allocated by the Debian project, but only created on demand. The ids are allocated centrally and statically, but the actual accounts are only created on users' systems on demand.

These ids are for packages which are obscure or which require many statically-allocated ids. These packages should check for and create the accounts in /etc/passwd or /etc/group (using adduser if it has this facility) if necessary. Packages which are likely to require further allocations should have a "hole" left after them in the allocation, to give them room to grow.

65000-65533:

Reserved.

 65534:

User nobody. The corresponding gid refers to the group nogroup.

65535:

(uid_t)(-1) == (gid_t)(-1) must not be used, because it is the error return sentinel value.

System run levels and init.d scripts Introduction

The /etc/init.d directory contains the scripts executed by init at boot time and when the init state (or "runlevel") is changed (see ).

There are at least two different, yet functionally equivalent, ways of handling these scripts. For the sake of simplicity, this document describes only the symbolic link method. However, it must not be assumed by maintainer scripts that this method is being used, and any automated manipulation of the various runlevel behaviors by maintainer scripts must be performed using update-rc.d as described below and not by manually installing or removing symlinks. For information on the implementation details of the other method, implemented in the file-rc package, please refer to the documentation of that package.

These scripts are referenced by symbolic links in the /etc/rcn.d directories. When changing runlevels, init looks in the directory /etc/rcn.d for the scripts it should execute, where n is the runlevel that is being changed to, or S for the boot-up scripts.

The names of the links all have the form Smmscript or Kmmscript where mm is a two-digit number and script is the name of the script (this should be the same as the name of the actual script in /etc/init.d).

When init changes runlevel first the targets of the links whose names start with a K are executed, each with the single argument stop, followed by the scripts prefixed with an S, each with the single argument start. (The links are those in the /etc/rcn.d directory corresponding to the new runlevel.) The K links are responsible for killing services and the S link for starting services upon entering the runlevel.

For example, if we are changing from runlevel 2 to runlevel 3, init will first execute all of the K prefixed scripts it finds in /etc/rc3.d, and then all of the S prefixed scripts in that directory. The links starting with K will cause the referred-to file to be executed with an argument of stop, and the S links with an argument of start.

The two-digit number mm is used to determine the order in which to run the scripts: low-numbered links have their scripts run first. For example, the K20 scripts will be executed before the K30 scripts. This is used when a certain service must be started before another. For example, the name server bind might need to be started before the news server inn so that inn can set up its access lists. In this case, the script that starts bind would have a lower number than the script that starts inn so that it runs first: /etc/rc2.d/S17bind /etc/rc2.d/S70inn

The two runlevels 0 (halt) and 6 (reboot) are slightly different. In these runlevels, the links with an S prefix are still called after those with a K prefix, but they too are called with the single argument stop.

Writing the scripts

Packages that include daemons for system services should place scripts in /etc/init.d to start or stop services at boot time or during a change of runlevel. These scripts should be named /etc/init.d/package, and they should accept one argument, saying what to do: start start the service, stop stop the service, restart stop and restart the service if it's already running, otherwise start the service reload

cause the configuration of the service to be reloaded without actually stopping and restarting the service, force-reload cause the configuration to be reloaded if the service supports this, otherwise restart the service. The start, stop, restart, and force-reload options should be supported by all scripts in /etc/init.d, the reload option is optional.

The init.d scripts must ensure that they will behave sensibly (i.e., returning success and not starting multiple copies of a service) if invoked with start when the service is already running, or with stop when it isn't, and that they don't kill unfortunately-named user processes. The best way to achieve this is usually to use start-stop-daemon with the --oknodo option.

If a service reloads its configuration automatically (as in the case of cron, for example), the reload option of the init.d script should behave as if the configuration has been reloaded successfully.

The /etc/init.d scripts must be treated as configuration files, either (if they are present in the package, that is, in the .deb file) by marking them as conffiles, or, (if they do not exist in the .deb) by managing them correctly in the maintainer scripts (see ). This is important since we want to give the local system administrator the chance to adapt the scripts to the local system, e.g., to disable a service without de-installing the package, or to specify some special command line options when starting a service, while making sure their changes aren't lost during the next package upgrade.

These scripts should not fail obscurely when the configuration files remain but the package has been removed, as configuration files remain on the system after the package has been removed. Only when dpkg is executed with the --purge option will configuration files be removed. In particular, as the /etc/init.d/package script itself is usually a conffile, it will remain on the system if the package is removed but not purged. Therefore, you should include a test statement at the top of the script, like this: test -f program-executed-later-in-script || exit 0

Often there are some variables in the init.d scripts whose values control the behavior of the scripts, and which a system administrator is likely to want to change. As the scripts themselves are frequently conffiles, modifying them requires that the administrator merge in their changes each time the package is upgraded and the conffile changes. To ease the burden on the system administrator, such configurable values should not be placed directly in the script. Instead, they should be placed in a file in /etc/default, which typically will have the same base name as the init.d script. This extra file should be sourced by the script when the script runs. It must contain only variable settings and comments in SUSv3 sh format. It may either be a conffile or a configuration file maintained by the package maintainer scripts. See for more details.

To ensure that vital configurable values are always available, the init.d script should set default values for each of the shell variables it uses, either before sourcing the /etc/default/ file or afterwards using something like the : ${VAR:=default} syntax. Also, the init.d script must behave sensibly and not fail if the /etc/default file is deleted.

/var/run and /var/lock may be mounted as temporary filesystems For example, using the RAMRUN and RAMLOCK options in /etc/default/rcS. , so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on dpkg to create them.

Interfacing with the initscript system

Maintainers should use the abstraction layer provided by the update-rc.d and invoke-rc.d programs to deal with initscripts in their packages' scripts such as postinst, prerm and postrm.

Directly managing the /etc/rc?.d links and directly invoking the /etc/init.d/ initscripts should be done only by packages providing the initscript subsystem (such as sysv-rc and file-rc).

Managing the links

The program update-rc.d is provided for package maintainers to arrange for the proper creation and removal of /etc/rcn.d symbolic links, or their functional equivalent if another method is being used. This may be used by maintainers in their packages' postinst and postrm scripts.

You must not include any /etc/rcn.d symbolic links in the actual archive or manually create or remove the symbolic links in maintainer scripts; you must use the update-rc.d program instead. (The former will fail if an alternative method of maintaining runlevel information is being used.) You must not include the /etc/rcn.d directories themselves in the archive either. (Only the sysvinit package may do so.)

By default update-rc.d will start services in each of the multi-user state runlevels (2, 3, 4, and 5) and stop them in the halt runlevel (0), the single-user runlevel (1) and the reboot runlevel (6). The system administrator will have the opportunity to customize runlevels by simply adding, moving, or removing the symbolic links in /etc/rcn.d if symbolic links are being used, or by modifying /etc/runlevel.conf if the file-rc method is being used.

To get the default behavior for your package, put in your postinst script update-rc.d package defaults and in your postrm if [ "$1" = purge ]; then update-rc.d package remove fi . Note that if your package changes runlevels or priority, you may have to remove and recreate the links, since otherwise the old links may persist. Refer to the documentation of update-rc.d.

This will use a default sequence number of 20. If it does not matter when or in which order the init.d script is run, use this default. If it does, then you should talk to the maintainer of the sysvinit package or post to ubuntu-devel, and they will help you choose a number.

For more information about using update-rc.d, please consult its man page .

Running initscripts

The program invoke-rc.d is provided to make it easier for package maintainers to properly invoke an initscript, obeying runlevel and other locally-defined constraints that might limit a package's right to start, stop and otherwise manage services. This program may be used by maintainers in their packages' scripts.

The package maintainer scripts must use invoke-rc.d to invoke the /etc/init.d/* initscripts, instead of calling them directly.

By default, invoke-rc.d will pass any action requests (start, stop, reload, restart...) to the /etc/init.d script, filtering out requests to start or restart a service out of its intended runlevels.

Most packages will simply need to change: /etc/init.d/<package> <action> in their postinst and prerm scripts to: if which invoke-rc.d >/dev/null 2>&1; then invoke-rc.d package <action> else /etc/init.d/package <action> fi

A package should register its initscript services using update-rc.d before it tries to invoke them using invoke-rc.d. Invocation of unregistered services may fail.

For more information about using invoke-rc.d, please consult its man page .

Boot-time initialization

There used to be another directory, /etc/rc.boot, which contained scripts which were run once per machine boot. This has been deprecated in favour of links from /etc/rcS.d to files in /etc/init.d as described in . Packages must not place files in /etc/rc.boot.

Example

An example on which you can base your /etc/init.d scripts is found in /etc/init.d/skeleton.

Console messages from init.d scripts

This section describes the formats to be used for messages written to standard output by the /etc/init.d scripts. The intent is to improve the consistency of Ubuntu's startup and shutdown look and feel. For this reason, please look very carefully at the details. We want the messages to have the same format in terms of wording, spaces, punctuation and case of letters.

Here is a list of overall rules that should be used for messages generated by /etc/init.d scripts.

The message should fit in one line (fewer than 80 characters), start with a capital letter and end with a period (.) and line feed ("\n"). If the script is performing some time consuming task in the background (not merely starting or stopping a program, for instance), an ellipsis (three dots: ...) should be output to the screen, with no leading or tailing whitespace or line feeds. The messages should appear as if the computer is telling the user what it is doing (politely :-), but should not mention "it" directly. For example, instead of: I'm starting network daemons: nfsd mountd. the message should say Starting network daemons: nfsd mountd.

init.d script should use the following standard message formats for the situations enumerated below.

When daemons are started

If the script starts one or more daemons, the output should look like this (a single line, no leading spaces): Starting description: daemon-1 ... daemon-n. The description should describe the subsystem the daemon or set of daemons are part of, while daemon-1 up to daemon-n denote each daemon's name (typically the file name of the program).

For example, the output of /etc/init.d/lpd would look like: Starting printer spooler: lpd.

This can be achieved by saying echo -n "Starting printer spooler: lpd" start-stop-daemon --start --quiet --exec /usr/sbin/lpd echo "." in the script. If there are more than one daemon to start, the output should look like this: echo -n "Starting remote file system services:" echo -n " nfsd"; start-stop-daemon --start --quiet nfsd echo -n " mountd"; start-stop-daemon --start --quiet mountd echo -n " ugidd"; start-stop-daemon --start --quiet ugidd echo "." This makes it possible for the user to see what is happening and when the final daemon has been started. Care should be taken in the placement of white spaces: in the example above the system administrators can easily comment out a line if they don't want to start a specific daemon, while the displayed message still looks good.

When a system parameter is being set

If you have to set up different system parameters during the system boot, you should use this format: Setting parameter to "value".

You can use a statement such as the following to get the quotes right: echo "Setting DNS domainname to \"$domainname\"."

Note that the same symbol (") is used for the left and right quotation marks. A grave accent (`) is not a quote character; neither is an apostrophe (').

When a daemon is stopped or restarted

When you stop or restart a daemon, you should issue a message identical to the startup message, except that Starting is replaced with Stopping or Restarting respectively.

For example, stopping the printer daemon will look like this: Stopping printer spooler: lpd.

When something is executed

There are several examples where you have to run a program at system startup or shutdown to perform a specific task, for example, setting the system's clock using netdate or killing all processes when the system shuts down. Your message should look like this: Doing something very useful...done. You should print the done. immediately after the job has been completed, so that the user is informed why they have to wait. You can get this behavior by saying echo -n "Doing something very useful..." do_something echo "done." in your script.

When the configuration is reloaded

When a daemon is forced to reload its configuration files you should use the following format: Reloading description configuration...done. where description is the same as in the daemon starting message.

Cron jobs

Packages must not modify the configuration file /etc/crontab, and they must not modify the files in /var/spool/cron/crontabs.

If a package wants to install a job that has to be executed via cron, it should place a file with the name of the package in one or more of the following directories: /etc/cron.hourly /etc/cron.daily /etc/cron.weekly /etc/cron.monthly As these directory names imply, the files within them are executed on an hourly, daily, weekly, or monthly basis, respectively. The exact times are listed in /etc/crontab.

All files installed in any of these directories must be scripts (e.g., shell scripts or Perl scripts) so that they can easily be modified by the local system administrator. In addition, they must be treated as configuration files.

If a certain job has to be executed at some other frequency or at a specific time, the package should install a file /etc/cron.d/package. This file uses the same syntax as /etc/crontab and is processed by cron automatically. The file must also be treated as a configuration file. (Note that entries in the /etc/cron.d directory are not handled by anacron. Thus, you should only use this directory for jobs which may be skipped if the system is not running.)

The scripts or crontab entries in these directories should check if all necessary programs are installed before they try to execute them. Otherwise, problems will arise when a package was removed but not purged since configuration files are kept on the system in this situation.

 Menus

The Debian menu package provides a standard interface between packages providing applications and menu programs (either X window managers or text-based menu programs such as pdmenu).

All packages that provide applications that need not be passed any special command line arguments for normal operation should register a menu entry for those applications, so that users of the menu package will automatically get menu entries in their window managers, as well in shells like pdmenu.

Menu entries should follow the current menu policy.

The menu policy can be found in the menu-policy files in the debian-policy package. It is also available from the Debian web mirrors at .

Please also refer to the Debian Menu System documentation that comes with the menu package for information about how to register your applications.

Multimedia handlers

MIME (Multipurpose Internet Mail Extensions, RFCs 2045-2049) is a mechanism for encoding files and data streams and providing meta-information about them, in particular their type (e.g. audio or video) and format (e.g. PNG, HTML, MP3).

Registration of MIME type handlers allows programs like mail user agents and web browsers to invoke these handlers to view, edit or display MIME types they don't support directly.

Packages which provide the ability to view/show/play, compose, edit or print MIME types should register themselves as such following the current MIME support policy.

The MIME support policy can be found in the mime-policy files in the debian-policy package. It is also available from the Debian web mirrors at .

Keyboard configuration

To achieve a consistent keyboard configuration so that all applications interpret a keyboard event the same way, all programs in the Ubuntu distribution must be configured to comply with the following guidelines.

The following keys must have the specified interpretations: <-- delete the character to the left of the cursor Delete delete the character to the right of the cursor Control+H emacs: the help prefix The interpretation of any keyboard events should be independent of the terminal that is used, be it a virtual console, an X terminal emulator, an rlogin/telnet session, etc.

The following list explains how the different programs should be set up to achieve this:

<-- generates KB_BackSpace in X. Delete generates KB_Delete in X. X translations are set up to make KB_Backspace generate ASCII DEL, and to make KB_Delete generate ESC [ 3 ~ (this is the vt220 escape code for the "delete character" key). This must be done by loading the X resources using xrdb on all local X displays, not using the application defaults, so that the translation resources used correspond to the xmodmap settings. The Linux console is configured to make <-- generate DEL, and Delete generate ESC [ 3 ~. X applications are configured so that < deletes left, and Delete deletes right. Motif applications already work like this. Terminals should have stty erase ^? . The xterm terminfo entry should have ESC [ 3 ~ for kdch1, just as for TERM=linux and TERM=vt220. Emacs is programmed to map KB_Backspace or the stty erase character to delete-backward-char, and KB_Delete or kdch1 to delete-forward-char, and ^H to help as always. Other applications use the stty erase character and kdch1 for the two delete keys, with ASCII DEL being "delete previous character" and kdch1 being "delete character under cursor".

This will solve the problem except for the following cases:

Some terminals have a <-- key that cannot be made to produce anything except ^H. On these terminals Emacs help will be unavailable on ^H (assuming that the stty erase character takes precedence in Emacs, and has been set correctly). M-x help or F1 (if available) can be used instead. Some operating systems use ^H for stty erase. However, modern telnet versions and all rlogin versions propagate stty settings, and almost all UNIX versions honour stty erase. Where the stty settings are not propagated correctly, things can be made to work by using stty manually. Some systems (including previous Debian versions) use xmodmap to arrange for both <-- and Delete to generate KB_Delete. We can change the behavior of their X clients using the same X resources that we use to do it for our own clients, or configure our clients using their resources when things are the other way around. On displays configured like this Delete will not work, but <-- will. Some operating systems have different kdch1 settings in their terminfo database for xterm and others. On these systems the Delete key will not work correctly when you log in from a system conforming to our policy, but <-- will.

Environment variables

A program must not depend on environment variables to get reasonable defaults. (That's because these environment variables would have to be set in a system-wide configuration file like /etc/profile, which is not supported by all shells.)

If a program usually depends on environment variables for its configuration, the program should be changed to fall back to a reasonable default configuration if these environment variables are not present. If this cannot be done easily (e.g., if the source code of a non-free program is not available), the program must be replaced by a small "wrapper" shell script which sets the environment variables if they are not already defined, and calls the original program.

Here is an example of a wrapper script for this purpose: #!/bin/sh BAR=${BAR:-/var/lib/fubar} export BAR exec /usr/lib/foo/foo "$@"

Furthermore, as /etc/profile is a configuration file of the base-files package, other packages must not put any environment variables or other commands into that file.

Registering Documents using doc-base

The doc-base package implements a flexible mechanism for handling and presenting documentation. The recommended practice is for every Ubuntu package that provides online documentation (other than just manual pages) to register these documents with doc-base by installing a doc-base control file via the

Please refer to the documentation that comes with the doc-base package for information and details.

Files Binaries

Two different packages must not install programs with different functionality but with the same filenames. (The case of two programs having the same functionality but different implementations is handled via "alternatives" or the "Conflicts" mechanism. See and respectively.) If this case happens, one of the programs must be renamed. The maintainers should report this to the ubuntu-devel mailing list and try to find a consensus about which program will have to be renamed. If a consensus cannot be reached, both programs must be renamed.

By default, when a package is being built, any binaries created should include debugging information, as well as being compiled with optimization. You should also turn on as many reasonable compilation warnings as possible; this makes life easier for porters, who can then look at build logs for possible problems. For the C programming language, this means the following compilation parameters should be used: CC = gcc CFLAGS = -O2 -g -Wall # sane warning options vary between programs LDFLAGS = # none INSTALL = install -s # (or use strip on the files in debian/tmp)

Note that by default all installed binaries should be stripped, either by using the -s flag to install, or by calling strip on the binaries after they have been copied into debian/tmp but before the tree is made into a package.

Although binaries in the build tree should be compiled with debugging information by default, it can often be difficult to debug programs if they are also subjected to compiler optimization. For this reason, it is recommended to support the standardized environment variable DEB_BUILD_OPTIONS (see ). This variable can contain several flags to change how a package is compiled and built.

It is up to the package maintainer to decide what compilation options are best for the package. Certain binaries (such as computationally-intensive programs) will function better with certain flags (-O3, for example); feel free to use them. Please use good judgment here. Don't use flags for the sake of it; only use them if there is good reason to do so. Feel free to override the upstream author's ideas about which compilation options are best: they are often inappropriate for our environment.

Libraries

If the package is architecture: any, then the shared library compilation and linking flags must have -fPIC, or the package shall not build on some of the supported architectures

If you are using GCC, -fPIC produces code with relocatable position independent code, which is required for most architectures to create a shared library, with i386 and perhaps some others where non position independent code is permitted in a shared library.

Position independent code may have a performance penalty, especially on i386. However, in most cases the speed penalty must be measured against the memory wasted on the few architectures where non position independent code is even possible.

. Any exception to this rule must be discussed on the mailing list ubuntu-devel@lists.ubuntu.com, and a rough consensus obtained. The reasons for not compiling with -fPIC flag must be recorded in the file README.Debian, and care must be taken to either restrict the architecture or arrange for -fPIC to be used on architectures where it is required.

Some of the reasons why this might be required is if the library contains hand crafted assembly code that is not relocatable, the speed penalty is excessive for compute intensive libs, and similar reasons.

As to the static libraries, the common case is not to have relocatable code, since there is no benefit, unless in specific cases; therefore the static version must not be compiled with the -fPIC flag. Any exception to this rule should be discussed on the mailing list ubuntu-devel@lists.ubuntu.com, and the reasons for compiling with the -fPIC flag must be recorded in the file README.Debian.

Some of the reasons for linking static libraries with the -fPIC flag are if, for example, one needs a Perl API for a library that is under rapid development, and has an unstable API, so shared libraries are pointless at this phase of the library's development. In that case, since Perl needs a library with relocatable code, it may make sense to create a static library with relocatable code. Another reason cited is if you are distilling various libraries into a common shared library, like mklibs does in the Debian installer project.

In other words, if both a shared and a static library is being built, each source unit (*.c, for example, for C files) will need to be compiled twice, for the normal case.

You must specify the gcc option -D_REENTRANT when building a library (either static or shared) to make the library compatible with LinuxThreads.

Although not enforced by the build tools, shared libraries must be linked against all libraries that they use symbols from in the same way that binaries are. This ensures the correct functioning of the shlibs system and guarantees that all libraries can be safely opened with dlopen(). Packagers may wish to use the gcc option -Wl,-z,defs when building a shared library. Since this option enforces symbol resolution at build time, a missing library reference will be caught early as a fatal build error.

All installed shared libraries should be stripped with strip --strip-unneeded your-lib (The option --strip-unneeded makes strip remove only the symbols which aren't needed for relocation processing.) Shared libraries can function perfectly well when stripped, since the symbols for dynamic linking are in a separate part of the ELF object file. You might also want to use the options --remove-section=.comment and --remove-section=.note on both shared libraries and executables, and --strip-debug on static libraries.

Note that under some circumstances it may be useful to install a shared library unstripped, for example when building a separate package to support debugging.

Shared object files (often .so files) that are not public libraries, that is, they are not meant to be linked to by third party executables (binaries of other packages), should be installed in subdirectories of the /usr/lib directory. Such files are exempt from the rules that govern ordinary shared libraries, except that they must not be installed executable and should be stripped. A common example are the so-called "plug-ins", internal shared objects that are dynamically loaded by programs using .

Packages containing shared libraries that may be linked to by other packages' binaries, but which for some compelling reason can not be installed in /usr/lib directory, may install the shared library files in subdirectories of the /usr/lib directory, in which case they should arrange to add that directory in /etc/ld.so.conf in the package's post-installation script, and remove it in the package's post-removal script.

An ever increasing number of packages are using libtool to do their linking. The latest GNU libtools (>= 1.3a) can take advantage of the metadata in the installed libtool archive files (*.la files). The main advantage of libtool's .la files is that it allows libtool to store and subsequently access metadata with respect to the libraries it builds. libtool will search for those files, which contain a lot of useful information about a library (such as library dependency information for static linking). Also, they're essential for programs using libltdl. Although libtool is fully capable of linking against shared libraries which don't have .la files, as it is a mere shell script it can add considerably to the build time of a libtool-using package if that shell script has to derive all this information from first principles for each library every time it is linked. With the advent of libtool version 1.4 (and to a lesser extent libtool version 1.3), the .la files also store information about inter-library dependencies which cannot necessarily be derived after the .la file is deleted.

Packages that use libtool to create shared libraries should include the .la files in the -dev package, unless the package relies on libtool's libltdl library, in which case the .la files must go in the run-time library package.

You must make sure that you use only released versions of shared libraries to build your packages; otherwise other users will not be able to run your binaries properly. Producing source packages that depend on unreleased compilers is also usually a bad idea.

Shared libraries

This section has moved to .

Scripts

All command scripts, including the package maintainer scripts inside the package and used by dpkg, should have a #! line naming the shell to be used to interpret them.

In the case of Perl scripts this should be #!/usr/bin/perl.

When scripts are installed into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently used to implement it.

Shell scripts (sh and bash) should almost certainly start with set -e so that errors are detected. Every script should use set -e or check the exit status of every command.

Scripts may assume that /bin/sh implements the SUSv3 Shell Command Language Single UNIX Specification, version 3, which is also IEEE 1003.1-2004 (POSIX), and is available on the World Wide Web from after free registration. plus the following additional features not mandated by SUSv3: These features are in widespread use in the Linux community and are implemented in all of bash, dash, and ksh, the most common shells users may wish to use as /bin/sh. echo -n, if implemented as a shell built-in, must not generate a newline. test, if implemented as a shell built-in, must support -a and -o as binary logical operators. local to create a scoped variable must be supported, including listing multiple variables in a single local command and assigning a value to a variable at the same time as localizing it. local may or may not preserve the variable value from an outer scope if no assignment is present. Uses such as: fname () { local a b c=delta d # ... use a, b, c, d ... } must be supported and must set the value of c to delta. If a shell script requires non-SUSv3 features from the shell interpreter other than those listed above, the appropriate shell must be specified in the first line of the script (e.g., #!/bin/bash) and the package must depend on the package providing the shell (unless the shell package is marked "Essential", as in the case of bash).

You may wish to restrict your script to SUSv3 features plus the above set when possible so that it may use /bin/sh as its interpreter. If your script works with dash (originally called ash), it probably complies with the above requirements, but if you are in doubt, use /bin/bash.

Perl scripts should check for errors when making any system calls, including open, print, close, rename and system.

csh and tcsh should be avoided as scripting languages. See Csh Programming Considered Harmful, one of the comp.unix.* FAQs, which can be found at . If an upstream package comes with csh scripts then you must make sure that they start with #!/bin/csh and make your package depend on the c-shell virtual package.

Any scripts which create files in world-writeable directories (e.g., in /tmp) must use a mechanism which will fail atomically if a file with the same name already exists.

The Ubuntu base system provides the tempfile and mktemp utilities for use by scripts for this purpose.

Symbolic links

In general, symbolic links within a top-level directory should be relative, and symbolic links pointing from one top-level directory into another should be absolute. (A top-level directory is a sub-directory of the root directory /.)

In addition, symbolic links should be specified as short as possible, i.e., link targets like foo/../bar are deprecated.

Note that when creating a relative link using ln it is not necessary for the target of the link to exist relative to the working directory you're running ln from, nor is it necessary to change directory to the directory where the link is to be made. Simply include the string that should appear as the target of the link (this will be a pathname relative to the directory in which the link resides) as the first argument to ln.

For example, in your Makefile or debian/rules, you can do things like: ln -fs gcc $(prefix)/bin/cc ln -fs gcc debian/tmp/usr/bin/cc ln -fs ../sbin/sendmail $(prefix)/bin/runq ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq

A symbolic link pointing to a compressed file should always have the same file extension as the referenced file. (For example, if a file foo.gz is referenced by a symbolic link, the filename of the link has to end with ".gz" too, as in bar.gz.)

Device files

Packages must not include device files in the package file tree.

If a package needs any special device files that are not included in the base system, it must call MAKEDEV in the postinst script, after notifying the user This notification could be done via a (low-priority) debconf message, or an echo (printf) statement. .

Packages must not remove any device files in the postrm or any other script. This is left to the system administrator.

Ubuntu uses the serial devices /dev/ttyS*. Programs using the old /dev/cu* devices should be changed to use /dev/ttyS*.

Configuration files Definitions

configuration file A file that affects the operation of a program, or provides site- or host-specific information, or otherwise customizes the behavior of a program. Typically, configuration files are intended to be modified by the system administrator (if needed or desired) to conform to local policy or to provide more useful site-specific behavior. conffile A file listed in a package's conffiles file, and is treated specially by dpkg (see ).

The distinction between these two is important; they are not interchangeable concepts. Almost all conffiles are configuration files, but many configuration files are not conffiles.

As noted elsewhere, /etc/init.d scripts, /etc/default files, scripts installed in /etc/cron.{hourly,daily,weekly,monthly}, and cron configuration installed in /etc/cron.d must be treated as configuration files. In general, any script that embeds configuration information is de-facto a configuration file and should be treated as such.

Location

Any configuration files created or used by your package must reside in /etc. If there are several, consider creating a subdirectory of /etc named after your package.

If your package creates or uses configuration files outside of /etc, and it is not feasible to modify the package to use /etc directly, put the files in /etc and create symbolic links to those files from the location that the package requires.

Behavior

Configuration file handling must conform to the following behavior: local changes must be preserved during a package upgrade, and configuration files must be preserved when the package is removed, and only deleted when the package is purged.

The easy way to achieve this behavior is to make the configuration file a conffile. This is appropriate only if it is possible to distribute a default version that will work for most installations, although some system administrators may choose to modify it. This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time).

In order to ensure that local changes are preserved correctly, no package may contain or make hard links to conffiles. Rationale: There are two problems with hard links. The first is that some editors break the link while editing one of the files, so that the two files may unwittingly become unlinked and different. The second is that dpkg might break the hard link while upgrading conffiles.

The other way to do it is via the maintainer scripts. In this case, the configuration file must not be listed as a conffile and must not be part of the package distribution. If the existence of a file is required for the package to be sensibly configured it is the responsibility of the package maintainer to provide maintainer scripts which correctly create, update and maintain the file and remove it on purge. (See for more information.) These scripts must be idempotent (i.e., must work correctly if dpkg needs to re-run them due to errors during installation or removal), must cope with all the variety of ways dpkg can call maintainer scripts, must not overwrite or otherwise mangle the user's configuration without asking, must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens.

The scripts are not required to configure every possible option for the package, but only those necessary to get the package running on a given system. Ideally the sysadmin should not have to do any configuration other than that done (semi-)automatically by the postinst script.

A common practice is to create a script called package-configure and have the package's postinst call it if and only if the configuration file does not already exist. In certain cases it is useful for there to be an example or template file which the maintainer scripts use. Such files should be in /usr/share/package or /usr/lib/package (depending on whether they are architecture-independent or not). There should be symbolic links to them from /usr/share/doc/package/examples if they are examples, and should be perfectly ordinary dpkg-handled files (not configuration files).

These two styles of configuration file handling must not be mixed, for that way lies madness: dpkg will ask about overwriting the file every time the package is upgraded.

Sharing configuration files

Packages which specify the same file as a conffile must be tagged as conflicting with each other. (This is an instance of the general rule about not sharing files. Note that neither alternatives nor diversions are likely to be appropriate in this case; in particular, dpkg does not handle diverted conffiles well.)

The maintainer scripts must not alter a conffile of any package, including the one the scripts belong to.

If two or more packages use the same configuration file and it is reasonable for both to be installed at the same time, one of these packages must be defined as owner of the configuration file, i.e., it will be the package which handles that file as a configuration file. Other packages that use the configuration file must depend on the owning package if they require the configuration file to operate. If the other package will use the configuration file if present, but is capable of operating without it, no dependency need be declared.

If it is desirable for two or more related packages to share a configuration file and for all of the related packages to be able to modify that configuration file, then the following should be done: One of the related packages (the "owning" package) will manage the configuration file with maintainer scripts as described in the previous section. The owning package should also provide a program that the other packages may use to modify the configuration file. The related packages must use the provided program to make any desired modifications to the configuration file. They should either depend on the core package to guarantee that the configuration modifier program is available or accept gracefully that they cannot modify the configuration file if it is not. (This is in addition to the fact that the configuration file may not even be present in the latter scenario.)

Sometimes it's appropriate to create a new package which provides the basic infrastructure for the other packages and which manages the shared configuration files. (The sgml-base package is a good example.)

User configuration files ("dotfiles")

The files in /etc/skel will automatically be copied into new user accounts by adduser. No other program should reference the files in /etc/skel.

Therefore, if a program needs a dotfile to exist in advance in $HOME to work sensibly, that dotfile should be installed in /etc/skel and treated as a configuration file.

However, programs that require dotfiles in order to operate sensibly are a bad thing, unless they do create the dotfiles themselves automatically.

Furthermore, programs should be configured by the Ubuntu default installation to behave as closely to the upstream default behavior as possible.

Therefore, if a program in a Ubuntu package needs to be configured in some way in order to operate sensibly, that should be done using a site-wide configuration file placed in /etc. Only if the program doesn't support a site-wide default configuration and the package maintainer doesn't have time to add it may a default per-user file be placed in /etc/skel.

/etc/skel should be as empty as we can make it. This is particularly true because there is no easy (or necessarily desirable) mechanism for ensuring that the appropriate dotfiles are copied into the accounts of existing users when a package is installed.

Log files

Log files should usually be named /var/log/package.log. If you have many log files, or need a separate directory for permission reasons (/var/log is writable only by root), you should usually create a directory named /var/log/package and place your log files there.

Log files must be rotated occasionally so that they don't grow indefinitely; the best way to do this is to drop a log rotation configuration file into the directory /etc/logrotate.d and use the facilities provided by logrotate.

The traditional approach to log files has been to set up ad hoc log rotation schemes using simple shell scripts and cron. While this approach is highly customizable, it requires quite a lot of sysadmin work. Even though the original Ubuntu system helped a little by automatically installing a system which can be used as a template, this was deemed not enough.

The use of logrotate, a program developed by Red Hat, is better, as it centralizes log management. It has both a configuration file (/etc/logrotate.conf) and a directory where packages can drop their individual log rotation configurations (/etc/logrotate.d).

Here is a good example for a logrotate config file (for more information see ): /var/log/foo/*.log { rotate 12 weekly compress postrotate /etc/init.d/foo force-reload endscript } This rotates all files under /var/log/foo, saves 12 compressed generations, and forces the daemon to reload its configuration information after the log rotation.

Log files should be removed when the package is purged (but not when it is only removed). This should be done by the postrm script when it is called with the argument purge (see ).

Permissions and owners

The rules in this section are guidelines for general use. If necessary you may deviate from the details below. However, if you do so you must make sure that what is done is secure and you should try to be as consistent as possible with the rest of the system. You should probably also discuss it on ubuntu-devel first.

Files should be owned by root:root, and made writable only by the owner and universally readable (and executable, if appropriate), that is mode 644 or 755.

Directories should be mode 755 or (for group-writability) mode 2775. The ownership of the directory should be consistent with its mode: if a directory is mode 2775, it should be owned by the group that needs write access to it.

When a package is upgraded, and the owner or permissions of a file included in the package has changed, dpkg arranges for the ownership and permissions to be correctly set upon installation. However, this does not extend to directories; the permissions and ownership of directories already on the system does not change on install or upgrade of packages. This makes sense, since otherwise common directories like /usr would always be in flux. To correctly change permissions of a directory the package owns, explicit action is required, usually in the postinst script. Care must be taken to handle downgrades as well, in that case.

Setuid and setgid executables should be mode 4755 or 2755 respectively, and owned by the appropriate user or group. They should not be made unreadable (modes like 4711 or 2711 or even 4111); doing so achieves no extra security, because anyone can find the binary in the freely available Ubuntu package; it is merely inconvenient. For the same reason you should not restrict read or execute permissions on non-set-id executables.

Some setuid programs need to be restricted to particular sets of users, using file permissions. In this case they should be owned by the uid to which they are set-id, and by the group which should be allowed to execute them. They should have mode 4754; again there is no point in making them unreadable to those users who must not be allowed to execute them.

It is possible to arrange that the system administrator can reconfigure the package to correspond to their local security policy by changing the permissions on a binary: they can do this by using dpkg-statoverride, as described below. Ordinary files installed by dpkg (as opposed to conffiles and other similar objects) normally have their permissions reset to the distributed permissions when the package is reinstalled. However, the use of dpkg-statoverride overrides this default behavior. If you use this method, you should remember to describe dpkg-statoverride in the package documentation; being a relatively new addition to Debian, it is probably not yet well-known. Another method you should consider is to create a group for people allowed to use the program(s) and make any setuid executables executable only by that group.

If you need to create a new user or group for your package there are two possibilities. Firstly, you may need to make some files in the binary package be owned by this user or group, or you may need to compile the user or group id (rather than just the name) into the binary (though this latter should be avoided if possible, as in this case you need a statically allocated id).

If you need a statically allocated id, you must ask for a user or group id from the base-passwd maintainer, and must not release the package until you have been allocated one. Once you have been allocated one you must either make the package depend on a version of the base-passwd package with the id present in /etc/passwd or /etc/group, or arrange for your package to create the user or group itself with the correct id (using adduser) in its preinst or postinst. (Doing it in the postinst is to be preferred if it is possible, otherwise a pre-dependency will be needed on the adduser package.)

On the other hand, the program might be able to determine the uid or gid from the user or group name at runtime, so that a dynamically allocated id can be used. In this case you should choose an appropriate user or group name, discussing this on ubuntu-devel and checking with the adduser in the preinst or postinst script (again, the latter is to be preferred if it is possible).

Note that changing the numeric value of an id associated with a name is very difficult, and involves searching the file system for all appropriate files. You need to think carefully whether a static or dynamic id is required, since changing your mind later will cause problems.

The use of dpkg-statoverride

This section is not intended as policy, but as a description of the use of dpkg-statoverride.

If a system administrator wishes to have a file (or directory or other such thing) installed with owner and permissions different from those in the distributed Ubuntu package, they can use the dpkg-statoverride program to instruct dpkg to use the different settings every time the file is installed. Thus the package maintainer should distribute the files with their normal permissions, and leave it for the system administrator to make any desired changes. For example, a daemon which is normally required to be setuid root, but in certain situations could be used without being setuid, should be installed setuid in the .deb. Then the local system administrator can change this if they wish. If there are two standard ways of doing it, the package maintainer can use debconf to find out the preference, and call dpkg-statoverride in the maintainer script if necessary to accommodate the system administrator's choice. Care must be taken during upgrades to not override an existing setting.

Given the above, dpkg-statoverride is essentially a tool for system administrators and would not normally be needed in the maintainer scripts. There is one type of situation, though, where calls to dpkg-statoverride would be needed in the maintainer scripts, and that involves packages which use dynamically allocated user or group ids. In such a situation, something like the following idiom can be very helpful in the package's postinst, where sysuser is a dynamically allocated id: for i in /usr/bin/foo /usr/sbin/bar do # only do something when no setting exists if ! dpkg-statoverride --list $i >/dev/null 2>&1 then #include: debconf processing, question about foo and bar if [ "$RET" = "true" ] ; then dpkg-statoverride --update --add sysuser root 4755 $i fi fi done The corresponding dpkg-statoverride --remove calls can then be made unconditionally when the package is purged.

Customized programs Architecture specification strings

If a program needs to specify an architecture specification string in some place, it should select one of the strings provided by dpkg-architecture -L. The strings are in the format os-arch, though the OS part is sometimes elided, as when the OS is Linux.

Currently, the strings are: i386 ia64 alpha amd64 armeb arm hppa m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc darwin-i386 darwin-ia64 darwin-alpha darwin-amd64 darwin-armeb darwin-arm darwin-hppa darwin-m32r darwin-m68k darwin-mips darwin-mipsel darwin-powerpc darwin-ppc64 darwin-s390 darwin-s390x darwin-sh3 darwin-sh3eb darwin-sh4 darwin-sh4eb darwin-sparc freebsd-i386 freebsd-ia64 freebsd-alpha freebsd-amd64 freebsd-armeb freebsd-arm freebsd-hppa freebsd-m32r freebsd-m68k freebsd-mips freebsd-mipsel freebsd-powerpc freebsd-ppc64 freebsd-s390 freebsd-s390x freebsd-sh3 freebsd-sh3eb freebsd-sh4 freebsd-sh4eb freebsd-sparc kfreebsd-i386 kfreebsd-ia64 kfreebsd-alpha kfreebsd-amd64 kfreebsd-armeb kfreebsd-arm kfreebsd-hppa kfreebsd-m32r kfreebsd-m68k kfreebsd-mips kfreebsd-mipsel kfreebsd-powerpc kfreebsd-ppc64 kfreebsd-s390 kfreebsd-s390x kfreebsd-sh3 kfreebsd-sh3eb kfreebsd-sh4 kfreebsd-sh4eb kfreebsd-sparc knetbsd-i386 knetbsd-ia64 knetbsd-alpha knetbsd-amd64 knetbsd-armeb knetbsd-arm knetbsd-hppa knetbsd-m32r knetbsd-m68k knetbsd-mips knetbsd-mipsel knetbsd-powerpc knetbsd-ppc64 knetbsd-s390 knetbsd-s390x knetbsd-sh3 knetbsd-sh3eb knetbsd-sh4 knetbsd-sh4eb knetbsd-sparc netbsd-i386 netbsd-ia64 netbsd-alpha netbsd-amd64 netbsd-armeb netbsd-arm netbsd-hppa netbsd-m32r netbsd-m68k netbsd-mips netbsd-mipsel netbsd-powerpc netbsd-ppc64 netbsd-s390 netbsd-s390x netbsd-sh3 netbsd-sh3eb netbsd-sh4 netbsd-sh4eb netbsd-sparc openbsd-i386 openbsd-ia64 openbsd-alpha openbsd-amd64 openbsd-armeb openbsd-arm openbsd-hppa openbsd-m32r openbsd-m68k openbsd-mips openbsd-mipsel openbsd-powerpc openbsd-ppc64 openbsd-s390 openbsd-s390x openbsd-sh3 openbsd-sh3eb openbsd-sh4 openbsd-sh4eb openbsd-sparc hurd-i386 hurd-ia64 hurd-alpha hurd-amd64 hurd-armeb hurd-arm hurd-hppa hurd-m32r hurd-m68k hurd-mips hurd-mipsel hurd-powerpc hurd-ppc64 hurd-s390 hurd-s390x hurd-sh3 hurd-sh3eb hurd-sh4 hurd-sh4eb hurd-sparc

Note that we don't want to use arch-debian-linux to apply to the rule architecture-vendor-os since this would make our programs incompatible with other Linux distributions. We also don't use something like arch-unknown-linux, since the unknown does not look very good.

Daemons

The configuration files /etc/services, /etc/protocols, and /etc/rpc are managed by the netbase package and must not be modified by other packages.

If a package requires a new entry in one of these files, the maintainer should get in contact with the netbase maintainer, who will add the entries and release a new version of the netbase package.

The configuration file /etc/inetd.conf must not be modified by the package's scripts except via the update-inetd script or the DebianNet.pm Perl module. See their documentation for details on how to add entries.

If a package wants to install an example entry into /etc/inetd.conf, the entry must be preceded with exactly one hash character (#). Such lines are treated as "commented out by user" by the update-inetd script and are not changed or activated during package updates.

Using pseudo-ttys and modifying wtmp, utmp and lastlog

Some programs need to create pseudo-ttys. This should be done using Unix98 ptys if the C library supports it. The resulting program must not be installed setuid root, unless that is required for other functionality.

The files /var/run/utmp, /var/log/wtmp and /var/log/lastlog must be installed writable by group utmp. Programs which need to modify those files must be installed setgid utmp.

Editors and pagers

Some programs have the ability to launch an editor or pager program to edit or display a text document. Since there are lots of different editors and pagers available in the Ubuntu distribution, the system administrator and each user should have the possibility to choose their preferred editor and pager.

In addition, every program should choose a good default editor/pager if none is selected by the user or system administrator.

Thus, every program that launches an editor or pager must use the EDITOR or PAGER environment variable to determine the editor or pager the user wishes to use. If these variables are not set, the programs /usr/bin/editor and /usr/bin/pager should be used, respectively.

These two files are managed through the dpkg "alternatives" mechanism. Thus every package providing an editor or pager must call the update-alternatives script to register these programs.

If it is very hard to adapt a program to make use of the EDITOR or PAGER variables, that program may be configured to use /usr/bin/sensible-editor and /usr/bin/sensible-pager as the editor or pager program respectively. These are two scripts provided in the Ubuntu base system that check the EDITOR and PAGER variables and launch the appropriate program, and fall back to /usr/bin/editor and /usr/bin/pager if the variable is not set.

A program may also use the VISUAL environment variable to determine the user's choice of editor. If it exists, it should take precedence over EDITOR. This is in fact what /usr/bin/sensible-editor does.

It is not required for a package to depend on editor and pager, nor is it required for a package to provide such virtual packages. The Ubuntu base system already provides an editor and a pager program.

Web servers and applications

This section describes the locations and URLs that should be used by all web servers and web applications in the Ubuntu system.

Cgi-bin executable files are installed in the directory /usr/lib/cgi-bin/cgi-bin-name and should be referred to as http://localhost/cgi-bin/cgi-bin-name

Access to HTML documents

HTML documents for a package are stored in /usr/share/doc/package and can be referred to as http://localhost/doc/package/filename

The web server should restrict access to the document tree so that only clients on the same host can read the documents. If the web server does not support such access controls, then it should not provide access at all, or ask about providing access during installation.

Access to images

It is recommended that images for a package be stored in /usr/share/images/package and may be referred to through an alias /images/ as http://localhost/images/<package>/<filename>

Web Document Root

Web Applications should try to avoid storing files in the Web Document Root. Instead they should use the /usr/share/doc/package directory for documents and register the Web Application via the doc-base package. If access to the web document root is unavoidable then use /var/www as the Document Root. This might be just a symbolic link to the location where the system administrator has put the real document root.

Providing httpd and/or httpd-cgi

All web servers should provide the virtual package httpd. If a web server has CGI support it should provide httpd-cgi additionally.

All web applications which do not contain CGI scripts should depend on httpd, all those web applications which do contain CGI scripts, should depend on httpd-cgi.

Mail transport, delivery and user agents

Ubuntu packages which process electronic mail, whether mail user agents (MUAs) or mail transport agents (MTAs), must ensure that they are compatible with the configuration decisions below. Failure to do this may result in lost mail, broken From: lines, and other serious brain damage!

The mail spool is /var/mail and the interface to send a mail message is /usr/sbin/sendmail (as per the FHS). On older systems, the mail spool may be physically located in /var/spool/mail, but all access to the mail spool should be via the /var/mail symlink. The mail spool is part of the base system and not part of the MTA package.

All Ubuntu MUAs, MTAs, MDAs and other mailbox accessing programs (such as IMAP daemons) must lock the mailbox in an NFS-safe way. This means that fcntl() locking must be combined with dot locking. To avoid deadlocks, a program should use fcntl() first and dot locking after this, or alternatively implement the two locking methods in a non blocking way If it is not possible to establish both locks, the system shouldn't wait for the second lock to be established, but remove the first lock, wait a (random) time, and start over locking again. . Using the functions maillock and mailunlock provided by the liblockfile* You will need to depend on liblockfile1 (>>1.01) to use these functions. packages is the recommended way to realize this.

Mailboxes are generally either mode 600 and owned by user or mode 660 and owned by user:mail There are two traditional permission schemes for mail spools: mode 600 with all mail delivery done by processes running as the destination user, or mode 660 and owned by group mail with mail delivery done by a process running as a system user in group mail. Historically, Debian required mode 660 mail spools to enable the latter model, but that model has become increasingly uncommon and the principle of least privilege indicates that mail systems that use the first model should use permissions of 600. If delivery to programs is permitted, it's easier to keep the mail system secure if the delivery agent runs as the destination user. Debian Policy therefore permits either scheme. . The local system administrator may choose a different permission scheme; packages should not make assumptions about the permission and ownership of mailboxes unless required (such as when creating a new mailbox). A MUA may remove a mailbox (unless it has nonstandard permissions) in which case the MTA or another MUA must recreate it if needed.

The mail spool is 2775 root:mail, and MUAs should be setgid mail to do the locking mentioned above (and must obviously avoid accessing other users' mailboxes using this privilege).

/etc/aliases is the source file for the system mail aliases (e.g., postmaster, usenet, etc.), it is the one which the sysadmin and postinst scripts may edit. After /etc/aliases is edited the program or human editing it must call newaliases. All MTA packages must come with a newaliases program, even if it does nothing, but older MTA packages did not do this so programs should not fail if newaliases cannot be found. Note that because of this, all MTA packages must have Provides, Conflicts and Replaces: mail-transport-agent control file fields.

The convention of writing forward to address in the mailbox itself is not supported. Use a .forward file instead.

The rmail program used by UUCP for incoming mail should be /usr/sbin/rmail. Likewise, rsmtp, for receiving batch-SMTP-over-UUCP, should be /usr/sbin/rsmtp if it is supported.

If your package needs to know what hostname to use on (for example) outgoing news and mail messages which are generated locally, you should use the file /etc/mailname. It will contain the portion after the username and @ (at) sign for email addresses of users on the machine (followed by a newline).

Such a package should check for the existence of this file when it is being configured. If it exists, it should be used without comment, although an MTA's configuration script may wish to prompt the user even if it finds that this file exists. If the file does not exist, the package should prompt the user for the value (preferably using debconf) and store it in /etc/mailname as well as using it in the package's configuration. The prompt should make it clear that the name will not just be used by that package. For example, in this situation the inn package could say something like: Please enter the "mail name" of your system. This is the hostname portion of the address to be shown on outgoing news and mail messages. The default is syshostname, your system's host name. Mail name ["syshostname"]: where syshostname is the output of hostname --fqdn.

News system configuration

All the configuration files related to the NNTP (news) servers and clients should be located under /etc/news.

There are some configuration issues that apply to a number of news clients and server packages on the machine. These are: /etc/news/organization A string which should appear as the organization header for all messages posted by NNTP clients on the machine /etc/news/server Contains the FQDN of the upstream NNTP server, or localhost if the local machine is an NNTP server. Other global files may be added as required for cross-package news configuration.

Programs for the X Window System Providing X support and package priorities

Programs that can be configured with support for the X Window System must be configured to do so and must declare any package dependencies necessary to satisfy their runtime requirements when using the X Window System. If such a package is of higher priority than the X packages on which it depends, it is required that either the X-specific components be split into a separate package, or that an alternative version of the package, which includes X support, be provided, or that the package's priority be lowered.

Packages providing an X server

Packages that provide an X server that, directly or indirectly, communicates with real input and display hardware should declare in their control data that they provide the virtual package xserver. This implements current practice, and provides an actual policy for usage of the xserver virtual package which appears in the virtual packages list. In a nutshell, X servers that interface directly with the display and input hardware or via another subsystem (e.g., GGI) should provide xserver. Things like Xvfb, Xnest, and Xprt should not.

Packages providing a terminal emulator

Packages that provide a terminal emulator for the X Window System which meet the criteria listed below should declare in their control data that they provide the virtual package x-terminal-emulator. They should also register themselves as an alternative for /usr/bin/x-terminal-emulator, with a priority of 20.

To be an x-terminal-emulator, a program must: Be able to emulate a DEC VT100 terminal, or a compatible terminal. Support the command-line option -e command, which creates a new terminal window "New terminal window" does not necessarily mean a new top-level X window directly parented by the window manager; it could, if the terminal emulator application were so coded, be a new "view" in a multiple-document interface (MDI). and runs the specified command, interpreting the entirety of the rest of the command line as a command to pass straight to exec, in the manner that xterm does. Support the command-line option -T title, which creates a new terminal window with the window title title.

Packages providing a window manager

Packages that provide a window manager should declare in their control data that they provide the virtual package x-window-manager. They should also register themselves as an alternative for /usr/bin/x-window-manager, with a priority calculated as follows: Start with a priority of 20. If the window manager supports the Debian menu system, add 20 points if this support is available in the package's default configuration (i.e., no configuration files belonging to the system or user have to be edited to activate the feature); if configuration files must be modified, add only 10 points.

If the window manager complies with , written by the , add 40 points. If the window manager permits the X session to be restarted using a different window manager (without killing the X server) in its default configuration, add 10 points; otherwise add none.

Packages providing fonts

Packages that provide fonts for the X Window System For the purposes of Ubuntu Policy, a "font for the X Window System" is one which is accessed via X protocol requests. Fonts for the Linux console, for PostScript renderer, or any other purpose, do not fit this definition. Any tool which makes such fonts available to the X Window System, however, must abide by this font policy. must do a number of things to ensure that they are both available without modification of the X or font server configuration, and that they do not corrupt files used by other font packages to register information about themselves. Fonts of any type supported by the X Window System must be in a separate binary package from any executables, libraries, or documentation (except that specific to the fonts shipped, such as their license information). If one or more of the fonts so packaged are necessary for proper operation of the package with which they are associated the font package may be Recommended; if the fonts merely provide an enhancement, a Suggests relationship may be used. Packages must not Depend on font packages. This is because the X server may retrieve fonts from the local file system or over the network from an X font server; the Ubuntu package system is empowered to deal only with the local file system. BDF fonts must be converted to PCF fonts with the bdftopcf utility (available in the xfonts-utils package, gzipped, and placed in a directory that corresponds to their resolution: 100 dpi fonts must be placed in /usr/share/fonts/X11/100dpi/. 75 dpi fonts must be placed in /usr/share/fonts/X11/75dpi/. Character-cell fonts, cursor fonts, and other low-resolution fonts must be placed in /usr/share/fonts/X11/misc/. Type 1 fonts must be placed in /usr/share/fonts/X11/Type1/. If font metric files are available, they must be placed here as well. Subdirectories of /usr/share/fonts/X11/ other than those listed above must be neither created nor used. (The PEX, CID, Speedo, and cyrillic directories are excepted for historical reasons, but installation of files into these directories remains discouraged.) Font packages may, instead of placing files directly in the X font directories listed above, provide symbolic links in that font directory pointing to the files' actual location in the filesystem. Such a location must comply with the FHS. Font packages should not contain both 75dpi and 100dpi versions of a font. If both are available, they should be provided in separate binary packages with -75dpi or -100dpi appended to the names of the packages containing the corresponding fonts. Fonts destined for the misc subdirectory should not be included in the same package as 75dpi or 100dpi fonts; instead, they should be provided in a separate package with -misc appended to its name. Font packages must not provide the files fonts.dir, fonts.alias, or fonts.scale in a font directory: fonts.dir files must not be provided at all. fonts.alias and fonts.scale files, if needed, should be provided in the directory /etc/X11/fonts/fontdir/package.extension, where fontdir is the name of the subdirectory of /usr/share/fonts/X11/ where the package's corresponding fonts are stored (e.g., 75dpi or misc), package is the name of the package that provides these fonts, and extension is either scale or alias, whichever corresponds to the file contents. Font packages must declare a dependency on xfonts-utils in their control data. Font packages that provide one or more fonts.scale files as described above must invoke update-fonts-scale on each directory into which they installed fonts before invoking update-fonts-dir on that directory. This invocation must occur in both the postinst (for all arguments) and postrm (for all arguments except upgrade) scripts. Font packages that provide one or more fonts.alias files as described above must invoke update-fonts-alias on each directory into which they installed fonts. This invocation must occur in both the postinst (for all arguments) and postrm (for all arguments except upgrade) scripts. Font packages must invoke update-fonts-dir on each directory into which they installed fonts. This invocation must occur in both the postinst (for all arguments) and postrm (for all arguments except upgrade) scripts. Font packages must not provide alias names for the fonts they include which collide with alias names already in use by fonts already packaged. Font packages must not provide fonts with the same XLFD registry name as another font already packaged.

Application defaults files

Application defaults files must be installed in the directory /etc/X11/app-defaults/ (use of a localized subdirectory of /etc/X11/ as described in the X Toolkit Intrinsics - C Language Interface manual is also permitted). They must be registered as conffiles or handled as configuration files.

Customization of programs' X resources may also be supported with the provision of a file with the same name as that of the package placed in the /etc/X11/Xresources/ directory, which must registered as a conffile or handled as a configuration file. Note that this mechanism is not the same as using app-defaults; app-defaults are tied to the client binary on the local file system, whereas X resources are stored in the X server and affect all connecting clients.

Installation directory issues

Packages using the X Window System should not be configured to install files under the /usr/X11R6/ directory. The /usr/X11R6/ directory hierarchy should be regarded as obsolete.

Programs that use GNU autoconf and automake are usually easily configured at compile time to use /usr/ instead of /usr/X11R6/, and this should be done whenever possible. Configuration files for window managers and display managers should be placed in a subdirectory of /etc/X11/ corresponding to the package name due to these programs' tight integration with the mechanisms of the X Window System. Application-level programs should use the /etc/ directory unless otherwise mandated by policy.

The installation of files into subdirectories of /usr/X11R6/include/X11/ and /usr/X11R6/lib/X11/ is now prohibited; package maintainers should determine if subdirectories of /usr/lib/ and /usr/share/ can be used instead.

Packages should install any relevant files into the directories /usr/include/X11/ and /usr/lib/X11/, but if they do so, they must pre-depend on x11-common (>= 1:7.0.0)

These libraries used to be all symbolic links. However, with X11R7, /usr/include/X11 and /usr/lib/X11 are now real directories, and packages should ship their files here instead of in /usr/X11R6/{include,lib}/X11. x11-common (>= 1:7.0.0) is the package responsible for converting these symlinks into directories.

The OSF/Motif and OpenMotif libraries

Programs that require the non-DFSG-compliant OSF/Motif or OpenMotif libraries OSF/Motif and OpenMotif are collectively referred to as "Motif" in this policy document. should be compiled against and tested with LessTif (a free re-implementation of Motif) instead. If the maintainer judges that the program or programs do not work sufficiently well with LessTif to be distributed and supported, but do so when compiled against Motif, then two versions of the package should be created; one linked statically against Motif and with -smotif appended to the package name, and one linked dynamically against Motif and with -dmotif appended to the package name.

Both Motif-linked versions are dependent upon non-DFSG-compliant software and thus cannot be uploaded to the main distribution; if the software is itself DFSG-compliant it may be uploaded to the contrib distribution. While known existing versions of Motif permit unlimited redistribution of binaries linked against the library (whether statically or dynamically), it is the package maintainer's responsibility to determine whether this is permitted by the license of the copy of Motif in their possession.

Icon caching

Ubuntu: Packages that provide icons in a subdirectory of /usr/share/icons must invoke update-icon-caches on each directory into which they installed icons. This invocation must occur in both the postinst (for all arguments) and postrm (for all arguments) scripts If you are using debhelper, the dh_icons program will do this work for you. . Doing this allows GTK+ to make use of the icon cache for efficiency gains, while ensuring that the cache does not get out of date and cause problems for some applications.

If update-icon-caches is not installed, this invocation may safely be skipped. No additional dependency is necessary.

Perl programs and modules

Perl programs and modules should follow the current Perl policy.

The Perl policy can be found in the perl-policy files in the debian-policy package. It is also available from the Debian web mirrors at .

Emacs lisp programs

Please refer to the "Debian Emacs Policy" for details of how to package emacs lisp programs.

The Emacs policy is available in debian-emacs-policy.gz of the emacsen-common package. It is also available from the Debian web mirrors at .

Games

The permissions on /var/games are mode 755, owner root and group root.

Each game decides on its own security policy.

Games which require protected, privileged access to high-score files, saved games, etc., may be made set-group-id (mode 2755) and owned by root:games, and use files and directories with appropriate permissions (770 root:games, for example). They must not be made set-user-id, as this causes security problems. (If an attacker can subvert any set-user-id game they can overwrite the executable of any other, causing other players of these games to run a Trojan horse program. With a set-group-id game the attacker only gets access to less important game data, and if they can get at the other players' accounts at all it will take considerably more effort.)

Some packages, for example some fortune cookie programs, are configured by the upstream authors to install with their data files or other static information made unreadable so that they can only be accessed through set-id programs provided. You should not do this in an Ubuntu package: anyone can download the .deb file and read the data from it, so there is no point making the files unreadable. Not making the files unreadable also means that you don't have to make so many programs set-id, which reduces the risk of a security hole.

As described in the FHS, binaries of games should be installed in the directory /usr/games. This also applies to games that use the X Window System. Manual pages for games (X and non-X games) should be installed in /usr/share/man/man6.

 Documentation Manual pages

You should install manual pages in nroff source form, in appropriate places under /usr/share/man. You should only use sections 1 to 9 (see the FHS for more details). You must not install a pre-formatted "cat page".

Each program, utility, and function should have an associated manual page included in the same package. It is suggested that all configuration files also have a manual page included as well. Manual pages for protocols and other auxiliary things are optional.

If no manual page is available, this is considered as a bug and should be reported to the Ubuntu Bug Tracking System (the maintainer of the package is allowed to write this bug report themselves, if they so desire). Do not close the bug report until a proper man page is available. It is not very hard to write a man page. See the , , the examples created by debmake or dh_make, the helper programs help2man, or the directory /usr/share/doc/man-db/examples.

You may forward a complaint about a missing man page to the upstream authors, and mark the bug as forwarded in the Ubuntu bug tracking system. Even though the GNU Project do not in general consider the lack of a man page to be a bug, we do; if they tell you that they don't consider it a bug you should leave the bug in our bug tracking system open anyway.

Manual pages should be installed compressed using gzip -9.

If one man page needs to be accessible via several names it is better to use a symbolic link than the .so feature, but there is no need to fiddle with the relevant parts of the upstream source to change from .so to symlinks: don't do it unless it's easy. You should not create hard links in the manual page directories, nor put absolute filenames in .so directives. The filename in a .so in a man page should be relative to the base of the man page tree (usually /usr/share/man). If you do not create any links (whether symlinks, hard links, or .so directives) in the file system to the alternate names of the man page, then you should not rely on man finding your man page under those names based solely on the information in the man page's header. Supporting this in man often requires unreasonable processing time to find a manual page or to report that none exists, and moves knowledge into man's database that would be better left in the file system. This support is therefore deprecated and will cease to be present in the future.

Manual pages in locale-specific subdirectories of /usr/share/man should use either UTF-8 or the usual legacy encoding for that language (normally the one corresponding to the shortest relevant locale name in /usr/share/i18n/SUPPORTED). For example, pages under /usr/share/man/fr should use either UTF-8 or ISO-8859-1. man will automatically detect whether UTF-8 is in use. In future, all manual pages will be required to use UTF-8.

A country name (the DE in de_DE) should not be included in the subdirectory name unless it indicates a significant difference in the language, as this excludes speakers of the language in other countries. At the time of writing, Chinese and Portuguese are the main languages with such differences, so pt_BR, zh_CN, and zh_TW are all allowed.

Due to limitations in current implementations, all characters in the manual page source should be representable in the usual legacy encoding for that language, even if the file is actually encoded in UTF-8. Safe alternative ways to write many characters outside that range may be found in .

Info documents

Info documents should be installed in /usr/share/info. They should be compressed with gzip -9.

Your package should call install-info to update the Info dir file in its postinst script when called with a configure argument, for example: install-info --quiet --section Development Development \ /usr/share/info/foobar.info

It is a good idea to specify a section for the location of your program; this is done with the --section switch. To determine which section to use, you should look at /usr/share/info/dir on your system and choose the most relevant (or create a new section if none of the current sections are relevant). Note that the --section flag takes two arguments; the first is a regular expression to match (case-insensitively) against an existing section, the second is used when creating a new one.

You should remove the entries in the prerm script when called with a remove argument: install-info --quiet --remove /usr/share/info/foobar.info

If install-info cannot find a description entry in the Info file you must supply one. See for details.

 Additional documentation

Any additional documentation that comes with the package may be installed at the discretion of the package maintainer. Plain text documentation should be installed in the directory /usr/share/doc/package, where package is the name of the package, and compressed with gzip -9 unless it is small.

If a package comes with large amounts of documentation which many users of the package will not require you should create a separate binary package to contain it, so that it does not take up disk space on the machines of users who do not need or want it installed.

It is often a good idea to put text information files (READMEs, changelogs, and so forth) that come with the source package in /usr/share/doc/package in the binary package. However, you don't need to install the instructions for building and installing the package, of course!

Packages must not require the existence of any files in /usr/share/doc/ in order to function The system administrator should be able to delete files in /usr/share/doc/ without causing any programs to break. . Any files that are referenced by programs but are also useful as stand alone documentation should be installed under /usr/share/package/ with symbolic links from /usr/share/doc/package.

/usr/share/doc/package may be a symbolic link to another directory in /usr/share/doc only if the two packages both come from the same source and the first package Depends on the second.

Please note that this does not override the section on changelog files below, so the file /usr/share/package/changelog.Debian.gz must refer to the changelog for the current version of package in question. In practice, this means that the sources of the target and the destination of the symlink must be the same (same source package and version).

Former Debian releases placed all additional documentation in /usr/doc/package. This has been changed to /usr/share/doc/package, and packages must not put documentation in the directory /usr/doc/package. At this phase of the transition, we no longer require a symbolic link in /usr/doc/. At a later point, policy shall change to make the symbolic links a bug.

Preferred documentation formats

The unification of Ubuntu documentation is being carried out via HTML.

If your package comes with extensive documentation in a markup format that can be converted to various other formats you should if possible ship HTML versions in a binary package, in the directory /usr/share/doc/appropriate-package or its subdirectories. The rationale: The important thing here is that HTML docs should be available in some package, not necessarily in the main binary package.

Other formats such as PostScript may be provided at the package maintainer's discretion.

Copyright information

Every package must be accompanied by a verbatim copy of its copyright and distribution license in the file /usr/share/doc/package/copyright. This file must neither be compressed nor be a symbolic link.

In addition, the copyright file must say where the upstream sources (if any) were obtained. It should name the original authors of the package and the Ubuntu maintainer(s) who were involved with its creation.

A copy of the file which will be installed in /usr/share/doc/package/copyright should be in debian/copyright in the source package.

/usr/share/doc/package may be a symbolic link to another directory in /usr/share/doc only if the two packages both come from the same source and the first package Depends on the second. These rules are important because copyrights must be extractable by mechanical means.

Packages distributed under the UCB BSD license, the Apache license (version 2.0), the Artistic license, the GNU GPL (version 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,

In particular, /usr/share/common-licenses/BSD, /usr/share/common-licenses/Apache-2.0, /usr/share/common-licenses/Artistic, /usr/share/common-licenses/GPL-2, /usr/share/common-licenses/GPL-3, /usr/share/common-licenses/LGPL-2, /usr/share/common-licenses/LGPL-2.1, /usr/share/common-licenses/LGPL-3, /usr/share/common-licenses/GFDL-1.2, and /usr/share/common-licenses/GFDL-1.3 respectively.

rather than quoting them in the copyright file.

You should not use the copyright file as a general README file. If your package has such a file it should be installed in /usr/share/doc/package/README or README.Debian or some other appropriate place.

 Examples

Any examples (configurations, source files, whatever), should be installed in a directory /usr/share/doc/package/examples. These files should not be referenced by any program: they're there for the benefit of the system administrator and users as documentation only. Architecture-specific example files should be installed in a directory /usr/lib/package/examples with symbolic links to them from /usr/share/doc/package/examples, or the latter directory itself may be a symbolic link to the former.

If the purpose of a package is to provide examples, then the example files may be installed into /usr/share/doc/package.

Changelog files

Packages that are not Debian-native must contain a compressed copy of the debian/changelog file from the Debian source tree in /usr/share/doc/package with the name changelog.Debian.gz.

If an upstream changelog is available, it should be accessible as /usr/share/doc/package/changelog.gz in plain text. If the upstream changelog is distributed in HTML, it should be made available in that form as /usr/share/doc/package/changelog.html.gz and a plain text changelog.gz should be generated from it using, for example, lynx -dump -nolist. If the upstream changelog files do not already conform to this naming convention, then this may be achieved either by renaming the files, or by adding a symbolic link, at the maintainer's discretion. Rationale: People should not have to look in places for upstream changelogs merely because they are given different names or are distributed in HTML format.

All of these files should be installed compressed using gzip -9, as they will become large with time even if they start out small.

If the package has only one changelog which is used both as the Debian changelog and the upstream one because there is no separate upstream maintainer then that changelog should usually be installed as /usr/share/doc/package/changelog.gz; if there is a separate upstream maintainer, but no upstream changelog, then the Debian changelog should still be called changelog.Debian.gz.

For details about the format and contents of the Debian changelog file, please see .

Introduction and scope of these appendices

These appendices are taken essentially verbatim from the now-deprecated Packaging Manual, version 3.2.1.0. They are the chapters which are likely to be of use to package maintainers and which have not already been included in the policy document itself. Most of these sections are very likely not relevant to policy; they should be treated as documentation for the packaging system. Please note that these appendices are included for convenience, and for historical reasons: they used to be part of policy package, and they have not yet been incorporated into dpkg documentation. However, they still have value, and hence they are presented here.

They have not yet been checked to ensure that they are compatible with the contents of policy, and if there are any contradictions, the version in the main policy document takes precedence. The remaining chapters of the old Packaging Manual have also not been read in detail to ensure that there are not parts which have been left out. Both of these will be done in due course.

Certain parts of the Packaging manual were integrated into the Policy Manual proper, and removed from the appendices. Links have been placed from the old locations to the new ones.

dpkg is a suite of programs for creating binary package files and installing and removing them on Unix systems. dpkg is targeted primarily at Debian GNU/Linux and Ubuntu, but may work on or be ported to other systems.

The binary packages are designed for the management of installed executable programs (usually compiled binaries) and their associated data, though source code examples and documentation are provided as part of some packages.

This manual describes the technical aspects of creating Debian binary packages (.deb files). It documents the behavior of the package management programs dpkg, dselect et al. and the way they interact with packages.

It also documents the interaction between dselect's core and the access method scripts it uses to actually install the selected packages, and describes how to create a new access method.

This manual does not go into detail about the options and usage of the package building and installation tools. It should therefore be read in conjunction with those programs' man pages.

The utility programs which are provided with dpkg for managing various system configuration and similar issues, such as update-rc.d and install-info, are not described in detail here - please see their man pages.

It is assumed that the reader is reasonably familiar with the dpkg System Administrators' manual. Unfortunately this manual does not yet exist.

The Debian version of the FSF's GNU hello program is provided as an example for people wishing to create Debian packages. The Debian debmake package is recommended as a very helpful tool in creating and maintaining Debian packages. However, while the tools and examples are helpful, they do not replace the need to read and follow the Policy and Programmer's Manual.

 Binary packages (from old Packaging Manual)

The binary package has two main sections. The first part consists of various control information files and scripts used by dpkg when installing and removing. See .

The second part is an archive containing the files and directories to be installed.

In the future binary packages may also contain other components, such as checksums and digital signatures. The format for the archive is described in full in the deb(5) man page.

Creating package files - dpkg-deb

All manipulation of binary package files is done by dpkg-deb; it's the only program that has knowledge of the format. (dpkg-deb may be invoked by calling dpkg, as dpkg will spot that the options requested are appropriate to dpkg-deb and invoke that instead with the same arguments.)

In order to create a binary package you must make a directory tree which contains all the files and directories you want to have in the file system data part of the package. In Debian-format source packages this directory is usually debian/tmp, relative to the top of the package's source tree.

They should have the locations (relative to the root of the directory tree you're constructing) ownerships and permissions which you want them to have on the system when they are installed.

With current versions of dpkg the uid/username and gid/groupname mappings for the users and groups being used should be the same on the system where the package is built and the one where it is installed.

You need to add one special directory to the root of the miniature file system tree you're creating: DEBIAN. It should contain the control information files, notably the binary package control file (see ).

The DEBIAN directory will not appear in the file system archive of the package, and so won't be installed by dpkg when the package is installed.

When you've prepared the package, you should invoke: dpkg --build directory

This will build the package in directory.deb. (dpkg knows that --build is a dpkg-deb option, so it invokes dpkg-deb with the same arguments to build the package.)

See the man page for details of how to examine the contents of this newly-created file. You may find the output of following commands enlightening: dpkg-deb --info filename.deb dpkg-deb --contents filename.deb dpkg --contents filename.deb To view the copyright file for a package you could use this command: dpkg --fsys-tarfile filename.deb | tar xOf - --wildcards \*/copyright | pager

Package control information files

The control information portion of a binary package is a collection of files with names known to dpkg. It will treat the contents of these files specially - some of them contain information used by dpkg when installing or removing the package; others are scripts which the package maintainer wants dpkg to run.

It is possible to put other files in the package control area, but this is not generally a good idea (though they will largely be ignored).

Here is a brief list of the control info files supported by dpkg and a summary of what they're used for.

control

This is the key description file used by dpkg. It specifies the package's name and version, gives its description for the user, states its relationships with other packages, and so forth. See and .

It is usually generated automatically from information in the source package by the dpkg-gencontrol program, and with assistance from dpkg-shlibdeps. See .

postinst, preinst, postrm, prerm

These are executable files (usually scripts) which dpkg runs during installation, upgrade and removal of packages. They allow the package to deal with matters which are particular to that package or require more complicated processing than that provided by dpkg. Details of when and how they are called are in .

It is very important to make these scripts idempotent. See .

The maintainer scripts are guaranteed to run with a controlling terminal and can interact with the user. See .

conffiles This file contains a list of configuration files which are to be handled automatically by dpkg (see ). Note that not necessarily every configuration file should be listed here. shlibs This file contains a list of the shared libraries supplied by the package, with dependency details for each. This is used by dpkg-shlibdeps when it determines what dependencies are required in a package control file. The shlibs file format is described on .

The main control information file: control

The most important control information file used by dpkg when it installs a package is control. It contains all the package's "vital statistics".

The binary package control files of packages built from Debian sources are made by a special tool, dpkg-gencontrol, which reads debian/control and debian/changelog to find the information it needs. See for more details.

The fields in binary package control files are listed in .

A description of the syntax of control files and the purpose of the fields is available in .

Time Stamps

See .

Source packages (from old Packaging Manual)

The Debian binary packages in the distribution are generated from Debian sources, which are in a special format to assist the easy and automatic building of binaries.

Tools for processing source packages

Various tools are provided for manipulating source packages; they pack and unpack sources and help build of binary packages and help manage the distribution of new versions.

They are introduced and typical uses described here; see for full documentation about their arguments and operation.

For examples of how to construct a Debian source package, and how to use those utilities that are used by Debian source packages, please see the hello example package.

dpkg-source - packs and unpacks Debian source packages

This program is frequently used by hand, and is also called from package-independent automated building scripts such as dpkg-buildpackage.

To unpack a package it is typically invoked with dpkg-source -x .../path/to/filename.dsc

with the filename.tar.gz and filename.diff.gz (if applicable) in the same directory. It unpacks into package-version, and if applicable package-version.orig, in the current directory.

To create a packed source archive it is typically invoked: dpkg-source -b package-version

This will create the .dsc, .tar.gz and .diff.gz (if appropriate) in the current directory. dpkg-source does not clean the source tree first - this must be done separately if it is required.

See also .

 dpkg-buildpackage - overall package-building control script

dpkg-buildpackage is a script which invokes dpkg-source, the debian/rules targets clean, build and binary, dpkg-genchanges and gpg (or pgp) to build a signed source and binary package upload.

It is usually invoked by hand from the top level of the built or unbuilt source directory. It may be invoked with no arguments; useful arguments include: -uc, -us

Do not sign the .changes file or the source package .dsc file, respectively.

-psign-command

Invoke sign-command instead of finding gpg or pgp on the PATH. sign-command must behave just like gpg or pgp.

 -rroot-command

When root privilege is required, invoke the command root-command. root-command should invoke its first argument as a command, from the PATH if necessary, and pass its second and subsequent arguments to the command it calls. If no root-command is supplied then dpkg-buildpackage will take no special action to gain root privilege, so that for most packages it will have to be invoked as root to start with.

 -b, -B

Two types of binary-only build and upload - see .

dpkg-gencontrol - generates binary package control files

This program is usually called from debian/rules (see ) in the top level of the source tree.

This is usually done just before the files and directories in the temporary directory tree where the package is being built have their permissions and ownerships set and the package is constructed using dpkg-deb/ This is so that the control file which is produced has the right permissions .

dpkg-gencontrol must be called after all the files which are to go into the package have been placed in the temporary build directory, so that its calculation of the installed size of a package is correct.

It is also necessary for dpkg-gencontrol to be run after dpkg-shlibdeps so that the variable substitutions created by dpkg-shlibdeps in debian/substvars are available.

For a package which generates only one binary package, and which builds it in debian/tmp relative to the top of the source package, it is usually sufficient to call dpkg-gencontrol.

Sources which build several binaries will typically need something like: dpkg-gencontrol -Pdebian/tmp-pkg -ppackage The -P tells dpkg-gencontrol that the package is being built in a non-default directory, and the -p tells it which package's control file should be generated.

dpkg-gencontrol also adds information to the list of files in debian/files, for the benefit of (for example) a future invocation of dpkg-genchanges.

 dpkg-shlibdeps - calculates shared library dependencies

This program is usually called from debian/rules just before dpkg-gencontrol (see ), in the top level of the source tree.

Its arguments are executables and shared libraries

They may be specified either in the locations in the source tree where they are created or in the locations in the temporary build tree where they are installed prior to binary package creation.

for which shared library dependencies should be included in the binary package's control file.

If some of the found shared libraries should only warrant a Recommends or Suggests, or if some warrant a Pre-Depends, this can be achieved by using the -ddependency-field option before those executable(s). (Each -d option takes effect until the next -d.)

dpkg-shlibdeps does not directly cause the output control file to be modified. Instead by default it adds to the debian/substvars file variable settings like shlibs:Depends. These variable settings must be referenced in dependency fields in the appropriate per-binary-package sections of the source control file.

For example, a package that generates an essential part which requires dependencies, and optional parts that which only require a recommendation, would separate those two sets of dependencies into two different fields. At the time of writing, an example for this was the It can say in its debian/rules: dpkg-shlibdeps -dDepends program anotherprogram ... \ -dRecommends optionalpart anotheroptionalpart and then in its main control file debian/control: ... Depends: ${shlibs:Depends} Recommends: ${shlibs:Recommends} ...

Sources which produce several binary packages with different shared library dependency requirements can use the -pvarnameprefix option to override the default shlibs: prefix (one invocation of dpkg-shlibdeps per setting of this option). They can thus produce several sets of dependency variables, each of the form varnameprefix:dependencyfield, which can be referred to in the appropriate parts of the binary package control files.

dpkg-distaddfile - adds a file to debian/files

Some packages' uploads need to include files other than the source and binary package files.

dpkg-distaddfile adds a file to the debian/files file so that it will be included in the .changes file when dpkg-genchanges is run.

It is usually invoked from the binary target of debian/rules: dpkg-distaddfile filename section priority The filename is relative to the directory where dpkg-genchanges will expect to find it - this is usually the directory above the top level of the source tree. The debian/rules target should put the file there just before or just after calling dpkg-distaddfile.

The section and priority are passed unchanged into the resulting .changes file.

dpkg-genchanges - generates a .changes upload control file

This program is usually called by package-independent automatic building scripts such as dpkg-buildpackage, but it may also be called by hand.

It is usually called in the top level of a built source tree, and when invoked with no arguments will print out a straightforward .changes file based on the information in the source package's changelog and control file and the binary and source packages which should have been built.

dpkg-parsechangelog - produces parsed representation of a changelog

This program is used internally by dpkg-source et al. It may also occasionally be useful in debian/rules and elsewhere. It parses a changelog, debian/changelog by default, and prints a control-file format representation of the information in it to standard output.

dpkg-architecture - information about the build and host system

This program can be used manually, but is also invoked by dpkg-buildpackage or debian/rules to set environment or make variables which specify the build and host architecture for the package building process.

The Debianised source tree

The source archive scheme described later is intended to allow a Debianised source tree with some associated control information to be reproduced and transported easily. The Debianised source tree is a version of the original program with certain files added for the benefit of the Debianisation process, and with any other changes required made to the rest of the source code and installation scripts.

The extra files created for Debian are in the subdirectory debian of the top level of the Debianised source tree. They are described below.

debian/rules - the main building script

See .

debian/changelog

See .

Defining alternative changelog formats

It is possible to use a different format to the standard one, by providing a parser for the format you wish to use.

In order to have dpkg-parsechangelog run your parser, you must include a line within the last 40 lines of your file matching the Perl regular expression: \schangelog-format:\s+([0-9a-z]+)\W The part in parentheses should be the name of the format. For example, you might say: @@@ changelog-format: joebloggs @@@ Changelog format names are non-empty strings of alphanumerics.

If such a line exists then dpkg-parsechangelog will look for the parser as /usr/lib/dpkg/parsechangelog/format-name or /usr/local/lib/dpkg/parsechangelog/format-name; it is an error for it not to find it, or for it not to be an executable program. The default changelog format is dpkg, and a parser for it is provided with the dpkg package.

The parser will be invoked with the changelog open on standard input at the start of the file. It should read the file (it may seek if it wishes) to determine the information required and return the parsed information to standard output in the form of a series of control fields in the standard format. By default it should return information about only the most recent version in the changelog; it should accept a -vversion option to return changes information from all versions present strictly after version, and it should then be an error for version not to be present in the changelog.

The fields are: Source Version (mandatory) Distribution (mandatory) Urgency (mandatory) Maintainer (mandatory) Date Changes (mandatory)

If several versions are being returned (due to the use of -v), the urgency value should be of the highest urgency code listed at the start of any of the versions requested followed by the concatenated (space-separated) comments from all the versions requested; the maintainer, version, distribution and date should always be from the most recent version.

For the format of the Changes field see .

If the changelog format which is being parsed always or almost always leaves a blank line between individual change notes these blank lines should be stripped out, so as to make the resulting output compact.

If the changelog format does not contain date or package name information this information should be omitted from the output. The parser should not attempt to synthesize it or find it from other sources.

If the changelog does not have the expected format the parser should exit with a nonzero exit status, rather than trying to muddle through and possibly generating incorrect output.

A changelog parser may not interact with the user at all.

debian/substvars and variable substitutions

See .

debian/files

See .

debian/tmp

This is the canonical temporary location for the construction of binary packages by the binary target. The directory tmp serves as the root of the file system tree as it is being constructed (for example, by using the package's upstream makefiles install targets and redirecting the output there), and it also contains the DEBIAN subdirectory. See .

If several binary packages are generated from the same source tree it is usual to use several debian/tmpsomething directories, for example tmp-a or tmp-doc.

Whatever tmp directories are created and used by binary must of course be removed by the clean target.

 Source packages as archives

As it exists on the FTP site, a Debian source package consists of three related files. You must have the right versions of all three to be able to use them.

Debian source control file - .dsc This file is a control file used by dpkg-source to extract a source package. See . Original source archive - package_upstream-version.orig.tar.gz

This is a compressed (with gzip -9) tar file containing the source code from the upstream authors of the program.

Debianisation diff - package_upstream_version-revision.diff.gz

This is a unified context diff (diff -u) giving the changes which are required to turn the original source into the Debian source. These changes may only include editing and creating plain files. The permissions of files, the targets of symbolic links and the characteristics of special files or pipes may not be changed and no files may be removed or renamed.

All the directories in the diff must exist, except the debian subdirectory of the top of the source tree, which will be created by dpkg-source if necessary when unpacking.

The dpkg-source program will automatically make the debian/rules file executable (see below).

If there is no original source code - for example, if the package is specially prepared for Debian or the Debian maintainer is the same as the upstream maintainer - the format is slightly different: then there is no diff, and the tarfile is named package_version.tar.gz, and preferably contains a directory named package-version.

Unpacking a Debian source package without dpkg-source

dpkg-source -x is the recommended way to unpack a Debian source package. However, if it is not available it is possible to unpack a Debian source archive as follows:

Untar the tarfile, which will create a .orig directory.

Rename the .orig directory to package-version.

Create the subdirectory debian at the top of the source tree.

Apply the diff using patch -p0.

Untar the tarfile again if you want a copy of the original source code alongside the Debianised version.

It is not possible to generate a valid Debian source archive without using dpkg-source. In particular, attempting to use diff directly to generate the .diff.gz file will not work.

Restrictions on objects in source packages

The source package may not contain any hard links This is not currently detected when building source packages, but only when extracting them. Hard links may be permitted at some point in the future, but would require a fair amount of work. , device special files, sockets or setuid or setgid files. Setgid directories are allowed.

The source packaging tools manage the changes between the original and Debianised source using diff and patch. Turning the original source tree as included in the .orig.tar.gz into the debianised source must not involve any changes which cannot be handled by these tools. Problematic changes which cause dpkg-source to halt with an error when building the source package are:

Adding or removing symbolic links, sockets or pipes.

Changing the targets of symbolic links.

Creating directories, other than debian.

Changes to the contents of binary files.

 Changes which cause dpkg-source to print a warning but continue anyway are:

Removing files, directories or symlinks. Renaming a file is not treated specially - it is seen as the removal of the old file (which generates a warning, but is otherwise ignored), and the creation of the new one.

Changed text files which are missing the usual final newline (either in the original or the modified source tree).

Changes which are not represented, but which are not detected by dpkg-source, are:

Changing the permissions of files (other than debian/rules) and directories.

The debian directory and debian/rules are handled specially by dpkg-source - before applying the changes it will create the debian directory, and afterwards it will make debian/rules world-executable.

Control files and their fields (from old Packaging Manual)

Many of the tools in the dpkg suite manipulate data in a common format, known as control files. Binary and source packages have control data as do the .changes files which control the installation of uploaded files, and dpkg's internal databases are in a similar format.

Syntax of control files

See .

It is important to note that there are several fields which are optional as far as dpkg and the related tools are concerned, but which must appear in every Debian package, or whose omission may cause problems.

List of fields

See .

This section now contains only the fields that didn't belong to the Policy manual.

Filename and MSDOS-Filename

These fields in Packages files give the filename(s) of (the parts of) a package in the distribution directories, relative to the root of the Debian hierarchy. If the package has been split into several parts the parts are all listed in order, separated by spaces.

Size and MD5sum

These fields in Packages files give the size (in bytes, expressed in decimal) and MD5 checksum of the file(s) which make(s) up a binary package in the distribution. If the package is split into several parts the values for the parts are listed in order, separated by spaces.

Status

This field in dpkg's status file records whether the user wants a package installed, removed or left alone, whether it is broken (requiring re-installation) or not and what its current state on the system is. Each of these pieces of information is a single word.

Config-Version

If a package is not installed or not configured, this field in dpkg's status file records the last version of the package which was successfully configured.

Conffiles

This field in dpkg's status file contains information about the automatically-managed configuration files held by a package. This field should not appear anywhere in a package!

Obsolete fields

These are still recognized by dpkg but should not appear anywhere any more. Revision Package-Revision Package_Revision The Debian revision part of the package version was at one point in a separate control file field. This field went through several names. Recommended Old name for Recommends. Optional Old name for Suggests. Class Old name for Priority.

Configuration file handling (from old Packaging Manual)

dpkg can do a certain amount of automatic handling of package configuration files.

Whether this mechanism is appropriate depends on a number of factors, but basically there are two approaches to any particular configuration file.

The easy method is to ship a best-effort configuration in the package, and use dpkg's conffile mechanism to handle updates. If the user is unlikely to want to edit the file, but you need them to be able to without losing their changes, and a new package with a changed version of the file is only released infrequently, this is a good approach.

The hard method is to build the configuration file from scratch in the postinst script, and to take the responsibility for fixing any mistakes made in earlier versions of the package automatically. This will be appropriate if the file is likely to need to be different on each system.

Automatic handling of configuration files by dpkg

A package may contain a control area file called conffiles. This file should be a list of filenames of configuration files needing automatic handling, separated by newlines. The filenames should be absolute pathnames, and the files referred to should actually exist in the package.

When a package is upgraded dpkg will process the configuration files during the configuration stage, shortly before it runs the package's postinst script,

For each file it checks to see whether the version of the file included in the package is the same as the one that was included in the last version of the package (the one that is being upgraded from); it also compares the version currently installed on the system with the one shipped with the last version.

If neither the user nor the package maintainer has changed the file, it is left alone. If one or the other has changed their version, then the changed version is preferred - i.e., if the user edits their file, but the package maintainer doesn't ship a different version, the user's changes will stay, silently, but if the maintainer ships a new version and the user hasn't edited it the new version will be installed (with an informative message). If both have changed their version the user is prompted about the problem and must resolve the differences themselves.

The comparisons are done by calculating the MD5 message digests of the files, and storing the MD5 of the file as it was included in the most recent version of the package.

When a package is installed for the first time dpkg will install the file that comes with it, unless that would mean overwriting a file already on the file system.

However, note that dpkg will not replace a conffile that was removed by the user (or by a script). This is necessary because with some programs a missing file produces an effect hard or impossible to achieve in another way, so that a missing file needs to be kept that way if the user did it.

Note that a package should not modify a dpkg-handled conffile in its maintainer scripts. Doing this will lead to dpkg giving the user confusing and possibly dangerous options for conffile update when the package is upgraded.

 Fully-featured maintainer script configuration handling

For files which contain site-specific information such as the hostname and networking details and so forth, it is better to create the file in the package's postinst script.

This will typically involve examining the state of the rest of the system to determine values and other information, and may involve prompting the user for some information which can't be obtained some other way.

When using this method there are a couple of important issues which should be considered:

If you discover a bug in the program which generates the configuration file, or if the format of the file changes from one version to the next, you will have to arrange for the postinst script to do something sensible - usually this will mean editing the installed configuration file to remove the problem or change the syntax. You will have to do this very carefully, since the user may have changed the file, perhaps to fix the very problem that your script is trying to deal with - you will have to detect these situations and deal with them correctly.

If you do go down this route it's probably a good idea to make the program that generates the configuration file(s) a separate program in /usr/sbin, by convention called packageconfig and then run that if appropriate from the post-installation script. The packageconfig program should not unquestioningly overwrite an existing configuration - if its mode of operation is geared towards setting up a package for the first time (rather than any arbitrary reconfiguration later) you should have it check whether the configuration already exists, and require a --force flag to overwrite it.

 Alternative versions of an interface - update-alternatives (from old Packaging Manual)

When several packages all provide different versions of the same program or file it is useful to have the system select a default, but to allow the system administrator to change it and have their decisions respected.

For example, there are several versions of the vi editor, and there is no reason to prevent all of them from being installed at once, each under their own name (nvi, vim or whatever). Nevertheless it is desirable to have the name vi refer to something, at least by default.

If all the packages involved cooperate, this can be done with update-alternatives.

Each package provides its own version under its own name, and calls update-alternatives in its postinst to register its version (and again in its prerm to deregister it).

See the man page for details.

If update-alternatives does not seem appropriate you may wish to consider using diversions instead.

 Diversions - overriding a package's version of a file (from old Packaging Manual)

It is possible to have dpkg not overwrite a file when it reinstalls the package it belongs to, and to have it put the file from the package somewhere else instead.

This can be used locally to override a package's version of a file, or by one package to override another's version (or provide a wrapper for it).

Before deciding to use a diversion, read to see if you really want a diversion rather than several alternative versions of a program.

There is a diversion list, which is read by dpkg, and updated by a special program dpkg-divert. Please see for full details of its operation.

When a package wishes to divert a file from another, it should call dpkg-divert in its preinst to add the diversion and rename the existing file. For example, supposing that a smailwrapper package wishes to install a wrapper around /usr/sbin/smail: dpkg-divert --package smailwrapper --add --rename \ --divert /usr/sbin/smail.real /usr/sbin/smail The --package smailwrapper ensures that smailwrapper's copy of /usr/sbin/smail can bypass the diversion and get installed as the true version. It's safe to add the diversion unconditionally on upgrades since it will be left unchanged if it already exists, but dpkg-divert will display a message. To suppress that message, make the command conditional on the version from which the package is being upgraded: if [ upgrade != "$1" ] || dpkg --compare-versions "$2" lt 1.0-2; then dpkg-divert --package smailwrapper --add --rename \ --divert /usr/sbin/smail.real /usr/sbin/smail fi where 1.0-2 is the version at which the diversion was first added to the package. Running the command during abort-upgrade is pointless but harmless.

The postrm has to do the reverse: if [ remove = "$1" -o abort-install = "$1" -o disappear = "$1" ]; then dpkg-divert --package smailwrapper --remove --rename \ --divert /usr/sbin/smail.real /usr/sbin/smail fi If the diversion was added at a particular version, the postrm should also handle the failure case of upgrading from an older version (unless the older version is so old that direct upgrades are no longer supported): if [ abort-upgrade = "$1" ] && dpkg --compare-versions "$2" lt 1.0-2; then dpkg-divert --package smailwrapper --remove --rename \ --divert /usr/sbin/smail.real /usr/sbin/smail fi where 1.02-2 is the version at which the diversion was first added to the package. The postrm should not remove the diversion on upgrades both because there's no reason to remove the diversion only to immediately re-add it and since the postrm of the old package is run after unpacking so the removal of the diversion will fail.

Do not attempt to divert a file which is vitally important for the system's operation - when using dpkg-divert there is a time, after it has been diverted but before dpkg has installed the new version, when the file does not exist.

 ubuntu-policy/fhs-2.3-source.tar.gz0000644000175000017500000010633611054263224017654 0ustar cjwatsoncjwatson @\[w63ꇺ=ǖlIzQINg"Y$X 𢛣4N۳^3$ƾY*Odwpxpp{{w<8~p?p8L,UV;\5> ʢTV ̰{2(uGASqM˩z6u/Nu>IybijCg"$rHM,KYF_ch'&nv}zIPEGO"m:{ tR *w`ybS&%GnW/K;޿LLAlƔ"(*-hLeؑy,2"U9D8H"lDpl,MNd2a36P[0U b9P3>'*XpP f5ImE3P\ {\2S5 Pag E&փ!$؀pSb?KE("M3WU `>m VEANSXbXY6)pP Gl^i5/S:# (R!}7+LI3ܓq4R*'Mܨ.Ww] @Lw͍N&%T^M ; @ MKOsc<(eƟIu"<`PP`eZ y)/.[+K:8JY3afA* )WcL 'HP] UZf:o`;p_FPk֚5 jZ+5_lp/*hwHVM]Gj)AC7!j:1 5g.(*`.$,ӤH|’ڪUSh4D9=ɽ^E@yEM`{ De. $9Bʆ2mIzPl*Jح Qa5UCŤLsAuFL]bjfe2'ƀa{V%MI&q;dxX=)[ lv,GNtF0`CҾߑTߚZ6x$Y=K6!N?LWRC-R"o GXty+i,RfS#B]Fq a~ =ϫt6?JRާT+NvJdd(y" CäʊÃk@G$p"aDdr]@rE/yVAd3O:W=Gxh'f3&5y?qNC{8R%EރijmSx`tPgwgTPݝyx`nxF$n4ٱ-2&VK-VdCڱx,pNFbE'3 @a`5$Yx"g^24zE|52*fė2~cjڞ2N%7éO/U gu5 Bh2] (A4Q# fs&k'=JLo KNV8uS!EekH61SõHF9{ZN֑& @TA'u*M[/eP}II!BN2t̻|!{)}CCVxN'3q:R]LMm?E3Ym SsDV:)$T_]=0ҙSH)K! 4_~CXyFyW=qj{]3NC u#|XY[@~(?E ߈Ʊ4g~Uf{mNF& Q#;\*H5uBA?Du·<_?G_'~*F\o _ 3qfa}1eH8]Z3oQ ^%?br4I&>tFۅ V@V 7y 9$H{;>ɀyho8xwډtDs'd0WҞPGdIe6L'XlP&uhT -Eʘ_i{q;oČ:sz6tԭ+-dQ~_e6ijVsz07KU#/UG?ip뺋ZZ-tw{~ċΏKVQY*4/v"5dU3Fvk:6Q|m@9fOIlnEڪ-WJ[vu_en4m1)PxHpu m F/ެd` q^,ٞ`X:EB{oSRjCA>Ctx' ^Eۖ/I65oVf-EMӓ!N45nqsc?V_kն·S /7իs7}Rf6=ݹ&&m3J t"c uo}ԥ6PkB.Pd:-ޫy<孩;Fo4YFG1}'';|adi(L0*7i#rR[59gwF L >N#5%N-up.{^fxiΪ4{GtgVP9yCga 8꽤.=ǡ"a$ȴ C5 :/SO{#-r\vNY.jV2PS7V XE Tɓ%i|P-t?]-7ioYgtdyݩS]ufyLZH^63n$)8 a/ 茫?$7iXC>2%\̬ϻKmXʀVͷtޕӺiL}6[snLE-'Օ%`ń$LI1?JׄA_F$ܱ-oM̅ UNM(朹%]s"/NJeiJ|Kc΂θSU+vT%5 Ek/xV`[}͵@`,r$u_9NSUƝ^}7罁T 1sQ"bǼ" +=뺾I2$1dZ.WEO3zn 73",JZ6S.~^CsRaoF! Ab6 R GeVM>\tJw}u*{a*P^>Evųni #wwQ)m?pp>۶ӟuNjCI 7 hk{[W7Bv!7﮶MQ!qKD]"'zU 2 P2ߞΈ E'UiV a=o %Ez d%k<,*:5P^%cag_dzLkQϳ,Tߙ._"Ӈ9&Xm cNnV&bu gZz&DLԼ2ASI4Đho.G7S'BDr:AD™_hgZ(TѠOr6OPXLbD4}*׋ (we9ؽʞq$?(9`u*Ă}2f[^4cgtpE&Ǽ(!tŘahA GFȽC mo8=tFI4Oo>v¸=}||vztAcE^|J1SFWWOG|$-yE~Xdg't?*a׃.}04n' `E60E2y;Xcظ_9x( ȬCt1)H}OKCKZ8"/lW$iGiA 5epVoMDm>E9`sqTN=T! 쪷GH,E: i%zW`LU6'(4,v3"-~c Bgsyrk!M7gBtKXx\ذ]/A{ݩ+&v\чʻ7)7~mtx/Bv{>m/>AaW *Ӆp]Sy"^AqF>}CxG`mpϪ[tܖl[$m={۷p:4wT kx}p9 VF/z&\s+D{^iEЂB.E16y%s8]Zgb!^J1ZRK1&c!(ѷAc苁D?d5a<{ƲX <)l5NV6X<m38x*zp1bPͫļv)ռ/ ~EZڷua%/A.qɦ(Y^C_ޘJ_,,TXoLu5 ^: p+<&zȵ'GX4>$2 kC:!{F[JxI 3z墒)$=@_R.١]6\H QɩJJl TX:J3/+II>~ > kM^QM»;w׭; 0 h䲏-glΛTtsyTx^ᆶ'|㩰K>dWHl8o ㊷d} )Q6$㛢Y:EG2 p*o:P 3q-J`DrId en$Ol0G簒_%bCE3IjG XǷ)*fތTLk p]MĆ_b3}%aj1I֌_3xiܺr_gҀ;~Mչ3Fb;֧kݠH F2W?O.*,:y70u3\A c_5[;BR`bGFK`Z$8?}\DGxe1: {.u?~s Bc\Ooaq-L<<4\\LHDU{";1eXZ*۞Su NН= xޠ$]ER:hpb#oی@f9gۂ[VNνL '8_Bt/O_tw'cwl 6v#e}+d\mLWuH=h lT"c_*1ah+x'݁KEMI קY&x턗˓={'.}&zc^m% Zժ*@owqA9".l|^G~Sbfe 5VFГgJX9 _m{byyWS?Mny}|~/'A`+< s] 5Es'$ WhA N1 "񉀀W))ւYhYMܤ7DIVԝ&wʺ@vI4\Β_=@Q$z8+:`]4wA@9,IN1ig}i%Ǩ>vH(a)_S \3#*I1žAPYfL1Niwj(2ց_7XEx䢵+dz FX&;)Z :z[:D-bS#SkimY;b"ӕ"@_3mV>3O5G ƹDw15thc4yFyJI2::֪W=!R9PxzTeI9lqAau0@L )?J?˜#0F^v Mnf%A달TN/ah0H~Q0;BY|]tFRWBq %HDWe9ňҕ JBs u:ds=-}W b te'1`E&=+4] \e  Ṋ^ W%S 2R'={Nً%EAYąj` ƽ7<3ՒG TxsY@'W aY.r@wD잟jTa``tNgp*{np~b|pn c70ޒj$uZ<~MɧTx|ia0%dKjƐ 8ʒ;xf&9M z'@1[k&b!FM:|\m;|Dh9=YLp(4RJ)5PSF疁>'at9'NͨMc&6/IVzG.\<*S  LAz;T ^,sb5l3T!t- xQdm^Ӓ[0"/wgrIsx\b`},b-&R [iR#Tزͫ6޿aJ4055g:naZcgzKfk^]s~nHSb$ؒRQ7ī{#CAμ!mxLg7BChvm?M9vM|sw|GKwH~WCۣSwA毡wm^U@ P;vZ,7wrw;icc޹A{/n`I9fNzZhSwTHDsE}pb܀9uwo aH8A*9lyk)], 6 y˴ N4' ɳLvv6) !a1z΀Wn# kusd( 'AR{Ⱈn{o]vd_;qiY9s[RG[eۻo ɍtvqӾ}aM_ }tє=`SZSu{=\N@UEF&?Uh؟,Nm 2.4_3υ`j#yGofb] yx̹t,]ާ vF|t,r QR+̨٪SBJCVOfn[\fFRWY"A2YC6:D];1ϷLB)(zDaL2Ch@ht>$SF'\YUBjmՑr^P~k'c/Gc1Om  /MܡcU{I+2۶ r>{~eӷqtv@QMp}ZnS*F8t:q\-`-/Ŷ2ALzL W>D$^D8_+Еljr*nocv  Z3]Ch6`d*gRJ=޼*VW:xl*s[ݷhzcw,8{$|M4CHaGa'wdg[bS)U U>eN [$< $90 u&l #&!I|Jh&?.v $qbj¹j9o5CjB'm3Zfqm,=dB- Z:Q݋9;Й:J8Q2W/? O M =1Z\kYɪk[T\im|=Z^ڭ#6yּud]-~'R+?S'=\؉L`B {*۪s^qߏ,dI*a*JG^,:ryOUruZ5S$oPs5j16'2 +3HXg4 (X .b*U:b(HY5iDx& J. \pӻ7`Hk%Y!g MJlYFC"6)_9TZi}4k9.|5nXSa*/jT6N礠4725tT5MI&ƐU5] <ڈ)¶ɥxX6^@Ȃ{V%+llE^YWGPExǑ[[X/ o1-T{>~~:$({{0ǣ>K8C8QG1p[P=BI0 ,=>2a2`3Am}}Se}t =F,]Wi8J6ħK 3܂zO]b^'EUjj7BՌ;-쪱 ?aOY{~*Z_Ob)8^\(Eb'i≑*=`;6K1ڄJ rQ#`uYmWQwL w oO Cjv9aYDD*/-+?yԆAcwM~ ᇫyAzvK߁ rt1CCR$=6e[`Sr [+~Xh}7uSV kR°z1oU_݃X\pI㒵 S,DFJ`%SB 66)*jBLxW6)0F0Ʀ k:9w{^cprRa/B|x/Y,gqpvj,Gej.=4R΃y]sI} !ܽhdBdG=1DznqƂ;xk&G'_6Ebn )js85GX.hkuT!ɤq=}xO}xӋ=tSwtPE>^271mSU;8¶JG!yb=1X_UKP3`750˩d8@eH鋕q8I)WK{o'{O$GrvS7V"9S v5Wчaԡn#րo3a)v,g/s(S(LR8c+ekU$?Me;f􊻝0c-Q<|$q $]%Np[}?+e.y"^5hOʾ}T1k)Z>;X!$(zzPG˥sX< +V=֤ԉY*غX 3Gbq\\-+ .ɇ-v d^E^Z}Q nR*svJNܱռJJ@;J~ƗAN;4,cO5\}:e={>!Mm}Z}Ԧ{Kׁ3]Bܾ_t9b4hcQD.de ^p 637Z7> ^tQM3`|Εu@D>ЌܷF'R.s:lmP[ WXt u˻ٛQ!ݠZf,E,iUy\E`tӞAJ-;Ie M$fAsWH vYD67_> :.Cb]HWSux\}+>'mDž2Ti&q;3̤t ,jГ`X%PID=;q691I1`3ެ0j2ם~;y~OXոU5fٳY3~%2@\];w dDh>mGwEZa.V&;W&5w3)T,b sFwI iS DLB` yՖ˄ iZieTԡkR)seq/=|h dpqzm|rRuDC=! 45*&|V=Ч<Dkս&V!ծ`eU</?Eb[+.{Z`s u0E ®߫ΫbZ46ŔB[e\LJTA^y*){o ENLPs*^|c> f3R+]}b|<γsQ+ɭqVrZBΆ=e~P{ R=epM.AT tȘXK=ui4 J(&C3ͧN6%&L8Ŏh?إLC,@.vuI6[hEolᏦզUɕ7iP7N[6l` 󻞀zD4Ώ->L<p]x9z0)p;%쁑1 ra:@. DΡL_aE]Oc1 vY;=)1P" Z2.*}kfgpm2_m$j 0:҈EUF? TH 7gr=Dk>Jqv&R/NсTM‰ gg/fpQtOVE!I4ZSڐ7W >f\g y"'R2m}ɷ[b?>9Y;C{PogQf5t$: <_Ļ-LuV+,!6L\z;ȹg녇j,1Z=VR6H_4 (me 8&^8l4rD75kIvEIe\(A:J/S*$.:TWYZ<_cDs$yeoMA;{G/A{8gKQ.R,/v#PU9h"_,Z <*06mڮM@I+xyOIyQc-ċl@T Jo@[jAʗ)hVH:w`FAl ӎ@C>SѨABRnAli NJXaLmȊ.~@9!)h }~jxlL'1pXpy4 ]UV6*ҋ&3Z~H@i3ЎxV,a;VKtyN,VX~4Kȃ{E|ܙ)r8SB>rHO-=ꍷqnւ[``[3 O1V~D7ĦW"zc~3N1&!4;[g$ ))՘a :"[%l"n!ʋ:Vg$ o #=,^v<%%נˏrCh-:2M(ЖV^2'R@:MV ܒ ܌[}s'zLſSYr{ S(k)+% :urBV_Ź?{H@|6d nﰌ&l׾a>ݴ?8HVw2h'g{As@_^:Qb,PW\U~plЋcXE%TMЇVKDv;m6jB)3 D"MLgK 1c5^j9{M 6bRX&U9s I!q#Ykv;8z첦AX} OcghUmNGAvM*Sj I/0"F7f͏G/ <1eiu1*v,J_~!Ol8xpe<&/60 Z'_Z4v:䩦BkoBr¬mΡ@HApq>ϧp+ 2ǥ*$ e+B;Y"+ K/yS. ;s6*'{\gBy廻;.5-=94)߹4&*7k/Lw+I$ASr,|tTfr=F UwHS<:7F>0ͿJ^XW?wXxNp!٥+]|a1ߡ04k*w0Y#^\T@>:4O̟ ߜ_)^k=r4D7y5SSi7 zr9ϒط)H[Kn=|R硭lub[ d' i蠑f&$[c'SQѡePr|T~G[JRj(ZTcTeOkO;u_W[2/_|iN=:FW/? hQF0qA%}Ȣy2tTF Ug Z<+wm%\dntxp7@;K$1*8w ,ebq08@$af*YQn<M]eb#26>KPb%>g@<}G<{~;==;=ѳg==} ?yWѣ)L(jNYuNv QX{BG "]]@g1zώa'$՟DFx;2f#V-rV㋒$qbeO\Xob uɊOe@5avBΰvL^?XUS)_b]{z]jP;u;vKm: S ³DwldT2S {_%_+E_l/3/1֑kY7aqtv#(UM&<0 ~eѩ3ݡ00~JV][֋^BCϋq\ξEofU!R2:%1˄.t+X"P5Snէ m|7ͦ8UaRAR.*Ql7r7̪Jd&4OkŪMp t⛲^ry~)|äAܢs*Ole/:L#˝2:$~OhO5WAIl܄&584 gQ~qp;5\[ԩ"ӯ{ xAbVT_\bK1<cpnXA*ʉP͡}$a;DuR4%~(yr9g=/hSQmu?fF.Oms_h7uaJ$6~Q曲*|"p2fߞ[r'eDSQ1lSUMA'5t Wvg8 \zxB-# ?X,$JjfVE5 )IL/daR֙~3D!ʍ뜉ƯI\gxL-0X/?mi]=Eg<\ HH~"sFX3]Š#JP4^d,s38 x.wI5):HDz|.VysyXs`9?_!F*3MrȻ  &jYǚ75Vtg4-vɰA Rd8l}%g*%Y:j:R1뿡/o;hieDK;<11AN@c;TS})bfv|tdLcF Mq3ӰH균i1! Աs^FpeQM TCL4 +vC,)ck'ԝܾ mƷu>YSiiuo L_ak-slqڠLj 2tQ^Z}+gvu&(munSUОn,T_vm-4aiBPs/Wӊ.'tj-Z <^h[oC>OƺQn$0=Iq jnWډ 5"׀whX ucŢ ȴ-S#eh: .iJW0Cɽ8c 4Y˳Ycza2yQDfҀEMv[D/r*azǫΗђWU)9aQ񌸣j͑;2 FfqFhd%0o]ۙoXY2RH*Vq'4ciw0eIi<-FzA=t(oM]ψnUI uB PsA;&( 54RPs)`!F]6HXL|ퟗ(iV[ނ֔Y|&sc.[C{YoFdvPX1Z.U6풳4o2h?=.ujKT e {%3bnJ?T8ݮl+\\*נ NF́Xy_>2/9$&+ɯSJ=:2%Y ցpT۾]V&rM p鶥Fm#DJf``P5=ңҍ b_2&ZAU_':`)] $; 5ڃҩD).5$yw]k,esn+rvܹh\j'e2ITgt"(d'>ǺSq 9KrFB} |ĉqzD Txe+>{d*A!&Qvfarc*OKC G3RÞmI dӺ'>zÿէnߔW)dM#BŘ\y{at5^ nYߐmڞ =a] Ժ6ޏ?Gp)7$dOKCټǜA)B0*L)yd6@dhtÛ׼Nd1&⥑t{"c"L9SaHWlP|3!zGFߧWD7=zLڄlZ_%*(&g{ҹGJV3lIX锐+t5X%#=ǛT=xfOh; u9"u`t~q$}9Fb߷XsZUH ]rȺ31TL޸bw1 3|oNW#LLJ[jOŮS`&1^=ZtNgTj*TTqζo{^8U[̦7 :60e%t]h֩ sB+C6tX/n7A2![])zSq)M4,,~}o@Ę֏Ȁ"MhX2JJ\T⎶Q0It[8:9`ⰮƁ.)-fV C,Y3o۔S_8tސ 'KgXIn,|8su·t^Laп,h-k1hHqPP#謴e8kNQ Rm;r^}'zZ`BnF={EVEQsL4~in`m: To4Φ!6&_$iMj;"۔^4 7C" É\^$ U)!X_=)u;2>?ّB7,-sjdxgl:]mw\tǓ4tbe$d_-dZ9 0N9Ђ N ǡu廉bph,#Vz*b#(n Q h;)Zߵ֙7MP>.ghGQ;XZե20eRsX3&^<( :n=%OK]jFT&{<\4GD(;*WR̀.\6-#UQ~8BuJ۴3D+'-n@ߤe+~C Z?3rs@4Gr V}c2_>3..gD1/ ąi|,7.áCrJS'@.W=<:%,)W=9;A5N>Zy3]K.NWf29`_[idqaʩ헖|r&!*x<.Ъ+D}ݨPk:Ǵ%ȳ\щ9Kq8_8aZ1ebwRY[9]1+DyQ-~L. (Xe+ >*$+OE ;d6{s#8ݫ`9ƙ˘..o8bЏ s ]̔bp<貙 Z` n(Z&80Kʣ[4-3 ΃ ^`p &Ѣ#}qxSd1!R)PzoD~hri؄ɟ__\^2sǻz%9I'L%ݫ"g)f%. $ʂP1a0d$ KKqg5hffϖT*a,d]s^ߕgG4':%b)|LhSQ._ +k`n^Rh~ ƫ2tiWg_=nW*2D Լ'{J鐝:c|}Ѝ C f#|x3c ʰq.wk4TzrIK"i͐\A'eY+_/Cn 3I7ZЫիPa~_3&i&+ DJ +l)*+FԃD~o/moL;TnjƘ:EJ",{XT JdT66msٕlZL)X+rqu\$" :AwhjŖڊz#c+T$ut[c u]E]w=?dHzD K1^phg+jӵCm9LtIHsbHlwlv=G,@ꔭ'"XH<}HE|+]w69Hi9%.U]sJ\M7T$9tz` C-Kt[Ԏ_/5 &1ui7aȵ3|pkQȁ%]yɎ>;M@`p}rr[\:|!(^{G\Rt#S.}X֝9I8l$jmxƅ$2OA5k(7QeFZx !l90AnH N:B g9>n/GO#,h!vJX-;yrT] © p6i{F.UVKͷIk_5]WP;rțu gy1^ \3V'7[ִ5eJ"Di2QGly1vbRP+EIO<[$v8^ȥ Q,IZjKw+ޅgKP9xRj3^.ĥ.SS%ڛU}}Y6n3gUYl>TӔSuH)7@Be~ibI ")H ] (2B~lwo_>pe+_z4يoOS?=܏{msE5.@5 5}}׶Yoe&e} v8!+qBdG:IZipAt56!7+t*7\b6̒'՗-~nblɣGO?ѣG'ϞçU]iއ/Yk6qܵ ٰIㄇLt*ʰ'gf*7z^x|M!wK|trpі~%SҒmj.GaKpj<39 d}0y\QMڟ Gۙgrˬ}Ăqa"M"kS1KiQ BD6"%t0~Rm>|n)rs8߾@, }DI[q::l?JJӏX`}Wtȩ)r!A6Q[ݹc@y xY U pVCIFI# o#MR5ʕ0<%?z5Ep06he{7:ME\#FFgFtKw}MTV\Wg~5OhU/]F޽~pUW^ M3լu'`vnYo6}m`S&!speB8 Ơ~>Zt S0 ʬȨ>[B%ճI/C > `Q7)'EujTUH\Sf&( u~ 6A E$ =iKW~0*(wzȓڝ>=vbb0?a)H7K͙D,UG ƫr/f-&h^C^z ܺ}ˤTM_3Opt~'S[ ZynV&hn `yg!wzN3c} MaDi`bn-#?pfdpOh\.ɷTފ7qOoK76w/ ֑^{S0NӃ6/mAi ?l:9G|y?ެeBW@*,dŠiʲCνf,WFRk򀋮m!;“-M/t@TAl\TX.a"ʵpG ź8ߑff5ozsI6)LsppTyrDř0ryHi4ahWK>IDwccImUnȥ#ٿCkC0FI,*xW6ӧbSxAEJœ ZԢ ?|nS&v 24ytj'PӆSAӼ>ɠz NVa$) K>ri,r4S:h6)YOL.o zCZ6VOVȌl庐 bL$ze -(::iO <^mƴvll_XxaRJ7а.:L^-Nͣ' `dxXcUaf)DRݠ{}XP}K&b}>WSF;͑Dd4C뱿seaX&± itIɌpzWG165={`kk "\!_.ݍ}% Sr}DP-|,R}tpTYkYJ=cAL8i,ACDYE2ull% L6qΓӼ (hSՏ[[,0%)o*" qxi*AYATTxCBr/T+ vq֎/{RN׍UL>|e)*7\HG@u" t(RRKɼLG%zBM3R 8i5vJQ|A׋  ksӨ@Z_D+h,Ϫ"'ǣR(L D2qE\%)uo@bv%nq s$dC uvu˅/1y95Wo Q ӡp`|2*Cԛ)-fn6YK/>,mD- mU{5M8 |@Z.t#]ڍr%h%֜ĤO2rF,|Ihڄe WiqGWD/*iFNBVn֋>( dݍ8'H!b&Ƌ=G ktU`I l`+^ӊW0 "y`, ӮG$yxAX*K>O*& ՐIPE"g LXA98巉%M[c]|'P#A|#y`\W.'4UT#Xt e2TՕҶt)9q@#?4grJ,NM^-!)Am_쎲+f!$k8?Bvg J7 45MԌV*9{7řS" N w*~642yTi$Ȍ&Ee$*{kbغML>_,6N+ᴳdt9*9 rsRD5Q._FW.A4KscZh8[t}U^7o}=]bFf6xMfݴ=oM;2ɀw->*}P",yEZb >9o" #.6dhE*6FU<,0836΅*ͩ!(A E )+E=y:Vte>d&u*k5BA~a$)$! 0ꄶ@x ΫU!ǤȨZv&=@U`]^G>У`ݗ({ FҴ37ʏ/~y!~L3~/OKkTP܌ *EYtu*YZE5Ơ!X 4lGT7I=Vl{KP36l)9 Q(px#=5)rF9-=~aMךl锞Sje)+B1H--8csE-i}&-0̣ȥ 7G%ysUX1nr`q16uu"7tFpf/g~zom8sr )#t)xyLVVz30IAh'1ʍ ^bjO&7Nq'~r #H~Œ̴iNA3%znR4[|RXAWפ&,WIYslr}M`C ̖u)~D }tzуoDŽ)טm$㶵DT@25.*?HbVgi3-n!0kJaJD ɣRlp-*S6'$Ljt`J>4Q)_(PI @W%0r$g-E]XY"FM6wdTq:GgEˍVv=9[eV'a*ZXù.VOȸH:|zpom6&Vo ɩָweg^O v JU626֜8"xpIdb/n8 EhJd\ 7usXN%bv⩘Z2p 6㌱ezQv]Z̤x`ë `h]DD``$[L˿)Vsb%olkF/Rf ;*,Yō)7֑@\ieoLc6`nH'^qʖXǽ`Zbj l; Ľ) "ah@J:waoJ| 답:cNEyfQtl] Zu g&m :}v(7tH{Gz宽#9N> ,?SoP/gMuĝX4? *g#,eYAV5p9t&üyDyz'T.R7W_^dVR%hEο@c^YGᇫKHcГIYOB6,>U1bxQ/CO4HmsovЃ;ئ6YpE`ꟊEt4qGPK_<[zO?۰?={\ɳӳGTɗ[\c3 N_ϔ:cbl|UD~C}D>G7i_1wͿtLX{xSx!$1|'D ~~+Ex?c (F) F:zE" Fߔ9K2ҺѫE3(zEɋwk.栦NB!mrd80 F$*J&DL%d?|Ox;l82ވ`|rx@_pn"eGifi9|1)Y$3?:K't̀(wo_dlv{ܿGJjyK<8Q lW'08b@ts3MtZq~= $`~fTՖrVvcϞ=2M&*FelyX8UtNCo VE\tnϗ/?_~|ϗ/?_~| )ubuntu-policy/.gitignore0000644000175000017500000000041011175362266016133 0ustar cjwatsoncjwatson/body.tmp /debconf_spec/debconf_specification.html /debconf_spec/debconf_specification.txt.gz /head.tmp /menu-policy.html/ /mime-policy.html/ /perl-policy.html/ /policy.html/ /stamp-build /version.ent *.html.tar.gz *.pdf *.pdf.gz *.ps *.ps.gz *.tpt *.txt *.txt.gz ubuntu-policy/README.shlibdeps0000644000175000017500000001144511054263224016777 0ustar cjwatsoncjwatsonIn woody dpkg will use a different method to determine on which libraries a package should depend. Until now dpkg-shlibdeps has used the output of ldd to determine which libraries are needed. This will be changed to using objdump. This however changes will need a couple of changes in the way that packages are build. Let me first explain the differences between ldd and objdump. A binary itself is linked against 0 or more dynamic libraries, depending on how it is linked. Some of those libraries may need other libraries to do their work, so the linker will need to load those as well when the binary is executed. For example, to run xcdrgtk needs the following libraries according to ldd: libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x40019000) libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x4013d000) libImlib.so.1 => /usr/lib/libImlib.so.1 (0x40170000) libgdk_imlib.so.1 => /usr/lib/libgdk_imlib.so.1 (0x401ab000) libc.so.6 => /lib/libc.so.6 (0x401d9000) libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x402b5000) libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x402b8000) libdl.so.2 => /lib/libdl.so.2 (0x402da000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x402de000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x402e6000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x402f3000) libm.so.6 => /lib/libm.so.6 (0x40392000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x403af000) libtiff.so.3 => /usr/lib/libtiff.so.3 (0x403cf000) libungif.so.3 => /usr/lib/libungif.so.3 (0x40411000) libpng.so.2 => /usr/lib/libpng.so.2 (0x4041a000) libz.so.1 => /usr/lib/libz.so.1 (0x40442000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) Now if we leek a bit closed we see that xcdrgtk actually only links to a couple of those libraries directly. The actual depencies are a tree which looks something like this: (anyone interested in writing a tool to make such a graph?) xcdrgtk +- libc +- gtk +- gdk | +- libXi | +- libXext | \- libX11 +- Imlib | +- libjpeg | +- libtiff | | +- libjpeg | | +- libm | | \- libz | +- libungif | | \- libX11 | +- libpng | | +- libz | | \- libm | +- libz | \- libm \- gdk_imlib +- libgmodule-1.2 | \- libdl +- libglib-1.2 \- libdl \- ld-linux (I haven't listed libc in here, but all libraries are also linked to libc). What ldd does is give us a complete list of every library that is needed to run the binary (in other words, if flattens this tree). objdump however can tell us exactly what library something is linked with. For the same xcdrgtk binary it will tell us: NEEDED libgtk-1.2.so.0 NEEDED libgdk-1.2.so.0 NEEDED libImlib.so.1 NEEDED libgdk_imlib.so.1 NEEDED libc.so.6 All the other libraries are automatically pulled in by the dynamic loader. And now for the connection to package management: a package only needs to depend on the libraries it is directly linked to, since the dependencies for those libraries should automatically pull in the other libraries. This change does mean a change in the way packages are build though: currently dpkg-shlibdeps is only run on binaries. But since we will now depend on the libraries to depend on the libraries they need the packages containing those libraries will need to run dpkg-shlibdeps on the libraries. That may sound a bit strange, so here is an example: Generally a package does this in debian/rules: dpkg-shlibdeps debian/tmp/usr/bin/* This will need to be changes to: dpkg-shlibdeps debian/tmp/usr/bin/* debian/tmp/usr/lib/lib*.so.* For lib* packages which don't generally contain libraries and didn't run dpkg-shlibdeps a dpkg-shlibdeps call will need to be added as well. This gives us a lot more flexibility in the way libraries are packaged. A good example where this would help us is the current mess with multiple version of the mesa library. With the ldd-based system every package that uses mesa need to add a dependency on svgalib|svgalib-dummy in order to handle the glide mesa variant. With an objdump-based system this isn't necessary anymore and would have saved everyone a lot of work. Another example: we could update libimlib with a new version that supports a new graphics format called dgf. If we use the old ldd method every package that uses libimlib would need to be recompiled so it would also depend on libdgf or it wouldn't run due to missing symbols. However with the new system packages using libimlib can depend on libimlib itself having the dependency on libgdh and wouldn't need to be updated. ubuntu-policy/virtual-package-names-list.txt0000644000175000017500000002656011054263224022041 0ustar cjwatsoncjwatson AUTHORITATIVE LIST OF VIRTUAL PACKAGE NAMES December 2007 Below is an authoritative list of virtual package names currently in-use or proposed and not objected to. Please check the list below for things relevant to your packages. New packages MUST use virtual package names where appropriate (this includes making new ones - read on). Packages MUST NOT use virtual package names (except privately, amongst a cooperating group of packages) unless they have been agreed upon and appear in this list. The latest version of this file can be found in the debian-policy, or at http://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt (or any other Debian web mirror). The procedure for updating the list is as follows: 1. Post to debian-devel saying what names you intend to use or what other changes you wish to make, and file a wish list bug against the package debian-policy. 2. Wait a few days for comment (some of the comments may be on the debian-policy list, if you are not subscribed, ask for mail to be CC'd to you). 3. Mail the maintainer of the virtual package name list (which is the Debian Policy list ) notifying them of the consensus reached (or your suggestions if noone objected). Please update the bug report at the same time (retitling the bug to [ACCEPTED] .... Please include a proposed brief description of the new virtual name(s) for the list. The list maintainer will then post the new list to debian-devel and upload it to the FTP site. 4. Go and use the new or changed names. Manoj (based on earlier versions by Warwick and Ian Jackson and Chris Schwarz) Now, the list: Format: [Those marked with a (*) are handled using the alternatives mechanism; others may do so as well.] Miscellaneous ------------- awk a suitable /usr/bin/{awk,nawk} (*) c-shell a suitable /bin/csh (*) dotfile-module a module for the Dotfile Generator emacsen the GNU emacs or a compatible editor lzh-archiver an LZH archiver package tclsh a /usr/bin/tclsh (*) wish a /usr/bin/wish (*) Development ----------- c-compiler a C compiler debconf-2.0 the debconf protocol fortran77-compiler a Fortran77 compiler kernel-headers kernel header files (, ) kernel-image kernel image (vmlinuz, System.map, modules) kernel-source kernel source code libc-dev header and object files of `libc' System ------ flexmem anything that can access flexible memory via the OBEX Protocol foomatic-data PPD printer description files linux-kernel-log-daemon a daemon to facilitate logging for the Linux kernel system-log-daemon a daemon that provides a logging facility for other applications time-daemon anything that serves as a time daemon ups-monitor anything that is capable of controlling an UPS Documentation ------------- dict-client clients for the Dictionary Server dict-server the Dictionary Server dictd-dictionary a dictionary for the dictd Dictionary Server info-browser something that can browse GNU Info files ispell-dictionary a dictionary for the ispell system myspell-dictionary a dictionary for the myspell system man-browser something that can read man pages stardict-dictionary a dictionary for stardict stardict application capable of reading stardict-dictdata stardict-dictdata dictionary data which can be read from stardict wordlist a /usr/share/dict/words (*) www-browser something that can browse HTML files Network ------- dhcp-client a DHCP client ftp-server a FTP server httpd a HTTP server httpd-cgi A CGI capable HTTP server ident-server an identd daemon inet-superserver an inetd server lambdamoo-core a lambdamoo-compatible database package lambdamoo-server anything running a moo using a lambdamoo-core radius-server a RADIUS server for acct/auth rsh-client an rsh client rsh-server an rsh server telnet-client a telnet client telnet-server a telnet server News and Mail ------------- imap-client a mail reader capable of accessing remote mail folders using the IMAP protocol (e.g. Pine) imap-server an IMAP mail server mail-reader a mail user agent (e.g. Pine, Elm, mailx, &c) mail-transport-agent a mail transport agent (e.g. Smail, Sendmail, &c) news-reader a news reader (e.g. trn, tin, &c) news-transport-system a local news system (e.g. INN, C News or B News) pgp a version of PGP (International or US) pop3-server a POP3 Server X Window System --------------- x-display-manager an X client which manages a collection of X servers x-session-manager a program which starts a desktop environment or launches a general X session x-terminal-emulator an X client which emulates a terminal with a terminfo description in the ncurses-base package x-window-manager an X client which provides window management services xserver an X server that (directly or indirectly) manages physical input and display hardware Fonts ----- ttf-japanese-gothic Gothic-style Japanese font ttf-japanese-mincho Mincho-style Japanese font Graphics and MultiMedia ----------------------- audio-mixer a utility to control the input and output levels of a sound card, with a tty interface x-audio-mixer a utility to control the input and output levels of a sound card, X Window System interface mp3-encoder an MP3 encoder package mp3-decoder an MP3 decoder package mpd-client a client that can control the Music Player Daemon pdf-preview a preprocessor that creates PDF output pdf-viewer anything that can display PDF files postscript-preview a preprocessor that creates Postscript output postscript-viewer anything that can display Postscript files Java and virtual machines ------------------------- java-compiler a java compiler, for Java version 1 java2-compiler a java compiler, for Java version 2 java-virtual-machine a JAVA virtual machine java1-runtime a Java runtime environment, Java version 1 java2-runtime a Java runtime environment, Java version 2 Scheme and interpreters ------------------------- scheme-r4rs Scheme interpreter with the R4RS environment scheme-r5rs Scheme interpreter with the R5RS environment scheme-ieee-11878-1900 Scheme interpreter with the IEEE-11878-1900 environment scheme-srfi-0 Scheme interpreter accepting the SRFI 0 language extension scheme-srfi-7 Scheme interpreter accepting the SRFI 7 language extension scheme-srfi-55 Scheme interpreter accepting the SRFI 55 language extension Old and obsolete virtual package names -------------------------------------- Note, that no other package then the ones listed here should use these virtual package names. [There are currently no such package names in use] Changelog --------- Ian Jackson: 22 Sep 1995 Initial revision. Andrew Howell: 26 Mar 1996 Added www-browser. Manoj Srivastava: 11 May 1996 Added kernel-image, added new location of this file Warwick Harvey: 19 May 1996 Took over maintenance of list, changed instructions for updating list 25 Jul 1996 Added awk as per Chris Fearnley's suggestion Added c-shell, which seemed to have dropped off at some stage 2 Aug 1996 Added pdf-{viewer,preview}, compress, emacs 5 Aug 1996 Added imap-{client,server} 8 Aug 1996 Added editor 20 Aug 1996 Added sgmls, removed metafont, dvilj, dvips 25 Nov 1996 Removed editor (should have done this a long time ago) Christian Schwarz: 29 Apr 1997 New maintainer of this list 5 May 1997 Added wordlist 29 May 1997 Added dotfile-module, ups-monitor, tcl-interpreter, tk-interpreter 21 Jun 1997 Removed obsolete virtual packages: xR6shlib, xlibraries, compress, emacs, sgmls, inews, gs_x, gs_svga, gs_both, xpmR6 Added new section about obsolete names 1 Sep 1997 Renamed `tcl/tk-interpreter' to `tclsh/wish' 21 Oct 1997 Added emacs, c-compiler, fortran77-compiler, lambdamoo-core, lambdamoo-server 29 Jan 1998 Added libc-dev, emacsen 14 Apr 1998 Removed obsolete virtual package `emacs' Manoj Srivastava: 23 Jun 1999 Added pop3-server 13 Jul 1999 Added ftp-server Julian Gilbey: 26 Oct 1999 Added ispell-dictionary Added man-browser Added ident-server Alphabeticised lists Manoj Srivastava: 11 Jul 2000 Added x-terminal-emulator Added x-window-manager Added xserver Added linux-kernel-log-daemon Added system-log-faemon 24 Aug 2000 Added mp3-encoder Added mp3-decoder Added time-daemon Added rsh-client Added telnet-client 16 Jan 2001 Added rsh server Added telnet-server Julian Gilbey: 13 Feb 2001 Removed libc.4.so Removed xcompat virtual package names Manoj Srivastava: 14 Mar 2002 Added java-compiler, java2-compiler Added java-virtual-machine Added java1-runtime and java2-runtime Added dict-client Added foomatic-data Added audio-mixer and x-audio-mixer 30 Aug 2002 Added debconf-2.0 Added dhcp-client Added aspell-dictionary Added radius-server 9 Sep 2002 Added dict-server 3 Aug 2003 Added myspell-dictionary Andreas Barth: 25 Apr 2004 Added stardict-dictionary Added inetd-superserver Manoj Srivastava: 25 Jun 2004 Added cron-daemon Manoj Srivastava: 4 Feb 2005 Added mpd-client Added flexmem Manoj Srivastava: 16 Jun 2005 Removed aspell-dictionary Manoj Srivastava: 18 Jun 2005 Added x-session-manager Added the section on Scheme and interpreters, which includes: scheme-r4rs scheme-r5rs scheme-ieee-11878-1900 scheme-srfi-0 scheme-srfi-7 scheme-srfi-55 Added x-display-manager Manoj Srivastava: 26 April 2006 Added httpd-cgi Manoj Srivastava: 02 October 2006 Added stardict Added stardict-dictdata Added lzh-archiver Russ Allbery: 8 Jul 2007 Added dictd-dictionary Rename inetd-superserver to inet-superserver 2 Dec 2007 Added ttf-japanese-gothic Added ttf-japanese-mincho ubuntu-policy/debconf_spec/0000755000175000017500000000000011175403354016554 5ustar cjwatsoncjwatsonubuntu-policy/debconf_spec/debconf_specification.xml0000644000175000017500000002554711054263224023607 0ustar cjwatsoncjwatson ]>
Configuration management Protocol version 2 Revision 7.0 Wichert Akkerman The Debian Project
wakkerma@debian.org
 Joey Hess The Debian Project
joeyh@debian.org
 1998 1999 2000 Wichert Akkerman and Joey Hess This text is copyright by the authors under the terms of the BSD license, sans advertising clause. Introduction Configuration management is quickly becoming a very important issue. Having programs which do cool stuff is great, but we need to store their configuration as well. We see more and more different configuration systems being introduced all the time, which is not very practical. This text introduces a general configuration management system which flexible enough to be used for all kinds of applications. Configuration Data The configuration space All configuration information is stored in what I call the configuration space. This is a database with a special design which resembles the method we look at configuration information. This is done by defining a hierarchy of information. Each package receives its own space in the hierarchy. Each package is free to use a flat space, or divide its space further into sub-hierarchies. If multiple packages share a common purpose they may use a shared toplevel hierarchy, preferably with the same name as a shared (virtual) package name (for example, both mutt and elm can use mail-reader, strn and nn could use news-reader). This shared tree can also be used as a default, ie a variable news-reader/nntpserver can be used by strn if strn/nntpserver does not exist. Each variable in the configuration space has some information associated with it. Most importantly, it has a value. It also may have a set of flags and a set of substitution data. Templates Each variable in the configuration space is associated with some meta-data. The minimum meta-data associated with a variable is: long and short description, type, and default value. The meta-data is essentially static; the protocol described below does not allow it to be changed. The meta-data exists in a space with similar naming properties to the configuration space described above, and typically one variable in the configuration space will have associated with it metadata with the same name in the meta-data space. However, this need not be the case; many different variables can all be associated with the same meta-data. In effect the meta-data serves as a template for the configuration variable. Template information So, what do we need to store in a variable template? Of course we need a name to identify the template. Template names are made up of components separated by the character `/' (slash). Each component is limited to alphanumerics and `+' `-' `.' `_' (plus, minus, full stop, underscore). A type is also needed so data can be verified. Here is a table of common types; implementations are free to make up more. &type_table; Of course a default value is useful as well, and finally we need a description of the variable. We actually use two descriptions: a short one (limited to 50 characters or so) and an extended one. The extended description may be word-wrapped by the FrontEnd. To make separate paragraphs in it, use . on a line by itself to separate them. Text in the extended description that is prefaced by additional whitespace will not be wordwrapped. Both the description and extended description may have substitutions embedded in them. Ie, ${foo}. These will be expanded when the descriptions are displayed. This information is stored in a template file that consists of stanzas in a rfc-822 compliant format, separated by blank lines. Here is an example: Template: hostname Type: string Default: debian Description: unqualified hostname for this computer This is the name by which this computer will be known on the network. It has to be a unique name in your domain. Template: domain Type: string Description: domain for this computer This is the domain your computer is a member of. Typically it is something like "mycompany.com" or "myuniversity.edu". For localization, the description field (and also the choices field of a select or multiselect type question, and the default field of a string or password type question) can be supplemented with versions for other languages. These are named Description-ll, Description-ll_LL, Description-ll_LL.encoding and so on. Configuration frontends Of course applications can use the database and meta-database directly. But there should be a simple system to interact with the user that is simple and modular enough to be used with systems ranging from shell-scripts to Fortran programs. To do this we define a general frontend that can be driven using the simplest and most common form of communication: stdin and stdout. Using this simple form of communication gives us a great advantage: it becomes easy to change the frontend. That means the user can switch between a console, a graphical or even a web-interface at will. Besides being able to switch between types of frontends there is another important aspect of a good user interface: user friendliness. We have to account for the fact that some users know more then others and change the information we show or ask from the user. We do this by giving everything a priority and giving the user control over what kind of questions he wants to see. Experts can request to see everything, while novices get the option of only seeing only important questions. Finally there is an option to simply skip all questions, so it becomes possible to do automatic configuration using default values or values that are downloaded into the database from a remote location. This makes it simple for example to install and manage clusters or lab rooms or do installs for dummies. Communication with the frontend This communication between the frontend and the application should be as simple as possible. Since most IO implementations default to line-buffered IO, so we use a simple language where each command is exactly one line. After sending each command to stdout, the client should read one line from stdin. This is the response to the command, and it will be in the form of a number followed by whitespace and an optional string of text. The number is the status code, while the text provides additional information. &statuscodes_table; Here are the currently supported commands. &command_list; Debian install-time configuration Debian has had an excellent packaging system for a long time now. There is one thing missing though: a system to handle the configuration of packages so we don't have to stop the installation every time a package needs some data from the user or wants to show some information. We want to make a package which does not break older dpkg's, and we want to be able to get the configuration information before the package is unpacked. To do this we add two new files, config and templates, to the control.tar.gz of a .deb package. Since all installation-software (apt, dselect, dpkg) download the package before installing it, we can extract this before the package is unpacked. The templates file lists the templates for variables that this package uses. This is done using the format as used in the example in the section on templates. The config-file contains a new element, which I call the configmodule. This is a program that will determine the configuration before the package is unpacked. This means it is usually run before the preinst, and before the package is unpacked! Please see debconf-devel(7) for details. This is done to make sure that we can use the desired configuration in the preinst if necessary. How does the configmodule get its information? The configmodule needs a way to retrieve information from the configuration space, ask the user for information if necessary, etc. But we don't want to implement a user interface for each package. To solve this we use a separate frontend as specified in the section on frontends.
ubuntu-policy/debconf_spec/include/0000755000175000017500000000000011054263224020173 5ustar cjwatsoncjwatsonubuntu-policy/debconf_spec/include/types.xml0000644000175000017500000000450711054263224022067 0ustar cjwatsoncjwatsonAvailable data types Type Description string Holds any arbitrary string of data. boolean Holds "true" or "false". select Holds one of a finite number of possible values. These values must be specified in a field named Choices:. Separate the possible values with commas and spaces, like this: Choices: yes, no, maybe multiselect Just like the select data type, except the user can choose any number of items from the list. This means that the Default: field and the actual value of the question may be a comma and space delimited list of values, just like the Choices: field. note This template is a note that can be displayed to the user. As opposed to text, it is something important, that the user really should see. If it is not possible to display it, it might be saved to a log file or mailbox for them to see later. text This template is a scrap of text that can be displayed to the user. It's intended to be used for mostly cosmetic reasons, touching up around other questions that are asked at the same time. Unlike a note, it isn't treated as something the user should definitely see. Less complex frontends may refuse to ever display this type of element. password Holds a password. Use with caution. Be aware that the password the user enters will be written to a database. You should consider clearing that value out of the database as soon as is possible.
ubuntu-policy/debconf_spec/include/commands.xml0000644000175000017500000002022211054263224022514 0ustar cjwatsoncjwatson VERSION number This exchanges with the frontend the protocol version number that is being used. The current version is 2.0. Versions in the 2.x series will be backwards-compatible. You may specify the protocol version number you are speaking. The frontend will return the version of the protocol it speaks. If the version you specify is too low, this command will return the numeric return code 30. CAPB capabilities This exchanges with the frontend a list of supported capabilities Capabilities both the frontend and your confmodule support may be used; the capabilities supported by the frontend are returned by this command. Currently used capabilities capability description backup Backing up to a previous step is supported. multiselect The multiselect data type is supported. You do not need to check this capability if you depend on any modern version of debconf.
TITLE string You can use this command to set a title in the frontend. This may appear in different ways, depending on the frontend being used, for example it might change the title of the frontend's window. If you don't specify anything, a title will automatically be generated. STOP This command tells the frontend you're done talking to it. Typically the frontend can detect the termination of your program and this command is not necessary. INPUT priority question This tells the frontend to display a question (or other type of item) to the user. question is the name of the item to display, all other information about the item is retrieved from the templates described previously. priority is how important it is that the user be prompted. The frontend need only ask this question if the priority is high enough. The question is not displayed until a go command is given. This allows us to ask multiple questions in a single screen. Once a question has been displayed to the user and the user has provided input, the frontend will set the seen flag. &priority_table; Note that the frontend decides if the user is actually prompted or not. If the user has already answered a question, they are normally not asked it again even if input is called again. And if the user is ignoring low priority items, they will not see them. In either of these cases, this command returns the numeric return code 30. BEGINBLOCK ENDBLOCK Some frontends are able to display a number of items to the user at once. To do this, they need to be given blocks of input commands, enclosed in the BEGINBLOCK and ENDBLOCK commands. Blocks can be nested and very advanced frontends may use this as a user interface hint. There is an implicit block around any set of INPUT commands that are not enclosed in an explicit block. GO Shows the current set of accumulated items to the user and lets them fill in values, etc. If the backup capability is supported and the user indicates they want to back up a step, this command returns the numeric return code 30. CLEAR Clears the accumulated set of INPUT commands without displaying them to the user. GET question Ask the frontend to tell you how the user answered a question. The value is returned to you. SET question value Set the answer of a question to a value. RESET question Reset the question to its default value. This includes resetting flags to their defaults. SUBST question key value Questions (and other items) can have substitutions embedded in their descriptions (and, currently in their choices fields). These substitutions look like "${key}". When the question is displayed, the substitutions are replaced with their values. This command can be used to set the value of a substitution. FGET question flag Questions (and other items) can have flags associated with them. The flags have a value of "true" or "false". This command returns the value of a flag. FSET question flag value This sets the state of a flag on a question. Valid states for the flag are "true" and "false". One common flag is the "seen" flag. It is normally only set if a user already seen a question. Typically, frontends only display questions to users if they have the seen flag set to "false". Sometimes you want the user to see a question again -- in these cases you can set the seen flag to false to force the frontend to redisplay it. Note that as a special convenience behavior, frontends will redisplay already seen questions if the question was first seen by the user in the same confmodule run. This makes it easy for a confmodule to back up to previous questions without having to reset the seen flag. METAGET question field This returns the value of any field of a question (the description, for example). REGISTER template question This creates a new question that is bound to a template. By default each template has an associated question with the same name. However, any number of questions can really be associated with a template, and this lets you create more such questions. UNREGISTER question This removes a question from the database. PURGE Call this in your postrm when your package is purged. It removes all templates and questions your package has generated. ubuntu-policy/debconf_spec/include/priorities.xml0000644000175000017500000000144411054263224023111 0ustar cjwatsoncjwatsonSupported priorities Priority Description low Very trivial items that have defaults that will work in the vast majority of cases. medium Normal items that have reasonable defaults. high Items that don't have a reasonable default. critical Items that will probably break the system without user intervention.
ubuntu-policy/debconf_spec/include/statuscodes.xml0000644000175000017500000000131611054263224023257 0ustar cjwatsoncjwatsonNumeric status codes Range Description 0 success 1-9 reserved 10-19 invalid parameters 20-29 syntax errors 30-99 command-specific return codes 100-109 internal errors 110-255 reserved
ubuntu-policy/debconf_spec/Makefile0000644000175000017500000000055111054263224020211 0ustar cjwatsoncjwatsonall: debconf_specification.txt.gz debconf_specification.html %.html: %.xml html.dsl jade -V nochunks -t sgml -d html.dsl \ /usr/share/xml/declaration/xml.dcl $< > $@ -tidy -q -i -m -f /dev/null $@ %.txt: %.html links -dump $< | perl -pe 's/[\r\0]//g' > $@ %.txt.gz: %.txt gzip -cf9 $< > $@ clean: rm -f *.css *.html *.txt *.txt.gz .DELETE_ON_ERROR: ubuntu-policy/debconf_spec/html.dsl0000644000175000017500000000145011054263224020220 0ustar cjwatsoncjwatson ]> (define %generate-article-toc% #t) (define %generate-article-titlepage% #t) (define %generate-legalnotice-link% #t) (define (article-titlepage-recto-elements) (list (normalize "title") (normalize "subtitle") (normalize "authorgroup") (normalize "author") (normalize "releaseinfo") (normalize "copyright") (normalize "pubdate") (normalize "revhistory") (normalize "legalnotice") (normalize "abstract"))) ubuntu-policy/Makefile0000644000175000017500000000241111054263224015574 0ustar cjwatsoncjwatsoninclude debian/rules policy.sgml: version.ent menu-policy.sgml: version.ent mime-policy.sgml: version.ent %.validate: % nsgmls -wall -gues $< %.html/index.html: %.sgml LANG=C debiandoc2html $< %.html.tar.gz: %.html/index.html tar -czf $(<:/index.html=.tar.gz) $(<:/index.html=) %.txt: %.sgml LANG=C debiandoc2text $< %.txt.gz: %.txt gzip -cf9 $< > $@ %.ps: %.sgml LANG=C debiandoc2latexps $< %.ps.gz: %.ps gzip -cf9 $< > $@ %.pdf: %.sgml LANG=C debiandoc2latexpdf $< %.pdf.gz: %.pdf gzip -cf9 $< > $@ # convenience aliases :) html: policy.html/index.html txt text: policy.txt ps: policy.ps pdf: policy.pdf policy: html txt ps pdf leavealone := $(FHS_HTML) $(FHS_FILES) $(FHS_ARCHIVE) \ libc6-migration.txt \ upgrading-checklist.html virtual-package-names-list.txt .PHONY: distclean distclean: rm -rf $(filter-out $(leavealone),$(wildcard *.html)) rm -f $(filter-out $(leavealone),$(wildcard *.txt *.txt.gz *.html.tar.gz *.pdf *.ps)) rm -f *.lout* lout.li *.sasp* *.tex *.aux *.toc *.idx *.log *.out *.dvi *.tpt rm -f `find . -name "*~" -o -name "*.bak" -o -name ".#*" -o -name core` rm -f version.ent rm -f *.rej *.orig # if a rule bombs out, delete the target .DELETE_ON_ERROR: # no default suffixes work here, don't waste time on them .SUFFIXES: ubuntu-policy/ubuntu-mime-policy.desc0000644000175000017500000000113211061226145020536 0ustar cjwatsoncjwatsonDocument: ubuntu-mime-policy Title: Ubuntu MIME Policy Manual Author: The Debian Policy Mailing list Abstract: This manual describes the policy requirements for the MIME system in the Ubuntu distribution, describing the rules regulating the registration of programs that can handle MIME content. Section: Ubuntu Format: debiandoc-sgml Files: /usr/share/doc/ubuntu-policy/mime-policy.sgml.gz Format: text Files: /usr/share/doc/ubuntu-policy/mime-policy.txt.gz Format: HTML Index: /usr/share/doc/ubuntu-policy/mime-policy.html/index.html Files: /usr/share/doc/ubuntu-policy/mime-policy.html/*.html ubuntu-policy/ubuntu-menu-policy.desc0000644000175000017500000000107211061226144020555 0ustar cjwatsoncjwatsonDocument: ubuntu-menu-policy Title: Ubuntu Menu Policy Manual Author: The Debian Policy Mailing list Abstract: This manual describes the policy requirements for the Menu system in the Ubuntu distribution, describing the hierarchical structure of the menu sections. Section: Ubuntu Format: debiandoc-sgml Files: /usr/share/doc/ubuntu-policy/menu-policy.sgml.gz Format: text Files: /usr/share/doc/ubuntu-policy/menu-policy.txt.gz Format: HTML Index: /usr/share/doc/ubuntu-policy/menu-policy.html/index.html Files: /usr/share/doc/ubuntu-policy/menu-policy.html/*.html ubuntu-policy/mime-policy.sgml0000644000175000017500000001133711054263224017253 0ustar cjwatsoncjwatson %versiondata; ]> The Debian MIME support sub-policy J.H.M. Dassen (Ray) jdassen@debian.org The Debian Policy mailing List debian-policy@lists.debian.org version &version;, &date; This manual describes the policy requirements for the MIME support system used in the Debian GNU/Linux distribution. This document is part of the policy package for Debian. The policy package itself is maintained by a group of maintainers that have no editorial powers. At the moment, the list of maintainers is:

Julian Gilbey J.D.Gilbey@qmw.ac.uk

Manoj Srivastava srivasta@debian.org

 Copyright ©1999 .

This manual is free software; you may 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, or (at your option) any later version.

This 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.

A copy of the GNU General Public License is available as /usr/share/common-licenses/GPL in the Debian GNU/Linux distribution or on the World Wide Web at . You can also obtain it by writing to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.

About this document

This document is distributed as the mime-policy files in the Debian package . It is also available from the Debian web mirrors at .

MIME support mechanism

If you need assistance implementing this sub-policy, please please ask for it on the debian-devel mailing list. If you have proposals for changes or additions to this sub-policy, please bring it up on debian-policy.

Background

MIME (Multipurpose Internet Mail Extensions, RFC 1521) is a mechanism for encoding files and datastreams and providing meta-information about them, in particular their type (e.g. audio or video) and format (e.g. PNG, HTML, MP3).

Registration of MIME type handlers allows programs like mail user agents and web browsers to to invoke these handlers to view, edit or display MIME types they don't support directly.

MIME support implementation

The mime-support package provides the update-mime program which allows packages to register programs that can show, compose, edit or print MIME types.

Packages containing such programs must register them with update-mime as documented in . They should not depend on, recommend, or suggest mime-support. Instead, they should just put something like the following in the postinst and postrm scripts: if [ -x /usr/sbin/update-mime ]; then update-mime fi

ubuntu-policy/libc6-migration.txt0000644000175000017500000002534611054263224017677 0ustar cjwatsoncjwatson Debian library policy supplement draft for libc5->libc6 migration This document is meant to tell what a Debian package providing a library should do to support both libc6 (glibc2) and libc5. Note that these requirements are for Debian 2.0 (codename hamm). Contents 1. Run time packages 2. Development packages 3. Source packages 4. Requirements on libraries for Debian 2.0 5. Conflicts and Dependencies 6. Handling bugfix releases for Debian 1.3 (bo) 7. Requirements on compiler packages 1. Run time packages A package providing a shared library has to support both C library packages, libc5 and libc6 based libraries. This must be done using two Debian packages, each depending on the correct C library package. The package naming convention currently suggests to name these packages as follows. Some packages (mostly from base) may use locations in /lib. based on | package name | library location -------------------------------------------- libc6 | libfoog [1]| /usr/lib/libfoo.so. libc5 | libfoo | /usr/lib/libc5-compat/libfoo.so. [2] If a library runtime package contains files that are needed by both versions of the library, a new package should be made for just these files that both other packages depend on. This package naming convention does _not_ apply if a package uses different sonames for libc5 and libc6 based packages There are two exceptions from this rule. The shared linker ld-linux.so.1 and the C library files libc.so.5 and libm.so.5 should still be located in /lib, not in /lib/libc5-compat. Packages based on X have to use /usr/X11R6 as prefix, not /usr. Note that the X libraries are designed to work with both C libraries. 2. Development packages The Debian policy requires that all files needed for compiling/linking other packages with the library are in a separate package, the development package. Up to now this package simply was called libfoo-dev. As packages based on libc5 and libc6 usually cannot use the same development files there has to be a clear statement how to separate these. So for now the following packages are required: based on | package name | hierarchy locations --------------------------------------------------------------- libc6 | libfoog-dev | /usr/{lib,include} libc5 | libfoo-altdev | /usr/-linuxlibc1/{lib,include} Note that usually is i486, but may not be hardcoded in debian/rules. It should be obtained using dpkg --print-gnu-build-architecture Remember that the libfoo-altdev package has to include symlinks /usr/-linuxlibc1/lib/libfoo.so -> /usr/lib/libc5-compat/libfoo.so. to enable using the shared libraries when compiling. All documentation that is not depending on whether the library was compiled for libc5 or for libc6 should be either part of the libfoog-dev package or be put into a separate package if it is large. In particular this includes manpages which _have_ to be part of the libfoog-dev package. Note that the choice to base Debian 2.0 on libc6 fixed the fact that the main locations will be used for libc6 packages. The alternate locations are used for libc5 based packages. This decision does not necessarily mean that by default the compiler uses the libc6 packages, please read section 4 for more information. Using a four-way approach for library locations (standard and alternate locations for libc6 and libc5 based packages) will make Debian systems inconsistent with each other, something we should avoid at (nearly) all costs. 3. Source packages The source package name should _not_ be modified for hamm. If a bugfix for bo has to be released, use bo's source package to extract the bo source and add for each hamm release a line to debian/changelog stating that this release was a hamm release. Make your bugfix changes, including changes to the control file according to section 6. Then unpack the hamm source again, update debian/changelog and debian/control to figure the bo release, and release a new hamm package (including the bugfix, if it affects hamm as well). [3] 4. Requirements on libraries for Debian 2.0 Libraries (regardless of which library they're compiled against) need to have runtime dependencies on one of libc, libdl or libm to enable the shared linker to determine which library to use for a binary. These runtime dependencies are _NOT_ dependencies in the Debian way, but dependencies generated by the linker when generating the shared library. See the binutils manual for more information. In general we want libraries compiled for libc6 to be thread-safe. This is, however, not practical or feasible for every library package. Making a library thread-safe involves quite a lot of work, much of it nontrivial. Thread-safe means that the following changes must be made to the library packages: - compile the library using -D_REENTRANT or -D_THREAD_SAFE - there may be no permanent data residing in the library memory that can be different for different threads. this means in the first place no static or global variables that are not in some way protected from access by a different threads via mutexes. - all write access to files from a library must be both protected using some file locking mechanism in addition to using mutexes. - at least some library functions must be protected from being used at the same time by two threads sharing the same memory space. This is done using mutexes. As these usually are all nontrivial changes to a library if it isn't thread-safe already (in which case just using -D_REENTRANT should be used in addition to whatever the library uses to support threads), I suggest that no-one starts doing this without getting in contact with the upstream maintainer(s). If a library has a thread-safe version, the debian package should use this. The performance deficits usually are very small when not linking to libpthreads so only if there are serious reasons, the debian package may include the non-thread-safe version. There will be a list available that lists all libraries part of Debian and their current status regarding compliance with these standard requirements. This list will be posted regularly to debian-devel by Helmut Geyer . 5. Conflicts & Dependencies for hamm packages The libfoog package _has_ to conflict with all versions of the libfoo package before it was made to use the libc5-compat directory. Furthermore it should depend on libc6. The libfoog-dev package must depend on libc6-dev and the libfoog package of the same release. It has to conflict with the libfoo-dev package. The hamm libfoo package has to depend on libc6 and has to conflict with libfoo-dev and libc5-dev. The libfoo-altdev package has to depend on the libc5-altdev and libfoo package of the same release. 6. Handling bugfixes for Debian 1.3 (bo) Using the dependencies from Section 5. there will be problems with making bugfix releases for bo. These have to be handled carefully as otherwise there may be tremendous problems for people using hamm systems. As there is one package name used for both hamm and bo that stays the same (libfoo), we have to very careful. The following steps should be followed: i) when making a bo bugfix release, be sure to make a hamm release at the same time, using a higher release number for the hamm release. Update the hamm package's conflicts according to section 5. ii) Any bo package for libfoo _has_ to conflict with libc6, libfoo-altdev and libfoog. iii)The libfoo-dev package has to conflict with libc5-altdev and has to depend on libc5-dev. 7. Requirements on compiler packages The compiler and binutils packages have to provide working development environments for both C libraries. Basically (that is from the compiler standpoint) there is no real difference between the two environments, only some paths and automatic definitions have to be changed. All this can be done (and is in fact done) by supplying a different specs file in a different location. The gcc packages do this as follows: The gcc package uses libc6 by default and is installed in /usr/bin. The alt-gcc package uses libc5 by default and is located in /usr/i486-linuxlibc1/bin. By prepending this to the path this can be made the default. These requirements are fulfilled by the current gcc packages. Remarks: [1] the name of a library package often includes the major version number of the library. If so, the 'g' should come before this number, e.g. libgdbmg1 as package name for the libc6 based runtime package for libgdbm. [2] The location ../libc5-compat was introduced in the ldso package. As ldso is a package on all linus distributions we'll keep it for compatibility with other distributions even though /usr/i486-linuxlibc1/lib would be more consistent. [3] An example for relevant sections of the changelogs for a bugfix release for both bo and hamm (with the last bo release being libfoo 1.7.54-6 released on Mon, 16 Jun 1997 and the last hamm release being libfoo 1.7.54-8 released on Wed, 18 Jun 1997): -=-=-=-=-=-=-=-=-= bo changelog =-=-=-=-=-=-=-=-=- libfoo (1.7.54-9) stable; urgency=low * fixed bug #543547884 -- J.D. Maintainer Fri, 20 Jun 1997 08:32:03 +0200 libfoo (1.7.54-8) unstable; urgency=low * hamm release -- J.D. Maintainer Fri, 20 Jun 1997 08:32:03 +0200 libfoo (1.7.54-7) unstable; urgency=low * hamm release -- J.D. Maintainer Fri, 20 Jun 1997 08:32:03 +0200 libfoo (1.7.54-6) stable; urgency=low * added handling of bar. -- J.D. Maintainer Mon, 16 Jun 1997 18:45:14 +0200 -=-=-=-=-=-=-=-=-= hamm changelog =-=-=-=-=-=-=-=-=- libfoo (1.7.54-10) unstable; urgency=low * fixed bug #543547884 -- J.D. Maintainer Fri, 20 Jun 1997 08:52:09 +0200 libfoo (1.7.54-9) stable; urgency=low * bo release -- J.D. Maintainer Fri, 20 Jun 1997 08:52:09 +0200 libfoo (1.7.54-8) unstable; urgency=low * finally made package compliant with those strange policy for hamm libs. -- J.D. Maintainer Wed, 18 Jun 1997 15:34:12 +0200 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- Helmut Geyer Helmut.Geyer@iwr.uni-heidelberg.de public PGP key available : finger geyer@saturn.iwr.uni-heidelberg.de ubuntu-policy/fhs.ubuntu.desc0000644000175000017500000000113111061226133017067 0ustar cjwatsoncjwatsonDocument: fhs.ubuntu Title: Filesystem Hierarchy Standard (FHS) Version 2.3 Author: Filesystem Hierarchy Standard Group, edited by Daniel Quinlan Abstract: This standard defines where files should exist on UN*X systems; in particular, on Ubuntu systems Section: Ubuntu Format: text Files: /usr/share/doc/ubuntu-policy/fhs/fhs-2.3.txt.gz Format: PostScript Files: /usr/share/doc/ubuntu-policy/fhs/fhs-2.3.ps.gz Format: PDF Files: /usr/share/doc/ubuntu-policy/fhs/fhs-2.3.pdf.gz Format: HTML Index: /usr/share/doc/ubuntu-policy/fhs/fhs-2.3.html Files: /usr/share/doc/ubuntu-policy/fhs/fhs-2.3.html ubuntu-policy/fhs-2.3.pdf.gz0000644000175000017500000067526711054263224016357 0ustar cjwatsoncjwatson^Cfhs-2.3.pdf\y /Ebku3\%J1̺IHcɕHmBb*MC,Ӛ_y}fxO* 1p? =I..3) '璑a> vu"ε/9@쒅3$;9a\;ui=94 h\\ڥ{cqܵ9"k̍8CB~/$Ήj_/:Y?(%dl**kqfuzWI; f='(yWW}S/<߹ Bw{ű} iԏ}ƤFpLRNr[H3l*~Iy.RfO?gv.jk6?ܮ&-C15ǴDA}M!3Ydޙ:bj(r1gƸPssth@MKTZ%ma cVs9;qb sG-aN\4`l,NػrĥDpAD!Bbb @ sYq--(N 9g$E$EE$%!BR.;ĥK)(:rDj?T|pW(Ԃ rp{K=312>2չ,\.6`$(q?RU{Kz[.^APqҎ1 7|*]{nѨJ[/T>^yad,, Ɔu 1Fzѵ>vrmU^K]x+~.(ȏ>{3w*!z\j iKuϕHA^+g~4jO\nȔhy o~%y`Q?^omO_d1S@B8ecƍHL[B߽bMmaiJ%mKmQl:& z\k48v eM )S#Nϡ.mUDyD ~oN'9ۦ(ӗAz۴`7X+Fló3ОVd݅*<1ypl5 Ϻw6$|xzC'|zh8u_/Ƿ9sa׉; W>%a>;Tx/$Kg9,/=w^"3 ;Y/K]w>{^$? F%nVO6נ-%aͣ~ +?պ<3?^D^x~/Cw((n(" ļ'SaNqڷDٝ>9jqqoUA FUlY^Ŵ5+?Gwwa[&`=;.xp~p]nIc~Wv{b'ܚ|]sRhNлp͙:~|5숂R췴vp)J xZFkתvE}LOa4{Yϡmr/ \rLC곽/}"H֤ 7'#+ܞ/US@/ǀ瀈ȿ"b_e? DDݙEpH|GZݥ%ť$fRf{!i{du) ̐v'OmиŽ6juye?]I3jPOit-~l`Wb-u` 7P34_==?Նom< F人='E ${{&C3yzpwO<ι/L>s%(I Cy)\TgIԬ*.!|dOcnv3u<’p~{ԌXtk\gʱRin#=r CIICWSf'gC+-]~KTZl70!K:tg[5%/Ν>zKqP\Qx[_LJP4Z^]O!PW}9*AG>z080쒐Kќxr$ea\Fgm׭6{m+eDp[0F ]\ڴ؜SpB1m3WEsږ\Tъ/Y|\Xz⥥"/Z*0N` ˂[lV[vdVu]㟀  6rk1xRnS;0Bηñflllm@ Y2~D֕e#g_;sn-z?G&hDK[1O=}"ˑB_լɢDg0mb&!.7tjÖAmi={xIK Qe'(4((_ n<zLCUOnQZRG*,Ko3v]_l KQM$[./Ŗjp(8:xkFr!*0٭wl_ӀbK{tE6l% L lf!FE쒒Җ[wɹ\~3P NrGGΈ#БܡX3C e^F{U+dC/!LchIк h~"Z'P2lOJ+^)ޅD䬐Dz'.X᪷Xbc=0~\^o| {&2<8@ܽʥ["td&Y=EI~z N딸b4U@./b[U>:|N6g{ e1+v㶛ԕW1t1AVya3Xs Y|,p(Qc>\_v(t`.eVG: #Hܘ"u` +SbfRSˑ5 Clu޽tv iٯq9ad޶Q9j{ AsSo5@Chr%a=@D.k UިU5Q\ǧo*+9PC$R>ؙ:>n³b6Sxx[F},~ISY8XjGR+A5@I ޲4|KUˡ.C7PeiU6OU' X~ݽ+89잿 u٪m嶟Ki8̠|7G(X !95:u|$iWS`;=A =d94]=8$(a-}cjЪI/]¡J/\9_Bg<ӣxMA6,vo^x1^~&# r7o_T>躑 :mC"}/:-WA*9Y"WJP7xAIF]IjBE,A]>'F[JϧSS^w l*t6E`xW@`eR3]Nj{2ymU)?Au}%rY;ZKMc'Ry4.q+rk|[a&hINtG{n|Gn8Dg^MPTT3K$i)85`;0?%}D^9>s3\",cg=e.-^{;Ijژ< F3i4idQq!ϙ~h4iyȷqa]6-_ CzG!ho@BIfv=lO{;I~MrXs)*!ӣW s4s} @ 7N5"hRB}AZfɷ116s&}ìQfL[Tu;ZO#LIzGhrIglXe-z/!AtKM~9j-7W:GJ'NiW#>)>Y~ˀy^w̄K nvo;Ovbg畗`\4*[Vo{0bxH9T!^ۻH9bTm]7 oq6n0KԿ{ {YmN%v(9w*Ul6QI+M;bFg}vEW"Lѥ􇰖ukCW%i*8$z_-Ԥ]b!ۺ@[.#Sau9k ~"2%;I4yR_4FA{CC89boyY;!lVX, -<5g\~vPo>>?'pL }>S_Fs6aTs2s~D6A(y5!"N3e:tϟ3|V8̩Gn7gπ3@B{C LB1Ԁpt niA3S xQ|$fTY Ӧ2 ʇr-#8@\UF8&M]k4@!B[)$J<47Z<j~ue"AOެ)=M4u~Fԧږ )QG9%w5วoz=6nU*5Y>_](2e2V{gfU`>gjy[{·}Ӄ3#o>I81u'Qvk&% g^Rnzd-u*C<^3(ajLx=02-=,o5r%j) XՋW!Ri+yzTm/U٭<\ɉq<؏M/ b(QuUafKwD7E1F4nfk|&&Z Z<L|A5UfwIpt.G_eS'-&P“Ysq!N/^mҥWQWhL@dxxfCo.%yN E o lҞ ޤ@%f;f55zy>$cG9QC>}yDNlr8q~37)aN7Ro7eAy`|=o'3;WVfpl 0(qM  )H쓌@D6'u vNc\tw ׸.׊|tm$b(&Z<)oc|-h <5n['eSyJ!f]-ٞd'7juPbg!Cq<5DqyPm_%I T,tt]pIW 쳋İ C2h@E@\TtUBqI@uβ߀P9R{ 6=ܡ} q.YitRz>`ф^Ϸq<4G&T%;js?i47Nje!q t~_}χW6D޽psL;96ʼnr }Bz96&m]&[ lb^W4f>šqӀyU6mL8mtk8 BU`+O0]?ؕv^WJ/n'QƮ\M nW-5J ѓ($@k T,mPw X#]?X2Ĉ@^HA(i@@|ϏX 0\T{BUδǁ83i?i?i?gsoՁ9&_v}7`R7 \Ԉ,yK*{؈ҝ..j<͏u it`iLU[}qPp& SUxN#OZ?ڨK\g=ܙ/Vυa|蛉9C_|ޣXWI{2U_Rr~\ۋ~q."{ps״wr|E4,ux+z pqA/vJʜ9Gphѵ=<-zev=;yXu[_o t~AL^vYw*3z-Yl6yEc`+?tѮ՛m,߼i!^bgڔ#*wl>T$W4%i/\]yO W2/sLp*K 4AyUw<ä1=R n\Cْ[W&켸d j\y[jvdǶ44pkV.ܾ9`Ж=?U] ph-e#4>9^['ܧ]<[v~{ z wt'+d^]'.o|l˪ 8eYTv~4Zu)_j_Pfi>;vv k[;cߖPOJ:asvE/z#we^5pG}g KEVZzG}*CZ ta{ ^ O8 Gf͇Su\[ `6^WVs0̵w4Vu *Ȑ5^ ܺ.bj!(|j QqCӯۂ`zV3E|v~?>ҝ;V9Zx6N NO/|}# m-WR# m-G [G5b#Z74?M.kt< ]D"OWU\ Z1p\{jͣ:Fp+84'7l'GY?=(uw/S wd5CY}_R8[Un}qN gj~R @urFo?sעxU:!5Fl5#9B34Y邭gQ]աHdI%Pq= OvH b_:V !J^$`k8_sʿMe:e+fR.gߺճSQ#k)?WPϦ2Q"-9,QU{d^]x+.y6_g(4FBo3Gam\/|#ag8FDŽ0B$+ٹጺ2 W46Ȅȃ1ĄbT˿8aD]f2 3]T▪1\ ]US+O!30DBLfP)\ RC d(X r9Cdj"Cj`2Yk05C[ b/]TyD4Ș6˛Z4Uy6Ŵ,:~ k -9jmfq}[NE\2a5ovcPd7U@s:J .{!I@CdLPd@Y#"@aWSjaAfvHlNרY:r2!vD9iZ!-[uE=uX}B}G q о5XoQt_u/p-X\6wDvLXǍ8WsDd 3)9P#9bZ|!Ԫ媺sC 稩tXf#ClUЊ`H|z#`B<ր̶5 PR.aa"Zi(/pT"\nb>ߴ ]<<dHH MA&9m0Ck.ҩDQڏ(!POU:ԙA P6cX lIFM3%`;iPa21/9]@wF*]J #`%ԗ2J'Q@-Aԑx~dX;%>!Vf@AV;WjBa=YL ^o-M"MeWD-JQ R6, ]$EBYHB?7aYcW\L7J z7hPďKA+/$d-GZA4,4gx??}Qz@!* ;2!GÏAJV"Pm,2@d2?R%(%#Li\ӓ#0W}2[5i!l4 6Q !:)ȵ)HzR(PDu5""R)@ ]GR6@mj%W w =~S}q&h^֤"AǶ`/:"sB8ͤoJf| XztDoOGOƀ8d[25)@R73=ډ<}B{@TTo|vH53Օ6Q,"وM;-Q F[Enם\z̺׸9vj׫}*5XuwZuv_GGû_?ϯʿ\.{Up0w`AeQ-Vz\UV },;%kyd@p[VB:#{u~zjf-PZ%  YK sLRgA&Ԡ.3ЛT% ΂PKAX.#ǃX*`{1~  +k]hUCMnS ulvAj:.ӿ닞j7(Ͻy` LR~8-mRP@0qqU(\8aV80;N($%`RٰQ1QlXybs'KtOkx*!}rkfB)k ʚ>Oٔͦb TU}¢ќ,׻cMe<49J3? 3BS&SoN,ApD/ulXC+À[' BpDO3|LFrsNt&>sfe{ Wmn` 2bAX'(p$$D~8z 12|[:ȍjF)cSS!^a I,!mT2g I\"sTҢ$E0iF2! F!]"KC>N(ri2DAt&* O[id+-8j,[S% &/?퓵_K{>(Oi!:RtĊZ<{we١W]^[X{#WUꐡ+*Lƨy)e7=.Җfon}k/o.2`mqy5y̺SJ+%۬e\akk]7mJ>{}6Ipbgpr? ,faJlޝabbPWGCKWD}x|5)7ZDG~`B E/P0˛!Peok=m.Z3 <%=Jү_~Q:=K>UE}i27qhH}ؖa4# \%aXe(̘RsXvWRbC\rq8nkSi1~`I((^p⽑`H-RdC^;`%[eơk;f׋SqdD8@@o{DQP$R2R/e hzC|1[yщcp4p鼌,d {&/J6 'p2ND{KXGr5(NdƤLRdsR˺iih|Xko@z"q'Xm]:/U/BS:ɆzwȪ:usyك} ׃O}ҧ^'jjQK˾m1x8.N/6 a0Haܨm౷m6V} 32n%M4dC\v@kL'~;Ƶ*/:øGpOC&ҌE8g5Ijt^GZSIPָO9L3z)]ɁMĒٸlt&lh|R@)m1l(q LH+B N4^ HG1dqv܌e0R  xZB%^ ^Mͨ4x1w}aO]*C/5 ɗn<hi}_;X$RH_}˰44o:P82~PKKXɈ Uov,s̟#mΖDV?f.U ymI-<@ofRGf.OieWMV2X+I+0OڏحVJE\BrqhYnO AgueKbϯ\ b0R0i2uǭa{vYuvK }H%[V /XPAA I!{sLRӔv.t\z3{.-RҍeViT6)CDn_qiO r%< U#w(r,MGf /YŠYN{ &J Bj]:eplx8T?"vPHp׈܅]m8@ERGd6DnPj43  fIsnܴ3)i-qH銼jUnjR_EDkw7;'w#wwMȝ0>}p /x~AB1@(RU 2*~νmXn޽m9K{Kv0]Z2riK% /V,0[>my?glߑD,OŠJL0;T1ef6l(j ӚŠlLP0Є\i~,gBQ@S--1wGI H=2mޕ~ԢlX= |yl3 h) VD 1F,kN"|t1LcJPg#|@K83E)τgm[3=kdq<SMfm%>N#xVlƏ'4upc|B Ls@:q Q1 p]gJ t`yzbƅwIŗyt~b"&%98} UYFfliV%7nEy}_*u!X$J3X@/`!'tDqAsǍD8>I౼l[Y^$ɫ#CقJν;q ]ON->?M}bϣ-ve|ߝ\m6^ G"<,noU>W8YB8mֱokv)o[vrPEXbP&uKy蒁aAd(?ZGPHPʡίA%-vq4CvH֬MGM7jY*jg^\ZehFNE4^%4Q K nP[k[fiL6~$5Dl1I!&QH3d.AOA@ k:0_)1yлJC5Qkq;_9 ;xv#3dZp% (*m_޺ny9%1(vqQ?}P"9[okP{*+sH'>dS~:= fΒD3`֖a+]& e?N!b CU~tmW6|?n@[wh"v{__o#ZsV]};!`@|\Vy&;Z|hij##a uA( ֆS}_F4FچoH'EH1+3v]6!KcKj@ _bENyʹRV̫?QOf@5D@'@pS*@LDL~^!fboy@j2`qr>*dDPf  1[] U;#Ae0MOh'QmkjFպP<x8Fd?]<k9!39E9Z).NϴWj-ϚGd4ͅʖU{Qq7SeʭG9gF1@qAmst'JsXތc1 <8wL@a<əLɴoq0}s 7C;4;+Bz8`h> kQː .1jCt'poʭSgv }T)^_jJ飲ͷ9z"qpK}33<1.-t!G_%pUtlwtvayee %ySr~|i \IW5G<ǍN s:%(DM6]3砅s w_>Z[d-'s q#r~N Ɇx;tI|w;l3ֵN pā2'B:s 9- V-(|/B8o;E軁 x cS2 bJmFJ箜j+m|Uxa,pYDt|̛!ۜN9A6.e{>8+/ʇhy`v$ɫ#;ҵћs슄tq"ѝ;貛SsM@UsHaK|^mf \Hmၧ}!eJ`ik~V`kpBrnA9+d(wV^u"h{47ojmIL[|K7 #=[0xs̙sY{SϸB`}iun=ڽsV`$3psg޻x( c"bɷl-H ґ qA(Q5 X Q bX!A * 0;H;y30sɝ󹆣ft|0Xk]q[H \MD7d \\3qŕdcKمI.~Xk99h#v2[foL` ڼsEvk4L[nH),=@zHրHqdHF@[$k[m?Bwt.VkteXvs:4n:4n/[Jjt졾@}HmAo& zams{ (dOI+)hqJNwP 4F .rj,y*+bM8"sT.#[Pl ;l[)0wuJ;z:%6ȞX੽Վl<ccu, cuMf`uкX\bsBh8 5BI@(;j*%bn0 |(+Lʊ7ipK8{- .ԯgUNܛkMmr3IX6өyM8(Y|2BMܱfg/~XhFy⬽~z-C}dEzVC//lQ!-_Dxi%F_eF[up^^a@MΜo-BfdH>uGc.o8glBo,YCfxӧV)꺙Sۙs7^7C;da `$e^V 9Ru)_qݘ_ް5>ܽ jBbE^!".K_,0[gf$r?p9e^'X˔Aʼ|=C.ײt,Jܐ5 ٻ^2"Y )\8u}Mmk`3ւc{(g=K+ޣkpǹ#e)F9>ыDyC}gh OjKr @7 sGs%/93*w34QY`d\C?GnS>`&CI_2-K EY:Z\DċW,?qZOҏO;wDMI\@R0&`27A2i3<3uӯbt28 ~ ;8`!L2W&!dûsQ`%'s&3gU8`5W+1.ٱ"ڴzqozOw$.̱Yګiy5xk('8wV[65Y~%آk-ގ /0* ż@zwLT2r3 !>-qj{z <"nbYIG2C6n 4vK? &]cU!?K8a>p!Y~ ռI2IF&]FCN2FME$e{'>+%{ |TWwb+ώ&o̬[xjiU;QӋVT=w;ثUoV}383gmڸ5Q-.d =5asCf8(UT-.lMOS3D<w^6ʓBf˶7L6ELB1vsJͫ#6Еx6 nҁ]l !UL6Ml<_4v%jY 'uqcFgL:"f p+n1i,卑=^ c7yzw5Xgy .}P_w&#O0Ocy7cثIBc\ K~EN2sг-j*ouO ]S84j}ۼONX\YY8ڠk l{*?)^ [TQm-Yy/νzVs &/škz<$jWnJZ%+:2TAb+o;ƖG${&^wLmM^OIr^߻5zEVis%nt|\y.uS*ozJ4dY3JV b.! \ +Çdg`̍ƯZgd)|SlZGV3vr)!eqoQėG̓/{<5 V%U݆?B:-־S0Ha@#En1:KOFoLJTʬ$Jˆd34k.^qav9mVAC pKĊHp|./G,ueyx"^lhpg_  冣[FZtSP׆9YA|]~ /ɔRzQY`"${7^L @[f{z_h#&2;xTG5%Z$C晑uMMl־z>~ee11Ao/2s6jESa`e?9Fcj]# vQxx2rw0HO"y }xb/|Q:(#7 do4< k7|VayV9dt|wMS}au0'D^ \jx]]IE@lk7]Gߵ 4u4 їkzl 65#=rrcvI}yդCwz``:O׷tSnu*r2ݮ[P˕ $ɻO#=niGs]aܦwkNG[)0{֗xwyS_L[n3y1m/L Kc5g?\ܩni)} F?n{4k' z[oqc{d}uۛe }[%!ψcO؞(z v!.XVP0ůH+ځ[gŦ|!x謵9AF%%gNW+̶]e‡|' =AR<v4'Y%{SIHV  F5{S}X+qxd+ P,V'^%؝HֈHq/7dA 3f2C `I7oxL6iEӰ M?؂+kpK`@*I ˆ2z0)9)_< q_[뽩Q(~-O(NV/⬒/YAuգؾ1J7 -N|O+_X|U' =X$rP1ltCuG,u#A(eXs 7I\D%'!|3ŦQ &fv^5{nV7s&lJބ WVl&@>,H0̀2Li_X9dFhxve1>Fjey0.EaUnU2?`YH͝*SzrU3f_?k K^|sU}/ t*"3GO,e}gZm?Xm18&H8Mކû=->=$'gtj.4k)(!414us/Kh2t0qD'w34)JHN˷ԳΈ]: MXr G .W։ٱ@J$4P4QY4ɓJ?ށWwH!&gűhb'v&J2~.Y2ӓ=~Wנ-,sg:Ϟ)_<;TI u0&֢60y& K<Є\6μ3er\K6?]^B|ƅ93y=J]~w̌~/0 Yh&[裫GW K$>MBI$lAD죒C"Dɐ`#[gaj5[X:Wj?~?^LqmRY2̌Bg{:bf4|.q &Kو&`&"@9&!C`=tRHwWboL|H9(﯐y1r*MWz(w 3!?I7eɄUUjgiI@D‘2uycY{r*gy'P9ի'ϞoswU˞Um/^/Ӽ+mZ&'Ν:|qci+h5|<yxp$Xgʟ+r6h{kTBA=,E[ vt*t-\!hAƻ" 5B]` ˻*&ؔ*s+wBcm"r7biM=謂IGWk_.9AzF0Wb`x._VDyW k3HWү;mBג0_Xe7c4FAtҨ>!&y;pI`]]x(q9yock۲K.ＢLL ]xĎ2ogW嵔VW<]~nU뎱=?XުNJ@oWYmG_ݶ)oՑML_5ʿdר3z7jU_sz _;sX5J|)@,md!x]CFAn0Fk /y A%JԦҕ]k{`yBmiYoʑEFMcQNnK^+#TN ?q6"r|nuG_76={Ƨ }V_suTV@gOne.SRzD|ranځ_^Be,[uXFO]_g`wZ68L T>To 쪅!T!VT}duqWיP\!3qv/A'.k:UIqXmcV4 XN xie8['CvA`#/~)eէDj~jE&٥+.>4* HtEz(˥<7~_!d5rd%6@@?\L.6Ͷ+Iznod~,|\-Ki  YϯgeieΞ\p;)jid+w4=v?uc#̜8[4k©bnetK7F}5T)0ft*㧁ەuj0FA"BDAfMwR['o6|M;Ԕw}f;f\%wʓc\[g7k{:مϸv¥ߛ+j5pk3IKRlȟ>xYu<n%{n&Rn7plopκ7]ק~<{_iyC faeeۺɶJ]`sCpJp.`DYP[,W qqb53~,|e(7_HB,,:7$/:)./Ԡ 5\cNXw!Dczz1 ȡuY2e,;Mذ42_D`K==F;}@H(4ـE5Ҋ$LdP7@MuMq~EW~.yKNвc޺SwxS!# G9ZNJ"3,I(WMxCUu~կ;]<;%G.]^B~i |JIY+ eW9i9fq6&C!丠kɎsQ>ʷO``XzKU9H+O=# >9!x %2;l1bbawY.jW HM6i/ϭ.]?a`x~Հ`\&!#0 $6@3c3xBg4  oC?րBf ~gg0.Ksh_`dGl\~1kX MJcA jGmgh-|/~BnXHlFm66Q| B.ǣ6@a;bBX+p u]bsodp;\ }}  ٯco`|EFSB?תگjm~uӷpŏIi͖ _L'Lˣ/2k\I={qi7f+/MBNʋ|/#J~m^.1YrG6?1K} 5%a:FF V,8. / a B4@$ >yA`p9L8A9 &p >;w I-]xst,'Q$D(E@H" Q$D(BEHI!"$Q$D(BEHL呥 c>@װ838\懶#/Z1p1t 1ѵut9Y4wur11̋yB#,3qޝ``YlK0XL~O99;ZvĥA,%)J,9d3pxl)` '̝-\Ѡ-*ODqŃ5.􄗛CWf)PuxBVvO GCb"''$UMɎ>r,g'2YUTb`w%EÚOS=`Bc >2"K"KX3.}=T_yl_`Cou3=Za]-ml͝[e949J4ڸU׍spb 鶎gZ̝-ങ-t%YJ>㪂` "x|6,>~)b1Xlv/NV\:܃XK̐%2"dzt]4R-qh F=6 Ȕ~Ò;Ŏҍ>r; GK |ٚGINV39{'3 KQW4 +c_Q0 &$:;28dܮhp+J@Ip\zr,]1AQGN`lRCRCGOYX?[s23ʌWART|ѕ.BɊLuRRq옙L>n4x%}TO#;9ZZus=1P|Z)]\ĉd2 <ې!(bZ41Cp.A0w]e bGF9:<8zl&\.'=\H+G{`$]?\)!*a]e\f&:w%EPSP! ,dDQt t%5J/#8 ]é0zs*8 ah59(}Ȗ &G]XMT J'BRJH)xBS@谹,_ yںR|Ŏ>r4\n;.8#L.9j`߭7?u 4/%f_ҥpބ!E؅@%AJ4Td#DNQTAmWBlTRTRgaLRC A+K>J>>*Qvx`p!8}=r6Nx/.9us/SA3%IJ39B~Da<ų]i TEIG+'M]$a z})kօEbԋ6j|` . f, 4>L A|\mDpF䁙 KQW.P|)%.  6cy,buEhQ*N2Ȅ sF$z=LHQrČz}o!]nt#M(QGN !\aJ=\I\f[ٻaf y _ UT2[4dl ,͂~`Y!T-^t%/JH:h+Xy2\a{%Fà)% ">$R;QDLG7g'[G9(vny xü& _$i!IJA9Ґx ЧÙKѽ&ە'B $_PPupt{98;ao=] ŗR/fffǬ`P{8o(yQ2A5{2$( PϞVbfahlok~Y|[WUUQɘұo |c0Yt<-Z48%-JFY;~-dYuW흥4lo'!UJh+SG3 bWspZclac&y*h/^P!pEC'Tl\{\gg+ZmeSpxPe-gyG3'd":4_@ En]ɧ,I۽bNt_uY8+w jCS/Qx6i}@oA9B|9TB| l}E՞b ^} fMn qF =1(X|'"OlUp[іfGz"MZ(L)Q0h:U)$Fd<g#B)F7Ec3 f ўS!k!g]!W?yĮ%!Zˡ(\)I yPh{!]C&S I . ]Z o`=uqC08.KkdF]osc1X u.tP`0qg̈́ޖnfIx̪#g6cpXWo|fsLpx3,q(OhxwENUx4bMnTvGj &M8a DcD܄OXP<p}@uȨ;);C(eOyXn+olC\sSՈp%{7as91ׇ'gy<kZlyE2fV+uacw1rXƍ5/eT:8@S6*j9Bp ((ɔHt*1?k*~~^E;EAWu9tHW<C9oXie#3ȡj{ITx`Ee w=Q9rXEi,L 0Ah;O>;sn㚱ã-7les fy1VR3xh*dzO"wJܟ@W '/ qdE>b61ҞՕ&B܌!:]6gmh2y^-o9I+}'Aކ?;q-z ߽O(/!NvUv`nU.Đ_38>apH`(pd}B(JAY>hkd{ =84Y:ecc0? Uߙis !sXGι4Ln]@4-2[9pkb/s]u޵9mhOΙ׳dń'^J+BPk ̍ٴMO6|P[^930 n]MLhْ{f,o DQW`0?%_5.¹[rl@$3eq^],΁k $=D+Tc#\ήCjNK _>#& 㒵5있kcIJ=u< d}rQq-ܣ\Ġ]EF=v4]m'N^}/ad"F9gv\?>fWOJ9r?Ar?>g,ܘ-wua-#@hmpĭdrp[ f- ܘ#Z%@BeV_%xT%O.^X[mYjHXې2zc. p?r7]oGQ:MIw$͸wy3iNwf1y=k YWMC^CfG~>Zcr< fG7y;*P+64%K OgR_^v^yH@)Sd;(04m$#k%JcfIw dnGL|Z>|XH}Bv]vƩ*ccs]#!{vu\hHK\c%bsJfUVn|{;i2)^ q- Q|>vY+-6Ŀ)c{Ռ~N~% ^]?|wuUZr S=~X>ʃxyxbcٵo9\8숧U&޼'Ȓٱ'W߮[ E y#o_!_|5#368Kǧ )#ּn+f\ ?HpjrW1ZwVHhP+Ӯ453d͇JyX!cxj~EQ8s Giۮ jF%/Ii2B˄'se8\?Pd+\=ط25f/H' ˠ287 j!lO( 73h  yj+A,܉&k̂ )MBMC!ײdP.ܞzAG {FZ2AfCcȟ(6i sI3¥E w* {2P.V#$8& k1 DyE¥ਛy&$Ԫ9$:BG?, 59 9LjL$T0sU0Y j~UO[F^!A4f'B$,d RYw˝LQrtMdRv!С% tԑV "U-aʶ谌tʑ2&kY0!5t |kǢm}d]= P64b;Ǡ |t`oyA>V7#hdXhK>t=#G0]]w@/[eA՝BzcDM.~?c`@4ctnJv-pÀUH t=mbNYv¿d LnMfK&Xw%m2SwR\վeiX}or *eğ{u5lI"&tyPKDZWyJZ6-{I#-U4z[>GS~e Y}͡j;[D@OWޖO5]gKi_dm1xn0.$ae-<Ր2d~:x ]2?na\/'@۾C;A|b NJ99}(9kodP>ulw%R\'!}80a> gۘjA6fpKkMrK/o̷T`8X2Wj[bI䀃Bj&UUⅥ 7jdA"%Pk{I8/әR?/ r/(\OOze:) /Y+Aݵ3tQD˒HuwppQEu\rG(}L<A,X͍GUT+Tڅm]nU#}v4k[ A&Q kU`1 NP( b0Qj*r#E 8@R@E@ I$ e{ŴZm=|gZ{~w qzeͪ5H ܖaBY= ;MHesn;j28*( ϠlJZ^ &οNw$A cB_z+ VAXrzd_7tAՀTe1L~mxt:D>oY3QȖa!J[ȿGMhmbT'sQ"IUчʯ赅g4b˰p t%-2)SLK/>+Ph5B.[FOśAwy`~>@q|ڏ4Ao J&+ L{2nXA7`既`͵=׻ΧoN8or}<(+4.{I寰7IQRm n}\[0E#P=.RGyAv:݆*UifYu| T=3==D@G:ThYRO+z)?Ŭ, 8R\sJT%F3rfAAuCK -W L46F"YC$$ @p(BHA$<⟁/TYI?⟎, V~J[M+džlaڲ|Zm8c nN%-zHwI_=y3~y8Q[3$u$jlsVT>-n"ɞXc 8ҒzoA=8Ț36t0YzZfLd6 $ Ql/+"Eӈt:_i)4Y[,&&bl"2tZ(#K*7>;%“s&\a鹴xf _eeh CaDz̏ =aO A,b#ЇĻS_A7e%mœQ_=yM}b剖 ]xv[k:҉۾Dȧx}xKHȢ =#^`=G.mӫtBc9UܨoםbZ_3-B21VeDhU?;z5X[Мm^ϐOq7;aèC2<;1cH6?&e&Q~Xx]2+LQ#1w:9+\Ka[{~^;x+}G23v8]Vם{pFNcvxj%rn"K7r6E['M.Y* U :tX=6]2Sqf`7 Bi[*AKC|+`NxÞVK妜Eůb/3<@lڟV|` ;ח9vu" sl1Ž-cX1n5^U`F=0Z.H7doٯ9e]i`A9laYG YsU R#a "l`]lj~Җ{ʖ6*BfkȆ?y 2ţԆV4אu/ޭ2iX a)[+DMnɱ~X1`6JPL )=16aR^W_K`p!#(/ќ8 ZJnW/RD 89 0K9 ?zaa+d۶;7u9uϓ=-UHa u_$ FL5(0B4Wu2(n'_qI+&c2d ta9!L}QVTBqZPD(Uyce~bn/*ҧ<æi\ ZkCI]ܜp?C2myq({G`.8-6_nja^y1Cn#`y0_]7kSuByL,-:eU%w:ŹhIYw, >$ɔU lҫp]}{`-FٯP:Xp2sJIŪ'&kѤ&y.Cq qHݍ{Q1]ڽʘQ/I8Q)t6wEʐl!OaW DA)CHi㰤[q.vp*pmJՕl,P5k<xEL/'0 ѡzNL'(d 1pPfVac1Z91ɰcn~9G]?&A7;WcFyُufNZrފ)mjb1Yjڏ R\yh,[[6G} G$".dNMFc;[H; 26f0Yo?)?5&Si 1znIYd,}3(9Wsnd[ nKtbQzÑUiOE7L ;u.SYA:[\ah!qrﰱPb%1ҥMzGYyhHn| +{snv[&FO:Wj˚!7׵4P-_ףm vyߟ,FOpG01Y(kid7uo VAXrf2irnC+ՀĶ}zq`%3x| g$.\utmH+oYV2,W N7[MfJgoj N*Wy pygHSD,Ŗa= }%-2)O$]rg-J$Ah?Rv=|k$syYc8LXWGHìYM‡WVAq<*Ftxeg9ˀ@Y67(D9p1s~KʫOtD4Ki eݢ W"l7RKnaHF'd Z*:unK"v=Yf^?}F8G1H3K 0-`E.YjBluzmЖZ_hlVJHigXjP/RTR)lYCZIsS]jA*&ȄaqJ۳aӑ (J2ZRFz?3{w5,Uq#xEil1eČ ˖V/#n(g)l1 v%>J,< Ǚ ; N$^:flcOAzw1l, N^ 2Ø<;Lt{7?BT.ȼtB (JG존>JCco6#%uol^6^2P 5h{'0l-QudiTFZrj旻O5 8]%Ցa zY#௩@{㺫x>/vMJYd5ς!5w݃ ʮ]̓xn˂G ZD-’ׂUmX6l BwJErFѻ0>IylƎLj,#CfzlƆiבvSc~tU`IW5AXD3RzJTrrQ[4U}Gxgj~-SK}cbBNCc@L'X껩lޮ^^hl-&8*E'ːLs:3ILurJPJ5sRQR1%ٷui9->~~[+!A&Z5I3fBD]$3޻j' 5^ i޴|Ę_D (GC^Օm= @Q].8QPx^'d "OȸGAs Xue:Ad 7%b㱑?zʞm޼4bQ˜th6Z^4Cg;J̣3y.pʎ/uJtS{_QvdݢSgE}B'QQq>HDo򎘡3.5MʎZ[O =-D? m\ P[ӮA5 ^xs=YS-fv@PbZo"h{˕-}2y m&D7GciB(XeY&)hI4S $w$(H N.ҌT#-5߮'{+DQG/~ Q4tFg^ro̕1Kʎ xn3a0ۓC ִAEUZxܕ`6rCZ opϢެ˾Oр(g4N ` 4 P FE ѣ>(Z~k"r=F!Qd"g(|zGPR`+Sv(cyy%DCxm(N5\ Gugƚ0:E]?'ٕg׷y%?AfԬ٫ܚ润t]!neJW^y1v?2pЦ8Q:֞inC`%X]Tb`wmNuNoMqE2xǺ{e]=ֶ5Nx.祣rḍկstxE.Z`d5'KQ a!.1hw?cMW! ~!GN< ?"OW9 ¯bqM}ůuC%~#CDyAH<˓ Q@丘ERz\y.!wx^VY8O ^IǗZ \n9X23ʂ$y4E 0Yff&-eBjFX1n:xcLY iYN']Y%J.r 0gVF]Xnp{7 p@Ju˾g[,mhfm0;ElpcF oE/'ﴏgOLf=pU˸P`o,pM1x'k@xss<ͱרhEAtNR9)r 7 1`T,&48J-cv;Oz+6n4:lL;8oo-}᬴SӴ"%-jVj?]򕮤nÙ嗵87Dq-Orn}zEi\`f6sw]=C˪Bʐ~EnԨI'&] #0R8W`]>m͉s(Vr 5kOaMdA $kEQ>t 8r3a]R|^?#0^l@F/e?:m&*-vN[ڢswu (iS͐mIsPHok H 5WWeWgԅ'R>EϒE譢DKhc'|֊5BFюr^?۹pR'J-!ʞ+f*Y+{F+6G9ʩ^ԅdڤqYѷ@"W3Yih 4 )9s5QN'ZɑyuDhGUJr*,}h ,cH%=vv W>Wu=_Ck3 "GҌPş%5wxY4Zٓ@I kGG2j#)a;RÊCy KWҥ$i (rZ7.rje2G7y^iƛEW[R7Y%yOWQ{Xy}GE򊛲+B23<ᅃ>bj׋?uN7{H_ͥx6ݚL:RgrUvSoN`=_˟M8oH-_tKir2HH'CDFL"fqI478ߋ_2?֚>$tiwDial鑲='EgIP7$ ӚN}1Ky+ho+maa@o ިde܇I-_UP#-~VtiܦǮX9n{֞WjPX^!ڽ_/QJQҝgJ)0|n{x}b ?m.cY ʯ-;!Gx._s;WԔc8֓Ԩ ܞ'hʅF9,nC-ax^*M[ minx0QyR6 ICen-8/k\( ̚ʅw r֋s&1I?٦ q_6m-lYK;*#Iǫ6`7)Xe-ЦT.e/zN f_K(]Jq/ ~Rt)%vhfz2P!ܗX__`sJ}?ΤNůWyW9ܲCU+68&ΏyQСòWmfKTӭkҁݏKgp9}K8H$RJn_;,u{J{o]]d^\+ ޴0#<_>D;A3(0H[ީ0v6#5Ip{wX'ha0~A_ lՕ}*lu;!-쎱7*|)2?ߵ.5k|0$nh+c8SaF/A#DTַ/)ia੽Z{o۠% &VύUfՇ+qEG޾޾*m*[6SuM}1&ZU EZ6)JDNo'LZ>Ww^ˢ^6kVtvm,&Vi>ΨyVcu-Ia;-Gr88 {ǫ7ء[8n;_λPV(5qods% ^,P;* gҷ-/G'#<{Dc\&&&N\D]uGd)z?-vAdxHW:G).!\BݍuqW_ PuCE~GuuAmC jS!8YJO]6B!OM'wu i8l36*1^Q]&gG}Q L=q̳kT3/?=m ӽ %N }7 Rlʼn mĉG1Pa c){({-S'F+ J1X, L 86ςj L.be8]3X,ЂIaG aVG5ǎրXH * -84`2(rU;Az8QͲ5 $,6@bz rӁj ka`B)vkm{8]#w"DH X,ژXY o5-FҋZtaOE3VGv&kvd+1f|)ګLm～}?ߎG5ޙ \֣*/5;F~~_s^CK*w.eݻz{~ҙrħ^yɧQ)+_5<|S!V}jؙ [6V>e .w7v9SZ*{稾-ԱVuPQTkO7m^0%3$m^pz mݷjˍ*ۃW^?ݟГ[Xsg]ϚcZ0&x#¿qKxB%hխu"po$iҷwi-(jYZ+rxp *iEfid`yqRaÂGu>Pomt5=gRФ@i\4 Q/ \Vsζ򤨍xLF#EljL%gp)Si,g> ~V".BD?&?epTlA ʤAԝ${"B sl |\5b]>_hu/~an\BQE3ե5 -Nv& =np[qx )hFYwI?N| H]ʻji?/U!uM'HVyv又4Q3 m] Չ:}|K j˼K̒].mTa^"[g PEs&->'^bBu<)cB"BP'MG |g A'X+SkJHa̝&(81DbAc e.⃂?55 x@n]?X]O^&6,0q;MpS.N􃹛D\?1(<14 떉B )zbz2P 1xLǘT]|> $hC[p?wvJrPY{ݳ.W<÷Ye(饼ܻ /ڂX+nܽO' u/4?Y'ϠXt 5ϟO\I{ b8sM*CȲ`<*I| S2VxH "`&-]f !/ўC32y)^ΤR;u1\3(dK7O!h8vc-F bO_B+:=`AÔTO< |"*h +yahm8inX0!RC/r ^xA3 YF!`.,hL.p=oR`_cB4|>,TF¡~IɞxJ ~x< 6撸-ϳGXbwUFIqC}۞vwx7::_;%sq+0ukss͛NS:oޅl鯌דÅlF?;Pn {`hc/p% y?Χ~E(DdT@Ye&QЖMxiDGiNfVgGox`!"/cG3p?kxrL-XF?uRHt*i@0㦿*\/MZu3dNjӾ}+j/{JwYmmlՏ:ƭ^ﶱgC;(H|lI(Qb$ܙ%krګ C0m6M-ܙj\-eo:j}H@\=m[uEXdiAwS5$L3Ԙ Wk"\GA|6r I h bć((ɸ\X6vAj| vӢNtvh/mj#@FA~ &!IȡƱH0 :ԃ`%lK4K1,Z<N)B*jHE-x/R*π\vZ峍Q@Oh6v*TS!Hْr̨\xx*dt(R1fT6ٻfcB16AuXJlbD-HFfhK,Me:^>F/F"egCۄ@!㢁FQ(QCUFAAډْ;LK Dah,1E/!6F5Y *@iP(5SgY:ft]8 3(%z@p߭G+E'9t\޹Y,/"pEVr`׈-e/#<3]Fڙ] KYVٴhsdyD+s7ҕc.^ gjlw=E)5 ]t:%vOY@Ypȿ=A xLI]nqO02Qp@#ȟnn LFKn L.GN;g7ȃ1p> [j4N=-j R*ȓdqvqeVl3IkPcj9 wd;ɓ6)…^ .9 ~ }"]+,)t!ڙq$L2r~K)}n=Tj=\F&٨Tzes p{:jJW@ o)H*-EMhf냤{}`na-֖0.K5 ,'š&!r?_ pi_ڋ+Orه b_&D;/?qy@,'ɓN-gc>$- p--B0yl, | vdl<)5rAɓP K< ? /w#l'Kc٬F&_di+ ,0H A҃x @֣@bdL\56'K}PptAvP@ow8W_I?3M:di3IQse1,qdmdp*5|۬+IzZO &d/%X @l<9nA3 ;ѝSN^=q#¤;qsӑAm42ye?h;KųqpLlΌڀ{=ym%YY<7/o(k'^I~ߥR B n)lx@gfj]DǢ3d\tFaD:͌yW,Ivx࿋16WAn5(Ej^Cdo_##5%U 2[8g{f&+no"٠Wۯi3-^@g%ozXu3OnGOeDr<^y +yX=;cot s[qY?3e&kHe̤`mX4źA]S#&c  'q28;ؒ?EisvĤNm* ўC4KvE[ |*p2XE,LJWҏTomwNgOgy>o W@i\4 Q8<\V8;({ G4}xOeCCfux]Gem3xbFv2ZEwZ7'wyx^F;{Dy8JQNu?IW\h7N;EĻBJyoi/K!}X&\Y箊f}ć`W]zt~(^#;QWwqf8ëoHG3ڶ?t?Cyߐ4R F鿛_[CǥeS,i5f6eatOklAZ[y{>eyDI_ݧå-,3w{>nʻBmۼ[%#׹y'1C Mt!n񘲳xl_. = !f,fel8P͘uQnTØ}Msv&u160/9#04`8 zt/*?3e߸҅ȟ2@1uK~?,k%[:$ ۟GYBo>j,izC[kY*eVu|H?ug YYes\aw=mZWY2m1#Fr .Ԩ8s7OZ +DhK!I(`3Qp|ԓM{fTx͔ÓQet8GTu6;Főt Cs{=e-^vl1+;Rk)`%̓(!ԃd8k8Dj*K\@ꥁ9Ð~biH(5^љ{kn5\JoаK,6ѸnB׻难4ЋKA%!d5<\MH<<21ȕmg ɳ˕,re ],kEijȕ$ ,Z8m+JxxuZ ~5 AKOZ-CK(8R hte Y 5Nɮ(SPyZ,ߓ3ai$N6liG>38tc}͑^]?8Ƒ+T8/ DAd$@_l4DL& 5ލiwI$ F'- G쌹"!AL* I aHp-VD(s$xTlh<*>$q-]3Ʀ(0MGM bZ$Yih6Q IqAioepULP,9Db?!㢌Q\1 '(x9/aAA 2`3 N}'dc&!I`hbv6Wtqq^7?%z-v?TPe$=RM_a_2Qcn\7X;26f+ HM, ;$A|pJ= I.5-MCȮHKAۧZ @# lDSr|EoA2ܺQ#2E<\r[}L. V+ChybJ*A1HޔYۈme,ۄm˾E^ E3E. }o:a+zXjwMY'2Rr{OwC_ˁܜՐ?s LG2jw.Jkk.lH7<멊uxxɫܗ}tLU[Y鵣k;%*~%5,:]A_g1ڨ/}!`P;2K7|2b`{鞩ʏEO]+,'BYG%|"KHe5G_w/06#L=#C၏$c0H@$,N~C@Ok~eaDnǗEܾ6ԑdY?@I; -ب?o=$SŇٙS/ܽ=ܫsM;3{)w UN%PvM#M失G]W-Oeՠ:K+ҩ\4-Pps oVtf]ymExެ)5A L*R; JFR~}?xtK' *"*%}Mi+;pYػ#ԇNȤ# \Jih=#h.}}duIs4>Yp+WJˡ2Ѳ]>q]T o1RP͠¥yܷLJ .pM; H+Q|' ?J餯 HVJ3oja ᕉza΅#TWX*zYP-fvdGj:ڻi9y.U\,  g-U[i5ӵiDx鰉5w Жf>/"6EL!tшZ!=ΖAA~]||k r 2?ren"R"ޓX]WV|-Ec[7ƨ7v;z "wqKzKspl7 Gv-!v: gN H%}q]RiGqMŸcĸZC΅WLxo==k: _) ݔWg'Kh,74͚U|Pc:+OHrȁ-yu=X(}9ЯÙ8Tc2IXW4Z9.2X#0ᡓhWnhiZ!7 _X̒wɲe yYKnE`(hƬ%nFޘǍe4<gԸ.L.p{/FA:xǘrtA>6![=s$ ai.~u>KC¡3l^_/W6z(*^xwNWZ|ߏ:6}uMMR:{{ۺkۣx?e'F٣:~IՏEEiDV n+0\$Df3gϿ%voи|57D_E(BSE!XRͽ mu=sQQt<-8ϝvLP_̅lEG =>^]z#zrvӲoDo_{m' wcOͺk><":y3Jq̈́$Vl`%F\!2.kǀnm=f:zn[Bg7b2ō&bAc|o˚>xB/-lszPa9 kPAGL2-x`U@SeߕSĈ 1A]H++":xԖ1E?L4[z~`i9PU&BM1qr%X6f%d7˸LRZM"j>:M2 [;VU脉6 T/sM\ecJQC"fD#J`dt3{N _Ōr`_QclAVlĈ׃d)ez7(R,1bX5 f gM&' *N^w''*ws'oo}J~ܛf?33eݮ257 % W,8G@s;h)QH۵Л~,M֊ ћ@7k?wYft(c} 1 7NUoÿ|{^B_LQ0ct?~} ȇ>|$ a0+\#|:QOþ~>0ʪbEToP 9ۓ#^YU0A긯s&P3V,J%E˪a8"}йfFeA,!wWS)4lܭsN?S+:?,hP]L]WlbP󛸕4~p>0Qk|Ah7*0_2/8xA>6![wHf|>H>>? >8v9q1]1٦+{k^멮Ju,Q銖fvb_obnX(Mj|σS%5"DXaD""'[:OGxd>Gxd>GJ_"W%Uj_u/OS)xJ|<%>O#|<"#|<"#|2OS)x|2OSTx*|<> O#H|<#H|<#H|*OSTx|*OS|l֖|dU= =oG'gQqӊ+֭зWO6{%% F")RA )5UuE%fէxNwxb!V2+ ==dV\ca5VjeAHJJ `>5G3#Tap? ͑HV û $x'ANV,ͬ("8 {lJj f^,I dOez t-׭Oi'8`QG=Ep<+dԫ0^ʣ`7>Q,TJ JgPTTP>띬>(L6ZTGlj 8@_Uux*Oz 3XofntzA [n4٩+NUΦ"N mInj]k]贠Yf5޿Zb5%_(4NQ]+PU#ugktc؀!G2 Ƕ2* 0^&PfJ3ޥG7`Ѥ7]QUAFMuϩa.=y4>:Ԕ`H `訤 ^I8,׮[թn8l6z侾 /YFIQUXTSz3(|ZzV?8}ԉX *JWJyQ 6Z̾ V N*^pv (SzۑTԕUeՔӄ.ڧ 񽒒LWپwlXZW1FwtGaARQVP!*#FVZb׀G(|r")+*S (YQRo4 >"=Q;d%2~W )'>zLM̬&ꛙ蚮q4z>:QE.Z%e;{Z V0P!YExF{SRFo:zVEv_?{ E:0uVcJ ]aG`77&< ]N4 <*j}h8G+5`QEOP*$IO*QAIYK0~} 0hN++)TTiQWxG̕5uiuP:],GLȞ HlU uI" "jQVĪ.0! ((ӈ)QB.Kb<}s{o?̇%OX5z,qs5CJct)^< 8oRL mLGAqa< J( 3y8D1G2郇'ZQH*Dz ف@eBk,]RWK|\x.E=0)E9)8$ TTdKf 1 dSpH2.H\`ЖPs7:rp .* 𼭆}\z^oArĸ`zPP5TP12IQ,:lAQ@\ИyM<(8 nؘ8U~$ ! K3U,Çq#>mϱ_&x(`!ŋCBr`8IANTLp>0\x & &@JfQ/%HmK=}8 1a prt 0I*&p/.H`p:P#hd: }5IX0pgaáp@pp $Ө HC!`0Gޠ obA0C B H) ;S'!0BqD#@}@E$-ѷ :Kʼn80H0P8P C!;arGAqa EB7.F}WAH0(>6}ןE_`0mӦ77[{￐`~q!bB@}(~a[s`D mK9o|G^`n[DqpN̼iM8ggݖ>I•5ǃYT4IWb\G7ߝ~v~A\n?~YX>O=4EƷRpL:Wג\)r׺XIS& MZj[j/56ȝ[#/ӜbԊN]TkE>*\F%VYRb{:Z<&U{&%Fݘ&ն5VbX}tP_i%I& W2,)ږX}[YWBjv ʮ搝[Wdb$oy,&V (|vF}yusWʳ75G_\:79`G/m=!32Ҹy i˺#voL 9FDJCd? )CZj.*\\YY?p_Aqu@ՙiwt?p QbY0+;tNi |uOuaa*a"hw$hs :H_\Q)Ec&M~oȾ6_m_Y\.ogvRF=,I;ط|>in,(UX(wE'a.R]`_$\RFrˌo1˓ zա,o^q?!Ö!(.>s Ӕ_#=0PxV֍Oc}iyM vS1#ÀTg')C[YJ]ǕDmqY灜~ѯￓ CǫdNeU#cv4VஓS+W3)#3# gؠJTZWGTV4X'<yk10jYy( *a$wHB=e]{I7NHV7hݔrmq4{Ӫo@w.si('m/6qeͧ[qEiGrU9UÂoE2慓 @NK|槵7]nY+D{"KZf&wT#}J[&JDQ_Qr\.!,SK,|>%ƍ7hLcKamU(Jzy_c UsCS{ڙOu4dV7n?0^#"Lq'O 6D -MjN?SG[kt;Zh+%q %wZQ\]Oɓ´X]Y4_wM maNe-,2ی㝸 <1̴y\9̯b$ͶI%f r= Vޗϲy2?Ip)%'t&p~lh{G#*XG8?JQʆۻJ.\e`+K\N) 5gnoOGN*=n?0f\h'Gd$򛽛G.p5 7=jj( XB$uÇZ"?poэhȬxzSoEֈȇfӭأ€8kDr,(IZ3S8%Rdzdvs^F i{v&0D _K;k}A%n./.o @Xɏ ;6+[;teӭǏEw<0QewdE_[Y6z]5*l \dtɳx-[LoOkv<@&B2yp;&un+[l5SKyAȦ.<')8pLٻKBg1{ +)x'ߝ~ `9'!Nw9CM,@g=a`"?wkDfj kU$s~_[&E1?~m%;uBk"j%bae)bLPPQhEtzz֠mZ%}帺`x iS~q6BCK[EC^ت%v:~t@69(mQ Y~ĴKr͑ڮ9*| dVK ` ao!T׿mCnIoӣ>ZIqDHp6o+ 3<[79ʻV<3S. <WBw,*]uX~>V88P,szv?AswjYt\ RlڦXc|rm [3:]v}l*']nw!gW5|EvLԫQ䔛!̫K}N0|s>NKވPx6۪dvzc$j126ۗ eXW+#oL=`5;Lvf$/+;qƟMݎ$+{:y`Vj `p` #B@,PA".*>7 vA`d丹΄K0 FV 90m*?[?Y!P^F9pOʜl*0!g0!&4=H}t&js) XY|5ziPQKժ _kK\j}Ci*h{Z"hfmߡWTGLS$oZb9eL/ϵ[HGǀ!cC)Fm lZXx 4_B -ZhX|t?;$ j_͕ ?d kT}iJJO#ƒSjhZe#oM*5FC2&` `zHFצoaO HP@ߣ5oک .Yd`mێׅiTUeSWt3#.)jkbqT}y)`;l&XEXErQM^[gEơ P@ -JBPEQP[4 VD+DM5& XA#d(ia >v6kgssk7V{S._ݜ)V+-Wf cCB ]J8#!JD?LꁽWFbW7~@AZ 8hѵ+݉U8MܻȋUigo\B{gaβ'*eBLNƁLL;F 2b`%(5*5"xhuЀ.4M05xKT_SsEJ xQ]OAyU-Do%6JVȕ22gMj؄ڀ#1}=E@R*ۍc<+;h$vs@?S\ $ 5ΛRUP qà.<ԕnO2 +WmS V>2`TWR [`kचتR#ݢccoi37n:^((1?:/̏i,wj#$\:6+gʇwśCa::B2D80_"{Ż}G(c砱cMN ^J$_ ӟcWs\m*4ՂlD0I^1QдI*Fyi0#7cp-#SQ&Y//8rWO+\o?Ay)+D6I^1MKA. ңd[ZN\cur"/{Cw_jl '05{J,{g('ϪQ"E.:zwʍCʮ!1E[Guob>~p:#eR!#/PčgƗ92v?]|Iivx.9 Qk8"f6TL&Pj- 7H"djcr@sZ zr?Li>NZqZja~ L3g&jH? -5YsrpuTF&s-Nv!Zo'@4o{qP;7vu*2؀++D{.RmAt(7h mM!Y8rcifsϥC7Wur[v7w7F{3: ?V?2Z`yENcheI]}Ŵtpe`LѨ>y޶^(pPrcA` |zmkq|VN؛ZKLMlM9 ;hW7/bX-_->)vp) ~ A0x"9])%MCr r>d'~Sa[O\T@F>cPX/($J@ǃ1uȘ: 1d86%\`S[g'|S*O%oڟW_X9#) p-U XArQAYmF9R{ A@ @/tTS X//X,p'a/8npFxNMsup|/x;14" !ԃ F@i A)+@7ׯn63o*mAO:U(l(")=|Ќd"F]Liv"Ifkj!BH@. v\+f!- vgtY0IXMd R'92O ]5/!Ysɑ  j8 {x cnBNEբjDjY~ mKPG8yxrOa~>nwcDht@L X|GH6 +b)BVr}yYܰ Cœ0|v#hq!Iv3/Ǜ2"[~'XtTC^J ]/:e7?nr*+%W_  ~ٟN;ؓc%aU]vh4pgVRt!B?Ԛhj/h 0xB DAT)J{Ҟ!EmJѕ.i}UonA2uRVH$ rV$ r)Hn/b"/&V*ek*uF y3ifBK'vMfNShgF>T4ԐVɳ^] Z(Bnv5uoD氠3EAFJb% CPasMe&)+d2ͥj4~_ٷy3WI.Րԅ,T20/<(PoRMK&WFZ.d3CKKQbfbe욻ZP\œjFO72)ݹ*2WśxZSuҌnjI TL24RynJ~{J#Uoflj>lTbmTk3H+u%%JI fz[z{ CVKꆱhpnhF{\H[ll ]WivPq2Wd3=(nZdZo umuäE&]]L0snZbIBb +b\m%p*b6a~,Zc2:TOo ͤ16L{D}Fwd }hᨴMW- Cakp`(7N989?jn:W1NɭΫT{Ib~J_ Dz TI;,_!/ʇuwbl\h#d>Ru!=tHT $\e$mw&Kk,=`3QBr"ilT-,ݏC_Hd#l =Zj]K5{tGJ-i%@vuwj'bf V: }k'``#5LZ(Q7V*!* B`$Tkvcq.χR&?TSᕌPk<c\޶Q&8n|%,)!?2}?-WR-HKT#LJ5lvP_DJj[Kv[L(JÌBrZfj *mZJR"ʨYm*r&&E^W's{?su t\j,$|SU򫛷h|Ǥ rRۡl(Z!Eg\x9,c&adk5ahp}a)ۉ1:R)$ҍ$ny%PFrlo' `f:MD87A Q24Fa9F犝R{= ^Yj,ҁ#ec/i 9/ZO۫i-߼Sa|كW wWJJx-(QWEDBz2[tњ\FAȷRV_Pikl5& Ո[GbvTYv.ta*o|kx.<(<"MI gM-笱t$-[N;ݸOf! 8vhq¾.."-l}I?8%{:M ԵWO/E?= G;]^ 8 g蕢i,%=Ո gnk׽B+!oN˚v/ / {3E'b=E/N,??1"fÒϳfvSe*}5yGC:}} :"1blUvvT iyr5Odud :9[ε1hNM@ssANGnFs}nxK1"EQ2H %d;N*,S4l=gbty :ec޴*$x|㻺 إ3y?5kB}Q~Y;loj#ݴ7^0̈́em9I/)k·LL8m 3NkJ"ׅһ_zsK>/4W ;<{{vg2(wE.VDFM]j7I$~Zoxz * nW f{)9_J9jOq #|`sH˼D0(qrtHNs/+Hǭc0!FK2588e-KwI.tD̠$aR"mTQ┣|_*&J,C?%.nzfB Sy?xs2B(1D6`G8b" մN.s9 Fx 9:Qp#`@ۃA,H # oj > dʔYe@Zg|˼?3>Ltzb:} G;UA_霞MB˨'h93HB h`9u=3˧2_A 8@#hQG-̠ilrF~Dc0VGzoZHV|L-⍐@- #p"fSxinH_iqmuz8m NnRw_EĢw7=[ lACP,Fj֎J~vH?ff^Q°O4ò$gH| 2i̯?/ uT-;y.:$c e"22wf+H)h2ęk O(ҴƤļęXX6Cu0 G0ǣu >3On>gwrP^*V&{&h|_Grugb)އ}bO@1iyz:LxuIb.wKś3 xAřV0D!Q\@Jz#ƒ=/x?K͍I&{^ķϗ $={rXP.F҄Kk,wX׺;I`:7k|Kz\TZ}(7O~{N.|~sonI+ }anR|NKBTեV:lݴ/89J6/I)uG'aB*XfoGbU],4 38UweeqXf'S8 hxA\`g)fŬYֲ#sFwnGO{ ,JwhFօk{qbw.4r>"౜f@?}hgoO 9r?+SXa1A;ƺSqGNJoe GlQ:w R\ T7YqfXɆx}$#d `)ǽw4nzU i!B =*Kԟ?G^)Ο-oYR f 3Z]!~y/$C{dӳz}C%3Y C Kjc<^E}ϟ1$ZfW'mSlO 7Qፁ՝W]6Q9z[N±%$}t!+lɑ +թ3^v;RmmqW܌HT8#UX^PoQi&H 2$DeLjy6Sx-{%l(%ej |1'1?76nU6rn.Pa#dc tY)K0Oe=-BlsltqT![y'u0T9v"qJTϷ^ ><Z4XL뾰Gy !>cGwKzjXJ";v~_ۅU@eMZ:TQw S "r˓,\(3l4 ~-_­\ ՠ5lHlknE6BܛŎ}eae+`kf6R@eC؞1I~ S9F@@ᾇtD4ʐݾъY0'?1M`gE.Y/\-hRgZ d -@ 6jm9WﲠiYlCZ Ů+CǶ9љ5L:Yzm52TlDi /~D}K0E08L&3iF诡/a켅ml9+@e5vVb$0D@CZ@oқ4qECP@ 6:oMsTDCb!Uږ#Ot^,bO73sdAOa[d1@Y \ <ʲD,?@#Hʒ YH( @^) ;6v-&"Ӗ.*K,#˗xknMxv=~qW!W.e,WQknF^CVeb r@Y2CugOMY8))M0tӤߟpATԫ z~ACY&]pYȲ8e J:F׮,D"@p, K1.ݝy.pZesӥ+\v=I]|ϟH?-v)؛u#>;i/G=-;C o|hW~^>j]^5>ٛ_.y~I?vSxc C6(8䁴TQ)u`@{1?QL~aOm:ȕ/8!جNV,wtOa*S'@m"2'c=yj*yS&?{Tr:7114~@^ PLrP:Ӥm y+2&r*2E'S}/W}CgRNq:< gF7dff`7KH%)#RqD]Z9RGzL%7jH 0юRBf:d~95"XZ@# =/! Q[=;DFD9"EJݏ`[. E agRC`Zi]q'\R2dN}7gҾ.4WjUf*T{].'?{eujwm뽃A} h+A6KMЦmfdDT =h8[ mdhAnf4j5 'ڠ~v 5ԦDN[4G}4{Rir}#_--G_J99FDCRl|b{H YE-}DEll(@{䜜'߻i;@17Ǩmwʣiꗄ Q@ 1h%? >& ƨC KRfPU2f<" m"ixZ 6c,A^M'fD[g fKRb[4593[-gWxYq]J|[WcpMq;]5=} ]o-eAnɴ^IAscVG_|^/&-6`'19k!!?6Sä 2NVcŪ{uKZ$ThƬnyzmL=,aB<[޹\ۿa{>d7,٦u^Mt3koHb 1Jnj7;;kFF V:)Z86&4\2@ѳv9ԈNV{LZ̾g'ءlC-gnSӬBdh:"5-t{V]gfp=<ա|NdFW{W^SWuZ>䓍 <|%WHڨgĦ4C:bMl:oH6/ϋ.[P,/gRU  G-&õ%ֲ49GͺQNyYjSKMp 鑱2M-[}Ie|"|6-Fŀ5hCxT6s%y)!1X$S lhzu=cIb\Qn7ӭ>"H~i =9,h#lb JLYϖ"'[NU=B^s<\VwO Լ{d^SX]feIg;KN#|ݑ(%G8I.3A8GoRsChw2>JW5 j:s|8tn&pKy>4zz֯ݦ^jmդe8O{L+x~0ٳe_ISTAٲu1VI^< K֩ɸ~5 MN>P%Eyz#/Uf\UfeԃA0+SKxzCt埜̼S %&O9k" KP& 1NT.b$`TIipMm31/^iJO4Cj3neS C9G(- ?ͪsdpOo~SB}&[i[sY HV*^GV_yZmc[ !ض1"jFoY܂e6u]!bٶq_T e5:/G:!PBjb<@Rgfג K%At+%b3mwfD}X9C@!&";ArMג?޲'CHTـvIh:m!?咪 &ZTn=a_r-~Wcs"!mp~G[2U&b9,-0)XlԊ)hdcSj)|C )͘ u~&5/nE2 &sAbHyY\v@Ԥ0g@4f(CKPCCT˪&رdMJQ$NՃ &^R. 23J[5u>yRzIjVW7!Ww JHwa3Yzr6==]Nɇ&<ٛPֳj^C,GNiqqȿo/Z9XP֩+$.l^^"_%[3rAi P-䵚ۥdFiZZhNsB=*BZ$JK43H һq*;/G#kz:_.·P}gB` gCP? o Ys M/C~ =OK[ LO@i2YPm3_&0Z ZWu.mbvῩِkuONBe,A7ߌJL)ÐҒS%$(J 1 ? JQZ\<(j|\ ?_I4GFƐ|?Ñvv\<2D@X/jmֹH >k=J%X@}nXfV^PLPFsajAb j"a%.h.srGxa=P$虦* #su=9^kx݁+Ywf!b@,T`ߝVaM 77 RV9FA4u7h3󛈨hXQo'Kc{mVLFbē9ߣMMIaq,'R6*u#YPC0 Qʺ9hsM y㈡"UGO%Wm\6\Q3.GlAtA1 =VE6"B 1K2fJDydbVbeB1@Cc 2,SP3djDT.'@$&Ĝ܅hX^ێS6( QМJ"D MQl&q;2t 0 FL "&ǀ 2DV^ N'.xzgM2KqʺB q'븡q4Ma!üȲ IW(ȍ[8kmf3fd$΁n"FRE%ʬhw^䙋66%*q.ĕtD d>dm"ejȰ!Ѭ`tDb.$^dpU i/ oyMNå+^{ xwWwr-xY}m[^TȠv?jLmS9{|y>z[h4>@51ֿ}-8 }Qq^\V޼&Le;M~-rxKŬR)3-*|qlae|,͎U릸 ym1|mٲχ* b LT0?-@LPzgXUxŒ)CA=Vі{{"K"'<j!4 3r9,N 7G"΍.CED7ۤQUNF';.UUܹݧݛpW>/UWH{LiaVE׸T5n4멪L5;.I/GO.y3h|zѳ̧9‹}kn+뱡BL HoRbL//m~{jj1zbPrِ{>rHv" /bЭ l%OM&g,GEOX HbD#0EhY9@0!؂E E9s:qC <P7ӹTʛYU7ДhG/!2LycKj0ӻY9Quƪ͒%nA)/"g9} AIuS޿A=GbO \6* ;C~_ }H%s?fj!4,bwxNT9:O0i=u3M*lHcֶݭsn58kv9dJXM}5^~z=i^2ւ8' T'^3}>=[Y>8wUˋ\&6jԂ(exם 4j_=gSb5S-fs`n+gIh[ݕCˁSޓb'E1rIcX?zNe?0TKJZr ɱKc5Ӝߨi` QSӜ~5"@?f8Zڄ \^v*=d ƈPP@j~*;ѠL$>eWԫ2!bkCM5$Χwz1 wtXbZy(Mƣʟy0K/Ac5obfܻ"HNN^%\XQo\m(}t hmS۳vfXUxТS\@$+J `Er9z,\ܦ^,%VĽ|R 2"p'~{]c2ܠa/|Kg z%J.L⃆DNwϽ3ODm|3F~wZ&o12%J̺_-~ л>s[l\"ď[ZV~Kv-bQ@ 1E. -)p:Ek*<İȣ"aٽ5!-_|KG]^_aZ t+T; !xJOn ZjhLWYrjz솓uٷ5~cg)0vTWw,/J?ۻbȳqq[J WdTK-sjzqYtS=Uk3 50դ+ mh*4̠/]MTCjZq;hij}Y&\4ڸ4 c84fGOkWE Bm^h[vĬ 6Dt(L)j8S5iR] iq(4TJ&5T 12G5 cL) 7얰d(.Tk`X- RBڼ`JT@ 1LVVǮ3߱[!NjQxtxl l?M00UudRr f0VIÔ.- S)e(A:`J&jjzwN)sZBj{4gz ʂLXZ,wYJ˓MP7[~3F㷔[{;dc[_{v\V󲾺PZ2#NڿU'6n2\ uu_޵ujoVjV ScM-DgCͲ;7/i9S3p}yJo*gevf"4UҲ&^ttNmQp".`wtt8]d*qdM"'4Y(RMNoux6&%?h$Jocq}BxgP}a&GAuMzgTqPN[mUt7)G{so1Ei -N!9o+ڗ<ޡͲGiuv(MM|Rv7d#(c WCF??w6"? z^aT?T(-9>=Jxf {*AHM6ڬr'@+ъ{4z]--۵Y(u=1X %ErP*Q4,ǀkQ|($*`&' )Z֠ɐv޵ F= #m&iI6U8 *P ȵ!Xof  ֯ ˾_,H;\@[z:P(ܰ~ b?Lbm~uK'0$ByL0F@ (LT!i*(wkmVTAGA =G+ %>@@~~f^dǯQyx/Vu5ڽgXuTuGQrrȰU(ʴԔZek;xe@f[SzUUŝ0q JjҔ{YS%3}:wڒ갷'uzicmڒ[ Pڴ fYi~|ֺM2=S-^nC,-e*yū̾j$m~zpC٧{O'锆Z%0/kNc;H']{zikOi]\_✿騳҉St >qX _h@()d;\ fO/MF t n(L]wWM ӶKB@Q8y:  &!f/oXE>Vy}ש]%dCRc5~8֩ #)6(U&y"CS\e!*t+q@>*=Pi)Zf)aC{Q&)lDDDYbB1V_2g?@ ob~tGZ+;P1YIWv".% gxtFI%;b%njٗg^-()R*vO͸|5cN{(x.k6&ZS.qjCMr.TvH;½у]虅0|<.iz f\"ć`>f?䐆ں0-mvm5nhGFk^~w]:/j_AiauΛ>rbŚɽվz\-5,iN L7“})$ONNC믳+Pb Ax2T'LRd']d^ʪɼ&ka)KUWbwK%󠉍ʰĩlq@sdȍNGJ䔲UyHWk{~XRz^Z2kqkROCT=zVb1SzJxʎtE]?gXоn8 ů_ :pV,J`GXe(C( t pdUD! S JdK$/v/|YyTb~_B6oB.nc[]Y]@ik|Yviɪ^>)+ƈh>.ooGV۾ =nfZäFNC8":P!ˈ04xO*i 2Đ>le%p:Vr z0"7Q3) F uM6%F)u3-8ܞZ4j5_~ijvQk=$0Iq* bfdGs.!RGǨC v<4l$-!p۞ZgD]6yn7`ӹZ!n9np$;D^3SL'Y~N)-T_~Ďj~xUK^"w~BWe5qJ>^F*WWUV_`&S׼7ԍsu'JhӾmg_n;P1KĢ)0ڦL6^'dx`)/S%d 7CbtCEQ JL ׇ^͍GqW½s)Ƞ=NcMQloe\m4ԯ^cْ?|fKH{EBȘ tE淰Px %&+ͿѾ24A ˾Lj6WV[y` -(0UCE´oMN.R\3MnER(/4ƴ{N8J;PTޑp톴(w?pN=W/vSQZm=6â߮l> !aB]iX~z:[~eo9V⇠A_B݇ -_kG<Q(!"u+މBًp+(-x!aoNdVQZOXq/Z%@$k꾸b:- *k:J]c SP\TcŚ(-f.@ɗAV/54oPJ[B} G*8Hp_65g}Wgj8*3Ϩڀv=n `@!rA,o$V9u ei4;HKEiL(Xi$VBX(M<َ޲>M0HEuˬ\1(׫;9QK, ^@iw,nG ?(xs *_X(ޚK}UxKx"y'Zdd_G=+}?!}P&ZK油mYu*{cUT8tTqJO=8AVVVƭ@'%QG_?KC/CM\*S/( V`#3fY0BݕBQy!:K_ ) XuJ"'c%(8s gayU,e5Kvh;.!}/0*9p'0!qQѵtvF>I+K(dHO䬡7(+8rl%W_pGW *}GNohȣbX:pԋI+bY:"D;*Q@(ǡ)2ETc"bmB:N[Wsr .O:jسFώmǤ?bZ:@ ;ÙseT<1CbȨEQSe:%BuJh @<@2 f8f,Kg9tnwҊIVdpٝȑB7):DG U[ߤm@Ltc$1"J2oMr1 /R֝E;ƫ1=u,97qeѶ2r%" $9"'d8s6=44Aκטԭ\휓\A{ɖGg ?+ |KyIe=olCVG `5wݓi鬅vp ~&gMht0A$Xչ#&?d,gh^7̨'?a׋VhaeiqϹƟ3zZm 3~>Q{udr^uFaghG9GH>zrOߎk,mJO}loH @ (9 >cJ%X-V69^FzX5n{.<~ԛӲ>f8(&y$!G'xFK]Vz }A>\^C>A/5)ř |{$ޮz+^a5Zm߭h77=u*Tᛛ5.2=,l}{] vø_"'+hd(LE\^# !ǃI,qЊ SEENB\ccn)hO 5mX>gYj+ILV`o68}jt”'Xn,t% VgO6!z?3j;f~}ci'GN\jM|yi3.%QOo?uhY=ιstڃ0k{҄$3iMܦR8g޻o8sxEq4ʽNhȠSLV-DɁȠcVz3R𽰊JAÿ@F !^ s0VVʤ͸AopLR7sIy^nz3gN#)$ JdxZsnp*<޿}jV!;v:~ʼn-~j-7wA(g`Ra_,otKɌq@$<0s!HZB`1:$a{8-EAgkS᠎”uP'?|ۭ' 2:"oTƖʟk ޓqsnH|)8_ |£xk8jCa1C ZjN roHvPGcTadD~/>eu=(~A0G=1B &.8`8)3BkmAz?L&{LZ Nƣjne[}WHVn|Fvc;A¦HЀdrn.=νpYSU+YUUqdv:9+h;Se82d+Pnd`g6E0x"+WƐq:Xŏ5]]q,E ~_(Uʂ__WGxAGxAGxDQGxDQGxJ<%OI$S) xJ<%IGx$IGx$IG) xV UZ,5)(m}aD0 4!9WR%, R,DOJ8 ;c%_HK(X^+%E "h2EDJJd Y~af &X0n"䄊;% CK"cpQ*0~7s ڦf&ᓇ BaTE3\ WTE 4+C Q&)wy 5-Qx  ddd x% (  4X<@FÀC*0$hQ S緯6,,7;7vod!ccKX[xJIDREE`:| E"xE2#|~k7il0<Em2-_<~HBIi`gODa;YnFHK(h}:C %%1F hA{aDT􄢉(| $^ JYzޯM@K(Xaj!j!1X**aHXg7%:U:Bf0Y?> #"%8 Jx itmK.CKHh`e aa5NY0~"pB~BDI]lBƉO 4w{7w@2gs3SS!w=Ҁa E#"X"X%GU\@KnCK(h`%0O~\e`X%a0&Jvp @LU7^W֣Ff:F&(&(:MMشyaQacʗۣXT+XM5Qoh^BEAKX]˼X@ xE\O(Ѫ:Xo\I"r[IYB?]7WuS]pMd%,밂nvPKY3]Y /On1ARE@{~tw8?twqswzS༽Ց躃Zng&š/|q<'(s!1&?G~k-,jۗd-k/M.X-3e[t/}nv__z~g_4G*T6q1M&VDd|0 4Խ,kO^mɠuwsq- Mqv4_SMn viu5Tвowdilo*+7+iA]n&w^TJJWDgzhgI o|9>Mw9;5[۔n;ibh;|˂̫͌bM?dcNW5k2y72./WrigؼnMr5KMa/}d+e[V]VV'I*STͲyɭg7w8),ȥUr/ɼX7iZpinCVT7-Crc2K#Ϣ73:.P%OC] oŞ]~ ^U17n#/@v 4tݔj|[ =`τ|霷[:ƽٙd7N-HgeY5[)ZfRlԹ}Ven|^ߩ)@[_b0@YwFFЕH,Nq|9 gQ ;7[^Ю&.S:粰Դu o*]Qq2olwHBfy%O{%hRPPƽa=/d~FbzGxlawٹ﫟 d*+L:4\0 ݏ5`@uC6!\ P>6w$oCs U'l ӎ}w2_O/]ֵL4+5)GV|ZMYY\S2+djUu P}c7:۳=jWj8HL6&]Z5W=S=x+үN=ߣV<& qK곃wapfX7A'=8 )hQmܷ| cgN{e YCge$ OzHJrc7xLS5shI ,{mT|h1+z̝i)?vEU(O#JG؁Ҕ=!7$&< !U2g04 y}=ćU2G"ayUi- J&|H$I;xGL*R֣}kBNG2gָ}j6ޣʜv޷68}y|hMOݛBˇZ0OCgMc/d;eyV*4}ЈjD.?cg:*Z*n+ͳho~sYP^oOAEVd_sD10\SƓq$iUHIZwoXe܆nw| qN?] nFױGwf%cWpcw}XpT` rD Pߑ.z<;q.l*jL0O%h0O=odo^/lFI,Yn#]$e@CFR:zKiREi(Ki8 = nYb@3JTnOȏy$w'ՒJW)\/)qwȇTJ }TX5J5>岻 A ZkK[z4,ߛNSUS:i]dҚܘ7kq[S#(CtuR4%jbF_~ݲx_xeFNcV~GGPbo[sҞ$GͅGH|8iOmS=,l ӽKs+:L愃[S\HjFw9"jf#]Vwސۆ_ j'BK6$]mvlMH;Ξa{lg=_o(+_yHC-;hٚnr~Qn:yA0) . <*и^B*oaz-Hz~RƼ.5j>/ o;2ń'|.r:_ TS[([ݤZ[V֧@+{pQiUVSPp5˭qOۇ%_%slhE}큿UuZ M]]XڮPS7o@mh.^ ڮ_yaR9Q9 Pi7FL0L0zö%j&P2jRb]xxAюh2rW"R]"JYSJ;BLJ$f([-PnI; <||XF~ [G!6)tVb@{V!ZeBg]3Wfw>o9>gĚg~,ly45Kw-,}>4v|(*h4y_*;1b<]399O_+j;R;noR?/[Rw^^ HY w hkхQKJy?<.$l]ߴ.2lԬ^zJ+NTRE c&Yg&[`!Rc1#W @fh:񸺕~D;JQ:rȥӅhkzLB;̆ȥN[*X@Z4\ƱǧD8,HrN.+ !r[T42VJ"1Drt%*n^6;ǩaCWI.%/ MNHJ'Ƃ Y>==zxHF{=UF <}>cDm2jN&s/?f}g惪w,h4Ԡ!L!_i?yn~?:d4hָfZ#&c7{mx3x[ܩ>=X;|ា(s7+*oT?r`ܓ? 4.N].\콑M _Az$<8{/Z ޛYK yda?[z\GZm86-$k zL `@kq*z94ZăqrN"=4K%R*k.>y#Dу48"kJXB :уlsX SX {p^D|:Qv,Jɝ}Jv,N\k+,&߱M{;_`ӱHI8 *Y` ӭgrRg쬄ɮGam@. rgױH3:YY}BBpBy(@Ģyxgd 26 &~JN (ön>9[}𭑢#>Ã#D;v9 Hȿ=o+8S{ށ_Yb3BsSd?c)@y"¾"*a V*) ĢLSyv*M[0*7+\R(5!d1N߉T9-4AI^ӟƝێn2=LeIUF\{Bg{>:[drJߤյ<3 cE.>cC{,H'5's2rَgIbZͽ-) wBwS'g@s]'3n8 8 V#e*{YST!S-]ܖ%$o{=VoNm!YUdTdEȎ)`=-;o"}ΐ`=#vcw޾%eԑx?S]T3; eFiqc璢*'$FψOv,jhNZVJP𡈠9X7!j&TvT{4\ %3R("`Y ;ahoc%Jjo#ۙsND _4{rM֪1(H0 @ߚ``xT<<s}EFǓ_d"񥟅*]oU_a@a0c>@7U8 p>dƆ߮hco؊LSTkmH n{yG ^Q;p㐃T?.:p,|jnpmя* H\ᬄF"Y9xT b\&J{/ !0K|+zz{< A\*zP|pI%A\ Kkv]~\e2WX fAw6˫k>PԞ#ur˶5hK\1{ p/gc4w˗6dQCq'w+6@Y1Ү[ PS;s+ơ/zeU&nU8g (C#ǏFiybC <cZzH#o (r_u_@~~ ĨyQ܇?F4 u3: :} 2l!R9ҫ,s'zNS+yJB܋JԒ] jݒ K+&FJ %6,B8=Q!hBߜEŶ|Zo& @# Kc%P^ֈK!<0C%DZc#>!-.Z=&aV'w=Z(CE@PeuABPg'QvU#t?"AaHT;X7YuL>0OhRQ+Bi` 0+bv*kC+ģVGŊڣ =JAPڐ/3$&2DJD%ͼe7WI0ٞgȶ6R9뉋C6t00.+?^RÃsAZy % uG?I@U|/*3T@@"#XDW3Vb(^O̪Ffq$.uA ;QɷJQ|CP{JAI|mN\'.@qqȴ_OC= $D|sCɢ|WYobމyzX+%{C 5g֜'p'XYbVSMwl1f1Ne gXJ˚V!g_@Y#Uxz}Eb#UyCEknXH)8@-~gG\yVOjLV빢@:;=i}Rn@zSSŞi&󘾦"dsܛ{΃ vNR&{+)<ͤU@?-m9~ne0T{J񟫥Y7՚Pǭ͋$ ,eIlyDCejR4/#34moj*Cɺ"jF;YG"P{nTW:4drT{^Q{F}!wd>ɪgj\0!ڡ1|7,T5{v I7ܓ\W$K?gkg@%r Ԩ][@UYE}MC=ͦ0c\n;{f e'BfM'|]|$t$tX fhz#%6@ )# #>L%aMhJ; bJ<簀y0;mϛz^=3]RՑ.Vw o՟ |xNBJ yRSEeLĖZݙ9{%k0v yGe_;#nŢ]+gv|oVT%]=Gg_ɪoüy+ώݛ-6g(ឤ:2 Cg~NƜn㤂@ʿػ\Ǯ ,slZx:f lhu9'y+ Bl\m!g%A!ŸuȿlO+ &7~Bw!9~.-f _:UbY9rj;i`MHḠ?+zrs4tDk\Dؖ͏RU%683m*4 %^t"$fdA/Y$/tIGJN.G|/*ePlv(9v9Y!LjG'FYo*PL%qfjCT0_A?Fjƻ?n*x6\T)7.vcK`ʡx@|'tTdT9d12d?ILvk@ONB#{ܑ; xFx?>,зR9g;Y:lBp̶Cj%l_ ۡCvFqCJDCۃ@JF৞Bg,zh"L?&pvէ щOfLa^YB~tEAeLĆ4!V4ٵc~tC @)I7[T3z,b(-j;UK{&Y֏vE dqB PGE#M܁L_k`[>/n.2Mv~KfuI:GGX:/'gSɈ!|wbeF."w s8 v~;JX{<{хw wn]ޏv%3D =w-. ~\eQ҉;0'xk1 Uq!F@sEh4Wv@ 'V E:dJ^nt4 o[3vAqAEDo)s"[{2g|v<⎶Ħlu7LKMo6+^m q(T!cccY3^xA p'+&M_6w;UAG6{؁+\&2P"'*yV^?\ϝ(P}jFQVY q Qؓe[ Z{B+E򖹼A{@in7YedjFǕ nQURTmdctSpU#ϛ#3ʄ=|rrd_=%0ƯW2{: }c;7ͱ7%&n8\/;kikG}}=}6=s>*y;ߨ0JV0r}}J{|RoCv9ܡl}ʜw wt|di;pcЀ^^fy5bmϯlcbq/fϏɮs!hcZ//SdѓCϞv^uֽC2޷(ȧգz:ic^V7xȜzsV 9Mrbm cF0 Bs tTYC~TXZ8F]Kаn(¡[WR"tE>oZ"4f ސ%2D+D^/rc\ WGy l *m-R g[@4|GT rp2=q؛*J6a \AXis'q4z ul%4$SOcߤV x@R4Ā'F0pצ`MZ? ?uĸM2w/vv{#2_=| ! #tyБuDQ"M@}dkB.P3ui Wxb_,`<.(X8 Vb'V *h C]4z({hCz}4֌*@FBO:R&h+t93ATh0A4<`(%9ń3O)Kg"wsʋdEAybAk@pAB#>HX|8Tratt5qlkh.~F 9Gb@yGHG<#@qgl7!C !cE".]TW?RI"<}7 Q lEnL@ O$Di:]c.gh/Ewm{D * m#am`Tl AfjST+8: ^$t0N%Ÿ5QU8;G[hs e( {<5dm4&^Hpc~HIpoUZߡnsGL{o ɻ_" }8aA-3gY2zt.Ld-wpHS9c!j AQdRT.?(Vx˨&82 }j03wd}x=-ZX/L*GF48ղ*_Uv|8+l.tQ⥲`Xy˄u+[C40Ɂ4lr*VFkəeL dIH9\F#kHk7>-}&:ǂXRQ$ddzU W(Lh,HLo{LZǩ2nWI)8> 8V#e*O`EmOz?-+B;isfC䝲F- d}F:eF[e]%oӟtT~D@gSWtI;."s蹷[L˯ۭ*j_r1AhV7Y tOHN_̓1B9)e.̴,O9iNEl5{V, ,Q oXE *Q6Jq& HR8۰! -nQH0[B(&GFҕ U*A]hXj=>dCie$ݜe2L\odVpidJϽ cYkȜș=::#K5pJnh0_ u@SF9/5!,MD5D$Q*P"5/.BKD j󟊌(+QE BV'־fpFpOw__VǎJ|OoZ_ /Kz90K/muRnфS6IQejM6) N=t,,6Wm66Z ?tiM(̲ϓ3h#LdlMIᠽ<Ϩ)fbGjHk<egdo?+V+ ?xӜqrj0AĝGccwZ t(!*>ƀϨWBuF+~&巳gIѵQ"q'FjK^յ<p\>zLg+ث|k2WפdZVLMZsĝ& E7 0@BAUs +WW +ZoȤca•9^=v$LNfH14 8 V#eJ?ݮy\nyfo/uxBokpE[3ؓ=ⓧb-q ?.$0XڙP.g2h4E y.F3H,:P2X.~8>-?uI 1V-6tsXDCh`c YzOǩG%+$`ƍkVMNHJ'[3i\Zn!++~U|ٜ3ц<ꡝlgwDߴ0wI ]QOܿ6ڇMm8:G%ƞ[j-Qb-TsPв)Qm4^&n+' ݹufr6o,0qba+b0b\9Jf*\9k}^,1:%Zոl"G_x>hFVfqgV{킑O)A] 4Igdg<=VФJ?C%'4~$4Λz'w],JD$T&"2~<:aHkM;YUB8_ ynU|ff;ac_UHsܬ\|L}ՙo5 "| ҴڽSC܈h0OH>uv ?*l _F L"2q_<%2I_ /(.2q_<%2I_ /2L<,2LnitG[',a*#@FѰ ]%e#l>;Fxa.a܏71XKaB# I7]D@il h(i05D+%ăٓ2\1Ҥ LIX-zNlŸJwL5+̖8S "ʤ 13:O`: hh`q$a<51#15-E C%Jzgwf`F6O ͊b8> 8 i| 'i0CFs:MсfM"vB)28QE=m-)y5m 7sM/d|ޑ'}SIYLye--g0BLZ7 ~|ӌ(.X C!G0ƅfe[`=E`0/LvM6?tG+-.)1'>dyEuU=mC-%m/T'2Jz/'6z$cpI8Ue-e=y U-Jȏ@ol(Nz?)F +X&ABܒU_Q[Gyi0F[G)~d a (L'I C@KXCYIUԉ]8 ah{M7 +"2 $P{J0)st- zMU6l &q̔MjMYHyN={}?^UU>$l _1$1}λb:J*bn4~Jܽz fde>xh"xgF65l[V;(Yѽj]豭/8jbz~:Ji6nƿս?c]Hv?hyRyUjH@-N=#{Nlo \~"Շ:gcjT ,k˭;hН@;>%5 Mzn5۳eMjlx`鳻z5OߒGm[-+1+M,u/l_%tgDՐ>;ךÌxҋ~ϲ#aEK o.<Ȇ{ys=S88K+X -_܊ ׯڶm#iOXh$r$>ZxT>9߻g%:t5i/n 6*ʊs,׸&]>C N[OePvA۵I7z.BǼO8x6u\G;fK V E;ߜCAqݛm ,\;]vϳ['Q>5Ϣbُ#ShF?/O=Iy}Il<2C&ȴsQVѕ:3r6l}1^Lڋ3^*.p9s2,ݯ >^tgO@nnS7 [ӯͧ'-XklJo?nA~gڑ|U1ZGr|p~c&Jկ5Lcz]YvTJ~./LAf^+ (R;vŜ Wul4ﾖxW8ےFr< YPm]ӵ^odzv߮*^|< /ߗ{]iHC6Qʹu 勜19K,^.AIg$׿ 7-| `玸ˎf(LIKZԉ * "Ns:@=iU unK[]azywVxm =SL*Զ]ѡ6X9\؏;6̺p9#saܺC?1 * rS<} {61X|t]G#Ys.Mz(tzk UܘK{uiqx|P?~XmNSbm {w~lM*=iQN3gxi)x哇sm_j7?xPj㲙#u3.S^LAޣ+fm%D1fLU)cnFɞ4'8~xK__d*#]~Wv\!1/Wf]8ꖉ⬥}1Ys|;Y1O|F-j36RZ9[fqnj/.UEZ +d# μ2:W?&j!kZqJC&ԅ6Podihݫn%w43BWʞ"e"5'UFu6[k㰟@bZwFoJ2LtibhBg<,vR,><'aHA530; C:*B<^h_}w6XYxl4 L_\J+go- 5]1x4Yg:L}^R%п\=z^R@>tI6O5=ysߜ{_ج7 eT~Mؒϝdz.~}NM}ʖ&xNXraPP Pߧ+:bCw͗ZbM j#Xm-?? j0r$fqʯ6:):>/! kJ6jr2_>u,Q*>Sc-yxnӌ!ElM'$u@'ҁNҗs7{b|!#.N`ٱ<#ML$;3L)2KL&3:"/yy%Є)LbHj!q(YB|%??; :ybI 'JYdO"3>LLDfq 42 K2+֓/"? Dɰ*%Y䝄~~^N< B$< "~EI1$2:'_DZml$E*y@AYd@DV'` I0Y; ˑgb( >Vs#` 4X<PGр2 ,OY@pT$Fch F2Y,S*O``_s!OkUn`C&*&woŽXIJXzg_Uջ̆U ^jLL$MYw"xa1V'WX:.9+eo]*qBHF~ YGS[a[w{+|'HRF\]|Ѧ -) ]MЧ /Q6ms"Rs8 _ȯǰ,bl5!'S z1HF(.:Dq|`81}\";J)x|*ѦbvVxr YKAO ?6r-G.=G7|MZQ4"`>ej2UrpVY9s[]#ulMQ85/ZjEqmnSGѳK6W h2#uMn~#T ,ݿv*!uQ*P{ռ <7(Sr0P=&6E /NV/Cn&*?u5E#R 4ΞD!U{|6I</|J6#̙wɼ* s_5ꤕe,fZ]7$ӉY~.S39ݦrlS北kx F3w7_IN+@6{ !hk.sJӮ I l&Aɹ%<8Px zhe:1ŅL@R)>mX^}S&1$#uY5/t:HK9V)#* =It_Bʥe/Nice3[|6e=7JmsكG4s5SD H_gپ*Jj*cVu5J3v;sCCJ9nSZ & 7A![L;31m-hK]aah\x|> Qcj,J Ё](FX1o1pnFrifp-m)`ǧSM;?z`ne* b:&W,HSx^"o^E xaUVz[ ??x_\B1ӷ0dd籷59œ++3[;gsC[CC;[[[s +{s}Sӏ3} -==ӹC2N?VS3{|>z*:wL5&_G+G}0W/J 0Sf%c\OgđK:Hpv@"ˇCnLS<#Ɓ8dZsPV7  b⾺ EVCyxWMP81=)oygSY=)}]TvZEJR`ͮڮKg-fuzѤLZ5ίUZSLͱuHdJx5HW[Ss(;ڹXkҫzd͉T?T'_XQlq|uZÙSUg.i5.RfO\2m>wv<'lDs5]&ݩup©ya&̰r}ك0tV _Edgje)vb xj00[.)(ibekg#TrH?T($Oo < FJ@9N jy  <Ќ  rhFIU F^)(čЀ !0t_|.CNg-6䆜` @$A04 >k7?: > p V}^|kwJ@80gm6ʨ= }C}zpC@hH >ǡn:nq `##yN =z&?% [ [@P[4DUTfx)W* g$P]7;·Szc'xw($:UGJ71+s:A˧ZSݟo|vQGfDʼnH~AV{GvXUGel/_{8|t,SI[㩝{zS ; g߈dlw=Bni3rYoˁPq0Z;I3uYIHn^C_ AyVWƒ *T؟`I76niCsQ  ZMp ID4V M1684=>tR&>\ٶK>Mҍ+7.4YϭjCcvCGm9d~N[T^z|A fH 8UJ`z"؉۲pŵj:^}0*ęX\()2, O-]ugXl4`juV`E曝 D[8펿2.`!8Ɓ|=>1/IkzDyZT'ɞ!k7?\Ki\/c p&(._-⻔-N6c5 C )!V4FWn Y{2-Dw8TU#ii $O2[*v9Ͳ{"Sʫ=:b) [oTiq5"Efcq{VdHNb#qOri~Qvfɾ;@iGFa4kZf^18bY 'irH$ y'ME:̛؅1eD8 PϷJ;\k.v ):pya]B{sX0 t0&~70Q؀shCM#9[+Q]TA5mrz~qncGUq冣rq#;X/|9Va`D:\Yxev[O|IQPTa y*}o.r{JcBy츼+%j!mkrކoE8=2JrŬ4F\1{X&CH/ĦVvI@dw-7RVRJɠ܃m@S%էf9d`VZ*0 ;E$8ר?|3j at͝oU'Xw$g( &ۧRTOeIhjȫL"C/>iy8Q*AL&2؄;4s~4=kK-o |gyW7 (0rg2ᲄH9G56bH<_q;Ѥ^#v<.\s뜛v>w9Pk[ "GE0H\YĔM+ơWeQSIjdߺ*kܾ#&L4;1r?O\R&0vyPI9`qq:/ۏ.he @X?YJ/[Zn PW7d?S=|Q(UXVWyW{AaU11v蕚TPlAZr/w#"m|e+MV)'%\ ۷b&^߽7/qqyηf`Ұ{Dz6s)^6]p꛺I0c>p ߌgM|ֻVji/nCAߨ粋~ӬhQZMs Y~ +:gX>)Qed*M*:ft g͝?ŷ2WV:K홻,5󸀂U1P dži-G gPכ T5,–=]w&_P͌УhYJsͤ& ]?C+3Jlu:XK/>1AE1dem{K<:Ma*xZJqQ5(|K?=gI[jk$04olp欇=a'L2CMŠ07M zA`T0,?Ժ<9bb44`9FFś6 t,Cyh0;rp5ʿ@炃32 !@@t1)sp ==@tsp tz`  E`sP qCęYsP ==haP xs Ctz&Ah~n!^z~ w##ԴCSQ)S@<,€G,UF޸hmZb!"2pHSxVnZs< ߂yhſP={x Q`d_+F& nbR_͋B3nh$*0Z$>\ znkca_$~*Zi9hpى͠8jZu!ℳghFvӇ>kS E&z['#nC/ѣykNfaoIRD_,C.yip@ѯvmO" 9f"8GbsT*H_%(g-i2U*m*or{,-J_`}tR:ĵ#?Sg5Z~X{#URp˟0KU@xylMF宼C3`ÞRŀw%R\Ԯ..b'-BSl߷k/XǪ.= ^FIJ(PdZXvWkEgU@{#HG1gR = Uu-^HqG;s wg%qW~,z( ݑߴ3(䍑z"*ʐ[X+h_|}8']+V . 0S+p(L^;wwSQJ_փ/?o-l@L>.Kϕ$+[-J`4f-b,sVGnnIf27CVTװ6œ|o NnZYe!qO&&2<0ni@>7yx`0秜XE&Gۻ}umN,ΆK$IzSq`\N3v"s)G&hו銏p ny#K]2^(dǴOwj1hS1`T(:{r̯ vjӡB! 0_T=G48Q)AtC "hg >KS Ar#j9 FUYp$SM sEU٩s|1hs|1M'U ΔFBU1cϼ%k i^F#HkTkb\bϝ-Q) ^_hq\[h C!oGun`\Y8:2UK8?5E xӆͯ,}z^Kh9Kb8H^rq^'7#Z52X`fy6\8':wf/oCS=Mi߶:`2e*ԯwewp qUl mM^W.rZY)Sx C>NIH ʭ.L@Iz5hkB'y7 ' N4Oo{RS= 7Q!ρiK@8,%edA~<@Gp`'Ê*VU#z1*jcYtWss_~~K}Yi-e?5FQm#b|_s/}Q[z1J0շYeͧ ʟ]T^!TWJf"vÒSQDQ*A >O;YLsP[Y\vi4 ѷk84E>ޟn3~]In奇7q}N-{EϹdsΔ*ol BǛG? 6ao\;0 5xZ6}UztT2hN&A?;~mI}a{*M&­eLbU$U(Q*V26,uX7%u@ XQ*{xA܆+Phңw:%5ض!Wxi<zHi(7yt97> !]T%JႂxN7x=lc߫{_ Q)YmD-g^7awܚˇ}o;7 5q{¬Ԣ֪7vqĉgޗ9muoRDz*o$=_ DJ@Pj% d`?"y<]hSH8+5U-Cc/¹ř^NKD[)J; +v֋Tn)1KKV~a"ȥuxz%ܗדjN-67L(EWUc}R[Ԍw5bWWӻKfD'nM;4n<].RR%.&υ)Eʞ Mq&x}-9E*뇋A#tmWpuCƃ?W&Ԣq+<[p3s|O2>jL3pNU t§wf"xVT.03114ms55M][/Vc$Jph|4ShSEVf?XQRc7dyF`ʪ~bĥg*vyЗTnRŁ-3XMlg }P–/1*T -NnBJ"2 @DNr5P!_LRѩ`ݐ2W/gzTxxIe$2m;Y7G>K+/ɺt7}\rXmD.{_b/5NUORf+^ o0i^̿ͬmSʑ&EKGMC:9뗻]ÛBCU+Ԯ-F=!M6` =o\e&W}lg#o3_=M|i6xpd&DGKyŖ v۫ @[:Q؊9E5y5̂in6hov+['EgP~Oɥӿ_NM/IJ&@k9%Qȏ>,l}7SH8uɒf<ɒVMSyK6i]-A峸ÏQwb(ߎtqq40] Dp!*tu(@aWWӷ2bߡSzt M/)B){w<k ʆzY¹hh࿧FeAgAgQũ!@4V%~5 =QQ @=4J?`?OJ[3900YDCPtO`gшUG74SF ݵ O6ZY{r@(dꯌz3,BPES^"aPF0 Cw3Wo?q$:9()hϢէ D͂A00*?r@ (7Q3곌aQ!L 8mqG8L!܀Oh w({g$˝ 9& Fe.**#~ 6/Oa* AvzE׳P6f/E6z9"))0R֡Zr u qrZT0'c^K?hguLAr)og e_.O$픚|<1ɝn n Q7ؼNQ?ݫҺ76\y3xnh+'/?QxǗ;re6=f ƣeLy)j}blMb޵i>du#S {:sƅ҄&X.P/KBc76i{ǵBHF}%$TEx-dA6Nsށ|//5$r$}W 'u=yFbLm4G#]3s͎|Ǿl)Cfn5V+sgܐ ITʜ>!Wxg%eE YuO~*D"/ƧkVBd(R GJyDīGnFiJ?̱egQ&=CReEi|}SHhܞLė^pX. a rX oo!K>]Dqev{Fĕ}pp}Fy4>&iW N>AB:Zk턁_IҨ`'d"M?ͬUVg9&лt 4+$mmZcrD^S.v,| Z?H}p~UA_#bZ2L{9]R<3/XZmړr!f*:,r{dEx,>$K1.Z ŭ 5y!i<%ח>N4~_.m]͎#! j+ePӽk9Kc!\38&)OQO:\zAQECinL `r%7K&ꌎ)%򗜟Q)6K /TOb.IuC*J~ {;,Xf7X9ͮ2%XkyPG!I+˥OI-&K~q5Qͤ:TQ#9 try9}縳Ľ/Wg95z N4֪Բ w!¹Uf{+<}^K#T|knTKIb; [ݺYoibOQC /W  fng++⛍j j\K~5=r .t Ztڥn`GZuaF #Rٝś4LCXY(Sq2 pߩ'A㝛!,H 3q{R_9_Ht?oO(B OGFcO t QYZhh0 F>]sTtݟ>^f=Ch3Ϡ螛~eB !~;&|3| Шi9 t :P(r5:YN?qjDpYՐg4CO&pY(č@S>WCN5r;q;09ވPt 9ިQ,EABNeBαU`g)o>l~fD y ɂu6PQH 9Xr/;GF̡J!Xo)?Q >i8$.8B12>Ce{}s@Ա[3 9Q50n 9 EsO D>#]+*C)9rF`qmOfvyÏ[qA̳E+X-XIsMG_Q@OyTx1WR5ȿ59^|'/2[EzA݀m(*2JC`"(:Ru~сaRGJb\5j莋LEH??*iz'Qw}iVŰ|:2@o7>_6ԕ`[ފi,~heHNfd= _xME:7ܼ%N*^k<. 4g‚UΡytklr, wxlTܣ6&ʊ›m?&> ޮ s[p),8|`SJM(U"g^h '} 䭣/P%̤iSS~ 6X!a]_8[Ԓyt 0ĖmwZR;6|%lVoV\sC,Ɵs}(S|ϰ0I~{3p w¿a\4q75yKVL ̎"uTߝjfPN./"8 Yqk,#JouYoRl˃1;,#XIOݍ.Xe c& ٨?(octRuj(1txpʁԘ&kUޭ5Wq5Q :n 9J.ݼ,Ǔ1ԩsCr#~Դj|^Η8teBy>Hqt(<*kmjU#%wD,W4օr-F0~\WQzbpŲp '׷Y,`yڴoS~OҔ$t~90CԵcdu'.8h'0u?],Ϙ,)' P`vHwF{Q(O$K9qz .4py2۽ߊV0jh]AVg.JiP+֍F3O]x1N౺dvijFHۃ5ctb pN xGf\-m /Myry} N6],jXƘRqnO{ $ڏ%oKۿ Vir@K•VT/4c+q)mEN4PfSaŤ$ٰ\u6LZ_dVZכ,[#u-q EJdR>?.X`^xӥɵ}VuR^kٚVVvSdɸ5͎dq>_0~#0C<ߕ;rRM|{Z0A{/XɍO4=Y4yݧFȟsW7޿h{Ow;`n30:_hȳ8FJ?s0n0l!jfwM1~U͞U{XDw 3X"~D;}vdƬ#vywArK؍8]Xp3]Ie|Qtʣ@EQ{'&.{4:qµ7_G)m-G'dbn|g/{%N`®Zŋ.ҟY¯Sدow*Xƙx+ bM`% $L:_0tԜ0rzj2 S=~0AuGX6hw]dE=UUif37Xۯaн ZҾv0ؖ|Ugx[~Cs7]J *:.WgWzɂpQďgAݕeE07 T%)ڛB䔾<a`c^.@o[G_wޱ!5^d68hL燿B͕EszpIGТor¼lDRMDէr57]O*4ϞEƧ̷0I8c_T\I-)KvhPLc~{ti8xZKo]ـen_e[+KկƐCn7y\+>Hw̔^" #zʠtB)\S W@N}P /HZ2 mآo% ~͚_W+ |d3|j}/4␯ 5yž7RV߹xҵ5]b)=IG =j%tdP&&"uSze}Qxj߉čj`87iJa(M~ .*QΙ*uA力d?p+lEr2l{`6*ݪEs"HȿjDt`(/S/t`U_@$y:?gQPʠ8bfh9SA'l_(, b`ϱ0T9pG@)_vAhаnvh[#3r>% Й7$ws.s ?7೎ >JHD0s F09NU*MP]h8H;uz G"}4߀A1TI$̃qCPPhYj]*?Agp7D2!hgQ|>Z[E3TDԣǟ@9&)M%8C@C# t-A0 =}'"Ψ~CC!-$)mF1;e1[T=֤ :T5}Qaْc6EX&^Qm}q9 ;l\l%kK3&tJM˃ڛ D,clk+$ *LLeh(2q[8*JZYl9d+;޼Sۚjۊ7<8ݸqF߂u, q+jm[ҳCBN"/b}`_X83@OoЫVsnW$}/UY)ch5!rشLL!aGkf:]K*):i[a\u -Td4Ȭ=Z~vw8r%Ȥ0~&'_ ɳp1.#vw[EC }2t{/_0p2--wv]|';:GLf)KH'6jOK^*$h^ M`\gJ馳);lޔx3(twy _a2&,^.t]Waht׷ sEĜ 5ΤX_]" q_8G*T ^pbHj6 ~eV5F!vf,ZH,WB9Qu!omL$_"}=# v.=R;ƀ-uK]6o5l2i_غ#{54zR;41Ȇc.:B/L+zloѵQT[0vwwģ#㻤ɽKc|tM?8JQ+mphEjvY܎SCҮNm$' :X̿SRc~㷓 qm}$"Gi9VAVZlXK$*lDRU"~Ok"T*AU"~ϩB DR DU.=0s|4 ꙎF. ApBh7M|ӑTGAP^v07BsU݂A A?A|Pt 7$gaSew FS>X$*?@%@9 FĒ%٦q91?t9n"T6XA}f g.UszB`t%9jChrֹhOegTg4z 4 і5?jjU F`@#.rԧ7䥏5x`6N^}HRP({E|UP\/!;kF}%-ڛ4,>ش=9y#Cw$@8N8z9E1I5Sє>vhr5Lp"䢓4M|~d7,ץfkI&LpIO8^uo ysD'kߝaǓ::yB㯐H9[bVh7 3Q{ 2>qc 3ş^gpد]}K/[Ŷ΢d(~52P1F\H9cHl@t5҅wޱF =1{Y{G׽CᛡP' ꢊcn\zoR]t!'v)%̀JSh:cU#T¦$]4n1 n:/s`V;exTvL]D'%#`g\;qbUkQi=6tyv@,BA9j~$ F,b-Fe\&X.p:]ϻ*F+AD}ھ+='|.[jc򉩌>r/4< KuG}N4Rkeذ*q9&x#{uY|,e럮hRqRɟ?]R u]43(KYTh=uQa3`Wz;O@QcL/n6rͤf>҅.O5o݌0x$ʓ}T {\Y/w&K[cafWd`'׋ q[S 48W܏+Q_nѪ%XG:5`4)tS\YΤo_\_ٯL^xRv]mwNzЊwyYx\Z[B_U ce]IA._J Jw_9BpD Co2 z@K7E+3%`fC~B:;՞0 = 90j?slJAًTс@n: ow]r(e 2RH4-sUMEEy`$*Pb:l~@J;lv6tFv-jw0l& ɇo9?XS\ϲ]NVy4+X|x)AEygD>-j N|F?ωgCb a:x] 7p. ⛠gs|Dғ9-E|e׆1/<9x/,N1OSr:Ukrf9P G , %l:i=QƟ" A]RI QpN̥b qg1& Hx-a3{L\Scqjṙ#Bቶdj ~yaܒb߾v?4*8ތ 4cW Cϱ>"{cGK! 6=5R$j玛n|5qoLvS@3N]ݤ3=EIZr['%<~nך7yi o ;g5|lg',Rg::c̈́Q"w0+_mS*h55 vݸiD$0v ϷApYT͙F9{gQ>β=>g VXB jҝt-ݿWqj%x3b^}8^ia{V"S &i-6w#LoLۧ' r VōWs hioa(L*]=^ᏌeEoX rZ2˸ T7mkTqsu4".ZveDg׿Rl-bD/Նڨ܋0o#EH걭1',[b7`ٟ>ټ+ʙMNyGUٔJg {j/)aOy[0WF@SY{U:!OWg")hENe2-i VM X5Q _Z<{HePS%qC'=ŴI'`߬G9Ҳ2rF?Å%y^NrD73۴/VU^axrK:vQɰ-[,Q^b6[9pKt\f墘v.n& qQ Dֺ&)5)a ]7Rn2q.Ad~ҞءwX- b'ѡcV$UDs}c$uyDd's՚Oq K](ϲ+S+MhHU~A%7֏, wu.䎐Fk1@ p\g.v(1K܃h|#;CEa0X{@2@Y/Y*D|H`Lmg*TTQ?q`T=< Q 9 B+j>{_3Ѳ뇆D\d'#Xa0X|S6$p$S̻$ʔԲXy 9]_I iqG)ο}sEuG6x[HЮJy=/Fk'&jGEzlw6ys%5_d ,z".P8b݆ߓm~'A97_v~fP%JbjQYu=Nb~!ŻdxVN_4U{j5J1lOչ;{R\u~R{fl?J2˨}Jb=&piNޠ=`EMF"c_Jο)XL"@)!bv##QK]@1E,,HPP~Jo`QzT-Z; kSiJG*p_ߋows+)DgGݾکm<D]񮛪XS`A%̢Zr;I2s- LG+O5uF]& rwîcV3dۗEg*$Ҁ_>%zcvQYT\ܓvU#"^cL^W1{<['Fp)I^eKh$_̉R`w֣lΧE:")wG-4>?|x+쭵.q!D[{FA{})G o-S/sVGފH4g] -O?Z?@2*vkLu0y``Ci` ;r~$+]bR o<ϑ %2#BQz2糳[;6XWZ3XN;JőozoWtpo CAW K.h{7{\Jeܕ~G}R/|vC+9^zr$%x*3_뺔y3_r훞n5ZKR?q]PHpT]l$?^F'(BFT B''JeVkm KΪ<-&lpAvCוbTZ϶:I,в4,笲W1WjZ^˃+LW"z!,=}mO!0W#5*mDS9hF< r2>7S |FHO&H攰b_YU`LYX=~q-*1@AMqGL7<.H]\c)RfY$Mg>:^wXCK!EuN0I_ݿ 9y_w4p\j )C9Q|Ӌ<@b K%: '[g-;粋}TeȀK*M? pon-V/N>@IOUcEbu(b$Il$BtwzKκ:/$x1ENS-)  3TlM}cxTIN P>QV͑UuA< {2}fm Vxo+]P\V]XoȦ}P*we7}Q:kL/FllEa~ӄ3K񂩝[ϫ>(vǘPƴNZ^iƖ3M`*Ovl{W"L[ s|`Jmݛ(zn' Eu K̹<$ڥo *=i^)ņ( z8.3*E㎝ZVӏ ^۸wM50(z>qw6Ѝ:6!qiR):f隟 ~p>V^ۡJS7;rݺ,&}^=}p)ӆ.,+)ʓM쬹WeRJyhF^)XbVsl *4ﻘzH$iɒY4LQؿ|>琴􉝺q]ѧ"`T\&'YSKETK˷{ ro-@'@P^ˉp1*E1`p"E.JMﲍo`-LS`Nl_RHBB=-)=-!{тQqF00ĩBS{Z/(UFF~3qa< < =IDa  sN7h,g3TIb$ޛHY<Q!T9РA4 8D"O4GE4#a3s *6) D 䆢)΋E30 !#ֿ8(1H9.3(ɍDB"*Uz20(n$,@cPh IO)8]v4:dpp,ZE}eA NW'g p#?`t@$ g DrCN7q8seBwJ F`ș\w0酂!),u00 牃aaAHY<@Pua?_8Ht?eAvLQh `4TH̳z, Gw Cii~O* n! V)uE4*tOPBB AƄ"!gg ?'3"?hʋVS두3]߿n4L z'4~ce"RO*< 8s*FHkTրHńEe;f1%#+̈L'zG^WI8LO˒#g9{ 9CXo?yWAQbq.(9h-oµ2*I6^L&! ~ˋ}j,x%dbMv=AOҜkUGDfs, C(]bk_0E H9Qaޡ)k@TCBmw0~͓0 MR֫)^#uk̪ls!q7AB^]:YB'Gr CNV >r#J^}_1lu\ӹ[ѱ?iد_$>|/g7ЇVMl _?h.!%FjΥUo q-v ƒ45. H^9H@OIse^NRK݀# kwQW0:>kxq\Rghz}o=Е~ϒ7t+qb4ΡgF%?vIȅkBRIaqS';L\GelS387]u{+3É.-Bŝ/oFn'5/yf=..v-/6̚6+5aŃPe&?}_&IE7$ٖi%^c0ȇ:sAgޭNv0Vh?ЕX2&˜4=/v.鴪ŵI{)IBbzUDlf?( 7d(G!LТO!/f[2֙$T#<Աى 0 =*HXRZwܫ*Sq>6|PZ,dAd& =R-R?A4Pbkly2%}&&ÝV[EjbLlu L˪[){Ja m}3ޟٯyl*n]}hh1jR4{i{$$H>{pb(lP`χdϐ!fdnϱglZ[B|4 )nB}iAylf=OsMޏO&*3y)`Eq{JZ0TܠUg"* COH4F0TQ4~Q[h 7MB$ EuAE眂5m_zjy`gMU*d?3c~,(JaܧSSO #Fal_rQIp(7;gb h< r#8G G ?`r@PЀ1k E҈ZH6 BczhT$rE=|#̍ʩ;7@|zhGF /V@r' r j63(ei|߰q>4wlY 0_?==IVL)EnkEBI.J!B|#rԶgl6[@'oudyzV芋0:KE^;j`S m/>>`Of`mr\{pY/zM\/uUftV|ҔfiIB֊إBGOGi.b( G6,<ßz+HSp>KX_]I;J]%Jx8ZwBR١p}?_rw#|υԨ=>jA_߽lt}$zωl$yc̽S?cWzEP? ' ˙z^*crL1P὞XrU[涅H;6,"!qtI&"q]!R"\!noyWcR+oKT=K}>;ҹU1bha$@]+Kl#$h7jHbR_gͥ}Y0J腸*\sM^oT"NϚ,EXa1Qg-cښåi z.PLHLኗd8)yE^*rXU5&mc$ypb~tI=GT^T'XbMXH׏Ӱ#xJ +*Ccq,C_i[H5*DVU)/Ŧq &DFֿ ۍNx&6~#1Ae!䤟ґlj/2Fi>k{I=Xf7md#}f\ @Yz5*֙ *9|tנ^c|+)*LWҽXF51o4oZVx?<㊓\@Z Cjensx6i>ޥ~.+oӎyڈ޲'3J>gKǖ`ug۳wTww_rhbDBOplDFIj^CA։w &8U+Ŗ<8_~ZF .e HCJxwY4,}9u bȶc>-ⱾJm8/ j; w[%+_En6~e}F5roNKM;G85DK[2Ú'4V.I^bLt5JPǃ]([S?PӨ{@vѨ+WŢOl2Rok"cNz\)[P*6œUGņ󲙐'mwNhumե߮:~X[_n(/(nR_㼗U}C3]s{165U:alFRdwG]s:5~lܺ/TJ`G]*3haїWUL 7xmvdߦ`Ѭ591]`F>H94l][Yri .q^V( Й62DryY실k-{҄-IׂԮB.~{!MK`P]UH冤tt!ǵ5BzfZzgk$ut+-Ma7jB.dmrؐ޴_p:o Grё$fؔT _d\<7PE#Ivƫ.W^k?Y"j֋׌8AU9H/=p)ig#Jo%dv.g6*vR{/!R ͈=JYs+}xG#?oF_a9_zZxέޠ]vKW|}Wk"ۃ0[RQs+ս.۹^ّ)ʯ:_>Zkv;z^y)+d~zP Sy'4',8- XZ{{?E>C]} Lx}U:L7bm}1_4V؎zoy LwV 'JyYݥՊ꡸Scنs]waP/!{[{SˮҘiʾaZ+w%:.'Nů@*JJ_{ɐY{H=XcO%"-[l桗 vO+^HT~_.PKe}:c&?ei}EpטּGs^p>[6)r5ܹ[K+J5;UyMdFneQ \;[=R 5貂[ pCZtf} <\Ob56#,Ȋt~+}a& Ԯ /0߻T/LdNy3=)^l&k>rj!mY: 9Ʉ{^%CO;,L7 MPx )!~pNyk^^n-9Ơo[+H3" v[HLxmA EiOݛIWydib[ӪE9OU`Ә6ˡ+Z<6XԉUwS~Y n6 jF~`[I²S1ICo^V|v hDpQy N7׼]"HEQr5-NєZO r٫HCa #B=UbnhK uR=,s7rdݯgg p+RcxAO "(3{\& DqYvM^4~ 8eDgfZ;ZW6Ku, 3 eyAʍ-,G^%;~=yCx}އȭ[et Գ` 2(J rxx~#I~EȰʚ;ʏ LR,*uL_ĺZf:"倅ZwBRʤH_+1orw][ npPvҐnyŗ6hB7it䀕\W<5_ɩcCӦͰu2'2`[}G=7fte| Qm"]gs.+^M!6 PQ}C N/]E'6%_fXagBXZhYTڇ3),"xhrsÚ,yx1 氁1cJ,w"#o1^⪱k??"`/r[s9n/Yؾf2u D\#MBy]5]F5 g>42W ,"C>D7r*HOuZ:vU|EAclI0|›) !m! NsND%t4-٢X|mߜ@Kd=۔?&s>;߳An(=W8$-u?6gV$7vsLjl X'V#?9s4@q;+Iݗo(HbK9q/C 0#?[P6sv.+MK-o6TDZ&v7ȂfHb-ܪufޚք2q‰Od6G*|@ #%e>욵;Ú1T̎v@yRXNW]XORZ }A}5 {0pB yQ dXZ6d~WnQI}>|e5꺅{j#eJ<{mQD꭛Zx}o8}T/7&.ĎX=.|XC͠ P U6_0ᇼі #Ou-B"E8jWX3XU]oh֧'g[de}#(_@@⏽eIG~݀Pݣ`vZ0Tf"7|iWFsY{l¢@[m-mY^9J:oB%/xމr!.<Ί1^jL奡N^y_P >}.ɦ̣U8ޔ[-`ruqN+9ڈ%ƺ2U"ZQ"!YFu^|AM#Cz>&Z{1={ї0^8lM6z Sushb~Q7xkj k]Ow#?iZ"_~l7;{u0 ÁdAޒf8.xPG.?Yw*ۦNp:Y^\>jr&;yDv,$R'T\Z^00¾oGU-_n2kl3ˬHZ1izI>4zQz8Ve}}5ғҶT>iy % ">Ӑ^l^&gp/~+3JrJx1.*Q=v:JAzWے}HL~\ (#L M$ KQFmު]{SQ5RSeG  K]-֊3XI\*=HuT6R lv "R H H7HwK#- )HRR"҈l}snϾy1<:k}ֺV̹fSġa bM;jfD iܛG6#uGdZq(&h{}iahZѓK 9A>OD>YMPlI|ʍPJ \qfCO9IHO1_:XN:wYf5S\(#HW?%i߷fCLWNqlV]M]/:Yj3^Xԥr42ٟA8OirSKȐSɖ!M MeD}icK]{48đsԲLGNn{V1nKֹB6Eˣ8'LtbDy܈x W7xstjBztU6.7?[[S^[Qwl53I5woL??N<(w{^UNՃ{in'Wx!d?1| o\`3֍ D4K/#D 2;]a0~y!({JPdBԧ6 ' ;C8-92\ ]mt~Q3[aKf{==c7~X@bZID@z@ſ17G/αrEHgZ:d 0j+NLhS(~PS90'*u7 mgvܒ&ۭX_mOBe/ޒ1}LQzg/HUI>I )RaM} ~Q5b\K RGDG}+W3+m# =nQf[^Qgn6LJ/ Ofllo<įkdW~B v/e{1 0tqa+L"^ddq2e'G 6dPj4Dڰ0wdd4~nf2G6 `7Fhz-J ׹!~ =AO`fxԈDEN'3⻐]ĺBۿ>Lj$R|m۴Kls3ׅ `SRBf^ LWHrivQ)I9+{TScK vXk YipBn}p}W.E%R=]/<(vgfQziNL//c:6XT+fˤg^4˼\U{sWQ\-EU@bXr%2Fm)pk,wۏ5-o yfGѵ6VrOA.jwXD=g;$D\0VUxEj!]#*Y ❽8%g9ӟ7ﾖr.q[@Q%)$2sC&VjN̮z,1> *m|Jpy0+yOxܺn|Pvm58FϨ+ HgJ%,|W[TBUSj] To}M p68:;@E0K`g]#@+eavPNaB4 ฬCp0 B(&8CpqNpĿBy0lcw\8 cU1uU!g|y0 (Aʂ` i`.0 P\EPb :cv%p&# nsGM<lj#EwK&Y~#\i9{Lxb`P#ޯ@;{q\{gA9~gn#uABKf#) YtzQT9QV BQĦڵU`#j5#'G{FJ*"$v_tSsG7~A*K[mu "M2,t[to Rvlqu~}YWlM^ G}Mja`.c-{^PtS| xG%tI-sĴ(1~'S8Y~Jmo|)#1shk+(\unU!>ࢣ~KrH(5+PrU+|e`x\]_Pjz)ȻA[yd B)ό.6 0<Թw#"f:)^$tOXP{)Xx=^0<3ϧB;VZM݄N^݊ -*"*撜r{IQTXYF6N+/-Rn2aQ?&K5v[vNm;+͈H#!]PjBTPA&+xoJLҟ+?s>:`S#t'xˈ4"̵FyTHl1`ϼ|Roč6ÞwQȨZ%84޳[b{\4 a>"j.V$? .? t:kX2! ^c(TVKfI>zۣ!ĶF\&(1쪢IVBOˋO.֕ffZ\q|>b;}sdmR!i_7>.2y$3vdV$hwX 7CYEELߍ@WŤU]A%-pjstXK iEV'wgh\~fT/[~IR˛y* f~s๏αH&f&gZ4`l\)M`~Њ"CVqnr;)_ĩGd&r[ԛ .H_2H:Vv 4I^es+)_SJus3ATYvwG^=dS6}|¶- ،ѭi 2|Q."K )|DSLدzCAy9V: o{ RZFWJ[oZL1ТL{*GDfaʹm9 ?©t_|\,_/Vٿ6H[Y=d>nPujK P֓/OPɌ2~ƻPڡCJbœζyd#қZ^Nu6ܥ:2]CYK60}=k\\u{ptd;BYy' 3x/*sXi8Wªc5&ZP5BGf?e$'G.}W2"$|`u8k' ywYHkڲ.5?_2(/vjQ~EX9ӉLZJD!FvޤDcI#{e[Yi·L6~3i=z:S/jG'&%G(mދhǿ4%cCvΏ_߽6SC,/>/B;ռVșuf86aivhsJ x[ Nz^mrӷBdѹZD8n\Xd$.[wU; ^ȵm;s|V vs3'G!D `9 =q ZWL=o]kG+Gc'ox~lǭjSP;t"bW; >rZn/RncԾW'L1Օ l릵/Iqh_٧ |$0Yz}| , ~ls;ѫq8:|‡ȖWGj*|:mn#0޹Ϧ:0x.\5㶪 d^]6@c da!Q!".Qh4kڽK%.˜J[5xv(C3ҔW $wQz>َIWUyx k[~p5fRL/鏥l~:#g{:Wt8n+_eBdA5+b-ӗ n@YoxH fBx; L'c>*>=/ 3E Ff~Rt{+Q75XnTbyZK=l#-nOև["ygTͤXMjm-.XG v98'<۰M#+#e2w'>K(#+JRk _?h5,5s&D-{"ݥS+]ix8v;KCR,0sfRVpjRgBG">Yܶ)vު(H8u]%eyp~Ӓt$!!QIe+7m騕|S#t63s?5x4}F) `^@QuHA~zv(]b`)2^/;ylؿI xo6,mX|GN1opp <<@`N^Ć?pzvPB@V040Y.p K F$8l[F`7$?ZP <Ab+ 97I;8.K`L(q(N_ӒCb_3H_")qRF ``Ę%eŀX¸bGar80ll DzNDiQ`{邶$ad= <7~8΢Z/g$| 4J'k&G- (ChCvvj;}}>3spI3Ւ6\;ILtqNMxFy}xp)4? [iW2yz~ᛁW >%yͲG><طs+A^ur3Mn}$\Kw!y_ {J?[Ɛiz)KF X\)k8ӚҪԬQS'2+{32]>yXx8T{h]:Er{Gg7;_>//PHE=uB.rE$9Bd{v1Vv* O?^L?:(į<T'rNX9/* i9ʨ6Ɗ>-(~ɛE5tȘ$)j_Vf墚 W+ȍE0m]TNg饈Jn/љ5|Pp᲍!4x'29byQ|*:`\?N0f./zmQbk{y7}62jqtR(w\RUhԸiEutT͒S{6"繙Jmmx42J}_^d{P+w~\aI;]vuGEvw{ U+iU;o_YV!p8TZ[(_-Hue:4WtYlֽ&W-f`{ɷ_?Y-ӮX7ҫ. ft?0 Vԕ/dki~$y;`=5K !%Qި0+5]Jm%7i;Uu/D@/wϜ3`gL`H\ 8 ( (* }]+fƆ:oh;_EϬ]LF.0 ;0:Ҡ˩A kKUV38Σ_o{`HG1@r]Z?XIѹ.*c@`GX !@F 夀QS0A*B@`\xvlA0y@`\Wblи ;z`JZ|vFA8 FaN<0:.<]{x0ڣAP! +l=6<.=_c GsA~Fmha ŸAp<BAK Zgj )'HLlUŸz[J 4a_K2s_-T*qDSl)1?9Q-XK6"|NI`brnc9 Bޮc?t1=CpnwӕuMC+3T)w,!L`C=8Oپq^Qk?t{~ Fm›#=hַ 7vP&D݌LaHfEh"G:`/Eg 䖿Mg<:aQ\k!jLffYD+CĖf$`=|?Eor];=J e L?`aR*NuIu4w%I:53y6+3msqbaWf}KIET< 7bV'WcfIINmpF1cP@%{{n|Z6)/{,~;IT[OH[kF˯B!b}Y&U1e+.^]TfӞr7>9dMǥJUCa3~8s-ds SkF-3^eWuCTPCttb`VĀخP~Efa.H "I~ohgȈ D6v%&O5ekAm/f,wtt0Ѱ]cz=%}! ijoL9#֍"BIC:ߢ 1&//Bf?_P:K0xwM%b3]r+#MHkfj{mb/N1讞@Y/pl7iq 2ӊ}Ǒr[GDߜِ)Zw1lV2S⸖g=9n{>03cI&'ӣ7)nӝzI ͤkEoS@0xZ`I]EBУ}ڴMC>Bv`K'R$7ex/Ovt<|@s)ڮ04e59qa 2IU (7Dg&w[{t~MLYgLuj4lor1SFWyW>ϵ2pQ3B6d)tuTx͓ͧTy"z ɨG6 }#>dz%_:g_ )r/}10N[a+|E(&wo^tǣ>Iz;CX*?8-S_i8wd>k2b_lXLK .+Ԧǣl7Gv:v$>4ݮxO|C}ZA%Sw+OI a+7 D=߳#_o[dW< xuo`GpmΦB%klv_؞=g[8~Ft 6Wwt Wopu 5`\gr#ohЙ >H}MLO (-dAaX[GG* g~ p!`ʂ#(#n{88  P?!@.@0\X CHLc@0@gUl g>:@LCJ[0Oac-|0lraP$!#i :O4. b"= P+ Ag0} X;) þdg7 x:; N]a$ . xAbJ|`ñ eбTLi 8z g?8mW0b*z09 zY`N0v1vg_ĆG{ )Džybd`"t(:+ #R Gw+aAq=ZoS q*c̨su\:W#]u|al2KҾ9J  rVPή[tLV7*c[SQ>@^?ȸl3V_d\L.llLaK2AHk)co[f /}(c j~t_ Tٺ6a\uT9iu0 mTBTeE7Ya:q/ӓ~4_歀B3LH0igLpѦH7(as|W%"SL\$Pq8g#l:iԹ.'=Ma{ZwSVݣt!a J|Wh *~PRWBxTށBjc&cm,o5=* _iM}^O@pgf[|O[hm e0o*hW/Lp-OeP꫹>[M!^}RݻgQh1TX6nxQ7EʀWZsW:g<*!PAlPh RUX-6VqP^=O(%mh>c͍^u'v*{]xɸɆ* 7]T\O`CBuBFl! $Za=,B'7޻| 7i'_ 8)xźjWJ qi5)Z_)+5@&x䉆62x_/;qpjMH>2khG ŐfFʕo'] qPqD=_CC/mH=rU:I+^! +5򲸯o.8~VMQacܮ =kIuhCg$ɷ= 2Y7Z]N*2Pt6">L8;<#YSc2ۂ{eּ/oV=mZ`y $E!!h~P$] _a&Z5FH\^wt]@PH5*I^#KZق2}VQN ͠E7[ZTw> wQ_#qˌ0dZ+\=KO5DMSO6F Id?<R>J$z=%"7Ճ Sx+GW]T74<Ϣ$lgG3S҇j˯ VӞ ~mԬf׬=:f'Z@_bN+ -缑;$v,Ɣ:~G/Zs7z%摟(B?_)z߃* 5I٫c8;=ܒ&4XD(8~#*."yT‰$!z~KO=WO5##2XG~ &8~fa_7ipZӷ_37`thO;8.Egvax8680DAK3 ; am+k.OxV-J yhW?qa`JKR <#Mp;πo??iqٚC` !!pAв2 ڃϺr¥30Fߠ. ņz>cWC @\v[t, &ca-+@U(#Eѥʶ?LX'R2&ĴSlrV>/z#롳sΡjGk wx}E@w܆]{#LLswN]q`zϕT`# !퓐3knq4$@dI)*z@ë=wAz4M6_y>mEf_H~ydms+ccZʗ+;3MuD9G[W0rc_`pĬ5@mQy7׊T:^Jt3{nV-7rLߜiUUV Sٜ1ۨUEJiڮsZ#T^tvtp$`,kFG?}*vgstͻY“_ ]Bٞ݀j8|cА=W\PLM? ^O> ^{JHk ښh3uTHw뽱?lfN<߼T%n6#kiuڹ8 KۍxԎ@<& J8@4߳S3qjRhǒM4:éic7ۗWz3(`R4M߄DmYNV%01+ȒHomܵ4Wuu^<i֣7&+):JJg#z -SilgCs+qqt}0-gJxLWM|u| G׭fM-Dd6dkSϏؚ>drpo\&&[x3kt3OfS{{QEc5Ro^N#?Mw|1j\rU[ݟ\9ԴHU-0 IfI2KjPgM|sM0m}zEbxӌOۛ0/ϿEEғ|@/{/Ȃm=9[_^9?i2m+ N:z .ȯ$Uk[f=pIK)NTBZ)ދ͢odԌ&қ>.dZ/3߈2r^-((Fs@E bBѳlJC Juޯץ5/f1ޙ FڮL4IIpnM(5e~~,T5YLJ4="Q@eWa類LJ<b@rAǁJ QQH{H*?Ȯ|%/S&q7uh= \)0T_ծ%C0~sDn{##G2I}FI2U [WYY'W59kh 2wNHnOd2'Z]"U/Μ6^ _rx#h95F +ʽLfmY(>J{/}`|9ӳnUW$-3f8+r۟s0>؁4 * =Y;sb^ tTע ޼[8W O`bSX%  1Di _>b~mTEN5Ks>sf@U]g(_MZs?_plnf$L}\]mqF2Aj%1^OP芩+もح_f&Dv>zAHȁώb~XY<1*wðQk7#=ԂA +kBG܊/F){O5J0baIf~эz'&C8$=邉ZC=ȠEx{躆ɤ>NjSM0xV^1uQij;.f_ij|5mNαMT-3,TZή|]ŷ*c`,vՖw& Ô̾d\nL1kI{Jw7VF,6?];ff4zM-$q3ZeCRjQҡƗ>! aIHqI&T9vMC,O2Hs#{Ϲ }5ibov/C?(k83f (o5)Ĥ TҞP<1-3NQ91j1TGpAs 6Uf61y٢t]$liIR0TGXMuzȳfrSSk/{"E%d5mK6$D<ꎏz\C줢LA{;-`mdfV)sIfȐ] 沟}:Cxrtdz_7ӿ{#-n~f>1< Aauy0Z :3{W?0 3p82j(LQS`։Т0lx8NͣSG0qw8r;:W @ÐP)'4ZCv#r~Fm7] Dv?aҢS)u*۷6tb,HfѕHz7LMd@c$tVǨ}r#anx4nWe 8 8쫙{*'sJEs^<֢ZCA?&ذ0EeZ=TrCm u)ò{wZ*4B_] {,3GzͨBYIl@% <ܚ?vcGcoۣUDLB-BkAmP%isuE\hFE;%2lutE^s k2䤺Es֨r|e;1%g'^A$؇}RW ^";Pi|u.%tvm.M[}^ys\!LOy} 8>ԕ꼂ۻB[awS}9i=9mQrwM:gHUiMZ*tG5bZ2NK)]yS9&;P^D_4nC[?'vYf/)WTd=?QhKO߸!)M?81IC.929I};4UC%HVNTP E\_Nfi8t`vgvhg&ޫfR"Ǚs ]4ʩ]&UFԍb?(`RS~&[JQS֣$yNQoK_]!;l yznsKlb0ҫͻjej@-3.8w|:~һ4xk*$Z#S>thSX876Ma@*ؑ67cq.xP l7If1m:J!ȧid"Rg;0!򞜓n|^ՙ ه(UO֡a[:ٮL~b0jl/Jʺ|n!sZTey5aKI2i%$I?{s|_<|H<ůf-,;DTϧWLƩQ+;;ܻ[8Id1ۭȧRRQ"\_]y ta6k6dŴ?0NEzVYB~ò\[E.! gE9'zj!Ko|32[UQAu5¹LJuw(:g?@ʏ3.Rl!_,5K#Aj?gb n}?x0sq >ɡ[p^s,%S.KO/_\/ݕ(M `un& {jAɤwz:r3%{O!crrl0<-cV?V_kZ#]ӊ O?0a\I3$ CP( L?0v'Gy(ֱPOԦ<a #su1%Y0Gbo @yP cz̃Bpwb< / P$GAԘˆH`(iPZ8`$ ѥ1V# D~ _41VDbF"q=`x.C Fw ڡ 0YG@C~VtCa:vU3+M'l Q0 <(:Ac?kl @ + ; q3`B>ɟw6k $g}ͣulzhF8 q C_Y0".%Qb6lF2uL# !yju&(~?zwVRM;͏`}r3oqVj$^HӜuEXlhNiVdkޒZxй:RjKI|Q#d~XANB#Lݽ|Z7b7^&(X ra:Z3&I:is9&Kxs٨֟g , z'(NT0}_w2z:Gk#dA}H}b]U΍Pl'e%Sz;<9ЩytI[Ll]$,Dt?y(l+_B m >P|m ,7O;v^(O]eqc ˂tNSH.i]f;~ j󘿖XpV0U4Is=撢Yxg5qzQ\%Zy}Z{ Jdot**_Ru4uUEW b,.g Zz@tu[qU|~P=vR|zbq۳Kuc"JՄ _ "KRO袆a@ǘ؜Uixr)_8r~{>w8!mj1_f #‡Ql}ߔYzer <Y < SM'뾛qܧ$7mm</U1.9(34?VM{7df),|"Z;:2گP#_r"<¸3!(i{^2X# @ͦ ES%ª LfT>t~ ֎NӼdL-E95&ESݪbt^TaUЭLNq'[Rի@[]Xlj\<I:n$qAM>!4]y'r#&42C;nL_4K5OjR-N*]r0[I4IQhO3 ktlzo=,hkO!gr|A96A\̟GCbY}3ߎ|RsHb[`6ӭ84;1=?ylOHei-7A9^H]QSyyCk v?yטwg_e 3Ozcbo0?78Zmu<] Ea2=oxtvf0ބ06 P$:GήX℞ LvI@Ϭc&ψaw (&ʟ!o~.5(w)E xXW `0.Y `-F{r}?AhHL+zPQ CQ acg[@c(ghV@`=Vޡ C&<+Ѓ<[XXw'D{R$p#y6 fU[+qQh98'!^ }6u\HBׇbگ Jξ4=;- иp]4IA+R-?"z09O'4MVa wrxm\1lf!+j*6'rnLN֘QKSge;G ؎n?uW!}'}O/y!H3r'|߅=$8uZ" /FƼ?:~t9jkε-X1S*q`ҍ@d)0a?x\+>1)yU{g)mSkkFpN:߰߫xHɗI\a!% /gD0I[+qcuj"tջqu5Π!Q+Ĥ+%c ZGY}~,uKQE1ɿnm19]?}k{Đ3iudgoJO[),H_>1mQӆU\׾Р0Z5Yr]h`Vi^X[ aL\׋ɧ&- CsU qK5~%/ZVݡToj#%dH']gᾣC֦YjW/$Y6:!UW "I+}nzhZzbٽ6:qLӉ4+s S.CC}!'a,FҮ|QSejrKcJ<%28"ˠye2\tHm 7g ؙO? }Ś⒛{-3xg?;god(RJI dW0|rK`=~}iý{e2ٵ $yϠ,|7r}V~"i n5-n!'j{ q`[M9D'` w5o 덥MWl|oH~kS#X|[<9oJ-?zbE7?h/{%>0Xwi'†LN1&8G@薎䓃$Q+T>G :`-g=(Ok? #cj Gx#cops -)8cʎ7<r`ƌP, 3&oc}G cJ3/?#ѩC#0pmJ#9;#o@hiLp. adЉ 0ȿY @!4~os(@`/@Li.gD0NGc8 d= i>!p .m F8. xH pS0Ơ=8)ϵW~nf_G%DXLDžzfRfɷYq\~ƹ.?HC+wZϜ}~{^]jE4heHSǿvs, es;-X\moUXNp{/}-ҼwMݛ~q>ɷ8=6t?^6V5r.%la׆ µ>JRYx>o uo꩓WV̪p("nGLQSїo=<{ed*J_#5|dТLMۤ*CÛR.D_<9NE7?M@O> ~ݒec-w+Z][GEY08i `8X=}:ީذER[;J2jJUAlT|4x/?ڳJ$!͑Ru;Ĩ-r l8zC]ϝ\b[M'j)0~ }۴cxö\S/ygrϕ2V&Zâcw>_0F}sJa 5 2}.(>g,=Neb3m\ydJG(WmOzv8hk*$?<ܣ)yΙ;x=gMBG^`Vm(j,~"OlϤsIyOwѕl[ٷHt˯|"/'/#xjr=w v{~<~PC\ui0$ø'#j/'ȼח]_Q>;aՍ$̖VHlbYnܬQ"lBta:Qq<,^;b{NJL^PH֑(/oE@e$UE</wҸ ^In;V]į8!Z'bt#L *ã9f׺D!rNl[۶[!U0#,ů; r3կuY:ݗkԗmeR ٹO =wڷ<(B2Ϻ\2ɝb;ץ449 ]理 ےtVJz&1 5zO ό+J qYR[2Xm0Iy=, P*He~He(щCVD8{H;莰ӊqzcnOjוh{\˖Uf8W9g =6a{Z\][)ȶ9|mᡩHVI[6f 8[!z=|j_ʙ\rv]kSWl_Rwclۧ$#t1?49j,q*| WW QhF)G!W>X(\Ŀp#.$@#V tqs\iz !1 'YOy4^rJ];u nhYLA<`.0^z5>Ȑmnŝd7k~o40ɩ ^7‹Xyx8|/B+kdڤX*+]M㌬ >S%$.rW%`te'\&]%\:r K{TKRo:)7P f|v6 Ubɟ9A?+ b͆6٧K&KS>c|&8~ή/QHf!3hsI(IX:sۨe/~XJru_{Z@tOnSU,jSƖ4(F ѫ~!B_o:) \ Ie d\N3n\U(͊Vs|QpaMouN!Cсo—Z7vj R-}뙁D;#^>oԍϖI7-?;XoVT#j5?)b GywwE/S{'ڴ˦5ֶe~6H5tV|O~UKBJX1Ō64946$rhcGu nVQ3ݤ &;je6Ya“kiG'eM_7g:~ Zpd~&brxvAZ5z9%cG61a/RU,[uw0jO;yFy/m[G^.qI8$ɍiO[B'1{.f< f$u`7Tf`ۿY{ۉi mڕfie (r8 MbTR##v?HxSFa9:'*W_4+sS᳏1!g~qByE4cWJ=:e zIR9K-b_M$θ9W<4!:r"0/F&ptA )}fs|W jP7.9•DCy~oA>ZFXNOr9k"~oJ:?uf4ؓ(;Ux~hs-"8Gi' 4}߰qYTU%+a.oī9֏rn\$#ZS 5=  ߀*8:ω)o}u1yح-9s$QWW$~ߢ EkܓE?m,aƧ>KlQ/˞֜$57/UЩّ2Vt%6OTwVĽߣ V VLw )*|hYӕ_Sul͟bWIclGIysyZo bF8| >? >u8qӔ34?r^P*oG\#%zBgDJcn0b y}栩3ZQ2]ܓm>4ɬ_6=M$zTRvwh|n//!AΈ5 Yl9zgR'+m|H5?;fn 00 kD7ztm;ܸ(3rV$R/l WX]eFJ#`9&ҖGu?27QP'd'=ߌ]_0[((f$lSg>紑@ŜLnD_˞,a$ҟ/BW9JDg1 'tfO1?*ΥQ4^J(%0.ܘB\ 2D@]sxB7&Hλ/j^׈eI#S4Ke^ ++{z'Am6)t#mLi6{Y)O =ݧ&,xcMhJDޙ% )YKPyMx"]y']|0#fbh5I`c&l@cC3ؤ(ebIwHh " m21R1(wQ]4iB.cv1'ǯ跞(ȓ|t/(t~be6f^H6RaY tl%q5Gg%j|P3c $ǧ܎޳np$4N[yb擸26ଝQO7ǣklxϢ،*~QhSحF7F/m  \/tlC2U9>; ЂԟQ>4 it >}ʵXaP`43|T#`r^*9[T.ߜ: cXuh+=v,0t!nKn 5֕N=YV#cV,F;72uI?lO{;"n$ 6.ZvBHPPz`e"/X\L$.P @R!dcO(p促y6P? r¡(†P( ƆB`CpzX&QX gf H;+9d,x 8QIaD+8 +h:VF zQ ,pC!`hp! ӱ <[uN`T"!(촃iplxC08Cbb +y$Zb匽+~՟ٱX(w2?@ă"AtAB,x٦0;zS|8zgG"X8qlA1v+H0ZCvᬅqh~b^@.1bñS@/Aљ%R@\vL(lBaEtJ8_A =]:3  ˜c &ĜDaB{>&U#+ 7Govq(khN#Yk G;ߤ\9SSȸݍ\ɵtЕ-p9~~?Y[؛~V7?NJb|PFFXe#mBެ˦1g:MN7߇xH ]b{v:^ ?=Ĺ#n-^ȧH0ዠ0JS0Ӥ /{(p+[yIn7hP^/:OZ.k6QtK؇Ñ}6L>ޝQn n$nu#Y97edž/eɘ|/'N0ɟV;U}Z QChĒ-[&7{[eSNBxgFtDgGj{\nw!PjjywCB@7Og֗sǷ8_yx \oUIh[\lӷ_ܲlzEԅ5VY>g#Iw)>;;~nyC{ׇX+n C'' ]ittWoGfqc*w§!ϱ[TΩXo$|9^ +/a0z}Hdde#wC~9˕I=[{S7+{]g(5>q}xweO4yV ɨ(fqDž%3BW_m^'Qbx kCJH{dzm;=1ZP"_RंX^!危o }1(=~Qknt }+B:ST!qE'ͪ jOo㘝:Xw@:BI/[7/y0t&8 8ZSi8Lh8䯪5!8CdcCIkh8Z h M8?0u:q1CHpL"GMA`YqYm-#jJI& eNv-`|{L5KP\ PiP.t6sp8 by_NCh?YMWkݥ pTMݧo.x mgSE?cu 18y(Kό|h_hu,XPr-`Hao|aѲD+VPr`=phP62yjQ&뵟6()#EEdOfiLvL4ԟͤ3EKu+?{N3`cvZGJ hi^УP"IWnNg)e>w覾|9l&CԛMZzod->9 Y&B|LUێ˃gCۈ75vj<9Hut6²!FO(14h$E)eU+ wpZjF RUujUZ7ڏKzw/|T8XyϬ؂ ybN.6oӵq94\Q\H=(̎JӔ\RE)ᯒQ7K)6;6^`&'}Hӵ(f V}ͷ'!Z7ֻMœeFWuI?şeN )ЀFݴ$VywqɎI>na;-ÉnsWNmvy+o*Bty')aD 'T/u>ӷ2S\#_+gF2d&eTxjk߳+4&k8!0b,|4ɝ`1ʓ6fouԖ֢F?is̍d̚!~/y|x Iqדmq$y*$ngiRrEZAe0A]q^'@R@Ӷfx!ծ?Ty/Եe)R틄:tecNTCI4!+ JgsbjouSIkt"UsBCIW7s׽ouWm>_s]Gslħzza(O=Ae^yHlcfPz[ٶeqk&!ckJSENK#V5C\j=_u˅1u +FYP?Lc\!kΊ8 K?<:Ö;m%[Sqʕagg_șX^n1k8.Mfﻮ="*\HT=Qmx`|a#7ɚ3,}#i Iׇ7?i*"X}g{{kFж8!gG+W<> / h߳oyTƗ-JtsVȒ6s+U Mcu'\qt<]כo+XK~ 8eo|CZ-W|`H< Z@K%[$wJ{avYZ 1[72nȉ N*0Z$q;(*TNg"uNi.DR8<6P&,Wܟ$yQ~PR*._-ŧ+3 ?\\!'ct\noa$*:GEP0 Ut/JF=J*ZM2xqgH<SlLnKM⇓l=ѷ;! .6yؓO4pcMy)}7/J[/kQ|rw!΄sI\ /2]TU楓M֬REh8DQMLQiD:?^乫%)rPA$+%x4> [ 6Yc7Z`Ն lp¤F8 I ZIgWP?N>G~(ab#.88 kφ @# Ņ308p\P$f5H,6.tQ cjk-3b4~F*Tv:3.~dbzH''0 !8 Z) 0 X9zĿE91.-&( K p\;xpLtP8ց}SXy>kơ`TT J;@1¸ ^L68VA@UiXi3t+PH'PG+ 0‚Ǿ؃#]`@bcΎY-GE;B@q(JE`evSl# i+@0)CXwvPgӏ˦VcܱHБ)bA(k@g<y{vKGGLar@XA?yaH [HW8GǦi2MHr[љS<':bKL~  0.@[,w"GNZO 1m/F!I Ec:|y!d3IFFzl 0lدX71L UjTmHtdnDGBFI+j#-{t۫n|1|}lqM`!#xJ-})bط|gDѷRMn3pT2mz39uq'ѳgtwVH})\%PR]8 ;=)Ԙۡf@xQsm/{7Q WWۅrYtFJN[5q a떨7U{uZ_Y.yc`` U^l^AqsY1v˝ubDz/jYMb5bKLY&UV*3򚽣R#.=i3[r G+R%>W@󦦄ozi4dYeKo6]u5O5 .ʎ9wdl2xoJ "ho~C, 5~V9#O\lfKO&m¢SC(b3IXlȾ)MHΑ>ο%&ЪF`}[O}͗+?6|}GonUw.yDaΓ@ :'gv,h[>܋[hӘw#N[]~Ȇ2"(M9l-$|zᴙomYf:*Y<:NY.GJnz:DI'r a A$iG\\uR8+۔ Du"YVrch-˔5eˌ 5>*!]Ѱ=r9`&a"5,r=qrWv};)LA2Q eEd =c; GޭQq/RUem|bOOb|#at+{|*De2=gj1.injy=!Ԏb1Fhn e.66۞vi΅bqE7JLxKǽW*ϙyc>kh4ŷZ>[ Xt_2s㼚l|Ī<&<'5;^d獙ɣ>-ƿ_,ViIUD'xR[ZCM2N;EGGkh+.h`U[_;rfs/^I;zurOZ~x z(ayvwTf$[7K^JX*A/R!~пw_ 6:4wpIK5m|Z} *G|h^NSwɒǚWL:gGv|Y/tvwi[esx(q鉇^h[~zsG?,_֥KefF*V\ߞ1CSPgcSAb܀"R ~o޸”{V 'Ox1;'h;+9ahߌMŞة^~d}ZUoxS87#u/b |̀';Na+ZBUݟak7Nt#leqqeۭ2ֱgjk5i T*r-d_Jϙrw씢n|^Ntn̗grI|I>Q,n ޼!K/\L}uw.H ~]|_bvu{wN?{8oEY+-NZ2Sy>?G#x[zo % 1(U'úm˴ '7v:׼g?#+ƬﯭPVֻ$Av9"~kaf]sy9&E5K>ʨN8;nUrQ:c~ X 4-3W-++Δ{t3F92 47K߭6ukhͯ~:ZDT\^1zI '}ly){IUዂMt#2N\{>#R/i.se;SwP1m2zUښ@zVͼ{-(]%h>2MWMMI^90FJ7qG~&rbmڂV~Q&/zuEa]'5w)< SYԴݗiCoʃ+<-[ޟ#UF۫؊~9=}{cwU[\+˼WY[GUG5FX\Rt⼨Wޠ0 XdTo,>7(lWRlPy(>5`Gn#t{&^23RcPݷ~N,4rCaվgݨ2M.霨mP\&rF -?%YO?V9L>czwEo0kܙ.\ߙ#MK<;G_k5W;6nYutStUL';{Z (]5NƸ9NfqœQPS߁ Y>zuNe[) /d׾HXkU|]ɊMjˠW,5I / d_}~voRKNPQ,Mţ͝}[U#$_̽{#ܷ. #^0b y@Y:$t#2c;lyU1N>81Xw~0;e]c.'_e=25ɗZ}le[ŲL|gʤq [J, jL;:2W{IW&ׂڹ/UY|w ϟ^8jvV>}rUiBDE]f}!iD[Q3~{˚6 T81 {dذvk(75?WjU/s5%kFdK\UF4mPrvw4C?z/Ҫl}M,Bf[PZ}%Y&$ib291hCGUN [#դUlԪ^tYp,V#?8gF={GO uTi:ӚV+nb5|fst{w-KBF >5I/w=y;r;7KcZn"Q8wiZcgq^caLpmVA V퉘!k6-O\]5}I|t}T걧8W+HV/DXKF1 2sfm\c5b5ޱ*^{U{TMˤY]f4nzlwP_M@٘x`OZL+rN*z(G1c%L^HP0&Ruە5Ҷ\F5_mʄ͕AnwDOi+/Ԫˋ_Ӧ3[DdγA4{_/>&tIhަr2=ӬGW0+O+]PUwgro w6,fkѪ:#WiOsdK/{W/G 5Hg_U6Ie-ua^Z`g/-'OrA£=׮;Fg3$떊_5nEc; OVuD-=y_'dF"ykMp4e]+[zuѪ7ՏMi,s}zk;M>4/O]\Uu12vha[fj>7UoTY=2-O~NokM[gSO)*wIx̹)W˞Cq\N/WQ@N{a$y}&_Mt-ᦧS]ٰAs6WQ>6b^w_$yӬs[X".ۧ٨qlahO*n+ 0,A[ kqHz\e\l6׏ԙ:~H!k3bghyP0`: U 'Ą _~m+n; %*V=y3uQ1v6oʫo~Bek7Osrn߉ >: r]]ޕܺp[o}2B_;קңpύwO~%kN<倹NU@ʟY4r^3NMӛtaZĦK"*"<:r+/'oIӾ䬪"ƆJy;os/>- [Zs^يV{-TIk׍w"# a%> :7L#lAI+]zټCgۮouYVzEMIUv#vO׈gIv}}L]6WW^e>EWYqo7^\Y=eᰂQꬷ+8K,0H]x!ݥaO+#ۣ]1węMqQ;S 9r|qtz'L7YT͑ۑqkNܭ|fRk oTz?~7YђjW<2/녖<"! Vυ ͜x=v~Ab e}ߏQ# J_$v}NIV|*Z1F#su)k_uwEr;F4wKg~o:=⟙=tD\jĀ=)ZC۶ BA.3 >`zl'ϝZs%g1ó'ƪ[WN&2gm۷7{Nu]KB=Yqmٝ}ߊ4^[`29\dq~}dOK q=DfEuڂ DӺ5M^h̼Sܝ{y_~lt<شAQ9an|0:i;bAuj7ɮ`Dřc<*yz÷kލy(a+/V+6t $6%&Yag7@,tjΗ>,:/P,yP& yy@cqXqrcg{4l\S4&y?Njoz^?ZMg= #Ӳ{XDUaԂ4h WzF7</37Uc[f=*?.? ^Cjn%FaQ6csGzRu63<~+3 7iS*y朂i-Gڼc)d9SgR%kĚ'Bnֱ~iG^kl'5A#zqv'A-u 2ȹ-hZ6b b+w=NFZO䍾a E(BѳE(PⳆ7GM膞ߣ#ͬ=x>I,TXOZ#x>ެM/BKt+$A lw`DO%"yV|Zj>2ӣ#M=9)`C 'HɣrJ=B5҇1zVnŞO>} tGvvNRdN=$.0 Y~yh| %u\kٝ. gH^gv[x=%O%ԏ.y([ۯ|]͘5hnZZb[Bm- :;ז绥ܽr)6l7ƿy)8zm3ju=Wj{|i-z1ȎwHT=ji1wg~ox ɑ 764Ls}ѾÒ<53iJȑUs%NslW//٬2tzviJDe]&3x<:/S3}5F/wU_\Lشcӧ&}pi}t\+?,q%.DWjHz}R:_X ^8+Cu!QGo>Fu Kz#זqxb{3Nj(/&ypzV󆁯vh6iQf|U=ӱI$M&N4^qz\iwkls s{țΨ61Ce r}Oxf!-pV#+5pY= [jk-υ;%mއ,%RR{yRَ7#2L۰o F/\^ۊ{E*[z`Իh;}?O|ǥj#ӳn12^jgOV_pT][;/E5P:cFuSN;2AdҹJ1H$r{_زAKG-kXϜn?u5 8,cRI9>IFH&|З\0O#ɞ"V amZrSLpCˍD([j3yeR_Np=]CI[kxr[RGo?e])}B5̖ |ta,n%pj@8F&tz77e޲IriE:lh`㷆:uAewKLGt}}ʛFvss?Ӻ lcG&E׻ aLꮚ6;e`J-?CUZ*ɳbpVL4zܫ5ZQj-{Itu/o'&$DhijП 䋮3$M|q흕|-3ݐIxhË5RS7'}s4,5"K?4X*~܍gne^a'I̡ W>p [LZi(:s9!s^U/Mz6>SKޒSU0uwgQ]]߻車\{+'5?5h1]KzhtFjpt Pi^so-y>E}5xz>Qk?C"}HnE?'a'^rJe`Wޯ/۶WWf^ͦ#9D|NaffHYyd.nzp1+9 .G;Q32)G TEX*\*g{BM|h1e t;sLrqq%n>8/<1u Xkݜ|۸-~o.uFX2ɨYxmg^U|m`ǓfJ7蜭hw8U:qݼ[ /Z+5U:nh8irIf܆9sl3/UhqnԸoOjmɣ+/{]Td3Q Q?2ߟ!:`~&%Wmh~jȧc_/w51inG.7/W=5fz|Ք3̾_=9["K~ϻZNG#盚o_k*3`jUn!뮚ff] |Opd\;!k7Zy1t鳺kת^WSQC?(dd}V k⇮3Hӻa C;iكjkTiNbzNji[7M< x(54ەfFVl>m䁯9J v2SY$ʡW{jPbqQ2Faڷ'U\ў.7vtQ/u]VܠUOom\Ly}=$QQK? 3g^gVz{[Lm~3bS$;m)s$I޸{k{J>ꜳ~|K~z6'$0 Jit=rnP,=SEʛw/ p w]67w]뱬1OIR5S `*QѷրRy׃^x@9*]Mls1HEEbXA45Qiھb1ӝ47WwF8׾TsZUj%ವ2#}Rys 8WطyŪ{]&9qq$Y49C^.3 ӗp<=xzR[ю#nHx*xïj +vߑ-cG)mX=貦ĆYM!g*?@JMŕ˪h櫽Ri ^:Yc.R-C'U\[Tv\h۾ /[?d►sŊ IU&|:t->'ٴ];^[J.{ї!+{m1|̖Yw}7]mJ+OroE>Sodi(ʹڪso>zo;.Ll8EFsVzrI5eZɖFxqN|L "hX%>M~']">\%\?w(o_7zB,WuUxY2P/;p.>Eߥ>]?Z>aF 7sI9Emܙ^ǦZNvLꡰpS]$ݓ2k3Ye~hG(5jO)$No.7K9["%p{uzMEZL+|c5lҔѳ6ڮ||zRlE$6efwc籧<ӨkT2|DWaQ f#0mc#1=>#{5in˅CyU=F?[u>ƨ;|#*x]sul'9#y_ஈuU#r|pzղ~Ƽ3sdCZ<peؠŭ;mCܽUЀY)7{RߨimEOjiQp\sc]W޸\=~Cȸ~;J߼Bږ3kykn'3A2GvߔM Zm$8@yYntf7/WUySXr>B;tf3+oN{rO躄9-gHq"K={Bkm`yp;։W֥ i'u/8>ic݁Bl--$FTzݬ}&E[Яwu)X+yP.UC~Lk=6l-l<&%$?V~8IgުoIP9ȑAwV9!Qh&+Ij=j~3kN1P[lǬ!}kGx^8g<|z%O~8بWqk½ 9f[^wIzCۋW4o$ ">hg 1y?F/Yz Kd^.fWvYfVN/^}7`^jz]YV=ZU7$+G_{0EBfM|6qKgMbV7'aT>dmI7׮ `T|er'z*8;z;z$ rc]rd9Yqو{d1QBˬhF],sIDȻwJPU"}$ybr}7UäַwVWLޕ2#QJL-v8an^2 [x#9X>Zmlv1^\YbKa ,ݳ,=vMڶzȑe[gH5<}<}k>nuWbЋoWi0!Wk)׿gI.d!g?.*V}¡k>x9Wjqu{#+'I8PutA[Ƃ) (^KYtm΅"]s괏ߑ3Ox^pV;9fHQ..7QS|@iql[վ2{ռDk);SD.Pz0v͵eD?eT?cqrV^ר z!jҹUNa}8"1?w׏YKO{6+Wx-%5oT{fEK^L9ܚj>/n #mֆJu[б!1W󲵥WVk*f.=`|vM!~ֺ̫e{oo\9u3Ò/̾hb WH' wn֚yϵ.:ʇ(oVX/bRUQdq©Olƍ&1x{ehK6,N/ʘ1ww 7Fkgz~~輡J/1qrC<{~R#N\/7dwoך3+C^} Uټя v4$YtXTG:]GY!`yaƮ>!Cį?RjQc9Qrhԕs /bKEoˮjqj %o}6DB_6{Ox;&͏1^4_rEw_ov:_y˃b#]Ni7[.%#F{9#;q&{umRzVE|( 6SiS/wMUdK_ٳX)2MKWge_.tn2y9HS.~OEy{ǯw^|%3TP.hU_0oR@fACy1f${ Fw ;^/cuŤ_&mѝ!\?kA>+XbCɿiȊPKi8![oĨ-Nv=ͭLtϡq/7Ĵ\op^q0{b吏 ^<6L"S7[4Ɋw_"f90nGef-gYD7oڊLnY9Tvs-mRV'ڲ^<5[ϭ{OԚ>ysqc27s^cV%67"N]U;lFZldu0u "3ykztr~+ %}to^ G|ĝj~dKg)W؄|3>jqF^j* fJl!i*f͹~~ |ٯEbS Xwvo >YNe2˧zqsظ͚Oi:]ߒ#>A -^Ǐ&t=Krp)1K .e-nzRv-»܊JG]/aq+U]`#iu޺'F= kIxlt[;#GI.v%#G#GQ`e[ ?K=:)؎8#rª1x]d[u)N .(ի8G Y ?<%l VM׃OJ;ߑDh髟x -4+=Z>}۞wyOw=i;}o1fWGCHRd]T'!%>+\=:#a7N_cEZ[SN"84gs.z2p<.uqc66۪pɕKhvٙ6\nL`SOx|2Gz cۮ \ 1HH?%ȉ*v>[81 ^<ω;VK3XٷTQAx*۰%24fT2V;˛mAmRLcc- /K^I)g`Ų瞟;]qv~^puKG{ǀ7ѼSe˅߷;,̸tr싥skm|>W|^)ɔt0_Q\Qc&5#L7^6>aD]t;ƈ1P<{biG߂ec',N68j%wy.p1UjzWX͚[^Ϯp ԼcyV989 "o45e/}XNmG+LIT_TkwU Y:U 9 i!RT]6bo ELMNkxm}1~ǿpP_שANٹZfą 2'jb[~=RVNWjF}{1\$)ب.[."pFetO_g4TEVӪZ<3,7xtꅋS],3MnjS:o“L)3?)GuK'$:>Yɷ`'7'" É'W8h6{T0jyȃmp+,jҢ3K>M(tָ3[tu8`o|g]ǑJzf+˅L񓩶yFɀVQͫ'_蓅)8[Mz+L@\.Ǟ1H}{XggeC.濖r½ǟ-~'{Uj!"N=蟏Qcgd}Iܖشߝ!tKU[rWwj۞K)fu,^gW?a&jP5>UlIzX|-|;;P}7n0eQ^ MWg^8 ᧷?ev>:Tׇc=V[=U'+"3:rEr}ud#òAG.{#.XHɸ-/U6+ߤB]ܚSpٞ /6Tf<]X|SŎ-OW 3Tw:zFqSgf*}Kqk 7⽦AXå}K*s^ziIO\[9vȰ4ԊSsrtK$H?ZaE~ߓem0"<, e_βt/MO|.e;Gase$g[r`>j'n(rf!z/+\T.^q SX.];|>5npCYņ쎞'@U8QDjqڍgnGC/9:/ (8 }O䖞fbT Vno+!(9- azC[^v>46[Ap{"58; nX:1h[^>A]ޓa۲)Op{"|׭ӡ6j|X+IףSejX"$ ?vpփw0UwdO;'ӛ%X;H⬟-'';٨G"GQ 'uSʊ-ȉNlWFكi#Ob!+r~O<#b @y=ٯl$ȿ#%exٳ}%\%m '8G_Y(`[!!;]Yʝr8AܞN.SK]n®fd]n_GqW>X:Dru{W]$2HjN%3O3hlw_RU^ٓ~|(yʑqe4'oMFoQ~RҚfٷRvז |261Sf3fγ6/;Y׼9k 2G9NK u~\֐TwIqZEKeÎ'#wZp<4\^$X_:{Զ|Z68G½rљI~ssjxQﾎs\WzuNeDžO?b|k皴^HOU m䒉j3w74{in0L XgZ}yRju٦#iAdMcv!#.\˘Elrȵ/FM0qĉeR1[.+EWJ*]6唔 :fY%uk]qK\2!⠈ִ*<"^8c |V\ǠS7ee͜3iZ؏ |Z\zjZd M4d]]6Pqsi .F:j&{6f)Q{!KOטfX{< Ͼ8*SfIA_ZַtV֗ô nλ3L|ON:ߤVo,JYo}#Y:xÄ)g*Hqkڴ4aGҲcvβ_z;Z_3 %[ׯAr|XUG6\-qA?f=79"yfό-S}>[llQW-~dѵۆ0_kI[|g#}ޮr^!bAӃgkD횿D'L(?2jơ&؄명8)Ȯ q`gR3g@8_o6b6.ͻW(/r~y &ˋmT=ek)J<6e}P1[fLUPFݥ8;K]SsaQ}ƙ i;vӹ+N(4ܸ<}`bAu".1ʶuj̩jL^N\~袤ozyYR]=1 :,oxrZ4xӹ& %Eezm ^ϝhY:t |[. ?޿X[3-Ŵ抳_F.XbF%*=}\~)OW]ǴwAVm"7nuduĶ3 peԁZsSpk^UEʈ\nRelS9NsI9~k獮گX\vf 71mpw*մj },˷na{ G=UeUmsO?\-oV^`h;Dc4TGueW<՘abĂn.5In'z×~Έyߜ@/ay9̦u gw~@3he.3tu1K{}ۊQ_ˏxڤ0V%sɹܦ .&%EoR[DG+:9z7z΅9 7FSΘ%dcdcdX1>1.?p ӘcFŭ,JZ܊YkfXU>vMqKޫJ 9Qd?^YW3d_8=T2mŵK&~OOаTS@CKm Y6| !UxןfEc.qo6Ys*~lɷٯFno^E䎞Տ~r;Roz}串[NoژtAiMɜ/%Mziwq‘YL߿YM3]N/qEӓLK yzƞyF{+ 6=/t} :׃Qq3>Gbl7}K+⎉\1޼iKM/xgHoH 8xÂ|׺U#xs?3:_{g_n&_HEzO ױuCc GVwY0Ti>7xO?ٍ!>ɘ>=<~, Cx[ޚxJp{Rn=|L PJNtx%z(}X^뎾[|%z֩n)P'0% 5(La8DO,-}'2ζ8OxO1l:$Y=Q)GG`['HnOo}bUdrG2yOxMR'`w};ZS"Y!zw(+qY!;m-3-IQ˾ {"w49\w)(%uߑ$y^I8!yOЎa|%50twn{"v5s|ۭa.$J}rGӟ~ [`5ıj v,Z&QTp#=<;F!}׎\k}B9w-#̰u~m!vٙ7Fq*g3ebN8LN>t[ x>]\3JNc?VI [s'VV,'k1[]r[('%K/L{ÛYwҗVS^wf^._y!e;-&H%g%_lrLtbq[#vtTpڲB>'%?9y(ܡK-+l;DީDtpoC57蘴Up~?Lħ5`a=68}s*:VǽDLFV_< i5I{#Ӛ5p:7e'5'-H/нzJ2A·i6_ԏwy |ANlgsn٢{#>>KkFhdvݟ}(jʎ (|Xs7v=ys>Υ|{UwY˖%6] MRQkmf?@vu}@1֚m:iM\o.w]kkwKW+.Ԗyzۧ}S \=יo/+_[}U٣ߕvaKP}l-?]}"anyH,k£wI|;ld[Mjѩo(TZ4oB%KI FPَ9kcB߽-NޒTm}]}B2?L5J]ggѭui6qD i{|sn/UiMYڷ凝{ܐ,o9}{:qrmrj jgj_rX_|M'y@J9^\;÷_`8݀WS}#>x}3ݜyCK ugC,;ߧVz1l׭&k_>K3@#_?-iY]v^T 砬n.K^j8xe3}>?ePҌXwo>Ferϲ >_/mɪϹjJVFD{Igo`QG3qZhԩg^)h(Sr x?pc7&KVzY/{λZB'ZH;gbW<܎2}r}N:/OT?AF˰~7^<4g\=܋zzq뚉Eg2ŏ^7+~Rn/x^߂NZߔ6 DI2z˺q dH_\xcX+W] E{i;Vw {rWQ66v69g}3ۢ%f86'X-|jŪ}ͳAyΟ|5={bIOonCZ/^~n7mQÏJNԨ1;?:b=me=ՌxcIE^"C?߯ērUbƋOL1T+fĠ3'\QI)ܜ{JD'<Z\}$˭|]T}?s@Ko\kHܼ|uiw M-6ы4\:dC_}l,/ٙ^5Fa޽#'x#A$Um{[/3߉=*X2mr¯Ŗm˯Yd#mImw=M^uYdsGީhA'*8]{}.ٵfsX} ͵N9{]¨N^wlZ.[['f瑼sʾZu̩ޖWwl}uta*ƹ~ΰ6xfo} />z\vX{YH}mE>JZR U4],Wb*JsD+sbb *;6{x5Nvأ&~+(:]Ӧ8_NG^\BӁ7K="Fq]*D/3ݑq6XR3޶M9f]c,~113~~2v9Y7-˴Z=#oIhiyhxwcKg3Z&M7n]y4K/k|g? Š⹇g3vYg[;HXPm'LR*,6YGĚe#=:yn~ddE9~p?Kx;3>6t9p[{aH텕+a.aqXw<9_ⱝ%=i;{ب{vWºaNcTs>Cv 9JҟeVj>} ciyO ]>Je_%+5X퉮黼Y#,[y!r %5B?MxjGتC=wzr'S`lGI'B`W؆v=wz ,?g'W|s_ eahOch**|O/ܞ`9|[hx[d/&N^2v Qg]^N >{g7{dYJ/_-گޚ]m}Is;h*IN.n*t|eIo*Ê 7-\)Dpce e܃ow@E&M8һy9*[ǫ&$տ|U9%u;okv;&/sYYޮό..|7LqghfIcE&X[ ikv54sl[X &7u+Jިs?. OZy~׼[KyPgK?G=3-(Rɢ>>Oht}Zdߞ>/*m8ŧUzژd{}2H3dp1mixMwS7}ʬ[`NUSXM[ʧ#$}}Dܧɯ9\Z)il;m|e^K*>xva}|˘Ͼ7siV˭QN^}Z#I>+3hz 2Zz4ՙ=ZDsJk*yy^%fNYwS%\ҰPmsdËdĴrB24cjEi3QʸG[dթ{b6ˎE{O-lnqrv''&5gޛvHUq+jv?$묏R5LH %-LmƯN|wfа'AE6x_v^l$:–Wnh tbʽ~aw:>l4ydFaU2H?>&pՒoE\ܶ6~+ƭx?#.3]aCy}2}1t{}5J+ϖhkhjpPcY>2DZtiܸ; 4':}zsD|nlIE>%ߔה1ìNӁΉ~ioe񐒇! )*ʿ*'&8嶫/ī7{ވuJvƀ2'K^}$ zq%(7&LF7ytPݮrnEwn D'#s&I}i0GQ'mW4:+/oIǎQgVƔ0.y~Sv -]۷[\UV6'XW\uUປ~>CU?Yn`EJy|.`4!-?#c7$곫yy;m0Ayi*qMaN6|I]EaNChL}V7Lfl'}1%m+-OlxP,wת#/ -:0mIr1Õ5Q,/zؼ i:;s]vgM qM9VWṉ7$7-;IL3xT_SLf)^(^SqE}+ o5k)Rjy#w=T|'?99X+mOTLj<+ o޿;`G[$iCA+&^05_i˰mVCb葉O.9xsV\K!{!,b,׍nWKP7{WvUvoIQ[| aiWEQ'FT^S7k.d{ {t:ƠzqWgTL x$\SNoX˞Uubu~F=mu;lQx|}Cl\60{@CNX=>Si NDHjˇ8-߻_jZT\pb۫[F:j<41.c/gb{|1)[|TU⟯8’]Yd/ξںn`~=φ rfkșYxӮwIşWBx|ɺӑ9Lݼi$;EVvj[_7V8%^vPyhŅzwVZڛXPPZxl7[?[Z6HkKGUw8ۻz09`۝3];G4փӁyşMSoLo9=caq vq sr0šzwut8QrFu$Ūk0Ǐ O#(ӕz˝j+hO;@G |)@sT9juGpt9z}ǐc1pL9fsǒcűpP#`kɎa=W>{WW{W_N+^ l9v{jǙqqs9OǛq9@N' 58ˤoC$E"ȤFcl(ܽ(9 ]\8T1?gZLWq3Fޜ\AɀO#MJ.y(kυ v;s(}:8z.UCE嘀cJ#JP .^AbKˢ;U>N%Sv^=sdUX %c!:8Q$fË w/gW{[wZ`::U9:pE(p1TTYQoNQI ɣL"t|:$J';$8쨖$LtR*CG3ŇG3Ň<SGf Lcf <"tǡG<"4(yD!# yDhюziQ#BB4!S8;b#NM h~G x" ʇ0 aa" " /c0x`ħ"H1ܐ0 Zό.+> OLC#-h +>^@[ b064$Ct >䛑I| 1 (1PKQ+x KAidsPɃiP KO 0P#BېG|F!$IЧ >>--\Cˀq2`tA7n`A1҆vC;ܡЎw;1Z!b a a aYy0<1@VD +=H?TFV) rgJxΔ3Aniه(1 cdJ *q#2f118蹎Au v^G}8Yc8 cy3ƀ÷󠣌rKn]Ѝ;#xGiP:r3tG3pI8"N.# x g Z$.hpEy g hp  6 A7hupF :=88#O4z8ZV #ۏ@+BŁGMG/@+A a4 Ґ|Zm@hSp O)8 }P"8dhEp"nE`  D6lh`Oh`Oh`Oh`Oh`A8mA H,# /uXZXZXZXZXZx!hC`chC`chC`chC`ch5`ch5a!jB @;A vA@!(b5p hKB 6A$m(I0q` cG`AtG   F~A|'3+ F nA&}M2q;qqd6#mG$IF!n>B&}M2ȇHM}É#$G>/H0~|`'!V`I0~|$?>Dg3 ƏљLJLCt&!?I0|$O>cO>cO>cO>cO>cO>cO>cO>cO>c/>c3^x@<|C<!<| ʃ)~ -|S@!~ P>O|`?!~ ~p%fQa0Shp)fj#`OwTF4h\.yBpE|= ,8,\8>ρ>IXp$!agaH;vᓰ 䓰{'! 䓐?Ip#p##ppppB  @?X\,P.(GϫSin Ӣ(S #3 J`IqF`'K* ub*چAXE?Jc0 |]*-l_/a'''nf:3 ?vGюAyBҠ!9D!>!9D!>!9D!>!9DqpQC) ) xx9'1&7 "4h4;4,a% :`|`q0>,h54, aљE! ":(ADLy7<~CDt>O0A`CD3r Y 3K?Dtfg":'Dtf)2r  ADFAxADFADf\0̂ AFcQD` :Y 3K4D`f,`% "0/D`_(#E//X_z"qY24X_(0(#cQF~!BTEy2 QCTEUQ 8XQ 8XQ 8XQ8XQ8a:q%!$S>qCF>Q8a;q2a0͔',ClĀClĀH5h DC H;ѐY!2K28DC H҆CÀ0 ]ps,d p!2 /0(8DOf, TqaR?fʃLy>F (#[1F 6b`*."B \@5Yh T5]1pQJ+HDJ,`M38fm8\NTq8 4(&"8(f"p8c.PiP?QD.pقJBA Rqt!8Dp⌦BM3 g4(" (h*QԎEaAA@eqY~# 2oQf8,G5(1A0|KQf8,G7(F@Ł" 2 pQ̼<@[f-@G@Y#4"X KmqVH@ƁU$ n*HG[85z8qf8N7Y8G@Tg "QY@$ 3 Duf@;jܢnюhG[tW!"әHb:I@Lg p QY$,@e 2 pHZz;Y$M   hJZf;B+,W 0˕}f,Wi@fVY$`/ hKZfVY$ 0%xI@+@MF1K R&mI@,e&0K R&mInM`2 [3KLR&#af)6Y$Ma2 hSL.)!)R'm I@,uЦ (FBB @CBMdFY6&ٓl m 1C0|>Ih`SH^Gy8Hwu66666666666666O+@B' !I~~~|e.MBoY&\L¹fsR3 qYj&!n3K$mf,5f"5LBfI2 YZ&!R3K$DZfi,-[eb+L!2K$Vfib+p"VE8 A!&QZ |p2V?8ABy a )L@Z ,X`+tW^4BgV{8 &X4BzD( BihJ'~[[v[Ͷ ,]Y8Cc~MsI3EBi݄.Jk&ttthȃ;`2E`*g4+BP3Qځ"zQ8]f#c"[E;p 욅>F+0Z-?BoFl86Blen pV Sإ #GCb@f vBO]~m)%.#!آ !0]!0]Y4 %@-zhكmm~^>_4:C @!˴ = 06KHPHZ m.17BJ8MHJ8GHGZp6pvn[qPO{WF@B x=}A8O\A)GIM^pҠC\twobtJX ^tr]p%p/W(R% b³ "N)x_A xWyths4 S k_<Ѣ gY#(#zQWqBS A 0&W˄)0g + T3Z/\/p7H.4虁=h/ANIZZ%Zp_@)hFv / 9Bh1ꑀA ͕@`,"$ Bs!)`BA0\%}FW 8+68+D68+(8+!8+8,pZ ibi¯h¯ь W@@B-S@7O T:͋@= 55 4 訣/UccMC ]k*KjڦFFZ:Z:BU543 Uշ04U720P5ԠUMu5~I pP\\W]KW_ TKjh=̋F榺jF̶+22 iIU͇=013T8lkx4F4W123k骛٘kP5kj[ҕv=}m#cN?ZFT>_46g}~jyR]kmK؏ļiimO=hH5Tzj)ХFHB |>P"tTM55S @45e}s 'sU}sꙪ&žCXXmhA˰0¡9U5d؈$?14ȧ 306з󮑱&o GSPT _3W02tIz 䐒a+Ɣ.jcS#uhi =L(JK]SڻL[m@;us979x@Gk>W%_l5,#]it ȟXQJR#wi$msKgktAv[?(AGh(c$H'<|gQqgL , ?ch?H>#Ph#w ({!@P#ܕ3H3GX1cX]lg}d}@7>wL-5TUiW7eI9j6uR9gD3ډnVng|fafK9:6tMYٴi7J0J X~AS/[ht*j2P5跉Ѥc(P^Fݘn>K;BW*GmSUhUV`n=2(H]UGX@<@"adM=loi|` @kNu&h-EL 6m ]us+#S ZxP3><mU4(r;^7U5i_5, .U 4ͨjtCCJ,uԩ*ӓ ~&K? cCt 1ow!78>,/Ra3jgFS@OQPGC SZX! ɩp1ZaWST/Fv~Mݔ#zFj(}c z˜0 \4T5 AĂnoZ48*1PJЎ16Ԥ`nXQvL 0O&Г~H>v*#;U\׉_Ogd TgK j3 .":eR:q~,p g{ bn[.*Lsf6#N?ߢx@d R1Gys*'@q`Np;e1l3s^ ;6m fA}l{,^,ߩxs` g: pٟ1'G` Ϛk;;P'Ͽ=!ho{X:eB;eZ%,pS))3%P,~g^ yK;T)]dBG{sSҘ :2=BN׮ci:eXgP:9yۙFՐNծk8ad:1mHZ8E˜:S/4Dl/؇ѩ?^N<rzq$s]=\/}#ϯ[.?G? ):ru[[w/gq?fn/۔yn@X9>g ((RUq,]}}m=y;zȵ}2JZvT'Gvp2w!gIz:3y)vnџWPP䘻SП@ps~SQD=ӷJ rwsK)mkj"*{G_8C|řr(4l4.,o{iٲ$K?L᰺0~o%jq>g]BWq>7Y| 9(ƐO>|P W\XPVas[hANO^ڵOojVoj ;%) {mM=O8)QQ裠(^=Ɯ0eZʊ2=V. &.LoO ޷N{ն)_>|/>t*fm[KQv".l`^}~~ح#ӃߓO=͍kA@m) lDm =-nrCuzuaV<|t8oyxm' ֝CDia7R~aõ-\6nn-176u-2nD*j}k?~Rʥ>%|*5 7dO7|*]X}aRĠ'z~C˜x߳8>CHY)ׅymb.|/za;/CXtS*m5ѯ-!dT6֑ځ>3%^-)S_0v3$nN^ c]B #<%eG LC,W\Ro^ʱ;16xaj> ޶P!B ;`#m-}` 0ߪVCrwmOJ;F֘Fcuy"xcu﫭%m7vs6U|(~/s1oa k|-0HٽF's6.1}5-޾?cGoz0̫ޑoSֱ{geԆ(G[޺tDm;X]xΙ33 >Wh/s,(2a`ЂSq3(9!8gXb9ch=T~O Yi8:hk}2 ( ܵx6ac%!+7ngzr:Fk\} 1mk6"@g;,Ƞ|cnT m sPya.^#>}oEri.so٘/Qo40qa&acυmr, cVOJ@~jWR{l=l~>f/gK, m# `ECN qsaUZ"عϷ[6f>l7(ض* m3W4Xx^1ؽoy"j_^8h~Io{-4[j}̓Ċ!~mN&uɽSE~ [WX6]ln1'u$#Vw\Jj[g&!5O[֎Ӄ>츱ęa5[8W3S?33P]أǙ\{XC-6a{'mgh!ژ¦@Bcy 8( RY'pQbmSWͶĐ1s|!l71}<琩H:$ql9bc,;aÇwM}:9l+_{_;+.Uy!=saQ^v=uo[~[kUu6\bm *:?c =ޘq"`r1׎"n g֡\s=0{-eZ[ ^XAcy`noz? F-67O}ƊFGt!?% ݰNhw0QOUq ?ip_A%Wi 6#OuNaasy~ {| F{2V`5{Š?2ڨNbcocMC vSXɼ51ҡm-lbWӐ8yH85nfnhyuc.}O@rLGNC3ޔΘ[- 궏-6 VSe{dk rLkSԦi+) #ի j}Pokή]9]c5jKW,1ȥƊc]<'EC%`y=CsxG5&q:IuXkF1@G]P&Xek7k,o(eQc{:1^ZƖ^[N1m^a)G]c5 ʃ򤬼C945?| 뙨JuJc~/T kz Hb*W,oRT!s,,.|Oh#Ḇ$Fꧺ'&:CvP+6`ǚ ˝c"'8Ȋ-za)SFQ.awƮ(\2%.e9Q{#"SC~X3L!8sO`|QaA8uADR.(0 ,8=6rvzj֣``~i SMlA^̃Ƀ0flS;(凌Qc 9;qtɞ=bGXrP3Xp|ZʍVM[y0΃~ c5- F6|!ڂG`~kAkA@kA@kAkAPOQVA] |K_`s[2j茊l_[2i] kMki7X[?)փqkj/s-hq-/GV"1س1荳L:oXq,5`>321@olC 1yc+m+Uz؎p|vs grvd1fͶ9U5|Bdc d&N<@ƨskeo1@xn/ÄXr#m)e)sGy*1ݲW k8l )Qn~#=F**Ŷ藾Kc- m Rga-G |Ϩ0:1&}cdE:]Lsc}hm8)F*&pQ1;"{^r̎|K[:X`Acmcθٺ̓ Ը/o31Ke[K4f8=y-c𚬡l\H`JFy |0ӒƁζ-C '`>C=uT"Ϩ9Ch'a C/ʶ]j67(e<1 +rۘM[֪y ݌srjȯ؞mϭ-CǴj󣶐;CΘ$SRM{>5`)X y\?ƠOC(iȩ\wKεǻ-u]f ?1G%F _\ Å8r=*2WEVKbUζٍQ9=L  1r?Ʃ{%`-)Kco!֖7vݹ;aJGND,|7їiŰ탟j-'LJr-Ɔ6Q \ /lcj /X[-U=>ɏY]&>iW} sO7Wc5g25gF,qɻz&MsCG y1^Roa70|-zĆݜ-mKgWYv;RXpړӳ]lcnO7*:Dѯ=G nM9Zl%:ȱ߃CO~KHJȱ3cvmMjw50ù`N5p g+5k.j uOVGLA'!n6 K|w\˱ L]yuyC1_1_Jn-廕z{sj`{p?i9.ƐYE,87`Ib䕎G ˞7V!r93֡D{l\P:ױ81s޲,y:Tpܮ) s,ٶGͶRѩSJ]~X!w"5<;pb_y}\wᾓn.[#w/rƈmtY= s,6Qri0/ E<ۢN7\&1oK}%uhgb@C虄tEI -!/~^=ޑ1 y___yAGM#}cqO4c2CPsDb{\G\G%ej8[l g;< Pᨫ{uN1>K9ԓ Frnbq8'7iUc_! 10pwLXpJ& Fˇ\ 4LO1!J{lG u)ăaF}D'7<~nwr^UYŧm滝w~x/j`fqlK1a\[Z㼚b+9WBl I!{A޿Nae){rO FK ۢ>T8r z]s Gcje~qy/??ag믿a]_ο/߿/1e_*ubuntu-policy/debconf-spec.ubuntu.desc0000644000175000017500000000101411061226123020636 0ustar cjwatsoncjwatsonDocument: debconf-spec.ubuntu Title: Debian Configuration Management Specification Author: The Debian Policy Mailing list Abstract: This manual describes the package configuration system used by the debconf system, and defines the format of the template and config files which are used. Section: Ubuntu Format: text Files: /usr/share/doc/ubuntu-policy/debconf_specification.txt.gz Format: HTML Index: /usr/share/doc/ubuntu-policy/debconf_specification.html Files: /usr/share/doc/ubuntu-policy/debconf_specification.html ubuntu-policy/upgrading-checklist.html0000644000175000017500000010117711216714045020764 0ustar cjwatsoncjwatson Policy checklist for upgrading your packages

Policy checklist for upgrading your packages

About the checklist

The checklist below has been created to simplify the upgrading process of old packages. Note that this list is not `official'; it simply gives an indication of what has changed and whether you are likely to need to make changes to your package in light of this. If you have doubts about a certain topic, if you need more details, or if you think some other package does not comply with policy, please refer to the Policy Manual itself. All of the changes from version 3.0.0 onwards indicate which section of the Policy Manual discusses the issue: [3.4] means section 3.4. The section numbering changed when the packaging manual was incorporated into policy; the section numbers used below refer to the current version.

Here is how the check list works: Check which policy version your package complies with currently (indicated in the "Standards-Version" field of the source package). Then move upwards until the top and check which of the items on the list might concern your package. Note which sections of policy discuss this, and then check out the Policy Manual for details. If you are upgrading from Policy version < 2.5.0, it may be easier to check through the whole of policy instead of picking your way through this list.

The checklist

3.8.2.0                        Jun 2009

     * The list of archive sections has been significantly expanded.  See
       http://lists.debian.org/debian-devel-announce/2009/03/msg00010.html
       for the list of new sections and rules for how to categorize
       packages.                                                 [2.4]
     * All packages must use debconf or equivalent for user prompting,
       though essential packages or their dependencies may also fall
       back on other methods.                                    [3.9.1]
     * Legacy XFree86 servers no longer get a special exception from the
       FHS permitting /etc/X11/XF86Config-4.                     [9.1]
     * Removed obsolete dependency requirements for packages that use
       /var/mail.                                                [9.1.3]
     * Speedo fonts are now deprecated.  The X backend was disabled
       starting in lenny.                                        [11.8.5]
     * The GNU Free Documentation License version 1.3 is included in
       common-licenses and should be referenced from there.      [12.5]
     * The requirements for source package names are now explicitly
       spelled out.                                              [5.6.1]

3.8.1.0                        Mar 2009

     * Care should be taken when adding functionality to essential and
       such additions create an obligation to support that functionality
       in essential forever unless significant work is done.     [3.8]
     * Changelog files must be encoded in UTF-8.                 [4.4]
     * Tighten some format requirements for changelog files from a should
       to a must.                                                [4.4]
     * Remove alternative changelog formats.  Debian only supports one
       changelog format for the Debian Archive.                  [4.4.1]
     * New nocheck option for DEB_BUILD_OPTIONS indicating any build-time
       test suite provided by the package should not be run.     [4.9.1]
     * All control files must be encoded in UTF-8.               [5.1]
     * debian/control allows comment lines starting with # with no
       preceding whitespace.                                     [5.2]
     * Init scripts ending in .sh are not handled specially.  They are not
       sourced and are not guaranteed to be run by /bin/sh regardless of
       the #! line.  This brings Policy in line with the long-standing
       behavior of the init system in Debian.                    [9.3]
     * The start action of an init script must exit successfully and not
       start the daemon again if it's already running.           [9.3.2]
     * /var/run and /var/lock may be mounted as temporary filesystems, and
       init scripts must therefore create any necessary subdirectories
       dynamically.                                              [9.3.2]
     * /bin/sh scripts may assume that local can take multiple variable
       arguments and supports assignment.                        [10.4]
     * User mailboxes may be mode 600 and owned by the user rather than
       mode 660, owned by user, and group mail.                  [11.6]

3.8.0.0                        Jun 2008

     * The base section has been removed.  contrib and non-free have been
       removed from the section list; they are only categories.  The base
       system is now defined by priority.                        [2.4, 3.7]
     * If dpkg-source -x doesn't provide the source that will be compiled,
       a debian/rules patch target is recommended and should do whatever
       else is necessary.                                        [4.9]
     * Standardized the format of DEB_BUILD_OPTIONS.  Specified permitted
       characters for tags, required that tags be whitespace-separated,
       allowed packages to assume non-conflicting tags, and required
       unknown flags be ignored.                                 [4.9.1, 10.1]
     * Added parallel=n to the standardized DEB_BUILD_OPTIONS tags,
       indicating that a package should be built using up to n parallel
       processes if the package supports it                      [4.9.1]
     * Debian packages should not use convenience copies of code from other
       packages unless the included package is explicitly intended to be
       used that way.                                            [4.13]
     * If dpkg-source -x doesn't produce source ready for editing and
       building with dpkg-buildpackage, packages should include a
       debian/README.source file explaining how to generate the patched
       source, add a new modification, and remove an existing
       modification.  This file may also be used to document packaging a
       new upstream release and any other complexity of the Debian build
       process.                                                  [4.14]
     * The Uploaders field in debian/control may be wrapped.     [5.6.3]
     * An empty Debian revision is equivalent to a Debian revision of 0 in
       a version number.                                         [5.6.12]
     * New Homepage field for upstream web sites.                [5.6.23]
     * The Breaks field declares that this package breaks another and
       prevents installation of the breaking package unless the package
       named in Breaks is deconfigured first.  This field should not be
       used until the dpkg in Debian stable supports it.         [6.5, 6.6, 7]
     * Clarify which files should go into a shared library package, into a
       separate package, or into the -dev package.  Suggest -tools instead
       of -runtime for runtime support programs, since that naming is more
       common in Debian.                                         [8.1, 8.2]
     * Files in /etc/cron.{hourly,daily,weekly,monthly} must be
       configuration files (upgraded from should).  Mention the hourly
       directory.                                                [9.5]
     * Packages providing /etc/X11/Xresources files need not conflict with
       xbase (<< 3.3.2.3a-2), which is long-obsolete.            [11.8.6]
     * Manual pages in locale-specific directories should use either the
       legacy encoding for that directory or UTF-8.  Country names should
       not be included in locale-specific manual page directories unless
       indicating a significant difference in the language.  All
       characters in the manual page source should be representable in the
       legacy encoding for a locale even if the man page is encoded in
       UTF-8.                                                    [12.1]
     * The Apache 2.0 license is now in common-licenses and should be
       referenced rather than quoted in debian/copyright.        [12.5]
     * Packages in contrib and non-free should state in the copyright file
       that the package is not part of Debian GNU/Linux and briefly
       explain why.                                              [12.5]
     * Underscore (_) is allowed in debconf template names.      [debconf]

3.7.3.0                        Dec 2007

     * Package version numbers may contain tildes, which sort before
       anything, even the end of a part.                         [5.6.12]
     * Scripts may assume that /bin/sh supports local (at a basic level)
       and that its test builtin (if any) supports -a and -o binary
       logical operators.                                        [10.4]
     * The substitution variable ${binary:Version} should be used in place
       of ${Source-Version} for dependencies between packages of the same
       library.                                                  [8.5]
     * Substantial reorganization and renaming of sections in the Debian
       menu structure.  Packages with menu entries should be reviewed to
       see if the menu section has been renamed or if one of the new
       sections would be more appropriate.                       [menu policy]
     * The Source field in a .changes file may contain a version number
       in parentheses.                                           [5.6.1]
     * The acceptable values for the Urgency field are low, medium, high,
       critical, or emergency.                                   [5.6.17]
     * The shlibs file now allows an optional type field, indicating the
       type of package for which the line is valid.  The only currently
       supported type is udeb, used with packages for the Debian
       Installer.                                                [8.6]
     * Packages following the Debian Configuration management
       specification must allow for translation of their messages by using
       a gettext-based system such as po-debconf.                [3.9.1]
     * GFDL 1.2, GPL 3, and LGPL 3 are now in common-licenses and should
       be referenced rather than quoted in debian/copyright.     [12.5]

3.7.2.2                        Oct 2006

     * Maintainer scripts must not be world writeable (up from a
       should to a must)                                         [6.1]

3.7.2.0                        Apr 2006

     * Revert the cgi-lib change.                                [11.5]

3.7.1.0                        Apr 2006

     * It is now possible to create shared libraries without
       relocatable code (using -fPIC) in certain exceptional cases,
       provided some procedures are followed, and for creating static
       libraries with relocatable code (again, using -fPIC).
       Discussion on debian-devel@lists.debian.org, getting a rough
       consensus, and documenting it in README.Debian constitute most
       of the process.                                           [10.2]    
     * Packages should install any relevant files into the directories
       /usr/include/X11/and /usr/lib/X11/, but if they do so, they
       must  pre-depend on x11-common (>= 1:7.0.0)              [11.8.7] 

3.7.0.0                        Apr 2006

     * Packages shipping web server CGI files are expected to install
       them in /usr/lib/cgi-lib/ directories.  This location change
       perhaps should be documented in NEWS                      [11.5]
     * Web server packages should include a standard scriptAlias of
       cgi-lib to /usr/lib/cgi-lib.                              [11.5]
     * The version of FHS mandated by policy has been upped to
       2.3. There should be no changes required for most packages,
       though new top level directories /media, /srv, etc may be of
       interest.                                                 [9.1.1]
     * All fields, apart from the Uploaders field, in the control file
       are supposed to be a single logical line, which may be spread
       over multiple physical  lines (newline followed by space is
       elided).  However, any parser for the control file must allow
       the Uploaders field to be spread over multiple physical lines
       as well, to prepare for future changes.                 [ 5.1, 5.6.3 ]
     * When scripts are installed into a directory in the system
       PATH, the script name should not include an extension that
       denotes the scripting language currently used to implement it.
                                                              [ 10.4 ]
     * packages that invoke initscripts now must use invoke-rc.d to do
       so since it also pays attention to run levels and other local
       constraints.                                                [ 9.3.3.2 ]
     * We no longer use /usr/X11R6, since we have migrated away to
       using Xorg paths. This means, for one thing, fonts live in
       /usr/share/fonts/X11/ now, and /usr/X11R6 is gone.
                                                      [ 11.8.5.2, 11.8.7, etc]

3.6.2.0                        2005

     * Recommend doc-base, and not menu, for registering package documentation.
     * Run time support programs should live in subdirectories of
       /usr/lib/ or /usr/share, and preferably the shared lib is named
       the same as the package name (to avoid name collisions). [8.1]
     * It is recommended that HTTP servers provide an alias /images to
       allow packages to share image files with the web server [11.5]

3.6.1.0                    Aug 2003

     + Prompting the user should be done using debconf. Non debconf
       user prompts are now deprecated. [3.10.1]

3.6.0                      Jul 2003

     - Restructuring causing shifts in section numbers and bumping of
       the minor version number:
     + Many packaging manual appendices that were integrated into policy
       sections are now empty, and replaced with links to the Policy.
       In particular, the appendices that included the list of control
       fields were updated (new fields like Closes, Changed-By were added)
       and the list of fields for each of control, .changes and .dsc files
       is now in Policy, and they're marked mandatory, recommended or
       optional based on the current practice and the behavior of the
       deb-building tool-chain.
     + Elimination of needlessly deep section levels, primarily in the
       chapter Debian Archive, from which two new chapters were split out,
       Binary packages and Source packages. What remained was reordered
       properly, that is, some sect1s became sects etc.
     + Several sections that were redundant, crufty or simply not designed
       with any sort of vision, were rearranged according to the formula that
       everything should be either in the same place or properly interlinked.
       Some things remained split up between different chapters when they
       talked about different aspects of files: their content, their syntax,
       and their placement in the file system. In particular, see the new
       sections about changelog files.
     - Added Games/Simulation and Apps/Education to menu sub-policy
       [menu policy]
     - Debian changelogs should be UTF-8 encoded. [C.2.2]
     - shared libraries must be linked against all libraries that they
       use symbols from in the same way that binaries are. [10.2]
     - build-depends-indep need not be satisfied during clean
       target. [7.6] 

3.5.10                     May 2003

     - packages providing the x-terminal-emulator virtual package
       ought to ensure that they interpret the command line exactly
       like xterm does. [11.8.3]
     - Window managers compliant with the Window Manager Specification
       Project may add 40 points for ranking in the alternatives [11.8.4]

3.5.9.0                    Mar 2003

     - The section describing the Description: package field once again has
       full details of the long description format. [3.4.2]
     - Clarified that if a package has non-build-essential
       build-dependencies, it should have them listed in the Build-Depends
       and related fields (i.e. it's not merely optional). [4.2]
     - When asked to restart a service that isn't already running,
       the init script should start the service. [9.3.2]
     - If the purpose of a package is to provide examples, then the
       example files can be installed into /usr/share/doc/package
       (rather than /usr/share/doc/package/examples). [12.6]

3.5.8.0                    Nov 2002

     - It is no longer necessary to keep a log of changes to the upstream
       sources in the copyright file. Instead, all such changes should be
       documented in the changelog file. [12.7]
     - Build-Depends, 	Build-Conflicts,
       Build-Depends-Indep, and
       Build-Conflicts-Indep must also be satisfied when the
       clean target is called. [7.6]
     - A new Apps/Science menu section is available [menu policy]
     - debconf specification cleared up, various changes. [debconf
       policy]
     - It is no longer recommended to create symlinks from nonexistent
       manual pages to undocumented(7). Missing manual pages for programs
       are still a bug. [12.1]

3.5.7.0                    Aug 2002

     - Packages no longer have to ask permission to call MAKEDEV in
       postinst, merely notifying the user ought to be enough. [10.6]
     - cryptographic software may now be included in the main
       archive. [2.2.4]
     - task packages are no longer permitted; tasks are now created by a
       special Tasks: field in the control file. [3.9]
     - window managers that support netwm can now add 20 points when
       they add themselves as an alternative for
       /usr/bin/x-window-manager [11.8.4]
     - The default compilation options have now changed, one should
       provide debugging symbols in all cases, and optionally step
       back optimization to -O0, depending on the DEB_BUILD_OPTIONS
       environment variable. [10.1]
     - Added mention of build-arch, build-indep, etc, in describing
       the relationships with `Build-Depends', `Build-Conflicts',
       `Build-Depends-Indep', and `Build-Conflicts-Indep'. May need to
       review the new rules.  [7.6, 4.8]
     - Changed rules on how, and when, to invoke ldconfig in maintainer
       scripts. Long rationale. [8]
     - [Added the last note in 3.5.6 upgrading checklist item regarding
       build rules, please see below]

3.5.6.0                    Jul 2001

     - Emacs and TeX are no longer mandated by policy to be priority
       standard packages [2.5]
     - Programs that access docs need to do so via /usr/share/doc, and
       not via /usr/doc/ as was the policy previously [11.5]
     - Putting documentation in /usr/doc versus /usr/share/doc is now
       a ``serious'' policy violation. [12.3]
     - For web servers, one should not provide non-local access to the
       /usr/share/doc hierarchy. If one can't provide access controls for
       the http://localhost/doc/ directory, then it is preferred that one
       ask permission to expose that information during the install. [11.5]
     - There are new rules for build-indep/build-arch targets and
       there is a new Build-Depend-Indep semantic. [7]

3.5.5.0                    May 2001

     - Manpages should not rely on header information to have
       alternative manpage names available; it should only use
       symlinks or .so pages to do this [12.1]
     - [Clarified note in 3.5.3.0 upgrading checklist regarding
        examples and templates: this refers only to those examples used
        by scripts; see section 10.7.3 for the whole story]
     - Included a new section 10.9.1 describing the use of
       dpkg-statoverride; this does not have the weight of policy
     - Clarify Standards-Version: you don't need to rebuild your
       packages just to change the Standards-Version!
     - Plugins are no longer bound by all the rules of shared
       libraries [10.2]
     - X Windows related things:
       * Clarification of priority levels of X Window System related
         packages [11.8.1]
       * Rules for defining x-terminal-emulator improved [11.8.3]
       * X Font policy rewritten: you must read this if you provide
         fonts for the X Window System [11.8.5]
       * Packages must not ship /usr/X11R6/lib/X11/app-defaults/ [11.8.6]
       * X-related packages should usually use the regular FHS
         locations; imake-using packages are exempted from this [11.8.7]
       * OpenMotif linked binaries have the same rules as
         OSF/Motif-linked ones [11.8.8]

3.5.4.0                    Apr 2001

     - The system-wide mail directory is now /var/mail, no longer
       /var/spool/mail.  Any packages accessing the mail spool should
       access it via /var/mail and include a suitable Depends field;
       details in [11.6]
     - The perl policy is now part of Debian policy proper. Perl
       programs and modules should follow the current Perl policy
       [11.9; perl-policy]

3.5.3.0                    Apr 2001

     - Build-Depends arch syntax has been changed to be less
       ambiguous. This should not affect any current packages [7.1]
     - Examples and templates files for use by scripts should now live
       in /usr/share/<package> or /usr/lib/<package>, with
       symbolic links from /usr/share/doc/<package>/examples as
       needed [10.7.3]

3.5.2.0                    Feb 2001

     - X app-defaults directory has moved from
       /usr/X11R6/lib/X11/app-defaults to /etc/X11/app-defaults [11.8.6]

3.5.1.0                    Feb 2001

     - dpkg-shlibdeps now uses objdump, so shared libraries have to be
       run through dpkg-shlibdeps as well as executables [8.1]

3.5.0.0                    Jan 2001

     - Font packages for the X Window System must now declare a
       dependency on xutils (>= 4.0.2) [11.8.5]

3.2.1.1                    Jan 2001

     - Daemon startup scripts in /etc/init.d/ should not contain
       modifiable parameters; these should be moved to a file in
       /etc/default/; see [9.3.2] for details
     - Files in /usr/share/doc must not be referenced by any
       program.  If such files are needed, they must be placed in
       /usr/share/<package>/, and symbolic links created as required
       in /usr/share/doc/<package>/ [12.3]
     - Much of the packaging manual has now been imported into the
       policy document

3.2.1.0                    Aug 00

     - A package of priority standard or higher may provide two
       binaries, one compiled with support for the X Window System,
       and the other without [11.8.1]

3.2.0.0                    Aug 00

     - By default executables should not be built with the debugging
       option -g. Instead, it is recommended to support building the
       package with debugging information optionally.  Details in [10.1]
     - Policy for packages where the upstream uses HTML changelog
       files has been expanded.  In short, a plain text changelog file
       should always be generated for the upstream changes [12.8]
     - Please note that the new release of the X window system (3.2)
       shall probably need sweeping changes in policy
     - Policy for packages providing the following X-based features
       has been codified:
       - X server (virtual package xserver) [11.8.2]
       - X terminal emulator (virtual package x-terminal-emulator) [11.8.3]
       - X window manager (virtual package x-window-manager, and
         /usr/bin/x-window-manager alternative, with priority
         calculation guidelines) [11.8.4]
       - X fonts (this section has been written from scratch) [12.8.5]
       - X application defaults [11.8.6]
     - Policy for packages using the X Window System and FHS issues
       has been clarified; see [11.8.7]
     - No package may contain or make hard links to conffiles [11.7.3]
     - Noted that newer dpkg versions do not require extreme care in
       always creating the shared lib before the symlink, so the unpack
       order be correct [8]

3.1.1.0                    Nov 1999

     - Correction to semantics of architecture lists in Build-Depends
       etc.  Should not affect many packages [7.1]

3.1.0.0                    Oct 1999

     - /usr/doc/<package> has to be a symlink pointing to
       /usr/share/doc/<package>, to be maintained by postinst
       and prerm scripts.  Details are in [defunct]
     - Introduced source dependencies (Build-Depends, etc.) [7.1, 7.6]
     - /etc/rc.boot has been deprecated in favour of /etc/rcS.d.
       (Packages should not be touching this directory, but should use
       update-rc.d instead) [9.3.4]
     - update-rc.d is now the *only* allowable way of accessing the
       /etc/rc?.d/[SK]??* links.  Any scripts which manipulate them
       directly must be changed to use update-rc.d instead.  (This is
       because the file-rc package handles this information in an
       incompatible way.) [9.3.3]
     - Architecture-specific examples go in /usr/lib/<package>/examples
       with symlinks from /usr/share/doc/<package>/examples/* or from
       /usr/share/doc/<package>/examples itself [12.7]
     - Updated FHS to a 2.1 draft; this reverts /var/state to
       /var/lib [9.1.1]
     - Added MIME sub-policy document [9.7; mime-policy]
     - VISUAL is allowed as a (higher priority) alternative to EDITOR [12.4]
     - Modified liblockfile description, which affects
       mailbox-accessing programs.  Please see the policy document for
       details [11.6]
     - If a package provides a changelog in HTML format, a text-only
       version should also be included.  (Such a version may be prepared
       using lynx -dump -nolist.) [12.7]
     - Description of how to handle version numbers based on dates
       added [3.2.1]

3.0.1.0                    Jul 1999

    -  Added the clarification that the .la files are essential for the
       packages using libtool's libltdl library, in which case the
       .la files must go in the run-time library package [10.2]

3.0.0.0                    Jun 1999

    - Debian formally moves from the FSSTND to the FHS. This is a
      major change, and the implications of this move are probably
      not all known. [9.1]
    - Only 3 digits of the Standards version need be included in
      control files, though all four digits are still permitted. [4.1]
    - The location of the GPL has changed to
      /usr/share/common-licenses. This may require changing the
      copyright files to point to the correct location of the GPL and
      other major licenses [12.6]
    - Packages that use libtool to create shared libraries must
      include the .la files in the -dev packages [10.2]
    - Use logrotate to rotate log files [10.8]
    - section 5.8 has been rewritten (Programs for the X Window
      System) [now 11.8]
    - There is now an associated menu policy, in a separate document,
      that carries the full weight of Debian policy [9.6; menu-policy]
    - Programs which need to modify the files /var/run/utmp,
      /var/log/wtmp and /var/log/lastlog must be installed setgid utmp [11.3]


** Please note that section numbers below this point may not be up to date **


2.5.0.0                         Oct 1998

  Policy Manual:
    - Rearranged the manual to create a new Section 4, Files
      + Section 3.3 ("Files") was moved to Section 4. The Sections
        that  were Section 4 and Section 5 were  moved down to become
        Section 5 and Section 6.
      + What was Section 5.5 ("Log files") is now a subsection of the
        new Section 4 ("Files"), becoming section 4.8, placed after
        "Configuration files", moving the Section 4.8 ("Permissions
        and owners") to Section 4.9.  All subsections of the old
        Section 5 after 5.5  were moved down to fill in the number
        gap.
    - Modified the section about changelog files to accommodate
      upstream changelogs which were formatted as HTML/ These
      upstream changelog files should now be accessible as
      /usr/doc/package/changelog.html.gz
      + Symlinks are permissible to link the real, or upstream,
        changelog name to the Debian mandated name.
    - Clarified that HTML documentation should be present in some
      package, though not necessarily the main binary package.
    - Corrected all references to the location of the copyright
      files. The correct location is /usr/doc/package/copyright
    - Ratified the architecture specification strings to cater to the
      HURD.

2.4.1.0                         Apr 1998

  Policy Manual:
    - Updated section 3.3.5 Symbolic links:
      + symbolic links within a toplevel directory should be relative,
        symbolic links between toplevel directories should be absolute
        (cf., Policy Weekly Issue#6, topic 2)

    - Updated section 4.9 Games:
      + manpages for games should be installed in /usr/man/man6
        (cf., Policy Weekly Issue#6, topic 3)

  Packaging Manual:
    - Updated prefix of chapter 12, Shared Libraries:
      ldconfig must be called in the postinst script if the package
      installs shared libraries
      (cf., Policy Weekly Issue #6, fixes:bug#20515)

2.4.0.0                         Jan 1998

    - Updated section 3.3.4 Scripts:
      + /bin/sh may be any POSIX compatible shell
      + scripts including bashisms have to specify /bin/bash as
        interpreter
      + scripts which create files in world-writable directories
        (e.g., in /tmp) should use tempfile or mktemp for creating
        the directory

    - Updated section 3.3.5 Symbolic Links:
      + symbolic links referencing compressed files must have the same
        file extension as the referenced file

    - Updated section 3.3.6 Device files:
      + /dev/tty* serial devices should be used instead of /dev/cu*

    - Updated section 3.4.2 Writing the scripts [in /etc/init.d]:
      + all /etc/init.d scripts have to provide the following options:
        start, stop, restart, force-reload
      + the reload option is optional and must never stop and restart
        the service

    - Updated section 3.5 Cron jobs:
      + cron jobs that need to be executed more often than daily should
        be installed into /etc/cron.d

    - Updated section 3.7 Menus:
      + removed section about how to register HTML docs to `menu'
        (the corresponding section in 4.4, Web servers and applications,
        has been removed in policy 2.2.0.0 already, so this one was
        obsolete)

    - New section 3.8 Keyboard configuration:
      + details about how the backspace and delete keys should be
        handled

    - New section 3.9 Environment variables:
      + no program must depend on environment variables to get a
        reasonable default configuration

    - New section 4.6 News system configuration:
      + /etc/news/organization and /etc/news/server should be supported
        by all news servers and clients

    - Updated section 4.7 Programs for the X Window System:
      + programs requiring a non-free Motif library should be provided
        as foo-smotif and foo-dmotif package
      + if lesstif works reliably for such program, it should be linked
        against lesstif and not against a non-free Motif library

    - Updated section 4.9 Games:
      + games for X Windows have to be installed in /usr/games, just as
        non-X games

2.3.0.1, 2.3.0.0		Sep 1997

	* new section `4.2 Daemons' including rules for
	  /etc/services, /etc/protocols, /etc/rpc, and /etc/inetd.conf

	* updated section about `Configuration files':
	  packages may not touch other packages' configuration files

	* MUAs and MTAs have to use liblockfile

2.2.0.0				Jul 1997

	* added section 4.1 `Architecture specification strings':
          use
	       <arch>-linux
          where <arch> is one of the following:
               i386, alpha, arm, m68k, powerpc, sparc.

	* detailed rules for /usr/local

	* user ID's

	* editor/pager policy

	* cron jobs

	* device files

	* don't install shared libraries as executable

	* app-defaults files may not be conffiles

2.1.3.2, 2.1.3.1, 2.1.3.0	Mar 1997

	* two programs with different functionality must not have the
	  same name

	* "Webstandard 3.0"

	* "Standard for Console Messages"

	* Libraries should be compiled with `-D_REENTRANT'

	* Libraries should be stripped with "strip --strip-unneeded"

2.1.2.2, 2.1.2.1, 2.1.2.0	Nov 1996

	* Some changes WRT shared libraries

2.1.1.0				Sep 1996

	* No hard links in source packages

	* Do not use dpkg-divert or update-alternatives without consultation

	* Shared libraries must be installed stripped

2.1.0.0				Aug 1996

	* Upstream changelog must be installed too
ubuntu-policy/fhs-2.3.ps.gz0000644000175000017500000037352411054263224016217 0ustar cjwatsoncjwatsonR@fhs-2.3.ps}{wƑ)zϮoțAog5"j2s& $hD_U7|#''A"zwjxtwi4W_FMk=˸v_rY"fӑ׮@эzIV2_7?<4 mWT_ˎc"OaxNӓk; ,j  Psg]EX~FP|Z4i8b٧HZfZUc PFj( k2(r#w#onF2Rq<5c 7Vdb MvNd* C|-4n,P|oB3V)=*xj";g]{Iz/<y)PM:N7i8pf?b9qXK!VҶeϑUT ]@^`)㱿y,~Nli?E4 8\u4ص`l>Pͧʘ'y Q !z吖` L53nlFy|e=1Mڄ׷YRh0 BPk r <-y+!L<]sDL$ ;)O=cE "w)ak`|&N}:__|^7\ qحoM$z瘺n|/1`NWi1.JFЋݗЃlC2A Q )C *Љ k<`y L  =qp60O&3nGSH±t:鴟SAQ<∿(4چhk(= f5ZXCFgD8ZLFe iPؕ?b/VI H |Zu>E9&F \YAIy!TjD^*| 'CX'*D0ߥuZcB7|iy(@ɿI 2x;@B)/d'E:3<ޅtY<^/E*g`٥)yD6>}iM8#hס "1Paq)(E$Ix/-B0QDDMUAgrdQ?;,<rtkDBzfNWS6yyJdd[]Z}(Ovۍ^)fio/LWy\Z'g! G'k?Y}[D)Iґ{+<=T8uxzRE <>ݵNsИ@6isyd9ʘi gLT;&וiTN~oyJ6y'`0%f^DFEHb,0c? {MhK)t9 킒5H$b(k*Ъ8SiP*elTR}:K[ȘMVxG8=j1=jqAG&4m,~!~LuTxLR#s*吪m.`.E)MwTQҝ2*=a(YG'n8Vb18HϹ)]z o;~PJa*Q 'qlَ p5| of~Lf0lieӋxS(GKkyønHp:T.n ƈby CxB,6;K~~#;~#TItҐ߅SC(B 9澗0WrPH4 cv%F5fqٚCq`q]X4b*GȘ6r&P5 HЍ>[f󍴛̄"ƔR> [X%QӪTVm JpB(CJ 8G2 fc{ϬY͗$7Fl<> }Y:sZFbd̴ˢ,bH.ޓ\?Y!ԁct#Z#,c6>B"9[ڛDc]?mԆ'R<Ғ(F?Y|QN#d[E bL{C\m>ﶞIۦa!yXZ':J[i}' iQZI뽴.;v㕴,ki u#t{4J>y;WQM}.hF(F86 ԥ ; ;0 5HA҂!p ,`?= HBz# 5 Ry.vkK2yL\Eb}i?e Y$ 2F!_&Z~gfF.w X`G_e ܍xBo< I0 31y2K*VSo5]ޫ+8V<ȅ_+ E[s /,3XЈne0 ѭkhѭs>>6EX][$E&颷ZTlL ^IwV >Jbf;#A6evhGЉ9yv,}t)*ӄ:52vC'Ц'0;<pO`M;%^QNZ:DX6:!QlH )5L22LLt{S?f;VsHDYcUl!-r >UY@ι?YwvE֓P0p $K'4;0'$7 qX/ah;g籌35OzJ]-GGKTr' 5PNJfjk'Jm|嚎*f,@q!'/~`dv.Pw=Sq7NY,#/7!&?Y<#Kŕ9` S#hQ9>_ZoM t3wW ?6(of\Zʘo|!k棖T{T[_Xკݬ#WLukfdBGCf W6JY" I>fBdˀ-'1l&R )VkO \3{D#>iNFf7]cùZlTQ(FYLXsM!9Օ#,B?!kwHsYgF2t&OKryAלZzP@Fhr4MwdKԬ`ܥ wE:wnvJ:lD g4!'DsI5'o]@|)'?<1[_H0Mw^N4.b\0mzE8uClt82ydO'IsV߄8,%]+KT|e.}S#NxC =4ox$rB'y&]9|KGWe& 22+Q;/*;!QgRjUF4GzM7- /p.Ғ;U i ܴ qU,_ͯ3d3H[[z;m|s7Wv "x'%3^Ɩ57ͭHz{Ygi9}5+u.7{/[y,5}J<]O2m8!J2:L(cP%gmd,79䦔Uo#RmJ#S*Ie5cJ$d|\H'CP&0b)J=jp@4f(x(H(KY!(=eLrcϑZ*wBȒM0 y:Dij|,7,0w&ڿP=CӍۼ$hz-t󔼤 ev-(q 1>w?s Q aydLoiM Nd`]b_,ft*iMMEΜ,:;-jٙz=ޫ<|D:{,Atm{{NV")Av}3P<*uw0^+דz6޻p. F+7 T=0k9-cx I>S7_c%bX!x`F=P}tL׀kC&-Jӕʥw s5{}@%Hgrbz  |?k4}rcPvV{WoWYF!FsW05^>Ra9ȇh<8qͿ:sb*Zlݽ^yvvHS!:\3gV*KwםT?k4멄0B&`0ZL\֡A߀T[;З:$c_Qh_ʩVr@-]:?e)*3zyvx. Vj#Av~Z~LpO Fy AjuWartzK ڌMp=?qEI_l0`F:*7<#}mH9{>&BnAŒ;k9hǤ"/Xmۗc t(!IZs0]s@ނWkN%(Z {k~azܜD`{=n˷v 2`~'*wϒacU K6!uF̿ T3ɭSgur}=k[/BzmYA4>tM$JPNb9ĉL15}{{b-2!r27Bh* 8hQde90#p#诒$@?0ePNm*=L&DTiɎo{\[2U>Æɟw ߫ Fv_ .cr@)? ũ`XtV[ѯT!Ei߃6\Ov tZ!jk..`ʝٖ'>ХwD;hG>{Q*-{FFbm'Q%F-aGej[FܵxA #tG>h%\ܕmAC~f{qdZ {svn(?w@M`A&^Veۣ.YD Cp=ݬZB7Ze j#౑.Ft#&Leg})ȎHZHjb@xmRBrp# _r~Ѿ1vQr-J8و1"#Ej6f@t.l͡/Ωnooϩ5z?+ P%%*7YEkKPXN{Ks߯TmQ`pZ=35 ҅-4^C濫zhޯ= \D/ JOjF^̠gN/.~fF{t%tI3MgKfn{% 4$3G>Q>}?Pe]W2ўuv>1G9ԟ\kC6т0u{z1VV|&,Oߋl7fnEjNIEWб~YGL_g]}L^^CWѐv, 6_ s kulmR:fwnTjY}^[U-{ C;h Z[s@YqZղnw8!j瞟(Yvm۽z':;**D28hr];s +:`[NgDDHOj?ԏ0T8/7\DQ@$L[B7TT~!_O/_O^[<ɷ?Icn!5d#ńA/rߩ8mt_Y0O8HיL ̸,770\ @V G##ڧk 'a{?ˍ5>FjI;:U$kDT/NǮXC3Z~}^]Q1MBДyg5f5c Kb o@GhwYkJdwZӛ$UwZs#R@սZ2^-!f/["Ƨ.`5w _Ret^h'1UN"kALF)z(j*̒ͯ󻘘H7clzz6ɿvWQDBvL_N,^O:֯WˤRq!+Wڪ_Z[KV:IszǷrڜo8آ9oqnzE^XBt`7גXֻ-xGEK=Kb^b) hհULT\irJŕ*V@[s ]u% 1-(>7\i裇\-9]~M800^%/i3= e[*VO**mUR$@BZpv8 ]o}؛ӥnn$3=+_myQ"^wo/ޝޜPPWv8]Jŕ*T\ir9pYN:]? -R$Jl趍NÐ~ZZA/ W^z8?|ERP񳇿jP]hBc_Gŕ*T\ir2˶$Yi~8AR^h2s}؇p32t;{_rGM{@_V吕+mUYmJ|v|&lSmݥ(noMgp(:{0v5A{IQ|WX7d/*VS^^irjåVC&"luBm:ʿ}~+sֺmzmnvakAGȺ3T|TWo/N?\:7Koǿi3UXT\irJŕ*W߇>%JIdqH:X<СoyszֿTwJ[T[PP/{? WO%S?"i{ڢri(=lۖ^K7bĕE@ cu岊w~UYJ+TR|(E,I$Se"^Ύ]`vYv{7nv{ trbD/>>v}2%rSvU4UڪWirȿCi_9/eSt\@ig;8r{->Q7oـ-:R1; lU`TPծ吕C~=ɥ8\qgW]\N פw#f Tu{~#"t/;SxʗjM1*) T\k᤮jgߛ8|ax'b Cg$QKR7 4p3Vf֭At6(qDvv]UV^fў2ND=&sX\\\_]^?GV/_Wg/V0nK?K[x^C7?!\F0dn[nsv4avAUůeڗc[Psl>/hZRz9g~l ϖߐyThi27uq[q=:Nkt9'mnzҦHdzҖ >i{&חb/7f\Ɂ+|6誯p%,M@ћ:5I;vِBOO㼳lh gW1ʝAܥʐd&ygiHE8Dxр-!-!ѧxߴ@17`=K 7hϩފ( v<+[H(v]?a6@5Ƀ($NԸ~ 34?~Sgo)>$8>0#kmD0 Bkt|G! AA?G?>jGIqp\GYM} &ܖ^T K#V kR}-g' `]1y:b/O}9le \l(K@9 `e?v2ߊ=clC=%ܸd ړզ3n#uvUq 54>VB]E_\\߿Q 0%:YM|څjIE"58J"9GDgoȯ6P :]4jAxz,ⶤ2ꦜ텠| ݒNAAgA9ƗǢάBxY?uyikPE.鄽$M/| _/._]}iQ~;~=SLg,Snb |(Muw(HS.(2Drr݇JhxQ{+҇yQ]qMCxOY?[~CzcQ?[~C>WX9l Ep>r_H8ō2wʷr?:k"@r`J] ޗ9qa7O?ygo 2@ 1ᙢs> (_C(sM9]ъlvG33i_nHϼH`鏖B!}:M,=٥?l17[p?4nVۼzCoXB4bQ)N>—bQ#^^~K~/!39BKbWINŌzk/r>v žQo^:b#c'o* g#&ôQćGL'pl .9#KE_9uFߊ(z|SyV\9~W_jS%l9 Fh0,Mfk>7&~!_U^ ao&ô8PQOdiJ=^\׻7׋7Qj,Uei27T/8H-m tr>7E{Xyټ3il%d@AǠ{ҙTw/G)ڧmYf[2YmVb(M*yi (;CcU#^]W?]^9|-5&\NIhxk?j]3q3,Koa6 A77'D 5$C1$^{N*|;1goHosgooiye%^Y}Q@S3nn="D=uSJM={tv ~{D?.8ػfOLe$&ϖߐ~l =Xg \ 4WN1ۤZs$؈opogޱWAKtҟo I|۪fEcjS6_W`80y^ޖ%JZa鏔; pW/6J->&G*| El%*N:IAIG_9oDq`9* ,x&A,.UPlO-!pT@/ ZFw9538Yq76BZsN㧫egy1P\&OU; Y˪i^v4@N5^dnx{}zvvWOQhe۬3A i7Q^zq>_ܢo9*Z0{fУ$Qqx鋋˫χWo//~>?+i"|kn۸O'qcn=Hϖߐ)>t3#>#lsolrWgna0qj *@9A ޏ~l ϖߐ&LuМ!QOF{1#@m-2:P5M5Pׯhӿ8 VĶ5n:F@yRO~CzHA+ pҨ, A|_0])6TIgDl妞K)7b?[~Cܻkg@.,ꜚۧa+]lSg9HOw%h,Mڣmߋ׏$Eq_i5{ƵgN*l Zx>w`WşAwxDHЉx)k>gCp @f`HM~%ix«#xO?~SgoN@[hc@Zf'AҖٙv M"2 S/+'S|3! `qMrҏ#G 1@pZw/ApCO/,r,۟:h_S'2ؔ-w®LyV2^!u:ahmsG Kl/;sv7rJ}湭購ex乵?!ɉټ0Msnd6-v涮ޚ=P >gD($3Iq:mN] }Yb?[~C)7w1<7@>BʠmE`Y{o3'bHMLNsDLAָ2ϰ˃-!-!F7N 4Б##.::v{|IgB/p7%׫r+ޕ9Ol9`2G1& Miq17/] /_~}̸NiRE̚x1d~)1-!^#,јdXM?&@`V^àqR=,h_c>H7m)oy~C)j~Cz5OF d6-6s[Q~~_/ 埴'mU}svzyY_li崩Ežz>m飃'9s]%OKo1m`(NY[g{U43nxl^aE U;_[sd?b7b(7?壨Fd6-6s[Q}Ab_/ mzšE@KybEQ(goHw71nh } wpOoE ٝ_7lŜщh7+YbQ,-ǝ>JR]C 7}Dëo//~<}Ooޞ~]ۤ(6Mogoȿw|r*Kw|VNy41_ϟ];Bϻ5I‡y6Ը93?~Sgo&(C(PBW}$ssQߡA5Ou'h$|RkOlpגAꙨ l yM`Oƣ$K鯌L͂Cq-b$]r Ô@&sGߝ__\_/7 Ք mTs&/goȿF>K &4i䫯c )U"x% 0hϛk9$.IBiM%}xT{ϖ?jϖxBW 0{/?XM?~0-|=cOkpVY96y'M"cL,4I$|rAeB5"Jz9b?[~C)7lh@@qc AS=iȢc'ttEyS,1T߬O̗M0LxI-BJr v*8G c7o. opW^]_~@l>{K-=U?[~CvœOA儆_Nh*M+&f2tY!29NnALcI$r0SkKXV Q㏁H8ժ*7+@?*I|@OԚψ9sO O'Tcp!P)Q&iXmM]?wiuYLyWbguGU? Rid,=ŔWWo\_Ѷ{58hgx^:Yo.2;ƒ7y&ARÎ~HpUe::҇˪'. &{AV44MǂnkUc|.߻˖\^UgJɞטA UFM B7g~Qm`ŗsu/ogoȯ!=,}uátWN"YzRs $AS0x]OՊ=]Oqk<$?~~1" FQ11PۊzHt,$|6z"}?K6x1jc~~l~&>fM<44Mǂnkܡzi,QBEhF)_|?ͦ->iŭպҿ{ެ;Y{-I/y9R&#>R"09c*3c4\hG >eimgb1߮h*sq4/rvBIOVm+Q62!JgOb3SLZ)˼.&4@&*Ki(j6_{@bUsjdz_~S;sy::^]$ w^?1raғNnܷ?ShUgBOą L܀a[G782K?ua-!! |T.}ioȅ_xw|lgX^4ZXVփ=olʟD~l 3Ň,|R)ɘx`H2'8@ia3+ncWUbx X@vPH UIǖ!~-mAEzNO-!ѧL~<3$kc9 ӰՋ8 ~o'zwfg;vL/|#h&uX^H 54qCrr%Dw5j ><}ݛ뷗χWW7?#j`qqWt{tkvq5;3D' 'J84&#Qs̃g G(_ϴ f$[H`z)iCE>ʟ~fߐ~fߐ%0]g1,Mfk>";A~M}WFh˿z^2b_RX #ϒ4!n /o߾:~ AGP|0izGSgo)>T0 &D_9n0H!bQ)GHٵc# !ޭ MF#B6TEvܳ? ث OA8?I ,3p|-K (̣='Ab_NǙ $ MZ|aָK*"x!-!ϖߐph 5WNБۚzi/X=F}~6YWQ6>|mq'nDjjFQ3jhd/.\_x~կ? /OgsWxrTTC}54TxRi:+'0Vy~ԍͷGWpg bCѠä%Xρ<w)^K 49_$릿.Jrj>T0C2EG,R |4H'YҠ/5"A齓"?[ ?[~C~cBQV<~4~$`Zļ>ke|v Ȗm~K6lkޒ$.u6lρWFT dh27}/7JLӟ]I6JV Xkz,jf:|,M榿CG.9pI½Pe"/Hq+$5;/GznL3!qQbq7?)M"h@+'QۊOO( z 2N:3dL:-3iE{[wՍwףih2ӫW^]_cWz$g>鏯q0e"D'Q*<G { ߐ^$cEii27'&I.NYU` $pTM FGm8ϸ{ ߐ~oH/`K 4X|&iAۊz \2HX ԕ͋άfۼS%A?$A*BiM{xuD\]^ߐś/67qn~n j<.rz*_^|,'=X?[~Cz -!?Oa.K3VX`Ȥc,)A5WcK $n- tҟ6zҪ5ڌ?Ks-ϵlyϖߐJ7'[ dna]YFݰǁG1ֱR|oخ6QW'ovk+y3!nJu1! Mzxv~}qWë/W6 վ4PJsqPP>QZhgFӦ Q\>wϏ3@TMo01T_y%~?[~C<0UɃEMK(dn+$8TP!C5bLt#q}WJpI{\lvjә5^ƽ>Uˆ M_Es !}"x|WgF 1|4J3=Ko0(rA)ߞ.`ITQwH !kA=pl r~jr*`GWFIn+jg8ag)_CJCG,r|>ϖjWvD&25#a7HF`h2Aϯ?WN /\Ns ҳKgo/VD+KP9hEU@$Zl&x +x/~~GĻfѠ&%ydi27Q=(׏9OqPUC!dn\n89>&nX}y? 6̞_{7?~n~l p`!phaN+'80mLCe?51_1wJ{A\6x)Z!{aߐ^X?g,kYMeG`E} k1ovjSGV[G"k:X6 8BYl@礏8$ti3su_44z?{o`ЃCPNFI?>pV/I x7hqĔ_/J4$Y&*/FN*(Qpy-!-!l8|g e!]huN[k pyđaiUAo0&Y.c[˸I/b?[~CCN!TxTQEF/ P8-Hà6`7"+!]Yf&` 44>Vջ!Nj_*ⳟe;jSE|VdoϏ=?ɛvwgw{ }DuT.G!kAT|'ﲪ/~wY.g?~Sgo]w"c!]h c:fFV& O:3#y[Jsuc|*qCng*qw@1R7C>/^>._\/_.vsKsjfĎ8aŎ2߀;nvKer|-h 6$| ހ䍚&s.߽>=b1NKܕ0ST~<:{0,TBpZ˜5 N$!~d4LX0DFѳ7O-!'Ỉkg.,ꜚp|ܢ?]r ~d)Qq~dP%Yr/op"cB[gfyK?[~CzK?[~C}yJ (+'mAL΃ހ hB Ut^ͬ}^ϋQf5fU:*ei27}ūӷo_??E/>726e?c)%2?F3Չv NOcZvo-VJ2Gb-Gh)$dܶne(-}$9!M?+bBc FҞrvkØWW~1 ?/_ZZkΆWz OxPxNn6f+zpKw6@y^vZzD?o//hlbߣt$<7W}}>>6&mA iasL'Q(  z=[]p0Ԇo~{FOW!alycH"| 㴡֡V?-V009FP]UpӞijmn;Auc5a(Xo2|Xț|)Ai-BoVmaMRFOZdNX}ۋ_j^ /8pZҶuovoY?6rm{АI#-~贮@a ?žA]L$|,ߦs '/=mo!O-! tف>:"`ΐdN9S`g'ݘ`=G|j6:y|9YmcxҝH>mW%lH f4虔?-!?qsGtMwC5pIO:h?ەgr4ߍs/l F H2y=\e { M榏wWozw6|9<=^⋮_kӺl<޴l59 &q9#شU%N{a> ϺrmDjیryV 0vuavƲB> 4~z?[8l _9b ,'0_9G$nk_qnotQQZE+׫hZ}9>ًi;vMّr@%1xdnAWo/.^=x9;.~|wZ.p1Sgopn?"%JPK5>#iImЌb2Gyei27H *.ťO4\,hY}^M:E{;AE Edn8wŻ7g/htۜþIտ0yC`JGWNR9M4O2PS7Y]12/;/~p$.&o~zw~6|_<2N[EB,ϳ|`B?[~C?[~C~vs*RQhB~$润&aO9\V뼓=ʪ I"׆H?3/إ!Myy?FO-!}@E 6[̦n 5#zQdPwA>,We<Or[vÈ5I&Q og?~*U;3OgoHo|goo3 nH_<嗏m`ϖߐӃ-!]V07/-M榿>4*ŒziJ)Z . 3@joiC+h2^FR=uj ^x'47%}Vb>728I,VK9Y*3c4\hG >eimgb1߮h*sq4/rv"ߴ&r;z}?~On3sXW~1 ?/_ZI@ Z/$Wxe󅒱lݞ}2/P7\nw!fsɆs hXϲV.8nݴчɹEvm\BY~\9$8LY߹.^\ EeGr~+3Q"nowΪҋ#+Rە(^tbݾe'ʙ)rmr~ev370釪7 %ӛ^Sol)s YC;)vۉŪ. [&8H v=LD %Ӈi\4W\ N^o򱬥=_(r\ml+z]۬徤{s Uy"aH fRJ`ik D QȊ)pO2=iD\`d&/KC^/Pkz9sQrzph XR.~KO!ڋ| wXfm;:K%ӝw]QOrv)  =C{Hx#vDk*nMlN0Ů)~&_y+^T Qϕ³^];O{2QBODE*'^/R2 ne&<Ӷ3{ڡ*.:/s`$wTPpFOER- ,[Y-SW(w{\o/n|QҜ=gyT]B͸ŝ!CDl~*[\rIH)37,-3i Ns VKd2 ֔xڦɷ 9k{w6nhSLLYk̀c@8D iɭTo 27];F3ȃ>1/? 'I`c9Dܯσ;pٟgNYF[t~:utcLxhJJ5Fv߬H©. f#ӿ^] ׻ŪH,p KF J1Eb9meQ 1G3 e46}8Iky W7Cό*@ +?~ ?~LUĺMn?UG􇇖n?Y O{#~[d:.n%n ro@t ;@GΆhX ijdR&Kf->Ng[}h9.€Nҕk )OfNvi(-';&)sl1Ų~V`-t o8٦?@pw5'nZJ_,pOԸr*oxׂk H,q948H_;IN]ٙMq iO5"ByG-ї)D|5+;Az\KP҈zZ[!P6G}0d&/M#&lKÂKgp!MV ص܌[8>'ym`)]a$;ޜbbJgUFu&}M){HQrٞRp'^3cr6tAid=U=ʗ2%Ȟ_k[)孢_= x~eYy NC@LY,OhJ# RwPh遵fAnf % GXtŸmBIiP:ʖ9Q e$ 5k+yX%?kj=nړs |kr :fQZ;6m|OM;3g(ź 89X Jڦ4T'v<6hE -5\`pWFl4ߍALۨ̋cV}$MV~Otʍ}[QG1 [ rcyժ@%ϷewZZXA 7TuCcl7 Q\3AmI6X2chp'%lWnxVNgroVYo˲?[H>6ϊm>ץ&t[÷W/ !+zN:T?lZȭ%3\^)ڪS}&Osm[g-$H ɏ?~@{$~h=ٲc9&?ZՔ.p[ 3>$Dy!?Jɰ`ԟH>n+\[8t'Dne-ŲlmVV?f~Ae>?AO,Uu&Q2wެvV -X~ٮ}a?}$K?f$*s#v(3fٶk"eI8^TvqMO* \3%Mۍ걌#{1,#8e 8,ŷeP|R˯y@ jO*.9BEv4Ck7Z?@ HE# Ëm{YQžИ3"3iE\51t@aoҾ75xęz'Pq GW m'{$4|jXc([ ԩ`țRWT ȋ:D6`->]-LGƠrBSRni`>R  v9h?6tbŬ(s 05IQ3p%$AB+%S3_UI9:Ϣ} ٱP,) }qF=j\m$Q fT{$U Co&L= +t=J Cٴ`;s;kCg; tn^h%T NVr\S\% RQ;C4;Z8~x-]pc},OjMi_}y'ԪڡȄvuuθ3⇑憱ByPrS)n9j>SْG[h ãJ=@i+n} @< 4_t"(qM_G Ia l"_˅Y>RyjQg5lg7+y!T'}S]U  O?=C*i[.V~/׫DN oiӵS5-놮5pi`Ϛ6jޚ1i//.Ƣ6+V k! #BxQ>ʕ%B`(* "+Y$$5ݬfE$ ;ͽ!9` h}X5X] AG+ّ׻΢|-ro-yD^}l xJSmC ~%%v(.dM#28!.8_ec4.rA^ȕXr[pW<ߎm&/}ޚ!Ȅu>ciZuD6ܜ_'+y' s>:z' @O+-z"j]jMz? JNԽ`(~Wmҋ)=]ce &'m믍ȕnht`{}nuj4mfh!k6ϕ剚@BND(p0c%܏HiueJa)bs/!nks۞5Ӓ`%_~BWt a|,y·aIc]lв\B֗ f@y&(@;c $0|?͊Ѭ ̵`K|Kƀz67&{TO>NWRkB6:(d͏@N!ʆ6 6PVПSgU 5 b"j87FƦ!Sx:;& l[^Mq][r2`)@]{RmƱd4/U5Ŭ:MVj&Y5sul[|Aer4JXspaQ^۴i8 K^̦B})mT:S%;S'CS*)OmiJYz[)Ŷ >34JARijU?y1Cyv/j)F>` $˖&(0 e8:ϺTØ*Gȳ v>aiQ.ա矐9q`I-$f3MAඐTpJ`z`i>YCgDQiS%m3ؐCG*87~hCܗ(^!uFJpNau6n](Kf?:~qN򇃱'0v^mdʹv*OT^%g=g3Ʊ >m{;rFTI ClQw.G!EYrY]4rݍ %[YDe` ]}wO+y1XZ-( LX>V(u:Pd{//ƍ" tH6GOn<4Y59Qr]SF P80&rI^ƀwG3I_7-CD`ZZ7ԲF\3z?47|t#> 6vBt$ kP~f4m[9ɻ_ Bx ֛MBd!uw\g@Ve\Eɀ좓A#&jnO5gS<:;B\fVAeKVqV f j ~7;| ԕV5ErFJam4mL8r[)8[ú)eKŎfWU=B|egۺBr\܍8K l r(Z7%zZ{0K쇂O<E$/ӭʗ7`轻@܀\~BP{QC~ -\_^)ǃ`ɍ3|.= P ,'ߞ`-!xd*l̦x^djnN 'ZWKj^-ݫ{t5xZWKګ{tҽZWKj^-ݫ{tҽZWKj^-WK{i{D:T45SeJ߷j@Qկ'FzDh&b‘'=yzF WǓorh)sIٙM5 (Q iG%"6eRs 46J3`:v*PVn3W9ms IǥNuAE ] EiwCK :5)!E:0*ld,T O ԶBme.(snoQCAK›$Ƹ%9榦wB&9v%!Ə;EY+Vһ+NUUCu+l\qji橐 v +E9*pu0ltX3tU;rnKjV? ~UQy+":܋7mg Pf%x7K"D}.J!fg6հ8jnX]:aKF2TtȔUGW#q UҤLHCRG Q)-S0 qjLjRO5(Li]00^CJM?Jp._FAdqt `g "_߭?uSn WQں]84M@@\Xf7-~=yǯUsTkߣ=6!>@Qq!3%#IZt/Wֵ1 KJ@<%%@_CRmh f*":)\ y!g Lԃ^ &c=>H_` ҩiglhTyrmix]AAXZʖ\ eW$Y`C;c3 dm-jf_uv] Y+q?|t Jt/SVX`FXzr(A eGaJnkS0~SEe1Xw |w!-Z|@ >~QZ7?w<8ihFi"84iai9P-۱dPfFZ]-9Y| ֦mʘ:BG2EpDqi)K{(!8Q&9]  ACK"tV XA/nH 1KSKuSE4ӂeJ `}44Sگ\3]Ne檏Cڂ% A}'d%lXb-H8az;|~7W jWD/ִ)3p<).JiçJD5gC|1ۇ6 FjzY!ddij1jnuJ] Yvy^DMQH Z I[k 1bM$m*ô\feӊ~Eh½,-FFrl.#ت҃n "xs/"b/5"w;0( 3*:8<} ➂KÀ>\Od~V neE BnALsO A@߁p! l0hDfdQˢ6AQ!EG fg6G[?`?^] \zw5|~3#UsJ~vc{)-ZB 91ۛqp7%/ܒn406cn8P8&8L;B -tB lɮD%|ldz rU?DIjA".HlgmVX/q_fʽ~Hy2 "+=rsnF5:\ LOmpT*8hlгTlHg-ڋE;6j-7{oj LG5QM=C<%zTMxR=~֔g '/A,]\*Q'jO$SeIy; I0w NOp((-TǛz[:pIc^ iQGqVjԹrUbb@V/}|YːwӒQs]Orl},^$اzJTT.0#HKQIvV2U" '=?hAi ֐rO~-./JWS7L*Cɵ*((J\ۮ%Szp=M> za-(+nVݸΊ5>A6RD LTɋ)mVsS8/y[*9۰L(/_ʋ!j`yXϖph͗"Up>wrk{ӓw3IʲZ eVщz,baZ{-\i]\O0$|*ݏ&|7+l}Ppt):ғ3wW{ң}⸁)l$N9|UɥljPoB: ŷgЫnIC$l⍽qOD1t7YȉmO]GW[xB9&ԱTle bx࣒Pͣ)\vb j+.@ſ69ݱ3P#Rx]sJZp7f[M[ 10krZΛtv-:78ީA*T{AT -*ƪpl< 8b>.@G=ʙ3W U$Q,xS- q3Js&eY"%~Ų%Sb V+wX-V]WЫ+]DmJ{j?m7;ɑH{;-vjo&Z|[^``zdՎ!-:)@ D/cJ- CVٙMPփ86 I|ǭ$ٙL JնܥmZ_lrL.z+b[`}M}B@i UQzxfG92Flle}ԫ>kCq/l~] H(IԛI֋,I 5~-iL<.|xӤ]$u\xu l9*@6{Z% %B4W6z& `v$=CnZVa2`'dMʼ,M o;ᖮT D_It0;k =&YL%|pK[{n?}nfM0< 㳾e} >z>{o>z>z>z>z[Yfh!-*gP} |\ nЁ =f*GL7jYrڒ _h};kw(b@@Yu@ox43cv4;T[XArcjANIwB4s˜e'p 0`gkp0#= ]ֺ9USnc'lR'oh~| nTeg6LwZܥƉ#%ajx98B5<$@Fչ 9rG;R#m -FgT.)3\O9Rߣ@]7*̤ilz뢩NЎE;G'գaߑD4Y>VXi \W}O@12nA1O3B U[err^ n׍ۋ_NB4Rj%RcT]5M\J.=@S%2v̰i4Mއl53h5os\9M[oVM8`=BkJYXwiZznt:NPzr N{w9kal]Dq|Ԩ:ﴢp{]C--l.Y7:P2>'-݊4͇̇<'Q.uf~nz, &O&v&c2~otAmMœe';enZYsw]S"^[d!ѱCEF”xqO4MwK,Tnn 0 ( <ldm vX2߂Y3+Uf)6Yn]t~4R6Wk}0[7_lK /w XWqݣQ+Ua4F/wPi wR+;`1Ou"nN-KxmLAs|MMK3m& A'~a(A!S6Rʋ j!;ņ!f熧r)] 1.&4lZpH|0H?Z7^kuqrDu!nvDBԽ=1I2=zcsl色XI10;)^P>(ET%+ hu֡mu:x[m_:x[omu:x[omuߢC1!4ESOHSCUzWk$h!A榹w5'tX%?jyq˰IԴDS RĊPdZHG9j&>,w|CPcM4#$܁hv  s)z&`^ Vfg1?M:@,.d'7HA\$Ϝ$ o $Tٰǎu,J%K.0p$u@ũ g6+XECuܴU5NZTހ^bvfSʹK{a6[SzɞOu[#~CI<03jv)kIM/=zq5vK+OuZ2Sd-wC^F`20Ӗ sӜ шzza_iSKIT Rsr,0|b&Gg`|EXJ=|}ס6~._^\]kpp7/zwy HI*F.5fϷ#_Ң>x ]1xC;,m#o EW&`>`rmD:Llf7*(|d|5}R:ai0?+ HDo;cnPYz}T?"LP$Fy}NJPf5?ۙQc Nw xV m)J&Ue J:1{pm)lIgU EiN ܤFMB ӚQLRw"ǚPm}/rzYPB_.񐆷a4$KadݟRl4m-73PUɚ]YE J"V)OYDSZ̦LrM<'5Q2 JRDt}OgxOnFRhBܬ)E%kK$UGˆo2Hq68#g39gڠ=[MsMI#Qj8Ut .j02G˵2cJ횄ylb08ZbP(OԕKn{J#]-l"g =[wX^*tG o?rFid<2T A7 P긏Vܵ,wxo~z{C2/ESٙM낣=Z4A(\MV^݄&2׸YUɲw jY50aZznܟ!P8$EwٙMk(riE C=,-Fhl1g6ΟFuUQ: U}ތBUUJ=O*v{N*} t@ACNG0$'e7b!Z|B ca@á)q#)©Vyo ʾ%+-ܩ SM5kg:`w(Gt(VDDW(2/WsI!ງ·%ihK.}_>O@n)n}`tix@T3gjUiװ8c/%C$AaskQG ]jKe# O!  bfSr3ZXav뱳2 Ttg(vWQA!^X0<—K."1< _ 0O?(r;&6p6Ns\9iK޽ܒHPӻ!jw'j`Ԡ 5[+QtyS31d͆hφ(z^@j86n1jRP :tgr˽CGCj^QH./塖\S{.43*_c5,;:+O0h/D)w\]^Sli[91[g7gD2 ̻PKS}7  m^0&YDޡ%w]Sv5\a'gNi]3q$f̡lwwuŪ.NM&8z㸧^v<{}+|q50+u'^ ҁ.~Cjv{FT^݅qK\Ҫlt 0`LMD5Y}z`(lARO1[TN񃘽 b}M7ӱܴO/#Q Cl<~Ѳz^ "7i!x<+)LCbioxRPx}w^ Cɍc#ؠr_Ȏݍ_и#7`bk&4I5ӯ(NGS?hcb;v7Mn4zVGQB' &j Ap0#2y@DO})FR:;@>h(vAnKYՍTCl.kwE]֨:jCdTr7U{Vꑜ5Ub cr%$gMb @˪&t c蹁h{ 0 B/cvfSyK+L<3b~Gdz/UO֤`A66Ĥ?5} oLo<GyC|FٙMP%eU */;svF(L#տO)(`N:6%/r&}?ڟ )2Lz Ihﰽɓ,RmTL=bS*ʚaeM‚azٙMhݨ剺zsU2\-jc~>”r tS;Wd0 S-LyPs&M_i *;qC{JMؒa!^j68HPaZ##%2>OF(GOqzVN--]AMDnz~ڛk7h24;9 uh_0(g0Q/p`@d6hj鹱 =¨ҵ0Hi4}6uRw XZG%Ņ»Ai6) iFUzAu \O+rMCcsEܲ# 6Ҍq6x{Pa`BTJ4\DG:PƋInTiupj<6A6fhx .w X!73ZgF963|Ac?1Cj0"#(ir}i) C Xplhh剽_%%|$P@f;1a,fkc*YK|E=~i:y%XA+'Pda>Ce[Q4[ljU-qu\q=q0NM32*ؤn/ /%4sSarHIORs6Rwừ%r|x!y #0Ro zv|6[k2@ؓe\l$o5B3bGm 4_j޴&Xo8HBV"Qwb5Pk,$=VwҬ`\ #>Ts{G6W%MJBxw%ɷcza dc>|# lg- K0*wtS•Ս\?{u%DLmF(ETj %*[Vm6h( 56tJ4xpwi_QKցqJ݃*IFj *p ztw}@^W(TI&jb vGzC?ӧ I5-?2X,ϠS,e!EBT1)rPRm7eP ]^dny&]޶&j Uյk*}ifU%nXWq/%tF lW DN^Yд蹮4QNQwH '`vfS|iPwclUrt˿F>r 7}p ^ezHHHpv9\zB ~Qa/'VAr"2Xw( uDR6gC khکƗ*ywި^G5[= %f2I|yAPf~O ݿFÁ6SXypCFK}77 %ܒQ_ԥz[,RWy6_ec| H}Wky$1j9 RBpbI w KJ|#d !56Dh:uKN.g^QsJ -I-,߷ giYHX͌LJHH)DX "RHh`hS~̤JP+ԙ3ƎP6?`uaCЪelO%}=ڳ#t;;`K7cQ%tHnkR}E*i{745)ҵ4SQa `e:vcÿРGG@@݊ހG5{M,-ܨY)AM糚KDo ϊ UI w@Lq%;3A1sIj _I"U {=-ҥXGA9A#\w~>}u=|sz=|qqZG DB%]]Gvo_P c> JóhEdznOtJ]}^ʺiL)#C,]bQU_CH;RBLB5 cHd}([91Սvc0ȖM QKdn?^z6<;l/5VPR1V7Ib GWzjIn QN: OϜdjQK͍ vZbbdZ@ȯ~=NfkTT:EADAi*s~h{L{f] ӰB'XNŝc/o\Os+JXh;^Ul#ӊz~I"4p ;cމb9r*@eԡ熕癦D) tI gbZ/ýiϜdm\Ҵt@^'JSj3R@ǟ jn閕%s83jx=ER{ݛoQ ȔZkpo+tӈo e*`Qi!lKL#65oTDoZ%AaU3j ]t#RVTB:aQ_L LٮDd CbbO{bօDI;*$h%x^u>Η^Eu>x^u>x^u>x^u>x^noeIqAPoe *V򷾷,ǰ|;A9C˼8H/Ѧ{s.gj,9`u޷h4AUG(181nPiHaJ BUȪ`tD hlgl1[d:у)6f|h?Ľljq|xk[2`!g"G?rٙN w1-Yu@O,o_T&HZ3l3CQ9J Ќۨ 9Ҙ]Φ}8Gd)aIj?Xw%x},Ml3EM m9 NPbSWsBuXeiϜdĉfzn&GӺl;;el:#Y⬣T:Cǣ?:n3L߳㼲SuR^,na R9j5g%;/:HD=A/r8Ձe"V,G[ XRXf5S]\NB[M쮄 #$ QC3' ]{Ea[0f^A^aiq3FSM)c(g$j/RmN]9ҼtE?a'ȘX[5\T'*4Ne.*^(sѠr 'Eyzn1%*y:I2xƱ@6"S޳g3l])Brl3j[ͅkmF9Z6\m**^8d4UQLF{рLF'z-u#}1h2:޸a8T,GA/VϞ^vC-3 ǝ\80!8. )=;.mAߚ€w mM -jfԲ<_,;\*s{ɞ ~Gbѓ@'p7HxQ8Gwݮ ҄b'Uc*`$FN!h!yIoS͉>SĔe9tevI~2e;+樕/1zА}7E_q^.clVOEټk6;$p7 I[$YFG-?i ($; -nvj`> #,zAיpş+PIh.pa׭`i[u| A5hxQ+, 7NЄ<i fM+IP7T./ggoN߾}ul^]4jL5˹1<7AL$Bx.Gl5~"wp}B.;vnzf깻#d\xM eY3WƄ%|G6ׄ1EWb"o#y˭>nc(GԼ,UNG~T5׌Zמ*Y3Sȃu!OUsI67#X?9}\l {= BKl #'vwBLQvs M-=7 |]0c,3ѠIr'fg:%B51{#%"γfg6yG^M*NwKI0à hӿ$}*|NNaa&n( h 8<&Uо#(߈vuaefsc`A2ȵ2~ņF%"+7C2vN ۿ" r}|D"Q m#6>TF=IwAC;Cru"O_^%yTA}'FJ2!Үv9V-7xah-$F\P$bxŤ#:Jކ, pbZ@E!7>0Z,x Xy-B {=0q kLKsA҈znxVl)*}Z+e>үg҈]Vqމ0-׿FϥnЕĺOm؝ ٙM=ch{v]Chſ\ۧlh+]A?N[ e274S@ώE` foG.LZMoXI#ٮ6 99ttI{V3Fpܳ5fg69ZgM(NPԶax3hۖtRľQ:6"WD=;MAmsjCpkb&lfz+MA}trE(-7?nQ|Tj{Ǡ[ 0UG /ö cyr؆) 'ffN/k'aMP^ž"<2H>[#88Xb-= 0ܐwuTX', hW9]bǩ.vO*c+`ۓzvΛ^mz!coqɩr#!pX ܨPqפЍl,R8=>l\ll/iF ڛ$hy*@{bCä[]Kz!\"S-=*#b5.&:X8ۻz&% 9J,Չ {XzVė92.%Pj&H:+E pU3vc' >v >v_>vc' >vc' >vc' >vc' C0pF5&`$lx$jQ^.t J^VN_gY3'ɸngkU9bxGGxnn(w  Oe}䓼(g\l.G[Pz$GQwh,}=7hs }~&/aNg4R9I~>;vbaഃ0+~e*d]jAY;KDFN׳b-CrO[ 075UNʩ޲K OdNYLcVJLŢg`nfTxLÈjdE QĺLDPg0Q8q/Ra]%򞀍rm;O{`;D'ŏϯBTG3ZFB#G : &N@tqu4/qmp.z8uji$a;_ CŰ`,5ۅ^O9\)"P*IۡSjZ쯀 Djp'J1KhUb" : 1_`+z;oաm\)475␽lP l) 0Ri@e٘. nl<͛"Ru'7B ? [/5xE)hS|\ #3$d_ YJF1Nu#s uC烊I2CL o`{O 3j8B%f{ !w(AyXKi :ƅ O  Ɔ nƖU; Nz:%+OQ{Th( F^ Rhg,T<^*`"H#Tr4e|PۧVu\u]IVe%꽢=?V<6-ڻ}8ɠp`A 97a IvtNG@N<):t/irI2;/._^@__\\^ﮆҩ7ewCxڴJ&o~Zjpf v҆x-r08aQSBy7,u/GR#u{'|[|qK/*ZG{bpqȖ<^i@sUfEm)Mi$MN&51ҳcK),qq+Q Kھ4ul_;1N#@^YOA_{M޺YZ/n@X?'~j A`TnV>XaYav]o&'tZ@(OHFQ57 8؅ܡռ)ԡTU"%] sLk-@z}b6J;˚uA):^-ۋ5l{7[%|X4RU|#ACq~ ~?*4ŕn;7%(Sh\(\;sLDŏy4J/bF~ucFJ6re~h_Icc^16Z YZny#4ca$uLW/>Xj;Q,w&h©IL)))D 2#hZznptn 0ZmtB32P$PH\5̦5Ѳnt]O[]C^moS00dэo-x/CGi?Xa  jNr I47'[=-%P"[],U]mWk{uE5xT8bUt^RchْS\yYpXjB~JIW,6ȓ 6OU߭/w'7@Ľ3+m4'Мi%3 2{wZ ,fڌc .xJLULF夘:qӞӃtI\ 2YNqtɱLz9[.H@ŇI_9/n귘mY lɕaˮi|I/z̜stƅ&A5L+ek-}ؼH=u_CߡFr/ ;]}B}CwT }ADUAusPNCмe}cvfSӢu=W˟ϟ^^|~6u0{$k;N9S {ֽ=:QJ*(dOQ9nF^`(9QlD90*d?9iOW ޿(lt"pV&T [4+U*j;kl5u^P1u6AM#)}xFpJy?)$ID*j#Xc;~ l̳*^#ߟ樔\_-n,,Aflx_g<Ҝ5ɭ B-SPkl` a €ßzg*_d&WѳopBa WݖŨ|nڋ.Irt+]aSQ̬'oG'd >+t@b283S;g5@in%<ו?1њI8:P:<!2P.uceZPu* M9<_8!~p7Y *#Q^0p6O&zK(iqCa 2f/VyBc +þK‡6xٍ I%qҷг䱜Sxe6yn@ѲW ܵr[90L1FrI.,'rmeph9=.=p@TC8 pd3 fjwX=hoG'˕ap|2n:ByIT\}nYK6icq{ 0C1ĢWNwg&:?Ψv)lpa#4؁~z/_^Fz"95Ҧ-m2<{vX6_zIspbl9GlAo2R h54q:p* 6@Zv16QEt0Hii+&kZdd5Qh覒 Xs T|"@A"ɬHQLi))7'YFz68d}KǡvMޥZvc0tiL,w@r`L]q2cA7h%LpQKٴ`!6xKqz괅Մ"A" գBIUgGg] #LK$L@/eip>|k<ߡ|>0ڣWL[u›zS@o M)7jʛzS@)7ЛzS@o M)7ЛzS@o M9S@RE__rma(I^\MM؂4JAF^WX`Ƞ.nv)O<M x'iвO1ʨ`П{Vtzvә6UzKf4!3CSCWKE(hoMte+Q<`gYy0|әcb *.EcZ(у!IXI DR-Mc"юWٙMq05; !zT?(&z6jʃw!g qn/l -F]8*&ߍhJ1LWeAcP?~XMVJhږjAHD7Q>|tCIbFUWY.2츀A= vq"tn8| >e nț4in4HɄ`f\+{#c.oTFAT5>h)X{dbN96/cɞuuҩPRgtqL`P'J]KI'@"sTVDbDC)xݖA^Buv݀o*/o?p6PGrf{ VFxxȶBDl;j`rzqAn6vaCq [Y;ܛVRWܒ7Rޣw2<;Wmbt&mtC>6 ~L^H+y>q £L᭾{l!>j%b"1Õ$RO0Rj*.匾~5!h;64QpoNVӄ8* Z)3hZ>AYCN/qe3^3^clBX؍U4 c\͠m-Oui- jow`.!bR=nv7$ڝee(FNn\hi„/נOVY*VB"J{a:I.G! XV;')8.W`z\2 *1L[HJصaLEsyڶv c~k8;Xdm&3Zl(b?*j)?7m@>{eB`6,Y nJ-V3:nŕê !CuNZg.T{LO^6ZxP}}aFDÕa@΃J / ;CNU@k JǽOX{&C6g./yt%@=앫P wLf\B#&h0:YDp 5$ ",c,^?ud4 PΕ HW>-cXQ}V8rxnGІ @jA 35svʦ`7FQ*h>S$kyFȉ]`R`/t,XOl S0-1CȮ`0}o<~?Ɇ֎4yDHv!MnkF(w~K WSØb-%R| '݂ep i$`-4u½ M/rUĨ)H^FB 4U-j8'10%L8^ əv; 6H*Q`/tp.2m!YG*n ,Nɿ*6K#Jé]x5< 5Ɣ6F!*b 膛XvZprB|{V?*sYY.LI|HzXZ FGKy414 }O`-(R G+OM( e$W1{*3T b0u7 56p|B"(e`WT/lzkǵWhcڍMB(\5P2.\ARe]_p*sA: {́+oV^~/lS> ^\LQm;Tڐr߰ΐ?t{VOۿ~v㎧x+AлІ pP3xQx cS =L{El4K(; N^@ZQSRy;/Kz.|~oY콛S=8$UlbQbQqoXZ/-{R##OZ+(#QPF OԻ\%oA{#v ~mF̴;+?8Ahfx^2/ѡZ$wyαt`"#NNGyn㓸zJ&}gWrp c /bKQ#󖦤i+vbǒ +Dؾ2Oj YCwEVnxيۅ)QJ)+ 58gLx3QNb+Hҽx)$DD`71B> ʠ*(vYoE{1aOF꘮\`R mt ?(pa i5F%8ji$IG\n\,.WeAV. 1%⭉?10/+{ob>tjXpyuSY89 RM.g!u¾u 7Ή\{e1SDt1S]i UKPЮx,lk7d%SǃD;"/e7(]N{AP$YdtJ(pMNd,0`}S=WMuJ;\Xfe=|ؗgX\&5c~_P88דGDT/l\8vz0=+|y:/ʢQ>ő>"Ytɳh/k+nnY [G[rض=eT~:Vm!eMd1< YQN+s2EGێ]QЗ#K 7]74M~S#SyHC0<G3%@ 97ۘ3݂ߝ__\_ @#꡿b8Cu<^k< 4g߻8<ع"U*}4-Q6wQv"PJ=oFDPI{3^epwp[qAky\1=ztuUSo+ c댫ޟíSW)+t BI4$ah1.7=]_C@3Tj^ ILl?{l]aY^//JL/eY}Dr^h aYG`d,x"S @7ﮞ_~݇o[8VV%[Ƶ{d٥Mq%V[9nUw/B\G#ۥ-XdU+E뾥ԇAp*'iX\4*]ϜỆJ:uFaH﷫28 FZ#,WwH=5S8n!oCĬ|ʑCZ+nu^vۥnp%Dz5NfsN+jnҦXƽɮ\RD(edo ^Q]6kVJKRijl$R9ό* 4ެ( 78b!M%vJNt03Isi2"_9,M+ZCR^ѽWa9I Kfk"Al|-J5{bzlVg pmQ&LчqC%B14BէaR {`$ f6NjNm/  RNKTm'nܬh(4iOuGp'Rl#haxAt@=ĝ|w<]j@w l(2LiQl~yw~_nzH Y~~LxwtD8ZNٓ6 Ԍ9)'@J B`+{e>njcd 4=wZOf!톮`kYE J _I_$@~y1ZxvtY*֯˪h' =>1!vCr.(PpvxRe=-z`NG~_R \1GP 3[קt#r'˱!sRļJ(~͆"f:YdWařyxT&ʊ^wrE+ui   ^JAn&3X > o}$[2?PUm@\ұl.+{BVQ !9vk,9zmY'|?yPSS4Y;4k'\zgʊ}R,"LXDw&Na}2߉nwڹQ]{ɲ̋a )3NaNmzwt/0Y>in-:JYBnro"(Ns-  ms@{FYa*K4OpAI:*v9F"rJXزa\ǣ\Ne+#-$F22lo zBhuw0蜯4g t-f!֫Mȍh}k8++?cKϟ3 f6. Yqeo^__yqc#zI87ϐ1!439_ov:HbUs;aviSl9YѮיFHLoviNLJa6>̨nYf0~aZ?u=S)+V`82cU$X( ΗKlV6Nq86Nq"b_!)vp?N{;6;ޢs< ~wH0hdzF8ilB94ΞnAzţpkEkQg7|<y>iDxժÌl'./JȲz V)rFg(!3FITLcYᣨ繻Yʥ^h(})eV o}쬐p?7+ˍaS`?#[غ+ 'tM l"*&צC^Pc[/5+xp Q w,d6v,'- )8٪+'FuFK=\bQoXӂ#%?g[7E]| }\?5gsKKb'M%={d)8qs)Q3dұ Ywʡ p>9!O{ 9}^r8@zMc;l; an trZ4u?]8?N.蚥^Ӗzkup+?0m) W5TF骗~cB^y~j*u@+C7F} #Z & 9w]-vA $ ,N7EvcMq k2fq-"쉴%=_F,.l'TIџV?0=t^Ew R$_MlDt[=m移4U:vwr*Sd:=N9mn"]y Ce}6#rQO?`_UfTiY9/=ܔыj$3rEAh~$uFWUο2Go3 z!y;aڧNI}6z'mQKjZVA3qSFr(z7P5"v۬Ad2΃яrEx8w#8)Kړ:Tm_Mel]v-mxoWw \`ҩ0sL#xwQ$O+k@}hQ%٬A^2PuWQ=S 'x)g[Me/zXȞa|Y;&XVH|ІN~^fMhwDpћ#1h7_ USf=$GPfu3mY6 .5PΥvvgtmHҖpD~ZI :]8¿ѱd^2J0HarWtR*5`.顧|G?m0]ȑ5#j" G`D߈rRÈGSs[r ߴFs9mWE756Sk⇲թvVmjCP3deth1g#5{[ ˭x:ؑ#K0v'''&}4| LH>'zM=9&t$/!&e}\*9mp%_]l05zkۍvM"66P|bCI[~W/_=__}͋/0tJ0,JP7/ȘE%;mB:Ԍޣo, a1&5ċ/ :0cvP( ٥N1MkF&խP "J&,Dj+s;jC*[R;pЛn&Һ Ǥ4e=T'}|WTE#+y<0`9eG׸Q-/µX<*+*c(mE2l#8/^뙡6 ayMźWG^8 &)Y٥MㅓemU eF=8Ɔ #?+/.Q~޶S: a> ^Xv7VR H_߼8Ϸ ٵa&az`mKN{/f*(X͜|ֹ/쫐HsU`:[ A ER*+ ViuȟRsĴ1_n]gb>+[^~-_#i>qHM)JeY_oyogv*s@/HN;=XB6Qff/7#(~C/1ޓ$LVqU Q,;af,#7dy `iG 00`8&Q1 s˒OT̓ L nK2a]E4Y%׀$>eŐ:\iE. 4zc~$Ql7)*BŌ*&fe:z5|ǨSБ 0,4dʚ)0@>5Ms[)\QEzNr68P]-YC>`fQT'ޤ"l2<.3Enƍ27p]5BtSn\ tc@iӂ?bAUof[m%(ְQgd10C78Sbu3IG#?b5p52C`5M\l?9x&AcKda)O2ry4h;x_)r xWkSe++< <$ ZU( b`@i k.yqB=U'$w#9 LQs8v,œa?-&^*7@2}K?f+w Ti`6`W͒,uʎUbud+KŎۺjфQa* B 2۔e+G[nxBg|=`jKL vMkPXn抟Pdq7,'oJg:XGTӃ(kT?%NR@BKzo?W||W/߾}A](z񇝫âuux9EZCCrsqT -HP:I'6ZL<7&C8}@imrgǛt~"yj/H"M+Tl?.f`;Oު7iF* ϡ^ˡʞ}~ ߷Wr}_}P\Q_nDy=W\Hr;/bx0shȞ[&^/9e؁[Ug0'1ƚ#}(- $v`1zI1`RI."Fd#VXf!uf4-CX. t95tOߗeg6tKf RdA. ` #1\ܕsdn*I!OB_\+}kKsi<πBڨ? |4REtPxi^?{+V?頨r؄˻z"@xn@ @9ȪrV)PIstoV( ֫J7ˬyvp%תWKHa+<MH$O%%hC 3p X3Sfd)EnƧ?e|)E 0L]Z@$ y27brS.m/˖i~Čt:AYzI;SO&8~gFF1RN a<@<SGP~q09K_q&O[ N~fIHs7| ig0M G˪?0C_g5W}6f@yJ߬1P劾}mMfs>"9k+LKNqJmm[4y}҄E1){efuBǃ HiVƖpG`pJo'[E[q54(%- #+XHVWmύV): rN0:{sۛsXեW N)4q٥M,X>-zQZW|q-W\ Kb8YP빢LGiJ&douңiB(W-]"ń(4s2}l|/[A[< C+Xg]l{#xqq}.Ȳ 3g딹bEVHt P*|\% _TUlnwY8%Jna4a^@|BU쓫g\IDG#. ٥Mq4[/AR~Brߠgt'x63 |N,7sWUUHp͌kf`kfh9kf53p \353p \353p \353p \3B\3 s!pD4:4LGD1Ek&&?YRϊpB=5٥M1uIbׄU "Mu!q,ɮ$ϥ0<̡C5_fER~D!>/whI-$RKbYwPFIUAgHw(rJ(3s[g=m09`D !br9Ÿjuk6ߕZDA pvbGP\-YJS^ ^y}}0֏=nwz_BWвLfc)CM9hC./ fR2n-`UuOz#Z#˶P#Z¥f%0p!(WMOLĻ)@X>0gCPB;*B`O|2b*oK'̓8<&Vj^)^f=GxWq_:IZHʳ= ¨ذ(H&Npw4KW/^C5iA KEX]SAʲ50ppQ*ZÔA@ݫ7D݂ 0MQ cb?s?rZ Pt j82U])HV`z@N=ϱ B8r 7\#iч}}*NOzvD[MOhr׃/@xzYM3JF˳u)NqjaR0* ֛; p* Zc=?'&CE*:~vq&Qz4g.U ހ ٥MwE(d7o޾zZn7^TtF`f}^vrդÙ\vG9FQ6"ef|g(G+dqe3Qq %d:lȞ0fcoR-'ʥ}w&i6u{QPĐԂC6ZDHj{Rhd4S ?y- =B+!yDu#W=Y,ΡleFtl{38 ,CCg^lg{b C g$F.L~9KZ EkIl4r3vҘ Oo۱ #&,`,y?\=W{?aNv!%rh;1nFO +"5WLV9;x B4kl8".24Kb;Fkp\/M~$Yp=l /*J1Fz/k iրm];L4LkKո6]2'A{˟p25LX`yႉpȹ'rꥉQ5HE wUxH}Rtr1EKx> *eUݯ'p-a&/a_\/' wд?>z7%>ɌX/X1F;^y=Qߜ`ۅ6k &T-n)I?9<^n fdEXPK(1-(7G\Cy\͆Z ݯxe7~ F^͡Ֆ +CAVn[䄨5܎{'fGN|)lX?6utr ME[%́K! ;fN6n{.Z}OHf &-^i>%m%9 } .b-m}l WJh\@.˃W_$tHR>Qqؠ ir[%e!&z(G숷[;ℌ(X PS<uȲx'X WI`ӪQ$9W1.ucy4dOB֫7)rC~$4[C갧7NxF;*< xh0^Zܱlr6ID[ :H#~ ;Y98Z},p.>_-Pi)/:ٞ8+~,ēC<pf 'HTs8 U#u)ہ򯕩~ʎ^+s?v9b *NAOeSAOEOEM詎g[)*͍/ 8 @mle}e-LHCT{QdP{үjo'Q0iq=3̅+&h(TVJ-"­$J׻ZYV庂ri &((9z3I(Hkv]rD1g2 TMHrqE$ŞM犟=WLr!tJs3 ۭ Bt 76f 㖐1t8~b 7gU.]2*y]Q, Ψsf#./'˖ke4U3xnUݻ)iUhY?L\u_sRrlg4+4R 賍ݱT 9(̏Ue9q3y7`Nrɠw,<7xSo|$y&Be:bLåRj_2BHIDj\-j͔: ?N߷#y;AIغF(U={Nc|rk@ _ep\pPIz-wx/֜"wγ:(( jowXy+cC@$D| ȁk jAAf3FB(Exl0$r ;W]itgnd8$oK6GN #EWTDNhz2@viSlrlz]}A!y|f]gFN ԼӮc,g'um?+Nj8shz5\ ɡp_il"'LO fD; V:] {yVQ%wVʕMx$8bfQ}K#٥N JSHjV I1h"&bh"&b@h"aP4M@1D 4M@1D 4M@1D 4M@1DD$E:6lJf*#?@֓IoNJ-p"y58 ѰP7e1~q|P З)F{t`$1G`_V`L<*$ R'$ݕq?*;YE&8hG&h2D#{ZdoAs+Ӹ'jSI̢=DK #Aq 6j` ռ/`SXA=7њa1)FQKL L{6Glx<'z&*llΜPZq!Zq̭̐[H୔'$Ks.s)%XR]H9ގ_Hl?fp/ld0@fuqصCvk}.$Ź׷?oVυyg}j:0(?*$4C_}clɄo$8F-7OKiaJ1r SU1U3@*GyG%oi :↢nb>?6a7ߑ=a-GL3n|u5AMuF#ަ|&VLWbVpuxu]xȲSm.u4^3U 6'Dtȟ2.ROUQYơ>RS^%M]e06" v-_t 7oefQ)xAO=VE{y-M33a&hx k+7?hD] :~Uu,.X91dA:>&b&@|_vEq!`(TkC?7eOHZ#0UQx8>` yBSM]TR`dilЩ~B,[ZtǗ7~Ly iI~&G^fڹ61 N8p SN]Z+R\꘠4+[t QP \ǯ7 WOUG0ܱT/5:e!Ԝ{I$Ck`'g ٥MSe{ 2=eLcX=lR.wr}ZyGLRsZij g3Y(E 4Dna%d}*f]ф(=l VK(UaJ5 m^.6^׀vѮb9ޘRf\h.1J-vŶ&]-|O?NT =! [1L㑓ezǣV-:T=ƖJW*N _O8i M\v!B{E~c[[Xgb>13s] xLޣhJODqY['зFF)PUGz9ީh[g!, YCKQ1z@ȳAvG{۱-v rQO0foL ~3RFhFlxd6.9,.~"Ko&YvsX=lR.^[U.ʛ=zɩəg<$zwbTv":Rs Y8Ц] H2 bRNeGD|D@.v~4΁ݸB_0tUK?SԖ#zڷ*d "\0)8Y~PX@yяNq]9S6y!oHK.!'d|/!(4Cٔl=1*pJ!pnzZ'0́E7>_g2 "ffM(.J[L;=ֺ>Zn6G_槜N7޼ +E!m+Z!+6u2V~ 1 ^Pb+İ/شgh VX:q16(Ay@`  T N@Q,;JuN@ai7xuy%#~(3iv6^yޞG}OpT 14c'W47\' /B)ʡ-Kaz%Y#7(~{9Njwc"r97EyOw~)'Dia+''J|nw5>Ý0 R;| 6~*i4ۑ Fj:I|G'|N8zJu&#GU+,/rJ/\.# _+fb>N\,_8ypҦ؊slŽ8PXL8aRIP*t7^i['41X`3]|AVnb6|@YHHO)g <2#pi9us H߁r<4Am n} TG &}s.381ai}ȮӪ.vѾUr|S!>qzTweR`b K;tvp$1 w,h,ԛ;aTX$l 3]>5fKTHskJfb;Ov!Uo/9c%ILxH %d{Ai?4/$?SDf+0z* zYWx!DuʮKBg>gãf46d_@RRUVID׍D-13m6i=d ny''DE]JEtC$ՔV>i[X.K*Mˎh-F ʙ.xZ3]ڮ`EG- 6dNCFetIK^ k*9<&ūM„x];8YvC {JSlz (+VK'׎]Bcx]ps<|EhpprR!'opl$LJ7,>٪wpw}M&E*cwȽHDT>jQf1"}lW#X _bTkyw}Q\O,];}|y^}jEߦ+r>P+%G#́Z^y=7zzO!K7Ɗ R Tjg#+Vg@ 8y5Iomij<jbsv+ױ .Z' zOgB)vײY)J6U+s&bN*/ w_VRD n71lܨ:Y?Jv[Fp_X=6$'U!+faƅy-k.\6oio=-ͩN54 ɚL MxJ Mz j=P|v6!Bo]kUEe:!|Q&dz="p9_(Gʲ^!yUnx O^i4-@9c+,f ̍\2Ƈ>{i =!ՆIV|.R,G]=ֽi8B6v8,~?-[i$zg< |;6wgrDKDHRYߎ_|7qޣdJ] ?)/H#Hu9+\ #m=M N6M< F=T6o-ؾY;,]Yeiv\Y_/. =3^[eigYQDK8GԭV "!I|#mUi<mY6i77<Nǻ, "xтN\)se >4Ӕy+vlWPa>Σgq$W*T^(1-(7Gl'{ jӕK"GkDg@oևaa^i []Ԏ˜Fm`k]3dpuX*9vru\gqAQ,hzT\Ku@z54eRh>H`_:IDD4ۜ$)eQx MT5 e\.FrcviS2Jtr}s$nHi0x -0_0ZMsNg&Lqt7cCM=dYd q5fb/zoGHKEO!] \8 0'rQơوIMߩ8uK`9Pݝzb/Ixcl.˘ae)V,H~E_:Pcl*ۤ|YcqlMR5n -S ܲCט<B~O_:Hd%"z֯SX):pQуv6_&Bk, ]:c Dx(h& @i\`G)mseM{-oj\-mS5z~ VO9E?Ӑ(1-(ݿSGlCy'mt+.jYM3nSJF˳8&:86@)tg51j]2 |vfXsQZ<03DL<ۖUË@;),,H}bRB>i9{囫o.?_ 7Gx<&wS9RA7u P?~U׹$aY* )8Yn0='߉ÒS?QdEGaviSthȞ`=Ȕ&Fр)B(\au( kA@@9Ogc[hR&VIMtVQxfC/bLoTdrW^9G2s:)^CNFu/h1FK)[ɨnW :UΑ9kBO'$Fyfl::#.rؖi]Y‘ɉ 7(^p,eO;Y>?̒u`ܭ` Nj DCUxH:r\xr}m-EXw#DfJM0MU >g +j)Q֫z>`Wb1*HbvKe,գ,' 4 띑MV3|sY,+50B^v L`qE} BW_U0PTA_r*~4`U4Lo7x}|\;I^ g\U 7R!.&&b3rA_\1 I~_ Wܗ# .G#+QGQH}"`µ^Fs1u}}cZS=NѻSѻuȲ- jPuaY_CI3 WzT>g$f?gF4tN#i9@a ek 7ʋƜg"J98VBek.T]◟?!uH&a2聀(mw ^y2C?^lT¶cQ9~5 ٥M,U{PkWVP`WtzkOޠ<.&a%>x?D!~p݆}w:O FW5z#t?sT~:o?=!k3M`Q >3Wyzϯ}qr X:ʉS,J-9'Jr9 ۮ{0g80M&Be#<oLQ0)I){xtJu(T$'zGmG pQ<9 Q^kwZҾ?{oUA@@9Œgezٖ\5kp&zN>$ Q魋'“CF.y02R؇RGy.A3A#W5x={ w/yc|<./_SLאlc9X̦un . X8@`4՘C?P.Q8 i=vvk 8vk"t)zy_mW)y;4u;I)+ &rr0݂$ ;Oo6̊@^u F,܅TR6v (\m#؍o}^MK l B2P"5e@-z;h!_%]X8siAaD:,)"ʉbTie~nmW\k 4lI:3oiǛa).gNS |Ia O;[2,9@!0OSc  Jc`B4e{jj7fTp8^Q#@6t}@pͣ8qZ.ܯ>Ju}QNmZ8"tώ~q]/isi#g]9Ekax ]Y{/hs8BvѦ`*UmRfTj@̥X6 OҎi/j8gZqh;gaSgCaU~uc1pW?ʕӂ0~p =m'D"bsdy0c8quD7dO;55Y㗫3!'X<V-/p|Pdޣ/[ƭx07>L$)l}_!|ws _ReR䀶[U߱,NڧߍC Wk@ :}mY"wW:X7sGszT4lY@p݅x P:0nUKN[Cz+@g(0 y1U27_^ٱ+_(+ƭߟԍZ?t~@EDn[Y2on'[䑺wIZ yxim:gg3XMz z-8Riu_7+ERnkka! O_VfW!`A6/[J}?r!MyBfFw ts߅ >W%t?0/)ܑ &s4U\* B(<k# ]84 u6X[m6obl^BNsv]_wA}¾XmT/肥T˃\wx[;"zG0{Fv6,HBikCj 9`*I fn{5&L{-`һ4Z[|[oo ?4=y u<*d?|{^_ ^7fB~|V%"2ِ\GQ侀^I3X荶Bq_ o`|h KE ^}3%-W|,^D,4BgYC^ Gio6f,~Q`ftY,'R ^uD5Q+ioto﫽BۮϭdaRnRjI.mEdʤ믰qG5[{v KKY`ZIjQ4"W]\CɁ;8S"&tMiqbEx[G}V arc6m"eUuM0vZ%ߙb0/:.SrU׍##>FC/52l}RzU fZTJM3H VO:̩n7Ei!q;8YJ^ [!Cg `B;.%ɕ=&ɉQY^!wN2\xݿK͖ȠX9hWP@4Tx,m"S nT2_k,s4k2;ǧnu!;>y BZHf)oh;#نhKHo*,ʼno[o8|9 r'>G_OOi|b7S yE[Y{GHAaZ&F# )Oǻ{D&6*]& :SLt)azY[ݽ!G_:KexQ /N0B 94cS‡&o7ƝP% mW)Cqӗ(4ѐv1iz]$ $V*֤Qi:|edD7\]y+)/:V;W tݫ} ؊'cYn"9W9{p(>֨?B PJ7ݿtɟ0s]1e Diغyw Ff'Ńu=-SoRHXA*HX)7H6.4mךX }護Ab;q؎߅F$b_+E8 E_R։A@bN+s !Z2QE,d1(ygz 0]:쬂 ԀZa'4V6Ec"ZbGN }(G ,L7&awNQ4F@l=.hWmU̼6a[78 |8KG? 45cej:h\sK%MqL4v,~rRM`\ǠqFʡqFBaʳѸۍ0N[s5RۭFߠ[sxjdKقX Cظc阖&4uyjYʱ뇡Ն cR_IG\ T]pg.XZ :N?O#SM b~ꀁSǞ-2%~u 0E uiAA=xLAh'ȸik3# Mn:];G4DooCdΐ* Ⰳ* 4"x1F PD9Kehα1GlҎ>=^ķ 1܊5Kܬf;1=l*$`,͡NleFyR~rE[}gM(}bs7ߝw<!ОNbWAǦ/d? gAs\r&Yf^حL<[U N*Sq>{ą~ʈ ߳++NX_>ݻW/L#]Ą8я ik9 /Vc n;ZQ$t1`RΌY?4#k.~i ٥M@,;FRS/Y&G_]E$1gD(3ӷro7w- ":J!q/YkG k9ݺ`9[i ވ7=7*b& 4o\a~ۊH R- ^|\@{{86=~ Rݷjޜ;HVSUD4tjif޵tE\ՄCdiؕ-NB@?%Fr5vґgD٥MҐ=ewIJ&Z=;hFUB|:_*JyU%?V*δd/:!snE5Q=kSw_o~zQ"3t*^*׋,«jl%ֳ >PQwJFݖX~H꯾nINNnݯهx_;¦tލf$TFrf-nӵG9n$hwPړΝ/_Mnx}!KΊ{'XGFGT{YhGbt"F]-*(3{4+߅J.r;ܮNb|6"*f>V\~ >bL:VB2EEAԲ  ~ р%R ?FOf\f_#þ` ס _'Q9IwV>gʨPuWQ=trFQ)bTGj0Pl/[#*t# G`(yL=oO,'hdNr0AO UP?Lҙ0Uv+چmsnNvpWwwf%@l;ߟsZ_;TrFkc->Huqg<9OZ~awꩢa+j%\I!\LM͏t{;6E{}l;tL#lw-W}XV|Ysq!tʣo!jDc<Ž-l}rV\p3N]r;BSWNjC[]p~sW?rTO@!N_RZwo.8и;C+^j;L װꏞW`{oXt`#07\oʧYIR?ﴚ1TӿlL-8XӴ$y.[iZ2ꨨ)2U(n%ԤY< -MUjTvIq+6=Vt ]$K%ZՐD!9tU3Ir4,tʬV%Yu4:)O++\}Cر kVs5+XL h=zW d͎ڨo)hb C0}{ GR[x2/z,ROTb'|V%#@y^/F ezٷJ/_~V,`ȊhK  ;b@8hy ޫK'R9H9Y0[;4Zb@ߖpEBDA . B/NIaxRrF}`̃}P$@ .mlȊ zw⨰^wqIm0H&W f6Ve ialPv`;xe_ úR/-L(iƙhƉ T%\ 2QyH#$MnDr|1jNm uP_;/?v8 ~pp?; B ]Kb)L8YfEJ5' ODIxBJ*˗/ _rER\Όi;+Wp$Cؠp=nhA0ѻ[8G|ͫ/_7Wo_~z g vF9]Z?XZ8`ACz) BKsO#AH|ӔGV $MbK٥Mw(- c1L+a8RMV/Vdz5EGnMX8RLܥI0_s.Zfc('uR$rNd7Vk5R˚>L- NBpbWUĝ̻ghO*r!b()e[ѻ5*ԅY:.m d&7{}|oPAN+/ gJOG(J&d.&ӲYz#NIKz콨`0)Z$-j? %(i#^Nd'Ya0 ,FC\rO\$?*"JpM~Q#Pi߹)/:U! z$P,u.q &!UiWQh@ m-4'ޑPGJ7Pgь36WɅX\P8򾺘l3#ۥDkT#WƒC~sIb ?శV£w,cf63lq`=ןy,O-ۥ۟А*,b<1*܄kԅ qQ&U%&Nҝ#\#귛b?!=,mf6-+:dfJ"Q)D0Cfb'%R_p5`_>nړ9FVRӇ͗#(4!ʜ=|VѤ}*4_:^R4 B|t͟Y5 O.y n>y}+5>"Rz|0yϤ}jJ7͠+/7\:y /̖($I fR̦k%¼M<}z`RY"݆C:K ^fȪ? xT_:~xT%"z٪FSjaK9SSvk^a5o64U zGѾlBDf[w5ʕ m8z Z? ay)s{hy0 %'Q S?ȡA/8|2Kh)s!(=#O4y635XUD:]PcѲYgkZ:pl̥yW#=*K:U"FjOq%z')'B#V#˻4AlΓtD=ʇN2fpfzW' bkeJOY9)YGEOb< Vtl=gh8ۚ> ӃA_5zUث{vLȫ}ܵf6Gly#@yohǘD1&(cLgc19R&r#ЍG Iw4 H7 H:: Hàt$Iw@t$Iw@t$Iw@t$Iw@WAW@}<~_OË`a1 #_.KF%̑tt)3(*,,> 2<CFIr9 ZK6꧳W٥Mq8}DFm&po MߜM#y,np +t,Uގ^l:~҉V,1:.P40\/0C}H,o64OmfO=) }g6r\e%Nߍ) #tun~hFp(%y o۵Vth, ;[›)%_=E "|trbEx7kL v`v"8Sf[dܐbLB4a"aviSX+Ǡ|^J?\+l h@#|AMbviSl7sL2Bd aS jܬf;Yu7c{%R3_^h1jCZ0z'9 | "`̀m$z} ACZt~,LQ 'X!.U^~{sAqȢMšFCAreOAՍׯ.}Y\ND[y!wMd1ٹ,F@@B#O( ' rdbmN?s/SZ)wOi)p]ꔧ'LpUԶ; ;z!bM9.uJx|ҧ&cj-ʆ +;+;0_Wv|e_Wv|e_Wv|e_Wv|e}e 0X ezٷJ/&څd#K9Yz/FNXj5^P^ۻX^ >Bŵ$_9k 㹔FjzRrirAM7x7&=]eW'hW٬aЂ/"KjAڝb]<8s-,q۲: \n5T!p":}FJ$9~A/Oˆk<ЗS1{%+1ʬ!<#tu@OlD }mQH?\i˼'; Gۿпr6i1\ q5fj[SU\#PzZ uJiX?o7{ rd]ɲ7.?\]!oDhm q)G@!z>3a'f:%<`Ү_S鏣L`=.i]UɲK_ ;]]Tr4'Fz _Mh҈]߯^7[w}C ECp>IpN8Phf-;n3W SpnaD-JRs=Mφ Ma Q{q_?JT!cP"N"!Lӧ9YYNXڑ0"PP #{)QCSIc#IQI*A`LCmB]$7'c EL 1R ZX !0(:hiPl/a ]l7Һ6\IGagVV|SHt'[Ce$48++uw*TT-( Y6jOA>kQLb#F+. ڶl0vSQx6b~o喲:a˒4^">Iv􅏠Dz6=cd.ڣC/Vanmj,ÃQ t +OmslPEmȀ3G;n 1t"$D䗊%s$pN$;=M"t7gȲj5CTsa\6ET}5V\q㜮DgiaWns6e`:+<}ndRXUk犒hZ"k c Ԣ13W?+NS,__Ǡ8J}OB|?14oFV:T"6$Ox2L%<L ^QIJfFZMUXAZ?C.% ٤XJSمe&a>/,ߍ[.P {Y$,!4 .W7n%]B?=GPh@ 3Kb9YfŁ7 kPsrٜdZn\G;+xokgDnak+ f!϶PJcT3Xz.ujʞRVu::pǂj.lyvyES^$ykRO ?sKd`i )b`GG%eoNYVv<#:+IJ.mm4Nn]=~y;=,h lV{ WR+^Cl d}9+ˍϩTK-hU'[8~vOT sdFWm$ɭaFn ߠ;9).J44 q3ݎ҈Q1)eg Guv5ʛ~` [q}Mg+:dQ]GuGOu?u:*rݺUjRKOZW'з>k^~5i8*ϋfFN镳rEg a3Zo'r^o췇5xx\y1zԍ/%\* 'P w٥Mݐ=iJуpi-WgyQVꮜB} ,m"k,`Jsk$V9Y^yY@!JK tV!]f ^mthJѴ0 )dz6ÎfkH!/ јXjC_ %KI< ^_kj *(fu;t=esUFp̺{t3z o˯u Ŏc+Gb ᅬn.5"d!b!lRf~YxƝ!Cs "?  xH!e#C`Mr?wХ^E)gaw@CWs\(8~ܩd$ZS ;9Uϯ`UށkC5 WƤ<4~vЁD,WgOhE_V)! .UWiU&U+Vۃ L9ԗk?w/ۿ< ݋W?}חo^\;8*lE( i l3pj}v7+)"rK\ Io|ERe0iwxo)6Uˎ:dA'6B'S[DԫYȝ$~%%[yw%՘|Z>LX0! "SeokJy3^#I10n69Mna6Mnà&mrp&mrp&mrp&mrpWv 3^tvspVii2)7./?7G棁d :MG$N"$REle",q@wІ&:V28 C035ҮNs~& IzqԐDbE'EGzX=GAνcviS/ +y}}zۏ71K7;MN3k/$րxIM{Ȧi<0JgB/0鏊̂f=#3Qz`viSlH[^pUqgcKh.`GQHDi!2 F(P~.RrϷUD!DWw3 6~afEZy%㰮8@ҮlC3i\*wMe61 qY~J7͐vtȟoWyOQB(W~KRPнOi>nPnKU(7h&~J.\.`LˎH@~tܘ>?eH}cڨ7YJ퓱]} ˉ;s? #,Sd*F,pAϊ' o_| #_?z!uQCg2uG>Bz E_ 7/8JGjfx\<Ʊ?6Te_N<;8"r5N/f̔zIp98?ܬfx)5JFqBEU*,7UKk1o9ZdfR#оP=4޶n0 hirCK<+9|#O1ϼARxЁqd.Tidn&Wvd,"s?-2K85ѱyAfi/EޖH]r6-i/-!oi(Q{Dfs:м4}?\EFh?k)).ZQ}7wbbs6כIn;˶ F2kܘ!]Yrٹǯ=Fd[ xmKYs |< gm_;; gC)p%,hh0rXEx Gxlu>Qe. .B֋I1 %!QYa72lxBJENseߜ9tnbDf®jRвx$xDܨ)Fs)ew꺴C+oɻb V˺EP5K xŶ`EH't!*w{a!f;;V<&*|e s}w򜁄a*e5q0KR H3"R*Kc{sqOاxocϑ$D,{$x}y = NJ0l]w4쮏U{2J}ލBI)y7 nleIkdua 5ItrM{_wG;'v%7jJ5˃XIHmE?R(m?#U.wӥjBg_~Ft. >rNMXG)vpl#0n_ 7T+G,&4IC;O ϫ(7q [=b}NdٲIu#¬}=#ghQ).0?N lҮ7ccŎZ,IPY2 p 2 p r2 z@8d@8d@8d@8_$NӄMӚz@HG}o@,Up BSprQVBZZTC tB(Xn#Pi3MJ 7=PiC ͚04og?)PU lcBg0^W%0 eݤ8;yq6%Ϻ)9\fE=?H%(> <ŕC7kM*ZO(4O %<`Hg5v@XfgC`+ `T4|\Q0ͧV_ z`0;E'ƕ\=-Y0 !*P'K-Q^֥JО,sUTU" ~%ĐZ'4R`5Xs/ V\pb]ِ'x}y>񹅪ܸF-^y<ŭc) 1\HW15 YzI(J JBJ! a٥M!r kEBP9Ku JrЍ 1^-PieDyy>[j.k :N(t%[Jz UVWG2cY4cB'%/NoUWj;0,`(w_opf(W{_$!}Jƃ1z*Hz&`s0#NpxwԴ09B4wO ~ MrB"G$@-HkI>v 9&IOZJ'^iO|" aaFC,Zv f<en gJ{'ɳmG߹dKbviS) T{ޥ%e{ ƽww10`.>.<.à\}py\}py\}py\}pyuyb =*)yQ[{>ϼ\=XXWsu ĂBu*J=>K]TEO*&gUS' %:dqP\I֕7>\j08z|9\W\9uʕS9k6.5i]7U|f7X0Zl |PGCT?\]aBA̝!r'PL o;ҝn6^3C,49 ,0[ aX5tUėx[)͘\)cq 9E3K^, l5oP`I" yi3lYj~pf<.N‰RK';Jq{n9Eю[0ѣr+#*y0>lKş"'v( Malr’E!VViƽS=\qB9Cǁxv{g(mzHw[VUs"n`nsR MW@iA~Ck*xJ ͬUI"+ 32l%yqW}cBE)2&ю(f8j!`:+&^wIH lG9x^/irMVa9[c+PQВl=?`,l3r8l}cA“~';CslRh ӭۣ(6a'k/(Wfb '_z&CT{  zF=_Ĕ9OJ>Y\T k)4w\-p6a% 6|>Yj:E"W], ?!x9\㡌uyE2S=4 ;1\ J4㑦-C;'/PsJL J3F!~hPwRMPKa;*_-ĕ!0{2񠩱dkRbf_: $s#(4s!]soڜhAC4+³gb![^~@>ROΦmDa ^S}.vU vٸC_,~)s(K$3 g8է}*\sAI֕uHy.hrUIzH"qȦ$>5OvdkMxVDY0\ad>W",Yk:'o []Vl WdF, ik$mQFn0whdzFE]FC1i|}+\VY&J.m-,iݟI0)eې'׏Wtz[J qeqܦ`/+hK.ÖꖁkãY"]E*Q,Lšߣ UgQGJyAa~$Y2+-:zE^2\.0H\.Iz:̎rZ/W<.=a~L(mF2l==|َƙRT'tǏB&Vz l}LA;WtI~o h;'=hWP# ^=i>K~%7JyMy˳ݐz\(/Ԗ C ܑKb2>#]t߉جхG=" .mw6ad~;cx\6a{le뻹_ē@&{ (4mnxn\iZkc].$n|Ң,d66)'78۷ׯnLA,B̤D{Le/!??6IzAviSlDߜxiN&椈`B?'QX)9)Y#:`Yv]&8_serdD'T#'֍7Sr988qv9&8Zݬ55>ݯihyЇď bd=1襲 J9D(J9DzJ9 %r@P"%r@P"%r@P"%r@P"E88dV1 {Di2UjĊ,Rp%yy|C_߼@AYkۏ@< d?сK W""$HcY.@=%(j$ g?83?8?8zpgpgpgpg_? SRfk49L4Ve.bU;%WGGjp"$`n>NQ ǻ}ۙP~?gVh#ݫ\m;r_=PrYԵԀu,k-Pigvk\Pfw|r$˳{֘Bߢ7tσB \f$t4#o1qO֝n]̌5grѿp0o9D~'~ < pGy8V07Rg8rqi| 4c920KyI=gONe\ ,ʺ捋tTV*RܪA@<9 t7|]䯇NBQp)8M钾(˫g&؈ pэ^V_. ga#? Y'sR@q~EHpu)F4rؒu[6׉9KYJU~P;qZ,֛l6 !{e--HO8tfڲC02jI΁[w[E']b-xzSKCĻprDߝ٭rl\I,e 6]yGDhrEI4#.SlT$LfѷP*% ~|?7-ז,tOTq4%oj%Wv ?MAtܪN^9<+8kUVo`{iBJ)`{\T 9W\$^8'ya7C8FZ/g .^px50}*_XCG%7-8rߕ Z"0UrP$2 ]{S$#ab EnLq\)MPF]uUC]sd҆!lϠrhui(rҤ87B bU.гq&BYj! f܃y% iڙ:Q0 0ok,Kn ,.FMrM`EUh8Y# ۇ$~{uwiG<@8Wo4 9Xv-M=ޫP E`@Ό 2swȄ(A)6D!0|/ |/߾oBaHm7!"J#u-åہ*YbF)+6,]) ~ت&2[uԽz"PMIIK `дNs1^yb_u.z0LC*7(MD*dLrfdD0. ?uGŻeu[QgCL"zodeE 3џVW#730ԳewX`LuND[x_pZղ[1:عeG7/_}zחo^ȏ/__D>JlcBw;:uW;mprwGRZ!;^0 Nq9K2٥Mq_,;k400P0ATK;G=0uFVs9BM%]%@G=,0Rp|FHl*f:%<\{7 &cTp,bcX]^-ۥ-XS]νE*B6=8.+/.e?/Cx#xK8:d;pC/,Ս\\}ҥ f4QnX/3:)]muzLv1<\]fdٞ| b xT$0zg`*]EjL3 i*uQ<&q?W(t_cȳ )p_-۔p(#˖{LeUU0xdy'hbaBe[Ҧpl [(+0Km~h㤧DD4[~q"glx|yWбgҍy&*ջi)x|,h8nY7dΗ2Z9}fM #℥lG(Ŏ-;eыƪnW jMY0(jF܅f6Veݭ@ar~a~ē"W@xFRv;$v: _.$Le]]zgDvNvNÂphix5L1ﬗYCDЂ#N0958H:N @QhRSSo_Q66} 'Rl8Y}W* >`OmOl*ऺxWW04WspRBۍ5Z]B#js_|ɉM+~,FQ!a?8wj;f~0mU% u"բ$wezJ]%dV^$(h b(h 0U(hP4 @AP4 @AP4 @AP4 @AB@AIz *y=jd>E$ `}`[,Q"xn@^~ KABB4c-g' Ô~χ6Rt~9hV^gE83, ?(cAص8 4:֑z\}xۛ:*b}F~4 zIAP6r, ~iQfsO<*X/CaY9BOU\﷛ݾI[X+֣aK iHkkS}k ).?ZDrAlG1l 6y%&$- l4,q1:߰-#ǒДłl`qAQC@%9>}!k# .dkrSK[ |%2LDE01Hf{BD\@.N JpjcI;%/:UE߽{%'OOE[(d/5).ZӎKdׄA(,g[X/z(T2UYVC8|O1q2B"$.H n %/:6Wjg Ü1l2L(rX@WݸEDK&p7I07@`.pշ3?*Vn0Ro<V=n"K@;8OX>8X>8zp,|p,|p,|p,_̱X\#~UO/=w-n$9;ρUw #Wa+mU Y5ÍdVjVmM`6a8vFR!`, *\;q!= 23ƐH!yyb6Kcm-;eǫ^T١XC >i k#(t?4N3wUsvgHyA!ƒdGl r?DU,y>&yRIތ]5A?@l-e V 46M|rJ b4f6OBSg^ |cIsQ[]t6eOrX՝ZyG01l9Bz==f+PzNyOԣ_P~=nɏ9Kb'˖{a ;Tf1]"5_QHJ]T.<#J=pw_Es48k.mG$-޻_bqd=HP#U{f+UzDRSK=#?a M?(Jr٥Ny E0(ظI‚jQi!V*[_jK[j9𨬗,d.f+Рsʲj[,0N @jJR%R^_cKi;^ 1d6'N 6I;0;XczJ)ZʅԣDGaR<Ak$ҦD,[v~g07i rz/ M(`e (zٟ6%r=^%b>-dc*Kb/8Yc6(}ڬSi=ex#ڞ4[)*Ranֺ:/ lɩ6& {aE@ÐmPsgH#Hyγ #'C8QىW״jØcLn6K$[P )2_Y0^6]Ϥ3$+˶U;EBѶ`-TCZAd& TSp Nu?e%zi|JqFzxZ2QYT!y83Zj4ȳ(z<{Xw5Bڰ'nH_: 4ۈ(7[42uQw; oQIYPwN>l+$YYo0:zKšM >v6ri"hW64-PifKkʋy=~0ze'TB'h8an%*=\U3*?k[`+ ::ѐ]'*(jI)q(`|&Mq4[ H.jfW`,7jPFiVtɝt0?a=fބ)VxDUCfWQld=g"Jdv(tũfq=v8}}WĿ{{N'L<ެWք WOc |?<) ]h+On!5 ُgkpڗ BR;(Fif?7x3U X7-[*K/ u|t>WU!ظDZ(-}(4A4E<*aG}Uj[t᪳Tu VqFl-~msw'uф&G¼\Al,ʲҪeC晄m//#˖70H|l^K(TF߶HmnZOij-N"SO@PWF~#٠E4/t~$JDJsu<~O(+K1I'gVC Sdj/RMN0좠P]5e;EkIR;lᾡ\^Hb@}K%3mpq[MK zZw!6R*nh@k@0XC ׿xÎ2K-!pzNgxv= laz'A*ӾK蔾U:I'6R⹈VEmD;} =4ۨǟՕ4nXҍoga. @NJl3x@4eԑPp Ak)ҦXTNy6(F Y]dZ;D8iN3uF*d3* %Tu{zNVMiqjx#Q 5n8aiyBXd׷ } RuȲMW/ñ&59H>Y>?\Cvz7[I($#r僓ekgl'LyG=EyBY:{jIR)8ԢWW,uRl߮~VpdD äؑɲDI8w$a'2_ɱQHX OGR*5=7~+,*$׋$-H$-˖[dfJ|Qna@> snar;]\hjt6X֋%YU jy 7և]ybN ٪J$1slzQZjgP~U Ra^vT-P 7ώjdF}\=䢮zPf@(L SEƜ8\e+)j8Q^70tLwXRN20Zs?;vH np"A,wLV!nɳ~nq6h),>A gYZga6~_$kIR iq/7V,[ZhA1xW_\}{uWW7_;XPi-4X!xɅrus3}[c(1"L=GDeC !MqACNAC?v@Ywf@wU=WK7$?M3atǀDE~ v5(΂&ҳmC$1^!̤)05&M}M1;9IqjSi;K"9v>]+uD, GS!!|AGB#ߠԲYv޼~W߾jog8X'b;['U++}?a#tC(Irc&0h*$$q5i~,ܙ,me& •8EV@s9*!i@ҢYX_ڙ)O [Hcxkb~[K.]J=nCU~@q@]۝,۝[2P(G$hK흳MqKs\n >v( F_s/x~o^ ~Ltlj0Lɲ S^g!rF xL@bB !N4 z}@^mͽ{-x WiZUsnh W/j[[mIV_osSs ߁ې뢽!B]`(L -M7G8eˎ~k17E'=I&9#IpۅNOS<[q%'%xlD6k`VA 3UKȲH1m&rUՔaOOQt O/OrS_נAS=移l3l>?"n[=+s=NuQۻ:/ջ|[q) _z HJcL ˍ\[dMH:= gdA HwVRGl|Uz/s^AUczfx,wZϞo;aZ NIzOw~[bsӒ7SD(K\ymHq4m6n ʃF`Kѷ?zWɯrH )(q ;T+0r<[K6Hrf+;h7|06nAGH=wַ9a "h=d?hz3 6 2wRvw~33qyLuph2UvZ8kDJ$ WC؅#{-KF%í\1~JI@4]=VrWG*5`.顧|G7u!GJG梽> |e+Ⱦ?i+Zx:B vN50jΔT e8.?֝C{!+'i5ڝܕkpgŏTF5кkST{= Nw"4NfS53s-,x$FbOͽtR$)i'ZͧY1-Y&U4$~Guujܦme~&:gRŌIek ]w6VT?ng);QϲYVV6\KiUL:cT9UyB{BQc˦ly<_e i)uG-,,4^fU TA9@ %yP$1 RVVE~!oLj Pq+KeIZ-,>xЖzfDl/R$3yjM1isd{* EFYu]hA7"W=aSa-LKԓI~E?) }\T9磉ΪR#ɌwG?/ %YbxR姶TnG/? (|TСǚ._K`mtÐ$wQ#@@!o}8i"?[hd{ZN[Oiy_җe= a9ayxX nxXA=<,<<,<<,a9}rzXN͇ex.S1IO_ yNX?؛{p.|6_hت x vQݺEf<l6}^Vv+6=VD(1ݶ?ns&I<WQ}_i ػG =]5W YNYn_ۏn# ^ia^k.w裲J=D7! ΑQ#}S޷Jf*[%Ʒb̟C{wn z3 i[ >*P6bdB?SfJ[ȑ}m%[7 7!IɚF8akjJ\M;qJM3Uk5J ,!$=(&UnnXzOEP_q9׵4B\:/_¥ogkE(xs@=*$WptJT DrkeL:Qlͻo_= { OYT`ro6SDv~>/fTCȧEօҦxoF?tDkzF;FlE"N鉜`^(D-ڴw*` 4%b.ΝQ|QzORKI:QX2Ǫ"p1a|D;޵"J$H{4`X]wΧHnSjI~U|Rp1O .哂*dyՎn~Cg=?U'"Egi7vK媰8ap-׏Wyxm-~0C/hBOק;kdSIUF&Miw6[ ?k#u=SORG|':U+ӯWR^%u(fxJJ$X։T7bTH%dI_ੋYh2$ 2UK$J)͈v9 0yi@ױ-δunxQ5-Rx^^FJ0'RW+'5MWQ5ĥ]IjtK<[Iu]qPw L/R+Aq[-ɱQ]ִ\=ꜫjUqj'43记 93`8d1Kfd| `l P$=η\m{ѪF֖͛Lqh(A]@(3Hފu,Ųd @M'AÀTIC6?=d CMYR+/k8%?ßiqx{_|{^$NA㑕3[raX&'c9_YSos®.қ%{#Cnh=l+@ RCԢ} bQHoH@,Qĉ6M&q18  RgAwbi#UlWQ?Uc^Zµ|LĤ2]>)#WUB7P|cЍa!(ONGfh`N`f&of$j#PIe[ȤZiQ=)-|Z{?Fm6Ư$ui=PnEݺt pZj(^81ĔՋ*L+b՞-\CEeӨ&[Oh~בJa- %մPWT[y|#KU1cSFPuz`NosNjm-0G0V[9]U=0͠c2%s]W-#&YuDU$ȅQca}\@;ֹ_sCGGșN08c!zdBz5i++: jZ&)/ɳi-@]ƹ[dicHIZkeirll\vx7l?Vص|tmuueвU&ChrRik1Sab]]rFW[L[otX"\&p'ZTιmtM!lY-BDaXkWAoP&tLD7BƏ[!59v[6 /<#W2W;0/Ro% $ k[Hh܆a;|76qCmOu˨k"߄4@M0zMXW_MӨJfH1HvB(53gl ^}nqqU][Uә3-LX|;3kiV]t=% 0'*Dl`RzRC&5Ēl>zӞu \UaIe=HTyΰ?9ʆ= >69:i {{V|#J L qB),1h/R$ѳ?:NN dBJmU3ݛ a] Q0XSȦK7K`"[|k"3*e8b~<$c J8c<0ŢHS7y_qX҆fvo?3;ß{d]ckE&Jl/~wb^Mz>cJ3 j05;mw%I:N&,E,krDHT#2'"1먰w;\资ɰ' 4U:)\3ÜD2RӐy0W3K:G||J`0O+g ~b6bmfő&Hn'ѫLq @e7yF6lu|З%0J9typWW-qt⸥[dIU}vXӞžcg܇ښVimYH !@D&: C.3R א#b.PE$a ,CdJ8D^·\!gc qӌkF3|N̆1Fz5f/ !%(W%C Һ<rB8޻ںfl8#Q*VR%\n:upU2`j#n"R`V$ƨk(b[a]"@#I=ߙۡے2lۋmo/]ۓmR1[5KHNJ":#b1 )xw^=x!d;cNNZP-Ri}/>k͕MoVLVKtF.olܟVы>3QHcuycAWabwrX2,8PfY_SغU3kd^"Zk( ͗kzvk2-ƽ-+d7RCix&[t·VChcsZ|+geP|a=,Mqu*@'YGs9پM%qѭNn=<[~ԡ,Sbg%M3r."֞(OСf^ͳ]awO+|Wp6bBn[fX&iذ:\)q3L(Єȱ`+UW3e8H 3n`bmU.Yǩߖ-δuG}u7n 1X}eVxe9pDVټsbN'H^B?xJCNTx%`xPpF_dݼ&dT[!:rbEvu,YSP ҏDD$+Ab.ߖ0-l{}yxz㗯6y3?0wlyAm^Y~۟~W(vocnhx8^Tg>wx%ŸtemN>wݬ E E0tE8{^MҤ+6:$]$r s$z]3RکgDgT z5>[n(/aCwg)!#.]z߇s^-g c MoC`.dVlwQdJe4v2gg3 S8/`?@OÌ2t%?+DH4)%7#|FS|Ka@ 93< = |_:\%},zAlwIn#UIfnٚxj=r2b9ʯH-́& fԊxwVюE""3`g}d$>jD$-gFΊiuZtawWezdkH:;OI1Hlav[`E0{LesM__߆;W2[ȏQG"vA<h4MRٌS{QLtpLy{,g>R)k>B/`VL8`ɹ٢yw,t.L+mL0U9Ʀ E)ku _R#5|f.^fR?.D`²c 1M?̊p+HJ1"}|i,m۲hfئ]VY'~Ni:IeWd$6mMbLYU6e̪$yhʶ׋IQ ^or⋻G?n^=pKzmMyv׋M[ʴZzMYmᏦצlUQ`:ߔy,Mguhu}SӮnzMtS?{s,ϊ^ue5OeAqzQMfMUWЋyiYK]ïOeI1rJѸGb嫲Y4}~̋bYyPNry-;o4ttQw(M#Ii^LVjjJ닊O^-86/څu1-g4rT5SM6e[/ڊڠQ,^K'mٜ$hWXz-V4hi3M%T-[bY-Yegie.'. s. >A]xuS4 0 ?,0 ,ٺ)0*EhmGsZZW''UWSpf[ZQꦒ-ۚ^:~+; l^Јe6).79"=MQ<_iA*[!po ]qn;:E:,r9qsx]Zj,X틚[<+3(D"6Zc,F sYK;{ZP'Y#%8Тf|g#w(-Ou[9l+E}w~p AZ,% &~#ML  ]Ϫ͔^ҿf]MOc[hIr[gkUM#zW//Nh/8<2OQt6tieV+25  KC``&'`Ҵ̢QoiYkY"$Mݔn#ƹFo\kƣ}]~s7Oe驌aF;_-/}ߔu]ԫG6qZ.,'9nēn<MEbQͥc/p_l$r[Iy̨duM"Ԇþf!ĬH1/p ?#!&m=.X\Ȧg ڏ}#lq_]R+O/H xh*^a.yv55Z%w#o+=!P+)Q=1JvyE"SFޕNBgωF̧U収G _ՇMF$&V,0B~龼$(WCģ!O3_:f ~ ]̅z%{mVH&1Qq^NA-~^(CL?O'1hY9lN?fUQo3^6V2k3p7`\BC~)Ty{ j8N}/z EYX tLK73Z=հ]XnE32 m9!H M.<Ñf̳UH׍<> r*ΎBT N*n*MobJL>׷_/ka2%/H_?m𜟝3 DُhsK~_mE1W.ydTG]*"ku]`\`nxΙVѺaK#5Jo_bSHs1]OgyA,tM(*cM3Ek< Dj;!ޘlJ_J>⽼Dky?@bvWPaQ{rB=j{.$s^wIH!_NWHhjzc˦ظEhw-KF;fR>2i/~ɞ65FlHbБlH/ ]S2̠IB&*=oofoY.o@$iO4drDWXfvg}i౵JZVlFBE.lCEQowo>+ iA,OAgt╸/B tGK>l-1Ɋ'hŎI- m}k}ʃw ^aLp9/t14%L_n(uji*,-WtabIUWGHf%][OȈώ^ȄVG'L9hL?v13b+$‚C.Ӷ ϘKӖ5:"y1CʑF)Ĺe32RT=_<9o4e,GJWxQr6,DOlz~l h1QAI'Qˏ6\dNgSgۛ.~w1)80 qє}u#Dk d? >zIsX͠Lh3TI>Δa]4ynڇSYF^p4ĥ/lvծhэ ! 1:)rK$MG(H%rsGmqʍ~kx`$҉EUOԬ}#xn{ dzfᎉ)wtUy /,R,Jg<>P2o`9^օMCE9dutV91Uv~? ^Yq!Sp gMQnw?2Xbh( mW,qhw!M1e1G-)%2kE/1xRܙ[c٬ ECcAv鱑b),joYRHM~N +VrO[#$^дD3 7B3h hs sFbO،$cnoٲ-H~g[ñ7`XyJi .DD 5K]1]Toq!!FU*bܦl/?LTuX-w W~fwDSs@-7-z^UԿ?U ,a+[#ooVffUqۻ+ɠ0SO\D@V~ઁ3#Ha#G"NJpMbHa|Ph)t n_"4BC0 !xV; mtGDaX3ODga웺&k &o-TڴLʬpF*3RYDD C+)/Rۛg+k%Dp`$|x'^Iu!vKOQoLZ+XhӢDIϖl(Ht6qsl Ig! QwG1YQyu|IHYe)z@;RƈCذo7wqb~|XOYma;ʸX4W_4K++"_z/t7o=T*3Ffx-#ͨlKc'*ae3:aUޟCV7}dȶmQ͋W[]"H=ŦȒ+; hrD21 oٴ:VklXgs[}ZMY^-=rĈF3Ve OFf2FzwU?q5 zfki < ^Ԑ0|: OOi3+s|G*hƘ^mZlo|u$RU$rc v5:,_,xj`Դ+6Jءl=KIe[#٬%hґjvfdm]>W^+PU!i<, i !$ㄞfH9nM{9 f3 вJ881pN7+DCEIT-1. it jr#g2#I)!q3LwDˌ-hDcB*oI\t$ga,kxQ>FagY}OPD,g$4/[ yɐsYa ޛaْٴ!#lOLZȧc_,=KF}(bSf&OMU:^D_ e`qǁ;h‰Eo[]MjXJv֊z#c,1{=@ b'䟏Ǚ$^P"N +W1A\HW&;}06Җ Oz}֭ī]9fQ PAro -cb6ROb@@T@PVzz q`=Cle3j7I3X_"LLy☍vjZ.'Т>݁9n㤫._}0GʔƑ5loLs!nioU!r K# ݲ> ȿUkL=(14BF8d5bUGG{܈]6.L3[^ 镪]!';kSsa;TZ{x^NVnժrvqE"z%żY_oX \k.\uveMsvC'9I}Éoj`Ad_uR{@YpdF?ίgov{C*fQ GlBϞBDZ36iVC`4^%Y>m0zjqMnҐI[F?u;bJutH`7 @_C6u.3gv[M̖Wp岶IlvAx < Ldkޤ3-y6cqL#,5d3qI\yzá)VˊSҔͽBZ X#y]b5%Mݵ0ZP{[CS ɝC&l\i]l8Ь"k㗐۳cT8qth$E#:L8(i^c+ 1+~ҫ.goƷ%$EYB[l=9Sp4J G@$#!#=ȁzQ  <#xctQ2Fodt]0}_ʵ=?(z|S \x!+E7Jgtx$]h2l]~mW=!0^9Jcjrb&tS!F~a"m(y/5v)AKA^ftoy`-ȡH8ԑpxI QQ.gf g1(ĺBNt!ˆFjHsb4ci ͉_;ܦ MabiH\HAP ~$PSLW,ǧs䰦c%R$~?V(sd<}O?Q#<8&Q;[f+=%;̚kZ:629|9{EN s&C6>@jJ7 0%3Z ƅM7KC9lGb'yk`܍ I7vORs!>Dq >_ZNKB9KBBt^E:qKO&?a~C{v^Pd82Cj~=:lok&xh3~s67nGg{XEk=ml@7@FYpxs3_\F$ sȈ 7g4 Ld.n-Kê`E*Gٲ '$##;kF -nVP54پ<@|w|<) K!W2;` VG/Ӌ&[;/_"yb|aLןO(mtPKKZK%F."t;et8ۂ5Hpb!vf\q ET`Zp[wUwy=F:TmwFW4}1t02=K'#y96Q^gm{؛smL0N3gI1 `Lj=3r{.Nj5;YL#"P3T@YOѥsY!ׯѧB Y^Ԉ>ZQ[HVDˬ[ynmK?]z )v R}or*NF`'IvX<^wפ\+0Rv&DD NV" گm>~L%.S"`~ĶA S }8#IHi&b# =vClvGWY"]N3&}bKQ[5 1ǭ^#^No{F XSLr< 68;ץZ >ZioFRGENu#W.&qG }!KQ+Fn 84mTSGo~~OeMً;,}ݍZZJo$rVl'5 GNKN %h!4Ȋ} #zC^`d-.䔯=f_{(Qx ˾]}D d zĹädH+bՈ]Ru!(BLsa % d>u<;WhaUlʸrVt]#=b=̛QFp |qDb ,4YFQm[4 Ǯ%UZ!df?D톢&G/+~:q@KiGΡI1vX GT=;nZ`^eOpnny9!hܰtmGPZwxc:5J(D0] ?̝߆(dn/"fw7rMպp 2mso=JJQ&+IȣM%%,`}DK.ry&41R'j}z& W 127.F~‰!ޜ:bn_EyhhBs F"85(:0(C ١hM+>/Lr1:M ?5 "p;O]1nqu#>%:} IO +s%dGIi>'P}n4]qu슉6+=RW1kbc/r N%tg ,:_(;֛ZPނE܂J|%V91 Zk)}0Pҕ2HtI_+(>$3aw?ow`lu.,1@XP9 1h$`dwX<ΤYi٥r4`qd]wr[(؄]%sa\#'S`>z: q@U 5lE\@/6 ;f^ l(P!|ub*VGӋbAcu뿟)=3X.m?{Z4]IƸFU \VuD+7?)# W]>D%$la={t=s* ms $ÝzA`}f{uC taX;,rG.j0:%X ]RUhnD^鼭aI'"@}0uMaxY``0rp|7CP'@Yr/l=W(hćWމZ`ġ]m )Ь;*Y4),ozή߭dt& pXVL%։No׏NoJjbZw~AKP 178F T+Ur@bub =nK'PSO@0Ųr#v\(+7Rj9m.tF.i!C[< sYjPOyBQdmpSUG|`Rtj pV&z)b/QCj IVqOMTNob65%%<%:'Bu_w7r5309fR%E xG{ߑ/"MPf=2>h|!D MRuYlGVcLt is0tHՌɶqsg9K2d0_3[\MA2t^ [0gˮhsTUW {"2y-*-͞L*z\:R]?{üf .#k QڵuWuG! pB-i/*6͂}XML.Í5VSڅ VxQF3xq/BԹSf=8|zxض=BQѴ9^,qX VKj:BU5&I:-*.ٻ"9Z.BC0,uZ=CkRjKkd0Au\~`~B/PϏ[W2,\@T4h8^Uzdacaۍ3afa%:]'O뗷>vz{#&C)MGIŕcŨ}>Vy8]V^ b$mB3\=4G+ߍBreꩫ役 ZQז;\#kZIDq`(䥸,BZt%#4#3p9tؿNDvWlجX@D5n\pgaT _jQꝽf/į7wJ!UUo$.n(x\(MPKJT@1|3G$ϦŲ-.^p /KNrD/{OVNWG5)mby~(uQ_s$?_ ;KU_'զӁ`%0L0D}]9PQ[,EeZ`ꂿu=M;l-H=b߸E* /T≿mnV87рDn=3^N#Ϛr4V2 XC<3,2?khz E{ŭ{l8!KkQ[Wי3s+Q"ZTƟȜ9Ér,8韣QF/ϓxևnU ,y+NQ!Ҳ9ΒetzF\y|Y5 lOZl㔸,1$ɳ#τCm[Yq28 ϙ.\F-EqAFJ Bl!6Ptm-մGXBRNY"F,Wsq4fW.s#_$1;@,@c N4,as08\] #MkQqFX H0 M;z=iz8xG8`)eeR}R0;dBc_6&fߦ\{A.ݐDwDmK&?~+w]H3l'Hgͼe|k-,^K?BV .6"E)p*=yL,xAv<5wBQ97- D_Te_G@/y.yk,j-`mJAd9[HY _ MsTt |t$Gpl }A@K:#Wcs2BvqBh}2_%zyZcbFe !Ɍpg~uO%О!;fq"fpf5zvW{g$. w"١5/tx9d-*ΰ#JJ.Qz's<+ہ{eNԡd{EK1+Wہ9# #Grl/eLn" (.g[C8'%&1Pf'6ܴD[߄m xzQvu=,d̢h,DbJEA'A4pTr21_~e}3L2ibe?}wh{ hA'k4'iiv: Z/NF$ɷ9n|\_9IG o){ҷ}rȖTݛ3ɑ~,ڝE6+1,Y+QfHIj5rE[IFjiVr&> SՄc1kb`Ȉ;'XHZ2:Q9e])ɷ̤nfMɋ8Cٻ.B"?VRȱQ;Hs{4W_:7]GZ4EM$ NbGv?']R/ ,{k }!JՔCvTM@rK:OcS8}ؚJa@v%P$OY+i|8D,C<qj ^; 4 tDglnq+ž[>'!#ЀY)v4T Eߗ}OmKv\E%OЍ5-@.+\+CPMq9}l:Tp6.D<**FnWqlڍb3ɃdIto>6G;KPDM؇WZ54/`Fy%18%,fMI(u9c+[ ŪQ䠺UA. ӡKwO~U=9d}b(P!؈<3KGNG] &%eEM@N1qX.M]z %*=NA eȥd4*[_rUl1EװZ.^Ἔjj&צ Mo|5Ӱ/yrnP>l,P8*©JXVr }(M໲ڼ?b$ӃOz(u3bP! )ة1JV6}65J7/8n/vJ}"ͬ?.YC#4Ec'{en `/Q\ŗkQtzI2 ͳמl?5zo#e^e]:1|FvC\bm|%Z p,uC#C-}wXG8ɚUӛ:<Δ@-U sI&/lBTS/eB[A`s4H/d3miQ7㉴lЖgt=?.0V-$<'bk%(gZ~g.\Dd"F7g/? ZPJM~u*GcMbC [i}ɷnj܉&j=dKiq_jF ͓YjL'׬O(-#/-V͜vo iDֿJ3i#M3"*\x# Ԣ` ޜZ[(pls. Y¢P9eH0:W44+u0(7/{OyUo6'sON v q6rt$rB.X!_BL 48HSc]UdtYsM񪱛mM{g`.wta23*xм}b3$&Jf"yN0[-?} 6"RXFfך"}v[l$%gDGD"\[s$=(e6i/4| 1"b~w!U*K,`v-#X$!L3+}pu<p?u@~>=x !m*o*lE)%MS&7 h7pmEX[D;ь]siY"o"u3dsGÜS+jD[2" s|؅~줧RCj=c,3/ UDȼ4\uu?GQ[=z CD(RhC199@1Mde4?do}rhf{8W>ZrWhȧ1?q/ 2>ŏ|ͣ/֋pٝ|#*0 +bDo|Y4 {?]3n.\1Zt/ 5Bc5Zcqwo|d"p>Y`A0RFǛs\T*ʞ띗ȅO)ۚ1={|yCӆ_~*h$^@؆/߻{o߰⟏g7@\%-)_fyţoy֤?nitz o/?N{- 6^hZœp ZHϪ3bgd8%GFP6X¶u$V/u2XlXSzybŦ׺"-do쇟XHdYvĴ>?aIڀ/vhMm?LYÀDo%6v$_z֙]VeX"& KDVMfNij5U~#(+EaXX; FTHH]_fX^8eR?R I@P, &l&x '7>!. U.$Sэ4ׁ;MŌX躤ĭaILbI"dO=w۞ytٌvERɱ  A,ZDAc`3nKD~wnӲ*6klNx J>hs^|r1͆|("w@0+I}Qz4{&Hl=wfnL<}ꫫ5"N)J׈ ݾl_9E`U>6$_|rӲ e8Aa"＜Z3!)P\DӘu/pʰYABF+|rW4>`@sƱq]<$ˉFΕM-MJ8͓^vqO ͇)\ >҃J5LB8p>~&%r9`ݟس((hN/ZNMWEgaWW]N6ى!{%!xkQ_TInp=_7Wťx߉Х~N{w|zg__!m 3C/u'4| jJh5۠^ LR[L AYPq"8G"DqyPlMGA>hKi.U#A*H"},qɍH9T~ \Iwܜ 3C\9{`|T:.*B=)$kSYpKҮqpa^C!!0xJ- IX TgN9 Nӟ`W*pL%;mۛ7}j ]kILʮ*1[9DCBnkawTJڢ5w ΂ͺ_LV<%G|3h#r7) ^6`A"߬p >A.venz{1JLxzConEBeg,[EZ[׃Zwq`n8V:k]#K>t208mv8z}R>bJ ߪBrZɠ5lDXu1"DG`9񋔻XC"2kq:FĢRZSXVî5yPP~x$<:ԘFRJY)ƒ`gGRY)|2Pi)yO-uh?AHM~T(ޯ{ƘFvV6U ).6)"^) oA,2"ĒT]Vo8?/̡a3ip*aYm ͠KmB ^aoD!=X.Ni3'+Dud2z_Y-AApŅO?Rߦ;\Lh+ΰ8uKQ z1i#X !g -J*adz2iGgwG?6YuDJΜE 9|PD { 0I%R6}6pNvlb( :|De{$Cwj(aqG 2WVN18į/Zx5"; ,HYHCqfhiyKpRO@=7m"7҄,I, ?>X2d6XqI\ G5P2M~}uCWnG'ACODCx-!oHq,Vܕr 1Q^޵q8M'FHKD)#4dAGN쓥a—6b/UVEnKzUP$d)t93Ē=˅dh=tZEx~GZ=6\8  $+jpE YHn1M.QCc}2 \5|&ǫmFQR,$h5.'lu+ٻ,cX2f@mm/Q11”iqw@R=Wȶ$^UBL=>z( G(*]utCFzoe9.2RQg+[q[.Wށ\:GCW-yhUqrg92pJ@<2Rc*\UfD[ +eכo+ T<֊~. \DM2wiAKr_  ]&X>`wiw^f(`_ W r6ҋ¼vBI`,l*'R#L⠰Eo#'-N>` }쥵p 89<Ӹe"^爫dr5ed(T& `4C늫ۋL]R#L`Egpύb6Yp3 "^\x6z1IPN M5pYoS9[}ys]=6*XtK4+HX˰b#>14^G.DoKge@I h v})>sioL%&"`@Nw.CLWЦ[P:VMd1j,B;p6 Ԙ V+茶ayϰ&*\alz:rfopc[Ꝫ7,¸Jr x%C54Ro53q% ZIn.IdLm4"'Js'ۧv@Go)NFmN1E +\98&KՄ%AEy9AdDCъqL|zu[6,) *kHY}N-}K8*tp(ak'D PUL#8n=pAC6: v4+zA>?C`YT}6p:z)p$0dbanð_8|eȸ -4wtﶸ'W_ȞF$qn#;796ϓC .'2 d)5 K:? p`=3jg[onj)a$fĦH&φ7bR5)Zr82ﶮ|L# u`}1|2a =x|CeQWvER?9붧/-7oN sLw?ygb0ʕ/,e~xg*gml<0HfXk{|d%(i99J9T(C[F^[|vυ]) n,X]'%4$ѧ! Ⱦ_6W9_}&{qfZRbZGk9%hq+'32*9^S Ğ,k顩l@,ЗN\XoB!gR@տǁ'ҍÏVw1>۠.|;-ڱ]{G>Z:òs0w5 қH9 i–sdeuĥU0xV1D@a W7Q"cOvZFZIhLFt$jVuL Hȋ}g`t8: :DǞEkH!9ٗ>/X  z᭛B f dBį >c3tc˗uJ;f Q 'K{#WBw(l? ;?(nٯm Do#}XxS`]AnZ/e2E$!Q7vv˂`OFZIA,SED{4qi`gWA|ZRIQZL'p;WZʰJؑas6qKEU6ɽ<$Q:P%z 4QFs?&.#d3T {BpẇûYI, bŴ~)aA TEJSfu]u@gQ۟K]?+a1DT&\ <1[Kpfˤc wyc]'+T:hl0wטX( K.28<MhBa,x tn [!ckmX)Cl[J JV X֕nNCBPe{ՆmIT)lb'izH0'?{R |Y|T*I'5PĘR#gbyw>pw&vl\$J`9REKв'񞗝q1g w ]{8 #r/&=H8_bÚM7uXh-򢽬ۙ[dԴGkREUqʳbťQɝُx3=bYIPyp~l GV$Vsث̘XB`4+<6>=Zs|wԩ|^!C7MUK$*L c_۩׮aeڣb!Hy ?4*s3`D@ȜPI൫N,ޞ%8\!9̋Wptb{0j>Krzp9\z[y4)B3UWu Ӊs._1&=s|YgU}Q+9T? )9yxy8ĎvաX=fGİb8ʌ#}9hDrqt*މ!9Տ{:1?qD*;*;^RY׎*(nvM_X.mˆ׮{W܏-۝8-LoL&10\ǁ]= YY]c]G<ɋJV0&sQْt/דRfӤ/%; ȭn([ZaR2TC 3@ZjC^\Pb>FQ6Ajuc{E}P@TbsG%1E/ci,B. ?!5PJ-yUzF)W)H\'/uuGfYo$S&O c1jUɫӍjZ{P$HM,"27mUWUCR3dƼp&ΥDS*2{ 8M .dG;Y.Y$rX Fヰ[`ljuֱp 6ƲJC¬ҷϡsum o9%S'cvNZ)l|8nE|u]7?(G!Ȥš0Yj11sUݖ!(XFA(@q/-䡐e:KoJv,=&CrRq J-a/]MvH[NFdwdW5dj: Ɖ1[%9H[ّ1F !VUk($CB>@Id%m D$-j-dXEo-R3״]gb4"y\O3a]aބs}ƈ#|/_cBg]rFU6?-#x6mnrhb\݃qz  ^|a :dˮ[ڂgZ81 3V'CQ,)qY@\I"k|ipQFv Q\*7SĬ+`r[a69|U [I7 ZqΦgsQNk›`s`kUL 8O5),?7sP[_|q'KҚf3XDY{.4,(+{XSۊa(o#sŤ@Cuwqs b O9TjK>K;[ll "~p5~SCa>5*U䢧T0$ *!-&y:WɁ8\\ +c3,"@H˅ٗ4^JTE  Q\]:)8RkST.%$j+p`L7%h@=8]`2n_ZfUr_W?~*Bnv]sVTj1z[2|-hhi.Oi@Qs& wKo%P ղQ+biA ԙ]Y \&c4k >x,~OaK} &ꪳ鯖,>jGy]GT`5yt[=l4DBSP (BZ! 'ETV\_æ [+  MC(yR)\["^n Y(` 2(8yӴ @.O#FLA5:BDS"R."uFfH . #Y@F:exQX{&Ӄw@E3=sEsssdYO9^ cIeD\s!rs1O(XlkH` p\O쫳b|Ke7&9Aw_-ܩ?}E<#AޓZu>1ڋ*ث,}Y ⦚S]M۬!%OvxU\+o$n5X,_|Ewnr}zs=bՋ*}8$9*dQ#C;hģ66?Z`ϋLO_-iʃԦ]}_4/ʋ 5+}>Έe* DΚSdɓvlB,nmZ,zE6mƗ|-g4O7e^_w_ϛ/I$ZgMks,Oʢj/HZ]mVzQhNX=6t7ncm*D u{S3wۮBHu؝v} B~N_zE~.B*S<ȯ'ڇr?~E,ŧ8,(j\-U</ѷޥ~򤷨DrJ.c" ᕙ B+qA.VA),Ҕ0в7O% Ml"h/Zu}sU.^%(;ε@𦚮2wE08oCh( .hݻQN߼k~Q$QGN#˱EKJ#݂rglZ~߱*ul&$qlKё8>e0kڵtV]VԧjM:6Bؓ.ԯ;!3V?>}74!b(1b3#D?{yZFnBC{~zũ?x1I,x)ۮeMrKjg]& ;|i crhr(<|A394sқ0nNԺX_!j~FS<(_Xp$98.P2LUۋ$șv3k(Ӆ`9Xқm Ψe* Gܩ^tܒ#IL)bVV,'۳zMYn`F֝ɨg#βcΤ&zD'q[vĺ5 9VI/sPo}"qZ諉>Ԭzo}%z *3SWq8AjZSb:L<csL)㑥Z),K=V]*PZb 6VMeVx.8 IV:D*3& ;.3 3 ;`TvH&qžXEkE>z4G9VEcOsҟ`t׷xz{wjj]~EVU^ìMូ5 ϫ+RanOn'FPTZrS_!]zu=3xǬt0܌TE95;Qy+`B 4h/ |'">~{EM +BHcmp7fKE~ K, Ϛί@!UF3P~PL;5t ƣ#C)uch2H}LR{2Բvs܈9X؜'f ep0{8'd0s z--E?oE\Ʌh=+(k8Ռzbv lsLNA*\nt159nRBwy۩l#̿֟ ;>W!{H]=%UݖG^ ~@y^Čҁʽ 6POFЇtAW#9Qlăx"QJըA@8n8OI6pXP63r Eado'T2_#]:d:[lі$zɉa,Ǥ!*(wAsBm.1eaCA=q]4̖Mxal8(g`!p ç$iٚ 8CݚMHYvM2̰Eȏ=ҿm5$X5CNRx\*9mR7BV H29vcN&aS$uΛNӸ0m\9He\W)qoIF K5 D3d&-˵(|>[CV1݅_T"Aziic͚%ύ9B@ 6>:(OE3c#YjQQn\Dvn^7~xI oԔ['+T;ukkt!ycMpbNt?Wb}Zg}>\]~9?aqe=oyMVơ4W|{0 n" 0˶%>UQXG6`?:.Z=2!/BtL-v zޮl[ 5ƚ,<(lV 0δl>R}GWgDt7-̤I1oo:&bFJ}3ܕR! ѝW1UEp,idi\=> =K<#3o!|Á:7,]/&"Zb]:냼vJmV_hzb/Bc/qe㊫:\1IۨZ^x4lnz6q&q# `xOEʒE fw:2y 7_TEDm:/;QMQb$U2_c|g$Y(f'e-]/$n͋^v8$ɇ2"x:uzv1&SO(ioՋ84[nLrX1qʈYV>k+UfCe]m+?}V;^CyAx;rbݬ mr\\y!G,S7PC0P/pIٿs]/H A:śZꜪUd./ۂ<\C9nf'ңތFjmli= s1z7Ӌvn/-]!Z]H 7ͦ yLW0W6wxwtYێjPQyٽH/.xXL UWʶBq.BȞfZQ#gC~)_DhT=㌆Rkl؁UE&8mro}1e #62?i@4^NyV!@HMYl6&j5]Bdlr7$$c%ɋM;6H}t5~"8e_$XZ K&bY_vpQck핣BE1Z3zh;ٺvu`3yZ.;LZr%"^ubuntu-policy/perl-policy.sgml0000644000175000017500000003701111054263224017263 0ustar cjwatsoncjwatson Debian Perl Policy Raphaël Hertzog Brendan O'Dea The Debian Policy mailing list debian-policy@lists.debian.org version 1.20 This document describes the packaging of Perl within the Debian GNU/Linux distribution and the policy requirements for packaged Perl programs and modules. Copyright © 1999, 2001 Software in the Public Interest

This manual 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 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.

A copy of the GNU General Public License is available as /usr/share/common-licenses/GPL in the Debian GNU/Linux distribution or on the World Wide Web at .

You can also obtain it by writing to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.

About this document

This document is distributed as the perl-policy files in the Debian package . It is also available from the Debian web mirrors at .

Perl Packaging Versions

At any given time, the package perl should represent the current stable upstream version of Perl revision 5 (see ).

Only one package may contain the /usr/bin/perl binary and that package must either be perl or a dependency of that package (see ).

Where possible, Perl should be compiled to provide binary compatibility to at least the last released package version to allow a grace period over which binary module packages may be re-built against the new package (see ).

The perl-base package must provide perlapi-version for all released versions it is compatible with.

Base Package

In order to provide a minimal installation of Perl for use by applications without requiring the whole of Perl to be installed, the perl-base package contains the binary and a basic set of modules.

As Perl is currently used by such things as update-alternatives and some package maintainer scripts, it must be priority required and marked as essential.

Note that the perl-base package is intended only to provide for exceptional circumstances and the contents may change. In general only packages which form part of the base system should declare a dependency on perl-base rather than perl.

Module Path

Perl searches three different locations for modules, referred to in this document as core in which modules distributed with Perl are installed, vendor for packaged modules and site for modules installed by the local administrator.

The module search path (@INC) in the Debian packages has been ordered to include these locations in the following order: site (current)

Modules installed by the local administrator for the current version of Perl (see ). /usr/local/lib/perl/version /usr/local/share/perl/version Where version indicates the current Perl version ($Config{version}see the Config module).

vendor

Packaged modules (see ). /usr/lib/perl5 /usr/share/perl5

core

Modules included in the core Perl distribution. /usr/lib/perl/version /usr/share/perl/version

site (old)

site directories (as above) for modules installed with previously released perl packages for which the current package is binary compatible are included if present.

In each of the directory pairs above, the lib component is for binary (XS) modules, and share for architecture-independent (pure-perl) modules.

Documentation

The POD files and manual pages which do not refer to programs may be split out into a separate perl-doc package.

Manual pages distributed with Perl packages must be installed into the standard directories: Programs

Manual pages for programs and scripts are installed into /usr/share/man/man1 with the extension .1.

Modules

Manual pages for modules are installed into /usr/share/man/man3 with the extension .3perl.

Locally Installed Modules Site Directories

The Perl packages must provide a mechanism for the local administrator to install modules under /usr/local but must not create or remove those directories.

Modules should be installed to the directories described above in as site (current), programs to /usr/local/bin and manual pages under /usr/local/man.

Site Installation

The following commands should be sufficient in the majority of cases for the local administrator to install modules and must create directories as required: perl Makefile.PL make install

Packaged Modules Vendor Directories

The installation directory for Debian modules must be different from that for core and site modules.

The current Perl packaging uses the vendor directories for this purpose, which are at present as described in as vendor.

No version subdirectory exists on these directories as the dependencies for packaged modules (see ) should ensure that all work with the current perl package.

The Perl distribution includes many modules available separately from CPAN, which may have a newer version. The intent of the @INC ordering (described in ) is to allow such modules to be packaged to vendor which take precedence over the version in core. A packaged module which shadows a core module in this way must be a newer version.

Module packages must install manual pages into the standard directories (see ) using the extensions .1p and .3pm to ensure that no conflict arises where a packaged module duplicates a core module.

.packlist files should not be installed.

Module Package Names

Perl module packages should be named for the primary module provided. The naming convention for module Foo::Bar is libfoo-bar-perl. Packages which include multiple modules may additionally include provides for those modules using the same convention.

Vendor Installation

A module should use the following lines in the debian/rules build targetThe environment variable PERL_MM_OPT may be used to pass the INSTALLDIRS=vendor option in cases where Makefile.PL is not invoked directly from debian/rules: perl Makefile.PL INSTALLDIRS=vendor $(MAKE) OPTIMIZE="-O2 -g -Wall" and this one to install the results into the temporary tree: $(MAKE) install PREFIX=$(CURDIR)/debian/<tmp>/usr

Replace <tmp> with the appropriate directory (nominally just tmp)

A Build-Depends on perl (>= 5.6.0-16) is required.

Module Dependencies Architecture-Independent Modules

Architecture-independent modules which require core modules from the perl package must specify a dependency on that package.

Modules which contain explicit require version or use version statements must specify a dependency on perl or perl-base with the minimum required version, or more simply the current version.

In the absence of an explicit requirement, architecture-independent modules must depend on a minimum perl or perl-base version of 5.6.0-16 due to the changes in @INC introduced by that version.

Binary Modules

Binary modules must specify a dependency on either perl or perl-base with a minimum version of the perl package used to build the module, and must additionally depend on the expansion of perlapi-$Config{version} using the Config module.

Automating Perl Dependencies

Rather than hard-coding the dependencies into the control file, using a substitution such as ${perl:Depends} is suggested. This allows the dependencies to be determined at build time and written to the substvars file in the form perl:Depends=deps.

Please note that dependencies caused by versioned uses and on separately packaged modules are not included in this variable and must be explicitly included.

Packages built with debhelper may use to generate this substitution automatically. This additionally requires a versioned Build-Depends (or Build-Depends-Indep) on debhelper (>= 3.0.18).

Perl Programs Script Magic

All packaged perl programs must start with #!/usr/bin/perl and may append such flags as are required.

Program Dependencies

Programs which require core modules from the perl package must specify a dependency on that package.

Programs which contain explicit require version or use version statements must specify a dependency on perl or perl-base with the minimum required version, or more simply the current version.

As with modules, packages using debhelper may use to automatically generate dependences (see ).

Programs Embedding Perl Building Embedded Programs

Programs which embed a perl interpreter must declare a Build-Depends on libperl-dev.

The default linker options produced by perl -MExtUtils::Embed -e ldopts will link against the dynamic libperl. If programs wish to link to the static library, then -lperl should be changed to /usr/lib/libperl.a in those options.

Embedded Perl Dependencies

Dependencies for programs linking against the shared Perl library will be automatically created by dpkg-shlibdeps. Note however that the shared perl library package only suggests perl-base and packages requiring any core modules from the perl package must depend upon it explicitly.

Perl 6

The current stable upstream version at the time of this writing is 5.6.0. There is currently work in progress on the next major revision, although the specifications have yet to be finalised.

It is anticipated that when Perl 6 is released it will initially be packaged as perl6, install the binary as /usr/bin/perl6 and use different directories for packaged modules to perl: /usr/lib/perl6 /usr/share/perl6 This will allow Perl 5 and 6 packages and modules (which should be packaged as libfoo-bar-perl6), to co-exist for as long as required.

At some stage in the future when Perl 6 is sufficiently mature, the package naming may be reversed such that the perl package contains Perl 6 and the current package becomes perl5.

ubuntu-policy/ubuntu-policy.desc0000644000175000017500000000151311061230113017602 0ustar cjwatsoncjwatsonDocument: ubuntu-policy Title: Ubuntu Policy Manual Author: The Debian Policy Mailing list; the Ubuntu Developers Mailing list Abstract: This manual describes the policy requirements for the Ubuntu distribution. This includes the structure and contents of the Ubuntu archive, several design issues of the operating system, as well as technical requirements that each package must satisfy to be included in the distribution. Section: Ubuntu Format: debiandoc-sgml Files: /usr/share/doc/ubuntu-policy/policy.sgml.gz Format: text Files: /usr/share/doc/ubuntu-policy/policy.txt.gz Format: HTML Index: /usr/share/doc/ubuntu-policy/policy.html/index.html Files: /usr/share/doc/ubuntu-policy/policy.html/*.html Format: PostScript Files: /usr/share/doc/ubuntu-policy/policy.ps.gz Format: PDF Files: /usr/share/doc/ubuntu-policy/policy.pdf.gz