X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=po4a%2Fpo%2Fbeyond-pkging.pot;h=7cdac89946ff696c4e648643bc2f9e7ee4c594f1;hb=6484c3554309c0613fff3885ea68b7e657a1d0e5;hp=2f40eeff36289ecce3f552ec9ef8aafeb9e186ae;hpb=bafa67a2c7b794d78396cf18f8d8e44d3160e3ac;p=developers-reference.git diff --git a/po4a/po/beyond-pkging.pot b/po4a/po/beyond-pkging.pot index 2f40eef..7cdac89 100644 --- a/po4a/po/beyond-pkging.pot +++ b/po4a/po/beyond-pkging.pot @@ -7,13 +7,14 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2010-05-06 17:34-0400\n" +"POT-Creation-Date: 2011-10-12 09:49+0300\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" +"Language: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" #. type: Content of: #: beyond-pkging.dbk:7 @@ -80,7 +81,7 @@ msgstr "" msgid "" "Make sure the bug is not already filed against a package. Each package has " "a bug list easily reachable at " -"<literal>http://&bugs-host;/<replaceable>packagename</replaceable></literal> " +"<literal>http://&bugs-host;/<replaceable>packagename</replaceable></literal>. " "Utilities like <citerefentry> <refentrytitle>querybts</refentrytitle> " "<manvolnum>1</manvolnum> </citerefentry> can also provide you with this " "information (and <command>reportbug</command> will usually invoke " @@ -113,7 +114,7 @@ msgid "" "reports that you submitted. Take this opportunity to close those that you " "can't reproduce anymore. To find out all the bugs you submitted, you just " "have to visit " -"<literal>http://&bugs-host;/from:<replaceable><your-email-addr></replaceable></literal>." +"<literal>http://&bugs-host;/from:<replaceable>your-email-addr</replaceable></literal>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -147,9 +148,9 @@ msgstr "" #: beyond-pkging.dbk:87 msgid "" "Please use the programs <command>dd-list</command> and if appropriate " -"<command>whodepends</command> (from the package devscripts) to generate a " -"list of all affected packages, and include the output in your mail to " -"&email-debian-devel;." +"<command>whodepends</command> (from the package <systemitem " +"role=\"package\">devscripts</systemitem>) to generate a list of all affected " +"packages, and include the output in your mail to &email-debian-devel;." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -187,31 +188,30 @@ msgstr "" #, no-wrap msgid "" "To: submit@bugs.debian.org\n" -"Subject: <replaceable><title-of-bug></replaceable>\n" +"Subject: <replaceable>title-of-bug</replaceable>\n" "\n" -"Package: <replaceable><pkgname></replaceable>\n" +"Package: <replaceable>pkgname</replaceable>\n" "<replaceable>[ ... ]</replaceable>\n" -"User: <replaceable><email-addr></replaceable>\n" -"Usertags: <replaceable><tag-name> [ <tag-name> " -"... ]</replaceable>\n" +"User: <replaceable>email-addr</replaceable>\n" +"Usertags: <replaceable>tag-name [ tag-name ... ]</replaceable>\n" "\n" -"<replaceable><description-of-bug ...></replaceable>\n" +"<replaceable>description-of-bug ...</replaceable>\n" msgstr "" #. type: Content of: <chapter><section><section><section><para> #: beyond-pkging.dbk:122 msgid "" "Note that tags are seperated by spaces and cannot contain underscores. If " -"you are filing bugs for for a particular group or team it is recommended " -"that you set the <literal>User</literal> to an appropriate mailing list " -"after describing your intention there." +"you are filing bugs for a particular group or team it is recommended that " +"you set the <literal>User</literal> to an appropriate mailing list after " +"describing your intention there." msgstr "" #. type: Content of: <chapter><section><section><section><para> #: beyond-pkging.dbk:128 msgid "" "To view bugs tagged with a specific usertag, visit " -"<literal>http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable><email-addr></replaceable>&tag=<replaceable><tag-name></replaceable></literal>." +"<literal>http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable>email-addr</replaceable>&tag=<replaceable>tag-name</replaceable></literal>." msgstr "" #. type: Content of: <chapter><section><title> @@ -230,13 +230,13 @@ msgid "" "Even though there is a dedicated group of people for Quality Assurance, QA " "duties are not reserved solely for them. You can participate in this effort " "by keeping your packages as bug-free as possible, and as lintian-clean (see " -"<xref linkend=\"lintian\"/> ) as possible. If you do not find that " -"possible, then you should consider orphaning some of your packages (see " -"<xref linkend=\"orphaning\"/> ). Alternatively, you may ask the help of " -"other people in order to catch up with the backlog of bugs that you have " -"(you can ask for help on &email-debian-qa; or &email-debian-devel;). At the " -"same time, you can look for co-maintainers (see <xref " -"linkend=\"collaborative-maint\"/> )." +"<xref linkend=\"lintian\"/>) as possible. If you do not find that possible, " +"then you should consider orphaning some of your packages (see <xref " +"linkend=\"orphaning\"/>). Alternatively, you may ask the help of other " +"people in order to catch up with the backlog of bugs that you have (you can " +"ask for help on &email-debian-qa; or &email-debian-devel;). At the same " +"time, you can look for co-maintainers (see <xref " +"linkend=\"collaborative-maint\"/>)." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -306,18 +306,19 @@ msgstr "" msgid "" "Looking up the email address of the maintainer for the package can be " "distracting. Fortunately, there is a simple email alias, " -"<literal><package>@&packages-host;</literal>, which provides a way to " -"email the maintainer, whatever their individual email address (or addresses) " -"may be. Replace <literal><package></literal> with the name of a " -"source or a binary package." +"<literal><replaceable>package</replaceable>@&packages-host;</literal>, which " +"provides a way to email the maintainer, whatever their individual email " +"address (or addresses) may be. Replace <replaceable>package</replaceable> " +"with the name of a source or a binary package." msgstr "" #. type: Content of: <chapter><section><para> #: beyond-pkging.dbk:206 msgid "" "You may also be interested in contacting the persons who are subscribed to a " -"given source package via <xref linkend=\"pkg-tracking-system\"/> . You can " -"do so by using the <literal><package>@&pts-host;</literal> email " +"given source package via <xref linkend=\"pkg-tracking-system\"/>. You can " +"do so by using the " +"<literal><replaceable>package</replaceable>@&pts-host;</literal> email " "address." msgstr "" @@ -344,7 +345,7 @@ msgid "" "the QA group contacts an inactive maintainer or finds more information about " "one, this is recorded in the MIA database. This system is available in " "<filename>/org/qa.debian.org/mia</filename> on the host " -"<literal>qa.debian.org </literal>, and can be queried with the " +"<literal>qa.debian.org</literal>, and can be queried with the " "<command>mia-query</command> tool. Use <command>mia-query --help</command> " "to see how to query the database. If you find that no information has been " "recorded about an inactive maintainer yet, or that you can add more " @@ -452,9 +453,10 @@ msgstr "" #: beyond-pkging.dbk:310 msgid "" "If you are interested in working in the MIA team, please have a look at the " -"README file in <filename>/org/qa.debian.org/mia</filename> on <literal> " -"qa.debian.org</literal> where the technical details and the MIA procedures " -"are documented and contact &email-mia;." +"<filename>README</filename> file in " +"<filename>/org/qa.debian.org/mia</filename> on " +"<literal>qa.debian.org</literal> where the technical details and the MIA " +"procedures are documented and contact &email-mia;." msgstr "" #. type: Content of: <chapter><section><title> @@ -480,133 +482,365 @@ msgstr "" #: beyond-pkging.dbk:328 msgid "" "Sponsoring a package means uploading a package for a maintainer who is not " -"able to do it on their own, a new maintainer applicant. Sponsoring a " -"package also means accepting responsibility for it." +"able to do it on their own. It's not a trivial matter, the sponsor must " +"verify the packaging and ensure that it is of the high level of quality that " +"Debian strives to have." msgstr "" #. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:339 +#: beyond-pkging.dbk:334 +msgid "Debian Developers can sponsor packages. Debian Maintainers can't." +msgstr "" + +#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para> +#: beyond-pkging.dbk:340 msgid "" -"New maintainers usually have certain difficulties creating Debian packages — " -"this is quite understandable. That is why the sponsor is there, to check " -"the package and verify that it is good enough for inclusion in Debian. " -"(Note that if the sponsored package is new, the ftpmasters will also have to " -"inspect it before letting it in.)" +"The maintainer prepares a source package (<filename>.dsc</filename>) and " +"puts it online somewhere (like on <ulink " +"url=\"http://mentors.debian.net/cgi-bin/welcome\">mentors.debian.net</ulink>) " +"or even better, provides a link to a public VCS repository (see <xref " +"linkend=\"servers-vcs\"/>) where the package is maintained." msgstr "" -#. type: Content of: <chapter><section><section><para> +#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para> #: beyond-pkging.dbk:346 +msgid "The sponsor downloads (or checkouts) the source package." +msgstr "" + +#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para> +#: beyond-pkging.dbk:349 msgid "" -"Sponsoring merely by signing the upload or just recompiling is <emphasis " -"role=\"strong\">definitely not recommended</emphasis>. You need to build " -"the source package just like you would build a package of your own. " -"Remember that it doesn't matter that you left the prospective developer's " -"name both in the changelog and the control file, the upload can still be " -"traced to you." +"The sponsor reviews the source package. If she finds issues, she informs the " +"maintainer and asks her to provide a fixed version (the process starts over " +"at step 1)." +msgstr "" + +#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para> +#: beyond-pkging.dbk:354 +msgid "" +"The sponsor could not find any remaining problem. She builds the package, " +"signs it, and uploads it to Debian." msgstr "" #. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:353 +#: beyond-pkging.dbk:337 msgid "" -"If you are an application manager for a prospective developer, you can also " -"be their sponsor. That way you can also verify how the applicant is " -"handling the 'Tasks and Skills' part of their application." +"The process of sponsoring a package is: <placeholder type=\"orderedlist\" " +"id=\"0\"/>" msgstr "" -#. type: Content of: <chapter><section><section><title> +#. type: Content of: <chapter><section><section><para> #: beyond-pkging.dbk:360 -msgid "Managing sponsored packages" +msgid "" +"Before delving in the details of how to sponsor a package, you should ask " +"yourself whether adding the proposed package is beneficial to Debian." msgstr "" #. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:362 +#: beyond-pkging.dbk:364 msgid "" -"By uploading a sponsored package to Debian, you are certifying that the " -"package meets minimum Debian standards. That implies that you must build " -"and test the package on your own system before uploading." +"There's no simple rule to answer this question, it can depend on many " +"factors: is the upstream codebase mature and not full of security holes? Are " +"there pre-existing packages that can do the same task and how do they " +"compare to this new package? Has the new package been requested by users and " +"how large is the user base? How active are the upstream developers?" msgstr "" #. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:367 +#: beyond-pkging.dbk:371 msgid "" -"You cannot simply upload a binary <filename>.deb</filename> from the " -"sponsoree. In theory, you should only ask for the diff file and the " -"location of the original source tarball, and then you should download the " -"source and apply the diff yourself. In practice, you may want to use the " -"source package built by your sponsoree. In that case, you have to check " -"that they haven't altered the upstream files in the " -"<filename>.orig.tar.gz</filename> file that they're providing." +"You should also ensure that the prospective maintainer is going to be a good " +"maintainer. Does she already have some experience with other packages? If " +"yes, is she doing a good job with them (check out some bugs)? Is she " +"familiar with the package and its programming language? Does she have the " +"skills needed for this package? If not, is she able to learn them?" msgstr "" #. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:376 +#: beyond-pkging.dbk:379 msgid "" -"Do not be afraid to write the sponsoree back and point out changes that need " -"to be made. It often takes several rounds of back-and-forth email before " -"the package is in acceptable shape. Being a sponsor means being a mentor." +"It's also a good idea to know where she stands towards Debian: does she " +"agree with Debian's philosophy and does she intend to join Debian? Given how " +"easy it is to become a Debian Maintainer, you might want to only sponsor " +"people who plan to join. That way you know from the start that you won't " +"have to act as a sponsor indefinitely." msgstr "" -#. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:381 -msgid "Once the package meets Debian standards, build and sign it with" +#. type: Content of: <chapter><section><section><section><title> +#: beyond-pkging.dbk:386 +msgid "Sponsoring a new package" +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:388 +msgid "" +"New maintainers usually have certain difficulties creating Debian packages — " +"this is quite understandable. They will do mistakes. That's why sponsoring a " +"brand new package into Debian requires a thorough review of the Debian " +"packaging. Sometimes several iterations will be needed until the package is " +"good enough to be uploaded to Debian. Thus being a sponsor implies being a " +"mentor." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:396 +msgid "" +"Don't ever sponsor a new package without reviewing it. The review of new " +"packages done by ftpmasters mainly ensures that the software is really " +"free. Of course, it happens that they stumble on packaging problems but they " +"really should not. It's your task to ensure that the uploaded package " +"complies with the Debian Free Software Guidelines and is of good quality." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para><footnote><para> +#: beyond-pkging.dbk:409 +msgid "" +"You can find more checks in the wiki where several developers share their " +"own <ulink url=\"http://wiki.debian.org/SponsorChecklist\">sponsorship " +"checklists</ulink>." msgstr "" -#. type: Content of: <chapter><section><section><screen> -#: beyond-pkging.dbk:384 +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:404 +msgid "" +"Building the package and testing the software is part of the review, but " +"it's also not enough. The rest of this section contains a non-exhaustive " +"list of points to check in your review. <placeholder type=\"footnote\" " +"id=\"0\"/>" +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:416 +msgid "" +"Verify that the upstream tarball provided is the same that has been " +"distributed by the upstream author (when the sources are repackaged for " +"Debian, generate the modified tarball yourself)." +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:421 +msgid "" +"Run <command>lintian</command> (see <xref linkend=\"lintian\"/>). It will " +"catch many common problems. Be sure to verify that any " +"<command>lintian</command> overrides setup by the maintainer is fully " +"justified." +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:426 +msgid "" +"Run <command>licensecheck</command> (part of <xref linkend=\"devscripts\"/>) " +"and verify that <filename>debian/copyright</filename> seems correct and " +"complete. Look for license problems (like files with “All rights reserved” " +"headers, or with a non-DFSG compliant license). <command>grep -ri</command> " +"is your friend for this task." +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:433 +msgid "" +"Build the package with <command>pbuilder</command> (or any similar tool, see " +"<xref linkend=\"pbuilder\"/>) to ensure that the build-dependencies are " +"complete." +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:438 +msgid "" +"Proofread <filename>debian/control</filename>: does it follow the best " +"practices (see <xref linkend=\"bpp-debian-control\"/>)? Are the dependencies " +"complete?" +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:443 +msgid "" +"Proofread <filename>debian/rules</filename>: does it follow the best " +"practices (see <xref linkend=\"bpp-debian-rules\"/>)? Do you see some " +"possible improvements?" +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:448 +msgid "" +"Proofread the maintainer scripts (<filename>preinst</filename>, " +"<filename>postinst</filename>, <filename>prerm</filename>, " +"<filename>postrm</filename>, <filename>config</filename>): will the " +"<filename>preinst</filename>/<filename>postrm</filename> work when the " +"dependencies are not installed? Are all the scripts idempotent (i.e. can you " +"run them multiple times without consequences)?" +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:456 +msgid "" +"Review any change to upstream files (either in " +"<filename>.diff.gz</filename>, or in <filename>debian/patches/</filename> or " +"directly embedded in the <filename>debian</filename> tarball for binary " +"files). Are they justified? Are they properly documented (with <ulink " +"url=\"&url-dep3;\">DEP-3</ulink> for patches)?" +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:462 +msgid "" +"For every file, ask yourself why the file is there and whether it's the " +"right way to achieve the desired result. Is the maintainer following the " +"best packaging practices (see <xref linkend=\"best-pkging-practices\"/>)?" +msgstr "" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: beyond-pkging.dbk:468 +msgid "" +"Build the packages, install them and try the software. Ensure you can remove " +"and purge the packages. Maybe test them with <command>piuparts</command>." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:474 +msgid "" +"If the audit did not reveal any problem, you can build the package and " +"upload it to Debian. Remember that even if you're not the maintainer, the " +"sponsor is still responsible of what he uploaded to Debian. That's why " +"you're encouraged to keep up with the package through the <xref " +"linkend=\"pkg-tracking-system\"/>." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:481 +msgid "" +"Note that you should not need to modify the source package to put your name " +"in the <filename>changelog</filename> or in the <filename>control</filename> " +"file. The <literal>Maintainer</literal> field of the " +"<filename>control</filename> file and the <filename>changelog</filename> " +"should list the person who did the packaging, i.e. the sponsoree. That way " +"she will get all the BTS mail." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:487 +msgid "" +"Instead you should instruct <command>dpkg-buildpackage</command> to use your " +"key for the signature. You do that with the <literal>-k</literal> option:" +msgstr "" + +#. type: Content of: <chapter><section><section><section><screen> +#: beyond-pkging.dbk:490 #, no-wrap msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n" msgstr "" -#. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:387 +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:492 msgid "" -"before uploading it to the incoming directory. Of course, you can also use " -"any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique " -"in your secret keyring." +"If you use <command>debuild</command> and <command>debsign</command>, you " +"can even configure it permanently in <filename>~/.devscripts</filename>:" msgstr "" -#. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:392 +#. type: Content of: <chapter><section><section><section><programlisting> +#: beyond-pkging.dbk:495 +#, no-wrap +msgid "DEBSIGN_KEYID=<replaceable>KEY-ID</replaceable>\n" +msgstr "" + +#. type: Content of: <chapter><section><section><section><title> +#: beyond-pkging.dbk:500 +msgid "Sponsoring an update of an existing package" +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:502 msgid "" -"The Maintainer field of the <filename>control</filename> file and the " -"<filename>changelog</filename> should list the person who did the packaging, " -"i.e., the sponsoree. The sponsoree will therefore get all the BTS mail " -"about the package." +"You will usually assume that the package has already gone through a full " +"review. So instead of doing it again, you will carefully analyze the " +"difference between the current version and the new version prepared by the " +"maintainer. If you have not done the initial review yourself, you might " +"still want to have a more deeper look just in case the initial reviewer was " +"sloppy." msgstr "" -#. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:398 +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:510 msgid "" -"If you prefer to leave a more evident trace of your sponsorship job, you can " -"add a line stating it in the most recent changelog entry." +"To be able to analyze the difference you need both versions. Download the " +"current version of the source package (with <command>apt-get " +"source</command>) and rebuild it (or download the current binary packages " +"with <command>aptitude download</command>). Download the source package to " +"sponsor (usually with <command>dget</command>)." msgstr "" -#. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:402 +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:517 +msgid "" +"Read the new changelog entry, it should tell you what to expect during the " +"review. The main tool you will use is <command>debdiff</command> (provide by " +"the <systemitem role=\"package\">devscripts</systemitem> package), you can " +"run it with two source packages (<filename>.dsc</filename> files), or two " +"binary packages, or two <filename>.changes</filename> files (it will then " +"compare all the binary packages listed in the " +"<filename>.changes</filename>)." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:524 +msgid "" +"If you compare the source packages (excluding upstream files in the case of " +"a new upstream version, for example by filtering the output of " +"<command>debdiff</command> with <command>filterdiff -i " +"'*/debian/*'</command>), you must understand all the changes you see and " +"they should be properly documented in the Debian changelog." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:531 +msgid "" +"If everything is fine, build the package and compare the binary packages to " +"verify that the changes on the source package have no unexpected " +"consequences (like some files dropped by mistake, missing dependencies, " +"etc.)." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:537 +msgid "" +"You might want to check out the Package Tracking System (see <xref " +"linkend=\"pkg-tracking-system\"/>) to verify if the maintainer has not " +"missed something important. Maybe there are translations updates sitting in " +"the BTS that could have been integrated. Maybe the package has been NMUed " +"and the maintainer forgot to integrate the changes from the NMU in his " +"package. Maybe there's a release critical bug that he has left unhandled and " +"that's blocking migration to <literal>testing</literal>. Whatever. If you " +"find something that she could have done (better), it's time to tell her so " +"that she can improve for next time, and so that she has a better " +"understanding of her responsibilities." +msgstr "" + +#. type: Content of: <chapter><section><section><section><para> +#: beyond-pkging.dbk:549 msgid "" -"You are encouraged to keep tabs on the package you sponsor using <xref " -"linkend=\"pkg-tracking-system\"/> ." +"If you have found no major problem, upload the new version. Otherwise ask " +"the maintainer to provide you a fixed version." msgstr "" #. type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:408 +#: beyond-pkging.dbk:556 msgid "Advocating new developers" msgstr "" #. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:410 +#: beyond-pkging.dbk:558 msgid "" "See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a " "prospective developer</ulink> at the Debian web site." msgstr "" #. type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:417 +#: beyond-pkging.dbk:565 msgid "Handling new maintainer applications" msgstr "" #. type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:419 +#: beyond-pkging.dbk:567 msgid "" "Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for " "Application Managers</ulink> at the Debian web site."