Differences between revisions 1 and 76 (spanning 75 versions)
Revision 1 as of 2007-08-14 06:38:44
Size: 1365
Editor: FranklinPiat
Comment: Initial Page
Revision 76 as of 2011-04-25 23:37:34
Size: 32669
Editor: JustinBRye
Comment: leftovers and internal links
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 below, 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#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(applicant)>>
 Applicant :: A person requesting membership in the [[#debian-project|Debian project]]; prospective [[#debian-developer|Debian developer]].

<<Anchor(application-manager)>>
 Application Manager :: 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:dpkg to perform the actual package installation, removal, etc. The package DebianPkg: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:aptitude and DebianPkg:synaptic.

<<Anchor(architecture)>>
 Architecture ::
##
 * (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` 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|port]]

<<Anchor(archive)>>
 Archive ::
##
 * (Not Debian-specific) a set of items combined into one file, such as a tarball or [[#.deb|.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: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(B)>>
Line 12: Line 64:
[[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(binary)>>
 Binary :: Several potentially confusing (but non-Debian-specific) meanings:
##
 * Any non-textfile, such as a JPEG format image
 * Any 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 [[#.deb|.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(BoF)>>
 BoF :: [[http://en.wikipedia.org/wiki/Birds_of_a_Feather_(computing)|Birds of a Feather]] discussion session, a common event type at DebConf

<<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(C)>>
Line 15: Line 89:
[[Anchor(D)]] <<Anchor(cdbs)>>
 CDBS :: Short for Common Debian Build System (provided by DebianPkg:cdbs)

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

<<Anchor(contrib)>>
 Contrib ::
##
 * 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).

<<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 [[#.deb|.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.

<<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 114:
[[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(dam)>>
 DAM :: See [[#debian-account-manager|Debian Account Manager]].

<<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(debian-account)>>
 Debian Account :: A Debian account is typically the login account of a [[#debian-developer|Debian Developer]]. The term Debian Account is sometime also used to refer to [[#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 to manage [[#debian-account|Debian account]] creation and removal by the [[#debian-project-leader|Debian project leader]]. The DAM has the final decision over an application.

<<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]]. (ToDo: DD/DM/DC/etc should all link to one central explanation of the distinction between them)

<<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 extra packaged software on a running Debian system (see [[#apt|apt]]).

<<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-maintainer)>>
 Debian Maintainer (DM) :: 1. 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.
 :: 2. See also package [[#maintainer||Maintainer]] and [[#debian-developer|Debian Developer]], [[#alioth-account|Alioth account]].

<<Anchor(debian-member)>>
 Debian Member :: Full members of the [[#debian-project|Debian Project]] are referred to as [[#debian-developer|Debian Developers]].

<<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-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(dehs)>>
 DEHS :: Short for Debian External Health Status (see [[DEHS]]).

<<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)>>
<<Anchor(D-I)>>
 D-I :: See [[#debian-installer|Debian-Installer]]

<<Anchor(distribution)>>
 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". 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(dm)>>
 DM :: See [[#debian-maintainer|Debian Maintainer]].

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

<<Anchor(dsa)>>
 DSA :: The [[Teams/DSA|Debian System Administrators]] team, who handle the basic infrastructure of the project.

<<Anchor(E)>>
Line 28: Line 180:
[[Anchor(F)]] <<Anchor(F)>>
Line 31: Line 183:
[[Anchor(G)]] <<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 [[#d-i|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(G)>>
Line 34: Line 205:
[[Anchor(H)]] <<Anchor(H)>>
Line 37: Line 208:
[[Anchor(I)]] <<Anchor(I)>>
Line 40: Line 211:
[[Anchor(J)]] <<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(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 229:
[[Anchor(K)]] <<Anchor(K)>>
Line 46: Line 232:
[[Anchor(L)]] <<Anchor(L)>>
Line 49: Line 235:
[[Anchor(M)]] <<Anchor(M)>>
Line 52: Line 238:
[[Anchor(N)]] <<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 :: 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.

## 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(N)>>
Line 55: Line 264:
[[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(new-maintainer)>>
 New Maintainer :: 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(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 57: Line 281:

[[Anchor(P)]]
 O:: Short for the [[#qa|QA]] status [[#orphaned|Orphaned]]

<<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(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:deborphan. Such unwanted relics are now increasingly tracked by [[#apt|APT]] itself.
## arguably backwards (if I outlive my dependents, I'm not an orphan, I'm a bereaved parent) but moaning won't help

<<Anchor(orphaned)>>
 Orphaned :: (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 of standard or higher, the bug severity 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 296:
[[Anchor(Q)]] <<Anchor(package)>>
 Package ::
##
 * (In Java, TeX, etc.) a unit of software with a single shared namespace
 * (In Debian) See [[#source-package|source package]] or [[#binary-package|binary package]]

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

<<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 workers, and advanced users

<<Anchor(pinning)>>
 Pinning :: 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(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:popularity-contest]], which periodically and anonymously submits statistics about which Debian packages 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 (though of course, `i386` isn't literally a port in the software-porting sense). See [[http://www.debian.org/ports|ports]] and compare [[#architecture|architecture]]

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

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

<<Anchor(R)>>
Line 67: Line 337:
[[Anchor(S)]] <<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(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(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(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:

  1. the root directory ("/") is the top level directory of the file system hierarchy - the part of the "directory tree" that everything else connects to.
  1. 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.)
  1. 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".)
  1. the root zone is the core of the DNS system, where the nameservers that are authoritative for Top Level Domains (the "root nameservers") live.
  1. 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(rort)>>
 RoRT :: Short for Request of Release Team; used in bug reports for package removal, to indicate that issues have been confirmed by the [[Teams/ReleaseTeam|Release Team]].
## ToDo: add the rest from http://ftp-master.debian.org/removals.html (including the non-initialism "RM:")

<<Anchor(S)>>
Line 70: Line 376:
[[Anchor(T)]] <<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(sid)>>
 Sid :: [[DebianSid|sid]] is the 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(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 (.dsc file, upstream tarball, etc) used as input to the package-building process.

<<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(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(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 413:
[[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(tinla)>>
 TINLA :: Short for "This Is Not Legal Advice"; compare [[#ianal|IANAL]].

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

##<<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 435:
[[Anchor(W)]] <<Anchor(W)>>
Line 82: Line 438:
[[Anchor(Z)]] <<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(Z)>>
Line 85: Line 444:
[[Anchor(Y)]] <<Anchor(Y)>>
Line 88: Line 447:
[[Anchor(Z)]] <<Anchor(Z)>>
Line 91: Line 450:

[[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 458:
[[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(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 below, 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 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.

Applicant

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

Application Manager

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

  • (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

Archive

  • (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)

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.

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

  • Any non-textfile, such as a JPEG format image
  • Any 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).

BoF

Birds of a Feather discussion session, a common event type at DebConf

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.

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

Contrib

  • 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

    DAM

    See Debian Account Manager.

    DDPO

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

    Debian Account

    A Debian account is typically the login account of a Debian Developer. The term Debian Account is sometime also used to refer to Debian Maintainer account. See also Alioth account.

    Debian Account Manager (DAM)

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

    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. (ToDo: DD/DM/DC/etc should all link to one central explanation of the distinction between them)

    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 extra packaged software on a running Debian system (see apt).

    Debian New Maintainer

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

    Debian Maintainer (DM)

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

    2. See also package #maintainer and Debian Developer, Alioth account.

    Debian Member

    Full members of the Debian Project are referred to as Debian Developers.

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

    DEHS

    Short for Debian External Health Status (see DEHS).

    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.

    DM

    See Debian Maintainer.

    DPMT

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

    DSA

    The Debian System Administrators team, who handle the basic infrastructure of the project.

    E

    F

    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.

    G

    H

    I

    IANAL

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

    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

    L

    M

    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

    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.

    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.

    New Maintainer

    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.

    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

    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.

    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

    (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 bug severity should be set to important. The term is similarly used to indicate documentation that the author is declaring abandoned; see DDP.

    P

    Package

    PAPT

    Short for Python Applications Packaging Team

    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

    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.

    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 Debian 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 (though of course, i386 isn't literally a port in the software-porting sense). See ports and compare architecture

    PTS

    Short for Package Tracking System

    Q

    QA

    Short for Quality Assurance - see qa.debian.org

    R

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

    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.

    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:
    1. the root directory ("/") is the top level directory of the file system hierarchy - the part of the "directory tree" that everything else connects to.
    2. 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.)
    3. 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".)
    4. the root zone is the core of the DNS system, where the nameservers that are authoritative for Top Level Domains (the "root nameservers") live.
    5. 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".

    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.

    S

    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

    Sid

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

    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.

    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.

    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.

    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.

    TINLA

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

    U

    Unstable

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

    V

    W

    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.

    X

    Y

    Z

    . (dot)

    .deb

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

    .udeb

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