X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=pkgs.dbk;h=2d2a295ee9873ad53b7dd3ab5498daae7913ea1e;hp=2acdf5c40e15d98208bc19c9e8e40cece75da22d;hb=d291c3aa43e7eca1303204812fe5323b6af9040d;hpb=39f9d44a972a229e8d148d5bc9adc5210e5c7c60 diff --git a/pkgs.dbk b/pkgs.dbk index 2acdf5c..2d2a295 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -174,7 +174,7 @@ output a very verbose description of the problem. Normally, a package should not be uploaded if it causes -lintian to emit errors (they will start with E). +lintian to emit errors (they will start with E). For more information on lintian, see For the native packages, the source package includes a Debian source control file (.dsc) and the source tarball -(.tar.{gz,bz2,lzma}). A source package of a non-native package +(.tar.{gz,bz2,xz}). A source package of a non-native package includes a Debian source control file, the original source tarball -(.orig.tar.{gz,bz2,lzma}) and the Debian changes +(.orig.tar.{gz,bz2,xz}) and the Debian changes (.diff.gz for the source format “1.0” or -.debian.tar.{gz,bz2,lzma} for the source format “3.0 (quilt)”). +.debian.tar.{gz,bz2,xz} for the source format “3.0 (quilt)”). With source format “1.0”, whether a package is native or not was determined @@ -268,7 +268,7 @@ the archive. Please notice that, in non-native packages, permissions on files that are not -present in the *.orig.tar.{gz,bz2,lzma} will not be preserved, as diff does not store file +present in the *.orig.tar.{gz,bz2,xz} will not be preserved, as diff does not store file permissions in the patch. However when using source format “3.0 (quilt)”, permissions of files inside the debian directory are preserved since they are stored in a tar archive. @@ -311,8 +311,9 @@ point release. To ensure that your upload will be accepted, you should discuss the changes -with the stable release team before you upload. For that, send a mail to -the &email-debian-release; mailing list, including the patch you want to +with the stable release team before you upload. For that, file a bug against +the release.debian.org pseudo-package +using reportbug, including the patch you want to apply to the package version currently in stable. Always be verbose and detailed in your changelog entries for uploads to the stable distribution. @@ -428,7 +429,8 @@ When the specified waiting time is over, the package is moved into the regular incoming directory for processing. This is done through automatic uploading to &ftp-upload-host; in upload-directory -DELAYED/[012345678]-day. 0-day is uploaded +DELAYED/X-day +(X between 0 and 15). 0-day is uploaded multiple times per day to &ftp-upload-host;. @@ -470,11 +472,11 @@ not support delayed uploads. The Debian archive maintainers are responsible for handling package uploads. For the most part, uploads are automatically handled on a daily basis by the -archive maintenance tools, katie. Specifically, updates to -existing packages to the unstable distribution are handled -automatically. In other cases, notably new packages, placing the uploaded -package into the distribution is handled manually. When uploads are handled -manually, the change to the archive may take up to a month to occur. Please +archive maintenance tools, dak process-upload. Specifically, +updates to existing packages to the unstable distribution are +handled automatically. In other cases, notably new packages, placing the +uploaded package into the distribution is handled manually. When uploads are +handled manually, the change to the archive may take some time to occur. Please be patient. @@ -841,14 +843,22 @@ fixing them themselves, sending security advisories, and maintaining When you become aware of a security-related bug in a Debian package, whether or not you are the maintainer, collect pertinent information about the problem, -and promptly contact the security team at -&email-security-team; as soon as possible. DO NOT UPLOAD any packages for stable -without contacting the team. Useful information includes, for example: +and promptly contact the security team, preferably by filing a ticket in +their Request Tracker. +See . +Alternatively you may email &email-security-team;. +DO NOT UPLOAD any packages for +stable without contacting the team. Useful information +includes, for example: +Whether or not the bug is already public. + + + + Which versions of the package are known to be affected by the bug. Check each version that is present in a supported Debian release, as well as testing and unstable. @@ -1151,18 +1161,19 @@ uploads. -Unless the upstream source has been uploaded to security.debian.org - before (by a previous security update), build the upload with full upstream source (dpkg-buildpackage --sa). If there has been a previous upload to -security.debian.org with the same upstream version, you may -upload without upstream source (dpkg-buildpackage -sd). +Unless the upstream source has been uploaded to +security.debian.org before (by a previous security update), +build the upload with full upstream source +(dpkg-buildpackage -sa). If there has been a previous +upload to security.debian.org with the same upstream +version, you may upload without upstream source (dpkg-buildpackage +-sd). Be sure to use the exact same -*.orig.tar.{gz,bz2,lzma} as used in the +*.orig.tar.{gz,bz2,xz} as used in the normal archive, otherwise it is not possible to move the security fix into the main archives later. @@ -1237,7 +1248,7 @@ chapter gives guidelines on what to do in these cases. Moving packages Sometimes a package will change its section. For instance, a package from the -`non-free' section might be GPL'd in a later version, in which case the package +non-free section might be GPL'd in a later version, in which case the package should be moved to `main' or `contrib'. See the Debian Policy Manual for guidelines on what section a package belongs in. @@ -1248,7 +1259,7 @@ control information to place the package in the desired section, and re-upload the package (see the Debian Policy Manual for details). You must ensure that you include the -.orig.tar.{gz,bz2,lzma} in your upload (even if you are not uploading +.orig.tar.{gz,bz2,xz} in your upload (even if you are not uploading a new upstream version), or it will not appear in the new section together with the rest of the package. If your new section is valid, it will be moved automatically. If it does not, then contact the ftpmasters in order to @@ -1268,7 +1279,7 @@ described in . If for some reason you want to completely remove a package (say, if it is an old compatibility library which is no longer required), you need to file a bug -against ftp.debian.org asking that the package be removed; +against &ftp-debian-org; asking that the package be removed; as all bugs, this bug should normally have normal severity. The bug title should be in the form RM: package [architecture list] -- @@ -1278,8 +1289,8 @@ short summary of the reason for the removal request. [architecture list] is optional and only needed if the removal request only applies to some architectures, not all. Note that the reportbug will create a title conforming -to these rules when you use it to report a bug against the -ftp.debian.org pseudo-package. +to these rules when you use it to report a bug against the +&ftp-debian-org; pseudo-package. @@ -1302,11 +1313,11 @@ automatically after the package has been removed from There is one exception when an explicit removal request is not necessary: If a -(source or binary) package is an orphan, it will be removed semi-automatically. -For a binary-package, this means if there is no longer any source package -producing this binary package; if the binary package is just no longer produced -on some architectures, a removal request is still necessary. For a -source-package, this means that all binary packages it refers to have been +(source or binary) package is no longer built from source, it will be removed +semi-automatically. For a binary-package, this means if there is no longer any +source package producing this binary package; if the binary package is just no +longer produced on some architectures, a removal request is still necessary. For +a source-package, this means that all binary packages it refers to have been taken over by another source package. @@ -1384,7 +1395,7 @@ Policy Manual for details). Please note that you should only add a Provides relation if all packages depending on the obsolete package name continue to work after the renaming. Once you've uploaded the package and the package -has moved into the archive, file a bug against ftp.debian.org +has moved into the archive, file a bug against &ftp-debian-org; asking to remove the package with the obsolete name (see ). Do not forget to properly reassign the package's bugs at the same time. @@ -1862,6 +1873,35 @@ role="package">ftp.debian.org. +
+Marking non-free packages as auto-buildable + +By default packages from the non-free section are not built by the autobuilder +network (mostly because the license of the packages could disapprove). +To enable a package to be build you need to perform the following +steps: + + + + +Check whether it is legally allowed and technically possible +to auto-build the package; + + + + +Add XS-Autobuild: yes into the header part +of debian/control; + + + + +Send an email to &email-nonfree-release; and explain why the +package can legitimately and technically be auto-built. + + + +
@@ -1932,9 +1972,9 @@ might be helpful. While preparing the patch, you should better be aware of any package-specific -practices that the maintainer might be using. Taking them into account reduces -the burden of getting your changes integrated back in the normal package -workflow and thus increases the possibilities that that will happen. A good +practices that the maintainer might be using. Taking them into account +reduces the burden of integrating your changes into the normal package +workflow and thus increases the chances that integration will happen. A good place where to look for for possible package-specific practices is debian/README.source. @@ -1946,6 +1986,11 @@ to the maintainer to react (for example, by uploading to the +Upload fixing only release-critical bugs older than 7 days, with no maintainer activity on the bug for 7 days and no indication that a fix is in progress: 0 days + + + + Upload fixing only release-critical bugs older than 7 days: 2 days @@ -2018,7 +2063,7 @@ if the current version is 1.5, then an NMU would get version 1.5+nmu1. -If the package is a not a native package, you should add a minor version number +If the package is not a native package, you should add a minor version number to the Debian revision part of the version number (the portion after the last hyphen). This extra number must start at 1. For example, if the current version is 1.5-2, then an NMU would get @@ -2294,7 +2339,7 @@ In any case, it is a bad idea to automatically put all team members in the a false sense of good maintenance. For the same reason, team members do not need to add themselves to the Uploaders field just because they are uploading the package once, they can do a “Team upload” (see ). Conversely, it it a bad idea to keep a +linkend="nmu-team-upload"/>). Conversely, it is a bad idea to keep a package with only the mailing list address as a Maintainer and no Uploaders. @@ -2392,7 +2437,7 @@ more information about the usual problems which may be causing such troubles. Sometimes, some packages never enter testing because the -set of inter-relationship is too complicated and cannot be sorted out by the +set of interrelationship is too complicated and cannot be sorted out by the scripts. See below for details. @@ -2596,11 +2641,8 @@ tests include this package. Hints from the release team are processed before or after this main run, depending on the exact type. -If you want to see more details, you can look it up on -merkel:/org/&ftp-debian-org;/testing/update_out/ (or -in merkel:~aba/testing/update_out to see a setup with -a smaller packages file). Via web, it's at . +If you want to see more details, you can look it up on . The hints are available via