9
9
"Project-Id-Version: PACKAGE VERSION\n"
10
"POT-Creation-Date: 2012-06-09 13:51-0400\n"
10
"POT-Creation-Date: 2012-08-08 21:41-0400\n"
11
11
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
12
12
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
13
13
"Language-Team: LANGUAGE <LL@li.org>\n"
2280
2280
"<emphasis>currently</emphasis> distributing at any point in time. All that "
2281
2281
"can be expected is that it is identical to something that upstream once "
2282
2282
"<emphasis>did</emphasis> distribute. If a difference arises later (say, if "
2283
"upstream notices that he wasn't using maximal compression in his original "
2284
"distribution and then re-<command>gzip</command>s it), that's just too bad. "
2285
"Since there is no good way to upload a new "
2283
"upstream notice that they weren't using maximal compression in their "
2284
"original distribution and then re-<command>gzip</command> it), that's just "
2285
"too bad. Since there is no good way to upload a new "
2286
2286
"<filename>.orig.tar.{gz,bz2,xz}</filename> for the same version, there is "
2287
2287
"not even any point in treating this situation as a bug."
2363
2363
#: best-pkging-practices.dbk:1690
2365
2365
"In these cases the developer must construct a suitable "
2366
"<filename>.orig.tar.{gz,bz2,xz}</filename> file himself. We refer to such a "
2367
"tarball as a repackaged upstream source. Note that a repackaged upstream "
2368
"source is different from a Debian-native package. A repackaged source still "
2369
"comes with Debian-specific changes in a separate "
2366
"<filename>.orig.tar.{gz,bz2,xz}</filename> file themselves. We refer to "
2367
"such a tarball as a repackaged upstream source. Note that a repackaged "
2368
"upstream source is different from a Debian-native package. A repackaged "
2369
"source still comes with Debian-specific changes in a separate "
2370
2370
"<filename>.diff.gz</filename> or "
2371
2371
"<filename>.debian.tar.{gz,bz2,xz}</filename> and still has a version number "
2372
2372
"composed of <replaceable>upstream-version</replaceable> and "
2589
2589
#: best-pkging-practices.dbk:1858
2591
2591
"The long description of the meta-package must clearly document its purpose "
2592
"so that the user knows what he will lose if he removes the package. Being "
2592
"so that the user knows what they will lose if they remove the package. Being "
2593
2593
"explicit about the consequences is recommended. This is particularly "
2594
2594
"important for meta-packages which are installed during initial installation "
2595
2595
"and that have not been explicitly installed by the user. Those tend to be "
3091
3091
#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
3092
3092
#: beyond-pkging.dbk:349
3094
"The sponsor reviews the source package. If she finds issues, she informs the "
3095
"maintainer and asks her to provide a fixed version (the process starts over "
3094
"The sponsor reviews the source package. If they find issues, they inform the "
3095
"maintainer and ask them to provide a fixed version (the process starts over "
3099
3099
#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
3100
3100
#: beyond-pkging.dbk:354
3102
"The sponsor could not find any remaining problem. She builds the package, "
3103
"signs it, and uploads it to Debian."
3102
"The sponsor could not find any remaining problem. They build the package, "
3103
"sign it, and upload it to Debian."
3106
3106
#. type: Content of: <chapter><section><section><para>
3131
3131
#: beyond-pkging.dbk:371
3133
3133
"You should also ensure that the prospective maintainer is going to be a good "
3134
"maintainer. Does she already have some experience with other packages? If "
3135
"yes, is she doing a good job with them (check out some bugs)? Is she "
3136
"familiar with the package and its programming language? Does she have the "
3137
"skills needed for this package? If not, is she able to learn them?"
3134
"maintainer. Do they already have some experience with other packages? If "
3135
"yes, are they doing a good job with them (check out some bugs)? Are they "
3136
"familiar with the package and its programming language? Do they have the "
3137
"skills needed for this package? If not, are they able to learn them?"
3140
3140
#. type: Content of: <chapter><section><section><para>
3141
3141
#: beyond-pkging.dbk:379
3143
"It's also a good idea to know where she stands towards Debian: does she "
3144
"agree with Debian's philosophy and does she intend to join Debian? Given how "
3145
"easy it is to become a Debian Maintainer, you might want to only sponsor "
3143
"It's also a good idea to know where they stand with respect to Debian: do "
3144
"they agree with Debian's philosophy and do they intend to join Debian? Given "
3145
"how easy it is to become a Debian Maintainer, you might want to only sponsor "
3146
3146
"people who plan to join. That way you know from the start that you won't "
3147
3147
"have to act as a sponsor indefinitely."
3281
3281
#: beyond-pkging.dbk:474
3283
3283
"If the audit did not reveal any problem, you can build the package and "
3284
"upload it to Debian. Remember that even if you're not the maintainer, the "
3285
"sponsor is still responsible of what he uploaded to Debian. That's why "
3284
"upload it to Debian. Remember that even if you're not the maintainer, as a "
3285
"sponsor you are still responsible for what you upload to Debian. That's why "
3286
3286
"you're encouraged to keep up with the package through the <xref "
3287
3287
"linkend=\"pkg-tracking-system\"/>."
3295
3295
"file. The <literal>Maintainer</literal> field of the "
3296
3296
"<filename>control</filename> file and the <filename>changelog</filename> "
3297
3297
"should list the person who did the packaging, i.e. the sponsoree. That way "
3298
"she will get all the BTS mail."
3298
"they will get all the BTS mail."
3301
3301
#. type: Content of: <chapter><section><section><section><para>
3388
3388
"linkend=\"pkg-tracking-system\"/>) to verify if the maintainer has not "
3389
3389
"missed something important. Maybe there are translations updates sitting in "
3390
3390
"the BTS that could have been integrated. Maybe the package has been NMUed "
3391
"and the maintainer forgot to integrate the changes from the NMU in his "
3392
"package. Maybe there's a release critical bug that he has left unhandled and "
3393
"that's blocking migration to <literal>testing</literal>. Whatever. If you "
3394
"find something that she could have done (better), it's time to tell her so "
3395
"that she can improve for next time, and so that she has a better "
3396
"understanding of her responsibilities."
3391
"and the maintainer forgot to integrate the changes from the NMU into their "
3392
"package. Maybe there's a release critical bug that they have left unhandled "
3393
"and that's blocking migration to <literal>testing</literal>. If you find "
3394
"something that they could have done (better), it's time to tell them so that "
3395
"they can improve for next time, and so that they have a better understanding "
3396
"of their responsibilities."
3399
3399
#. type: Content of: <chapter><section><section><section><para>
3483
3483
#: developer-duties.dbk:39
3485
3485
"Most of the package maintainer's work goes into providing updated versions "
3486
"of packages in <literal>unstable</literal>, but his job also entails taking "
3487
"care of the packages in the current <literal>stable</literal> release."
3486
"of packages in <literal>unstable</literal>, but their job also entails "
3487
"taking care of the packages in the current <literal>stable</literal> "
3490
3491
#. type: Content of: <chapter><section><section><para>
3539
3540
#: developer-duties.dbk:79
3541
3542
"Lack of attention to RC bugs is often interpreted by the QA team as a sign "
3542
"that the maintainer has disappeared without properly orphaning his package. "
3543
"The MIA team might also get involved, which could result in your packages "
3544
"being orphaned (see <xref linkend=\"mia-qa\" />)."
3543
"that the maintainer has disappeared without properly orphaning their "
3544
"package. The MIA team might also get involved, which could result in your "
3545
"packages being orphaned (see <xref linkend=\"mia-qa\" />)."
3547
3548
#. type: Content of: <chapter><section><section><title>
4179
4180
#: l10n.dbk:160
4181
4182
"The best solution may be to mark the bug as forwarded to upstream, and "
4182
"forward it to both the previous translator and his/her team (using the "
4183
"forward it to both the previous translator and their team (using the "
4183
4184
"corresponding debian-l10n-XXX mailing list)."
6313
6314
"Packages are not removed from <literal>testing</literal> directly. Rather, "
6314
6315
"they will be removed automatically after the package has been removed from "
6315
6316
"<literal>unstable</literal> and no package in <literal>testing</literal> "
6317
"depends on it. (Removals from <literal>testing</literal> are possible though "
6318
"by filing a removal bug report against the <systemitem "
6319
"role=\"package\">&release-debian-org;</systemitem> pseudo-package. See the "
6320
"section <xref linkend=\"removals\"/>.)"
6319
6323
#. type: Content of: <chapter><section><section><para>
6322
6326
"There is one exception when an explicit removal request is not necessary: If "
6323
6327
"a (source or binary) package is no longer built from source, it will be "
6393
6397
#. type: Content of: <chapter><section><section><section><title>
6395
6399
msgid "Removing packages from <filename>Incoming</filename>"
6398
6402
#. type: Content of: <chapter><section><section><section><para>
6401
6405
"In the past, it was possible to remove packages from "
6402
6406
"<filename>incoming</filename>. However, with the introduction of the new "
6412
6416
#. type: Content of: <chapter><section><section><title>
6414
6418
msgid "Replacing or renaming packages"
6417
6421
#. type: Content of: <chapter><section><section><para>
6420
6424
"When the upstream maintainers for one of your packages chose to rename their "
6421
6425
"software (or you made a mistake naming your package), you should follow a "
6451
6455
#. type: Content of: <chapter><section><section><title>
6453
6457
msgid "Orphaning a package"
6456
6460
#. type: Content of: <chapter><section><section><para>
6459
6463
"If you can no longer maintain a package, you need to inform others, and see "
6460
6464
"that the package is marked as orphaned. You should set the package "
6474
6478
#. type: Content of: <chapter><section><section><para>
6477
6481
"If you just intend to give the package away, but you can keep maintainership "
6478
6482
"for the moment, then you should instead submit a bug against <systemitem "
6485
6489
#. type: Content of: <chapter><section><section><para>
6487
6491
msgid "More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>."
6490
6494
#. type: Content of: <chapter><section><section><title>
6492
6496
msgid "Adopting a package"
6495
6499
#. type: Content of: <chapter><section><section><para>
6498
6502
"A list of packages in need of a new maintainer is available in the <ulink "
6499
6503
"url=\"&url-wnpp;\">Work-Needing and Prospective Packages list "
6505
6509
#. type: Content of: <chapter><section><section><para>
6508
6512
"It is not OK to simply take over a package that you feel is neglected — that "
6509
6513
"would be package hijacking. You can, of course, contact the current "
6515
6519
#. type: Content of: <chapter><section><section><para>
6518
6522
"Generally, you may not take over the package without the assent of the "
6519
6523
"current maintainer. Even if they ignore you, that is still not grounds to "
6541
6545
#. type: Content of: <chapter><section><title>
6543
6547
msgid "Porting and being ported"
6546
6550
#. type: Content of: <chapter><section><para>
6549
6553
"Debian supports an ever-increasing number of architectures. Even if you are "
6550
6554
"not a porter, and you don't use any architecture but one, it is part of your "
6567
6571
#. type: Content of: <chapter><section><section><title>
6569
6573
msgid "Being kind to porters"
6572
6576
#. type: Content of: <chapter><section><section><para>
6575
6579
"Porters have a difficult and unique task, since they are required to deal "
6576
6580
"with a large volume of packages. Ideally, every source package should build "
6619
6623
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
6622
6626
"If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be "
6623
6627
"of assistance (see <xref linkend=\"dpkg-depcheck\"/>)."
6626
6630
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
6629
6633
"See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for "
6630
6634
"instructions on setting build dependencies."
6633
6637
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
6636
6640
"Don't set architecture to a value other than <literal>all</literal> or "
6637
6641
"<literal>any</literal> unless you really mean it. In too many cases, "
6672
6676
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
6675
6679
"Don't depend on the package you're building being installed already (a "
6676
6680
"sub-case of the above issue). There are, of course, exceptions to this rule, "
6681
6685
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
6684
6688
"Don't rely on the compiler being a certain version, if possible. If not, "
6685
6689
"then make sure your build dependencies reflect the restrictions, although "
6701
6705
#. type: Content of: <chapter><section><section><title>
6703
6707
msgid "Guidelines for porter uploads"
6706
6710
#. type: Content of: <chapter><section><section><para>
6709
6713
"If the package builds out of the box for the architecture to be ported to, "
6710
6714
"you are in luck and your job is easy. This section applies to that case; it "
6747
6751
#. type: Content of: <chapter><section><section><section><title>
6749
6753
msgid "Recompilation or binary-only NMU"
6752
6756
#. type: Content of: <chapter><section><section><section><para>
6755
6759
"Sometimes the initial porter upload is problematic because the environment "
6756
6760
"in which the package was built was not good enough (outdated or obsolete "
6782
6786
#. type: Content of: <chapter><section><section><section><para>
6785
6789
"Such recompilations require special ``magic'' version numbering, so that the "
6786
6790
"archive maintenance tools recognize that, even though there is a new Debian "
6792
6796
#. type: Content of: <chapter><section><section><section><para><footnote><para>
6795
6799
"In the past, such NMUs used the third-level number on the Debian part of the "
6796
6800
"revision to denote their recompilation-only status; however, this syntax was "
6824
6828
#. type: Content of: <chapter><section><section><section><title>
6826
6830
msgid "When to do a source NMU if you are a porter"
6829
6833
#. type: Content of: <chapter><section><section><section><para>
6832
6836
"Porters doing a source NMU generally follow the guidelines found in <xref "
6833
6837
"linkend=\"nmu\"/>, just like non-porters. However, it is expected that the "
6842
6846
#. type: Content of: <chapter><section><section><section><para>
6845
6849
"If you are a porter doing an NMU for <literal>unstable</literal>, the above "
6846
6850
"guidelines for porting should be followed, with two variations. Firstly, "
6868
6872
#. type: Content of: <chapter><section><section><section><para>
6871
6875
"Porters should try to avoid patches which simply kludge around bugs in the "
6872
6876
"current version of the compile environment, kernel, or libc. Sometimes such "
6888
6892
#. type: Content of: <chapter><section><section><title>
6890
6894
msgid "Porting infrastructure and automation"
6893
6897
#. type: Content of: <chapter><section><section><para>
6896
6900
"There is infrastructure and several tools to help automate package porting. "
6897
6901
"This section contains a brief overview of this automation and porting to "
6902
6906
#. type: Content of: <chapter><section><section><section><title>
6904
6908
msgid "Mailing lists and web pages"
6907
6911
#. type: Content of: <chapter><section><section><section><para>
6910
6914
"Web pages containing the status of each port can be found at <ulink "
6911
6915
"url=\"&url-debian-ports;\"></ulink>."
6914
6918
#. type: Content of: <chapter><section><section><section><para>
6917
6921
"Each port of Debian has a mailing list. The list of porting mailing lists "
6918
6922
"can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These "
6923
6927
#. type: Content of: <chapter><section><section><section><title>
6925
6929
msgid "Porter tools"
6928
6932
#. type: Content of: <chapter><section><section><section><para>
6931
6935
"Descriptions of several porting tools can be found in <xref "
6932
6936
"linkend=\"tools-porting\"/>."
6935
6939
#. type: Content of: <chapter><section><section><section><title>
6937
6941
msgid "<systemitem role=\"package\">wanna-build</systemitem>"
6940
6944
#. type: Content of: <chapter><section><section><section><para>
6943
6947
"The <systemitem role=\"package\">wanna-build</systemitem> system is used as "
6944
6948
"a distributed, client-server build distribution system. It is usually used "
6984
6988
#. type: Content of: <chapter><section><section><section><para>
6987
6991
"The wanna-build team, in charge of the buildds, can be reached at "
6988
6992
"<literal>debian-wb-team@lists.debian.org</literal>. To determine who "
6993
6997
#. type: Content of: <chapter><section><section><section><para>
6996
7000
"When requesting binNMUs or give-backs (retries after a failed build), please "
6997
7001
"use the format described at <ulink url=\"&url-release-wb;\"/>."
7000
7004
#. type: Content of: <chapter><section><section><title>
7002
7006
msgid "When your package is <emphasis>not</emphasis> portable"
7005
7009
#. type: Content of: <chapter><section><section><para>
7008
7012
"Some packages still have issues with building and/or working on some of the "
7009
7013
"architectures supported by Debian, and cannot be ported at all, or not "
7016
7020
#. type: Content of: <chapter><section><section><para>
7019
7023
"In order to prevent broken packages from being uploaded to the archive, and "
7020
7024
"wasting buildd time, you need to do a few things:"
7023
7027
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7026
7030
"First, make sure your package <emphasis>does</emphasis> fail to build on "
7027
7031
"architectures that it cannot support. There are a few ways to achieve "
7035
7039
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7038
7042
"Additionally, if you believe the list of supported architectures is pretty "
7039
7043
"constant, you should change <literal>any</literal> to a list of supported "
7044
7048
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7047
7051
"In order to prevent autobuilders from needlessly trying to build your "
7048
7052
"package, it must be included in <filename>Packages-arch-specific</filename>, "
7066
7070
#. type: Content of: <chapter><section><section><title>
7068
7072
msgid "Marking non-free packages as auto-buildable"
7071
7075
#. type: Content of: <chapter><section><section><para>
7074
7078
"By default packages from the <literal>non-free</literal> section are not "
7075
7079
"built by the autobuilder network (mostly because the license of the packages "
7080
7084
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
7083
7087
"Check whether it is legally allowed and technically possible to auto-build "
7087
7091
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
7090
7094
"Add <literal>XS-Autobuild: yes</literal> into the header part of "
7091
7095
"<filename>debian/control</filename>;"
7094
7098
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
7097
7101
"Send an email to &email-nonfree-release; and explain why the package can "
7098
7102
"legitimately and technically be auto-built."
7101
7105
#. type: Content of: <chapter><section><title>
7103
7107
msgid "Non-Maintainer Uploads (NMUs)"
7106
7110
#. type: Content of: <chapter><section><para>
7109
7113
"Every package has one or more maintainers. Normally, these are the people "
7110
7114
"who work on and upload new versions of the package. In some situations, it "
7117
7121
#. type: Content of: <chapter><section><section><title>
7119
7123
msgid "When and how to do an NMU"
7122
7126
#. type: Content of: <chapter><section><section><para>
7124
7128
msgid "Before doing an NMU, consider the following questions:"
7127
7131
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7130
7134
"Does your NMU really fix bugs? Fixing cosmetic issues or changing the "
7131
7135
"packaging style in NMUs is discouraged."
7134
7138
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7137
7141
"Did you give enough time to the maintainer? When was the bug reported to the "
7138
7142
"BTS? Being busy for a week or two isn't unusual. Is the bug so severe that "
7161
7165
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7164
7168
"If the maintainer is usually active and responsive, have you tried to "
7165
"contact him? In general it should be considered preferable that a maintainer "
7166
"takes care of an issue himself and that he is given the chance to review and "
7167
"correct your patch, because he can be expected to be more aware of potential "
7168
"issues which an NMUer might miss. It is often a better use of everyone's "
7169
"time if the maintainer is given an opportunity to upload a fix on their own."
7169
"contact them? In general it should be considered preferable that maintainers "
7170
"take care of an issue themselves and that they are given the chance to "
7171
"review and correct your patch, because they can be expected to be more aware "
7172
"of potential issues which an NMUer might miss. It is often a better use of "
7173
"everyone's time if the maintainer is given an opportunity to upload a fix on "
7172
7177
#. type: Content of: <chapter><section><section><para>
7175
7180
"When doing an NMU, you must first make sure that your intention to NMU is "
7176
7181
"clear. Then, you must send a patch with the differences between the current "
7211
7216
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7213
7218
msgid "Upload fixing only release-critical bugs older than 7 days: 2 days"
7216
7221
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7218
7223
msgid "Upload fixing only release-critical and important bugs: 5 days"
7221
7226
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7223
7228
msgid "Other NMUs: 10 days"
7226
7231
#. type: Content of: <chapter><section><section><para>
7229
7234
"Those delays are only examples. In some cases, such as uploads fixing "
7230
7235
"security issues, or fixes for trivial bugs that blocking a transition, it is "
7234
7239
#. type: Content of: <chapter><section><section><para>
7237
7242
"Sometimes, release managers decide to allow NMUs with shorter delays for a "
7238
7243
"subset of bugs (e.g release-critical bugs older than 7 days). Also, some "
7265
7270
#. type: Content of: <chapter><section><section><title>
7267
7272
msgid "NMUs and <filename>debian/changelog</filename>"
7270
7275
#. type: Content of: <chapter><section><section><para>
7273
7278
"Just like any other (source) upload, NMUs must add an entry to "
7274
7279
"<filename>debian/changelog</filename>, telling what has changed with this "
7279
7284
#. type: Content of: <chapter><section><section><screen>
7282
7287
msgid " * Non-maintainer upload.\n"
7285
7290
#. type: Content of: <chapter><section><section><para>
7287
7292
msgid "The way to version NMUs differs for native and non-native packages."
7290
7295
#. type: Content of: <chapter><section><section><para>
7293
7298
"If the package is a native package (without a Debian revision in the version "
7294
7299
"number), the version must be the version of the last maintainer upload, plus "
7314
7319
#. type: Content of: <chapter><section><section><para>
7317
7322
"In both cases, if the last upload was also an NMU, the counter should be "
7318
7323
"increased. For example, if the current version is "
7334
7339
#. type: Content of: <chapter><section><section><para>
7337
7342
"If you upload a package to testing or stable, you sometimes need to \"fork\" "
7338
7343
"the version number tree. This is the case for security uploads, for "
7357
7362
#. type: Content of: <chapter><section><section><title>
7359
7364
msgid "Using the <literal>DELAYED/</literal> queue"
7362
7367
#. type: Content of: <chapter><section><section><para>
7365
7370
"Having to wait for a response after you request permission to NMU is "
7366
7371
"inefficient, because it costs the NMUer a context switch to come back to the "
7369
7374
"perform all the necessary tasks at the same time. For instance, instead of "
7370
7375
"telling the maintainer that you will upload the updated package in 7 days, "
7371
7376
"you should upload the package to <literal>DELAYED/7</literal> and tell the "
7372
"maintainer that he has 7 days to react. During this time, the maintainer "
7377
"maintainer that they have 7 days to react. During this time, the maintainer "
7373
7378
"can ask you to delay the upload some more, or cancel your upload."
7376
7381
#. type: Content of: <chapter><section><section><para>
7379
7384
"The <literal>DELAYED</literal> queue should not be used to put additional "
7380
7385
"pressure on the maintainer. In particular, it's important that you are "
7381
7386
"available to cancel or delay the upload before the delay expires since the "
7382
"maintainer cannot cancel the upload himself."
7387
"maintainer cannot cancel the upload themselves."
7385
7390
#. type: Content of: <chapter><section><section><para>
7388
7393
"If you make an NMU to <literal>DELAYED</literal> and the maintainer updates "
7389
"his package before the delay expires, your upload will be rejected because a "
7394
"the package before the delay expires, your upload will be rejected because a "
7390
7395
"newer version is already available in the archive. Ideally, the maintainer "
7391
7396
"will take care to include your proposed changes (or at least a solution for "
7392
7397
"the problems they address) in that upload."
7395
7400
#. type: Content of: <chapter><section><section><title>
7397
7402
msgid "NMUs from the maintainer's point of view"
7400
7405
#. type: Content of: <chapter><section><section><para>
7403
7408
"When someone NMUs your package, this means they want to help you to keep it "
7404
7409
"in good shape. This gives users fixed packages faster. You can consider "
7419
7424
#. type: Content of: <chapter><section><section><title>
7421
7426
msgid "Source NMUs vs Binary-only NMUs (binNMUs)"
7424
7429
#. type: Content of: <chapter><section><section><para>
7427
7432
"The full name of an NMU is <emphasis>source NMU</emphasis>. There is also "
7428
7433
"another type, namely the <emphasis>binary-only NMU</emphasis>, or "
7433
7438
#. type: Content of: <chapter><section><section><para>
7436
7441
"When a library (or other dependency) is updated, the packages using it may "
7437
7442
"need to be rebuilt. Since no changes to the source are needed, the same "
7451
7456
#. type: Content of: <chapter><section><section><para>
7454
7459
"Buildds upload packages for their architecture to the archive as binary-only "
7455
7460
"uploads. Strictly speaking, these are binNMUs. However, they are not "
7460
7465
#. type: Content of: <chapter><section><section><title>
7462
7467
msgid "NMUs vs QA uploads"
7465
7470
#. type: Content of: <chapter><section><section><para>
7468
7473
"NMUs are uploads of packages by somebody else than their assigned "
7469
7474
"maintainer. There is another type of upload where the uploaded package is "
7473
7478
#. type: Content of: <chapter><section><section><para>
7476
7481
"QA uploads are very much like normal maintainer uploads: they may fix "
7477
7482
"anything, even minor issues; the version numbering is normal, and there is "
7483
7488
#. type: Content of: <chapter><section><section><screen>
7486
7491
msgid " * QA upload.\n"
7489
7494
#. type: Content of: <chapter><section><section><para>
7492
7497
"If you want to do an NMU, and it seems that the maintainer is not active, it "
7493
7498
"is wise to check if the package is orphaned (this information is displayed "
7510
7515
#. type: Content of: <chapter><section><section><title>
7512
7517
msgid "NMUs vs team uploads"
7515
7520
#. type: Content of: <chapter><section><section><para>
7518
7523
"Sometimes you are fixing and/or updating a package because you are member of "
7519
7524
"a packaging team (which uses a mailing list as <literal>Maintainer</literal> "
7529
7534
#. type: Content of: <chapter><section><section><screen>
7532
7537
msgid " * Team upload.\n"
7535
7540
#. type: Content of: <chapter><section><title>
7537
7542
msgid "Collaborative maintenance"
7540
7545
#. type: Content of: <chapter><section><para>
7543
7548
"Collaborative maintenance is a term describing the sharing of Debian package "
7544
7549
"maintenance duties by several people. This collaboration is almost always a "
7562
7567
#. type: Content of: <chapter><section><para>
7565
7570
"In its most basic form, the process of adding a new co-maintainer is quite "
7569
7574
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
7572
7577
"Setup the co-maintainer with access to the sources you build the package "
7573
7578
"from. Generally this implies you are using a network-capable version "
7595
7600
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
7598
7603
"Using the PTS (<xref linkend=\"pkg-tracking-system\"/>), the co-maintainers "
7599
7604
"should subscribe themselves to the appropriate source package."
7602
7607
#. type: Content of: <chapter><section><para>
7605
7610
"Another form of collaborative maintenance is team maintenance, which is "
7606
7611
"recommended if you maintain several packages with the same group of "
7644
7649
#. type: Content of: <chapter><section><title>
7646
7651
msgid "The testing distribution"
7649
7654
#. type: Content of: <chapter><section><section><title>
7654
7659
#. type: Content of: <chapter><section><section><para>
7657
7662
"Packages are usually installed into the <literal>testing</literal> "
7658
7663
"distribution after they have undergone some degree of "
7672
7677
#. type: Content of: <chapter><section><section><title>
7674
7679
msgid "Updates from unstable"
7677
7682
#. type: Content of: <chapter><section><section><para>
7680
7685
"The scripts that update the <literal>testing</literal> distribution are run "
7681
7686
"twice each day, right after the installation of the updated packages; these "
7688
7693
#. type: Content of: <chapter><section><section><para>
7691
7696
"The inclusion of a package from <literal>unstable</literal> is conditional "
7692
7697
"on the following:"
7695
7700
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7698
7703
"The package must have been available in <literal>unstable</literal> for 2, 5 "
7699
7704
"or 10 days, depending on the urgency (high, medium or low). Please note "
7700
7705
"that the urgency is sticky, meaning that the highest urgency uploaded since "
7701
"the previous <literal>testing</literal> transition is taken into account. "
7702
"Those delays may be doubled during a freeze, or <literal>testing</literal> "
7703
"transitions may be switched off altogether;"
7706
"the previous <literal>testing</literal> transition is taken into account;"
7706
7709
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7709
7712
"It must not have new release-critical bugs (RC bugs affecting the version "
7710
7713
"available in <literal>unstable</literal>, but not affecting the version in "
7722
7725
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7725
7728
"It must not break any dependency of a package which is already available in "
7726
7729
"<literal>testing</literal>;"
7729
7732
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7732
7735
"The packages on which it depends must either be available in "
7733
7736
"<literal>testing</literal> or they must be accepted into "
7734
7737
"<literal>testing</literal> at the same time (and they will be if they "
7735
"fulfill all the necessary criteria)."
7738
"fulfill all the necessary criteria);"
7741
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
7744
"The phase of the project. I.e. automatic transitions are turned off during "
7745
"the <emphasis>freeze</emphasis> of the <literal>testing</literal> "
7738
7749
#. type: Content of: <chapter><section><section><para>
7741
7752
"To find out whether a package is progressing into <literal>testing</literal> "
7742
7753
"or not, see the <literal>testing</literal> script output on the <ulink "
7777
7788
#. type: Content of: <chapter><section><section><section><title>
7779
7790
msgid "Out-of-date"
7782
7793
#. FIXME: better rename this file than document rampant professionalism?
7783
7794
#. type: Content of: <chapter><section><section><section><para>
7786
7797
"For the <literal>testing</literal> migration script, outdated means: There "
7787
7798
"are different versions in <literal>unstable</literal> for the release "
7795
7806
#. type: Content of: <chapter><section><section><section><para>
7797
7808
msgid "Consider this example:"
7800
7811
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
7801
#: pkgs.dbk:2467 pkgs.dbk:2500
7812
#: pkgs.dbk:2474 pkgs.dbk:2507
7805
7816
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
7806
#: pkgs.dbk:2468 pkgs.dbk:2501
7817
#: pkgs.dbk:2475 pkgs.dbk:2508
7810
7821
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
7811
#: pkgs.dbk:2473 pkgs.dbk:2507 pkgs.dbk:2569
7822
#: pkgs.dbk:2480 pkgs.dbk:2514 pkgs.dbk:2576
7812
7823
msgid "testing"
7815
7826
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7816
#: pkgs.dbk:2474 pkgs.dbk:2479 pkgs.dbk:2508 pkgs.dbk:2509 pkgs.dbk:2516
7827
#: pkgs.dbk:2481 pkgs.dbk:2486 pkgs.dbk:2515 pkgs.dbk:2516 pkgs.dbk:2523
7820
7831
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7821
#: pkgs.dbk:2475 pkgs.dbk:2510 pkgs.dbk:2515
7832
#: pkgs.dbk:2482 pkgs.dbk:2517 pkgs.dbk:2522
7825
7836
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
7826
#: pkgs.dbk:2478 pkgs.dbk:2513 pkgs.dbk:2570
7837
#: pkgs.dbk:2485 pkgs.dbk:2520 pkgs.dbk:2577
7827
7838
msgid "unstable"
7830
7841
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7831
#: pkgs.dbk:2480 pkgs.dbk:2514
7842
#: pkgs.dbk:2487 pkgs.dbk:2521
7835
7846
#. type: Content of: <chapter><section><section><section><para>
7838
7849
"The package is out of date on <literal>alpha</literal> in "
7839
7850
"<literal>unstable</literal>, and will not go to "
7845
7856
#. type: Content of: <chapter><section><section><section><para>
7848
7859
"However, if ftp-master removes a package in <literal>unstable</literal> "
7849
7860
"(here on <literal>arm</literal>):"
7852
7863
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
7854
7865
msgid "hurd-i386"
7857
7868
#. type: Content of: <chapter><section><section><section><para>
7860
7871
"In this case, the package is up to date on all release architectures in "
7861
7872
"<literal>unstable</literal> (and the extra <literal>hurd-i386</literal> "
7873
7884
#. type: Content of: <chapter><section><section><section><title>
7875
7886
msgid "Removals from testing"
7878
7889
#. type: Content of: <chapter><section><section><section><para>
7881
7892
"Sometimes, a package is removed to allow another package in: This happens "
7882
7893
"only to allow <emphasis>another</emphasis> package to go in if it's ready in "
7896
7907
#. type: Content of: <chapter><section><section><section><para>
7899
7910
"Furthermore, if a package has been removed from <literal>unstable</literal>, "
7900
7911
"and no package in <literal>testing</literal> depends on it any more, then it "
7904
7915
#. type: Content of: <chapter><section><section><section><title>
7906
7917
msgid "Circular dependencies"
7909
7920
#. type: Content of: <chapter><section><section><section><para>
7912
7923
"A situation which is not handled very well by britney is if package "
7913
7924
"<literal>a</literal> depends on the new version of package "
7917
7928
#. type: Content of: <chapter><section><section><section><para>
7919
7930
msgid "An example of this is:"
7922
7933
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7927
7938
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7929
7940
msgid "1; depends: b=1"
7932
7943
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7934
7945
msgid "2; depends: b=2"
7937
7948
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7942
7953
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7944
7955
msgid "1; depends: a=1"
7947
7958
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
7949
7960
msgid "2; depends: a=2"
7952
7963
#. type: Content of: <chapter><section><section><section><para>
7955
7966
"Neither package <literal>a</literal> nor package <literal>b</literal> is "
7956
7967
"considered for update."
7959
7970
#. type: Content of: <chapter><section><section><section><para>
7962
7973
"Currently, this requires some manual hinting from the release team. Please "
7963
7974
"contact them by sending mail to &email-debian-release; if this happens to "
7967
7978
#. type: Content of: <chapter><section><section><section><title>
7969
7980
msgid "Influence of package in testing"
7972
7983
#. type: Content of: <chapter><section><section><section><para>
7975
7986
"Generally, there is nothing that the status of a package in "
7976
7987
"<literal>testing</literal> means for transition of the next version from "
7996
8007
#. type: Content of: <chapter><section><section><section><title>
7998
8009
msgid "Details"
8001
8012
#. type: Content of: <chapter><section><section><section><para>
8003
8014
msgid "If you are interested in details, this is how britney works:"
8006
8017
#. type: Content of: <chapter><section><section><section><para>
8009
8020
"The packages are looked at to determine whether they are valid candidates. "
8010
8021
"This gives the update excuses. The most common reasons why a package is not "
8011
8022
"considered are too young, RC-bugginess, and out of date on some arches. For "
8012
"this part of britney, the release managers have hammers of various sizes to "
8013
"force britney to consider a package. (Also, the base freeze is coded in "
8014
"that part of britney.) (There is a similar thing for binary-only updates, "
8015
"but this is not described here. If you're interested in that, please peruse "
8023
"this part of britney, the release managers have hammers of various sizes, "
8024
"called hints (see below), to force britney to consider a package."
8019
8027
#. type: Content of: <chapter><section><section><section><para>
8022
8030
"Now, the more complex part happens: Britney tries to update "
8023
8031
"<literal>testing</literal> with the valid candidates. For that, britney "
8033
8041
#. type: Content of: <chapter><section><section><section><para>
8036
8044
"If you want to see more details, you can look it up on <ulink "
8037
8045
"url=\"http://&ftp-master-host;/testing/update_output/\"></ulink>."
8040
8048
#. type: Content of: <chapter><section><section><section><para>
8043
8051
"The hints are available via <ulink "
8044
"url=\"http://&ftp-master-host;/testing/hints/\"></ulink>."
8052
"url=\"http://&ftp-master-host;/testing/hints/\"></ulink>, where you can find "
8054
"url=\"http://&ftp-master-host;/testing/hints/README\">description</ulink> as "
8055
"well. With the hints, the Debian Release team can block or unblock "
8056
"packages, ease or force packages into <literal>testing</literal>, remove "
8057
"packages from <literal>testing</literal>, approve uploads to <link "
8058
"linkend=\"t-p-u\">testing-proposed-updates</link> or override the urgency."
8047
8061
#. type: Content of: <chapter><section><section><title>
8049
8063
msgid "Direct updates to testing"
8052
8066
#. type: Content of: <chapter><section><section><para>
8055
8069
"The <literal>testing</literal> distribution is fed with packages from "
8056
8070
"<literal>unstable</literal> according to the rules explained above. "
8095
8109
#. type: Content of: <chapter><section><section><para>
8097
8111
msgid "Please make sure you didn't miss any of these items in your upload:"
8100
8114
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
8103
8117
"Make sure that your package really needs to go through "
8104
8118
"<literal>testing-proposed-updates</literal>, and can't go through "
8108
8122
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
8110
8124
msgid "Make sure that you included only the minimal amount of changes;"
8113
8127
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
8115
8129
msgid "Make sure that you included an appropriate explanation in the changelog;"
8118
8132
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
8121
8135
"Make sure that you've written <literal>testing</literal> or "
8122
8136
"<literal>testing-proposed-updates</literal> into your target distribution;"
8125
8139
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
8128
8142
"Make sure that you've built and tested your package in "
8129
8143
"<literal>testing</literal>, not in <literal>unstable</literal>;"
8132
8146
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
8135
8149
"Make sure that your version number is higher than the version in "
8136
8150
"<literal>testing</literal> and <literal>testing-proposed-updates</literal>, "
8140
8154
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
8143
8157
"After uploading and successful build on all platforms, contact the release "
8144
8158
"team at &email-debian-release; and ask them to approve your upload."
8147
8161
#. type: Content of: <chapter><section><section><title>
8149
8163
msgid "Frequently asked questions"
8152
8166
#. type: Content of: <chapter><section><section><section><title>
8154
8168
msgid "What are release-critical bugs, and how do they get counted?"
8157
8171
#. type: Content of: <chapter><section><section><section><para>
8160
8174
"All bugs of some higher severities are by default considered "
8161
8175
"release-critical; currently, these are <literal>critical</literal>, "
8185
8199
#. type: Content of: <chapter><section><section><section><title>
8188
8202
"How could installing a package into <literal>testing</literal> possibly "
8189
8203
"break other packages?"
8192
8206
#. type: Content of: <chapter><section><section><section><para>
8195
8209
"The structure of the distribution archives is such that they can only "
8196
8210
"contain one version of a package; a package is defined by its name. So when "
8204
8218
#. type: Content of: <chapter><section><section><section><para>
8207
8221
"However, the old version may have provided a binary package with an old "
8208
8222
"soname of a library, such as <literal>libacme-foo0</literal>. Removing the "
8213
8227
#. type: Content of: <chapter><section><section><section><para>
8216
8230
"Evidently, this mainly affects packages which provide changing sets of "
8217
8231
"binary packages in different versions (in turn, mainly libraries). However, "
8486
8500
"Subject: header. The nick should be registered: <ulink "
8487
8501
"url=\"http://freenode.net/faq.shtml#nicksetup\">Nick Setup Page</ulink>. "
8488
8502
"The mail needs to be signed by a key in the Debian keyring. Please see "
8489
"<ulink url=\"http://freenode.net/faq.shtml#projectcloak\">Freenodes "
8503
"<ulink url=\"http://freenode.net/faq.shtml#projectcloak\">Freenode "
8490
8504
"documentation</ulink> for more information about cloaks."
9123
9137
"Active development is done in the <literal>unstable</literal> distribution "
9124
9138
"(that's why this distribution is sometimes called the <literal>development "
9125
"distribution</literal>). Every Debian developer can update his or her "
9126
"packages in this distribution at any time. Thus, the contents of this "
9127
"distribution change from day to day. Since no special effort is made to "
9128
"make sure everything in this distribution is working properly, it is "
9129
"sometimes literally unstable."
9139
"distribution</literal>). Every Debian developer can update their packages "
9140
"in this distribution at any time. Thus, the contents of this distribution "
9141
"change from day to day. Since no special effort is made to make sure "
9142
"everything in this distribution is working properly, it is sometimes "
9143
"literally unstable."
9132
9146
#. type: Content of: <chapter><section><section><section><para>