Differences between revisions 1 and 96 (spanning 95 versions)
Revision 1 as of 2007-08-14 06:38:44
Size: 1365
Editor: FranklinPiat
Comment: Initial Page
Revision 96 as of 2011-05-09 18:53:37
Size: 62874
Editor: JustinBRye
Comment: an entry for X
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
||<tablestyle="align:left">Jump to :[[BR]][[TableOfContents(1)]]||
[[Anchor(0)]]
= 0 =
 0 : see also [#root"]

[[Anchor(A)]]
#language en
||<tablestyle="float:right; width:160px; background:transparent; margin: 0 0 1em 1em;" style="padding:0.5em; border-style:none;"> {{attachment:Debian_Jargon-160x160.png}} ||
<<BR>>
''Debian Glossary Only.''

If you don't find the entry you wanted be/low, check
 * PolicyGlossary
 * [[http://www.jargondb.org/|jargondb.org]]
 * [[http://kernelnewbies.org/KernelGlossary|kernelnewbies.org]]'s Kernel Glossary
 * [[http://www.tldp.org/LDP/Linux-Dictionary/html/index.html|tldp.org]]'s Linux-Dictionary
 * [[http://www.wikipedia.org|wikipedia.org]]
 * [[http://en.wiktionary.org/|wiktionary.org]]
 * or simply try it as a wiki pagename!

Or you can add it yourself. If you can't define it yourself you can put ''ToDo'' instead, but always check the sites mentioned above - if it isn't Debian-specific, an existing definition elsewhere is likely to be more helpful.

||<tablestyle="text-align:center;background-color:#ddd;width:100%">Jump to : [[Glossary#A|A]] [[Glossary#B|B]] [[Glossary#C|C]] [[Glossary#D|D]] [[Glossary#E|E]] [[Glossary#F|F]] [[Glossary#G|G]] [[Glossary#H|H]] [[Glossary#I|I]] [[Glossary#J|J]] [[Glossary#K|K]] [[Glossary#L|L]] [[Glossary#M|M]] [[Glossary#N|N]] [[Glossary#O|O]] [[Glossary#P|P]] [[Glossary#Q|Q]] [[Glossary#R|R]] [[Glossary#S|S]] [[Glossary#T|T]] [[Glossary#U|U]] [[Glossary#V|V]] [[Glossary#W|W]] [[Glossary#X|X]] [[Glossary#Y|Y]] [[Glossary#Z|Z]] ''~-Symbols:-~'' [[Glossary#Dot|.(dot)]] ||

## not really used as jargon, let alone being Debian-specific
##<<Anchor(0)>>
##= 0 =
## 0 :: uid 0, see also [[#root|root]]
 
<<Anchor(A)>>
Line 9: Line 27:
[[Anchor(B)]] <<Anchor(advocate)>>
 Advocate :: A [[#debian-member|Debian member]] who advocates an application. Advocates should know the [[#applicant|applicant]] fairly well and should be able to give an overview of the applicant's work, interests and plans. Advocates are often the [[#sponsor|sponsors]] of an applicant.

<<Anchor(alioth)>>
 Alioth :: [[Alioth]] is a collaborative development environment based on the [[http://fusionforge.org|FusionForge]] software as a service for the Debian project and community.

<<Anchor(alioth-account)>>
 Alioth (guest) account :: People willing to participate in the packaging or development of a software can ask for an [[#alioth|Alioth]] ''guest'' account, then ask for commit rights to a given project.

<<Anchor(alpha)>>
 Alpha :: A [[#port|port]] (formerly a [[#release-architecture|release architecture]]) using the Linux kernel on (Compaq/Digital) Alpha hardware

<<Anchor(am)>>
 AM :: See [[#application-manager|Application Manager]]

<<Anchor(amd64)>>
 Amd64 :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the Linux kernel on 64bit PCs - technically x86-64 or AMD64 or Intel64, nontechnically most new consumer PCs

<<Anchor(anais)>>
 ANAIS :: Short for "Architecture Not Allowed In Source"; used in bug reports for [[http://wiki.debian.org/ftpmaster_Removals|package removal]], usually indicating that the number of architectures for which the package is to be built has been reduced
## a much cooler way to get your pin-up's name into the project

<<Anchor(applicant)>>
 Applicant :: A person requesting membership in the [[#debian-project|Debian project]]; prospective [[#debian-developer|Debian developer]].

<<Anchor(application-manager)>>
 Application Manager (AM) :: A [[#debian-member|Debian member]] who is assigned to an [[#applicant|applicant]] to collect the information needed by the [[#debian-account-manager|Debian account managers]] to decide about an application. One application manager can be assigned to more than one Applicant.

<<Anchor(apt)>>
 APT :: Debian's Advanced Package Tool (or perhaps Advanced Packaging Tool - neither is "official"), a library that handles fetching the list of packages, resolving package dependencies, etc. It then uses [[DebianPkg:unstable/dpkg|dpkg]] to perform the actual package installation, removal, etc. The package [[DebianPkg:unstable/apt|apt]] provides the commandline tools [[DebianMan:1/apt-get|apt-get]] and [[DebianMan:1/apt-cache|apt-cache]], but other APT front-ends exist such as [[DebianPkg:unstable/aptitude|aptitude]] and [[DebianPkg:unstable/synaptic|synaptic]].

<<Anchor(architecture)>>
 Architecture :: The type of system a piece of software is built for:
##
 * (Not Debian-specific) a general category of hardware (such as "486" or "little-endian"), or a variant of some piece of software tailored for this hardware; may specifically mean the category as determined by some particular tool, such as [[DebianMan:1/arch|arch]] or [[DebianMan:1/dpkg-architecture|dpkg-architecture]]
 * One of the platforms for which Debian [[#package|package]]s are built, known by labels such as [[#amd64|amd64]] or [[#mipsel|mipsel]], and also differentiated by the OS kernel used - the same hardware (not literally an Intel 386 processor) may dualboot [[#i386|i386]] and [[#kfreebsd-i386|kfreebsd-i386]] architectures. See also [[#port|port]], [[#release-architecture|release architecture]]

<<Anchor(archive)>>
 Archive :: A set of files:
##
 * (Not Debian-specific) a set of items combined into one file, such as a tarball or [[#dotdeb|.deb]] file (technically an [[DebianMan:1/ar|ar]] archive)
 * A set of files, such as a software repository
 * Used as a synonym for [[#suite|suite]] by (e.g.) [[DebianPkg:unstable/aptitude|aptitude]] - "`aptitude search '~i?archive(backports)'`")

<<Anchor(area)>>
 Area :: The term used in [[http://www.debian.org/doc/debian-policy/ch-controlfields.html|Debian Policy]] for the [[#main|main]], [[#contrib|contrib]], and [[#non-free|non-free]] divisions of the repositories (also known as [[#component|component]]s)

<<Anchor(arm)>>
 Arm :: A [[#port|port]] (superseded by [[#armel|armel]] and no longer maintained) using the Linux kernel on ARM/StrongARM hardware, a CPU type originally created for the Acorn Archimedes

<<Anchor(armel)>>
 Armel :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the Linux kernel on little-endian ARM/StrongARM chips, now common in embedded/mobile devices

<<Anchor(armhf)>>
 Armhf :: A (work-in-progress) [[#port|port]] (on [[#debports|debports]] but not yet a [[#release-architecture|release architecture]]) using the Linux kernel on newer ("hard-float") [[#armel|armel]]-style hardware with an FPU

<<Anchor(avr32)>>
 Avr32 :: A (work-in-progress) [[#port|port]] (on [[#debports|debports]] but not yet a [[#release-architecture|release architecture]]) using the Linux kernel on Atmel's 32-bit RISC architecture
## whatever that is

<<Anchor(B)>>
Line 12: Line 90:
[[Anchor(C)]] <<Anchor(backports)>>
 Backports :: [[Backports]] are versions of [[#package|package]]s from [[#testing|testing]] and [[#unstable|unstable]] that have been rebuilt to be able to install and run on the [[#stable|stable]] [[#distribution|distribution]].

<<Anchor(base-system)>>
 Base system :: [[#binary-package|binary package]]s with [[#priority|priority]] required or important; a minimalist set of packages installed before everything else on a new system. Designed to provide just the things you'd be surprised to find missing on a usable UNIX system. Not to be confused with [[#essential|essential]], which is much smaller.

<<Anchor(bd-uninstallable)>>
 BD-Uninstallable :: a [[#wanna-build|wanna-build]] state

<<Anchor(binary)>>
 Binary :: Several potentially confusing (but non-Debian-specific) meanings:
##
 * Any non-textfile, such as a JPEG format image
 * Any ELF executable (often used generically to include shellscripts and other non-binary executables normally found in a `bin` directory)
 * The output of a build process - see [[#binary-package|binary package]]

<<Anchor(binary-package)>>
 Binary package :: An installable [[#dotdeb|.deb]] file as opposed to the [[#source-package|source package]] it's built from. The idea is that this is the "binary" compiled in the package building process (regardless of whether the output .deb contains a [[#binary|binary]] executable, documentation, or indeed Linux kernel [[#source|source]]code).

<<Anchor(binnmu)>>
 BinNMU :: a binary-only [[#nmu|non-maintainer upload]] - see [[binNMU]]

<<Anchor(bo)>>
 Bo :: The codename for Debian 1.3, [[#release|release]] date: 1997

<<Anchor(bof)>>
 BoF :: Short for "[[http://en.wikipedia.org/wiki/Birds_of_a_Feather_(computing)|Birds of a Feather]]"; a common type of discussion session held at [[#debconf|DebConf]]

<<Anchor(bsp)>>
 BSP :: Short for "[[BSP|Bug Squashing Party]]"; a get-together of Debian enthusiasts (either virtual or In Real Life) for the purpose of fixing as many bugs as possible.

<<Anchor(bts)>>
 BTS :: Short for "[[http://www.debian.org/Bugs/|Bug Tracking System]]"

<<Anchor(bts-link)>>
 BTS-link :: A system for synchronizing bug status in the Debian [[#bts|BTS]] with bug tracking systems like Bugzilla. See [[http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html|this mail]].

<<Anchor(building)>>
 Building ::
##
 * a [[#wanna-build|wanna-build]] state
 * (Non-Debian-specific) A piece of architecture in the non-jargon sense

<<Anchor(build-essential)>>
 Build-essential :: The only package that's literally essential for a Debian package build is [[DebianPkg:unstable/make|make]] (because Policy mandates the use of a Makefile), but the "build-essential" toolkit is a convenient short-cut: a standard set of packages defined to be required for all '''normal''' Debian packaging work, which can therefore be omitted from lists of build dependencies as obvious, just as [[#essential|essential]] packages are omitted from install-time dependencies.

<<Anchor(buzz)>>
 Buzz :: The codename for Debian 1.1, [[#release|release]] date: 1996

<<Anchor(C)>>
Line 15: Line 142:
[[Anchor(D)]] <<Anchor(cdbs)>>
 CDBS :: Short for "Common Debian Build System" (provided by [[DebianPkg:unstable/cdbs|cdbs]])

<<Anchor(component)>>
 Component :: The term used in [[DebianMan:5/sources.list|sources.list(5)]] for the [[#main|main]], [[#contrib|contrib]], and [[#non-free|non-free]] archive [[#area|area]]s

<<Anchor(conffile)>>
 Conffile :: A technical term defined in Policy; a file declared in a package's {{{conffiles}}} file is treated specially by [[DebianPkg:unstable/dpkg|dpkg]] to ensure that local modifications are not blindly overwritten by a package [[#upgrade|upgrade]] or deleted by a [[#remove|remove]]. Conffiles are (always?) stored in `/etc`, and are often conventional global [[#configuration-file|configuration file]]s but may also be initscripts, cronjobs, or similar.

<<Anchor(configuration-file)>>
 Configuration file :: Any file affecting the operation of a program, or providing site- or host-specific information, or otherwise customizing a program's behavior. May or may not be system-wide, or in an intelligible line-oriented text format, or marked as a [[#conffile|conffile]]. Personal configuration files are traditionally stored as dotfiles in the home directory (see also [[#rc|rc]]-file).

<<Anchor(contrib)>>
 Contrib :: Additional, external software, in either of two senses:
##
 * In various project upstreams, a collection of extra software produced by third parties and included into a distribution "without warranty"
 * in Debian, software that is itself [[#dfsg|DFSG]]-compliant but requires software in [[#non-free|non-free]] to build or run usefully (or the archive [[#area|area]] such software is separated out into).

## for the above the formatting fails if you take out the comment line
## for the following everything just works the way it's supposed to
## that reminds me, I should add an entry for WTF

<<Anchor(control-file)>>
 Control file :: As defined in [[http://www.debian.org/doc/debian-policy/ch-controlfields.html|Debian Policy]]:

 * The `control` file included in the `debian` directory of each [[#source-package|source package]] contains dependency information required to build the package, and has separate stanzas containing further information for each [[#binary-package|binary-package]]
 * The `control` file included in the `DEBIAN` directory of each binary [[#dotdeb|.deb]] (formed from the corresponding stanza in the source `control` file) contains dependency information required to install the package, plus the package description etc.
 * Any "control file"; that is, any file with the same multi-field syntax as the above - for instance, [[#dotdsc|dsc]] files are also counted as control files.

<<Anchor(custom-debian-distribution)>>
 Custom Debian Distributions (CDD) :: The old name for subsets of Debian configured to support a particular target group out-of-the-box. Now known as [[#debian-pure-blend|Debian Pure Blends]]

<<Anchor(D)>>
Line 18: Line 177:
[[Anchor(d-i)]]
[[Anchor(D-I)]]
 D-I :: see [#Debian-Installer]

[[Anchor(Debian-Installer)]]
 Debian-Installer :: Debian Installer is the set of program used to install Debian on your hard disk "The first day". '''It is not''' the program you use to install (add|remove) more program (packages) once Debian Installed (see [#Apt]).

[[Anchor(E)]]
<<Anchor(dak)>>
 Dak :: (Short for "Debian Archive Kit") The toolset used to manage the Debian repositories - see [[DakHowTo]]

<<Anchor(dam)>>
 DAM :: See [[#debian-account-manager|Debian Account Manager]].

<<Anchor(dd)>>
 DD :: See [[#debian-developer|Debian Developer]]

<<Anchor(ddp)>>
 DDP :: Short for the "[[http://www.debian.org/doc/ddp|Debian Documentation Project]]"

<<Anchor(ddpo)>>
 DDPO :: The [[http://qa.debian.org/developer.php|Debian Developer's Packages Overview]], which lists the [[#package|package]]s maintained by a Debian Developer or Team

<<Anchor(debcamp)>>
 DebCamp :: See [[DebCamp]]; the hacking session right before [[#debconf|DebConf]]

<<Anchor(debconf)>>
 Debconf :: Two things distinguished by capitalization:
##
 * `debconf`, a ([[DebianPkg:unstable/debconf|package]] providing a) [[DebianMan:1/debconf|utility]] for performing configuration tasks, closely integrated with [[DebianPkg:unstable/dpkg|dpkg]]
 * DebConf, the Debian Project's annual convention; see [[http://www.debconf.org/]]

<<Anchor(debian-account)>>
 Debian Account :: Typically the login account of a [[#debian-developer|Debian Developer]], but sometimes also used to refer to a [[#debian-maintainer|Debian Maintainer]] account. See also [[#alioth-account|Alioth account]].

<<Anchor(debian-account-manager)>>
 Debian Account Manager (DAM) :: A [[#debian-member|Debian member]] who has been delegated by the [[#debian-project-leader|Debian project leader]] to manage [[#debian-account|Debian account]] creation and removal. The DAM has the final decision over an application.

<<Anchor(debian-contributor)>>
 Debian Contributor :: a general term for active members of the Debian community, whether or not they have [[#debian-developer|DD]] status; sometimes used to mean the status of a non-uploading [[#debian-developer|DD]] (as recognised by [[http://www.debian.org/vote/2010/vote_002|general resolution]]).

<<Anchor(debian-developer)>>
 Debian Developer (DD) :: A [[#debian-project|Debian Project]] member who has gone through the [[#new-maintainer|New Maintainer]] process and had their application accepted is called a [[DebianDeveloper|Debian Developer]].

<<Anchor(debian-documentation-project)>>
 Debian Documentation Project :: A Debian sub-project covering various documentation issues. See [[http://www.debian.org/doc/ddp]]

<<Anchor(debian-installer)>>
 Debian Installer (D-I) :: Debian Installer is the software used to initially install Debian on your hard disk. This should not be confused with the software used to [#install|install]] extra [#packages|packages]] on a running Debian system (see [[#apt|APT]]).

<<Anchor(debian-maintainer)>>
 Debian Maintainer (DM) :: The status of a person who has passed the [[DebianMaintainer|Debian Maintainer]] process. A Debian Maintainer is granted some rights to manage packages, in particular the right to upload packages to the [[#debian-archive|archive]]. DMs aren't voting members of the Debian Project. See also [[#debian-developer|Debian Developer]], [[#alioth-account|Alioth account]]. Not to be confused with the role of package [[#maintainer|Maintainer]].

<<Anchor(debian-member)>>
 Debian Member :: Full members of the [[#debian-project|Debian Project]] are referred to as [[#debian-developer|Debian Developers]]. (ToDo: link to one coherent central explanation of the distinction between contributors, developers, maintainers, and uploaders, assuming there is one)

<<Anchor(debian-new-maintainer)>>
 Debian New Maintainer :: The process of becoming an official [[#debian-developer|Debian Developer]] (DD), or a person going through that process. See also [[#applicant|Applicant]].

<<Anchor(debian-policy-manual)>>
 Debian Policy Manual :: The document that describes what packages should contain, how they should be configured, and generally how packages fit together to create a Debian system.

<<Anchor(debian-project)>>
 Debian Project:: An organization of free software developers spread around the world with a common goal, to produce a completely [[#free|free]] operating system. See the [[http://www.debian.org/intro/about|Debian web pages]] for more information.

<<Anchor(debian-project-leader)>>
 Debian Project Leader (DPL) :: the official representative of the Debian Project to the outside world, with internal managerial and coordinatory duties; elected annually. See [[http://www.debian.org/devel/leader]]

<<Anchor(debian-pure-blend)>>
 Debian Pure Blends :: A subset of Debian that is configured to support a particular target group out-of-the-box. [[DebianPureBlends|Debian Pure Blends]] were formerly known as Custom Debian Distributions (CDD).

<<Anchor(debian-security-advisory)>>
 Debian Security Advisory (DSA) :: A warning message sent to the [[http://lists.debian.org/debian-security-announce|debian-security-announce mailinglist]] about a security alert for Debian software with available fixes. Not to be confused with the [[#debian-system-administrators|DSA team]].

<<Anchor(debian-system-administrators)>>
 Debian System Administrators (DSA) :: The [[Teams/DSA|Debian System Administrators]] team, who handle the basic infrastructure of the project. Not to be confused with [[#debian-security-advisory|DSA messages]].

<<Anchor(debports)>>
 Debports :: [[http://www.debports.net]], a site hosting unofficial [[#ports|ports]] that have yet to qualify as [[#release-architecture|release architecture]]s and be integrated into the main archives

<<Anchor(dehs)>>
 DEHS :: Short for "Debian External Health Status" (see [[DEHS]]).

<<Anchor(dep)>>
 DEP :: Short for "[[http://dep.debian.net/deps/dep0|Debian Enhancement Proposal]]", an RFC-like mechanism for planning efforts within the [[#debian-project|Debian Project]]

<<Anchor(dep-wait)>>
 Dep-wait :: (Plus more rarely dep-wait-removed) A [[#wanna-build|wanna-build]] state

<<Anchor(dependency-package)>>
 Dependency package :: An empty [[#binary-package|binary package]] that exists only for the sake of its declared dependencies on other packages, for instance to keep the current default version of [[DebianPkg:unstable/gcc|gcc]] installed. See [[#metapackage|metapackage]] and [[#transition-package|transition-package]] for other common types.

<<Anchor(dfsg)>>
 DFSG :: Short for the "Debian Free Software Guidelines"; the rules of thumb included in the [[http://www.debian.org/social_contract|Debian Social Contract]] that can be used to judge whether material counts for the [[#debian-project|project]]'s purposes as [[#free|free]]. The string `dfsg` is often appended to [[#package|package]] names and version-strings to indicate that the upstream version has been slightly modified to allow it to stay in [[#main|main]].

<<Anchor(d-i)>>
 D-I :: See [[#debian-installer|Debian-Installer]]

<<Anchor(distribution)>>
## LC_COLLATE=en_US rather than C, so d-i < distr < dist-u
 Distribution (dist) ::
##
 * (Not Debian-specific) the complete set of software from one upstream project, considered as a unit. MacTeX is a TeX distribution, for instance, whereas NetBSD is a full Operating System distribution. This is the sense in which Debian is "a distribution".
 * A [[#suite|suite]] within the Debian repositories capable of providing a fully functional OS on its own, unlike the supplementary ones such as "[[#testing-security|testing-security]]". This is the sense in which [[#stable|stable]] is "a distribution".
 * Used more generally (e.g. in [[DebianMan:5/sources.list|sources.list(5)]]) as a synonym for [[#suite|suite]]; hence [[#source|source]] URLs which put `http://ftp.debian.org/debian/dists/experimental/` alongside all the other `dists`.

<<Anchor(dist-upgrade)>>
 Dist-upgrade ::
##
 * In Debian package management, the process of migrating a whole system from one [[#release|release]] to the next (dist-upgrades skipping a release are not supported)
 * In [[DebianPkg:unstable/apt|apt]] specifically, an action that makes relatively aggressive (but intelligent) attempts to bring the system fully up to date, even if this requires some changes to the list of installed packages (that is, it may automatically install, remove, or replace packages). Compare plain [[#upgrade|upgrade]], and [[DebianPkg:unstable/aptitude|aptitude]]'s [[#full-upgrade|full-upgrade]].

<<Anchor(dm)>>
 DM :: See [[#debian-maintainer|Debian Maintainer]].

<<Anchor(dmup)>>
 DMUP :: Short for "Debian Machine Use Policies"; the [[http://www.debian.org/devel/dmup|documented]] Acceptable Use Policy for machines on the Debian network.

<<Anchor(downgrade)>>
 Downgrade :: An action not officially supported in Debian package management, though often possible (and where it isn't, a [[#purge|purge]] and reinstallation of the older version is often good enough).

<<Anchor(dpl)>>
 DPL :: Short for "[[#debian-project-leader|Debian Project Leader]]"

<<Anchor(dpmt)>>
 DPMT :: The [[Teams/PythonModulesTeam|Debian Python Modules Team]], who work to improve the Python modules situation in Debian.

<<Anchor(dsa)>>
 DSA :: Short for either "[[#debian-security-advisory|Debian Security Advisory]]" or "[[#debian-systems-administrators|Debian Systems Administrators]]"

<<Anchor(E)>>
Line 28: Line 302:
[[Anchor(F)]] <<Anchor(essential)>>
 Essential :: A set of packages providing the absolute minimal functionality that must be available and usable on the system at all times. The idea is, if you're hit by a software or hardware failure halfway through an [[#upgrade|upgrade]], leaving your package database in an inconsistent state, the essential packages should still work well enough to let you perform repair work.

<<Anchor(etch)>>
 Etch :: The codename for Debian 4.0, [[#release|release]] date: 2007

<<Anchor(experimental)>>
 Experimental :: The [[DebianExperimental|experimental]] repository is an incomplete [[#distribution|distribution]] which developers can use to try out versions of software not intended to migrate to [[#testing|testing]], and which users are warned not to install

<<Anchor(F)>>
Line 31: Line 314:
[[Anchor(G)]] <<Anchor(failed)>>
 Failed :: (Plus more rarely failed-removed) A [[#wanna-build|wanna-build]] state

<<Anchor(fhs)>>
 FHS :: See [[#filesystem-hierarchy-standard|Filesystem Hierarchy Standard]].

<<Anchor(filesystem-hierarchy-standard)>>
 Filesystem Hierarchy Standard (FHS) :: the [[FilesystemHierarchyStandard]] defines the main directories and their contents in Linux and other Unix-like computer operating systems. The [[#debian-policy-manual|Debian Policy Manual]] only explains the exceptions applying to Debian.

<<Anchor(free)>>
 Free :: Compliant with the [[#dfsg|DFSG]], and eligible to go in [[#main|main]]

<<Anchor(freeze)>>
 Freeze :: The distribution development freeze is a period of time when the [[#debian-project|Debian Project]] is working to finalize and stabilize the content of the [[#testing|testing]] [[#distribution|distribution]] (resolving release critical bugs, making final tweaks to [[#debian-installer|Debian-Installer]], deciding the contents of the CDs, etc.) before its [[#release|release]] as the new [[#stable|stable]]. Debian's release policy is one of ''Release when Ready'', so the length of the freeze period isn't fixed, but it tends to last something like six months.

<<Anchor(front-desk)>>
 Front Desk :: The front desk members receive the initial [[#applicant|applications]], [[#advocate|advocation]] messages, and final application reports. They are the point of contact if problems arise with an application.

<<Anchor(ftbfs)>>
 FTBFS :: Short for "Fails To Build From Source", a bugreport type produced by the build infrastructure when a [[#package|package]] cannot be compiled. See [[qa.debian.org/FTBFS]].

<<Anchor(ftp-master)>>
 FTP master :: Several things, none of which necessarily involve the File Transfer Protocol
##
 * The [[http://ftp-master.debian.org|ftp-master]] server, the primary copy of the Debian archive
 * The [[Teams/FTPMaster|FTPMaster team]] that looks after this server, doing tasks such as checking the incoming queue for policy or licensing violations
 * Senior members of this team also rank as "FTP Masters"
## I wonder which came first - the master-archives or the archive-masters?

<<Anchor(full-upgrade)>>
 Full-upgrade :: An [[DebianPkg:unstable/aptitude|aptitude]] action more or less equivalent to (and formerly known as) a [[#dist-upgrade|dist-upgrade]].

<<Anchor(G)>>
Line 34: Line 349:
[[Anchor(H)]] <<Anchor(general-resolution)>>
 General Resolution (GR) :: A decision ratified by a vote of [[#debian-developer|Debian Developer]]s, according to the procedure specified in the [[http://www.debian.org/devel/constitution|Debian Constitution]]

<<Anchor(giveback)>>
 Giveback :: In autobuilder jargon, packages are "taken" when an attempt is made to build them. Failures are often transient, fixed by simply trying again after a few days, so a "giveback" removes the "taken" flag from the package in the [[#wanna-build|wanna-build]] database and puts it back into the normal [[#needs-build|needs-build]] queue.

<<Anchor(gr)>>
 GR :: Short for "[[#general-resolution|General Resolution]]"

<<Anchor(H)>>
Line 37: Line 361:
[[Anchor(I)]] <<Anchor(hamm)>>
 Hamm :: The codename for Debian 2.0, [[#release|release]] date: 1998

<<Anchor(hppa)>>
 Hppa :: A [[#port|port]] (formerly a [[#release-architecture|release architecture]]) using the Linux kernel on Hewlett Packard Precision Architecture RISC workstations and servers
## which allegedly once existed somewhere

<<Anchor(hurd-i386)>>
 Hurd-i386 :: A (work-in-progress) [[#port|port]] (on [[#debports|debports]] but not yet a [[#release-architecture|release architecture]]) using the Hurd kernel on [[#i386|i386]]-style hardware

<<Anchor(I)>>
Line 40: Line 374:
[[Anchor(J)]] <<Anchor(i386)>>
 I386 :: A "[[#port|port]]" (or rather the original [[#release-architecture|release architecture]]) using the Linux kernel on 32-bit PCs - technically x86 or IA-32, nontechnically anything vaguely resembiling a Pentium processor

<<Anchor(ia64)>>
 Ia64 :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the Linux kernel on Intel IA-64 AKA Itanium hardware, not to be confused with [[#amd64|amd64]]

<<Anchor(ianadd)>>
 IANADD :: Short for "I Am Not A [[#debian-developer|Debian Developer]]" - a caveat in the tradition of [[#ianal|IANAL]]

<<Anchor(ianal)>>
 IANAL :: Short for "I Am Not A Lawyer", often used on the [[http://lists.debian.org/debian-legal|debian-legal]] mailing list. Not Debian-specific; see [[WikiPedia:IANAL|Wikipedia's definition]].

<<Anchor(ice)>>
 ICE :: Short for "Internal Compiler Error"; used in bug reports for [[http://wiki.debian.org/ftpmaster_Removals|package removal]], usually indicating that GCC does not yet fully support a new architecture

<<Anchor(install)>>
 Install ::
##
 * To set up an Operating System (e.g. with [[#debian-installer|Debian-Installer]]), or otherwise introduce software onto a system. Examples include installing a bootable image to your boot-sector, a homebrew kernel in `/boot`, or a shellscript in `/usr/local/sbin`. The Debian system is designed to permit various forms of local installation performed outside the package database, but you have to keep track of them yourself.
 * In Debian package management, to put a [[#binary-package|binary package]] onto a system in a way that registers it with the package database. Note that the package management system sees package [[#upgrade|upgrade]]s as a subcategory of installs.
 * In [[#apt|APT]] (or front-ends), a particular action. Note however that `install` and `remove` can each be used to perform the opposite function, if given an appropriate suffix (e.g.: `apt-get install foo- bar-` will [[#remove|remove]] packages `foo` and `bar`).

<<Anchor(installed)>>
 Installed :: A [[#wanna-build|wanna-build]] state

<<Anchor(ita)>>
 ITA :: Short for "Intent to Adopt", used to track the status of [[#orphaned|orphaned]] [[#package|package]]s (see [[http://www.debian.org/devel/wnpp/|WNPP]]) or documentation (see [[http://www.debian.org/doc/manuals/ddp-policy/ch-feedback.html|DDP]]).

<<Anchor(itd)>>
 ITD :: Short for "Intent to Document", used by a documentation maintainer who intends to start writing a document. Using the [[#wnpp|WNPP]] system avoids duplicated effort; see [[http://www.debian.org/doc/manuals/ddp-policy/ch-feedback.html|DDP]].

<<Anchor(itp)>>
 ITP :: Short for "Intent To Package", used by a [[#DD|DD]] or [[#maintainer|Maintainer]] who intends to package a piece of software; see [[http://www.debian.org/devel/wnpp/#tag-rfa|WNPP]].

<<Anchor(itt)>>
 ITT :: Short for "Intent to Translate", used by a translator who intends to start translating a document. This like the above is a mechanism to prevent duplication of efforts; see [[http://www.debian.org/doc/manuals/ddp-policy/ch-feedback.html|DDP]].

<<Anchor(J)>>
Line 43: Line 414:
[[Anchor(K)]] <<Anchor(K)>>
Line 46: Line 417:
[[Anchor(L)]] <<Anchor(kfreebsd-amd64)>>
 Kfreebsd-amd64 :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the FreeBSD kernel on [[#amd64|amd64]]-style hardware

<<Anchor(kfreebsd-i386)>>
 Kfreebsd-i386 :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the FreeBSD kernel on [[#i386|i386]]-style hardware

<<Anchor(ksp)>>
 KSP :: Short for "[[Keysigning|Key Signing]] Party", a common event at [[#debconf|DebConf]]s and other real-life get-togethers

<<Anchor(L)>>
Line 49: Line 429:
[[Anchor(M)]] <<Anchor(lenny)>>
 Lenny :: The codename for Debian 5.0, [[#release|release]] date: 2009 ([[#oldstable|oldstable]])

##<<Anchor(lexicographer)>>
## Lexicographer :: a writer of dictionaries; a harmless drudge that busies himself in tracing the original and detailing the signification of words

<<Anchor(M)>>
Line 52: Line 438:
[[Anchor(N)]] <<Anchor(m32r)>>
 M32r :: A rumoured [[#port|port]] which has never made it as far as [[#debports|debports]] using the Linux kernel on Renesas M32R embedded hardware
## whatever that is

<<Anchor(m68k)>>
 M68k :: A [[#port|port]] (formerly a [[#release-architecture|release architecture]], still available via [[#debports|debports]]) using the Linux kernel on Motorola-680x0 CPUs, once common in Sun3/Apple/Atari/Amiga machines

<<Anchor(main)>>
 Main :: The "truly Debian" archive [[#area|area]], reserved for [[#free|free]] software.

<<Anchor(maintainer)>>
 Maintainer :: The maintainer of a package is the person or group of people responsible for it (packaging, bugtracking, etc.); see [[http://www.debian.org/doc/debian-policy/ch-binary.html#s3.3|Debian Policy]]. See also [[#debian-maintainer|Debian Maintainer (DM)]], [[#debian-new-maintainer|Debian New Maintainer (process)]].

<<Anchor(mass-bug-filing)>>
 Mass bug filing (MBF) :: Reporting a great number of bugs for the same problem. See the [[http://www.debian.org/doc/developers-reference/beyond-pkging.html#submit-many-bugs|Debian Developer's Reference]].

<<Anchor(mbf)>>
 MBF :: Short for "[[#mass-bug-filing|Mass Bug Filing]]".

<<Anchor(mentor)>>
 Mentor :: An experienced [[#debian-member|Debian Member]] who takes responsibility for assisting a less experienced member or [[#applicant|Applicant]]. Outside occasional efforts such as the [[http://women.debian.org/mentoring/|Debian Women mentoring program]], such relationships generally exist only on an informal and unofficial basis. Every [[#applicant|Applicant]] has an [[#advocate|advocate]] who may effectively act as a mentor; but despite the name of the [[http://lists.debian.org/debian-mentors|debian-mentors]] mailing list, its primary function is to put new maintainers in touch with [[#sponsor|sponsor]]s.

<<Anchor(metapackage)>>
 Metapackage :: A [[#dependency-package|dependency package]] designed to automatically pull in a family of packages; may function as a shortcut to simplify installation of a full desktop environment.
## sometimes hyphenated, but writing it as two words makes it the adjective "meta", which has the wrong meaning

<<Anchor(mia)>>
 MIA :: Short for "Missing In Action"; (a database tracking) Debian package [[#maintainer|maintainer]]s who have abandoned their duties without retiring

## there's nothing Debian-specific about these (besides, there isn't even a glossary entry for plain "Kernel")
##<<Anchor(micro-kernel)>>
## Micro-kernel :: A micro-kernel is a minimalistic operating system kernel which provides only the most basic services, which generally include tasks, virtual memory policy, Inter Process Communication and basic hardware drivers. Examples of micro kernels are Mach (and GNUMach, OSKit-Mach) and L4. ~-(sea also Wikipedia WikiPedia:Micro_kernel )-~
##
##<<Anchor(multi-server)>>
## Multi Server :: Multi server refers to a system which has several servers working together running on a [[#micro-kernel|MicroKernel]] to perform the tasks normally done by a monolithic kernel; this is in contrast to a single server which is akin to a monolithic kernel running on a micro kernel.

<<Anchor(mips)>>
 Mips :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the Linux kernel on big-endian SGI-style MIPS hardware

<<Anchor(mipsel)>>
 Mipsel :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the Linux kernel on the little-endian version of [[#mips|mips]]-style hardware

<<Anchor(N)>>
Line 55: Line 483:
[[Anchor(O)]] <<Anchor(nbs)>>
 NBS :: Short for "Not Built from Source"; one of the criteria used to detect candidates for automated package removal, in this case removing a [[#binary-package|binary package]] that isn't built from any remaining [[#source package|source package]]. See [[ftpmaster_Removals]].

<<Anchor(needs-build)>>
 Needs-build :: A [[#wanna-build|wanna-build]] state

<<Anchor(new-maintainer)>>
 New Maintainer (NM) :: See [[#debian-new-maintainer|Debian New Maintainer]], [[#applicant|Applicant]], [[#debian-maintainer|Debian Maintainer]].

<<Anchor(nmu)>>
 NMU :: Short for "[[NonMaintainerUpload]]"; a version of a package that wasn't uploaded by an ''official'' [[#maintainer|Maintainer]], but rather by another developer. This typically occurs for security updates, [[#mass-bug-filing|Mass Bug Filings]], and when the maintainer is on holiday - see [[http://www.debian.org/doc/developers-reference/pkgs.html#nmu|Debian Developer's Reference]].

<<Anchor(non-free)>>
 Non-free :: Not compliant with the [[#dfsg|DFSG]]; also, the archive [[#area|area]] for software which is non-free but can be legally distributed by Debian.

<<Anchor(non-us)>>
 Non-US :: (Obsolete) A subdivision of the Debian archives needed for the [[#slink|slink]]/[[#potato|potato]]/[[#woody|woody]] [[#release|release]]s (1999-2005) to deal with US legal restrictions on the export of cryptographic software. Software such as [[DebianPkg:unstable/gnupg|GPG]] was hosted only on mirrors outside the USA.

<<Anchor(not-for-us)>>
 Not-for-us :: A [[#wanna-build|wanna-build]] state (not to be confused with [[#non-us|non-us]])

<<Anchor(npoasr)>>
 NPOASR :: Short for "Never Part Of A Stable Release"; used in bug reports for [[http://wiki.debian.org/ftpmaster_Removals|package removal]], implying that users won't see the package's absence as a regression

<<Anchor(nviu)>>
 NVIU :: Short for "Newer Version In Unstable"; one of the criteria used to detect candidates for automated package removal, in this case removing an experimental build as superseded by a more recent build already present in [[#unstable|unstable]]. See [[ftpmaster_Removals]].

<<Anchor(O)>>
Line 58: Line 513:
[[Anchor(P)]] <<Anchor(o)>>
 O :: Short for the [[#qa|QA]] status "[[#orphaned|Orphaned]]"

<<Anchor(obsolete)>>
 Obsolete ::
##
 * In [[DebianMan:1/aptitude|aptitude]] (e.g. `aptitude search ?obsolete`), any currently installed package which is not available (in any version) from any known archive. This usually means that the system has [[#dist-upgrade|dist-upgrade]]d to a new stable release that no longer contains that package.[[#transition-package|Transition package]]s don't register as obsolete in this sense.
 * Also used to refer to automatically installed packages that are no longer needed (such as [[#orphan|orphan]] libraries) and would be candidates for autoremoval.

<<Anchor(oldstable)>>
 Oldstable :: The distribution before the current [[#stable|stable]] [[#release|release]], which continues to receive some level of security support for a while (commonly a year) after it is superseded.

<<Anchor(oldstable-proposed-updates)>>
 Oldstable-proposed-updates :: the equivalent to [[#stable-proposed-updates|stable-proposed-updates]] for [[#oldstable|oldstable]]

<<Anchor(origin)>>
 Origin :: In `Release` files and [[DebianPkg:unstable/aptitude|aptitude]] searches, the organization providing the repository - examples include `Debian`, `Debian Backports`, and `Google, Inc.`

<<Anchor(orphan)>>
 Orphan :: (Not to be confused with the following) In package management, a stray installed package with no reverse dependencies (such as a library for which the corresponding executable has been purged), which can be detected with tools such as [[DebianPkg:unstable/deborphan|deborphan]]. Such unwanted relics are now increasingly tracked by [[#apt|APT]] itself.
## backwards (if I outlive my dependents, I'm not an orphan, I'm a bereaved parent) but moaning won't help

<<Anchor(orphaned)>>
 Orphaned (O) :: (Not to be confused with the above) Used in package [[#qa|QA]] to indicate that a package has no maintainer, and needs to be adopted (see [[#ita|ITA]] and [[http://www.debian.org/devel/wnpp/#tag-o|WNPP]]). If the package has a [[#priority|priority]] of standard or higher, the [[#severity|severity]] of the orphaning bug report should be set to important. The term is similarly used to indicate documentation that the author is declaring abandoned; see [[http://www.debian.org/doc/manuals/ddp-policy/ch-feedback.html|DDP]].

<<Anchor(P)>>
Line 61: Line 541:
[[Anchor(Q)]] <<Anchor(package)>>
 Package ::
##
 * (In Java, TeX, etc.) a unit of software with a single shared namespace
 * (In Debian) See [[#binary-package|binary package]], [[#source-package|source package]], or [[#virtual-package|virtual package]]

<<Anchor(package-tracking-system)>>
 Package Tracking System (PTS):: The [[qa.debian.org/pts|Package Tracking System]] lets you follow almost everything related to the life of a package, and is of interest for co-maintainers, [[#qa|QA]] workers, and advanced users

<<Anchor(papt)>>
 PAPT :: Short for "[[Teams/PythonAppsPackagingTeam|Python Applications Packaging Team]]"

<<Anchor(pinning)>>
 Pinning :: [[#apt|APT]] pinning is the name given to the use of [[DebianMan:5/apt_preferences|apt_preferences(5)]] to define a modified system of package-management priorities. This makes it possible, for instance, to run an essentially [[#stable|stable]] system but specify particular packages for which newer candidates (e.g. [[#backports|backports]]) will automatically be preferred for installation.

<<Anchor(piuparts)>>
 Piuparts :: Short for "Package Installation, UPgrading And Removal Testing Suite" - see [[piuparts]].

<<Anchor(point-release)>>
 Point release :: [[PointRelease]]s are updated versions of a [[#release|release]], with incremented minor revision number (hence the name), incorporating all accumulated security fixes and grave bug-fixes. (Also, In Real Life, a type of minor avalanche.)

<<Anchor(popcon)>>
 Popcon :: The popcon score of a Debian package (see [[http://popcon.debian.org/]]) is meant to reflect its "popularity"; it is derived from data generated via the package [[DebianPkg:unstable/popularity-contest|popularity-contest]], which periodically and anonymously submits statistics about which [[#binary-package|binary package]]s are installed on a system and whether they are used.

<<Anchor(port)>>
 Port ::
##
 * (Non-Debian-specific) a physical hardware interface
 * (Ditto) a TCP networking endpoint identified by port number
 * (Ditto) a platform that software has been converted to run on
 * a hardware/OS kernel combo for which some effort has been made to render Debian installable. See [[#architecture|architecture]], [[#debports|debports]], [[http://www.debian.org/ports]]

<<Anchor(potato)>>
 Potato :: The codename for Debian 2.2, [[#release|release]] date: 2000

<<Anchor(powerpc)>>
 Powerpc :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the Linux kernel on IBM/Motorola PowerPC hardware, meaning Power``Macs and other pre-Intel Macs

<<Anchor(powerpcspe)>>
 Powerpcspe :: A [[#port|port]] (not yet a [[#release-architecture|release architecture]] but available via [[#debports|debports]]) using the Linux kernel on a slightly more obscure variant of [[#powerpc|powerpc]] hardware

<<Anchor(priority)>>
 Priority :: A ranking system for binary packages, indicating how important it is for users to have them installed, and ranging from `extra` to `required` (not to be confused with [[#essential|essential]]). See [[http://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities|Policy]].

<<Anchor(pseudo-package)>>
 Pseudo-package :: (Not to be confused with [[#virtual-package|virtual package]], [[#wnpp|prospective package]], or [[DebianPkg:unstable/sudo|the package sudo]]) A [[#bts|BTS]] address that
 doesn't correspond to a [[#package|package]] name; see [[http://www.debian.org/Bugs/pseudo-packages]]

<<Anchor(pts)>>
 PTS :: Short for "[[#package-tracking-system|Package Tracking System]]"

<<Anchor(purge)>>
 Purge :: In Debian package management, to uninstall a package completely, deleting its [[#conffile|conffile]]s. See [[#remove|remove]]

<<Anchor(Q)>>
Line 64: Line 598:
[[Anchor(R)]] <<Anchor(qa)>>
 QA :: Short for "Quality Assurance" - see [[qa.debian.org]]

<<Anchor(R)>>
Line 67: Line 604:
[[Anchor(S)]] <<Anchor(rc)>>
 RC :: Has several easily confused meanings:
##
 * Short for "Release Candidate", in version strings (v1.9~rc5 comes before v1.9)
 * Short for "[[#release-critical|Release-Critical]]" in the [[#bts|BTS]]
 * Short for "Radio Controlled"; one of the few original Toy Story character names never to have been adopted as a Debian [[#release|release]] codename (it was a little buggy)
 * In a filename such as `~/.bashrc`, indicates a type of [[#configuration-file|configuration-file]] - usually interpreted as short for "runtime configuration", but apparently inspired by the following
 * In the [[DebianPkg:unstable/sysv-rc|sysv-rc]] system, indicates a type of set-up script (in `/etc/rc*.d`) - usually interpreted as short for "[[RunLevel|runlevel]] configuration", but apparently inspired by the following
 * In the MIT Compatible Time-Sharing System back in the sixties, "runcom files"

<<Anchor(release)>>
 Release :: see [[DebianRelease|Debian Release]]
##
 * The occasion of a new [[#stable|stable]] version of Debian being declared ready for production use;
 * A [[#suite|suite]] that has been or is going to be released; more generally, a synonym for [[#suite|suite]] - even [[#sid|sid]] has a `Release` file and is traditionally (if oxymoronically) referred to as "the unstable release".

<<Anchor(release-architecture)>>
 Release Architecture :: An [[#architecture|architecture]] supported as part of a stable [[#release|release]]; [[#port|port]]s qualify for this status when their autobuilders prove capable of "keeping up" and successfully building a sufficient proportion of the archive.
## citation needed; where is this documented?

<<Anchor(release-critical)>>
 Release Critical (RC) :: a bug that cannot be allowed in [[#stable|stable]]; a [[#release|release]] cannot occur until all such bugs have been handled (by [[#rm|removal]] if necessary)

<<Anchor(remove)>>
 Remove ::
##
 * In Debian package management, to uninstall a package, especially in a fashion that leaves behind [[#conffile|conffile]]s (thus if you remove and then reinstall a package you won't lose your custom setup). See [[#purge|purge]]
 * In [[#apt|APT]] (or front-ends), a particular action. Note however that `install` and `remove` can each be used to perform the opposite function, if given an appropriate suffix (e.g.: `apt-get remove foo+ bar+` will [[#install|install]] packages `foo` and `bar`).

<<Anchor(request-tracker)>>
 RequestTracker (RT) :: The issue-tracking system [[rt.debian.org]], used by the [[#security|Security]] and [[#debian-system-administrators|DSA]] teams (among others)

<<Anchor(rex)>>
 Rex :: The codename for Debian 1.2, [[#release|release]] date: 1996

<<Anchor(rfa)>>
 RFA :: Short for "Request For Adoption"; a [[http://www.debian.org/devel/wnpp/#tag-rfa|WNPP]] bug tag indicating that (due to lack of time, interest, or other resources) the current maintainer is asking for someone else to maintain this package. They will maintain it in the meantime, but perhaps not in the best possible way. Compare [[#orphaned|Orphaned]].

## <<Anchor(rfb)>>
## RfB :: Short for "Request for Boot"; used by the [[#debian-systems-administration|DSA team]] when a machine has crashed and needs to be rebooted by the site admin
## seen in acronym lists but not detectably in real use; not to be confused with the (ex)package rfb

<<Anchor(rfd)>>
 RFD :: Short for "Request For Documentation"; a [[http://www.debian.org/doc/manuals/ddp-policy/ch-feedback.html|DDP]] bug tag indicating that a manual or other documentation on a given topic is not yet available on the DDP and the reporting user requests that DDP members should give it priority when deciding which documents need to be written.

<<Anchor(rfh)>>
 RFH :: Short for "Request For Help"; a [[http://www.debian.org/devel/wnpp/#tag-rfh|WNPP]] bug tag indicating that the current maintainer wants to continue to maintain this package, but needs some help to do this. This may be because the maintainer is overstretched in general, or because this package is particularly hard to maintain, or because bugs require specialist expertise to fix.

<<Anchor(rfp)>>
 RFP :: Short for "Request For Package"; a [[http://www.debian.org/devel/wnpp/#tag-rfp|WNPP]] bug tag indicating that the reporter has found an interesting piece of software and would like someone else to maintain it for Debian.

<<Anchor(rm)>>
 RM :: Used in subject lines of package [[http://ftp-master.debian.org/removals.html|removal requests]]. It might look like it's addressed to the Release Manager, but it's just a shouty version of `rm`.

<<Anchor(rom)>>
 RoM :: Short for "Request of Maintainer"; used in bug reports for package removal, to indicate that it has been agreed with the package's own [[#maintainer|maintainer]].

<<Anchor(root)>>
 Root :: A word with several (non-Debian-specific) technical uses, all deriving from the same metaphor of a node structure with a root and branches:
##
 * the root directory (`/`) is the top level directory of the file system hierarchy - the part of the "directory tree" that everything else connects to.
 * the root user (uid 0) is the so-called "superuser", with unlimited privileges - equivalent to the "Administrator" on some other operating systems. (This name might lead you to expect users to be arranged in some sort of organizational tree structure, but it just means that the superuser can modify the root directory.)
 * the root window is the desktop background, the element of the graphical environment that all other windows are defined relative to. (Thus "root tile" as a synonym for "desktop wallpaper".)
 * the root zone is the core of the DNS system, where the nameservers that are authoritative for Top Level Domains (the "root nameservers") live.
 * the directory `/root` is the home directory of the root user. Not to be confused with the root directory as defined above.
##
 Not forgetting its senses of "inverse exponent", or "gain illicit superuser access, either for malicious purposes or to bypass a proprietary OS", or (in AU/NZ slang) "have sex with"... and it doesn't help that for some it's homophonous with "route".

<<Anchor(rop)>>
 ROP :: Short for "Request Of Porter"; used in bug reports for [[http://wiki.debian.org/ftpmaster_Removals|package removal]], to indicate that the package is no longer built on a particular set of architectures

<<Anchor(roqa)>>
 RoQA :: Short for "Requested of the QA team"; used in bug reports for [[http://wiki.debian.org/ftpmaster_Removals|package removal]], to indicate that it has been agreed with the [[#qa|QA]] team (usually because the package is [[#orphaned|orphaned]])

<<Anchor(rort)>>
 RoRT :: Short for "Request of Release Team"; used in bug reports for [[http://wiki.debian.org/ftpmaster_Removals|package removal]], to indicate that issues have been confirmed by the [[Teams/ReleaseTeam|Release Team]].

<<Anchor(rosrm)>>
 ROSRM :: Short for "Request of Stable Release Manager"; used in bug reports for [[http://wiki.debian.org/ftpmaster_Removals|package removal]], to indicate that it has been agreed with the powers that be

<<Anchor(rt)>>
 RT :: Short for "[[#request-tracker|Request Tracker]]"

<<Anchor(S)>>
Line 70: Line 690:
[[Anchor(T)]] <<Anchor(s390)>>
 S390 :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the Linux kernel on IBM s/390 AKA zSeries mainframe hardware

<<Anchor(safe-upgrade)>>
 Safe-upgrade :: an [[DebianPkg:unstable/aptitude|aptitude]] action more or less equivalent to (and formerly known as) an [[#upgrade|upgrade]].

<<Anchor(sarge)>>
 Sarge :: The codename for Debian 3.1, [[#release|release]] date: 2005

<<Anchor(section)>>
 Section ::
##
 * A notional subdivision of the Debian repositories into functional categories such as "admin", "kde", and "video"
 * Also sometimes used as a synonym for archive [[#area|area]]

<<Anchor(security)>>
 Security :: The suite used to propagate fixes for [[http://www.debian.org/security|security]] issues into [[#stable|stable]], maintained by the [[Teams/Security|security team]]

<<Anchor(severity)>>
 Severity :: A ranking system for bugreports, indicating how important it is for it to be fixed, and ranging from `wishlist` to `critical`. See [[http://www.debian.org/Bugs/Developer#severities]]

<<Anchor(sh4)>>
 Sh4 :: A [[#port|port]] (not yet a [[#release-architecture|release architecture]] but available via [[#debports|debports]]) using the Linux kernel on Hitchi SuperH hardware (used e.g. in Dreamcasts)

<<Anchor(shlibs)>>
 Shlibs :: Not a cross between a shrub and a blintz.
##
 * Short for '''sh'''ared '''lib'''rarie'''s''' - that is, dynamically loadable subroutines compiled into object files so that a single copy loaded into memory can be accessed by as many different processes as need it. Normally have the file extension `.so`, followed by interface-version numbers.
 * A special file defined in [[http://www.debian.org/doc/debian-policy/ch-sharedlibs.html|Debian Policy]] for tracking shared library dependencies

<<Anchor(sid)>>
 Sid :: The permanent codename for [[#unstable|unstable]]. While other codenames cycle through from [[#testing|testing]] to [[#stable|stable]] to [[#oldstable|oldstable]], the name "Sid" stays in the same place permanently.

<<Anchor(slink)>>
 Slink :: The codename for Debian 2.1, [[#release|release]] date: 1999

<<Anchor(source)>>
 Source ::
##
 * A package origin defined by a line in [[DebianMan:5/sources.list|sources.list]]
 * A [[DebianMan:1/bash|bash]] builtin that executes commands from a file
 * Compilable code, the input of a build process - see [[#source-package|source package]]

<<Anchor(source-package)>>
 Source package ::
##
 * a unit of upstream software (with a single build system), which may correspond to several separate [[#binary-package|binary package]]s within Debian;
 * the bundle of files ([[#dotdsc|.dsc]] file, upstream tarball, etc) used as input to the package-building process.

<<Anchor(sparc)>>
 Sparc :: A [[#port|port]] (currently a [[#release-architecture|release architecture]]) using the Linux kernel on 32-bit Sun4-style SPARC hardware

<<Anchor(sparc64)>>
 Sparc64 :: A [[#port|port]] (not yet a [[#release-architecture|release architecture]] but available via [[#debports|debports]]) using the Linux kernel on 64-bit versions of [[#sparc|sparc]]-type hardware

<<Anchor(spi)>>
 SPI :: Short for "[[http://www.spi-inc.org/|Software in the Public Interest, Inc.]]", the nonprofit foundation that manages resources and accepts donations on behalf of the [[#debian-project|Debian Project]] (which has no legal authority for doing so itself).

<<Anchor(sponsor)>>
 Sponsor :: a [[#debian-member|Debian Member]] with upload privileges who uses them on behalf of a package [[#maintainer|maintainer]] without such privileges. The sponsor is required to take responsibility for checking that there are no show-stopping quality issues, but is not recorded as the maintainer of the package. A sponsorship may be a one-off event, or the sponsor may also act informally as a [[#mentor|mentor]], helping to track down bugs and improve the packaging.

<<Anchor(squeeze)>>
 Squeeze :: The codename for Debian 6.0, [[#release|release]] date: 2011 (the current [[#stable|stable]])

<<Anchor(stable)>>
 Stable :: The [[DebianStable|stable]] distribution is the [[#release|release]] recommended for production use. Each stable release is "promoted" from [[#testing|testing]] status as the result of a cycle of development, debugging, and integration that usually lasts about two years.

<<Anchor(stable-proposed-updates)>>
 Stable-proposed-updates :: the suite where proposed fixes for major bugs in [[#stable|stable]] are queued for inclusion in a [[#point-release|point release]]

<<Anchor(stable-updates)>>
 Stable-updates :: The [[StableUpdates]] suite (formerly implemented as [[#volatile|volatile]]) is where proposed updates are queued for packages such as virus scanners that become uselessly out of date over the lifespan of a release.

<<Anchor(suite)>>
 Suite ::
##
 * A set of closely integrated packages (often multiple [[#source-package|source package]]s)
 * Used in `Release` files and elsewhere to mean a repository holding one particular "branch" of Debian's development process - [[#unstable|unstable]], [[#testing|testing]], and so on. Compare [[#archive|archive]], [[#distribution|distribution]], [[#release|release]]

<<Anchor(T)>>
Line 73: Line 772:
[[Anchor(U)]] <<Anchor(testing)>>
 Testing :: [[DebianTesting|testing]] is the Debian distribution automatically generated out of packages migrating from [[#unstable|unstable]]. The first step towards a new [[#stable|stable]] release is that testing undergoes a [[#freeze|freeze]].

<<Anchor(testing-proposed-updates)>>
 Testing-proposed-updates :: the equivalent to [[#stable-proposed-updates|stable-proposed-updates]] for [[#testing|testing]], used only in cases where the fixes need to bypass [[#unstable|unstable]]

<<Anchor(testing-security)>>
 Testing-security :: The [[http://testing-security.debian.net|testing-security]] suite is only roughly the [[#testing|testing]] equivalent of [[#stable|stable]]'s [[#security|security]] support, because it is run by a different [[Teams/TestingSecurity|team]] and because most new package versions fixing security bugs can simply go through [[#unstable|unstable]] as usual

<<Anchor(tinla)>>
 TINLA :: Short for "This Is Not Legal Advice"; compare [[#ianal|IANAL]].

<<Anchor(transition)>>
 Transition :: Often short for "library transition". A new version of a widely-used dependency hitting [[#unstable|unstable]] can mean that large numbers of related packages need rebuilds or significant fixes before the whole set can migrate to [[#testing|testing]].

<<Anchor(transition-package)>>
 Transition package :: A [[#dependency-package|dependency package]] designed to automatically replace one [[#package|package]] with another, to smooth over a rename or similar migration (especially for users performing a [[#dist-upgrade|dist-upgrade]]). Not connected with library [[#transition|transition]]s

<<Anchor(U)>>
Line 76: Line 793:
[[Anchor(V)]] <<Anchor(unstable)>>
 Unstable :: [[DebianUnstable|unstable]] is the Debian distribution where you can find the latest packages introduced into the Debian system.

<<Anchor(update)>>
 Update :: In [[#apt|APT]] (or front-ends), the process of refreshing the package-management system's information about what packages are available from the registered [[#source|source]]s. Not to be confused with (or omitted before) an [[#upgrade|upgrade]]

<<Anchor(upgrade)>>
 Upgrade ::
##
 * In Debian package management, the process of installing the newest versions of a set of [[#binary-package|binary package]]s (by default, all packages that have newer candidates available).
 * In [[DebianPkg:unstable/apt|apt]] specifically, the kind of upgrade that only fetches and installs new versions of packages, without changing the list of installed packages (so for instance a package whose new version has extra dependencies would be left unupgraded). Compare [[#dist-upgrade|dist-upgrade]], and [[DebianPkg:unstable/aptitude|aptitude]]'s [[#safe-upgrade|safe-upgrade]].

<<Anchor(uploaded)>>
 Uploaded :: A [[#wanna-build|wanna-build]] state

<<Anchor(urgency)>>
 Urgency :: A ranking system for uploads, indicating how important it is for the new version to reach the archives, and ranging from `low` to `critical`. See [[http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency|Policy]]

##<<Anchor(user-private-groups)>>
## user private groups :: [[UserPrivateGroups|User private groups]] is a system configuration idiom which allows users to collaborate by granting shared access to a directory and its content. Access is controlled by associating each collaborative project team with a Un*x group and then granting Un*x group membership to the userids of the designated project members.
## No, this is not what "user private groups" means.
## UPG means creating a separate group for each user, a feature which has always been standard on Linux.
## The feature this entry is trying to describe is *shared* groups *not* associated with any one user.
## Alas, the linked Debian Wiki page is in similar Bizarro-speak...

<<Anchor(V)>>
Line 79: Line 821:
[[Anchor(W)]] <<Anchor(virtual-package)>>
 Virtual package :: a [[#binary-package|binary package]] that exists in name only, with no associated [[#dotdeb|.deb]] file; used to organize systems of alternative dependencies (multiple binary packages can claim to "Provide" the same virtual package).

<<Anchor(volatile)>>
 Volatile :: The [[DebianVolatile|volatile]] suite is (roughly speaking) the old name for [[#stable-updates|stable-updates]]

<<Anchor(W)>>
Line 82: Line 830:
[[Anchor(Z)]] <<Anchor(wanna-build)>>
 Wanna-build :: a tool forming part of the autobuild system that maintains a database of the build status of packages (see [[http://www.debian.org/devel/buildd/wanna-build-states]] for details)

<<Anchor(wheezy)>>
 Wheezy :: The codename for the current [[#testing|testing]]

<<Anchor(wnpp)>>
 WNPP :: Short for "Work-Needing and Prospective Packages" - a pseudopackage used to collect reports of packages (and potential packages) in need of (new) maintainers in Debian; see [[http://www.debian.org/devel/wnpp/]], [[#itp|ITP]], [[#orphan|O]], [[#rfa|RFA]], [[#rfh|RFH]], [[#rfp|RFP]].

<<Anchor(woody)>>
 Woody :: The codename for Debian 3.0, [[#release|release]] date: 2002

<<Anchor(X)>>
Line 85: Line 845:
[[Anchor(Y)]] <<Anchor(x-strike-force)>>
 X Strike Force (XSF) :: The [[Teams/XStrikeForce|team]] responsible for [[XStrikeForce|maintaining packages for the X Window System]] in Debian

<<Anchor(Y)>>
Line 88: Line 851:
[[Anchor(Z)]] <<Anchor(Z)>>
Line 91: Line 854:

[[Anchor(Dot)]]
## Zombie Maintainer :: A zombie maintainer is a maintainer who does no work on a package but refuses to orphan it. The package bit-rots away in the clutches of his undead hands as he drifts on the margins of existence. His grumblings are occasionally heard on Debian mailing lists --- just enough to keep himself from being pronounced [[MIA]], which would be grounds for deeming the package orphaned.<<BR>><<BR>>Not much is known about these beings; however, experts in paranormal phenomena claim that once a maintainer has become a zombie he cannot let a package go until his work on it is done. However, having lost his spirit, the zombie is incapable of making any progress. The predictable result is that the package becomes a Slum.<<BR>><<BR>>What is certain is that there is a subclass of zombies whom we shall call "guardians". A guardian zombie holds on to a package while justifying himself by saying that he is doing Debian the service of protecting his package from damage in the hands of a mortal maintainer. A guardian zombie may go so far as to invite [[#nmu|NMUs]], some of which he will allow to pass without comment, to others of which he will react with howls of protest and mutterings of 'my precious'.
## Much as I sympathise, this isn't a widespread piece of Debian-specific jargon in need of definition.
## On the contrary, this is Google's top (and more or less only) hit for the phrase.
## Now, if you made it a wiki page in its own right...

<<Anchor(Dot)>>
Line 95: Line 862:
[[Anchor(DotDeb)]]
 .deb :: File-extension used for package of debian-based distribution.

[[Anchor(DotUdeb)]]
 .udeb :: File-extension used for package containing [#Debian-Installer] modules. '''do not''' install it in a regular system.

----
<<Anchor(dotdeb)>>
 .deb :: File extension used for the standard installable [[#binary-package|binary package]] format used by Debian-based distributions.

<<Anchor(dotdsc)>>
 .dsc :: File extension used for a Debian Source Control file, which is a particular format of [[#control-file|control file]] forming a crucial component of a [[#source-package|source-package]]

<<Anchor(dottdeb)>>
 .tdeb :: File extension used for (proposed) separate translation packages - see [[http://dep.debian.net/deps/dep4|Dep-4]]

<<Anchor(dotudeb)>>
 .udeb :: File extension used for special packages containing [[#debian-installer|Debian-Installer]] modules, not intended for installation on a normal system.

Debian_Jargon-160x160.png


Debian Glossary Only.

If you don't find the entry you wanted be/low, check

Or you can add it yourself. If you can't define it yourself you can put ToDo instead, but always check the sites mentioned above - if it isn't Debian-specific, an existing definition elsewhere is likely to be more helpful.

Jump to : A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Symbols: .(dot)

A

Advocate

A Debian member who advocates an application. Advocates should know the applicant fairly well and should be able to give an overview of the applicant's work, interests and plans. Advocates are often the sponsors of an applicant.

Alioth

Alioth is a collaborative development environment based on the FusionForge software as a service for the Debian project and community.

Alioth (guest) account

People willing to participate in the packaging or development of a software can ask for an Alioth guest account, then ask for commit rights to a given project.

Alpha

A port (formerly a release architecture) using the Linux kernel on (Compaq/Digital) Alpha hardware

AM

See Application Manager

Amd64

A port (currently a release architecture) using the Linux kernel on 64bit PCs - technically x86-64 or AMD64 or Intel64, nontechnically most new consumer PCs

ANAIS

Short for "Architecture Not Allowed In Source"; used in bug reports for package removal, usually indicating that the number of architectures for which the package is to be built has been reduced

Applicant

A person requesting membership in the Debian project; prospective Debian developer.

Application Manager (AM)

A Debian member who is assigned to an applicant to collect the information needed by the Debian account managers to decide about an application. One application manager can be assigned to more than one Applicant.

APT

Debian's Advanced Package Tool (or perhaps Advanced Packaging Tool - neither is "official"), a library that handles fetching the list of packages, resolving package dependencies, etc. It then uses dpkg to perform the actual package installation, removal, etc. The package apt provides the commandline tools apt-get and apt-cache, but other APT front-ends exist such as aptitude and synaptic.

Architecture
The type of system a piece of software is built for:

  • (Not Debian-specific) a general category of hardware (such as "486" or "little-endian"), or a variant of some piece of software tailored for this hardware; may specifically mean the category as determined by some particular tool, such as arch or dpkg-architecture

  • One of the platforms for which Debian packages are built, known by labels such as amd64 or mipsel, and also differentiated by the OS kernel used - the same hardware (not literally an Intel 386 processor) may dualboot i386 and kfreebsd-i386 architectures. See also port, release architecture

Archive
A set of files:

  • (Not Debian-specific) a set of items combined into one file, such as a tarball or .deb file (technically an ar archive)

  • A set of files, such as a software repository
  • Used as a synonym for suite by (e.g.) aptitude - "aptitude search '~i?archive(backports)'")

Area

The term used in Debian Policy for the main, contrib, and non-free divisions of the repositories (also known as components)

Arm

A port (superseded by armel and no longer maintained) using the Linux kernel on ARM/StrongARM hardware, a CPU type originally created for the Acorn Archimedes

Armel

A port (currently a release architecture) using the Linux kernel on little-endian ARM/StrongARM chips, now common in embedded/mobile devices

Armhf

A (work-in-progress) port (on debports but not yet a release architecture) using the Linux kernel on newer ("hard-float") armel-style hardware with an FPU

Avr32

A (work-in-progress) port (on debports but not yet a release architecture) using the Linux kernel on Atmel's 32-bit RISC architecture

B

Backports

Backports are versions of packages from testing and unstable that have been rebuilt to be able to install and run on the stable distribution.

Base system

binary packages with priority required or important; a minimalist set of packages installed before everything else on a new system. Designed to provide just the things you'd be surprised to find missing on a usable UNIX system. Not to be confused with essential, which is much smaller.

BD-Uninstallable

a wanna-build state

Binary
Several potentially confusing (but non-Debian-specific) meanings:

  • Any non-textfile, such as a JPEG format image
  • Any ELF executable (often used generically to include shellscripts and other non-binary executables normally found in a bin directory)

  • The output of a build process - see binary package

Binary package

An installable .deb file as opposed to the source package it's built from. The idea is that this is the "binary" compiled in the package building process (regardless of whether the output .deb contains a binary executable, documentation, or indeed Linux kernel sourcecode).

BinNMU

a binary-only non-maintainer upload - see binNMU

Bo

The codename for Debian 1.3, release date: 1997

BoF

Short for "Birds of a Feather"; a common type of discussion session held at DebConf

BSP

Short for "Bug Squashing Party"; a get-together of Debian enthusiasts (either virtual or In Real Life) for the purpose of fixing as many bugs as possible.

BTS

Short for "Bug Tracking System"

BTS-link

A system for synchronizing bug status in the Debian BTS with bug tracking systems like Bugzilla. See this mail.

Building

  • a wanna-build state

  • (Non-Debian-specific) A piece of architecture in the non-jargon sense

Build-essential

The only package that's literally essential for a Debian package build is make (because Policy mandates the use of a Makefile), but the "build-essential" toolkit is a convenient short-cut: a standard set of packages defined to be required for all normal Debian packaging work, which can therefore be omitted from lists of build dependencies as obvious, just as essential packages are omitted from install-time dependencies.

Buzz

The codename for Debian 1.1, release date: 1996

C

CDBS

Short for "Common Debian Build System" (provided by cdbs)

Component

The term used in sources.list(5) for the main, contrib, and non-free archive areas

Conffile

A technical term defined in Policy; a file declared in a package's conffiles file is treated specially by dpkg to ensure that local modifications are not blindly overwritten by a package upgrade or deleted by a remove. Conffiles are (always?) stored in /etc, and are often conventional global configuration files but may also be initscripts, cronjobs, or similar.

Configuration file

Any file affecting the operation of a program, or providing site- or host-specific information, or otherwise customizing a program's behavior. May or may not be system-wide, or in an intelligible line-oriented text format, or marked as a conffile. Personal configuration files are traditionally stored as dotfiles in the home directory (see also rc-file).

Contrib
Additional, external software, in either of two senses:

  • In various project upstreams, a collection of extra software produced by third parties and included into a distribution "without warranty"
  • in Debian, software that is itself DFSG-compliant but requires software in non-free to build or run usefully (or the archive area such software is separated out into).

Control file

As defined in Debian Policy:

  • The control file included in the debian directory of each source package contains dependency information required to build the package, and has separate stanzas containing further information for each binary-package

  • The control file included in the DEBIAN directory of each binary .deb (formed from the corresponding stanza in the source control file) contains dependency information required to install the package, plus the package description etc.

  • Any "control file"; that is, any file with the same multi-field syntax as the above - for instance, dsc files are also counted as control files.

  • Custom Debian Distributions (CDD)

    The old name for subsets of Debian configured to support a particular target group out-of-the-box. Now known as Debian Pure Blends

    D

    Dak

    (Short for "Debian Archive Kit") The toolset used to manage the Debian repositories - see DakHowTo

    DAM

    See Debian Account Manager.

    DD

    See Debian Developer

    DDP

    Short for the "Debian Documentation Project"

    DDPO

    The Debian Developer's Packages Overview, which lists the packages maintained by a Debian Developer or Team

    DebCamp

    See DebCamp; the hacking session right before DebConf

    Debconf
    Two things distinguished by capitalization:

    Debian Account

    Typically the login account of a Debian Developer, but sometimes also used to refer to a Debian Maintainer account. See also Alioth account.

    Debian Account Manager (DAM)

    A Debian member who has been delegated by the Debian project leader to manage Debian account creation and removal. The DAM has the final decision over an application.

    Debian Contributor

    a general term for active members of the Debian community, whether or not they have DD status; sometimes used to mean the status of a non-uploading DD (as recognised by general resolution).

    Debian Developer (DD)

    A Debian Project member who has gone through the New Maintainer process and had their application accepted is called a Debian Developer.

    Debian Documentation Project

    A Debian sub-project covering various documentation issues. See http://www.debian.org/doc/ddp

    Debian Installer (D-I)

    Debian Installer is the software used to initially install Debian on your hard disk. This should not be confused with the software used to [#install|install]] extra [#packages|packages]] on a running Debian system (see APT).

    Debian Maintainer (DM)

    The status of a person who has passed the Debian Maintainer process. A Debian Maintainer is granted some rights to manage packages, in particular the right to upload packages to the archive. DMs aren't voting members of the Debian Project. See also Debian Developer, Alioth account. Not to be confused with the role of package Maintainer.

    Debian Member

    Full members of the Debian Project are referred to as Debian Developers. (ToDo: link to one coherent central explanation of the distinction between contributors, developers, maintainers, and uploaders, assuming there is one)

    Debian New Maintainer

    The process of becoming an official Debian Developer (DD), or a person going through that process. See also Applicant.

    Debian Policy Manual
    The document that describes what packages should contain, how they should be configured, and generally how packages fit together to create a Debian system.

    Debian Project

    An organization of free software developers spread around the world with a common goal, to produce a completely free operating system. See the Debian web pages for more information.

    Debian Project Leader (DPL)

    the official representative of the Debian Project to the outside world, with internal managerial and coordinatory duties; elected annually. See http://www.debian.org/devel/leader

    Debian Pure Blends

    A subset of Debian that is configured to support a particular target group out-of-the-box. Debian Pure Blends were formerly known as Custom Debian Distributions (CDD).

    Debian Security Advisory (DSA)

    A warning message sent to the debian-security-announce mailinglist about a security alert for Debian software with available fixes. Not to be confused with the DSA team.

    Debian System Administrators (DSA)

    The Debian System Administrators team, who handle the basic infrastructure of the project. Not to be confused with DSA messages.

    Debports

    http://www.debports.net, a site hosting unofficial ports that have yet to qualify as release architectures and be integrated into the main archives

    DEHS

    Short for "Debian External Health Status" (see DEHS).

    DEP

    Short for "Debian Enhancement Proposal", an RFC-like mechanism for planning efforts within the Debian Project

    Dep-wait

    (Plus more rarely dep-wait-removed) A wanna-build state

    Dependency package

    An empty binary package that exists only for the sake of its declared dependencies on other packages, for instance to keep the current default version of gcc installed. See metapackage and transition-package for other common types.

    DFSG

    Short for the "Debian Free Software Guidelines"; the rules of thumb included in the Debian Social Contract that can be used to judge whether material counts for the project's purposes as free. The string dfsg is often appended to package names and version-strings to indicate that the upstream version has been slightly modified to allow it to stay in main.

    D-I

    See Debian-Installer

    Distribution (dist)

    • (Not Debian-specific) the complete set of software from one upstream project, considered as a unit. MacTeX is a TeX distribution, for instance, whereas NetBSD is a full Operating System distribution. This is the sense in which Debian is "a distribution".
    • A suite within the Debian repositories capable of providing a fully functional OS on its own, unlike the supplementary ones such as "testing-security". This is the sense in which stable is "a distribution".

    • Used more generally (e.g. in sources.list(5)) as a synonym for suite; hence source URLs which put http://ftp.debian.org/debian/dists/experimental/ alongside all the other dists.

    Dist-upgrade

    • In Debian package management, the process of migrating a whole system from one release to the next (dist-upgrades skipping a release are not supported)

    • In apt specifically, an action that makes relatively aggressive (but intelligent) attempts to bring the system fully up to date, even if this requires some changes to the list of installed packages (that is, it may automatically install, remove, or replace packages). Compare plain upgrade, and aptitude's full-upgrade.

    DM

    See Debian Maintainer.

    DMUP

    Short for "Debian Machine Use Policies"; the documented Acceptable Use Policy for machines on the Debian network.

    Downgrade

    An action not officially supported in Debian package management, though often possible (and where it isn't, a purge and reinstallation of the older version is often good enough).

    DPL

    Short for "Debian Project Leader"

    DPMT

    The Debian Python Modules Team, who work to improve the Python modules situation in Debian.

    DSA

    Short for either "Debian Security Advisory" or "Debian Systems Administrators"

    E

    Essential

    A set of packages providing the absolute minimal functionality that must be available and usable on the system at all times. The idea is, if you're hit by a software or hardware failure halfway through an upgrade, leaving your package database in an inconsistent state, the essential packages should still work well enough to let you perform repair work.

    Etch

    The codename for Debian 4.0, release date: 2007

    Experimental

    The experimental repository is an incomplete distribution which developers can use to try out versions of software not intended to migrate to testing, and which users are warned not to install

    F

    Failed

    (Plus more rarely failed-removed) A wanna-build state

    FHS

    See Filesystem Hierarchy Standard.

    Filesystem Hierarchy Standard (FHS)

    the FilesystemHierarchyStandard defines the main directories and their contents in Linux and other Unix-like computer operating systems. The Debian Policy Manual only explains the exceptions applying to Debian.

    Free

    Compliant with the DFSG, and eligible to go in main

    Freeze

    The distribution development freeze is a period of time when the Debian Project is working to finalize and stabilize the content of the testing distribution (resolving release critical bugs, making final tweaks to Debian-Installer, deciding the contents of the CDs, etc.) before its release as the new stable. Debian's release policy is one of Release when Ready, so the length of the freeze period isn't fixed, but it tends to last something like six months.

    Front Desk

    The front desk members receive the initial applications, advocation messages, and final application reports. They are the point of contact if problems arise with an application.

    FTBFS

    Short for "Fails To Build From Source", a bugreport type produced by the build infrastructure when a package cannot be compiled. See qa.debian.org/FTBFS.

    FTP master
    Several things, none of which necessarily involve the File Transfer Protocol

    • The ftp-master server, the primary copy of the Debian archive

    • The FTPMaster team that looks after this server, doing tasks such as checking the incoming queue for policy or licensing violations

    • Senior members of this team also rank as "FTP Masters"

    Full-upgrade

    An aptitude action more or less equivalent to (and formerly known as) a dist-upgrade.

    G

    General Resolution (GR)

    A decision ratified by a vote of Debian Developers, according to the procedure specified in the Debian Constitution

    Giveback

    In autobuilder jargon, packages are "taken" when an attempt is made to build them. Failures are often transient, fixed by simply trying again after a few days, so a "giveback" removes the "taken" flag from the package in the wanna-build database and puts it back into the normal needs-build queue.

    GR

    Short for "General Resolution"

    H

    Hamm

    The codename for Debian 2.0, release date: 1998

    Hppa

    A port (formerly a release architecture) using the Linux kernel on Hewlett Packard Precision Architecture RISC workstations and servers

    Hurd-i386

    A (work-in-progress) port (on debports but not yet a release architecture) using the Hurd kernel on i386-style hardware

    I

    I386

    A "port" (or rather the original release architecture) using the Linux kernel on 32-bit PCs - technically x86 or IA-32, nontechnically anything vaguely resembiling a Pentium processor

    Ia64

    A port (currently a release architecture) using the Linux kernel on Intel IA-64 AKA Itanium hardware, not to be confused with amd64

    IANADD

    Short for "I Am Not A Debian Developer" - a caveat in the tradition of IANAL

    IANAL

    Short for "I Am Not A Lawyer", often used on the debian-legal mailing list. Not Debian-specific; see Wikipedia's definition.

    ICE

    Short for "Internal Compiler Error"; used in bug reports for package removal, usually indicating that GCC does not yet fully support a new architecture

    Install

    • To set up an Operating System (e.g. with Debian-Installer), or otherwise introduce software onto a system. Examples include installing a bootable image to your boot-sector, a homebrew kernel in /boot, or a shellscript in /usr/local/sbin. The Debian system is designed to permit various forms of local installation performed outside the package database, but you have to keep track of them yourself.

    • In Debian package management, to put a binary package onto a system in a way that registers it with the package database. Note that the package management system sees package upgrades as a subcategory of installs.

    • In APT (or front-ends), a particular action. Note however that install and remove can each be used to perform the opposite function, if given an appropriate suffix (e.g.: apt-get install foo- bar- will remove packages foo and bar).

    Installed

    A wanna-build state

    ITA

    Short for "Intent to Adopt", used to track the status of orphaned packages (see WNPP) or documentation (see DDP).

    ITD

    Short for "Intent to Document", used by a documentation maintainer who intends to start writing a document. Using the WNPP system avoids duplicated effort; see DDP.

    ITP

    Short for "Intent To Package", used by a DD or Maintainer who intends to package a piece of software; see WNPP.

    ITT

    Short for "Intent to Translate", used by a translator who intends to start translating a document. This like the above is a mechanism to prevent duplication of efforts; see DDP.

    J

    K

    Kfreebsd-amd64

    A port (currently a release architecture) using the FreeBSD kernel on amd64-style hardware

    Kfreebsd-i386

    A port (currently a release architecture) using the FreeBSD kernel on i386-style hardware

    KSP

    Short for "Key Signing Party", a common event at DebConfs and other real-life get-togethers

    L

    Lenny

    The codename for Debian 5.0, release date: 2009 (oldstable)

    M

    M32r

    A rumoured port which has never made it as far as debports using the Linux kernel on Renesas M32R embedded hardware

    M68k

    A port (formerly a release architecture, still available via debports) using the Linux kernel on Motorola-680x0 CPUs, once common in Sun3/Apple/Atari/Amiga machines

    Main

    The "truly Debian" archive area, reserved for free software.

    Maintainer

    The maintainer of a package is the person or group of people responsible for it (packaging, bugtracking, etc.); see Debian Policy. See also Debian Maintainer (DM), Debian New Maintainer (process).

    Mass bug filing (MBF)

    Reporting a great number of bugs for the same problem. See the Debian Developer's Reference.

    MBF

    Short for "Mass Bug Filing".

    Mentor

    An experienced Debian Member who takes responsibility for assisting a less experienced member or Applicant. Outside occasional efforts such as the Debian Women mentoring program, such relationships generally exist only on an informal and unofficial basis. Every Applicant has an advocate who may effectively act as a mentor; but despite the name of the debian-mentors mailing list, its primary function is to put new maintainers in touch with sponsors.

    Metapackage

    A dependency package designed to automatically pull in a family of packages; may function as a shortcut to simplify installation of a full desktop environment.

    MIA

    Short for "Missing In Action"; (a database tracking) Debian package maintainers who have abandoned their duties without retiring

    Mips

    A port (currently a release architecture) using the Linux kernel on big-endian SGI-style MIPS hardware

    Mipsel

    A port (currently a release architecture) using the Linux kernel on the little-endian version of mips-style hardware

    N

    NBS

    Short for "Not Built from Source"; one of the criteria used to detect candidates for automated package removal, in this case removing a binary package that isn't built from any remaining source package. See ftpmaster_Removals.

    Needs-build

    A wanna-build state

    New Maintainer (NM)

    See Debian New Maintainer, Applicant, Debian Maintainer.

    NMU

    Short for "NonMaintainerUpload"; a version of a package that wasn't uploaded by an official Maintainer, but rather by another developer. This typically occurs for security updates, Mass Bug Filings, and when the maintainer is on holiday - see Debian Developer's Reference.

    Non-free

    Not compliant with the DFSG; also, the archive area for software which is non-free but can be legally distributed by Debian.

    Non-US

    (Obsolete) A subdivision of the Debian archives needed for the slink/potato/woody releases (1999-2005) to deal with US legal restrictions on the export of cryptographic software. Software such as GPG was hosted only on mirrors outside the USA.

    Not-for-us

    A wanna-build state (not to be confused with non-us)

    NPOASR

    Short for "Never Part Of A Stable Release"; used in bug reports for package removal, implying that users won't see the package's absence as a regression

    NVIU

    Short for "Newer Version In Unstable"; one of the criteria used to detect candidates for automated package removal, in this case removing an experimental build as superseded by a more recent build already present in unstable. See ftpmaster_Removals.

    O

    O

    Short for the QA status "Orphaned"

    Obsolete

    • In aptitude (e.g. aptitude search ?obsolete), any currently installed package which is not available (in any version) from any known archive. This usually means that the system has dist-upgraded to a new stable release that no longer contains that package.Transition packages don't register as obsolete in this sense.

    • Also used to refer to automatically installed packages that are no longer needed (such as orphan libraries) and would be candidates for autoremoval.

    Oldstable

    The distribution before the current stable release, which continues to receive some level of security support for a while (commonly a year) after it is superseded.

    Oldstable-proposed-updates

    the equivalent to stable-proposed-updates for oldstable

    Origin

    In Release files and aptitude searches, the organization providing the repository - examples include Debian, Debian Backports, and Google, Inc.

    Orphan

    (Not to be confused with the following) In package management, a stray installed package with no reverse dependencies (such as a library for which the corresponding executable has been purged), which can be detected with tools such as deborphan. Such unwanted relics are now increasingly tracked by APT itself.

    Orphaned (O)

    (Not to be confused with the above) Used in package QA to indicate that a package has no maintainer, and needs to be adopted (see ITA and WNPP). If the package has a priority of standard or higher, the severity of the orphaning bug report should be set to important. The term is similarly used to indicate documentation that the author is declaring abandoned; see DDP.

    P

    Package

    Package Tracking System (PTS)

    The Package Tracking System lets you follow almost everything related to the life of a package, and is of interest for co-maintainers, QA workers, and advanced users

    PAPT

    Short for "Python Applications Packaging Team"

    Pinning

    APT pinning is the name given to the use of apt_preferences(5) to define a modified system of package-management priorities. This makes it possible, for instance, to run an essentially stable system but specify particular packages for which newer candidates (e.g. backports) will automatically be preferred for installation.

    Piuparts

    Short for "Package Installation, UPgrading And Removal Testing Suite" - see piuparts.

    Point release

    ?PointReleases are updated versions of a release, with incremented minor revision number (hence the name), incorporating all accumulated security fixes and grave bug-fixes. (Also, In Real Life, a type of minor avalanche.)

    Popcon

    The popcon score of a Debian package (see http://popcon.debian.org/) is meant to reflect its "popularity"; it is derived from data generated via the package popularity-contest, which periodically and anonymously submits statistics about which binary packages are installed on a system and whether they are used.

    Port

    • (Non-Debian-specific) a physical hardware interface
    • (Ditto) a TCP networking endpoint identified by port number
    • (Ditto) a platform that software has been converted to run on
    • a hardware/OS kernel combo for which some effort has been made to render Debian installable. See architecture, debports, http://www.debian.org/ports

    Potato

    The codename for Debian 2.2, release date: 2000

    Powerpc

    A port (currently a release architecture) using the Linux kernel on IBM/Motorola PowerPC hardware, meaning PowerMacs and other pre-Intel Macs

    Powerpcspe

    A port (not yet a release architecture but available via debports) using the Linux kernel on a slightly more obscure variant of powerpc hardware

    Priority

    A ranking system for binary packages, indicating how important it is for users to have them installed, and ranging from extra to required (not to be confused with essential). See Policy.

    Pseudo-package

    (Not to be confused with virtual package, prospective package, or the package sudo) A BTS address that doesn't correspond to a package name; see http://www.debian.org/Bugs/pseudo-packages

    PTS

    Short for "Package Tracking System"

    Purge

    In Debian package management, to uninstall a package completely, deleting its conffiles. See remove

    Q

    QA

    Short for "Quality Assurance" - see qa.debian.org

    R

    RC
    Has several easily confused meanings:

    • Short for "Release Candidate", in version strings (v1.9~rc5 comes before v1.9)
    • Short for "Release-Critical" in the BTS

    • Short for "Radio Controlled"; one of the few original Toy Story character names never to have been adopted as a Debian release codename (it was a little buggy)

    • In a filename such as ~/.bashrc, indicates a type of configuration-file - usually interpreted as short for "runtime configuration", but apparently inspired by the following

    • In the sysv-rc system, indicates a type of set-up script (in /etc/rc*.d) - usually interpreted as short for "runlevel configuration", but apparently inspired by the following

    • In the MIT Compatible Time-Sharing System back in the sixties, "runcom files"

    Release

    see Debian Release

    • The occasion of a new stable version of Debian being declared ready for production use;

    • A suite that has been or is going to be released; more generally, a synonym for suite - even sid has a Release file and is traditionally (if oxymoronically) referred to as "the unstable release".

    Release Architecture

    An architecture supported as part of a stable release; ports qualify for this status when their autobuilders prove capable of "keeping up" and successfully building a sufficient proportion of the archive.

    Release Critical (RC)

    a bug that cannot be allowed in stable; a release cannot occur until all such bugs have been handled (by removal if necessary)

    Remove

    • In Debian package management, to uninstall a package, especially in a fashion that leaves behind conffiles (thus if you remove and then reinstall a package you won't lose your custom setup). See purge

    • In APT (or front-ends), a particular action. Note however that install and remove can each be used to perform the opposite function, if given an appropriate suffix (e.g.: apt-get remove foo+ bar+ will install packages foo and bar).

    RequestTracker (RT)

    The issue-tracking system rt.debian.org, used by the Security and DSA teams (among others)

    Rex

    The codename for Debian 1.2, release date: 1996

    RFA

    Short for "Request For Adoption"; a WNPP bug tag indicating that (due to lack of time, interest, or other resources) the current maintainer is asking for someone else to maintain this package. They will maintain it in the meantime, but perhaps not in the best possible way. Compare Orphaned.

    RFD

    Short for "Request For Documentation"; a DDP bug tag indicating that a manual or other documentation on a given topic is not yet available on the DDP and the reporting user requests that DDP members should give it priority when deciding which documents need to be written.

    RFH

    Short for "Request For Help"; a WNPP bug tag indicating that the current maintainer wants to continue to maintain this package, but needs some help to do this. This may be because the maintainer is overstretched in general, or because this package is particularly hard to maintain, or because bugs require specialist expertise to fix.

    RFP

    Short for "Request For Package"; a WNPP bug tag indicating that the reporter has found an interesting piece of software and would like someone else to maintain it for Debian.

    RM

    Used in subject lines of package removal requests. It might look like it's addressed to the Release Manager, but it's just a shouty version of rm.

    RoM

    Short for "Request of Maintainer"; used in bug reports for package removal, to indicate that it has been agreed with the package's own maintainer.

    Root
    A word with several (non-Debian-specific) technical uses, all deriving from the same metaphor of a node structure with a root and branches:

    • the root directory (/) is the top level directory of the file system hierarchy - the part of the "directory tree" that everything else connects to.

    • the root user (uid 0) is the so-called "superuser", with unlimited privileges - equivalent to the "Administrator" on some other operating systems. (This name might lead you to expect users to be arranged in some sort of organizational tree structure, but it just means that the superuser can modify the root directory.)
    • the root window is the desktop background, the element of the graphical environment that all other windows are defined relative to. (Thus "root tile" as a synonym for "desktop wallpaper".)
    • the root zone is the core of the DNS system, where the nameservers that are authoritative for Top Level Domains (the "root nameservers") live.
    • the directory /root is the home directory of the root user. Not to be confused with the root directory as defined above.

    • Not forgetting its senses of "inverse exponent", or "gain illicit superuser access, either for malicious purposes or to bypass a proprietary OS", or (in AU/NZ slang) "have sex with"... and it doesn't help that for some it's homophonous with "route".

    ROP

    Short for "Request Of Porter"; used in bug reports for package removal, to indicate that the package is no longer built on a particular set of architectures

    RoQA

    Short for "Requested of the QA team"; used in bug reports for package removal, to indicate that it has been agreed with the QA team (usually because the package is orphaned)

    RoRT

    Short for "Request of Release Team"; used in bug reports for package removal, to indicate that issues have been confirmed by the Release Team.

    ROSRM

    Short for "Request of Stable Release Manager"; used in bug reports for package removal, to indicate that it has been agreed with the powers that be

    RT

    Short for "Request Tracker"

    S

    S390

    A port (currently a release architecture) using the Linux kernel on IBM s/390 AKA zSeries mainframe hardware

    Safe-upgrade

    an aptitude action more or less equivalent to (and formerly known as) an upgrade.

    Sarge

    The codename for Debian 3.1, release date: 2005

    Section

    • A notional subdivision of the Debian repositories into functional categories such as "admin", "kde", and "video"
    • Also sometimes used as a synonym for archive area

    Security

    The suite used to propagate fixes for security issues into stable, maintained by the security team

    Severity

    A ranking system for bugreports, indicating how important it is for it to be fixed, and ranging from wishlist to critical. See http://www.debian.org/Bugs/Developer#severities

    Sh4

    A port (not yet a release architecture but available via debports) using the Linux kernel on Hitchi SuperH hardware (used e.g. in Dreamcasts)

    Shlibs
    Not a cross between a shrub and a blintz.

    • Short for shared libraries - that is, dynamically loadable subroutines compiled into object files so that a single copy loaded into memory can be accessed by as many different processes as need it. Normally have the file extension .so, followed by interface-version numbers.

    • A special file defined in Debian Policy for tracking shared library dependencies

    Sid

    The permanent codename for unstable. While other codenames cycle through from testing to stable to oldstable, the name "Sid" stays in the same place permanently.

    Slink

    The codename for Debian 2.1, release date: 1999

    Source

    • A package origin defined by a line in sources.list

    • A bash builtin that executes commands from a file

    • Compilable code, the input of a build process - see source package

    Source package

    • a unit of upstream software (with a single build system), which may correspond to several separate binary packages within Debian;

    • the bundle of files (.dsc file, upstream tarball, etc) used as input to the package-building process.

    Sparc

    A port (currently a release architecture) using the Linux kernel on 32-bit Sun4-style SPARC hardware

    Sparc64

    A port (not yet a release architecture but available via debports) using the Linux kernel on 64-bit versions of sparc-type hardware

    SPI

    Short for "Software in the Public Interest, Inc.", the nonprofit foundation that manages resources and accepts donations on behalf of the Debian Project (which has no legal authority for doing so itself).

    Sponsor

    a Debian Member with upload privileges who uses them on behalf of a package maintainer without such privileges. The sponsor is required to take responsibility for checking that there are no show-stopping quality issues, but is not recorded as the maintainer of the package. A sponsorship may be a one-off event, or the sponsor may also act informally as a mentor, helping to track down bugs and improve the packaging.

    Squeeze

    The codename for Debian 6.0, release date: 2011 (the current stable)

    Stable

    The stable distribution is the release recommended for production use. Each stable release is "promoted" from testing status as the result of a cycle of development, debugging, and integration that usually lasts about two years.

    Stable-proposed-updates

    the suite where proposed fixes for major bugs in stable are queued for inclusion in a point release

    Stable-updates

    The StableUpdates suite (formerly implemented as volatile) is where proposed updates are queued for packages such as virus scanners that become uselessly out of date over the lifespan of a release.

    Suite

    T

    Testing

    testing is the Debian distribution automatically generated out of packages migrating from unstable. The first step towards a new stable release is that testing undergoes a freeze.

    Testing-proposed-updates

    the equivalent to stable-proposed-updates for testing, used only in cases where the fixes need to bypass unstable

    Testing-security

    The testing-security suite is only roughly the testing equivalent of stable's security support, because it is run by a different ?team and because most new package versions fixing security bugs can simply go through unstable as usual

    TINLA

    Short for "This Is Not Legal Advice"; compare IANAL.

    Transition

    Often short for "library transition". A new version of a widely-used dependency hitting unstable can mean that large numbers of related packages need rebuilds or significant fixes before the whole set can migrate to testing.

    Transition package

    A dependency package designed to automatically replace one package with another, to smooth over a rename or similar migration (especially for users performing a dist-upgrade). Not connected with library transitions

    U

    Unstable

    unstable is the Debian distribution where you can find the latest packages introduced into the Debian system.

    Update

    In APT (or front-ends), the process of refreshing the package-management system's information about what packages are available from the registered sources. Not to be confused with (or omitted before) an upgrade

    Upgrade

    • In Debian package management, the process of installing the newest versions of a set of binary packages (by default, all packages that have newer candidates available).

    • In apt specifically, the kind of upgrade that only fetches and installs new versions of packages, without changing the list of installed packages (so for instance a package whose new version has extra dependencies would be left unupgraded). Compare dist-upgrade, and aptitude's safe-upgrade.

    Uploaded

    A wanna-build state

    Urgency

    A ranking system for uploads, indicating how important it is for the new version to reach the archives, and ranging from low to critical. See Policy

    V

    Virtual package

    a binary package that exists in name only, with no associated .deb file; used to organize systems of alternative dependencies (multiple binary packages can claim to "Provide" the same virtual package).

    Volatile

    The volatile suite is (roughly speaking) the old name for stable-updates

    W

    Wanna-build

    a tool forming part of the autobuild system that maintains a database of the build status of packages (see http://www.debian.org/devel/buildd/wanna-build-states for details)

    Wheezy

    The codename for the current testing

    WNPP

    Short for "Work-Needing and Prospective Packages" - a pseudopackage used to collect reports of packages (and potential packages) in need of (new) maintainers in Debian; see http://www.debian.org/devel/wnpp/, ITP, O, RFA, RFH, RFP.

    Woody

    The codename for Debian 3.0, release date: 2002

    X

    X Strike Force (XSF)

    The team responsible for maintaining packages for the X Window System in Debian

    Y

    Z

    . (dot)

    .deb

    File extension used for the standard installable binary package format used by Debian-based distributions.

    .dsc

    File extension used for a Debian Source Control file, which is a particular format of control file forming a crucial component of a source-package

    .tdeb

    File extension used for (proposed) separate translation packages - see Dep-4

    .udeb

    File extension used for special packages containing Debian-Installer modules, not intended for installation on a normal system.