1
# SOME DESCRIPTIVE TITLE
2
# Copyright (C) 2007 Free Software Foundation, Inc.
9
"Project-Id-Version: PACKAGE VERSION\n"
10
"Report-Msgid-Bugs-To: \n"
11
"POT-Creation-Date: 2007-07-01 21:16+0000\n"
12
"PO-Revision-Date: 2007-07-01 23:09+0000\n"
13
"Last-Translator: <>\n"
16
"Content-Type: text/plain; charset=UTF-8\n"
17
"Content-Transfer-Encoding: "
19
# type: Content of: <chapter><title>
20
#: beyond-pkging.dbk:7
21
msgid "Beyond Packaging"
22
msgstr "Au-delà de l'empaquetage"
24
# type: Content of: <chapter><para>
25
#: beyond-pkging.dbk:9
27
"Debian is about a lot more than just packaging software and maintaining "
28
"those packages. This chapter contains information about ways, often really "
29
"critical ways, to contribute to Debian beyond simply creating and "
30
"maintaining packages."
33
# type: Content of: <chapter><para>
34
#: beyond-pkging.dbk:14
36
"As a volunteer organization, Debian relies on the discretion of its members "
37
"in choosing what they want to work on and in choosing the most critical "
38
"thing to spend their time on."
41
# type: Content of: <chapter><section><title>
42
#: beyond-pkging.dbk:19
44
msgstr "Rapporter des bogues"
46
# type: Content of: <chapter><section><para>
47
#: beyond-pkging.dbk:21
49
"We encourage you to file bugs as you find them in Debian packages. In fact, "
50
"Debian developers are often the first line testers. Finding and reporting "
51
"bugs in other developers' packages improves the quality of Debian."
54
# type: Content of: <chapter><section><para>
55
#: beyond-pkging.dbk:26
57
"Read the <ulink url=\"&url-bts-report;\">instructions for reporting bugs</"
58
"ulink> in the Debian <ulink url=\"&url-bts;\">bug tracking system</ulink>."
61
# type: Content of: <chapter><section><para>
62
#: beyond-pkging.dbk:31
64
"Try to submit the bug from a normal user account at which you are likely to "
65
"receive mail, so that people can reach you if they need further information "
66
"about the bug. Do not submit bugs as root."
69
# type: Content of: <chapter><section><para>
70
#: beyond-pkging.dbk:36
72
"You can use a tool like <citerefentry> <refentrytitle>reportbug</"
73
"refentrytitle> <manvolnum>1</manvolnum> </citerefentry> to submit bugs. It "
74
"can automate and generally ease the process."
77
# type: Content of: <chapter><section><para>
78
#: beyond-pkging.dbk:41
80
"Make sure the bug is not already filed against a package. Each package has "
81
"a bug list easily reachable at <literal>http://&bugs-host;/"
82
"<replaceable>packagename</replaceable></literal> Utilities like "
83
"<citerefentry> <refentrytitle>querybts</refentrytitle> <manvolnum>1</"
84
"manvolnum> </citerefentry> can also provide you with this information (and "
85
"<command>reportbug</command> will usually invoke <command>querybts</command> "
86
"before sending, too)."
89
# type: Content of: <chapter><section><para>
90
#: beyond-pkging.dbk:50
92
"Try to direct your bugs to the proper location. When for example your bug "
93
"is about a package which overwrites files from another package, check the "
94
"bug lists for <emphasis>both</emphasis> of those packages in order to avoid "
95
"filing duplicate bug reports."
98
# type: Content of: <chapter><section><para>
99
#: beyond-pkging.dbk:56
101
"For extra credit, you can go through other packages, merging bugs which are "
102
"reported more than once, or tagging bugs `fixed' when they have already been "
103
"fixed. Note that when you are neither the bug submitter nor the package "
104
"maintainer, you should not actually close the bug (unless you secure "
105
"permission from the maintainer)."
108
# type: Content of: <chapter><section><para>
109
#: beyond-pkging.dbk:63
111
"From time to time you may want to check what has been going on with the bug "
112
"reports that you submitted. Take this opportunity to close those that you "
113
"can't reproduce anymore. To find out all the bugs you submitted, you just "
114
"have to visit <literal>http://&bugs-host;/from:<replaceable><your-email-"
115
"addr></replaceable></literal>."
118
# type: Content of: <chapter><section><section><title>
119
#: beyond-pkging.dbk:70
120
msgid "Reporting lots of bugs at once (mass bug filing)"
123
# type: Content of: <chapter><section><section><para>
124
#: beyond-pkging.dbk:72
126
"Reporting a great number of bugs for the same problem on a great number of "
127
"different packages — i.e., more than 10 — is a deprecated practice. Take "
128
"all possible steps to avoid submitting bulk bugs at all. For instance, if "
129
"checking for the problem can be automated, add a new check to <systemitem "
130
"role=\"package\">lintian</systemitem> so that an error or warning is emitted."
133
# type: Content of: <chapter><section><section><para>
134
#: beyond-pkging.dbk:79
136
"If you report more than 10 bugs on the same topic at once, it is recommended "
137
"that you send a message to &email-debian-devel; describing your intention "
138
"before submitting the report, and mentioning the fact in the subject of your "
139
"mail. This will allow other developers to verify that the bug is a real "
140
"problem. In addition, it will help prevent a situation in which several "
141
"maintainers start filing the same bug report simultaneously."
144
# type: Content of: <chapter><section><section><para>
145
#: beyond-pkging.dbk:87
147
"Please use the programms <command>dd-list</command> and if appropriate "
148
"<command>whodepends</command> (from the package devscripts) to generate a "
149
"list of all affected packages, and include the output in your mail to &email-"
153
# type: Content of: <chapter><section><section><para>
154
#: beyond-pkging.dbk:93
156
"Note that when sending lots of bugs on the same subject, you should send the "
157
"bug report to <email>maintonly@&bugs-host;</email> so that the bug report is "
158
"not forwarded to the bug distribution mailing list."
161
# type: Content of: <chapter><section><title>
162
#: beyond-pkging.dbk:102
163
msgid "Quality Assurance effort"
166
# type: Content of: <chapter><section><section><title>
167
#: beyond-pkging.dbk:104
171
# type: Content of: <chapter><section><section><para>
172
#: beyond-pkging.dbk:106
174
"Even though there is a dedicated group of people for Quality Assurance, QA "
175
"duties are not reserved solely for them. You can participate in this effort "
176
"by keeping your packages as bug-free as possible, and as lintian-clean (see "
177
"<xref linkend=\"lintian\"/> ) as possible. If you do not find that "
178
"possible, then you should consider orphaning some of your packages (see "
179
"<xref linkend=\"orphaning\"/> ). Alternatively, you may ask the help of "
180
"other people in order to catch up with the backlog of bugs that you have "
181
"(you can ask for help on &email-debian-qa; or &email-debian-devel;). At the "
182
"same time, you can look for co-maintainers (see <xref linkend="
183
"\"collaborative-maint\"/> )."
186
# type: Content of: <chapter><section><section><title>
187
#: beyond-pkging.dbk:120
188
msgid "Bug squashing parties"
191
# type: Content of: <chapter><section><section><para>
192
#: beyond-pkging.dbk:122
194
"From time to time the QA group organizes bug squashing parties to get rid of "
195
"as many problems as possible. They are announced on &email-debian-devel-"
196
"announce; and the announcement explains which area will be the focus of the "
197
"party: usually they focus on release critical bugs but it may happen that "
198
"they decide to help finish a major upgrade (like a new perl version which "
199
"requires recompilation of all the binary modules)."
202
# type: Content of: <chapter><section><section><para>
203
#: beyond-pkging.dbk:131
205
"The rules for non-maintainer uploads differ during the parties because the "
206
"announcement of the party is considered prior notice for NMU. If you have "
207
"packages that may be affected by the party (because they have release "
208
"critical bugs for example), you should send an update to each of the "
209
"corresponding bug to explain their current status and what you expect from "
210
"the party. If you don't want an NMU, or if you're only interested in a "
211
"patch, or if you will deal yourself with the bug, please explain that in the "
215
# type: Content of: <chapter><section><section><para>
216
#: beyond-pkging.dbk:140
218
"People participating in the party have special rules for NMU, they can NMU "
219
"without prior notice if they upload their NMU to DELAYED/3-day at least. "
220
"All other NMU rules apply as usually; they should send the patch of the NMU "
221
"to the BTS (to one of the open bugs fixed by the NMU, or to a new bug, "
222
"tagged fixed). They should also respect any particular wishes of the "
226
# type: Content of: <chapter><section><section><para>
227
#: beyond-pkging.dbk:147
229
"If you don't feel confident about doing an NMU, just send a patch to the "
230
"BTS. It's far better than a broken NMU."
233
# type: Content of: <chapter><section><title>
234
#: beyond-pkging.dbk:155
235
msgid "Contacting other maintainers"
238
# type: Content of: <chapter><section><para>
239
#: beyond-pkging.dbk:157
241
"During your lifetime within Debian, you will have to contact other "
242
"maintainers for various reasons. You may want to discuss a new way of "
243
"cooperating between a set of related packages, or you may simply remind "
244
"someone that a new upstream version is available and that you need it."
247
# type: Content of: <chapter><section><para>
248
#: beyond-pkging.dbk:163
250
"Looking up the email address of the maintainer for the package can be "
251
"distracting. Fortunately, there is a simple email alias, <literal><"
252
"package>@&packages-host;</literal>, which provides a way to email the "
253
"maintainer, whatever their individual email address (or addresses) may be. "
254
"Replace <literal><package></literal> with the name of a source or a "
258
# type: Content of: <chapter><section><para>
259
#: beyond-pkging.dbk:171
261
"You may also be interested in contacting the persons who are subscribed to a "
262
"given source package via <xref linkend=\"pkg-tracking-system\"/> . You can "
263
"do so by using the <literal><package>@&pts-host;</literal> email "
267
# type: Content of: <chapter><section><title>
268
#: beyond-pkging.dbk:180
269
msgid "Dealing with inactive and/or unreachable maintainers"
272
# type: Content of: <chapter><section><para>
273
#: beyond-pkging.dbk:182
275
"If you notice that a package is lacking maintenance, you should make sure "
276
"that the maintainer is active and will continue to work on their packages. "
277
"It is possible that they are not active any more, but haven't registered out "
278
"of the system, so to speak. On the other hand, it is also possible that "
279
"they just need a reminder."
282
# type: Content of: <chapter><section><para>
283
#: beyond-pkging.dbk:189
285
"There is a simple system (the MIA database) in which information about "
286
"maintainers who are deemed Missing In Action is recorded. When a member of "
287
"the QA group contacts an inactive maintainer or finds more information about "
288
"one, this is recorded in the MIA database. This system is available in /org/"
289
"qa.debian.org/mia on the host qa.debian.org, and can be queried with a tool "
290
"known as <command>mia-query</command>. Use <command>mia-query --help</"
291
"command> to see how to query the database. If you find that no information "
292
"has been recorded about an inactive maintainer yet, or that you can add more "
293
"information, you should generally proceed as follows."
296
# type: Content of: <chapter><section><para>
297
#: beyond-pkging.dbk:200
299
"The first step is to politely contact the maintainer, and wait a reasonable "
300
"time for a response. It is quite hard to define reasonable time, but it is "
301
"important to take into account that real life is sometimes very hectic. One "
302
"way to handle this would be to send a reminder after two weeks."
305
# type: Content of: <chapter><section><para>
306
#: beyond-pkging.dbk:206
308
"If the maintainer doesn't reply within four weeks (a month), one can assume "
309
"that a response will probably not happen. If that happens, you should "
310
"investigate further, and try to gather as much useful information about the "
311
"maintainer in question as possible. This includes:"
314
# type: Content of: <chapter><section><itemizedlist><listitem><para>
315
#: beyond-pkging.dbk:214
317
"The echelon information available through the <ulink url=\"&url-debian-db;"
318
"\">developers' LDAP database</ulink>, which indicates when the developer "
319
"last posted to a Debian mailing list. (This includes uploads via debian-*-"
320
"changes lists.) Also, remember to check whether the maintainer is marked as "
321
"on vacation in the database."
324
# type: Content of: <chapter><section><itemizedlist><listitem><para>
325
#: beyond-pkging.dbk:223
327
"The number of packages this maintainer is responsible for, and the condition "
328
"of those packages. In particular, are there any RC bugs that have been open "
329
"for ages? Furthermore, how many bugs are there in general? Another important "
330
"piece of information is whether the packages have been NMUed, and if so, by "
334
# type: Content of: <chapter><section><itemizedlist><listitem><para>
335
#: beyond-pkging.dbk:232
337
"Is there any activity of the maintainer outside of Debian? For example, they "
338
"might have posted something recently to non-Debian mailing lists or news "
342
# type: Content of: <chapter><section><para>
343
#: beyond-pkging.dbk:239
345
"A bit of a problem are packages which were sponsored — the maintainer is not "
346
"an official Debian developer. The echelon information is not available for "
347
"sponsored people, for example, so you need to find and contact the Debian "
348
"developer who has actually uploaded the package. Given that they signed the "
349
"package, they're responsible for the upload anyhow, and are likely to know "
350
"what happened to the person they sponsored."
353
# type: Content of: <chapter><section><para>
354
#: beyond-pkging.dbk:247
356
"It is also allowed to post a query to &email-debian-devel;, asking if anyone "
357
"is aware of the whereabouts of the missing maintainer. Please Cc: the "
358
"person in question."
361
# type: Content of: <chapter><section><para>
362
#: beyond-pkging.dbk:252
364
"Once you have gathered all of this, you can contact &email-mia;. People on "
365
"this alias will use the information you provide in order to decide how to "
366
"proceed. For example, they might orphan one or all of the packages of the "
367
"maintainer. If a package has been NMUed, they might prefer to contact the "
368
"NMUer before orphaning the package — perhaps the person who has done the NMU "
369
"is interested in the package."
372
# type: Content of: <chapter><section><para>
373
#: beyond-pkging.dbk:260
375
"One last word: please remember to be polite. We are all volunteers and "
376
"cannot dedicate all of our time to Debian. Also, you are not aware of the "
377
"circumstances of the person who is involved. Perhaps they might be "
378
"seriously ill or might even have died — you do not know who may be on the "
379
"receiving side. Imagine how a relative will feel if they read the e-mail of "
380
"the deceased and find a very impolite, angry and accusing message!"
383
# type: Content of: <chapter><section><para>
384
#: beyond-pkging.dbk:268
386
"On the other hand, although we are volunteers, we do have a responsibility. "
387
"So you can stress the importance of the greater good — if a maintainer does "
388
"not have the time or interest anymore, they should let go and give the "
389
"package to someone with more time."
392
# type: Content of: <chapter><section><para>
393
#: beyond-pkging.dbk:274
395
"If you are interested in working in the MIA team, please have a look at the "
396
"README file in /org/qa.debian.org/mia on qa.debian.org where the technical "
397
"details and the MIA procedures are documented and contact &email-mia;."
400
# type: Content of: <chapter><section><title>
401
#: beyond-pkging.dbk:282
402
msgid "Interacting with prospective Debian developers"
405
# type: Content of: <chapter><section><para>
406
#: beyond-pkging.dbk:284
408
"Debian's success depends on its ability to attract and retain new and "
409
"talented volunteers. If you are an experienced developer, we recommend that "
410
"you get involved with the process of bringing in new developers. This "
411
"section describes how to help new prospective developers."
414
# type: Content of: <chapter><section><section><title>
415
#: beyond-pkging.dbk:290
416
msgid "Sponsoring packages"
419
# type: Content of: <chapter><section><section><para>
420
#: beyond-pkging.dbk:292
422
"Sponsoring a package means uploading a package for a maintainer who is not "
423
"able to do it on their own, a new maintainer applicant. Sponsoring a "
424
"package also means accepting responsibility for it."
427
# type: Content of: <chapter><section><section><para>
428
#: beyond-pkging.dbk:303
430
"New maintainers usually have certain difficulties creating Debian packages — "
431
"this is quite understandable. That is why the sponsor is there, to check "
432
"the package and verify that it is good enough for inclusion in Debian. "
433
"(Note that if the sponsored package is new, the ftpmasters will also have to "
434
"inspect it before letting it in.)"
437
# type: Content of: <chapter><section><section><para>
438
#: beyond-pkging.dbk:310
440
"Sponsoring merely by signing the upload or just recompiling is <emphasis "
441
"role=\"strong\">definitely not recommended</emphasis>. You need to build "
442
"the source package just like you would build a package of your own. "
443
"Remember that it doesn't matter that you left the prospective developer's "
444
"name both in the changelog and the control file, the upload can still be "
448
# type: Content of: <chapter><section><section><para>
449
#: beyond-pkging.dbk:317
451
"If you are an application manager for a prospective developer, you can also "
452
"be their sponsor. That way you can also verify how the applicant is "
453
"handling the 'Tasks and Skills' part of their application."
456
# type: Content of: <chapter><section><section><title>
457
#: beyond-pkging.dbk:324
458
msgid "Managing sponsored packages"
461
# type: Content of: <chapter><section><section><para>
462
#: beyond-pkging.dbk:326
464
"By uploading a sponsored package to Debian, you are certifying that the "
465
"package meets minimum Debian standards. That implies that you must build "
466
"and test the package on your own system before uploading."
469
# type: Content of: <chapter><section><section><para>
470
#: beyond-pkging.dbk:331
472
"You cannot simply upload a binary <filename>.deb</filename> from the "
473
"sponsoree. In theory, you should only ask for the diff file and the "
474
"location of the original source tarball, and then you should download the "
475
"source and apply the diff yourself. In practice, you may want to use the "
476
"source package built by your sponsoree. In that case, you have to check "
477
"that they haven't altered the upstream files in the <filename>.orig.tar.gz</"
478
"filename> file that they're providing."
481
# type: Content of: <chapter><section><section><para>
482
#: beyond-pkging.dbk:340
484
"Do not be afraid to write the sponsoree back and point out changes that need "
485
"to be made. It often takes several rounds of back-and-forth email before "
486
"the package is in acceptable shape. Being a sponsor means being a mentor."
489
# type: Content of: <chapter><section><section><para>
490
#: beyond-pkging.dbk:345
491
msgid "Once the package meets Debian standards, build and sign it with"
494
# type: Content of: <chapter><section><section><screen>
495
#: beyond-pkging.dbk:348
497
msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>"
500
# type: Content of: <chapter><section><section><para>
501
#: beyond-pkging.dbk:351
503
"before uploading it to the incoming directory. Of course, you can also use "
504
"any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique "
505
"in your secret keyring."
508
# type: Content of: <chapter><section><section><para>
509
#: beyond-pkging.dbk:356
511
"The Maintainer field of the <filename>control</filename> file and the "
512
"<filename>changelog</filename> should list the person who did the packaging, "
513
"i.e., the sponsoree. The sponsoree will therefore get all the BTS mail "
517
# type: Content of: <chapter><section><section><para>
518
#: beyond-pkging.dbk:362
520
"If you prefer to leave a more evident trace of your sponsorship job, you can "
521
"add a line stating it in the most recent changelog entry."
524
# type: Content of: <chapter><section><section><para>
525
#: beyond-pkging.dbk:366
527
"You are encouraged to keep tabs on the package you sponsor using <xref "
528
"linkend=\"pkg-tracking-system\"/> ."
531
# type: Content of: <chapter><section><section><title>
532
#: beyond-pkging.dbk:372
533
msgid "Advocating new developers"
536
# type: Content of: <chapter><section><section><para>
537
#: beyond-pkging.dbk:374
539
"See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a "
540
"prospective developer</ulink> at the Debian web site."
543
# type: Content of: <chapter><section><section><title>
544
#: beyond-pkging.dbk:381
545
msgid "Handling new maintainer applications"
548
# type: Content of: <chapter><section><section><para>
549
#: beyond-pkging.dbk:383
551
"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for "
552
"Application Managers</ulink> at the Debian web site."
added
removed
po4a/fr/beyond-pkging.po
