From c8a7d3df9555400f12e6a942ee1caaae96b9b28c Mon Sep 17 00:00:00 2001 From: Weblate Date: Jan 04 2024 15:27:40 +0000 Subject: Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Co-authored-by: Weblate Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpageshow_to_get_sponsored_into_the_packager_group/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpageshow_to_sponsor_a_new_contributor/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagesinstalling_packager_tools/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagesnew_package_process_for_existing_contributors/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagespackage_maintenance_guide/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagespackage_orphaning_process/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagespackage_renaming_process/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagespackage_retirement_process/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagespackage_review_process/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagespackage_update_guide/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagesreporting_issues/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagesstaying_close_to_upstream_projects/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagesusing_the_koji_build_system/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpagesutilities/ Translate-URL: https://translate.fedoraproject.org/projects/fedora-docs-l10n-package-maintainers/masterpartialsmailing_lists/ Translation: fedora-docs-l10n/package-maintainers/master/pages/How_to_Get_Sponsored_into_the_Packager_Group Translation: fedora-docs-l10n/package-maintainers/master/pages/How_to_Sponsor_a_New_Contributor Translation: fedora-docs-l10n/package-maintainers/master/pages/Installing_Packager_Tools Translation: fedora-docs-l10n/package-maintainers/master/pages/New_Package_Process_for_Existing_Contributors Translation: fedora-docs-l10n/package-maintainers/master/pages/Package_Maintenance_Guide Translation: fedora-docs-l10n/package-maintainers/master/pages/Package_Orphaning_Process Translation: fedora-docs-l10n/package-maintainers/master/pages/Package_Renaming_Process Translation: fedora-docs-l10n/package-maintainers/master/pages/Package_Retirement_Process Translation: fedora-docs-l10n/package-maintainers/master/pages/Package_Review_Process Translation: fedora-docs-l10n/package-maintainers/master/pages/Package_Update_Guide Translation: fedora-docs-l10n/package-maintainers/master/pages/Reporting_Issues Translation: fedora-docs-l10n/package-maintainers/master/pages/Staying_Close_to_Upstream_Projects Translation: fedora-docs-l10n/package-maintainers/master/pages/Using_the_Koji_Build_System Translation: fedora-docs-l10n/package-maintainers/master/pages/Utilities Translation: fedora-docs-l10n/package-maintainers/master/partials/mailing_lists --- diff --git a/po/fr/master/antora.yml.po b/po/fr/master/antora.yml.po index 3aff88f..0b1fc06 100644 --- a/po/fr/master/antora.yml.po +++ b/po/fr/master/antora.yml.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2021-11-21 22:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,13 +16,14 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. type: Array Element -#: >nav +#. type: Array Element: nav +#: antora.yml:0 #, no-wrap msgid "modules/ROOT/nav.adoc" msgstr "" -#. type: Hash Value - Key: title +#. type: Hash Value: title +#: antora.yml:0 #, no-wrap msgid "Package Maintainers" msgstr "" diff --git a/po/fr/master/pages/How_to_Get_Sponsored_into_the_Packager_Group.po b/po/fr/master/pages/How_to_Get_Sponsored_into_the_Packager_Group.po index a5f8aeb..25cb555 100644 --- a/po/fr/master/pages/How_to_Get_Sponsored_into_the_Packager_Group.po +++ b/po/fr/master/pages/How_to_Get_Sponsored_into_the_Packager_Group.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-04-21 21:59+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,282 +16,94 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group #. type: Title = -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:3 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:1 #, no-wrap msgid "How to Get Sponsored into the Packager Group" msgstr "" -#. type: Title == -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:7 -#, no-wrap -msgid "Sponsorship model" -msgstr "" - #. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:27 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:6 msgid "" -"Getting sponsored allows anyone interested to become a Fedora maintainer and " -"get direct commit and upload access to their proposed software packages. We " -"require people to get sponsored into the `packager` group before getting " -"this access to Fedora to ensure that they have someone that they can go to " -"with questions. Sponsorship is *not* automatic and requires that you find a " -"willing sponsor. Depending on the sponsor and how much time they have to " -"spend with you, they may require that you demonstrate that you have the " -"knowledge to maintain Fedora packages properly (including an understanding " -"of the Fedora packaging guidelines) or they may be willing to take you on " -"if you just show that you are eager and willing to learn those things from " -"them. A sponsor will assist you with some aspects of packaging and the " -"submission process but will expect you to read about the process and " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/[guidelines for " -"packages] for a large amount of your understanding of how things work." +"xref:fesco::Packager_sponsor_policy.adoc[Packager sponsor policy] governs " +"sponsorship for the _packager_ group. This page contains some additional " +"tips that are not part of the policy." msgstr "" #. type: Title == -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:29 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:8 #, no-wrap -msgid "Convincing someone to sponsor you" -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:35 -msgid "" -"There are several ways to get sponsored into the `packager` group depending " -"on your interest. In many cases doing a mixture of different things will " -"increase your chances of being sponsored." +msgid "Discovering packages that need maintenance" msgstr "" #. type: Title === -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:37 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:11 #, no-wrap -msgid "Submitting quality new packages" -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:57 -msgid "" -"Until you are sponsored into the `packager` group you are not able to own " -"packages or to check in changes to packages which you own. However, you can " -"still create an initial package and submit it for review as talked about at " -"xref:Joining_the_Package_Maintainers#adding_a_new_package[Joining the " -"Package Maintainers]. When you open your review request in bugzilla, you " -"should block the " -"https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR] " -"tracking bug, that way all of the sponsors will be able to see your " -"sponsorship request. Although `FE-NEEDSPONSOR` is set on the package's " -"review request, it is the person that needs to be sponsored into the " -"`packager` group, not the package. The package undergoes a " -"xref:Package_Review_Process.adoc[ review and approval] that is separate from " -"someone sponsoring you. Note that it is possible to have accepted packages " -"which you cannot import because you have not been sponsored. See below." -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:68 -msgid "" -"When submitting a new package, usually a sponsor finds you, but you can take " -"a look at the https://accounts.fedoraproject.org/group/packager/[list of " -"packager sponsors] (only accessible with a " -"https://fedoraproject.org/wiki/Account_System[Fedora Account]) for someone " -"you know. Sending bulk requests to the list is discouraged. If you can't " -"find anyone that you have a connection with, you may want to try hanging out " -"in the " -"https://fedoraproject.org/wiki/How_to_communicate_using_IRC[#fedora-devel " -"IRC channel] to get to know some people. Also you might find a sponsor in a " -"that fits to your submitted package." +msgid "Orphaned packages" msgstr "" #. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:84 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:21 msgid "" -"Sponsors who work with people submitting new packages are looking to see how " -"well you are going to be able to maintain this package which is primarily " -"about whether you can package according to Fedora's " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging " -"Guidelines] but they'll also take into account how you'll be able to respond " -"to bugs against the code itself. If you like, you can include other " -"information about your involvement with the Fedora and upstream communities " -"that you think might help the sponsors in their decision. If you are an " -"upstream author of the package you are submitting or if you are active in " -"the community that surrounds it, please say so. If you can line up one or " -"more existing Fedora contributors who are willing to maintain the package " -"along with you, even if they are not sponsors, please indicate that as well." +"You can find orphaned packages in need of maintenance in notifications sent " +"to the https://lists.fedoraproject.org/archives/list/devel@lists." +"fedoraproject.org/[devel] mailing list. If you notice an orphaned package " +"that you are willing to maintain, post to devel, explaining that you are not " +"in the packager group yet, but that after you have completed the sponsoring " +"process, you are interested in adopting or co-maintaining the package. The " +"kind of replies you may get include:" msgstr "" #. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:94 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:24 msgid "" -"The sponsors that look at new package submissions often ask new packagers to " -"do some package reviews in order to further show that they know what they're " -"doing. If you do some reviews ahead of time, you can show the sponsors that " -"you've both read these pages and understand the guidelines. Go ahead and " -"link to other package review requests where you've left comments and reviews " -"(More on reviews " -"link:#show_your_expertise_by_commenting_on_other_review_requests[below])." +"A warning to reconsider this plan, due to serious problems with the package." msgstr "" #. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:98 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:28 msgid "" -"Basically, the more information that you make available, the quicker you " -"will find a sponsor." +"A note that the package has already been adopted, possibly with an " +"invitation to contribute in its maintenance (which itself may lead to " +"eventual sponsoring through the co-maintenance route.)" msgstr "" #. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:101 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:31 msgid "" -"If you have accepted packagesand still have not managed to find a sponsor, " -"feel free to file a ticket in the " -"https://pagure.io/packager-sponsors/[sponsors ticketing system]." +"An offer to help with the process, perhaps from the previous maintainer or a " +"potential sponsor." msgstr "" #. type: Title === -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:103 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:33 #, no-wrap -msgid "Show Your Expertise by Commenting on other Review Requests" +msgid "Review requests" msgstr "" #. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:118 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:39 msgid "" -"To show you familiarity with Fedora's guidelines, perform unofficial (also " -"called preliminary) reviews in other maintainers' package review request. " -"Please clearly state when doing these reviews, that these are yet " -"unofficial, and do not change the review requests status except for adding " -"you to the CC list. To let sponsors know of your preliminary reviews, link " -"to them in your review request. The quality of your reviews help convincing " -"a sponsor of your knowledge. They will also help out the other reviewers, " -"which will be much appreciated. After you got sponsored, you can finish " -"your unofficial reviews." -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:125 -msgid "" -"Reviews follow the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/[review " -"guidelines]. Note that it's not strictly necessary for you to work through " -"the entire checklist, but please do as much as you can; the more you " -"indicate that you understand, the better your chances of being sponsored." -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:130 -msgid "" -"You can search in the " -"https://fedoraproject.org/PackageReviewStatus/in_progress.html[list of " -"reviews in progress] for review requests to comment on. If you want to work " -"on review requests that nobody else officially reviews, see the " +"If you plan to comment on review requests to demonstrate your level of " +"understanding, you can search the https://fedoraproject.org/" +"PackageReviewStatus/in_progress.html[list of reviews in progress] and the " "http://fedoraproject.org/PackageReviewStatus/reviewable.html[list of " -"unassigned review requests]." -msgstr "" - -#. type: Title === -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:132 -#, no-wrap -msgid "Show Your Expertise by Opening Pull Requests" -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:144 -msgid "" -"The https://pagure.io[Pagure] based " -"https://src.fedoraproject.org[src.fedoraproject.org] system allows you to " -"Fork, modify, and open Pull Requests for packages even if you are not yet " -"part of the package maintainer's group. This is an excellent way to help " -"other package maintainers, and demonstrate your expertise. When requesting " -"sponsorship, you should list these PRs. In many cases, maintainers will " -"also be happy to co-maintain the package with you, and get you sponsored. " -"More on that in the next section." -msgstr "" - -#. type: Title === -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:146 -#, no-wrap -msgid "Become a co-maintainer" -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:153 -msgid "" -"Another way to enter the `packager` group is by co-maintaining a package " -"that is already in Fedora. To get sponsored this way you need to convince " -"the current owner of that package to let you co-maintain the package and tho " -"act as your mentor" -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:164 -msgid "" -"teaching you how to package properly in Fedora and how to use the tools " -"available for building and distributing packages. To get an owner to agree " -"to this, you may need to demonstrate that you have some understanding of " -"packaging already or at least, that you are eager to learn. Submitting " -"patches on bug reports, preparing updated packages if the maintainer is " -"behind on creating an update, or otherwise communicating with the maintainer " -"that you are willing to help are ways to show that you are worth the package " -"owner's investment to train you." -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:180 -msgid "" -"In some cases the package owner is a sponsor in the `packager` group and can " -"sponsor you themselves. If they are not a sponsor, they can get another " -"existing sponsor to do so, either by contacting a sponsor personally and " -"asking them to proxy the sponsorship or by opening a ticket in the " -"https://pagure.io/packager-sponsors/[packager sponsors pagure instance] " -"stating that they are a package owner who would like you to co-maintain " -"their package. They agree to be responsible for mentoring you in how to " -"follow the https://docs.fedoraproject.org/en-US/packaging-guidelines/[Fedora " -"Packaging Guidelines] and how to use the tools Fedora provides for building " -"and pushing packages but need someone to sponsor you since they are not " -"sponsors themselves. A sponsor will add you to the `packager` group once " -"that agreement for mentorship exists." -msgstr "" - -#. type: Title === -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:182 -#, no-wrap -msgid "Other paths" -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:192 -msgid "" -"Sponsors can decide to sponsor you for any other reason as well. For " -"example, you may be upstream for a package and want to maintain just that " -"package in Fedora, or a sponsor may know your work and packaging history and " -"deem you worthy of sponsorship with no further information. The sponsorship " -"decision is left up to the sponsor." -msgstr "" - -#. type: Title == -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:193 -#, no-wrap -msgid "Provenpackagers" -msgstr "" - -#. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:199 -msgid "" -"https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/[Provenpackagers] " -"are members of the *provenpackager* group. In addition to the rights " -"granted to members of *packager*, provenpackagers are able to commit changes " -"to packages they do not own or maintain." +"unassigned review requests] for review requests to comment on." msgstr "" #. type: Title == -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:201 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:41 #, no-wrap -msgid "How to sponsor" +msgid "How to find a sponsor" msgstr "" #. type: Plain text -#: ./pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:204 +#: pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc:46 msgid "" -"If you are looking for information on sponsoring someone, take a look at " -"xref:How_to_Sponsor_a_New_Contributor.adoc[how to sponsor a new " -"contributor]." +"If you have not yet been sponsored, request sponsorship by https://pagure.io/" +"packager-sponsors/issues[raising an issue at packager-sponsors]. You may " +"contact sponsors directly through https://docs.pagure.org/fedora-sponsors/" +"[Sponsors page]. It will help you find the right sponsor for you based on " +"programming language preference, domains of interest, native language, and " +"other criteria." msgstr "" diff --git a/po/fr/master/pages/How_to_Sponsor_a_New_Contributor.po b/po/fr/master/pages/How_to_Sponsor_a_New_Contributor.po index cef486e..32867f2 100644 --- a/po/fr/master/pages/How_to_Sponsor_a_New_Contributor.po +++ b/po/fr/master/pages/How_to_Sponsor_a_New_Contributor.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-01-04 22:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,21 +16,20 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/How_to_sponsor_a_new_contributor #. type: Title = -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:3 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:1 #, no-wrap msgid "How to Sponsor a New Contributor" msgstr "" #. type: Title == -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:7 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:4 #, no-wrap msgid "Becoming a Fedora Package Collection Sponsor" msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:19 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:16 msgid "" "The Fedora Package Collection has been setup so to encourage \"learning by " "doing\" and the development of cooperative relationships between Fedora " @@ -41,17 +40,17 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:21 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:18 msgid "Maintain at least three packages." msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:23 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:20 msgid "Have done five high quality, nontrivial package reviews." msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:29 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:26 msgid "" "Have been members of the packager group for at least one release cycle " "(generally six months) so that they have seen the process of branching for " @@ -59,27 +58,26 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:32 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:29 msgid "" "These are still somewhat vague to allow for flexibility but should provide a " "reasonable idea of how much experience is required." msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:43 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:40 msgid "" "If you're a packager and feel that you are ready and would like to move up " -"to sponsor status, simply file a ticket in the " -"https://pagure.io/packager-sponsors/issues[packager sponsors ticket " -"system]. These tickets are automatically sent to the sponsors list. A " -"report will be added containing information on your reviewed and " -"owned/comaintained packages, but feel free to provide additional information " -"that can't easily be found such as informal reviews done or prospective " -"packagers you would like to sponsor." +"to sponsor status, simply file a ticket in the https://pagure.io/packager-" +"sponsors/issues[packager sponsors ticket system]. These tickets are " +"automatically sent to the sponsors list. A report will be added containing " +"information on your reviewed and owned/comaintained packages, but feel free " +"to provide additional information that can't easily be found such as " +"informal reviews done or prospective packagers you would like to sponsor." msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:55 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:52 msgid "" "Votes will be collected in the ticket for a week. At the end of that time, " "if the differential between positive and negative votes stands at +3 or " @@ -91,13 +89,13 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:57 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:54 #, no-wrap msgid "Sponsoring Someone for Fedora Package Collection" msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:69 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:66 msgid "" "Sponsoring someone for access to Fedora Package Collection is relatively " "simple. If you are looking for someone to sponsor, take a look at the " @@ -109,79 +107,76 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:75 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:72 msgid "" "Bugzilla will send a notification mail for the new review request to the " "fedora-package-review mailing list. Take a look at their package and review " -"it. If it looks reasonable and it seems that the comply with the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging " -"Guidelines], then they are probably a good candidate to be sponsored." +"it. If it looks reasonable and it seems that the comply with the xref:" +"packaging-guidelines::index.adoc[Packaging Guidelines], then they are " +"probably a good candidate to be sponsored." msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:90 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:87 msgid "" "Add any comment for changes to the review request on Bugzilla which look as " "though they'd be needed for compliance as well as the fact that you're " "volunteering to sponsor them. Once they've made those changes, you can " "approve the package and sponsor the user in the Fedora account system. " -"Before you approve the user, please make sure that his/her email in " -"https://accounts.fedoraproject.org/[Fedora Account system] is the same as in " -"https://bugzilla.redhat.com[Red Hat Bugzilla]. After that, go to " -"https://accounts.fedoraproject.org/group/packager/, log in, then add the " -"username in the 'add user' field located to the right of the top of the " -"\"Members\" section, then press enter." +"Before you approve the user, please make sure that his/her email in https://" +"accounts.fedoraproject.org/[Fedora Account system] is the same as in https://" +"bugzilla.redhat.com[Red Hat Bugzilla]. After that, go to https://accounts." +"fedoraproject.org/group/packager/, log in, then add the username in the 'add " +"user' field located to the right of the top of the \"Members\" section, then " +"press enter." msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:105 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:102 msgid "" "A new packager cannot, at this time, make changes to packages he does not " -"own or comaintain until he applies to become a " -"https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/[provenpackager] " -"but you should still keep an eye on them. Generally the easiest way to do " -"this is for them to become comaintainers of at least the initial package " -"they review. You should be sure to review their commits to the Git " -"repository for how they look, and consider watching their Bugzilla activity " -"at least for a while (Preferences→Email " -"Preferences→https://bugzilla.redhat.com/userprefs.cgi?tab=email[User " -"Watching]). Respond with any comments that you might have and guide them, " -"providing assistance as they need it for any tasks. A provenpackager can " -"step in if necessary." +"own or comaintain until he applies to become a xref:fesco::" +"Provenpackager_policy.adoc[provenpackager] but you should still keep an eye " +"on them. Generally the easiest way to do this is for them to become " +"comaintainers of at least the initial package they review. You should be " +"sure to review their commits to the Git repository for how they look, and " +"consider watching their Bugzilla activity at least for a while " +"(Preferences→Email Preferences→https://bugzilla.redhat.com/userprefs.cgi?" +"tab=email[User Watching]). Respond with any comments that you might have " +"and guide them, providing assistance as they need it for any tasks. A " +"provenpackager can step in if necessary." msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:114 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:111 msgid "" "So what's the downside to sponsoring someone? Your sponsoree will likely " "have questions about processes; one of your responsibilities as a sponsor is " "to help them with the answers. A sponsor isn't expected to be omniscient, " "though, so you can feel free to ask for others' advice and opinions if you " -"get a really hard question. " -"https://docs.fedoraproject.org/en-US/fesco/Packager_sponsor_responsibilities/[Sponsor " -"responsibilities are detailed here]." +"get a really hard question. xref:fesco::Packager_sponsor_policy." +"adoc[Sponsor responsibilities are detailed here]." msgstr "" #. type: Title == -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:116 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:113 #, no-wrap msgid "Sponsoring Someone for provenpackagers" msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:128 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:125 msgid "" -"https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/[Provenpackagers] " -"have access to most packages. FESCo members should forward requests for " -"provenpackagers to the sponsors mailing list where sponsors can give their " -"advice on the provenpackager request. Provenpackagers may nominate " -"themselves, but having a sponsor endorse the nomination or proposing the " -"packager to become a provenpackager (the packager should agree) is " -"certainly a good thing." +"xref:fesco::Provenpackager_policy.adoc[Provenpackagers] have access to most " +"packages. FESCo members should forward requests for provenpackagers to the " +"sponsors mailing list where sponsors can give their advice on the " +"provenpackager request. Provenpackagers may nominate themselves, but having " +"a sponsor endorse the nomination or proposing the packager to become a " +"provenpackager (the packager should agree) is certainly a good thing." msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:136 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:133 msgid "" "By granting membership into the provenpackager group for a maintainer you " "are confirming that (at least in your mind) they meet the criteria for that " @@ -190,23 +185,22 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:141 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:138 msgid "" "Provenpackagers are approved on at least 3 positive votes with no negative " "votes. In the event of negative votes, the decision will be made by FESCo " -"at their next meeting. See the " -"https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/[provenpackager " -"description] for more information." +"at their next meeting. See the xref:fesco::Provenpackager_policy." +"adoc[provenpackager description] for more information." msgstr "" #. type: Title == -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:143 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:140 #, no-wrap msgid "Welcome Note" msgstr "" #. type: Plain text -#: ./pages/How_to_Sponsor_a_New_Contributor.adoc:153 +#: pages/How_to_Sponsor_a_New_Contributor.adoc:150 msgid "" "Once you have sponsored someone, we request that you send a note to Fedora " "devel mailing list welcoming the new contributor and cc the person you have " diff --git a/po/fr/master/pages/Installing_Packager_Tools.po b/po/fr/master/pages/Installing_Packager_Tools.po index ecbd946..bc12a64 100644 --- a/po/fr/master/pages/Installing_Packager_Tools.po +++ b/po/fr/master/pages/Installing_Packager_Tools.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2022-02-12 22:14+0000\n" +"POT-Creation-Date: 2023-02-15 21:53+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,19 +17,19 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #. type: Title = -#: ./pages/Installing_Packager_Tools.adoc:1 +#: pages/Installing_Packager_Tools.adoc:1 #, no-wrap msgid "Installing Packager Tools" msgstr "" #. type: Title == -#: ./pages/Installing_Packager_Tools.adoc:4 +#: pages/Installing_Packager_Tools.adoc:3 #, no-wrap msgid "Installing" msgstr "" #. type: Plain text -#: ./pages/Installing_Packager_Tools.adoc:10 +#: pages/Installing_Packager_Tools.adoc:9 msgid "" "The `fedora-packager` package provides tools to help you setup and work with " "Fedora. It will bring in everything necessary for general packaging work. " @@ -38,89 +38,107 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Installing_Packager_Tools.adoc:13 +#: pages/Installing_Packager_Tools.adoc:12 #, no-wrap msgid "$ sudo dnf install fedora-packager fedora-review\n" msgstr "" #. type: Title == -#: ./pages/Installing_Packager_Tools.adoc:15 +#: pages/Installing_Packager_Tools.adoc:14 #, no-wrap msgid "Configuration" msgstr "" #. type: Title === -#: ./pages/Installing_Packager_Tools.adoc:17 +#: pages/Installing_Packager_Tools.adoc:16 #, no-wrap -msgid "Ssh key" +msgid "SSH key" msgstr "" #. type: Plain text -#: ./pages/Installing_Packager_Tools.adoc:25 +#: pages/Installing_Packager_Tools.adoc:24 msgid "" -"You also must have an ssh key configured in the " -"https://accounts.fedoraproject.org/[Fedora Accounts System] to be able to " -"make changes to any package, including your own. `fedpkg` will expect the " -"correct ssh key to be available in your keyring. See wiki page " -"https://fedoraproject.org/wiki/Cryptography#OpenSSH[Cryptography: OpenSSH] " -"for more information." +"You also must have an ssh key configured in the https://accounts." +"fedoraproject.org/[Fedora Accounts System] to be able to make changes to any " +"package, including your own. `fedpkg` will expect the correct ssh key to be " +"available in your keyring. See wiki page https://fedoraproject.org/wiki/" +"Cryptography#OpenSSH[Cryptography: OpenSSH] for more information." +msgstr "" + +#. type: Title === +#: pages/Installing_Packager_Tools.adoc:25 +#, no-wrap +msgid "Mock" +msgstr "" + +#. type: Plain text +#: pages/Installing_Packager_Tools.adoc:30 +msgid "" +"To be able to test the build procedure in a clean chroot with https://rpm-" +"software-management.github.io/mock/[Mock], you need to configure your " +"account to be a member of the `mock` group:" +msgstr "" + +#. type: delimited block - +#: pages/Installing_Packager_Tools.adoc:33 +#, no-wrap +msgid "$ sudo usermod -a -G mock \n" msgstr "" #. type: Title == -#: ./pages/Installing_Packager_Tools.adoc:26 +#: pages/Installing_Packager_Tools.adoc:36 #, no-wrap msgid "Acquiring Kerberos ticket" msgstr "" #. type: Plain text -#: ./pages/Installing_Packager_Tools.adoc:30 +#: pages/Installing_Packager_Tools.adoc:40 msgid "" -"Koji uses Kerberos for authentication. To acquire valid Kerberos ticket, " -"do:" +"xref:Using_the_Koji_Build_System.adoc[Koji] uses https://fedoraproject.org/" +"wiki/Infrastructure/Kerberos[Kerberos] for authentication. To acquire valid " +"Kerberos ticket, do:" msgstr "" #. type: delimited block - -#: ./pages/Installing_Packager_Tools.adoc:33 +#: pages/Installing_Packager_Tools.adoc:43 #, no-wrap -msgid "$ KRB5_TRACE=/dev/stdout kinit @FEDORAPROJECT.ORG\n" +msgid "$ fkinit -u \n" msgstr "" #. type: Plain text -#: ./pages/Installing_Packager_Tools.adoc:36 -msgid "Here, `FEDORAPROJECT.ORG` must be in capital case." +#: pages/Installing_Packager_Tools.adoc:48 +msgid "" +"Kerberos tickets have a set expiration time, so you will frequently have to " +"renew it with `kinit -R` before it expires or acquire a new one." msgstr "" #. type: Plain text -#: ./pages/Installing_Packager_Tools.adoc:38 +#: pages/Installing_Packager_Tools.adoc:52 msgid "" -"Kerberos tickets have an expiration time, so `kinit` needs to be " -"periodically re-issued." +"Alternatively, if you are using Fedora Workstation and don't have 2FA " +"enabled on your Fedora account, you may add it through GNOME Online Accounts." msgstr "" #. type: Plain text -#: ./pages/Installing_Packager_Tools.adoc:41 +#: pages/Installing_Packager_Tools.adoc:56 msgid "" -"See " -"https://fedoraproject.org/wiki/Infrastructure/Kerberos[Infrastructure/Kerberos] " -"for more information about the Fedora Kerberos setup." +"To verify you can authenticate to Koji, use a following, no-operation `koji` " +"command. Observe that it reports your Fedora username and that it confirms " +"a GSSAPI (an encapsulation method for Kerberos) authentication:" msgstr "" -#. type: Title === -#: ./pages/Installing_Packager_Tools.adoc:42 +#. type: delimited block - +#: pages/Installing_Packager_Tools.adoc:60 #, no-wrap -msgid "Configuring Mock" -msgstr "" - -#. type: Plain text -#: ./pages/Installing_Packager_Tools.adoc:47 msgid "" -"To be able to test the build procedure in a clean chroot with " -"https://rpm-software-management.github.io/mock/[Mock], you need to configure " -"your account to be a member of the `mock` group:" +"$ koji moshimoshi\n" +", !\n" msgstr "" #. type: delimited block - -#: ./pages/Installing_Packager_Tools.adoc:50 +#: pages/Installing_Packager_Tools.adoc:63 #, no-wrap -msgid "$ sudo usermod -a -G mock \n" +msgid "" +"You are using the hub at https://koji.fedoraproject.org/kojihub\n" +"Authenticated via GSSAPI\n" msgstr "" diff --git a/po/fr/master/pages/New_Package_Process_for_Existing_Contributors.po b/po/fr/master/pages/New_Package_Process_for_Existing_Contributors.po index 261a92c..f13f119 100644 --- a/po/fr/master/pages/New_Package_Process_for_Existing_Contributors.po +++ b/po/fr/master/pages/New_Package_Process_for_Existing_Contributors.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-01-24 21:56+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,175 +16,187 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/New_package_process_for_existing_contributors #. type: Title = -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:3 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:1 #, no-wrap msgid "New Package Process for Existing Contributors" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:8 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:5 msgid "" "This is a short version of the New Package Process, streamlined to show how " "existing contributors can make new packages." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:13 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:10 msgid "" -"Read the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging " -"Guidelines] and " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Package " -"Naming Guidelines]. Really. Be comfortable with them." +"Read the xref:packaging-guidelines::index.adoc[Packaging Guidelines] and " +"xref:packaging-guidelines::Naming.adoc[Package Naming Guidelines]. Really. " +"Be comfortable with them." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:15 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:12 msgid "Make a package." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:18 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:15 msgid "" "You should make sure that it is a new package. A list of existing packages " "in Fedora Packages is here: https://src.fedoraproject.org/projects/rpms/*" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:20 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:17 msgid "" -"Some information on how to create an RPM package is in " -"https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages[Creating " -"RPM packages]." +"Some information on how to create an RPM package is in xref:" +"Packaging_Tutorial_GNU_Hello.adoc[Packaging Tutorial: GNU Hello]." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:23 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:20 msgid "" -"Make sure that your package meets the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging " -"Guidelines] and " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Package " -"Naming Guidelines]" +"Make sure that your package meets the xref:packaging-guidelines::index." +"adoc[Packaging Guidelines] and xref:packaging-guidelines::Naming." +"adoc[Package Naming Guidelines]" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:27 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:24 msgid "" "Be aware of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] " -"and " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/[Package " -"Review Guidelines]. They will be used during the package review." +"and xref:packaging-guidelines::ReviewGuidelines.adoc[Package Review " +"Guidelines]. They will be used during the package review." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:29 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:26 msgid "Upload your SRPM and SPEC files onto the internet somewhere." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:32 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:29 msgid "" "If you have already got a Fedora Account then you can use your storage at " "http://fedorapeople.org for this." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:34 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:31 msgid "Make sure you have a Bugzilla account at bugzilla.redhat.com" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:36 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:33 msgid "" -"Fill out " -"https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review[Bugzilla " -"Fedora review form] to create a review request." +"Fill out https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?" +"product=Fedora&format=fedora-review[Bugzilla Fedora review form] to create a " +"review request." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:39 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:36 msgid "" "Make sure you put the name of the package in the `Review Summary` field, " "along with a very brief summary of what it is" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:41 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:38 msgid "" "Make sure that you put the URL paths for the SPEC file and the SRPM file in " "the `Review Description`" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:45 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:42 msgid "" "Put a description of your package (usually, this can be the same thing as " "what you put in the spec `%description`) in `Review Description`" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:47 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:44 msgid "" -"The review process is described in detail in " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/[Package " -"Review Guidelines]." +"The review process is described in detail in xref:packaging-guidelines::" +"ReviewGuidelines.adoc[Package Review Guidelines]." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:50 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:47 msgid "" "Watch the review request in Bugzilla. Fix any blockers that the reviewer(s) " "point out." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:57 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:49 msgid "" -"When the package is approved by the reviewer, request a git module with " -"`fedpkg request-repo PACKAGE-NAME BUGZILLA-TICKET-NUMBER` and when the repo " -"is created request branches with `fedpkg request-branch --repo PACKAGE-NAME " -"BRANCH`. You might need to get a pagure-API-token before being able to " -"successfully request the repo. Wait until the requests are approved." +"When the package is approved, request a distgit repository for your package." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:61 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:51 +msgid "Make sure the reviewer is the Assignee in your Bugzilla ticket." +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_Existing_Contributors.adoc:56 +msgid "" +"Request a distgit repository with `fedpkg request-repo PACKAGE-NAME BUGZILLA-" +"TICKET-NUMBER`. (xref:Package_Maintenance_Guide.adoc[Package Maintenance " +"Guide] has more information about `fedpkg`.) You might need to get a pagure-" +"API-token before being able to successfully request the repo." +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_Existing_Contributors.adoc:60 +msgid "" +"When the repo is created, it only contains the `rawhide` branch. If you " +"want to bring the package to other Fedora releases, request branches with " +"`fedpkg request-branch --repo PACKAGE-NAME BRANCH`." +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_Existing_Contributors.adoc:63 msgid "" -"Once the requests are approved, checkout the git module with `fedpkg clone " -"`. (xref:Package_Maintenance_Guide.adoc[Package Maintenance " -"Guide] has more information about `fedpkg`.)" +"Once the requests have been processed, checkout the distgit repository with " +"`fedpkg clone `." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:63 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:65 msgid "Import your srpm" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:65 -msgid "First `kinit username@FEDORAPROJECT.ORG`" +#: pages/New_Package_Process_for_Existing_Contributors.adoc:67 +msgid "First `fkinit -u username`" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:67 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:69 msgid "" "Then you can import the approved SRPM into the rawhide branch by running " "`fedpkg import libfoo-x.x.x.src.rpm; git commit -m \"Initial import " -"(#nnnnnn).\"` (where `nnnnnn` is your Bugzilla package review bug number)." +"(fedora#nnnnnn).\"` (where `nnnnnn` is your Bugzilla package review bug " +"number). If your package is using _autochangelog_, writing the bug number as " +"specified will make Bodhi automatically close the bug when your package is " +"submitted to Rawhide stable repository." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:69 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:71 msgid "" "Obviously, replace `libfoo-x.x.x.src.rpm` with the full path to your " "approved SRPM." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:75 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:77 msgid "" "You should see it upload the sources, and finish successfully. If you " "didn't set up `ssh-agent` it will ask often for your ssh-key passphrase. " @@ -192,26 +204,26 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:77 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:79 msgid "Now run `git push` to get the final versions in your rawhide branch." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:81 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:83 msgid "" "You can now import the package to your branches (which you requested in Step " "7) too" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:85 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:87 msgid "" "The quickest way to do this is to use `fedpkg switch-branch BRANCH` to " "switch the branch (where `BRANCH` can be `f13` and so on)." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:90 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:92 msgid "" "Now you can `git merge rawhide`. This will get `.spec` file, `.gitignore` " "and source file together with any patches and other files from the rawhide " @@ -219,33 +231,33 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:93 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:95 msgid "" "Previous step already created commit for you, now you can push the results " "using `fedpkg push` or `git push`." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:95 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:97 msgid "Request builds" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:98 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:100 msgid "" "For each branch that you'd like to request a build for, switch using `fedpkg " "switch-branch` and run `fedpkg build`." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:103 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:105 msgid "" "If everything goes well, it should queue up your branch for building, the " "package will cleanly build, and you're done!" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:111 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:113 msgid "" "If it fails to build, the buildsystem will send you an email to report the " "failure and link you to the logs. Commit any needed changes to git, bump " @@ -253,12 +265,13 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:114 -msgid "Close the Bugzilla ticket (assuming that the package built successfully)" +#: pages/New_Package_Process_for_Existing_Contributors.adoc:116 +msgid "" +"Close the Bugzilla ticket (assuming that the package built successfully)" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:118 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:120 msgid "" "You should close it with resolution `NEXTRELEASE` or `RAWHIDE`, depending on " "where you built the package. The resolution field will appear after you set " @@ -266,42 +279,41 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:123 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:125 msgid "" "If this package will be built for any version of Fedora that is already " "released please submit it for inclusion in the `fedora-updates` repository " -"for those versions of Fedora. See " -"xref:Package_Update_Guide.adoc#Later_Branched_and_stable_releases[Package " -"Update Guide] for more details." +"for those versions of Fedora. See xref:Package_Update_Guide." +"adoc#Later_Branched_and_stable_releases[Package Update Guide] for more " +"details." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:125 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:127 msgid "" -"Add the package to the " -"https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups[comps " -"file(s)] if appropriate." +"Add the package to the https://fedoraproject.org/wiki/" +"How_to_use_and_edit_comps.xml_for_package_groups[comps file(s)] if " +"appropriate." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:127 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:129 msgid "" "Consider enabling xref:Upstream_Release_Monitoring.adoc[Upstream Release " "Monitoring] for the package." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:133 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:135 msgid "" "We know that this process can be as clear as mud sometimes, we're always " "trying to make it better. If you run into any problems, or have any " -"questions, please ask on the " -"https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[Fedora " -"development list]." +"questions, please ask on the https://lists.fedoraproject.org/archives/list/" +"devel@lists.fedoraproject.org/[Fedora development list]." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_Existing_Contributors.adoc:134 +#: pages/New_Package_Process_for_Existing_Contributors.adoc:136 msgid "" "xref:Package_Maintenance_Guide.adoc[Package Maintenance Guide] may also be " "of use." diff --git a/po/fr/master/pages/New_Package_Process_for_New_Contributors.po b/po/fr/master/pages/New_Package_Process_for_New_Contributors.po index d0fdf1c..c8830df 100644 --- a/po/fr/master/pages/New_Package_Process_for_New_Contributors.po +++ b/po/fr/master/pages/New_Package_Process_for_New_Contributors.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-01-24 21:56+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,69 +16,123 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Adding_a_new_package #. type: Title = -#: ./pages/New_Package_Process_for_New_Contributors.adoc:3 +#: pages/New_Package_Process_for_New_Contributors.adoc:3 #, no-wrap msgid "New Package Process for New Contributors" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:9 +#: pages/New_Package_Process_for_New_Contributors.adoc:8 msgid "" "This is a long version of the New Package Process, containing more details " -"so new contributors can follow it more easily. Also the mandatory " -"xref:How_to_Get_Sponsored_into_the_Packager_Group.adoc[sponsoring] step is " +"so new contributors can follow it more easily. Also the mandatory xref:" +"How_to_Get_Sponsored_into_the_Packager_Group.adoc[sponsoring] step is " "included." msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:11 +#: pages/New_Package_Process_for_New_Contributors.adoc:10 +#, no-wrap +msgid "Install Packager Tools" +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:13 +msgid "Follow xref:Installing_Packager_Tools.adoc[Installing Packager Tools]." +msgstr "" + +#. type: Title == +#: pages/New_Package_Process_for_New_Contributors.adoc:15 +#, no-wrap +msgid "Check if the package already exists" +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:20 +msgid "" +"If some useful software is not included in Fedora already, you can submit it " +"as a new package. The package you are submitting can be of any Free and " +"Open Source project." +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:23 +msgid "" +"Before creating your package, make sure that the software is not already in " +"the Fedora repository:" +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:26 +msgid "" +"Check if the package already exists by searching in https://packages." +"fedoraproject.org/[Fedora Packages]." +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:29 +msgid "" +"Search in the http://fedoraproject.org/PackageReviewStatus/[Review Tracker] " +"for packages under review." +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:31 +msgid "" +"Check the https://packager-dashboard.fedoraproject.org/user/orphan[orphaned " +"or retired packages that need new maintainers]." +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:33 +msgid "" +"Be aware of https://fedoraproject.org/wiki/Forbidden_items[forbidden items]." +msgstr "" + +#. type: Title == +#: pages/New_Package_Process_for_New_Contributors.adoc:35 #, no-wrap msgid "Make a Package" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:15 +#: pages/New_Package_Process_for_New_Contributors.adoc:39 msgid "" -"If you don't know how to create an RPM package, see the " -"https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/index.html[How " -"to create an RPM package]." +"If you don't know how to create an RPM package, see the xref:" +"Packaging_Tutorial_GNU_Hello.adoc[Packaging Tutorial: GNU Hello]." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:17 +#: pages/New_Package_Process_for_New_Contributors.adoc:41 msgid "" -"Make sure that your package meets the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging " -"Guidelines] and " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Package " -"Naming Guidelines]." +"Make sure that your package meets the xref:packaging-guidelines::index." +"adoc[Packaging Guidelines] and xref:packaging-guidelines::Naming." +"adoc[Package Naming Guidelines]." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:20 +#: pages/New_Package_Process_for_New_Contributors.adoc:44 msgid "" -"Be aware of the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/[Package " +"Be aware of the xref:packaging-guidelines::ReviewGuidelines.adoc[Package " "Review Guidelines] (they will be used during the package review)." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:24 +#: pages/New_Package_Process_for_New_Contributors.adoc:48 msgid "" "Make sure your package builds. This is surprisingly important because a " "significant number of submissions don't." msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:26 +#: pages/New_Package_Process_for_New_Contributors.adoc:50 #, no-wrap msgid "Upload Your Package" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:35 +#: pages/New_Package_Process_for_New_Contributors.adoc:59 msgid "" "Upload your SRPM and SPEC files onto the Internet somewhere so that others " "can retrieve them. This can be anywhere accessible by a URL, but it is " @@ -88,39 +142,38 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:42 +#: pages/New_Package_Process_for_New_Contributors.adoc:66 msgid "" "If you want to make ad-hoc builds available for users while you are getting " -"the package into the official repositories, consider using " -"https://copr.fedorainfracloud.org[Copr]. It is a lightweight automated " -"build system that can create repositories using the SRPM you upload. You " -"can use this Copr space to point reviewers to your src.rpm and spec." +"the package into the official repositories, consider using https://copr." +"fedorainfracloud.org[Copr]. It is a lightweight automated build system that " +"can create repositories using the SRPM you upload. You can use this Copr " +"space to point reviewers to your src.rpm and spec." msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:44 +#: pages/New_Package_Process_for_New_Contributors.adoc:68 #, no-wrap msgid "Create Your Review Request" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:47 +#: pages/New_Package_Process_for_New_Contributors.adoc:71 msgid "" -"Fill out " -"https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review[Bugzilla " -"Fedora review form]." +"Fill out https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?" +"product=Fedora&format=fedora-review[Bugzilla Fedora review form]." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:51 +#: pages/New_Package_Process_for_New_Contributors.adoc:75 msgid "" "Before submitting your request, be sure there’s not a previous request for " -"the same package. There is a convenient search box on the " -"http://fedoraproject.org/PackageReviewStatus/[package review status page]." +"the same package. There is a convenient search box on the http://" +"fedoraproject.org/PackageReviewStatus/[package review status page]." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:56 +#: pages/New_Package_Process_for_New_Contributors.adoc:80 msgid "" "Make sure that you put the *name of the package* (excluding version and " "release numbers) in the `Review Summary` field, along with a very *brief " @@ -128,7 +181,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:62 +#: pages/New_Package_Process_for_New_Contributors.adoc:86 msgid "" "Put a *description* of your package (usually, this can be the same thing as " "what you put in the spec `%description`) in the `Review Description` " @@ -136,7 +189,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:68 +#: pages/New_Package_Process_for_New_Contributors.adoc:92 msgid "" "Explain in the ticket that this is your first package and you need a " "sponsor. Also, include any information that may help prospective sponsors. " @@ -145,46 +198,45 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:72 +#: pages/New_Package_Process_for_New_Contributors.adoc:96 msgid "" "For bonus points, include a link to a successful koji build so that everyone " "knows you did all of your homework." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:74 +#: pages/New_Package_Process_for_New_Contributors.adoc:98 msgid "" -"The review process is described in detail on the " -"xref:Package_Review_Process.adoc[Package Review Process] page." +"The review process is described in detail on the xref:Package_Review_Process." +"adoc[Package Review Process] page." msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:76 +#: pages/New_Package_Process_for_New_Contributors.adoc:100 #, no-wrap msgid "Inform Upstream" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:89 +#: pages/New_Package_Process_for_New_Contributors.adoc:113 msgid "" -"The Fedora Project prefers " -"xref:Staying_Close_to_Upstream_Projects.adoc[Staying Close to Upstream " -"Projects]. Inform the developers that you are packaging the software. You " -"can do that by sending them an email introducing yourself and pointing out " -"the review request. This sets up the stage for future conversations. They " -"will usually advertise the fact that their software is now part of Fedora or " -"might want to inform you of important bugs in the existing release, future " -"roadmaps etc." +"The Fedora Project prefers xref:Staying_Close_to_Upstream_Projects." +"adoc[Staying Close to Upstream Projects]. Inform the developers that you " +"are packaging the software. You can do that by sending them an email " +"introducing yourself and pointing out the review request. This sets up the " +"stage for future conversations. They will usually advertise the fact that " +"their software is now part of Fedora or might want to inform you of " +"important bugs in the existing release, future roadmaps etc." msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:91 +#: pages/New_Package_Process_for_New_Contributors.adoc:115 #, no-wrap msgid "Watch for Feedback" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:96 +#: pages/New_Package_Process_for_New_Contributors.adoc:120 msgid "" "Watch the Bugzilla report for your first package. You should get " "notifications of changes by email. Fix any blockers that the reviewer(s) " @@ -192,13 +244,13 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:98 +#: pages/New_Package_Process_for_New_Contributors.adoc:122 #, no-wrap msgid "Get Sponsored" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:109 +#: pages/New_Package_Process_for_New_Contributors.adoc:133 msgid "" "When the package is APPROVED by the reviewer, you must separately obtain " "member sponsorship in order to check in and build your package. Sponsorship " @@ -209,7 +261,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:112 +#: pages/New_Package_Process_for_New_Contributors.adoc:136 msgid "" "See xref:How_to_Get_Sponsored_into_the_Packager_Group.adoc[How to Get " "Sponsored into the Packager Group] for more information on the process of " @@ -217,325 +269,427 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:115 +#: pages/New_Package_Process_for_New_Contributors.adoc:139 msgid "" "Your sponsor can add you to the packager group. You should receive an email " "confirmation of your sponsorship." msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:117 +#: pages/New_Package_Process_for_New_Contributors.adoc:141 #, no-wrap msgid "Add Package to Source Code Management (SCM) system and Set Owner" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:121 +#: pages/New_Package_Process_for_New_Contributors.adoc:145 msgid "" -"Before proceeding, please sync your account by login on " -"https://src.fedoraproject.org/[Fedora Package Sources] using your FAS " -"credentials." +"Before proceeding, please sync your account by login on https://src." +"fedoraproject.org/[Fedora Package Sources] using your FAS credentials." msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:133 +#: pages/New_Package_Process_for_New_Contributors.adoc:157 msgid "" -"If you are becoming a maintainer for a new package, instead of being a " -"co-maintainer, use https://pagure.io/fedpkg[fedpkg] to request a new git " +"If you are becoming a maintainer for a new package, instead of being a co-" +"maintainer, use https://pagure.io/fedpkg[fedpkg] to request a new git " "repository for your package. The sub-command is `fedpkg request-repo` which " "includes help text for setting up the Pagure API token the command " -"requires. When creating your API-key choose toogle-all for the ACLs. You " +"requires. When creating your API-key choose toggle-all for the ACLs. You " "must specify the repository name and review bug number. For example:" msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:136 +#: pages/New_Package_Process_for_New_Contributors.adoc:160 #, no-wrap msgid "fedpkg request-repo python-prometheus_client 1590452\n" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:142 +#: pages/New_Package_Process_for_New_Contributors.adoc:166 msgid "" -"The request will be reviewed and processed by an admin, usually within 24 " -"hours. Once the ticket is processed, you will have access to commit and " -"build the package." +"The request will be reviewed and processed automatically. After processing, " +"you will have access to commit and build the package. In case the " +"automation does not work, you can report the problem to https://pagure.io/" +"fedora-infra/toddlers/issues[Toddlers issue tracker]." +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:170 +msgid "" +"`fedpkg request-repo` only creates a branch for Rawhide. To request " +"branches for other Fedora releases, use `fedpkg request-branch`:" +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:174 +msgid " fedpkg request-branch --repo python-prometheus_client f{MAJOROSVER}" +msgstr "" + +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:179 +#, no-wrap +msgid "" +"You will need to run this for each non-rawhide branch.\n" +"If you wish, you can also use the `--all-releases` flag\n" +"to request branches for all current Fedora releases.\n" +msgstr "" + +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:181 +#, no-wrap +msgid "[#check_out_the_distgit_repository]\n" msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:144 +#: pages/New_Package_Process_for_New_Contributors.adoc:181 #, no-wrap -msgid "Check out the module" +msgid "[[check_out_the_module]] Check out the distgit repository" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:152 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:189 msgid "" -"You _could_ check out your module now, but before doing that, consider doing " -"`mkdir ~/fedora-scm ; cd ~/fedora-scm` — that way, all your files are inside " -"a single directory. Also, run `ssh-add`, so that you won't have to keep " -"typing in your key password." +"You _could_ check out your distgit repository now, but before doing that, " +"consider doing `mkdir ~/fedora-scm ; cd ~/fedora-scm` — that way, all your " +"files are inside a single directory. Also, run `ssh-add`, so that you won't " +"have to keep typing in your key password." +msgstr "" + +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:191 +msgid "Now you are ready to checkout your distgit repository from the SCM:" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:154 -msgid "Now you are ready to checkout your module from the SCM:" +#: pages/New_Package_Process_for_New_Contributors.adoc:194 +#, no-wrap +msgid " fedpkg clone your-package\n" msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:157 +#: pages/New_Package_Process_for_New_Contributors.adoc:197 #, no-wrap -msgid " fedpkg clone your-package\n" +msgid "[#test_your_package]\n" msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:160 +#: pages/New_Package_Process_for_New_Contributors.adoc:197 #, no-wrap msgid "Test Your Package" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:167 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:204 msgid "" -"Refer to " -"https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock " -"to test package builds] and " -"xref:Using_the_Koji_Build_System.adoc#scratch_builds for more information on " -"testing your package. Mock uses your local system while Koji command line " -"tool uses the Fedora build system server." +"Refer to https://fedoraproject.org/wiki/" +"Using_Mock_to_test_package_builds[Using Mock to test package builds] and " +"xref:Using_the_Koji_Build_System.adoc#scratch_builds[Koji Scratch Builds] " +"for more information on testing your package. Mock uses your local system " +"while Koji command line tool uses the Fedora build system server." +msgstr "" + +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:206 +msgid "[#import_commit_and_build_your_package]" msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:169 +#: pages/New_Package_Process_for_New_Contributors.adoc:206 #, no-wrap msgid "Import, commit, and build your package" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:173 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:210 msgid "" -"Now that you've checked out your (empty) package module with `fedpkg`, cd " -"into the module's main branch:" +"Now that you've checked out your (empty) distgit repository with `fedpkg`, " +"cd into the repository's main branch:" +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:213 +msgid "cd " msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:176 +#: pages/New_Package_Process_for_New_Contributors.adoc:216 #, no-wrap -msgid "cd \n" +msgid "Run fedpkg to import the contents of the SRPM into the SCM:\n" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:179 -msgid "Run fedpkg to import the contents of the SRPM into the SCM:" +#: pages/New_Package_Process_for_New_Contributors.adoc:219 +msgid "fedpkg import PATH_TO_SRPM" +msgstr "" + +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:226 +msgid "" +"# Review Changes, press 'q' to stop; Revert with: git reset --hard HEAD git " +"commit -m \"Initial import (fedora#XXXXXX).\" git push fedpkg build" msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:182 +#: pages/New_Package_Process_for_New_Contributors.adoc:232 #, no-wrap -msgid "fedpkg import PATH_TO_SRPM\n" +msgid "" +"Obviously, replace `PATH_TO_SRPM` with the full path\n" +"(not URL)\n" +"to your approved SRPM,\n" +"and `XXXXXX` with the package review bug number.\n" msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:189 +#: pages/New_Package_Process_for_New_Contributors.adoc:236 #, no-wrap msgid "" -"# Review Changes, press 'q' to stop; Revert with: git reset --hard HEAD\n" -"git commit -m \"Initial import (#XXXXXX).\"\n" -"git push\n" -"fedpkg build\n" +"If your package is using _autochangelog_, writing the bug number as specified\n" +"will make the Fedora update system automatically close the bug when your package is\n" +"submitted to Rawhide stable repository.\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:195 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:240 +#, no-wrap msgid "" -"Obviously, replace `PATH_TO_SRPM` with the full path (not URL) to your " -"approved SRPM, and `XXXXXX` with the package review bug number." +"This imports into, commits, and builds only the *main*\n" +"(https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide])\n" +"branch.\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:199 -msgid "" -"This imports into, commits, and builds only the *main* " -"(https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide]) branch." +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:242 +#, no-wrap +msgid "If the push fails with this kind of message:\n" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:201 -msgid "If the push fails with this kind of message:" +#: pages/New_Package_Process_for_New_Contributors.adoc:247 +msgid "" +"W access for why DENIED to YOUR_ACCOUNT fatal: The remote end hung up " +"unexpectedly Could not push: Command '['git', 'push']' returned non-zero " +"exit status 128" msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:206 +#: pages/New_Package_Process_for_New_Contributors.adoc:251 #, no-wrap msgid "" -"W access for why DENIED to YOUR_ACCOUNT\n" -"fatal: The remote end hung up unexpectedly\n" -"Could not push: Command '['git', 'push']' returned non-zero exit status " -"128\n" +"Then you don't have the necessary rights to modify that package branch.\n" +"View `\\https://src.fedoraproject.org/rpms/PACKAGE_NAME` to request those rights.\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:210 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:254 +#, no-wrap msgid "" -"Then you don't have the necessary rights to modify that package branch. " -"View https://src.fedoraproject.org/rpms/PACKAGE_NAME to request those " -"rights." +"For more information on using the Fedora package maintenance system,\n" +"see the xref:Package_Maintenance_Guide.adoc[Package maintenance guide].\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:213 -msgid "" -"For more information on using the Fedora package maintenance system, see the " -"xref:Package_Maintenance_Guide.adoc[Package maintenance guide]." +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:256 +#, no-wrap +msgid "[#update_your_branches]\n" msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:215 +#: pages/New_Package_Process_for_New_Contributors.adoc:256 #, no-wrap msgid "Update Your Branches (if desired)" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:222 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:263 msgid "" "Branches are `f#` (formerly `F-#` and before that `FC-#`), `main`, etc. So " "`f` is the branch for Fedora." msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:224 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:265 msgid "To switch to a branch first:" msgstr "" +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:268 +msgid "fedpkg switch-branch BRANCH" +msgstr "" + #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:227 +#: pages/New_Package_Process_for_New_Contributors.adoc:271 #, no-wrap -msgid "fedpkg switch-branch BRANCH \n" +msgid "(e.g. `f{MAJOROSVER}`)\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:230 -msgid "(e.g. `f34`)" +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:274 +#, no-wrap +msgid "" +"Merge the initial commit from main (Rawhide),\n" +"creating an identical commit in the branch:\n" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:233 -msgid "" -"Merge the initial commit from main (Rawhide), creating an identical commit " -"in the branch:" +#: pages/New_Package_Process_for_New_Contributors.adoc:277 +msgid "git merge rawhide" msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:236 +#: pages/New_Package_Process_for_New_Contributors.adoc:280 #, no-wrap -msgid "git merge rawhide\n" +msgid "Push the changes to the server:\n" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:239 -msgid "Push the changes to the server:" +#: pages/New_Package_Process_for_New_Contributors.adoc:283 +msgid "git push" msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:242 +#: pages/New_Package_Process_for_New_Contributors.adoc:286 #, no-wrap -msgid "git push\n" +msgid "Build the package:\n" msgstr "" #. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:245 -msgid "Build the package:" +#: pages/New_Package_Process_for_New_Contributors.adoc:289 +msgid "fedpkg build" msgstr "" #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:248 +#: pages/New_Package_Process_for_New_Contributors.adoc:294 #, no-wrap -msgid "fedpkg build\n" +msgid "" +"If there is another branch to work with\n" +"repeat _To switch to a branch_\n" +"and import and commit to each branch.\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:253 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:299 +#, no-wrap msgid "" -"If there is another branch to work with repeat _To switch to a branch_ and " -"import and commit to each branch." +"If everything goes well,\n" +"it should queue up your branch for building,\n" +"the package will cleanly build,\n" +"and you're done!\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:258 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:307 +#, no-wrap msgid "" -"If everything goes well, it should queue up your branch for building, the " -"package will cleanly build, and you're done!" +"If it fails to build,\n" +"the build system will send you an email\n" +"to report the failure\n" +"and show you to the logs.\n" +"Commit any needed changes to git,\n" +"bump the SPEC release number,\n" +"and request a new build.\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:266 -msgid "" -"If it fails to build, the build system will send you an email to report the " -"failure and show you to the logs. Commit any needed changes to git, bump " -"the SPEC release number, and request a new build." +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:309 +#, no-wrap +msgid "[#submit_package_as_update_in_bodhi]\n" msgstr "" #. type: Title === -#: ./pages/New_Package_Process_for_New_Contributors.adoc:268 +#: pages/New_Package_Process_for_New_Contributors.adoc:309 #, no-wrap msgid "Submit Package as Update in Bodhi" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:275 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:319 msgid "" -"The Fedora update system called Bodhi is used for pushing updates, " -"classifying packages etc. Do not submit Rawhide (main branch) builds via " -"Bodhi." +"The Fedora update system called https://bodhi.fedoraproject.org[Bodhi] is " +"used for pushing updates, classifying packages etc. You do not need to " +"submit updates for Rawhide (main) manually because these are automatically " +"created for you when the build completes. For all other branches, you must " +"manually push updates for all builds that you would like to make available " +"to users." msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:279 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:323 msgid "" "You can push an update using Bodhi via the command line using this in each " "branch:" msgstr "" +#. type: Plain text +#: pages/New_Package_Process_for_New_Contributors.adoc:326 +msgid "fedpkg update" +msgstr "" + #. type: delimited block . -#: ./pages/New_Package_Process_for_New_Contributors.adoc:282 +#: pages/New_Package_Process_for_New_Contributors.adoc:333 #, no-wrap -msgid "fedpkg update\n" +msgid "" +"It is often easier to complete builds for all your branches\n" +"and then push a single update using the https://bodhi.fedoraproject.org/updates/new[Bodhi web interface].\n" +"Bodhi is smart enough to split your update into individual updates,\n" +"one for each Fedora release branch.\n" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:285 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:339 +#, no-wrap msgid "" -"See the xref:Package_Update_Guide.adoc[Package Update Guide] for more " -"details." +"You can also select multiple builds from different packages\n" +"to include in a single update using the web interface.\n" +"This is useful when you would like to push linked builds,\n" +"for example: an application package and its dependencies\n" +"that are necessary for it to run correctly.\n" +msgstr "" + +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:341 +#, no-wrap +msgid "Please see the xref:Package_Update_Guide.adoc[Package Update Guide] for more details.\n" +msgstr "" + +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:343 +#, no-wrap +msgid "[#make_the_package_available_in_comps_files]\n" msgstr "" #. type: Title == -#: ./pages/New_Package_Process_for_New_Contributors.adoc:287 +#: pages/New_Package_Process_for_New_Contributors.adoc:343 #, no-wrap msgid "Make the package available in \"comps\" files" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:294 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:350 msgid "" "If appropriate for the package, make it available in \"comps\" files so that " "it can be selected during installation and included in dnf package group " -"operations. See " -"https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups?rd=PackageMaintainers/CompsXml[How " -"to use and edit comps.xml for package groups] for more info." +"operations. See https://fedoraproject.org/wiki/How_to_use_and_edit_comps." +"xml_for_package_groups?rd=PackageMaintainers/CompsXml[How to use and edit " +"comps.xml for package groups] for more info." +msgstr "" + +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:352 +msgid "[#watch_for_updates]" msgstr "" #. type: Title === -#: ./pages/New_Package_Process_for_New_Contributors.adoc:296 +#: pages/New_Package_Process_for_New_Contributors.adoc:352 #, no-wrap msgid "Watch for updates" msgstr "" -#. type: Plain text -#: ./pages/New_Package_Process_for_New_Contributors.adoc:303 +#. type: delimited block . +#: pages/New_Package_Process_for_New_Contributors.adoc:359 msgid "" "Fedora has the infrastructure available for monitoring new upstream releases " -"of the software you are packaging. Refer to " -"xref:Upstream_Release_Monitoring.adoc[Upstream Release Monitoring] for more " +"of the software you are packaging. Refer to xref:" +"Upstream_Release_Monitoring.adoc[Upstream Release Monitoring] for more " "details." msgstr "" diff --git a/po/fr/master/pages/Package_Maintenance_Guide.po b/po/fr/master/pages/Package_Maintenance_Guide.po index e25ce32..3bef9ce 100644 --- a/po/fr/master/pages/Package_Maintenance_Guide.po +++ b/po/fr/master/pages/Package_Maintenance_Guide.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-06-02 22:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,15 +16,14 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Package_maintenance_guide #. type: Title = -#: ./pages/Package_Maintenance_Guide.adoc:3 +#: pages/Package_Maintenance_Guide.adoc:3 #, no-wrap msgid "Package Maintenance Guide" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:11 +#: pages/Package_Maintenance_Guide.adoc:10 msgid "" "This page provides some basic instructions for day-to-day usage of the " "http://git-scm.com/[git]-based package maintenance system for Fedora. It is " @@ -34,103 +33,61 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:15 +#: pages/Package_Maintenance_Guide.adoc:14 msgid "" -"Some pre-existing knowledge of git may be useful, but is not a " -"pre-requisite. In fact, Fedora packaging can be a relatively painless " +"Some pre-existing knowledge of git may be useful, but is not a pre-" +"requisite. In fact, Fedora packaging can be a relatively painless " "introduction to it." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:17 +#: pages/Package_Maintenance_Guide.adoc:16 msgid "You may have been looking for, or also be interested in:" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:19 -msgid "" -"https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/[Creating " -"RPM packages]" +#: pages/Package_Maintenance_Guide.adoc:18 +msgid "xref:Packaging_Tutorial_GNU_Hello.adoc[Packaging Tutorial: GNU Hello]" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:20 -msgid "" -"https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging " -"Guidelines]" +#: pages/Package_Maintenance_Guide.adoc:19 +msgid "xref:packaging-guidelines::index.adoc[Packaging Guidelines]" msgstr "" #. type: Title == -#: ./pages/Package_Maintenance_Guide.adoc:22 +#: pages/Package_Maintenance_Guide.adoc:21 #, no-wrap -msgid "Installing _fedpkg_ and doing initial setup" +msgid "Installing Packager Tools" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:26 -msgid "" -"Start by installing `fedpkg` with `dnf install fedpkg`. This will be your " -"primary interface to the packaging system." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:31 -msgid "" -"You also must have an ssh key configured in the " -"https://accounts.fedoraproject.org/[Fedora Accounts System] to be able to " -"make changes to any package (including your own). `fedpkg` will expect the " -"correct ssh key to be available in your keyring." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:35 -msgid "" -"Before uploading sources with `new-sources` and `upload` and building " -"packages in Koji, with `build` for example, you have to get your Kerberos " -"credential first with `kinit`, e.g." -msgstr "" - -#. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:38 -#, no-wrap -msgid "kinit [FAS name]@FEDORAPROJECT.ORG\n" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:41 -msgid "Keep `FEDORAPROJECT.ORG` in capital case." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:44 -msgid "" -"Set your Fedora Account System username in file `~/.fedora.upn`. You can do " -"this via `echo \"FAS_USERNAME\" > ~/.fedora.upn`." +#: pages/Package_Maintenance_Guide.adoc:24 +msgid "Follow xref:Installing_Packager_Tools.adoc[Installing Packager Tools]." msgstr "" #. type: Title == -#: ./pages/Package_Maintenance_Guide.adoc:46 +#: pages/Package_Maintenance_Guide.adoc:26 #, no-wrap msgid "Common fedpkg commands" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:52 +#: pages/Package_Maintenance_Guide.adoc:32 msgid "" "This section lists typical fedpkg commands in a normal workflow, with short " -"descriptions. In this workflow, we will be operating on the " -"https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide] branch of the " -"package." +"descriptions. In this workflow, we will be operating on the https://" +"fedoraproject.org/wiki/Releases/Rawhide[Rawhide] branch of the package." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:53 +#: pages/Package_Maintenance_Guide.adoc:33 #, no-wrap msgid "Check out a package" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:57 +#: pages/Package_Maintenance_Guide.adoc:37 #, no-wrap msgid "" "fedpkg co \n" @@ -138,38 +95,38 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:61 +#: pages/Package_Maintenance_Guide.adoc:41 msgid "" "This retrieves a copy of the package sources from the server. It's known as " "your 'working copy'." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:62 +#: pages/Package_Maintenance_Guide.adoc:42 #, no-wrap msgid "Update your checked-out copy from the Fedora server" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:65 +#: pages/Package_Maintenance_Guide.adoc:45 #, no-wrap msgid "fedpkg pull\n" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:67 +#: pages/Package_Maintenance_Guide.adoc:47 #, no-wrap msgid "Retrieve package sources" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:70 +#: pages/Package_Maintenance_Guide.adoc:50 #, no-wrap msgid "fedpkg sources\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:76 +#: pages/Package_Maintenance_Guide.adoc:56 msgid "" "This pulls any sources stored in the \"lookaside cache\" (see below for " "more). Steps like `fedpkg prep` and `fedpkg srpm` will do this if " @@ -177,13 +134,13 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:77 +#: pages/Package_Maintenance_Guide.adoc:57 #, no-wrap msgid "Make your changes to the package" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:82 +#: pages/Package_Maintenance_Guide.adoc:62 msgid "" "This is not an RPM packaging guide, so we'll assume you know what you're " "doing here. New sources and patches go in the working copy directory for " @@ -191,83 +148,83 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:83 +#: pages/Package_Maintenance_Guide.adoc:63 #, no-wrap msgid "Run the prep stage" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:85 +#: pages/Package_Maintenance_Guide.adoc:65 msgid "Extract source, apply patches etc. within the checkout directory:" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:87 +#: pages/Package_Maintenance_Guide.adoc:67 #, no-wrap msgid "fedpkg prep\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:91 +#: pages/Package_Maintenance_Guide.adoc:71 msgid "" "This is useful for making sure your patches apply cleanly, and inspecting " "the source tree if you need to do so." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:92 +#: pages/Package_Maintenance_Guide.adoc:72 #, no-wrap msgid "Do a local build of the current state" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:95 +#: pages/Package_Maintenance_Guide.adoc:75 #, no-wrap msgid "fedpkg local\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:100 +#: pages/Package_Maintenance_Guide.adoc:80 msgid "" "This is the simplest kind of test build, but it's usually cleaner and a " "better test to do a Mock or Koji scratch build (see below)." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:101 +#: pages/Package_Maintenance_Guide.adoc:81 #, no-wrap msgid "Do a mock build of the current state" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:104 +#: pages/Package_Maintenance_Guide.adoc:84 #, no-wrap msgid "fedpkg mockbuild\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:108 +#: pages/Package_Maintenance_Guide.adoc:88 msgid "" "This fires off a https://github.com/rpm-software-management/mock/wiki[Mock] " -"build, if you have Mock configured correctly. " -"https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock " -"to Test Package Builds] can help there." +"build, if you have Mock configured correctly. https://fedoraproject.org/" +"wiki/Using_Mock_to_test_package_builds[Using Mock to Test Package Builds] " +"can help there." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:109 +#: pages/Package_Maintenance_Guide.adoc:89 #, no-wrap msgid "Generate a .src.rpm from the current state" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:112 +#: pages/Package_Maintenance_Guide.adoc:92 #, no-wrap msgid "fedpkg srpm\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:118 +#: pages/Package_Maintenance_Guide.adoc:98 msgid "" "You can request a Koji _scratch build_ (a test build, which will not go to " "any repository) of the generated .src.rpm with the `koji build --scratch` " @@ -275,49 +232,50 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:119 +#: pages/Package_Maintenance_Guide.adoc:99 #, no-wrap msgid "Do a scratch build using Koji" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:122 -msgid "See xref:Using_the_Koji_Build_System#scratch_builds[Koji scratch builds]." +#: pages/Package_Maintenance_Guide.adoc:102 +msgid "" +"See xref:Using_the_Koji_Build_System#scratch_builds[Koji scratch builds]." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:123 +#: pages/Package_Maintenance_Guide.adoc:103 #, no-wrap msgid "Check changes you have made" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:126 +#: pages/Package_Maintenance_Guide.adoc:106 #, no-wrap msgid "fedpkg diff\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:131 +#: pages/Package_Maintenance_Guide.adoc:111 msgid "" "This is handy for making sure you did not touch something by mistake, or " "forget to bump the release, or forget to include a changelog." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:132 +#: pages/Package_Maintenance_Guide.adoc:112 #, no-wrap msgid "Run some checks (rpmlint) on your package" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:135 +#: pages/Package_Maintenance_Guide.adoc:115 #, no-wrap msgid "fedpkg lint\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:141 +#: pages/Package_Maintenance_Guide.adoc:121 msgid "" "If you want to whitelist some rpmlint errors and prevent them from " "appearing, you can create an rpmlint config file named " @@ -325,19 +283,19 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:142 +#: pages/Package_Maintenance_Guide.adoc:122 #, no-wrap msgid "Stage any small patches or new source files for commit" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:145 +#: pages/Package_Maintenance_Guide.adoc:125 #, no-wrap msgid "git add SOMEFILE\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:154 +#: pages/Package_Maintenance_Guide.adoc:134 msgid "" "Git does not consider all files in the working directory to be a part of the " "git repository by default (handy for keeping other files around that are " @@ -347,30 +305,31 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:155 +#: pages/Package_Maintenance_Guide.adoc:135 #, no-wrap msgid "Upload new source files to the lookaside cache" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:158 +#: pages/Package_Maintenance_Guide.adoc:138 #, no-wrap msgid "fedpkg new-sources\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:162 -msgid "WARNING: This will replace the current list of source files, not add to it." +#: pages/Package_Maintenance_Guide.adoc:142 +msgid "" +"WARNING: This will replace the current list of source files, not add to it." msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:165 +#: pages/Package_Maintenance_Guide.adoc:145 #, no-wrap msgid "fedpkg upload\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:175 +#: pages/Package_Maintenance_Guide.adoc:155 msgid "" "'Pristine' upstream sources (like release tarballs) and other larger source " "files are stored in the lookaside cache system, not committed directly to " @@ -381,7 +340,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:182 +#: pages/Package_Maintenance_Guide.adoc:162 msgid "" "`new-sources` 'starts from scratch', replacing all files currently in the " "lookaside cache. You will typically use this command for many packages with " @@ -391,19 +350,19 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:183 +#: pages/Package_Maintenance_Guide.adoc:163 #, no-wrap msgid "Switch to a different release branch" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:186 +#: pages/Package_Maintenance_Guide.adoc:167 #, no-wrap -msgid "fedpkg switch-branch \n" +msgid "fedpkg switch-branch \n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:191 +#: pages/Package_Maintenance_Guide.adoc:172 msgid "" "Each Fedora release has its own branch in each package repository so " "different builds can be sent to each release. See below for more details on " @@ -411,19 +370,19 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:192 +#: pages/Package_Maintenance_Guide.adoc:173 #, no-wrap msgid "Generate git changelog from package changelog" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:195 +#: pages/Package_Maintenance_Guide.adoc:176 #, no-wrap msgid "fedpkg clog\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:201 +#: pages/Package_Maintenance_Guide.adoc:182 msgid "" "This command extracts your package changelog entry to the file `clog`, so " "you can use it as the git changelog if you like. Some maintainers draw a " @@ -431,19 +390,19 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:202 +#: pages/Package_Maintenance_Guide.adoc:183 #, no-wrap msgid "Commit changes" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:205 +#: pages/Package_Maintenance_Guide.adoc:186 #, no-wrap msgid "fedpkg commit (-F clog) (-p) (-c)\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:210 +#: pages/Package_Maintenance_Guide.adoc:191 msgid "" "This behaves by default like `git commit -a`: It stages modified files and " "commits all at once, though it does not add files which git is not yet " @@ -451,7 +410,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:223 +#: pages/Package_Maintenance_Guide.adoc:204 msgid "" "This creates a sort of bundle, a 'commit', of your changes to the " "repository, with a unique identity and a changelog. Other maintainers — and " @@ -463,28 +422,27 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:227 +#: pages/Package_Maintenance_Guide.adoc:208 msgid "" "The `-F clog` parameter will use the `clog` file from the previous step as " "the changelog. `-p` will push (see below) at the same time as committing. " -"`-c` combines the clog and `commit -F clog` steps into one, if you like " -"that." +"`-c` combines the clog and `commit -F clog` steps into one, if you like that." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:228 +#: pages/Package_Maintenance_Guide.adoc:209 #, no-wrap msgid "Push changes" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:231 +#: pages/Package_Maintenance_Guide.adoc:212 #, no-wrap msgid "fedpkg push\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:238 +#: pages/Package_Maintenance_Guide.adoc:219 msgid "" "This sends all the new commits in your local working copy to the upstream " "server. If you are still learning the system, now is a good time to `fedpkg " @@ -493,26 +451,26 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:239 +#: pages/Package_Maintenance_Guide.adoc:220 #, no-wrap msgid "Do an 'official' build of the latest pushed changes" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:242 -#: ./pages/Package_Maintenance_Guide.adoc:247 +#: pages/Package_Maintenance_Guide.adoc:223 +#: pages/Package_Maintenance_Guide.adoc:228 #, no-wrap msgid "fedpkg build\n" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:244 +#: pages/Package_Maintenance_Guide.adoc:225 #, no-wrap msgid "Submit 'official' builds from a stream branch" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:254 +#: pages/Package_Maintenance_Guide.adoc:235 msgid "" "There is no difference in the command line to submit multiple builds from a " "stream branch. But you need to create a config file `package.cfg` in the " @@ -521,22 +479,22 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:258 +#: pages/Package_Maintenance_Guide.adoc:240 #, no-wrap msgid "" "[koji]\n" -"targets = f28 epel7\n" +"targets = f{MAJOROSVER} epel{MAJOREPELVER}\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:262 +#: pages/Package_Maintenance_Guide.adoc:245 msgid "" "This example shows when you execute the `build` command, `fedpkg` is able to " -"submit builds for releases, `f28` and `epel7`." +"submit builds for releases, `f{MAJOROSVER}` and `epel{MAJOREPELVER}`." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:270 +#: pages/Package_Maintenance_Guide.adoc:253 msgid "" "In practice, you are able to specify two shortcut names `fedora` and `epel` " "for convenience. `fedpkg` retrieves current active Fedora and EPEL releases " @@ -547,39 +505,39 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:271 +#: pages/Package_Maintenance_Guide.adoc:254 #, no-wrap msgid "Do a Container Layered Image Build" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:274 +#: pages/Package_Maintenance_Guide.adoc:257 #, no-wrap msgid "fedpkg container-build\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:277 +#: pages/Package_Maintenance_Guide.adoc:260 msgid "" -"See " -"https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service[Container " -"Layered Image Build] for details." +"See https://fedoraproject.org/wiki/Changes/" +"Layered_Docker_Image_Build_Service[Container Layered Image Build] for " +"details." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:278 +#: pages/Package_Maintenance_Guide.adoc:261 #, no-wrap msgid "Submit a package update for the latest build" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:281 +#: pages/Package_Maintenance_Guide.adoc:264 #, no-wrap msgid "fedpkg update\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:288 +#: pages/Package_Maintenance_Guide.adoc:271 msgid "" "This is the first point at which you might possibly cause real mess for a " "real user, so use it with caution. If you are following the example and " @@ -588,7 +546,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:295 +#: pages/Package_Maintenance_Guide.adoc:278 msgid "" "Unlike most of the above commands, this operates on the state you have " "pushed to git, not the local state. If you have issues make sure you have " @@ -596,27 +554,26 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:299 +#: pages/Package_Maintenance_Guide.adoc:282 msgid "" -"See " -"xref:Package_Update_Guide.adoc#updating_inter_dependent_packages[Updating " -"inter-dependent packages] if you are making inter-dependent changes to more " -"than one package." +"See xref:Package_Update_Guide." +"adoc#updating_inter_dependent_packages[Updating inter-dependent packages] if " +"you are making inter-dependent changes to more than one package." msgstr "" #. type: Title == -#: ./pages/Package_Maintenance_Guide.adoc:301 +#: pages/Package_Maintenance_Guide.adoc:284 #, no-wrap msgid "Typical fedpkg session" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:304 +#: pages/Package_Maintenance_Guide.adoc:287 msgid "A typical session may look like this:" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:316 +#: pages/Package_Maintenance_Guide.adoc:299 #, no-wrap msgid "" "fedpkg clone foo\n" @@ -624,8 +581,7 @@ msgid "" "fedpkg sources\n" "fedpkg new-sources foo-0.0.2.tar.bz2\n" "gedit foo.spec # change the required things in the specfile.\n" -" # rpmdev-bumpspec is useful for simple version " -"updates\n" +" # rpmdev-bumpspec is useful for simple version updates\n" "fedpkg mockbuild # check that the changes you made are correct\n" "fedpkg diff\n" "fedpkg lint\n" @@ -633,41 +589,40 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Package_Maintenance_Guide.adoc:319 +#: pages/Package_Maintenance_Guide.adoc:302 #, no-wrap msgid "Working with branches" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:323 +#: pages/Package_Maintenance_Guide.adoc:306 msgid "" "Each Fedora release is represented by a branch in the git repository. You " "can switch between them like this:" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:328 +#: pages/Package_Maintenance_Guide.adoc:312 #, no-wrap msgid "" -"fedpkg switch-branch f34\n" -"fedpkg switch-branch f33\n" +"fedpkg switch-branch f{MAJOROSVER}\n" +"fedpkg switch-branch f{PREVIOUSOSVER}\n" "fedpkg switch-branch rawhide\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:336 +#: pages/Package_Maintenance_Guide.adoc:320 msgid "" -"The `rawhide` branch is for " -"https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide]. You can maintain " -"each branch entirely separately, if you like, laboriously copying changes " -"between them (so long as you always stay within the " -"https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/[Updates Policy] " -"requirements). However, git provides us with several handy tools for " -"working with branches. Here's an example:" +"The `rawhide` branch is for https://fedoraproject.org/wiki/Releases/" +"Rawhide[Rawhide]. You can maintain each branch entirely separately, if you " +"like, laboriously copying changes between them (so long as you always stay " +"within the xref:fesco::Updates_Policy.adoc[Updates Policy] requirements). " +"However, git provides us with several handy tools for working with " +"branches. Here's an example:" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:347 +#: pages/Package_Maintenance_Guide.adoc:332 #, no-wrap msgid "" "fedpkg clone bzrtools\n" @@ -675,56 +630,56 @@ msgid "" "fedpkg new-sources bzrtools-2.2.tar.gz\n" "gedit bzrtools.spec\n" "fedpkg commit\n" -"fedpkg switch-branch f34\n" +"fedpkg switch-branch f{MAJOROSVER}\n" "git merge rawhide\n" "# for push into repo\n" "fedpkg push\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:358 +#: pages/Package_Maintenance_Guide.adoc:343 msgid "" -"This will _merge_ the changes from the `rawhide` branch to the `f34` " -"branch. Git aficionados may note this is a somewhat unusual workflow, but " +"This will _merge_ the changes from the `rawhide` branch to the `f{MAJOROSVER}" +"` branch. Git aficionados may note this is a somewhat unusual workflow, but " "it is appropriate to the context of package management. Remember, after " -"pushing to and building for a stable release or a " -"https://fedoraproject.org/wiki/Releases/Branched[Branched] release after " -"https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updates-testing-activation[updates-testing " -"activation], you will have to xref:Package_Update_Guide.adoc[submit an " -"update] before any other Fedora users will see your build." +"pushing to and building for a stable release or a https://fedoraproject.org/" +"wiki/Releases/Branched[Branched] release after xref:fesco::Updates_Policy." +"adoc#updates-testing-activation[updates-testing activation], you will have " +"to xref:Package_Update_Guide.adoc[submit an update] before any other Fedora " +"users will see your build." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:362 +#: pages/Package_Maintenance_Guide.adoc:347 msgid "" "Note that merges will only be sure to work cleanly so long as the branches " "have not previously diverged. That is, if you do this:" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:375 +#: pages/Package_Maintenance_Guide.adoc:361 #, no-wrap msgid "" "fedpkg clone bzrtools\n" "# Make some changes in the rawhide branch\n" "fedpkg commit\n" -"fedpkg switch-branch f34\n" -"# Make some changes in the f34 branch\n" +"fedpkg switch-branch f{MAJOROSVER}\n" +"# Make some changes in the f{MAJOROSVER} branch\n" "fedpkg commit\n" "fedpkg switch-branch rawhide\n" "# Make some more changes in the rawhide branch\n" "fedpkg commit\n" -"fedpkg switch-branch f34\n" +"fedpkg switch-branch f{MAJOROSVER}\n" "git merge rawhide\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:378 +#: pages/Package_Maintenance_Guide.adoc:364 msgid "you may encounter a _merge conflict_." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:385 +#: pages/Package_Maintenance_Guide.adoc:371 msgid "" "Remember that git is a _collaborative_ system, and used as such in Fedora " "package management. It is often the case that you must consider changes " @@ -733,23 +688,23 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:387 +#: pages/Package_Maintenance_Guide.adoc:373 #, no-wrap msgid "Resolving merge conflicts" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:393 +#: pages/Package_Maintenance_Guide.adoc:379 msgid "" "This is a large topic and somewhat beyond the scope of this guide, but we " -"can give basic pointers. There are other good references in the " -"http://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging[git " -"book] and at " -"https://help.github.com/articles/resolving-a-merge-conflict-from-the-command-line[GitHub]." +"can give basic pointers. There are other good references in the http://git-" +"scm.com/book/en/Git-Branching-Basic-Branching-and-Merging[Git book] and at " +"https://help.github.com/articles/resolving-a-merge-conflict-from-the-command-" +"line[GitHub]." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:404 +#: pages/Package_Maintenance_Guide.adoc:390 msgid "" "When you merge and a conflict occurs, you can edit the files that have " "conflicts. Remove the conflict markers in the files and merge the changes " @@ -761,13 +716,13 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:406 +#: pages/Package_Maintenance_Guide.adoc:392 #, no-wrap msgid "Using git mergetool to resolve conflicts" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:411 +#: pages/Package_Maintenance_Guide.adoc:397 msgid "" "Git provides a graphical diff program to help resolve conflicts. This can " "be handy for visualizing what changes have occurred and dealing with them as " @@ -775,7 +730,7 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:422 +#: pages/Package_Maintenance_Guide.adoc:408 #, no-wrap msgid "" "git config --global merge.tool meld\n" @@ -790,50 +745,41 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Package_Maintenance_Guide.adoc:425 +#: pages/Package_Maintenance_Guide.adoc:411 #, no-wrap -msgid "Requesting special dist tags" +msgid "Multi-package updates" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:432 +#: pages/Package_Maintenance_Guide.adoc:419 msgid "" "When a change to a package affects a large number of dependencies (e.g. all " "perl, python, ruby or ghc packages), requiring them to be rebuilt, it may be " -"better to initially do the builds in a special repository, so that there is " -"less disruption in Rawhide." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:441 -msgid "" -"If you think you have an update that falls under this case you can request a " -"special dist tag by filing a https://pagure.io/releng/new_issue[release " -"engineering ticket]. Someone from https://docs.pagure.org/releng/[release " -"engineering] will likely want to discuss your needs to make sure this is " -"really an appropriate case (it's OK ask if you aren't sure) and that you " -"get what you need." +"better to initially do the builds in a _side tag_, so that there is less " +"disruption in Rawhide. See xref:Package_Update_Guide." +"adoc#multiple_packages[Package Update Guide, section Multi-package updates] " +"for details." msgstr "" #. type: Title == -#: ./pages/Package_Maintenance_Guide.adoc:443 +#: pages/Package_Maintenance_Guide.adoc:421 #, no-wrap msgid "Using fedpkg anonymously" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:446 +#: pages/Package_Maintenance_Guide.adoc:424 msgid "You can use fedpkg like this:" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:449 +#: pages/Package_Maintenance_Guide.adoc:427 #, no-wrap msgid "fedpkg clone --anonymous\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:456 +#: pages/Package_Maintenance_Guide.adoc:434 msgid "" "to check out a package without requiring identification. Obviously, you " "will not be able to push any changes to this repository, but it is useful " @@ -842,7 +788,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:464 +#: pages/Package_Maintenance_Guide.adoc:442 msgid "" "If the intention is to submit changes to a Fedora developer, the package " "repository can be forked and a pull request submitted. Forking is done in " @@ -853,48 +799,47 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:478 +#: pages/Package_Maintenance_Guide.adoc:459 #, no-wrap msgid "" "fedpkg clone --anonymous forks/my-username/rpms/somepackage\n" "cd somepackage\n" "gedit somepackage.spec # change the required things in the specfile.\n" -" # rpmdev-bumpspec is useful for simple version " -"updates\n" -"spectool -g somepackage.spec # download the referenced sources to local " -"machine\n" -" # fedpkg new-sources cannot be performed " -"anonymously, that is left\n" -" # for the maintainer to do after the pull " -"request has been merged\n" +" # rpmdev-bumpspec is useful for simple version updates\n" +"spectool -g somepackage.spec # download the referenced sources to local machine\n" +" # fedpkg new-sources cannot be performed anonymously, that is left\n" +" # for the maintainer to do after the pull request has been merged\n" "fedpkg mockbuild # check that the changes you made are correct\n" "fedpkg diff\n" "fedpkg lint\n" "git checkout -b my-branch # create a branch to use in the pull request\n" -"fedpkg commit -p -c # commit and push in one go\n" +"git status\n" +"git add .\n" +"git commit\n" +"git push -u origin my-branch\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:483 +#: pages/Package_Maintenance_Guide.adoc:464 msgid "" "Afterwards, a pull request from `my-branch` to the main package repository " "can be created in the _src.fedoraproject.org_ web ui." msgstr "" #. type: Title == -#: ./pages/Package_Maintenance_Guide.adoc:485 +#: pages/Package_Maintenance_Guide.adoc:466 #, no-wrap msgid "Tips and tricks" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:488 +#: pages/Package_Maintenance_Guide.adoc:469 #, no-wrap msgid "Local branch names" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:494 +#: pages/Package_Maintenance_Guide.adoc:475 msgid "" "If you use git commands to branch and checkout directly, you can define " "whatever local branch names you want. If you use `fedpkg switch-branch`, it " @@ -902,40 +847,41 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:496 +#: pages/Package_Maintenance_Guide.adoc:477 #, no-wrap msgid "Current branch and state in shell prompt" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:502 +#: pages/Package_Maintenance_Guide.adoc:483 msgid "" "It is often helpful to know what branch you are working on at a glance. You " -"can add this information to your bash prompt with the information " -"https://fedoraproject.org/wiki/Git_quick_reference?rd=Git_Quickref#Display_current_branch_in_bash[here]." +"can add this information to your bash prompt with the information https://" +"fedoraproject.org/wiki/Git_quick_reference?" +"rd=Git_Quickref#Display_current_branch_in_bash[here]." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:504 +#: pages/Package_Maintenance_Guide.adoc:485 #, no-wrap msgid "Importing a .src.rpm to update" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:516 +#: pages/Package_Maintenance_Guide.adoc:497 msgid "" "The command usually used to initially populate a git package repository from " -"a .src.rpm that has been through the " -"xref:Package_Review_Process.adoc[Package Review Process] can also be used to " -"update a normal working copy, if you have an old-school packaging process to " -"which you are particularly attached. Just run `fedpkg import file.src.rpm` " -"and it will upload new tarballs into lookaside cache, update a working copy " -"of the last version found in git, and commit all changes. `fedpkg import " -"--help` documents some other parameters it can accept." +"a .src.rpm that has been through the xref:Package_Review_Process." +"adoc[Package Review Process] can also be used to update a normal working " +"copy, if you have an old-school packaging process to which you are " +"particularly attached. Just run `fedpkg import file.src.rpm` and it will " +"upload new tarballs into lookaside cache, update a working copy of the last " +"version found in git, and commit all changes. `fedpkg import --help` " +"documents some other parameters it can accept." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:520 +#: pages/Package_Maintenance_Guide.adoc:501 msgid "" "This approach makes it harder to verify that your changes are safe and do " "not overwrite changes made to the package by others. For this reason, its " @@ -943,20 +889,21 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:522 +#: pages/Package_Maintenance_Guide.adoc:503 #, no-wrap msgid "Making changes on an older branch without breaking the upgrade path" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:527 +#: pages/Package_Maintenance_Guide.adoc:508 msgid "" -"Here is the scenario: You have built your package successfully on the `f34` " -"branch, but there is a problem keeping your package from building on `last`." +"Here is the scenario: You have built your package successfully on the " +"`f{MAJOROSVER}` branch, but there is a problem keeping your package from " +"building on `last`." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:534 +#: pages/Package_Maintenance_Guide.adoc:515 msgid "" "Solution: Make your changes in the branch and then add a digit to the very " "right of the release tag. There is no need to change the release in the " @@ -965,7 +912,7 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:539 +#: pages/Package_Maintenance_Guide.adoc:520 #, no-wrap msgid "" "Name: foo\n" @@ -974,7 +921,7 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:543 +#: pages/Package_Maintenance_Guide.adoc:524 #, no-wrap msgid "" "Name: foo\n" @@ -983,34 +930,33 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:547 +#: pages/Package_Maintenance_Guide.adoc:528 msgid "" -"Then tag and build as usual. This approach was initially discussed " -"https://www.redhat.com/archives/fedora-extras-list/2006-May/msg00083.html[in " -"this mailing list thread]." +"Then tag and build as usual. This approach was initially discussed https://" +"www.redhat.com/archives/fedora-extras-list/2006-May/msg00083.html[in this " +"mailing list thread]." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:549 +#: pages/Package_Maintenance_Guide.adoc:530 #, no-wrap msgid "Removing a package build pending for Rawhide or Branched" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:562 +#: pages/Package_Maintenance_Guide.adoc:543 msgid "" "From time to time you may want to remove a package build you submitted to " "Rawhide or to Branched prior to the Alpha freeze (both cases where the build " -"would usually go out to the main " -"https://docs.fedoraproject.org/en-US/quick-docs/repositories/[repository] " -"without further gating). This could happen in a situation where a bug or " -"issue is found in your package that will be resolved upstream in the next " -"release, or you realize you made a significant mistake in the build that " -"cannot easily be corrected." +"would usually go out to the main xref:quick-docs::repositories." +"adoc[repository] without further gating). This could happen in a situation " +"where a bug or issue is found in your package that will be resolved upstream " +"in the next release, or you realize you made a significant mistake in the " +"build that cannot easily be corrected." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:567 +#: pages/Package_Maintenance_Guide.adoc:548 msgid "" "This should only be done on the same day of the build, before it is included " "in a compose. If your build was already included in a compose you must not " @@ -1019,58 +965,58 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:569 +#: pages/Package_Maintenance_Guide.adoc:550 msgid "" -"You can remove the package by using " -"https://fedoraproject.org/wiki/Koji[Koji]:" +"You can remove the package by using https://fedoraproject.org/wiki/" +"Koji[Koji]:" msgstr "" #. type: delimited block . -#: ./pages/Package_Maintenance_Guide.adoc:572 +#: pages/Package_Maintenance_Guide.adoc:554 #, no-wrap -msgid "koji untag-pkg f35 foo-1.1.3-1.fc35\n" +msgid "koji untag-pkg f{NEXTOSVER} foo-1.1.3-1.fc{NEXTOSVER}\n" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:576 +#: pages/Package_Maintenance_Guide.adoc:558 msgid "" -"where `foo-1.1.3-1.fc35` is replaced with the name of your package build. " -"See `koji help` or xref:Using_the_Koji_Build_System.adoc[Using the Koji " -"Build System] for more information." +"where `foo-1.1.3-1.fc{NEXTOSVER}` is replaced with the name of your package " +"build. See `koji help` or xref:Using_the_Koji_Build_System.adoc[Using the " +"Koji Build System] for more information." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:578 +#: pages/Package_Maintenance_Guide.adoc:560 #, no-wrap msgid "ssh fingerprint" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:583 +#: pages/Package_Maintenance_Guide.adoc:565 msgid "" -"The recommended option is to include `VerifyHostKeyDNS yes` in your " -"`~/.ssh/config` file. This will result in using DNS to check that the key " -"is correct." +"The recommended option is to include `VerifyHostKeyDNS yes` in your `~/.ssh/" +"config` file. This will result in using DNS to check that the key is " +"correct." msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:590 +#: pages/Package_Maintenance_Guide.adoc:572 msgid "" -"But you can also manually check against the list of keys at " -"https://admin.fedoraproject.org[https://admin.fedoraproject.org]. The " -"strings there are what ends up in your `~/.ssh/known_hosts` file. So you " -"can accept the fingerprint when prompted and then check that the correct " -"string for src.fedoraproject.org ended up in your `~/.ssh/known_hosts` file." +"But you can also manually check against the list of keys at https://admin." +"fedoraproject.org[https://admin.fedoraproject.org]. The strings there are " +"what ends up in your `~/.ssh/known_hosts` file. So you can accept the " +"fingerprint when prompted and then check that the correct string for src." +"fedoraproject.org ended up in your `~/.ssh/known_hosts` file." msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:592 +#: pages/Package_Maintenance_Guide.adoc:574 #, no-wrap msgid "Problems connecting to the repository" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:601 +#: pages/Package_Maintenance_Guide.adoc:583 msgid "" "The `fedpkg` tool clones repositories using the ssh:// protocol, so this " "should not be a problem normally (as long as you have your ssh key). If you " @@ -1080,13 +1026,13 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Maintenance_Guide.adoc:603 +#: pages/Package_Maintenance_Guide.adoc:585 #, no-wrap msgid "It builds here, why doesn't it build there?" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:617 +#: pages/Package_Maintenance_Guide.adoc:599 msgid "" "Is your package building locally — even with Mock, even as a scratch build! " "— but not when you run `fedpkg build`? Before you get too frustrated, " @@ -1101,32 +1047,40 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Package_Maintenance_Guide.adoc:618 +#: pages/Package_Maintenance_Guide.adoc:600 #, no-wrap msgid "References" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:621 +#: pages/Package_Maintenance_Guide.adoc:603 msgid "https://src.fedoraproject.org/" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:622 -msgid "https://fedoraproject.org/wiki/Infrastructure/Kerberos[Infrastructure/Kerberos]" +#: pages/Package_Maintenance_Guide.adoc:604 +msgid "" +"https://fedoraproject.org/wiki/Infrastructure/Kerberos[Infrastructure/" +"Kerberos]" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:623 -msgid "https://fedoraproject.org/wiki/Packaging_tricks?rd=PackageMaintainers/PackagingTricks[PackageMaintainers/PackagingTricks]" +#: pages/Package_Maintenance_Guide.adoc:605 +msgid "" +"https://fedoraproject.org/wiki/Packaging_tricks?rd=PackageMaintainers/" +"PackagingTricks[PackageMaintainers/PackagingTricks]" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:624 -msgid "https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle?rd=Policy_for_package_lifecycle[Fedora_Release_Life_Cycle]" +#: pages/Package_Maintenance_Guide.adoc:606 +msgid "" +"https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle?" +"rd=Policy_for_package_lifecycle[Fedora_Release_Life_Cycle]" msgstr "" #. type: Plain text -#: ./pages/Package_Maintenance_Guide.adoc:624 -msgid "https://fedoraproject.org/wiki/Infrastructure/VersionControl/dist-git[Infrastructure/VersionControl/dist-git]" +#: pages/Package_Maintenance_Guide.adoc:606 +msgid "" +"https://fedoraproject.org/wiki/Infrastructure/VersionControl/dist-" +"git[Infrastructure/VersionControl/dist-git]" msgstr "" diff --git a/po/fr/master/pages/Package_Orphaning_Process.po b/po/fr/master/pages/Package_Orphaning_Process.po index 12db82b..b7690b7 100644 --- a/po/fr/master/pages/Package_Orphaning_Process.po +++ b/po/fr/master/pages/Package_Orphaning_Process.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-01-24 21:56+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,138 +16,151 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers #. type: Title = -#: ./pages/Package_Orphaning_Process.adoc:3 +#: pages/Package_Orphaning_Process.adoc:1 #, no-wrap msgid "Package Orphaning Process" msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:8 +#: pages/Package_Orphaning_Process.adoc:5 msgid "" "This page contains instructions for working with orphan packages as " -"specified in " -"https://fedoraproject.org/wiki/Policy_for_Orphan_and_Retired_Packages[Policy " +"specified in xref:fesco::Policy_for_orphan_and_retired_packages.adoc[Policy " "for Orphan and Retired Packages]." msgstr "" #. type: Title == -#: ./pages/Package_Orphaning_Process.adoc:10 +#: pages/Package_Orphaning_Process.adoc:7 #, no-wrap msgid "Orphaning Procedure" msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:17 +#: pages/Package_Orphaning_Process.adoc:11 msgid "" -"If the package has co-maintainers, contact them to ask whether one of them " -"wants to take over ownership of the package. This step is optional. If no " -"co-maintainer can be found to take over the package, the package should be " -"given to the `orphan` user." +"(Optional) If the package has co-maintainers, contact them to ask whether " +"one of them wants to take over ownership of the package." msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:22 +#: pages/Package_Orphaning_Process.adoc:16 msgid "" "The current list of maintainers can be found in the _Users & Groups_ tab of " "the setting for the package repo. The URL will look something like this: " -"`https://src.fedoraproject.org/rpms/PACKAGE_NAME/settings.`" +"`\\https://src.fedoraproject.org/rpms/PACKAGE_NAME/settings.`" msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:28 +#: pages/Package_Orphaning_Process.adoc:19 msgid "" -"After the first step is finished, go again to the settings tab for your " -"package's Pagure repository. Navigate down to the _Give Project_ section " -"and _give_ the project to the new maintainer or the `orphan` user (in case " -"no new maintainer was selected)." +"If somebody wants to take the package, skip the rest of the procedure and " +"give it to them as follows:" msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:32 +#: pages/Package_Orphaning_Process.adoc:22 msgid "" -"For completeness, under the _Users and Groups_ section, remove yourself from " -"the list as well." +"Remove yourself under _Users and Groups_, unless you want to remain as a co-" +"maintainer." msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:35 +#: pages/Package_Orphaning_Process.adoc:25 msgid "" -"Also reset your watch status if you do not want to be CC'ed on new package " -"bugs." +"Reset your watch status, unless you still want to be notified about new " +"package bugs." msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:40 +#: pages/Package_Orphaning_Process.adoc:27 msgid "" -"If the package was given to the `orphan` user, announce on the " -"https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel " -"mailing list] which package you orphaned, so that others have a chance to " -"take over as maintainer." +"Click the _✋ Orphan_ button on the left, fill requested information, and " +"click _Update_." msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:43 +#: pages/Package_Orphaning_Process.adoc:31 msgid "" -"Reassign the package's tickets to the orphan user, " -"`extras-orphan@fedoraproject.org`." +"Announce on the https://lists.fedoraproject.org/archives/list/devel@lists." +"fedoraproject.org/[devel mailing list] which package you orphaned, so that " +"others have a chance to take over as maintainer." msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:47 +#: pages/Package_Orphaning_Process.adoc:37 msgid "" -"After completing these steps, the package is orphaned. If nobody takes over " -"the orphan package in six weeks, it is automatically retired by " -"https://docs.pagure.org/releng/[Release Engineering]." +"After completing these steps, the package is orphaned. Package's open bug " +"reports are automatically assigned to the orphan user, `extras-" +"orphan@fedoraproject.org`. If nobody takes over the orphan package in six " +"weeks, it is automatically retired by https://docs.pagure.org/releng/" +"[Release Engineering]." msgstr "" #. type: Title == -#: ./pages/Package_Orphaning_Process.adoc:49 +#: pages/Package_Orphaning_Process.adoc:39 #, no-wrap msgid "Claiming Ownership of an Orphaned Package" msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:53 +#: pages/Package_Orphaning_Process.adoc:44 msgid "" -"Check why the package was orphaned by looking for the email at " -"https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel]." +"Ownership of an orphaned package can be claimed by any interested packager " +"at any time. They then become responsible for the package." msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:55 +#: pages/Package_Orphaning_Process.adoc:49 msgid "" -"Announce on " -"https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel] " -"which packages you want to take over." +"Check why the package was orphaned by checking the note on the left menu of " +"the package's main page at https://src.fedoraproject.org/[Package Sources], " +"and looking for the email at https://lists.fedoraproject.org/archives/list/" +"devel@lists.fedoraproject.org/[devel]." msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:63 +#: pages/Package_Orphaning_Process.adoc:52 msgid "" -"Log in to https://src.fedoraproject.org/[src.fedoraproject.org]. On the " -"page with the orphaned package, click the _✋ Take_ button in the left " -"column. (If the option doesn't work for you, " -"https://pagure.io/releng/new_issue?template=package_unorphan&title=Unorphan%20%3Cpkgname%3E[submit " -"a ticket to the Release Engineering team], stating which package you want to " -"claim and that this option didn't work.)" +"Announce on https://lists.fedoraproject.org/archives/list/devel@lists." +"fedoraproject.org/[devel] which packages you want to take over." msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:65 -msgid "Reassign and claim all open bug reports for the package in Bugzilla." +#: pages/Package_Orphaning_Process.adoc:60 +msgid "" +"Log in to https://src.fedoraproject.org/[Package Sources]. On the page with " +"the orphaned package, click the _✋ Take_ button in the left column. If the " +"button does not work, https://pagure.io/releng/new_issue?" +"template=package_unorphan&title=Unorphan%20%3Cpkgname%3E[submit a ticket to " +"the Release Engineering team], stating which package you want to claim and " +"that the button did not work." +msgstr "" + +#. type: Plain text +#: pages/Package_Orphaning_Process.adoc:62 +msgid "" +"All open bug reports for the package in Bugzilla are automatically " +"reassigned to you." +msgstr "" + +#. type: Plain text +#: pages/Package_Orphaning_Process.adoc:66 +msgid "" +"If you are not in the packager group yet, but want to claim ownership of an " +"orphaned package, you must xref:How_to_Get_Sponsored_into_the_Packager_Group." +"adoc[Get Sponsored into the Packager Group] first." msgstr "" #. type: Title == -#: ./pages/Package_Orphaning_Process.adoc:67 +#: pages/Package_Orphaning_Process.adoc:68 #, no-wrap msgid "Lists of Orphan and Retired Packages" msgstr "" #. type: Plain text -#: ./pages/Package_Orphaning_Process.adoc:69 +#: pages/Package_Orphaning_Process.adoc:70 msgid "" -"https://src.fedoraproject.org/user/orphan[A list of currently orphaned " -"and/or retired packages]" +"https://packager-dashboard.fedoraproject.org/user/orphan[A list of currently " +"orphaned and/or retired packages]" msgstr "" diff --git a/po/fr/master/pages/Package_Renaming_Process.po b/po/fr/master/pages/Package_Renaming_Process.po index c43f781..66200ff 100644 --- a/po/fr/master/pages/Package_Renaming_Process.po +++ b/po/fr/master/pages/Package_Renaming_Process.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-01-04 22:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,15 +16,14 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Package_Renaming_Process #. type: Title = -#: ./pages/Package_Renaming_Process.adoc:3 +#: pages/Package_Renaming_Process.adoc:1 #, no-wrap msgid "Package Renaming Process" msgstr "" #. type: Plain text -#: ./pages/Package_Renaming_Process.adoc:10 +#: pages/Package_Renaming_Process.adoc:7 msgid "" "For a variety of reasons it may become necessary to rename a package in " "Fedora. The goal of this page is to outline the process that must be " @@ -32,13 +31,13 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Package_Renaming_Process.adoc:12 +#: pages/Package_Renaming_Process.adoc:9 #, no-wrap msgid "Re-review required" msgstr "" #. type: Plain text -#: ./pages/Package_Renaming_Process.adoc:19 +#: pages/Package_Renaming_Process.adoc:16 msgid "" "When you wish to rename a package, you *MUST* request a re-review of your " "package through the xref:Package_Review_Process.adoc[Package Review " @@ -48,23 +47,23 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Renaming_Process.adoc:24 +#: pages/Package_Renaming_Process.adoc:21 msgid "" "The reviewer of the package *MUST* explicitly acknowledge this fact, and " -"check the package for the proper Obsoletes and Provides (see " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#_renamingreplacing_existing_packages[Naming " -"Guidelines] for more information.) They *MUST* document in the review " -"request that they have done so." +"check the package for the proper Obsoletes and Provides (see xref:packaging-" +"guidelines::index.adoc#renaming-or-replacing-existing-packages[relevant " +"Packaging Guidelines] for more information.) They *MUST* document in the " +"review request that they have done so." msgstr "" #. type: Title == -#: ./pages/Package_Renaming_Process.adoc:26 +#: pages/Package_Renaming_Process.adoc:23 #, no-wrap msgid "After the review" msgstr "" #. type: Plain text -#: ./pages/Package_Renaming_Process.adoc:35 +#: pages/Package_Renaming_Process.adoc:32 msgid "" "After the review is completed, and is satisfactory (for the avoidance of " "doubt, the lack of a clean upgrade path for users of the package in the form " @@ -73,9 +72,9 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Renaming_Process.adoc:37 +#: pages/Package_Renaming_Process.adoc:34 msgid "" -"After the new package is imported into git, you can follow the " -"xref:Package_Retirement_Process.adoc[Package Retirement Process] for the old " +"After the new package is imported into git, you can follow the xref:" +"Package_Retirement_Process.adoc[Package Retirement Process] for the old " "package." msgstr "" diff --git a/po/fr/master/pages/Package_Retirement_Process.po b/po/fr/master/pages/Package_Retirement_Process.po index 95bfa9e..f20557f 100644 --- a/po/fr/master/pages/Package_Retirement_Process.po +++ b/po/fr/master/pages/Package_Retirement_Process.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-06-02 22:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,84 +16,85 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life #. type: Title = -#: ./pages/Package_Retirement_Process.adoc:3 +#: pages/Package_Retirement_Process.adoc:3 #, no-wrap msgid "Package Retirement Process" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:10 +#: pages/Package_Retirement_Process.adoc:11 msgid "" "When a package reaches the end of its useful life, the Package Retirement " "Process lets other people — and automated processes! — know both not to " -"expect any more releases, and why it was removed. The process is governed by " -"https://fedoraproject.org/wiki/Policy_for_Orphan_and_Retired_Packages[Policy " -"for Orphan and Retired Packages]." +"expect any more releases, and why it was removed. The process is governed " +"by xref:fesco::Policy_for_orphan_and_retired_packages.adoc[Policy for Orphan " +"and Retired Packages]." msgstr "" #. type: Title == -#: ./pages/Package_Retirement_Process.adoc:12 +#: pages/Package_Retirement_Process.adoc:13 #, no-wrap msgid "What can be retired" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:15 +#: pages/Package_Retirement_Process.adoc:16 msgid "Packages can normally only be retired in the following branches:" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:17 +#: pages/Package_Retirement_Process.adoc:18 msgid "Branched (until the Final Freeze)" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:18 +#: pages/Package_Retirement_Process.adoc:19 msgid "Rawhide" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:19 -msgid "EPEL branches (epel7, epel8)" +#: pages/Package_Retirement_Process.adoc:23 +msgid "" +"EPEL branches (`epel7`, `epel8`, `epel9`, and the corresponding `-next` " +"branches) - see xref:epel::epel-policy-retirement.adoc/[EPEL Retirement " +"Policy] for additional requirements" msgstr "" #. type: Title == -#: ./pages/Package_Retirement_Process.adoc:20 +#: pages/Package_Retirement_Process.adoc:24 #, no-wrap msgid "Procedure" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:23 +#: pages/Package_Retirement_Process.adoc:27 msgid "Please execute the following steps in the order indicated." msgstr "" #. type: Title === -#: ./pages/Package_Retirement_Process.adoc:24 +#: pages/Package_Retirement_Process.adoc:28 #, no-wrap msgid "RPM" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:29 +#: pages/Package_Retirement_Process.adoc:33 msgid "" "If the package is being replaced by some other package, ensure that the " "`Obsoletes`/`Provides` tags are properly set by the new package as specified " -"in " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages[Renaming/Replacing " -"Guidelines]." +"in xref:packaging-guidelines::index.adoc#renaming-or-replacing-existing-" +"packages[Renaming/Replacing Guidelines]." msgstr "" #. type: Title === -#: ./pages/Package_Retirement_Process.adoc:30 +#: pages/Package_Retirement_Process.adoc:34 #, no-wrap msgid "Git" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:37 +#: pages/Package_Retirement_Process.adoc:41 msgid "" "Run `fedpkg retire DESCRIPTION` in Fedora branches Rawhide and Branched (if " "it exists at the moment) and all EPEL branches (if applicable). " @@ -102,21 +103,21 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:41 +#: pages/Package_Retirement_Process.adoc:45 msgid "" -"The command will remove all files from the branch, add a file name " -"`dead.package` containing the description and push the changes." +"The command will remove all files from the branch, add a file name `dead." +"package` containing the description and push the changes." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:44 +#: pages/Package_Retirement_Process.adoc:48 msgid "" "Do not run the command in any supported or end-of-life Fedora release " "branch. Packages must not be retired from stable releases." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:50 +#: pages/Package_Retirement_Process.adoc:54 msgid "" "Start retiring from the oldest branch, i.e. retire on Branched before you " "retire on Rawhide. If you retire Rawhide before Branched, it will still " @@ -125,53 +126,39 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Retirement_Process.adoc:51 +#: pages/Package_Retirement_Process.adoc:55 #, no-wrap msgid "Comps" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:54 +#: pages/Package_Retirement_Process.adoc:58 msgid "" -"Remove the package from " -"https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups[comps] " -"if it is listed." +"Remove the package from https://fedoraproject.org/wiki/" +"How_to_use_and_edit_comps.xml_for_package_groups[comps] if it is listed." msgstr "" #. type: Title === -#: ./pages/Package_Retirement_Process.adoc:55 +#: pages/Package_Retirement_Process.adoc:59 #, no-wrap msgid "Spins" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:58 +#: pages/Package_Retirement_Process.adoc:62 msgid "" "Remove the package from any https://pagure.io/fedora-kickstarts[spin " "kickstart file]." msgstr "" #. type: Title === -#: ./pages/Package_Retirement_Process.adoc:60 -#, no-wrap -msgid "Upstream Release Monitoring" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:63 -msgid "" -"Remove the package from xref:Upstream_release_monitoring.adco[Upstream " -"release monitoring] if it is listed." -msgstr "" - -#. type: Title === -#: ./pages/Package_Retirement_Process.adoc:64 +#: pages/Package_Retirement_Process.adoc:63 #, no-wrap msgid "Koji" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:70 +#: pages/Package_Retirement_Process.adoc:69 msgid "" "To keep retired packages from being pushed to the mirrors, they need to be " "blocked in Koji. This will happen automatically during the next compose " @@ -179,31 +166,27 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:78 +#: pages/Package_Retirement_Process.adoc:77 msgid "" -"You can check whether a package is blocked in koji with `koji list-pkgs " -"--show-blocked`. There should an entry with `[BLOCKED]` for each branch the " +"You can check whether a package is blocked in koji with `koji list-pkgs --" +"show-blocked`. There should an entry with `[BLOCKED]` for each branch the " "package was retired in. It is enough for a package to be blocked in an " "older tag to be also blocked in a newer tag due to inheritance. Example " "output:" msgstr "" #. type: delimited block . -#: ./pages/Package_Retirement_Process.adoc:84 +#: pages/Package_Retirement_Process.adoc:84 #, no-wrap msgid "" -"$ koji list-pkgs --show-blocked --tag f21 --package curry " -"\n" -"Package Tag Extra Arches Owner " -"\n" -"----------------------- ----------------------- ---------------- " -"---------------\n" -"curry f20 gemi " -"[BLOCKED]\n" +"$ koji list-pkgs --show-blocked --tag f{MAJOROSVER} --package curry\n" +"Package Tag Extra Arches Owner\n" +"----------------------- ----------------------- ---------------- ---------------\n" +"curry f{PREVIOUSOSVER} gemi [BLOCKED]\n" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:94 +#: pages/Package_Retirement_Process.adoc:94 msgid "" "Please wait for two days to allow for a compose to happen and mirrors to be " "updated. If the package is not blocked automatically after two days, please " @@ -214,45 +197,47 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Package_Retirement_Process.adoc:95 +#: pages/Package_Retirement_Process.adoc:95 #, no-wrap msgid "EPEL" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:99 -msgid "The retirement process can be used for EPEL as well with one difference:" +#: pages/Package_Retirement_Process.adoc:99 +msgid "" +"The retirement process can be used for EPEL as well with one difference:" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:102 +#: pages/Package_Retirement_Process.adoc:102 msgid "" "You can remove the package from any EPEL branch whether or not it has been " "released." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:106 +#: pages/Package_Retirement_Process.adoc:107 msgid "" -"For example, if your package has been added to base RHEL in RHEL-6.4 then " -"perform the steps above but use the `el6` branch instead of `rawhide`." +"For example, if your package has been added to base RHEL in RHEL-" +"{MAJOREPELVER}.4 then perform the steps above but use the `el{MAJOREPELVER}` " +"branch instead of `rawhide`." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:109 +#: pages/Package_Retirement_Process.adoc:110 msgid "" "When you need to add package from EPEL to any RHEL release, only retire EPEL " "branch when package is released in that RHEL release." msgstr "" #. type: Title == -#: ./pages/Package_Retirement_Process.adoc:111 +#: pages/Package_Retirement_Process.adoc:112 #, no-wrap msgid "Claiming Ownership of a Retired Package" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:122 +#: pages/Package_Retirement_Process.adoc:123 msgid "" "If you really want to maintain a retired package, you need to be aware that " "if upstream is dead, fixing release critical bugs, etc becomes your " @@ -264,64 +249,65 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:128 +#: pages/Package_Retirement_Process.adoc:129 msgid "" "See if you can figure out why the package was retired including searching " -"for information about orphaned packages on " -"https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel " -"mailing list] or emailing the former maintainer. You can also check " -"`dead.package` in the SCM (url like: " -"https://src.fedoraproject.org/rpms/system-config-network/blob/rawhide/f/dead.package[https://src.fedoraproject.org/rpms/**package_name_here**/blob/rawhide/f/dead.package])" +"for information about orphaned packages on https://lists.fedoraproject.org/" +"archives/list/devel@lists.fedoraproject.org/[devel mailing list] or emailing " +"the former maintainer. You can also check `dead.package` in the SCM (url " +"like: https://src.fedoraproject.org/rpms/system-config-network/blob/rawhide/" +"f/dead.package[https://src.fedoraproject.org/rpms/**package_name_here**/blob/" +"rawhide/f/dead.package])" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:131 +#: pages/Package_Retirement_Process.adoc:132 msgid "" -"Announce on " -"https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel] " -"which packages you would like to become the owner of." +"Announce on https://lists.fedoraproject.org/archives/list/devel@lists." +"fedoraproject.org/[devel] which packages you would like to become the owner " +"of." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:141 +#: pages/Package_Retirement_Process.adoc:142 msgid "" "Retired Fedora packages (rawhide branch retired) require a re-review if they " "are retired for more than eight weeks or if there is no previous review of " "the package. Submit a review request (a new bugzilla ticket) and have the " -"package approved by a reviewer as if it were new to Fedora. See the " -"xref:Package_Review_Process.adoc[Package Review Process] for more " -"information. To unretire a EPEL branch if the package is still in Fedora, " -"no re-review is required." +"package approved by a reviewer as if it were new to Fedora. See the xref:" +"Package_Review_Process.adoc[Package Review Process] for more information. " +"To unretire a EPEL branch if the package is still in Fedora, no re-review is " +"required." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:151 +#: pages/Package_Retirement_Process.adoc:152 msgid "" -"Request unretirement by filing a " -"https://pagure.io/releng/new_issue?template=package_unretirement&title=Unretire%20%3Cpkgname%3E[releng " +"Request unretirement by filing a https://pagure.io/releng/new_issue?" +"template=package_unretirement&title=Unretire%20%3Cpkgname%3E[releng " "ticket]. Specify all branches that need to be un-retired (including " "`rawhide` for Rawhide, unless it is for EPEL only) and include the link to " -"re-review. In this ticket, request that the " -"https://docs.pagure.org/releng/[Release Engineering team] unblock the " -"package for the releases that the package should be un-retired for. In this " -"request, clearly specify which branches should be unblocked." +"re-review. In this ticket, request that the https://docs.pagure.org/releng/" +"[Release Engineering team] unblock the package for the releases that the " +"package should be un-retired for. In this request, clearly specify which " +"branches should be unblocked." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:153 +#: pages/Package_Retirement_Process.adoc:154 msgid "" "Restore the contents in Git and prepare a new build and update (if " "necessary)." msgstr "" #. type: Title == -#: ./pages/Package_Retirement_Process.adoc:155 +#: pages/Package_Retirement_Process.adoc:156 #, no-wrap msgid "Obsoleting Packages" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:162 +#: pages/Package_Retirement_Process.adoc:163 msgid "" "While not strictly part of the process, please consider what will happen to " "systems which have the now-retired packages installed. Generally, such " @@ -330,46 +316,47 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:164 +#: pages/Package_Retirement_Process.adoc:166 msgid "" -"Please consider adding your package to " -"https://src.fedoraproject.org/rpms/fedora-obsolete-packages/[fedora-obsolete-packages]." +"Please consider adding your package to https://src.fedoraproject.org/rpms/" +"fedora-obsolete-packages/[fedora-obsolete-packages] if there are upgrade " +"path issues or security concerns." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:170 +#: pages/Package_Retirement_Process.adoc:172 msgid "" -"Please follow " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages[the " -"relevant packaging guidelines] if another package will be providing similar " -"or identical functionality to the retired package, or if it is necessary " -"that the package be removed from end-user systems on system updates." +"Please follow xref:packaging-guidelines::index.adoc#renaming-or-replacing-" +"existing-packages[the relevant packaging guidelines] if another package will " +"be providing similar or identical functionality to the retired package, or " +"if it is necessary that the package be removed from end-user systems on " +"system updates." msgstr "" #. type: Title == -#: ./pages/Package_Retirement_Process.adoc:172 +#: pages/Package_Retirement_Process.adoc:174 #, no-wrap msgid "Completely Removing a Package" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:178 +#: pages/Package_Retirement_Process.adoc:180 msgid "" "In rare cases, such as when licensing issues are discovered, it may be " "necessary to completely remove a package from Fedora. This differs from " -"normal retirement in that the package is removed also from stable and " -"end-of-life releases." +"normal retirement in that the package is removed also from stable and end-of-" +"life releases." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:180 +#: pages/Package_Retirement_Process.adoc:182 msgid "" "For complete removal, first follow the xref:Procedure[procedure for normal " "removal]." msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:184 +#: pages/Package_Retirement_Process.adoc:186 msgid "" "Additionally, retire the package in '''all''' dist-git branches. Since " "`fedpkg retire` refuses to work on stable branches, simulate it with the " @@ -377,14 +364,12 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Package_Retirement_Process.adoc:186 +#: pages/Package_Retirement_Process.adoc:188 #, no-wrap -msgid "" -"$ DESC=\"my description\"; git rm -r . && echo \"$DESC\" > dead.package && " -"git add dead.package && git commit -m \"$DESC\"\n" +msgid "$ DESC=\"my description\"; git rm -r . && echo \"$DESC\" > dead.package && git add dead.package && git commit -m \"$DESC\"\n" msgstr "" #. type: Plain text -#: ./pages/Package_Retirement_Process.adoc:188 +#: pages/Package_Retirement_Process.adoc:190 msgid "Finally, add the package to fedora-obsolete-packages." msgstr "" diff --git a/po/fr/master/pages/Package_Review_Process.po b/po/fr/master/pages/Package_Review_Process.po index 1002c47..70d9bd8 100644 --- a/po/fr/master/pages/Package_Review_Process.po +++ b/po/fr/master/pages/Package_Review_Process.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-09-07 21:56+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,76 +16,63 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Package_Review_Process #. type: Title = -#: ./pages/Package_Review_Process.adoc:3 +#: pages/Package_Review_Process.adoc:3 #, no-wrap msgid "Package Review Process" msgstr "" +#. type: Plain text +#: pages/Package_Review_Process.adoc:8 +msgid "" +"In order for a new package to be added to Fedora, the package must first " +"undertake a formal review. The process is governed by the FESCo approved " +"xref:fesco::Package_review_policy.adoc[Package Review Policy]." +msgstr "" + #. type: Title == -#: ./pages/Package_Review_Process.adoc:7 +#: pages/Package_Review_Process.adoc:10 #, no-wrap -msgid "Review Purpose" +msgid "Review Process" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:17 +#: pages/Package_Review_Process.adoc:15 msgid "" -"In order for a new package to be added to Fedora, the package must first " -"undertake a formal review. The purpose of this formal review is to try to " -"ensure that the package meets the quality control requirements for Fedora. " -"This does not mean that the package (or the software being packaged) is " -"perfect, but it should meet baseline minimum requirements for quality." +"There are two roles in the review process, that of the contributor and that " +"of the reviewer. This document presents both perspectives." msgstr "" -#. type: Plain text -#: ./pages/Package_Review_Process.adoc:23 -msgid "" -"Reviews are currently done for totally new packages, " -"xref:Package_Renaming_Process.adoc#re_review_required[package renames], old " -"packages that were once retired returning to the collection, and packages " -"merged from the old Fedora Core repository." +#. type: Title === +#: pages/Package_Review_Process.adoc:17 +#, no-wrap +msgid "Exemptions" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:31 +#: pages/Package_Review_Process.adoc:25 msgid "" -"Note that some new packages may be exempt from the review process. Please " -"see " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/#_package_review_process[the " -"list of criteria]. If an exemption is warranted, the contributor can skip " -"directly to requesting a repository for it. The request to create a repo " -"should include the `--exception` flag instead of a bug number:" +"Certain packages are exempted from the review process as described in the " +"xref:fesco::Package_review_policy.adoc#what[Applicability section of Package " +"Review Policy]. If an exemption is warranted, the contributor can directly " +"request a repository for the package. The request to create a repo should " +"include the `--exception` flag instead of a bug number:" msgstr "" #. type: delimited block . -#: ./pages/Package_Review_Process.adoc:33 +#: pages/Package_Review_Process.adoc:27 #, no-wrap msgid "fedpkg request-repo --exception \n" msgstr "" -#. type: Title == -#: ./pages/Package_Review_Process.adoc:36 -#, no-wrap -msgid "Review Process" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Review_Process.adoc:41 -msgid "" -"There are two roles in the review process, that of the contributor and that " -"of the reviewer. In this document, we'll present both perspectives." -msgstr "" - #. type: Title === -#: ./pages/Package_Review_Process.adoc:42 +#: pages/Package_Review_Process.adoc:29 #, no-wrap msgid "Contributor" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:49 +#: pages/Package_Review_Process.adoc:36 msgid "" "A Contributor is defined as someone who wants to submit (and maintain) a " "new package in Fedora. To become a contributor, you must follow the " @@ -94,27 +81,22 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:56 +#: pages/Package_Review_Process.adoc:40 msgid "" "As a Contributor, you should have already made a package which adheres to " -"the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Package " -"Naming Guidelines] and " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging " -"Guidelines]. There are also some packages that cannot be included in " -"Fedora, to check if your package applies, check if it contains any " -"https://fedoraproject.org/wiki/Forbidden_items[Forbidden Items]." +"the xref:packaging-guidelines::index.adoc[Packaging Guidelines] and does not " +"contain any https://fedoraproject.org/wiki/Forbidden_items[Forbidden Items]." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:60 +#: pages/Package_Review_Process.adoc:44 msgid "" "When you're happy with your spec file, you should then submit that SRPM to a " "package review. Currently, this is done by following these steps:" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:66 +#: pages/Package_Review_Process.adoc:50 msgid "" "Put your spec file and SRPM somewhere on the Internet where it can be " "directly downloaded (just http(s), no registration pages or special download " @@ -123,44 +105,54 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:71 +#: pages/Package_Review_Process.adoc:55 msgid "" -"Fill out a " -"https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review[request " -"for review in bugzilla]. Make absolutely certain to file this bug with an " -"account tied to your FAS email address, otherwise your followup requests " -"will be closed as invalid." +"Fill out a https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?" +"product=Fedora&format=fedora-review[request for review in bugzilla]. Make " +"absolutely certain to file this bug with an account tied to your FAS email " +"address, otherwise your followup requests will be closed as invalid." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:80 +#: pages/Package_Review_Process.adoc:65 msgid "" "If nobody comments on your review request, you might want to mail to a " -"mailing list (for example, devel) asking for a \"review swap\". This is an " -"offer to do a review of someone else's package in exchange for them " -"reviewing your package. This is usually one-for-one, or can be some other " -"private arrangement depending on the difficulty of the respective packages." +"mailing list (for example, devel) or the https://discussion.fedoraproject." +"org/c/workflows/pkg-review-swap/91[Package Review Swaps category] on Fedora " +"Discussion to ask for a \"review swap\". This is an offer to do a review of " +"someone else's package in exchange for them reviewing your package. This is " +"usually one-for-one, or can be some other private arrangement depending on " +"the difficulty of the respective packages." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:84 +#: pages/Package_Review_Process.adoc:69 msgid "" -"If you do not have any package already in Fedora, you need a sponsor. Add " -"https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR] " -"to the bugs being blocked by your review request. For more information read " -"xref:How_to_Get_Sponsored_into_the_Packager_Group.adoc[How to Get Sponsored " -"into the Packager Group]." +"If you are not member of the https://accounts.fedoraproject.org/group/" +"packager/[packager] group, you need a sponsor. Add https://bugzilla.redhat." +"com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR] to the bugs being blocked " +"by your review request. For more information read xref:" +"How_to_Get_Sponsored_into_the_Packager_Group.adoc[How to Get Sponsored into " +"the Packager Group]." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:88 +#: pages/Package_Review_Process.adoc:72 +msgid "" +"If this is a \"re-review\" request needed to xref:Package_Retirement_Process." +"adoc#claiming[claim ownership] of a retired package, add `Unretirement` to " +"the _Whiteboard_ field." +msgstr "" + +#. type: Plain text +#: pages/Package_Review_Process.adoc:76 msgid "" "Wait for someone to review your package! At this point in the process, the " "`fedora-review` flag is blank, meaning that no reviewer is assigned." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:99 +#: pages/Package_Review_Process.adoc:87 msgid "" "There may be comments from people that are not formally reviewing the " "package, they may add `NotReady` to the _Whiteboard_ field, indication that " @@ -172,14 +164,14 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:102 +#: pages/Package_Review_Process.adoc:90 msgid "" "A reviewer takes on the task of reviewing your package. They will set the " "`fedora-review` flag to `?`." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:108 +#: pages/Package_Review_Process.adoc:96 msgid "" "The reviewer will review your package. You should fix any blockers that the " "reviewer identifies. Once the reviewer is happy with the package, the " @@ -188,29 +180,23 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:111 +#: pages/Package_Review_Process.adoc:99 msgid "" -"If you have not yet been sponsored, request sponsorship by " -"https://pagure.io/packager-sponsors/new_issue[raising an issue at package " -"sponsors]." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Review_Process.adoc:113 -msgid "When your package passes the review" +"If you have not yet been sponsored, request sponsorship by https://pagure.io/" +"packager-sponsors/issues[raising an issue at packager-sponsors]." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:118 +#: pages/Package_Review_Process.adoc:106 msgid "" -"you should use `fedpkg` to request a Git repository for it. Before you can " -"request a Git repository for the package, you will need a " -"https://pagure.io/settings/token/new[pagure api token] with _Create a new " -"ticket_ ACL added into `~/.config/rpkg/fedpkg.conf`:" +"When your package passes the review you should use `fedpkg` to request a Git " +"repository for it. Before you can request a Git repository for the package, " +"you will need a https://pagure.io/settings/token/new[pagure.io api token] " +"with _Create a new ticket_ ACL added into `~/.config/rpkg/fedpkg.conf`:" msgstr "" #. type: delimited block . -#: ./pages/Package_Review_Process.adoc:121 +#: pages/Package_Review_Process.adoc:110 #, no-wrap msgid "" "[fedpkg.pagure]\n" @@ -218,49 +204,72 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:130 +#: pages/Package_Review_Process.adoc:116 msgid "" -"Request a Git repository for the package. For example, if your bugzilla " -"review ticket is 12345, use: `fedpkg request-repo 12345`. Check that your " -"review bug is valid. It must have the `fedora-review` set to `+`, and it " -"must be assigned to your reviewer. Otherwise your repository request will " -"be closed as invalid." +"Request a Git repository for the package. For example, if the package name " +"is `my-package` and the bugzilla review ticket is 12345, :" +msgstr "" + +#. type: delimited block . +#: pages/Package_Review_Process.adoc:119 +#, no-wrap +msgid "fedpkg request-repo my-package 12345\n" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:139 +#: pages/Package_Review_Process.adoc:125 +msgid "" +"Check that your review bug is valid. It must have the `fedora-review` set " +"to `+`, and it must be assigned to your reviewer. Otherwise your repository " +"request will be closed as invalid." +msgstr "" + +#. type: Plain text +#: pages/Package_Review_Process.adoc:130 msgid "" "If you want to add your package to more Fedora releases and not just " -"Rawhide, let's say to Fedora 34, you can use the following command to " -"request additional branches: `fedpkg request-branch --repo f34`. You must " -"wait for your repository to be created before filing your branch request, " -"otherwise your branch request will be closed as invalid." +"Rawhide, let's say to Fedora {MAJOROSVER}, you can use the following command " +"to request additional branches:" +msgstr "" + +#. type: delimited block . +#: pages/Package_Review_Process.adoc:133 +#, no-wrap +msgid "fedpkg request-branch --repo my-package f{MAJOROSVER}`\n" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:143 +#: pages/Package_Review_Process.adoc:138 msgid "" -"When this is complete " -"(https://pagure.io/releng/fedora-scm-requests/issues[tickets in Pagure] for " -"requests above are closed as processed), checkout the package:" +"You do not need to wait for your repository to be created before filing your " +"branch request, but you should request the repository before requesting " +"branches." +msgstr "" + +#. type: Plain text +#: pages/Package_Review_Process.adoc:142 +msgid "" +"When https://pagure.io/releng/fedora-scm-requests/issues[fedora-scm-requests " +"tickets] for the requested repository and branches are closed, checkout the " +"package:" msgstr "" #. type: delimited block . -#: ./pages/Package_Review_Process.adoc:145 +#: pages/Package_Review_Process.adoc:145 #, no-wrap msgid "fedpkg clone\n" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:149 +#: pages/Package_Review_Process.adoc:149 msgid "" -"Now you can " -"xref:Joining_the_Package_Maintainers.adoc#import_commit_and_build_your_package[import " -"your SRPM package]. Do a final check of spec file tags, etc." +"Now you can xref:New_Package_Process_for_New_Contributors." +"adoc#import_commit_and_build_your_package[import your SRPM package]. Do a " +"final check of spec file tags, etc." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:152 +#: pages/Package_Review_Process.adoc:152 msgid "" "Request a Koji build by running `fedpkg build`. (You will need to set up " "https://fedoraproject.org/wiki/Infrastructure/Kerberos[Kerberos for Fedora " @@ -268,45 +277,45 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:154 +#: pages/Package_Review_Process.adoc:154 msgid "Repeat the process for other branches you may have requested above:" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:155 -msgid "Checkout given branch: `fedpkg switch-branch f34`" +#: pages/Package_Review_Process.adoc:155 +msgid "Checkout given branch: `fedpkg switch-branch f{MAJOROSVER}`" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:156 +#: pages/Package_Review_Process.adoc:156 msgid "Let Koji build the package for this branch: `fedpkg build`" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:160 +#: pages/Package_Review_Process.adoc:160 msgid "" "Request updates for Fedora release branches, if necessary, using `fedpkg " -"update` or another Bodhi interface as detailed in " -"https://fedoraproject.org/wiki/Bodhi[Bodhi]." +"update` or another Bodhi interface as detailed in https://fedoraproject.org/" +"wiki/Bodhi[Bodhi]." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:162 +#: pages/Package_Review_Process.adoc:162 msgid "" -"If possible, add your package to " -"xref:Upstream_Release_Monitoring.adoc[Upstream Release Monitoring]." +"If possible, add your package to xref:Upstream_Release_Monitoring." +"adoc[Upstream Release Monitoring]." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:166 +#: pages/Package_Review_Process.adoc:166 msgid "" "To be notified if your package stops building successfully when dependencies " -"are updated in Fedora, you can enable " -"https://fedoraproject.org/wiki/Koschei[Koschei]." +"are updated in Fedora, you can enable https://fedoraproject.org/wiki/" +"Koschei[Koschei]." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:174 +#: pages/Package_Review_Process.adoc:174 msgid "" "You should make sure the review ticket is closed. You are welcome to close " "it once the package has been built on the requested branches. If you built " @@ -316,7 +325,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:179 +#: pages/Package_Review_Process.adoc:179 msgid "" "You do not need to go through the review process again for subsequent " "package changes, and should not reference the review ticket in subsequent " @@ -324,27 +333,27 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Review_Process.adoc:180 +#: pages/Package_Review_Process.adoc:180 #, no-wrap msgid "Reviewer" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:183 +#: pages/Package_Review_Process.adoc:183 msgid "The Reviewer is the person who chooses to review a package." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:189 +#: pages/Package_Review_Process.adoc:189 msgid "" -"The Reviewer can be any Fedora account holder who is a member of the " -"https://accounts.fedoraproject.org/group/packager/[packager group]. (If the " +"The Reviewer can be any Fedora account holder who is a member of the https://" +"accounts.fedoraproject.org/group/packager/[packager group]. (If the " "Contributor is not yet sponsored, the review can still proceed to completion " "but they will need to find a sponsor at some point.)" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:192 +#: pages/Package_Review_Process.adoc:192 msgid "" "Search http://fedoraproject.org/PackageReviewStatus/[Package Review Tracker] " "for a review request that needs a reviewer: `fedora-review` flag is blank or " @@ -352,7 +361,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:199 +#: pages/Package_Review_Process.adoc:199 msgid "" "If you notice some issues that need to be solved before you want to start a " "formal review, add these issues in a comment and set the _Whiteboard_ of the " @@ -361,60 +370,61 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:203 +#: pages/Package_Review_Process.adoc:203 msgid "" "If you want to formally review the package, set the `fedora-review` flag to " "`?` and assign the bug to yourself." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:205 +#: pages/Package_Review_Process.adoc:205 msgid "Review the package" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:207 +#: pages/Package_Review_Process.adoc:207 msgid "" -"Go through the MUST items listed in " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/[Review " -"Guidelines] ." +"Go through the MUST items listed in xref:packaging-guidelines::" +"ReviewGuidelines.adoc[Review Guidelines] ." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:209 +#: pages/Package_Review_Process.adoc:209 msgid "" -"Go through the SHOULD items in " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/[Review " -"Guidelines] ." +"Go through the SHOULD items in xref:packaging-guidelines::ReviewGuidelines." +"adoc[Review Guidelines] ." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:213 +#: pages/Package_Review_Process.adoc:213 msgid "" -"The https://pagure.io/FedoraReview[FedoraReview] tool (packaged as " -"`fedora-review`) can help to automate this process." +"The https://pagure.io/FedoraReview[FedoraReview] tool (packaged as `fedora-" +"review`) can help to automate this process." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:217 +#: pages/Package_Review_Process.adoc:217 msgid "" "Include the text of your review in a comment in the ticket. For easy " "readability, simply use a regular comment instead of an attachment." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:219 +#: pages/Package_Review_Process.adoc:219 msgid "Take one of the following actions:" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:220 +#: pages/Package_Review_Process.adoc:222 #, no-wrap -msgid "*ACCEPT* - If the package is good, set the `fedora-review` flag to `+`.\n" +msgid "" +"*ACCEPT* - If the package is good, set the `fedora-review` flag to `+`.\n" +"Do not close the review ticket yet - this will be done by the submitter\n" +"once the package becomes available in Fedora.\n" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:228 +#: pages/Package_Review_Process.adoc:230 #, no-wrap msgid "" "*FAIL, LEGAL* - If the package is legally risky for whatever reason\n" @@ -423,12 +433,11 @@ msgid "" "and leave an appropriate comment\n" "(i.e. _we don't ship mp3, so stop submitting it_).\n" "Set the `fedora-review` flag to `-`,\n" -"and have the review ticket block " -"https://bugzilla.redhat.com/show_bug.cgi?id=FE-Legal[FE-Legal].\n" +"and have the review ticket block https://bugzilla.redhat.com/show_bug.cgi?id=FE-Legal[FE-Legal].\n" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:237 +#: pages/Package_Review_Process.adoc:239 #, no-wrap msgid "" "*FAIL, OTHER* - If the package is just way off\n" @@ -442,12 +451,11 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:244 +#: pages/Package_Review_Process.adoc:246 #, no-wrap msgid "" "*NEEDSWORK* - Anything that isn't explicitly failed should be left open\n" -"while the submitter and reviewer work together to fix any potential " -"issues.\n" +"while the submitter and reviewer work together to fix any potential issues.\n" "Mark the bug as `NEEDINFO`\n" "while waiting for the reviewer to respond to improvement requests.\n" "This makes it easier for reviewers to find open reviews\n" @@ -455,7 +463,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:251 +#: pages/Package_Review_Process.adoc:253 msgid "" "Once a package is flagged as `fedora-review +` (or `-`), the Reviewer's job " "is done although they may be called upon to assist the Contributor with the " @@ -464,79 +472,72 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Package_Review_Process.adoc:253 +#: pages/Package_Review_Process.adoc:255 #, no-wrap msgid "Definitions for fedora-review flag Settings" msgstr "" #. type: Table -#: ./pages/Package_Review_Process.adoc:261 +#: pages/Package_Review_Process.adoc:263 #, no-wrap msgid "" "|fedora-review |(BLANK) |Package Needs Review\n" "|fedora-review |? |Package Under Review\n" -"|fedora-review |- |Package Failed Review, dropped for legal or other " -"issues.\n" +"|fedora-review |- |Package Failed Review, dropped for legal or other issues.\n" "|fedora-review |+ |Package Approved\n" msgstr "" #. type: Title == -#: ./pages/Package_Review_Process.adoc:264 +#: pages/Package_Review_Process.adoc:266 #, no-wrap msgid "Special blocker tickets" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:268 +#: pages/Package_Review_Process.adoc:270 msgid "" "There are a few tickets which can be placed in the \"Blocks\" field to " "indicate specific ticket statuses:" msgstr "" #. type: Table -#: ./pages/Package_Review_Process.adoc:274 +#: pages/Package_Review_Process.adoc:276 #, no-wrap msgid "" -"|FE-NEEDSPONSOR |The submitter requires a sponsor; the review can be done by " -"anyone, but a sponsor will need to come and sponsor the submittor.\n" -"|FE-DEADREVIEW |The review has been closed out because the submitter has " -"left; users looking for packages to submit may find some possibilities in " -"these dead tickets.\n" +"|FE-NEEDSPONSOR |The submitter requires a sponsor; the review can be done by anyone, but a sponsor will need to come and sponsor the submitter.\n" +"|FE-DEADREVIEW |The review has been closed out because the submitter has left; users looking for packages to submit may find some possibilities in these dead tickets.\n" "|FE-Legal |The package is currently awaiting review by the legal team.\n" msgstr "" #. type: Title == -#: ./pages/Package_Review_Process.adoc:277 +#: pages/Package_Review_Process.adoc:279 #, no-wrap msgid "The Whiteboard" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:286 +#: pages/Package_Review_Process.adoc:288 msgid "" -"To save time for reviewers, the " -"https://fedoraproject.org/PackageReviewStatus/reviewable.html[New, " -"reviewable Fedora package review tickets] page will hide certain tickets " -"which are not reviewable. The _Whiteboard_ field can be used to mark a " -"ticket with various additional bits of status which will cause it to be " -"hidden or displayed differently." +"To save time for reviewers, the https://fedoraproject.org/" +"PackageReviewStatus/reviewable.html[New, reviewable Fedora package review " +"tickets] page will hide certain tickets which are not reviewable. The " +"_Whiteboard_ field can be used to mark a ticket with various additional bits " +"of status which will cause it to be hidden or displayed differently." msgstr "" #. type: Table -#: ./pages/Package_Review_Process.adoc:293 +#: pages/Package_Review_Process.adoc:296 #, no-wrap msgid "" -"|NotReady |The package is not yet ready for review. It is possible to open a " -"review ticket, mark it as NotReady, and continue to work on it until it's " -"ready to be seen by a reviewer.\n" +"|NotReady |The package is not yet ready for review. It is possible to open a review ticket, mark it as NotReady, and continue to work on it until it's ready to be seen by a reviewer.\n" "|BuildFails |The package fails to build.\n" -"|AwaitingSubmitter |The package review is stalled and cannot proceed without " -"input from the submitter.\n" +"|AwaitingSubmitter |The package review is stalled and cannot proceed without input from the submitter.\n" "|Trivial |The package is trivial to review. See below.\n" +"|Unretirement |A re-review needed to xref:Package_Retirement_Process.adoc#claiming[claim ownership] of a retired package .\n" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:299 +#: pages/Package_Review_Process.adoc:302 msgid "" "The `Trivial` status is intended to indicate packages which, as an aid to " "new reviewers, are especially uncomplicated and easy to review. A ticket " @@ -544,68 +545,67 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:302 -msgid "The package is known to build and a link to a scratch build is included." +#: pages/Package_Review_Process.adoc:305 +msgid "" +"The package is known to build and a link to a scratch build is included." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:304 +#: pages/Package_Review_Process.adoc:307 msgid "The ticket explains any rpmlint output which is present." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:307 +#: pages/Package_Review_Process.adoc:310 msgid "" "The spec contains nothing which is unnecessary in modern Fedora (such as " "`BuildRoot:`, a `%clean` section or `%defattr`)." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:309 +#: pages/Package_Review_Process.adoc:312 msgid "The spec is free from excessive or complicated macro usage." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:312 +#: pages/Package_Review_Process.adoc:315 msgid "" "The spec uses only the least complicated scriptlets which are taken directly " -"from the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/[Scriptlets] " -"page." +"from the xref:packaging-guidelines::Scriptlets.adoc[Scriptlets] page." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:314 +#: pages/Package_Review_Process.adoc:317 msgid "The package contains no daemons." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:316 +#: pages/Package_Review_Process.adoc:319 msgid "The package is not especially security sensitive." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:319 +#: pages/Package_Review_Process.adoc:322 msgid "" "The code has undergone a thorough inspection for licensing issues. " "Anomalies which would be found by `licensecheck` should be explained." msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:323 +#: pages/Package_Review_Process.adoc:326 msgid "" "In short, this should be reserved only for those tickets which should be " "easily approachable by someone doing their first package review." msgstr "" #. type: Title == -#: ./pages/Package_Review_Process.adoc:325 +#: pages/Package_Review_Process.adoc:328 #, no-wrap msgid "Tracking of Package Requests" msgstr "" #. type: Plain text -#: ./pages/Package_Review_Process.adoc:329 +#: pages/Package_Review_Process.adoc:332 msgid "" "The http://fedoraproject.org/PackageReviewStatus[Package Review Tracker] " "provides various review-related reports and a simple way to search for " diff --git a/po/fr/master/pages/Package_Update_Guide.po b/po/fr/master/pages/Package_Update_Guide.po index b41d3d9..30a74da 100644 --- a/po/fr/master/pages/Package_Update_Guide.po +++ b/po/fr/master/pages/Package_Update_Guide.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-11-22 21:56+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,15 +16,14 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Package_update_HOWTO #. type: Title = -#: ./pages/Package_Update_Guide.adoc:3 +#: pages/Package_Update_Guide.adoc:3 #, no-wrap msgid "Package Update Guide" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:11 +#: pages/Package_Update_Guide.adoc:10 msgid "" "This document shows how to submit an update for a package you maintain in " "Fedora. It assumes you already have a package in the Fedora repositories. " @@ -33,95 +32,92 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:15 +#: pages/Package_Update_Guide.adoc:14 msgid "" "For details of the policy on requirements for updates at various stages of " "the https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle[Fedora Release " -"Life Cycle], refer to the " -"https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/[Updates Policy]." +"Life Cycle], refer to the xref:fesco::Updates_Policy.adoc[Updates Policy]." msgstr "" #. type: Title == -#: ./pages/Package_Update_Guide.adoc:16 +#: pages/Package_Update_Guide.adoc:15 #, no-wrap msgid "Overview" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:22 +#: pages/Package_Update_Guide.adoc:21 msgid "" "This page is intended for new and existing package maintainers. Testers and " -"regular users may be interested in the " -"https://fedoraproject.org/wiki/QA:Updates_Testing[updates-testing] " -"repository and the " -"https://fedoraproject.org/wiki/QA:Update_feedback_guidelines[Update feedback " -"guidelines]. This page specifically covers the update submission process." +"regular users may be interested in the https://fedoraproject.org/wiki/QA:" +"Updates_Testing[updates-testing] repository and the https://fedoraproject." +"org/wiki/QA:Update_feedback_guidelines[Update feedback guidelines]. This " +"page specifically covers the update submission process." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:24 +#: pages/Package_Update_Guide.adoc:23 msgid "" "There are two significantly different package update submission workflows in " "Fedora:" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:27 +#: pages/Package_Update_Guide.adoc:26 msgid "" -"https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide] and " -"https://fedoraproject.org/wiki/Releases/Branched[Branched] up to the " -"https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updates-testing-activation[Updates-testing " -"Activation]." +"https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide] and https://" +"fedoraproject.org/wiki/Releases/Branched[Branched] up to the xref:fesco::" +"Updates_Policy.adoc#updates-testing-activation[Updates-testing Activation]." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:30 -msgid "Branched releases after Updates-testing Activation, and stable releases." +#: pages/Package_Update_Guide.adoc:29 +msgid "" +"Branched releases after Updates-testing Activation, and stable releases." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:33 +#: pages/Package_Update_Guide.adoc:32 msgid "" "The repository layouts differ somewhat for Rawhide, Branched and stable " "releases, but the update workflows split up as described above." msgstr "" #. type: Title == -#: ./pages/Package_Update_Guide.adoc:35 +#: pages/Package_Update_Guide.adoc:34 #, no-wrap msgid "Rawhide and early Branched" msgstr "" #. type: Title === -#: ./pages/Package_Update_Guide.adoc:38 +#: pages/Package_Update_Guide.adoc:37 #, no-wrap msgid "Single Packages" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:43 +#: pages/Package_Update_Guide.adoc:42 msgid "" "The update workflow for single package builds in Rawhide and Branched before " "updates-testing activation is simple:" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:45 +#: pages/Package_Update_Guide.adoc:44 msgid "" -"Build the package with `fedpk build`. See " -"xref:Package_Maintenance_Guide.adoc[Package Maintenance Guide] for more " -"details." +"Build the package with `fedpkg build`. See xref:Package_Maintenance_Guide." +"adoc[Package Maintenance Guide] for more details." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:49 +#: pages/Package_Update_Guide.adoc:48 msgid "" "This is all you need to do, a Bodhi update will be created automatically, " "from which potential tests will be run." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:56 +#: pages/Package_Update_Guide.adoc:55 msgid "" "If the built package doesn't have tests, or if they succeed, the update will " "be marked as _stable_ and your package will appear in subsequently created " @@ -130,7 +126,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:67 +#: pages/Package_Update_Guide.adoc:66 msgid "" "If the built package has tests which fail, this will be recorded in the " "update. You can now either xref:waive_a_result[waive the failing tests] if " @@ -139,241 +135,40 @@ msgid "" "tests (on the now hopefully fixed package), and so forth." msgstr "" -#. type: Title === -#: ./pages/Package_Update_Guide.adoc:69 -#, no-wrap -msgid "Multiple Packages" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:74 -msgid "" -"Some updates require changes in multiple related packages, e.g. if a library " -"is upgraded to a new major version and packages using it need to be rebuilt." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:80 -msgid "" -"Fedora has the concept of using side-tags for these situations, which means " -"the builds are done \"on the side\" and do not affect packages out of the " -"side-tag, nor are they available for installing until the side-tag is " -"merged." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:86 -msgid "" -"Packagers can create side-tags on their own, allowing them to build " -"disruptive components in isolation and submit the builds in a side-tag as " -"one update in Bodhi, to be tested and subsequently merged into the main " -"distribution." -msgstr "" - -#. type: Title ==== -#: ./pages/Package_Update_Guide.adoc:88 -#, no-wrap -msgid "Creating a side-tag" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:94 -msgid "" -"To create a side-tag for building packages for Rawhide, the easiest way is " -"to be in the checked out `rawhide` branch of one of the packages and issue " -"the following command:" -msgstr "" - -#. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:97 -#, no-wrap -msgid "fedpkg request-side-tag\n" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:101 -msgid "" -"Alternatively, you can specify the parent/base tag from which to create the " -"side-tag, e.g.:" -msgstr "" - -#. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:104 -#, no-wrap -msgid "fedpkg request-side-tag --base-tag f32-build\n" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:111 -msgid "" -"Side-tags for particular Fedora releases are based off its respective build " -"tag. I.e. if you wanted to create a side-tag for Rawhide while it's ramping " -"up for Fedora 32, the parent tag to choose would be `f32-build`." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:113 -msgid "This will tell you the commands to" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:115 -msgid "build a package in the specific side-tag and" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:116 -msgid "wait for the respective build root to be recreated, e.g.:" -msgstr "" - -#. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:122 -#, no-wrap -msgid "" -"$ fedpkg request-side-tag --base-tag f32-build\n" -"Side tag 'f32-build-side-7863' (id 7863) created.\n" -"Use 'fedpkg build --target=f32-build-side-7863' to use it.\n" -"Use 'koji wait-repo f32-build-side-7863' to wait for the build repo to be " -"generated.\n" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:130 -msgid "" -"The latter is important if any builds depend on previous ones in the " -"side-tag. Use `koji wait-repo --build ` to ensure " -"that the respective build is available in the build root for subsequent " -"builds." -msgstr "" - -#. type: Title ==== -#: ./pages/Package_Update_Guide.adoc:132 -#, no-wrap -msgid "Bodhi update for builds in a side-tag" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:138 -msgid "" -"When you're done building all packages you want in a side-tag, you have to " -"submit them as an update to Bodhi before they can be made available " -"generally to be installed and built upon." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:142 -msgid "" -"In the _Create New Update_ form in Bodhi, choose the _Use Side-Tag_ " -"drop-down to create an update from the latest package builds in the " -"respective tag:" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:144 -msgid "image:Bodhi-builds-from-side-tag.png[Bodhi-builds-from-side-tag.png,title=\"Bodhi-builds-from-side-tag.png\"]" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:154 -msgid "" -"As with single packages, tests will be run whose result affects if the " -"update can be moved to stable. The difference is that tests have to succeed " -"(or be waived) for all builds in the update. If you have to update the " -"list of builds, e.g. to fix problems found during testing, edit the update " -"and refresh the list of builds using the 🔃 (refresh) button:" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:156 -msgid "image:Bodhi-builds-refresh-from-side-tag.png[Bodhi-builds-refresh-from-side-tag.png,title=\"Bodhi-builds-refresh-from-side-tag.png\"]" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:160 -msgid "" -"The web interface only works if you are the creator of the side-tag. If you " -"are a proven packager submitting an update for a side-tag, you currently " -"need to use the bodhi cli:" -msgstr "" - -#. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:163 -#, no-wrap -msgid "$ bodhi updates new --from-tag --notes \"whatever\" --user \n" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:168 -msgid "" -"Once the update moves to stable, the builds will be tagged to the main tag " -"of the release, i.e. are available for the general public." -msgstr "" - -#. type: Title ==== -#: ./pages/Package_Update_Guide.adoc:170 -#, no-wrap -msgid "Adding/Removing builds to/from a side-tag" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:174 -msgid "" -"As a packager, you can add or remove builds from your side-tag using these " -"commands:" -msgstr "" - -#. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:178 -#, no-wrap -msgid "" -"$ koji tag \n" -"$ koji untag \n" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:184 -msgid "" -"This can be used to remove a build that made a test fail or to add a build " -"that was originally missed. If you add or remove a build from a side-tag, " -"you will have to refresh the corresponding update in Bodhi." -msgstr "" - #. type: Title == -#: ./pages/Package_Update_Guide.adoc:186 +#: pages/Package_Update_Guide.adoc:68 #, no-wrap msgid "Later Branched and stable releases" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:193 +#: pages/Package_Update_Guide.adoc:75 msgid "" -"At the " -"https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updates-testing-activation[updates-testing " -"activation] point, the Bodhi update feedback system is enabled by " -"https://docs.pagure.org/releng/[Release Engineering] and builds submitted " -"with `fedpkg build` are no longer automatically sent to any official " -"https://docs.fedoraproject.org/en-US/quick-docs/repositories/[repository]. " -"The update workflow for releases of this type is:" +"At the https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updates-" +"testing-activation[updates-testing activation] point, the Bodhi update " +"feedback system is enabled by https://docs.pagure.org/releng/[Release " +"Engineering] and builds submitted with `fedpkg build` are no longer " +"automatically sent to any official https://docs.fedoraproject.org/en-US/" +"quick-docs/repositories/[repository]. The update workflow for releases of " +"this type is:" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:195 +#: pages/Package_Update_Guide.adoc:77 msgid "Build the package with `fedpkg build`" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:202 +#: pages/Package_Update_Guide.adoc:84 msgid "" -"Submit an update for the package with `fedpkg update`, the " -"https://bodhi.fedoraproject.org/[Bodhi web interface], or the " -"https://crates.io/crates/bodhi-cli[Bodhi CLI tool]. This causes the package " -"to be sent to the " -"https://docs.fedoraproject.org/en-US/quick-docs/repositories/#the-updates-testing-repository[updates-testing] " -"repository." +"Submit an update for the package with `fedpkg update`, the https://bodhi." +"fedoraproject.org/[Bodhi web interface], or the `bodhi-cli` tool. This " +"causes the package to be sent to the xref:quick-docs::repositories.adoc#the-" +"updates-testing-repository[updates-testing] repository." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:207 +#: pages/Package_Update_Guide.adoc:89 msgid "" "Monitor the update's status and the feedback you receive via the web " "interface or email, and modify it with updated or additional builds if " @@ -381,24 +176,23 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:213 +#: pages/Package_Update_Guide.adoc:95 msgid "" -"After the update meets the criteria in the " -"https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/[Updates Policy] " -"and you are satisfied it should be released as a stable update, submit the " -"update to " -"https://docs.fedoraproject.org/en-US/quick-docs/repositories/#stable-is-not-a-repository[stable] " -"with `bodhi updates request stable` or the web interface." +"After the update meets the criteria in the xref:fesco::Updates_Policy." +"adoc[Updates Policy] and you are satisfied it should be released as a stable " +"update, submit the update to xref:quick-docs::repositories.adoc#stable-is-" +"not-a-repository[stable] with `bodhi updates request stable` or " +"the web interface." msgstr "" #. type: Title === -#: ./pages/Package_Update_Guide.adoc:215 +#: pages/Package_Update_Guide.adoc:97 #, no-wrap msgid "Update attributes" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:223 +#: pages/Package_Update_Guide.adoc:105 msgid "" "At the time you submit the update, you will be asked for several " "attributes. The type of the update should be fairly self-explanatory: " @@ -406,7 +200,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:228 +#: pages/Package_Update_Guide.adoc:110 msgid "" "If you are asked whether you want to send the update to _updates-testing_ or " "_stable_, this is a no-op: all updates now go through _updates-testing_. It " @@ -414,7 +208,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:240 +#: pages/Package_Update_Guide.adoc:122 msgid "" "There are several schools of thought on filling out the update description. " "Some would suggest you consider the target audience: for a stable release, " @@ -427,20 +221,20 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:252 +#: pages/Package_Update_Guide.adoc:134 msgid "" "If you associate one or more bug reports with your update, Bodhi will post " "comments into Bugzilla to alert those following the bug reports that an " "update is available. If you mark your update as fixing the bug(s), Bodhi " "will move the report(s) through the `MODIFIED`, `ON_QA` and `CLOSED ERRATA` " -"states of the " -"https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow[bug workflow] as " -"your update reaches various points in the process. Using this mechanism can " -"be very useful both for you and for users of your package." +"states of the https://fedoraproject.org/wiki/BugZappers/" +"BugStatusWorkFlow[bug workflow] as your update reaches various points in the " +"process. Using this mechanism can be very useful both for you and for users " +"of your package." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:266 +#: pages/Package_Update_Guide.adoc:148 msgid "" "You may set a _karma_ (feedback) level at which the update will " "automatically be submitted to _stable_. This is optional. If you choose to " @@ -452,13 +246,13 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Update_Guide.adoc:268 +#: pages/Package_Update_Guide.adoc:150 #, no-wrap msgid "Who will receive your update, when?" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:276 +#: pages/Package_Update_Guide.adoc:158 msgid "" "When a release is in Branched state, the _updates-testing_ repository is " "enabled by default so most users will see the package, but only packages " @@ -467,19 +261,18 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:286 +#: pages/Package_Update_Guide.adoc:168 msgid "" "Where a package goes when it is marked as _stable_ differs between Branched " "and stable releases. In Branched releases, _stable_ packages are pushed to " "the base _fedora_ repository. In stable releases, _stable_ packages are " "pushed to the _updates_ repository. However, from the point of view of the " "packager, this is an insignificant implementation detail. For more details, " -"see " -"https://docs.fedoraproject.org/en-US/quick-docs/repositories/[Repositories]." +"see xref:quick-docs::repositories.adoc[Repositories]." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:294 +#: pages/Package_Update_Guide.adoc:176 msgid "" "When a release is in stable state, the _updates-testing_ repository is " "disabled by default, but QA team members and others run with it enabled in " @@ -489,103 +282,13 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Package_Update_Guide.adoc:296 -#, no-wrap -msgid "Updating inter-dependent packages" -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:307 -msgid "" -"If an update you wish to submit would cause a dependency issue of any kind " -"(a strict package dependency error, or simply another package failing to " -"operate correctly) if updated alone, you must not submit the package as a " -"single-package update. You must always collect all inter-dependent or " -"related packages together into a single multi-package update, such that no " -"user will face problems if they install all the packages in the update " -"together." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:318 -msgid "" -"For example: if you maintain a package `libfoo` which the package `bar` " -"depends on, and you need to update `libfoo`, you should check that `bar` " -"continues to function correctly with the updated version of `libfoo`. If it " -"does not, you must ensure the appropriate changes are made to `bar`, and " -"include the updated `bar` in your update along with the updated `libfoo`." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:325 -msgid "" -"The `fedpkg` tool does not handle multi-package updates. You can add " -"multiple packages to an update using the " -"https://bodhi.fedoraproject.org/updates/new[Bodhi web application], or the " -"command line tool. You can pass as many package names as you like to `bodhi " -"updates new` command to create a new multi-package update, or use `bodhi " -"updates edit` to edit an existing update." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:337 -msgid "" -"It is possible you will run into problems with permissions when trying to " -"add builds of packages you do not have commit privileges for to an update, " -"or trying to add a build for a package you do have privileges for to someone " -"else's update. If you encounter a situation like this, you should contact " -"the https://docs.pagure.org/releng/[release engineering] team or a proven " -"packager for help." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:352 -msgid "" -"You may need a _buildroot override_ to complete a multi-package update " -"successfully. For instance in the case described above, you may need to " -"rebuild `bar` against the new `libfoo` package and submit both packages " -"together as a multi-package update. However, in the normal course of " -"events, you would not be able to build another package against your new " -"`libfoo` build until it reached the stable state. To resolve this dilemma, " -"you can request a buildroot override, which causes the `libfoo` build to be " -"included in the buildroot for a short time in order to get the `bar` package " -"build done." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:361 -msgid "" -"You can request a buildroot override with bodhi: This would submit a " -"buildroot override with a duration of two days. Buildroot overrides are " -"usually granted within 15-30 minutes of submission. If you submit an " -"override request with the bodhi tool, it will suggest a command that will " -"let you monitor when the package appears in the buildroot, so you can fire " -"your dependent build at the appropriate time." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:363 -msgid "" -"You can also request buildroot overrides from the " -"https://bodhi.fedoraproject.org/overrides/new[Bodhi web application]." -msgstr "" - -#. type: Plain text -#: ./pages/Package_Update_Guide.adoc:365 -msgid "" -"The https://fedoraproject.org/wiki/Bodhi/BuildRootOverrides[buildroot " -"override instructions] explain the buildroot override process in more " -"detail." -msgstr "" - -#. type: Title === -#: ./pages/Package_Update_Guide.adoc:367 +#: pages/Package_Update_Guide.adoc:178 #, no-wrap msgid "Handling feedback from automated tests" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:373 +#: pages/Package_Update_Guide.adoc:184 msgid "" "Fedora's automated testing system, OpenQA, may run automated tests on your " "update. The OpenQA tests are functional tests of some critical Workstation " @@ -593,7 +296,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:384 +#: pages/Package_Update_Guide.adoc:195 msgid "" "In the Bodhi web interface, updates have an _Automated Tests_ tab which " "displays the results of all automated tests. Tests shown with a red " @@ -605,54 +308,48 @@ msgid "" msgstr "" #. type: Title ==== -#: ./pages/Package_Update_Guide.adoc:386 +#: pages/Package_Update_Guide.adoc:197 #, no-wrap msgid "Waive a result" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:395 +#: pages/Package_Update_Guide.adoc:206 msgid "" -"At present, a failure of the _dist.rpmdeplint_, _dist.abicheck_, or " -"_org.centos.prod.ci.pipeline.complete_ tests will prevent your update from " -"being released. On the update's _Details_ page in the Bodhi web interface, " -"the *Test Gating Status* will be shown as _N of N required tests failed_. " -"If you are sure such a failure is a false one, you can 'waive' the result " -"using the tool `waiverdb-cli`." +"At present, a failure of the _dist.rpmdeplint_, _dist.abicheck_, or _org." +"centos.prod.ci.pipeline.complete_ tests will prevent your update from being " +"released. On the update's _Details_ page in the Bodhi web interface, the " +"*Test Gating Status* will be shown as _N of N required tests failed_. If " +"you are sure such a failure is a false one, you can 'waive' the result using " +"the tool `waiverdb-cli`." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:398 +#: pages/Package_Update_Guide.adoc:209 msgid "" "You can submit a waiver for a failing result with `waiverdb-cli` specifying " "the `subject` and the `testcase`:" msgstr "" #. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:401 +#: pages/Package_Update_Guide.adoc:213 #, no-wrap -msgid "" -"waiverdb-cli -t YOUR_TESTCASE_HERE -s '{\"item\": \"this-is-the-subject\", " -"\"type\": \"also-this-is-part-of-the-subject\"}' -p \"fedora-26\" -c \"This " -"is fine\"`\n" +msgid "waiverdb-cli -t YOUR_TESTCASE_HERE -s '{\"item\": \"this-is-the-subject\", \"type\": \"also-this-is-part-of-the-subject\"}' -p \"fedora-{MAJOROSVER}\" -c \"This is fine\"`\n" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:404 +#: pages/Package_Update_Guide.adoc:216 msgid "Example:" msgstr "" #. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:407 +#: pages/Package_Update_Guide.adoc:220 #, no-wrap -msgid "" -"waiverdb-cli -t dist.rpmdeplint -s '{\"item\": " -"\"python-requests-1.2.3-1.fc26\", \"type\": \"koji_build\"}' -p " -"\"fedora-26\" -c \"This is fine\"`\n" +msgid "waiverdb-cli -t dist.rpmdeplint -s '{\"item\": \"python-requests-1.2.3-1.fc{MAJOROSVER}\", \"type\": \"koji_build\"}' -p \"fedora-{MAJOROSVER}\" -c \"This is fine\"`\n" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:412 +#: pages/Package_Update_Guide.adoc:225 msgid "" "You can also waive a failing result by result's id, which you can retrieve " "from resultsdb with curl. To do that, you'll need the `testcase` name and " @@ -660,72 +357,67 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:415 +#: pages/Package_Update_Guide.adoc:229 #, no-wrap -msgid "" -"curl " -"\"https://taskotron.fedoraproject.org/resultsdb_api/api/v2.0/results?testcases=dist.python-versions&item=python-alembic-0.9.7-1.fc2\" " -"| jq \".data[0].id\"\n" +msgid "curl \"https://taskotron.fedoraproject.org/resultsdb_api/api/v2.0/results?testcases=dist.python-versions&item=python-alembic-0.9.7-1.fc{MAJOROSVER}\" | jq \".data[0].id\"\n" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:419 +#: pages/Package_Update_Guide.adoc:233 msgid "" "This should print out the of the failing result. You can then submit a " "waiver for this failing result with" msgstr "" #. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:422 +#: pages/Package_Update_Guide.adoc:237 #, no-wrap -msgid "waiverdb-cli -p fedora-27 -r YOUR_ID_HERE -c \"This is fine.\"\n" +msgid "waiverdb-cli -p fedora-{MAJOROSVER} -r YOUR_ID_HERE -c \"This is fine.\"\n" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:432 +#: pages/Package_Update_Guide.adoc:247 msgid "" "Also, if you enabled automatic stable push at a karma threshold, this will " "be disabled if any automated test fails. If you have examined the result " "and you are sure it is a false one and there is no problem with the package, " "you may re-enable the automatic push mechanism or submit the package to " -"_stable_ manually once it meets the other requirements of the " -"https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/[Updates Policy]." +"_stable_ manually once it meets the other requirements of the xref:fesco::" +"Updates_Policy.adoc[Updates Policy]." msgstr "" #. type: Title ==== -#: ./pages/Package_Update_Guide.adoc:434 +#: pages/Package_Update_Guide.adoc:249 #, no-wrap msgid "Waive the absence of a result" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:439 +#: pages/Package_Update_Guide.adoc:254 msgid "" "Submitting a waiver using subject/testcase allows to waive the absence of a " -"result (eg. the test never ran for some reason, so there is no result item)." +"result (e.g. the test never ran for some reason, so there is no result item)." msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:442 +#: pages/Package_Update_Guide.adoc:257 msgid "" "If it is not clear which testcase you should specify, the answer can be " "fetched with this Python script:" msgstr "" #. type: delimited block - -#: ./pages/Package_Update_Guide.adoc:468 +#: pages/Package_Update_Guide.adoc:283 #, no-wrap msgid "" "#!/usr/bin/env python\n" "\"\"\" Ask a question of greenwave. \"\"\"\n" -"# Usage: either modify and set PRODUCT_VERSION and NVR_LIST and run, or pass " -"version as first arg and then NVRs as further args\n" +"# Usage: either modify and set PRODUCT_VERSION and NVR_LIST and run, or pass version as first arg and then NVRs as further args\n" "import pprint\n" "import requests\n" "import sys\n" "PRODUCT_VERSION = 'fedora-27' if len(sys.argv) == 1 else sys.argv[1]\n" -"NVR_LIST = [] or sys.argv[2:] # Insert your NVRs here, or pass them via " -"command line args\n" +"NVR_LIST = [] or sys.argv[2:] # Insert your NVRs here, or pass them via command line args\n" "for nvr in NVR_LIST:\n" " url = (\n" " 'https://greenwave-web-greenwave.app.os.fedoraproject.org/'\n" @@ -744,7 +436,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:477 +#: pages/Package_Update_Guide.adoc:292 msgid "" "The output will show that Greenwave is requiring a specific testcase to run, " "but it cannot find a result for it (neither pass nor failure). So now it is " @@ -753,76 +445,412 @@ msgid "" msgstr "" #. type: Title ==== -#: ./pages/Package_Update_Guide.adoc:478 +#: pages/Package_Update_Guide.adoc:293 #, no-wrap msgid "Troubleshooting" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:481 +#: pages/Package_Update_Guide.adoc:296 msgid "If you run the tool and it gives you the following error:" msgstr "" #. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:484 +#: pages/Package_Update_Guide.adoc:299 #, no-wrap msgid "Error: The config option \"resultsdb_api_url\" is required\n" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:487 +#: pages/Package_Update_Guide.adoc:302 msgid "Edit `/etc/waiverdb/client.conf` and add the following line:" msgstr "" #. type: delimited block . -#: ./pages/Package_Update_Guide.adoc:490 +#: pages/Package_Update_Guide.adoc:305 #, no-wrap msgid "resultsdb_api_url=https://taskotron.fedoraproject.org/resultsdb_api/api/v2.0\n" msgstr "" #. type: Title === -#: ./pages/Package_Update_Guide.adoc:493 +#: pages/Package_Update_Guide.adoc:308 #, no-wrap msgid "Branched milestone freezes" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:511 +#: pages/Package_Update_Guide.adoc:326 +msgid "" +"For a short period before each milestone release, the stable xref:quick-" +"docs::repositories.adoc#the-fedora-repository-in-branched-releases[fedora] " +"repository is frozen. These periods are shown as _Milestone freezes_ (Post-" +"branch Freeze, Beta Freeze, Final Freeze) on schedules. During these " +"periods, builds will not be marked _stable_ and pushed from _updates-" +"testing_ to _fedora_ even after being submitted manually or automatically. " +"In the normal course of events, they will be pushed after the milestone " +"release is approved at a https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go " +"No Go Meeting]. If you believe your update deserves to break a milestone " +"freeze, a _freeze exception_ may be granted through the https://" +"fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process[freeze exception " +"process]. Accepted release blocking bugs are granted the same status " +"through the https://fedoraproject.org/wiki/QA:" +"SOP_blocker_bug_process[blocker bug process]." +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:328 +msgid "" +"For more on the Fedora development process, see https://fedoraproject.org/" +"wiki/Fedora_Release_Life_Cycle[Fedora Release Life Cycle]." +msgstr "" + +#. type: Title == +#: pages/Package_Update_Guide.adoc:330 +#, no-wrap +msgid "[[updating_inter_dependent_packages]] Multi-package updates" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:338 msgid "" -"For a short period before each milestone release, the stable " -"https://docs.fedoraproject.org/en-US/quick-docs/repositories/#the-fedora-repository-in-branched-releases[fedora] " -"repository is frozen. These periods are shown as _Milestone freezes_ " -"(Post-branch Freeze, Beta Freeze, Final Freeze) on schedules. During these " -"periods, builds will not be marked _stable_ and pushed from " -"_updates-testing_ to _fedora_ even after being submitted manually or " -"automatically. In the normal course of events, they will be pushed after " -"the milestone release is approved at a " -"https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go No Go Meeting]. If you " -"believe your update deserves to break a milestone freeze, a _freeze " -"exception_ may be granted through the " -"https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process[freeze " -"exception process]. Accepted release blocking bugs are granted the same " -"status through the " -"https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process[blocker bug " -"process]." +"Some updates require changes in multiple related packages. For example, if " +"you maintain `bar` which depends on `libfoo`, and you need to update " +"`libfoo`, you should check that `bar` still works with the updated " +"`libfoo`. If it does not, you must ensure the appropriate changes are made " +"to `bar`, and include the updated `bar` in your update along with the " +"updated `libfoo`." +msgstr "" + +#. type: Title === +#: pages/Package_Update_Guide.adoc:339 +#, no-wrap +msgid "Side tags" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:345 +msgid "" +"Fedora has the concept of using side tags for these situations, which means " +"the builds are done \"on the side\" and do not affect packages out of the " +"side tag, nor are they available for installing until the side tag is merged." +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:350 +msgid "" +"Packagers can create side tags on their own, allowing them to build " +"disruptive components in isolation and submit the builds in a side tag as " +"one update in Bodhi, to be tested and subsequently merged into the main " +"distribution." +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:354 +msgid "" +"Side tags are cleaned up 30 days after creation, or 14 days if they have not " +"been used at all. Make sure and use your side tag before then." +msgstr "" + +#. type: Title ==== +#: pages/Package_Update_Guide.adoc:356 +#, no-wrap +msgid "Creating a side tag" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:361 +msgid "" +"The easiest way to create a side tag is to be in the checked out branch (e." +"g. `rawhide`) of one of the packages and issue the following command:" +msgstr "" + +#. type: delimited block - +#: pages/Package_Update_Guide.adoc:364 +#, no-wrap +msgid "fedpkg request-side-tag\n" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:367 +msgid "" +"Alternatively, the following variants allow specifying the Fedora release or " +"the base tag for the side tag:" +msgstr "" + +#. type: delimited block - +#: pages/Package_Update_Guide.adoc:372 +#, no-wrap +msgid "" +"fedpkg --release f{NEXTOSVER} request-side-tag\n" +"fedpkg request-side-tag --base-tag f{NEXTOSVER}-build\n" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:376 +msgid "" +"`fedpkg` will tell you the commands to build a package in the specific side " +"tag and to wait for the respective build root to be recreated:" +msgstr "" + +#. type: delimited block - +#: pages/Package_Update_Guide.adoc:383 +#, no-wrap +msgid "" +"$ fedpkg request-side-tag\n" +"Side tag 'f{NEXTOSVER}-build-side-7863' (id 7863) created.\n" +"Use 'fedpkg build --target=f{NEXTOSVER}-build-side-7863' to use it.\n" +"Use 'koji wait-repo f{NEXTOSVER}-build-side-7863' to wait for the build repo to be generated.\n" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:388 +msgid "" +"The latter is important if any builds depend on previous ones in the side " +"tag. Use `koji wait-repo --build ` to ensure that " +"the respective build is available in the build root for subsequent builds." +msgstr "" + +#. type: Title ==== +#: pages/Package_Update_Guide.adoc:390 +#, no-wrap +msgid "Bodhi update for builds in a side tag" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:395 +msgid "" +"When you're done building all packages you want in a side tag, you have to " +"submit them as an update to Bodhi before they can be made available " +"generally to be installed and built upon." +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:399 +msgid "" +"In the _Create New Update_ form in Bodhi, choose the _Use Side-Tag_ drop-" +"down to create an update from the latest package builds in the respective " +"tag:" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:401 +msgid "" +"image:Bodhi-builds-from-side-tag.png[Bodhi-builds-from-side-tag.png," +"title=\"Bodhi-builds-from-side-tag.png\"]" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:408 +msgid "" +"As with single packages, tests will be run whose result affects if the " +"update can be moved to stable. The difference is that tests have to succeed " +"(or be waived) for all builds in the update. If you have to update the list " +"of builds, e.g. to fix problems found during testing, edit the update and " +"refresh the list of builds using the 🔃 (refresh) button:" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:410 +msgid "" +"image:Bodhi-builds-refresh-from-side-tag.png[Bodhi-builds-refresh-from-side-" +"tag.png,title=\"Bodhi-builds-refresh-from-side-tag.png\"]" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:414 +msgid "" +"The web interface only works if you are the creator of the side tag. If you " +"are a proven packager submitting an update for a side tag, you currently " +"need to use the bodhi cli:" +msgstr "" + +#. type: delimited block - +#: pages/Package_Update_Guide.adoc:418 +#, no-wrap +msgid "bodhi updates new --from-tag --notes \"whatever\" f{NEXTOSVER}-build-side-7863\n" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:424 +msgid "" +"Once the update moves to stable, the builds will be tagged to the main tag " +"of the release, i.e. are available for the general public. The side tag " +"will be automatically removed." +msgstr "" + +#. type: Title ==== +#: pages/Package_Update_Guide.adoc:426 +#, no-wrap +msgid "Adding/Removing builds to/from a side tag" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:428 +msgid "" +"As a packager, you can add or remove builds from your side tag using these " +"commands:" +msgstr "" + +#. type: delimited block - +#: pages/Package_Update_Guide.adoc:432 +#, no-wrap +msgid "" +"koji tag \n" +"koji untag \n" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:438 +msgid "" +"This can be used to remove a build that made a test fail or to add a build " +"that was originally missed. If you add or remove a build from a side tag, " +"you will have to refresh the corresponding update in Bodhi." +msgstr "" + +#. type: delimited block = +#: pages/Package_Update_Guide.adoc:442 +msgid "" +"Removing the last build in a side-tag will automatically remove/delete the " +"side tag." +msgstr "" + +#. type: Title ==== +#: pages/Package_Update_Guide.adoc:446 +#, no-wrap +msgid "Removing a side tag" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:450 +msgid "" +"To conserve build system resources, side tags that are not needed anymore " +"should be removed. This can be achieved with `fedpkg` as follows:" +msgstr "" + +#. type: delimited block - +#: pages/Package_Update_Guide.adoc:453 +#, no-wrap +msgid "fedpkg remove-side-tag \n" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:457 +msgid "" +"Bodhi automatically removes side tags used for updates pushed to stable, " +"removing them manually is not necessary." +msgstr "" + +#. type: Title ==== +#: pages/Package_Update_Guide.adoc:458 +#, no-wrap +msgid "Using macros in a side tag" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:465 +msgid "" +"Koji allows macros to be set in a side tag. This is useful in certain " +"scenarios, such as changing configuration of builds in this side tag without " +"changing their sources. The following commands may be used to set and unset " +"macro respectively:" +msgstr "" + +#. type: delimited block - +#: pages/Package_Update_Guide.adoc:469 +#, no-wrap +msgid "" +"$ koji edit-sidetag --rpm-macro = \n" +"$ koji edit-sidetag --remove-rpm-macro \n" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:473 +msgid "" +"Please make sure `python3-koji-cli-plugins` is installed on your sytem to " +"have the `koji edit-sidetag` command available." +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:475 +msgid "" +"The following commands can be used to review macros configured for the side " +"tag:" +msgstr "" + +#. type: delimited block - +#: pages/Package_Update_Guide.adoc:479 +#, no-wrap +msgid "" +"$ koji taginfo \n" +"$ koji list-history --tag \n" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:484 +msgid "" +"Please note that the macro changes won't take effect immediately. It is " +"necessary to wait using `$ koji wait-repo ` command until the " +"repository data is refreshed." +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:491 +msgid "" +"While modifying the macro configuration on side-tags can be useful, it can " +"also be problematic. As such, macros must be approved by FESCo and the list " +"of currently supported macros is available in the xref:fesco::" +"Policy_for_buildroot_macros.adoc[Policy for Buildroot Macros]." +msgstr "" + +#. type: Title === +#: pages/Package_Update_Guide.adoc:492 +#, no-wrap +msgid "Bodhi multi package updates" +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:500 +msgid "" +"You can also create an update with multiple packages directly in Bodhi, " +"either with the https://bodhi.fedoraproject.org[Bodhi web application], or " +"with the `bodhi` command line tool. You can pass multiple package names to " +"`bodhi updates new` command to create a new multi-package update, or use " +"`bodhi updates edit` to edit an existing update." +msgstr "" + +#. type: Plain text +#: pages/Package_Update_Guide.adoc:507 +msgid "" +"It is possible you will run into problems with permissions when you are not " +"the maintainer of the package you are trying to add to an update, or when " +"you are trying to add packages to an update created by somebody else. If " +"you encounter a situation like this, you should contact the https://docs." +"pagure.org/releng/[release engineering] team or a proven packager for help." +msgstr "" + +#. type: Title === +#: pages/Package_Update_Guide.adoc:509 +#, no-wrap +msgid "Buildroot overrides" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:513 +#: pages/Package_Update_Guide.adoc:515 msgid "" -"For more on the Fedora development process, see " -"https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle[Fedora Release Life " -"Cycle]." +"Yet another way to build multiple packages together are https://" +"fedoraproject.org/wiki/Bodhi/BuildRootOverrides[buildroot overrides]. " +"Unlike side tags, buildroot overrides are not isolated and thus should be " +"only used in special cases where side tags do not suffice." msgstr "" #. type: Title == -#: ./pages/Package_Update_Guide.adoc:515 +#: pages/Package_Update_Guide.adoc:517 #, no-wrap msgid "Security updates" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:523 +#: pages/Package_Update_Guide.adoc:525 msgid "" "For bugs identified as security issues, there is an additional process that " "layers over the regular update process. If a bug is assigned to you that " @@ -831,25 +859,25 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Package_Update_Guide.adoc:525 +#: pages/Package_Update_Guide.adoc:527 #, no-wrap msgid "New package submissions" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:529 +#: pages/Package_Update_Guide.adoc:531 msgid "" "If you want to build a new package, but you aren't sure which releases to " "send it to:" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:531 +#: pages/Package_Update_Guide.adoc:533 msgid "New packages should always be built for Rawhide" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:535 +#: pages/Package_Update_Guide.adoc:537 msgid "" "New packages can be built for Branched and stable releases if adding them " "would provide value to users of those releases without significant risk of " @@ -857,25 +885,25 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:540 +#: pages/Package_Update_Guide.adoc:542 msgid "" -"The submission process for new packages, after they have passed the " -"xref:Package_Review_Process.adoc[Package Review Process] and been given an " -"SCM repository, is exactly the same as that for package updates." +"The submission process for new packages, after they have passed the xref:" +"Package_Review_Process.adoc[Package Review Process] and been given an SCM " +"repository, is exactly the same as that for package updates." msgstr "" #. type: Title == -#: ./pages/Package_Update_Guide.adoc:542 +#: pages/Package_Update_Guide.adoc:544 #, no-wrap msgid "Consider creating a package test plan" msgstr "" #. type: Plain text -#: ./pages/Package_Update_Guide.adoc:548 +#: pages/Package_Update_Guide.adoc:550 msgid "" "If you https://fedoraproject.org/wiki/QA:SOP_test_case_creation[create test " -"cases] for your package, and " -"https://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation[categorize " -"them appropriately], they will be automatically linked in Bodhi, so that " -"testers will have some guidance for planned update testing." +"cases] for your package, and https://fedoraproject.org/wiki/QA:" +"SOP_package_test_plan_creation[categorize them appropriately], they will be " +"automatically linked in Bodhi, so that testers will have some guidance for " +"planned update testing." msgstr "" diff --git a/po/fr/master/pages/Packaging_Tutorial_GNU_Hello.po b/po/fr/master/pages/Packaging_Tutorial_GNU_Hello.po index c36b14c..a41a120 100644 --- a/po/fr/master/pages/Packaging_Tutorial_GNU_Hello.po +++ b/po/fr/master/pages/Packaging_Tutorial_GNU_Hello.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-11-10 22:03+0000\n" +"POT-Creation-Date: 2023-07-10 21:54+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,161 +17,132 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #. type: Title = -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:3 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:3 #, no-wrap msgid "Packaging Tutorial: GNU Hello" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:16 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:16 msgid "" -"This tutorial demonstrates RPM packaging by packaging the " -"https://www.gnu.org/software/hello/[GNU Hello] program. While the program " -"itself is simple, it also comes with most of the usual peripheral components " -"of a FOSS project: configuration/build/install environment, documentation, " +"This tutorial demonstrates RPM packaging by packaging the https://www.gnu." +"org/software/hello/[GNU Hello] program. While the program itself is simple, " +"it also comes with most of the usual peripheral components of a FOSS " +"project: configuration/build/install environment, documentation, " "internationalization, etc. However, it does not include RPM packaging " "information, therefore it is a reasonable vehicle to practice building RPMs " "on." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:23 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:22 msgid "" -"For comprehensive information on how to create RPM files, including more " -"detailed tips, refer to " -"https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/[Creating " -"RPM Packages]. If you plan to create an RPM package for the Fedora " -"repository, follow the process for " -"xref:Joining_the_Package_Maintainers.adoc[Joining the Package Maintainers], " -"including following the various Fedora guidance." -msgstr "" - -#. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:25 -#, no-wrap -msgid "Development Environment" -msgstr "" - -#. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:28 -msgid "To build RPMs for Fedora we need a set of development tools." -msgstr "" - -#. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:31 -msgid "" -"This is a one-time-only setup, installed by running these commands from a " -"system administration (root) account:" -msgstr "" - -#. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:34 -#, no-wrap -msgid "# dnf install fedora-packager\n" +"For comprehensive information on how to create RPM files, refer to https://" +"rpm-software-management.github.io/rpm/manual/[RPM Reference Manual]. If you " +"plan to create an RPM package for the Fedora repository, follow the process " +"for xref:Joining_the_Package_Maintainers.adoc[Joining the Package " +"Maintainers], including following the various Fedora guidance." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:38 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:29 msgid "" -"To be able to test the build procedure in a clean chroot you need to " -"configure your non-privileged account to be a member of the `mock` group:" -msgstr "" - -#. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:41 -#, no-wrap -msgid "# usermod -a -G mock \n" +"This tutorial is intended to be run on a Fedora {MAJOROSVER} system. It " +"should, however, work also for other Fedora releases. Just replace strings " +"like `f{MAJOROSVER}` with your release number. Fedora downstreams such as " +"CentOS Stream or Red Hat Enterprise Linux are unlikely to work, because this " +"tutorial uses Fedora specific and very recent tools and features. In " +"particular, https://docs.pagure.org/fedora-infra.rpmautospec/[rpmautospec] " +"is unlikely to be available." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:48 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:35 msgid "" -"Those are the only commands requiring root privileges. All the remaining " -"work should be done from your regular, non-privileged account, or even from " -"a separate account created just for development work. Modern RPM-based " -"systems, including Fedora, are set up to build and test RPM packages purely " -"from within a non-privileged account." +"The tutorial proceeds in step by step manner, with most steps editing the " +"package's specfile. The final resulting specfile is listed in the end, so " +"in case there is any unclarity how a particular change should be applied, " +"you can peek there." msgstr "" #. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:50 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:37 #, no-wrap -msgid "Building the RPM" +msgid "Installing Packager Tools" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:58 -msgid "" -"We need the source code of the project we are packaging, often referred to " -"as the _upstream_ source. We will download it from the project's website " -"into a directory we create for packaging GNU Hello. We are getting the " -"compressed tarball archive, which happens to be the preferred distribution " -"form for most FOSS projects." +#: pages/Packaging_Tutorial_GNU_Hello.adoc:40 +msgid "Follow xref:Installing_Packager_Tools.adoc[Installing Packager Tools]." msgstr "" -#. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:62 +#. type: Title == +#: pages/Packaging_Tutorial_GNU_Hello.adoc:42 #, no-wrap -msgid "" -"$ mkdir hello && cd hello\n" -"$ wget http://ftp.gnu.org/gnu/hello/hello-2.10.tar.gz\n" +msgid "Creating the package directory" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:66 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:51 msgid "" -"The RPM package is configured by `.spec` files. We will create a template " -"file `hello.spec`:" +"In Fedora, package build instructions are organized in so called dist-git " +"repositories. There is a separate repository for each package. We mimick " +"this system by creating a new directory for this tutorial. In dist-git, the " +"repository name matches the package name. Fedora's rules for naming " +"packages are written in https://docs.fedoraproject.org/en-US/packaging-" +"guidelines/Naming/[Naming Guidelines]. For GNU Hello, package can simply be " +"named `hello`. This is also the name of Fedora's https://packages." +"fedoraproject.org/pkgs/hello/hello/[official GNU Hello package]." msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:69 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:54 #, no-wrap -msgid "$ rpmdev-newspec hello\n" +msgid "$ mkdir hello && cd hello\n" msgstr "" #. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:72 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:57 #, no-wrap msgid "Inside a Spec File" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:77 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:63 msgid "" -"The fields in our `.spec` file need slight editing. Please follow " -"https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/[Creating " -"RPM Packages] for these fields. In our case, the file might start as " -"follows:" +"RPM packages are configured by `.spec` files. Tools such was `rpmdev-" +"newspec` can be used to generate empty specfiles for different purposes. " +"For this tutorial, just create a file called `hello.spec` and paste the " +"following minimal specfile. It does not work yet, but we will try to build " +"it and fix errors as we encounter them." msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:87 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:73 #, no-wrap msgid "" "Name: hello\n" "Version: 2.10\n" -"Release: 1%{?dist}\n" +"Release: %autorelease\n" "Summary: Produces a familiar, friendly greeting\n" -"License: GPLv3+\n" +"License: GPL-3.0-or-later\n" "URL: https://www.gnu.org/software/hello/\n" -"Source0: https://ftp.gnu.org/gnu/hello/hello-%{version}.tar.gz\n" +"Source: http://ftp.gnu.org/gnu/hello/hello-%{version}.tar.gz\n" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:92 -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:404 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:78 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:554 #, no-wrap msgid "" "%description\n" "The GNU Hello program produces a familiar, friendly greeting. Yes, this is\n" -"another implementation of the classic program that prints “Hello, world!” " -"when\n" +"another implementation of the classic program that prints \"Hello, world!\" when\n" "you run it.\n" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:95 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:81 #, no-wrap msgid "" "%prep\n" @@ -179,8 +150,7 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:99 -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:413 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:85 #, no-wrap msgid "" "%build\n" @@ -189,7 +159,7 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:102 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:88 #, no-wrap msgid "" "%install\n" @@ -197,115 +167,223 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:104 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:90 #, no-wrap msgid "%files\n" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:108 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:93 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:583 #, no-wrap msgid "" "%changelog\n" -"* Sat Oct 23 2021 The Coon of Ty - 2.10-1\n" -"- Initial version of the package\n" +"%autochangelog\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:98 +msgid "" +"The specfile starts with a set of _tags_, such as `Name:` and `Version:`, " +"followed by _sections_ such as `%description` and `%prep`. Each tag fits " +"into a single line, whereas each section continues until the next one starts." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:102 +msgid "" +"Note that, confusingly, in addition to marking the section names, the " +"percent sign `%` also marks RPM _macros_. Thus e.g. `%autosetup`, " +"`%configure` and `%make_build` are not sections." +msgstr "" + +#. type: Title === +#: pages/Packaging_Tutorial_GNU_Hello.adoc:103 +#, no-wrap +msgid "Tags" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:106 +msgid "`+Version+` contains the version number of the packaged software." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:112 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:112 msgid "" -"The `+Version+` should mirror the upstream, while `+Release+` numbers our " -"work within Fedora." +"`+Release+` numbers specfile updates, package rebuilds and other work within " +"Fedora. The value used here, `+%autorelease+`, is part of https://docs." +"pagure.org/fedora-infra.rpmautospec/index.html[rpmautospec], which is " +"https://fedoraproject.org/wiki/Changes/Rpmautospec_by_Default[recommended " +"for Fedora packages]. It ties `+Release+` to package's Git history. As we " +"do not have a Git repository, `%autorelease` will evaluate to the default " +"value of 1." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:115 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:116 msgid "" -"The first letter of the `+Summary+` should be uppercase to avoid `+rpmlint+` " -"complaints." +"Often, `+Summary+` can be copied from the upstream README. The first letter " +"should be uppercase to avoid `+rpmlint+` complaints." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:117 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:122 msgid "" -"Often, `+Summary+` and `+%description+` can be copied from the upstream " -"README." +"`+License+` describes the license of the resulting binary package using a " +"SPDX license identifier. It must follow Fedora's https://docs.fedoraproject." +"org/en-US/legal/license-field/[licensing guidelines]. In practice, " +"determining the correct value often means inspecting the license " +"notifications in individual source files. Upstream developers may also need " +"to be asked for clarifications or corrections. In this tutorial, we just " +"take the upstream's word that the license is the GNU Public License, version " +"3 or later." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:121 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:124 +msgid "`+URL+` points to upstream project's website." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:129 +msgid "" +"`+Source+` defines the upstream sources used when building the package. " +"Usually, as in this case, it is a url pointing to a tarball released by the " +"upstream, but it can also be a local file. There can be multiple `+Source+` " +"tags if needed." +msgstr "" + +#. type: Title === +#: pages/Packaging_Tutorial_GNU_Hello.adoc:130 +#, no-wrap +msgid "Sections" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:133 +msgid "`+%description+` can often be copied from upstream README." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:137 msgid "" -"It is your responsibility to check the `+License+` status of the software. " -"Inspect the source files and their `+LICENSE+` files, and talk to the " -"authors as needed." +"`%prep` contains a shell script for preparing the sources for building. It " +"is often just the single macro `%autosetup`, which, in this case, simply " +"extracts the source." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:130 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:143 msgid "" -"The `+%changelog+` should document the work on preparing the RPM, especially " -"if there are security and bug patches included on top of the base upstream " -"source. Changelog data can be displayed by `+rpm --changelog -q " -"PACKAGE_NAME+`, which is very useful, for instance, to find out if specific " -"bug and security patches were included in the installed software, thanks to " -"the diligent Fedora packagers who include this info with the relevant " -"https://cve.mitre.org/[CVE] numbers." +"`%build` contains a shell script for the required build steps, such as " +"compiling sources to binaries. GNU Hello uses https://www.gnu.org/software/" +"automake/manual/html_node/Autotools-Introduction.html[Autotools] as its " +"buildsystem, so building involves running `configure` and `make`. Macros " +"`%configure` and `%make_build` invoke these commands using Fedora's " +"compilation flags and other configuration." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:133 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:146 msgid "" -"The `+%changelog+` entry should include the version string to avoid " -"`+rpmlint+` complaints." +"`%install` contains a shell script to copy the results from `%build` into an " +"initially empty _build root_ directory. As GNU Hello is using Autotools, " +"macro `%make_install` is used." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:137 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:151 msgid "" -"Multi-line sections like `+%changelog+` or `+%description+` start on a line " -"under the directive, and end when the next section starts or the file ends." +"`%files` lists the content of the resulting package. Mostly, the files come " +"from the build root created in the `%install`, but documentation and license " +"files can also be added directly from the sources. This section is left " +"empty for now, to be filled later." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:140 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:158 msgid "" -"Lines which are not needed (e.g. `+BuildRequires+` and `+Requires+`) can be " -"commented out with the hash `+#+` for now." +"The `+%changelog+` documents the changes in each new package version and " +"release. Changelog data can be displayed by `+rpm --query --changelog " +"PACKAGE_NAME+`, which can be useful, for instance, to find out if specific " +"bug and security patches are included. Its value,`+%autochangelog+`, also " +"comes from `rpmautospec`. It populates the changelog from Git commit " +"messages. As we do not have a Git repository, the changelog will be empty." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:160 +msgid "Lines which are not needed can be commented out with the hash `+#+`." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:144 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:162 msgid "" -"In many cases, many lines in the template do not need to be changed at all, " -"at least for the initial attempt." +"You can find more information in the RPM Reference Manual's section https://" +"rpm-software-management.github.io/rpm/manual/spec.html[Spec file format]." msgstr "" #. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:145 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:163 +#, no-wrap +msgid "Downloading source" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:167 +msgid "" +"We need the source code defined by the `+Source+` tag, often referred to as " +"the _upstream_ source. This is most easily achieved by using the `spectool` " +"command:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:170 +#, no-wrap +msgid "$ spectool -g hello.spec\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:173 +msgid "" +"You should now have the file listed in `+Source+` in your working directory:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:177 +#, no-wrap +msgid "" +"$ ls *.tar.gz\n" +"hello-2.10.tar.gz \n" +msgstr "" + +#. type: Title == +#: pages/Packaging_Tutorial_GNU_Hello.adoc:179 #, no-wrap msgid "Building the Package" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:156 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:190 msgid "" "We are ready for the first run to build source, binary and debugging " "packages. This, and many other tasks, are done with the `fedpkg` tool. The " -"production builds for Fedora are built in the " -"https://koji.fedoraproject.org[Koji] build system, which in turn uses " -"https://rpm-software-management.github.io/mock/[Mock] to manage isolated " -"build environments. To get as close to a production build as is locally " -"possible, we use the `fedpkg mockbuild` command which also invokes Mock:" +"production builds for Fedora are built in the https://koji.fedoraproject." +"org[Koji] build system, which in turn uses https://rpm-software-management." +"github.io/mock/[Mock] to manage isolated build environments. To get as " +"close to a production build as is locally possible, we use the `fedpkg " +"mockbuild` command which also invokes Mock:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:159 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:194 #, no-wrap -msgid "$ fedpkg --release rawhide mockbuild\n" +msgid "$ fedpkg --release f{MAJOROSVER} mockbuild\n" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:165 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:200 msgid "" "The build environment created by Mock is very basic. It does not include a " "C compiler by default, so the build will fail. The reason is explained in " @@ -313,7 +391,7 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:173 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:208 #, no-wrap msgid "" "checking whether the C compiler works... no\n" @@ -325,16 +403,16 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:181 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:216 msgid "" "Additional build tools are defined by adding `+BuildRequires:+` rows to the " "specfile. In Fedora, GCC is the standard compiler, so we need to add a row " "for `+gcc+`. GNU Hello also uses `+make+`, so a row should be added for it, " -"too. Add these lines after `Source0`:" +"too. Add these lines after `Source`:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:185 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:221 #, no-wrap msgid "" "BuildRequires: gcc\n" @@ -342,18 +420,18 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:189 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:225 msgid "Run a mockbuild again. The earlier error should be gone." msgstr "" #. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:190 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:226 #, no-wrap msgid "Installing files" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:200 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:236 msgid "" "The next thing rpm will complain about are unpackaged files, i.e. the files " "that would be installed in the system, but were not declared as belonging to " @@ -364,18 +442,18 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:202 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:238 msgid "We will go through the file list one by one." msgstr "" #. type: Title === -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:203 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:239 #, no-wrap msgid "Executable" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:208 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:244 #, no-wrap msgid "" "Installed (but unpackaged) file(s) found:\n" @@ -383,17 +461,17 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:215 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:251 msgid "" "This is the executable binary program. `+/usr/bin+`, like many other system " -"directories, have a " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/RPMMacros/#_macros_for_paths_set_and_used_by_build_systems[default " -"rpm macro] defined. The macros should always be used when available, so the " -"executable is listed in `+%files+` as follows:" +"directories, have a xref:packaging-guidelines::RPMMacros." +"adoc#macros_installation[default rpm macro] defined. The macros should " +"always be used when available, so the executable is listed in `+%files+` as " +"follows:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:219 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:256 #, no-wrap msgid "" "%files\n" @@ -401,13 +479,13 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:221 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:258 #, no-wrap msgid "Man pages" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:226 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:263 #, no-wrap msgid "" "Installed (but unpackaged) file(s) found:\n" @@ -415,27 +493,27 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:231 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:268 msgid "" -"The Packaging Guidelines have dedicated section for " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/#_manpages[Manpages]. " -"Following its instructions, manpages are list as follows:" +"The Packaging Guidelines have a dedicated section for xref:packaging-" +"guidelines::index.adoc#_manpages[Manpages]. Following its instructions, " +"manpages are list as follows:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:234 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:272 #, no-wrap msgid "%{_mandir}/man1/hello.1.*\n" msgstr "" #. type: Title === -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:236 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:274 #, no-wrap msgid "Texinfo pages" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:242 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:280 #, no-wrap msgid "" "Installed (but unpackaged) file(s) found:\n" @@ -444,7 +522,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:247 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:285 msgid "" "Texinfo pages are handled much in the same way as man pages. The directory " "is defined by the default macro `+{_infodir}+`, so the Texinfo manual can be " @@ -452,38 +530,55 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:250 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:289 #, no-wrap msgid "%{_infodir}/hello.info.*\n" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:259 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:297 msgid "" -"The https://src.fedoraproject.org/rpms/texinfo[texinfo package] has rpm " -"triggers that automatically generate the Texinfo `+dir+` file from all the " -"texinfo pages in the system. Thus, the `+dir+` generated by GNU Hello build " -"script must not be installed. This is done by calling `+rm+` in " -"`+%install+`. However, note that files are installed in the _buildroot_ " -"directory, and thus the removal is done like this:" +"The `+dir+` file generated by GNU Hello build script indexes all texinfo " +"pages in your system. Because the installed pages differ among systems, the " +"file cannot be prebuilt and packaged. Instead it needs to be created and " +"updated when the package is installed. The update is automaticlly performed " +"by rpm triggers in `+info+` binary package of https://src.fedoraproject.org/" +"rpms/texinfo[texinfo source package]." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:300 +msgid "" +"To prevent from installing the `+dir+` file, remove it from the _buildroot_ " +"at the end of the `+%install+` section with `+rm+` command." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:305 +msgid "" +"However, GNU Hello build script only generates the `+dir+` file if `+info+` " +"package is installed during the build. Blindly removing the file would raise " +"an error if the `+hello+` package were built on a system without `+info+` " +"package. To deal with both cases, delete the file if it exists:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:263 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:311 #, no-wrap msgid "" "%install\n" -"rm %{buildroot}/%{_infodir}/dir\n" +"%make_install\n" +"test -f %{buildroot}/%{_infodir}/dir && rm %{buildroot}/%{_infodir}/dir\n" msgstr "" #. type: Title === -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:265 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:313 #, no-wrap msgid "Translations" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:273 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:321 #, no-wrap msgid "" "Installed (but unpackaged) file(s) found:\n" @@ -494,59 +589,59 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:279 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:327 msgid "" "Since our program uses translations and internationalization, we are seeing " -"a lot of undeclared i18n files. The " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/#_handling_locale_files[recommended " -"method] to declare them is:" +"a lot of undeclared i18n files. The xref:packaging-guidelines::index." +"adoc#handling_locale_files[recommended method] to declare them is:" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:281 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:329 msgid "Add the required build dependency with `+BuildRequires: gettext+`." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:282 -msgid "Find the filenames in the `+%install+` step with `+%find_lang %{name}+`." +#: pages/Packaging_Tutorial_GNU_Hello.adoc:330 +msgid "" +"Find the filenames in the `+%install+` step with `+%find_lang %{name}+`." msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:283 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:331 msgid "Install the files with `+%files -f %{name}.lang+`." msgstr "" #. type: Title === -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:284 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:332 #, no-wrap msgid "License file" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:293 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:341 msgid "" "Every package must install its license, tagged with `+%license+` directive. " "In GNU Hello's case, as well as for many other projects, the license file is " -"located the source tarball's top level, and perhaps not copied to the " +"located at the source tarball's top level, and perhaps not copied to the " "buildroot during installation at all. Regardless, it can be installed to " "the standard license directory by using a relative path:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:296 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:345 #, no-wrap msgid "%license COPYING\n" msgstr "" #. type: Title === -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:298 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:347 #, no-wrap msgid "Additional documentation" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:306 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:355 msgid "" "Often, package sources contain documentation that could be useful for the " "end users as well. These can be installed and marked as documentation with " @@ -556,19 +651,19 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:309 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:359 #, no-wrap msgid "%doc AUTHORS ChangeLog NEWS README THANKS TODO\n" msgstr "" #. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:311 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:361 #, no-wrap msgid "Running tests" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:322 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:372 msgid "" "GNU Hello, like many other projects, includes an automated test suite in the " "sources. If at all possible, the test suite should be run during the rpm " @@ -578,8 +673,8 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:326 -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:421 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:377 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:573 #, no-wrap msgid "" "%check\n" @@ -587,14 +682,14 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:331 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:382 msgid "" "Run a mockbuild again and check the output to ensure that the tests were " "actually run. Something like this should be somewhere in the output:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:344 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:395 #, no-wrap msgid "" "============================================================================\n" @@ -611,100 +706,273 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:346 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:397 +#, no-wrap +msgid "Fixing automagic" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:401 +msgid "" +"Now the package succefully builds. But that does not mean that the `.spec` " +"file is correct." +msgstr "" + +#. type: Title === +#: pages/Packaging_Tutorial_GNU_Hello.adoc:402 +#, no-wrap +msgid "Listing all build-time dependencies" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:406 +msgid "" +"If you carefully read a build output, you can discover lines which mention " +"`+sed+` command:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:411 +#, no-wrap +msgid "" +"+ /usr/bin/make -O -j4 V=1 VERBOSE=1\n" +"rm -f lib/arg-nonnull.h-t lib/arg-nonnull.h && \\\n" +"sed -n -e '/GL_ARG_NONNULL/,$p' \\\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:414 +msgid "Therefore you need to add this line close to other BuildRequires lines:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:418 +#, no-wrap +msgid "BuildRequires: sed\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:422 +msgid "" +"Smilarly, studying `+configure+` script in the unpackaged sources, which is " +"executed by `+%configure+` macro, reveals it's a `/bin/sh` script:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:428 +#, no-wrap +msgid "" +"$ head configure\n" +"#! /bin/sh\n" +"# Guess values for system-dependent variables and create Makefiles.\n" +"# Generated by GNU Autoconf 2.69 for GNU Hello 2.10.\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:431 +msgid "Thus you also should record this dependency on `+bash+`:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:435 +#, no-wrap +msgid "BuildRequires: bash\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:438 +msgid "" +"Why on `+bash+`? Because `+/bin/sh+` program is provided by `+bash+` package:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:442 +#, no-wrap +msgid "" +"rpm --qf '%{name}\\n' -qf /bin/sh\n" +"bash\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:447 +msgid "" +"Specifying all used dependencies helps to make the `.spec` file resilient " +"against changes in the build environment. If e.g. `+sed+` package were " +"removed from the environment, this GNU Hello package would fail to build." +msgstr "" + +#. type: Title === +#: pages/Packaging_Tutorial_GNU_Hello.adoc:448 +#, no-wrap +msgid "Listing all build options" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:453 +msgid "" +"The GNU Hello build script, `+configure+` has many build options which " +"enables or disables optional features. Their nondefault forms can be listed " +"with `+--help+` option:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:457 +#, no-wrap +msgid "" +"$ ./configure --help\n" +"`configure' configures GNU Hello 2.10 to adapt to many kinds of systems.\n" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:472 +#, no-wrap +msgid "" +"Usage: ./configure [OPTION]... [VAR=VALUE]...\n" +"⋮\n" +"Optional Features:\n" +" --disable-option-checking ignore unrecognized --enable/--with options\n" +" --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)\n" +" --enable-FEATURE[=ARG] include FEATURE [ARG=yes]\n" +" --enable-silent-rules less verbose build output (undo: \"make V=1\")\n" +" --disable-silent-rules verbose build output (undo: \"make V=0\")\n" +" --enable-dependency-tracking\n" +" do not reject slow dependency extractors\n" +" --disable-dependency-tracking\n" +" speeds up one-time build\n" +" --disable-nls do not use Native Language Support\n" +" --disable-rpath do not hardcode runtime library paths\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:480 +msgid "" +"Some of them are already specified within `+%configure+` and `+%make_build+` " +"macros. The rest of the options, if they are important for the built " +"package, should be explicitly written in the `.spec` file to prevent from " +"their sudden and unnoticed changes. Either because a new Hello version " +"changes the default, or because a package which they depend on appears of " +"disappears from the build environment." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:482 +msgid "" +"Therefore modify `+%configure+` invocation in `+%build+` section like this:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:489 +#, no-wrap +msgid "" +"%configure \\\n" +" --enable-nls \\\n" +" --disable-rpath\n" +msgstr "" + +#. type: Title == +#: pages/Packaging_Tutorial_GNU_Hello.adoc:491 #, no-wrap msgid "Checking the result with rpmlint" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:356 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:496 msgid "" "Next you should check them for conformance with RPM design rules, by running " "`rpmlint` on specfile, source rpm and binary rpm. Command `+fedpkg lint+` " -"_should_ do this, but as of version 1.41, it suffers from a bug causing it " -"not to find the rpms created by `+fedpkg mockbuild+`. So instead, " -"`+rpmlint+` needs to be called directly. Pass files to check as arguments:" +"does this:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:360 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:500 #, no-wrap -msgid "" -"$ rpmlint hello.spec " -"results_hello/2.10/1.fc{NEXTOSVER}/hello-2.10*.{x86_64,src}.rpm\n" +msgid "$ fedpkg --release f{MAJOROSVER} lint\n" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:365 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:505 msgid "" "If all is good, there should be no warnings or errors. In the GNU Hello " "case, one warning can be expected:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:368 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:508 #, no-wrap msgid "hello.x86_64: W: file-not-utf8 /usr/share/doc/hello/THANKS\n" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:375 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:516 msgid "" "Descriptions of various error codes can be queried with `+rpmlint -e " "+`. In this case, in order to ensure a pure utf-8 installation, " "the file needs to be converted in `+%prep+`. This can be done with the " -"`+iconv+` utility:" +"`+iconv+` utility which is provided by `+glibc-common+` package, and `+mv+` " +"tool from `+coreutils+`:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:379 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:523 #, no-wrap msgid "" +"BuildRequires: coreutils\n" +"BuildRequires: glibc-common\n" +"⋮\n" "mv THANKS THANKS.old\n" "iconv --from-code=ISO-8859-1 --to-code=UTF-8 --output=THANKS THANKS.old\n" msgstr "" +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:526 +msgid "Run `fedpkg lint` again and observe that the warning is fixed." +msgstr "" + #. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:381 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:527 #, no-wrap msgid "A Complete hello.spec File" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:384 -msgid "Here is the initial version of `hello.spec`:" +#: pages/Packaging_Tutorial_GNU_Hello.adoc:530 +msgid "Here is the final version of `hello.spec`:" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:391 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:537 #, no-wrap msgid "" "Name: hello\n" "Version: 2.10\n" -"Release: 1%{?dist}\n" +"Release: %autorelease\n" "Summary: Produces a familiar, friendly greeting\n" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:395 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:541 #, no-wrap msgid "" -"License: GPLv3+\n" +"License: GPL-3.0-or-later\n" "URL: http://ftp.gnu.org/gnu/%{name}\n" -"Source0: http://ftp.gnu.org/gnu/%{name}/%{name}-%{version}.tar.gz\n" +"Source: http://ftp.gnu.org/gnu/%{name}/%{name}-%{version}.tar.gz\n" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:399 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:549 #, no-wrap msgid "" +"BuildRequires: bash\n" +"BuildRequires: coreutils\n" "BuildRequires: gcc\n" "BuildRequires: gettext\n" +"BuildRequires: glibc-common\n" "BuildRequires: make\n" +"BuildRequires: sed\n" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:409 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:559 #, no-wrap msgid "" "%prep\n" @@ -714,17 +982,28 @@ msgid "" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:418 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:565 +#, no-wrap +msgid "" +"%build\n" +"%configure \\\n" +" --enable-nls \\\n" +" --disable-rpath\n" +"%make_build\n" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:570 #, no-wrap msgid "" "%install\n" "%make_install\n" -"rm %{buildroot}/%{_infodir}/dir\n" +"test -f %{buildroot}/%{_infodir}/dir && rm %{buildroot}/%{_infodir}/dir\n" "%find_lang %{name}\n" msgstr "" #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:428 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:580 #, no-wrap msgid "" "%files -f %{name}.lang\n" @@ -735,54 +1014,299 @@ msgid "" "%license COPYING\n" msgstr "" +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:588 +msgid "" +"With this `.spec` file, you should be able to successfully complete the " +"build process, and create the source and binary RPM packages." +msgstr "" + +#. type: Title == +#: pages/Packaging_Tutorial_GNU_Hello.adoc:589 +#, no-wrap +msgid "Checking the result" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:596 +msgid "" +"Having a working specfile and rpms built from it, the result can be " +"checked. Before checking the result by installing the package, let us do " +"some simple checks. The RPM Package Manager `rpm` can be used for this." +msgstr "" + +#. type: Title === +#: pages/Packaging_Tutorial_GNU_Hello.adoc:597 +#, no-wrap +msgid "Files" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:600 +msgid "List the files contained in the package:" +msgstr "" + #. type: delimited block - -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:432 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:622 #, no-wrap msgid "" -"%changelog\n" -"* Sat Oct 23 2021 The Coon of Ty 2.10-1\n" -"- Initial version of the package\n" +"$ rpm --query --package --list results_hello/2.10/1.fc{MAJOROSVER}/hello-2.10-1.fc{MAJOROSVER}.x86_64.rpm\n" +"/usr/bin/hello\n" +"/usr/lib/.build-id\n" +"/usr/lib/.build-id/39\n" +"/usr/lib/.build-id/39/c97ecb15c6292ce23e8b00e15e6e72a61e5072\n" +"/usr/share/doc/hello\n" +"/usr/share/doc/hello/AUTHORS\n" +"/usr/share/doc/hello/ChangeLog\n" +"/usr/share/doc/hello/NEWS\n" +"/usr/share/doc/hello/README\n" +"/usr/share/doc/hello/THANKS\n" +"/usr/share/doc/hello/TODO\n" +"/usr/share/info/hello.info.gz\n" +"/usr/share/licenses/hello\n" +"/usr/share/licenses/hello/COPYING\n" +"/usr/share/locale/bg/LC_MESSAGES/hello.mo\n" +"...\n" +"/usr/share/locale/zh_TW/LC_MESSAGES/hello.mo\n" +"/usr/share/man/man1/hello.1.gz\n" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:437 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:630 msgid "" -"With this `.spec` file, you should be able to successfully complete the " -"build process, and create the source and binary RPM packages." +"You can see that all the files listed in the specfile `+%files+` section are " +"included, including the automatically processed locale files. Also, under " +"`+/usr/lib/.build-id+`, there is an automatically generated file. It is " +"actually a symlink, mapping a build id to the `+hello+` binary for debugging " +"purposes." +msgstr "" + +#. type: Title === +#: pages/Packaging_Tutorial_GNU_Hello.adoc:631 +#, no-wrap +msgid "Requires" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:634 +msgid "List the package's runtime dependencies with the following command:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:651 +#, no-wrap +msgid "" +"$ rpm --query --package --requires results_hello/2.10/1.fc{MAJOROSVER}/hello-2.10-1.fc{MAJOROSVER}.x86_64.rpm\n" +"libc.so.6()(64bit)\n" +"libc.so.6(GLIBC_2.14)(64bit)\n" +"libc.so.6(GLIBC_2.2.5)(64bit)\n" +"libc.so.6(GLIBC_2.3)(64bit)\n" +"libc.so.6(GLIBC_2.3.4)(64bit)\n" +"libc.so.6(GLIBC_2.34)(64bit)\n" +"libc.so.6(GLIBC_2.4)(64bit)\n" +"libc.so.6(GLIBC_2.7)(64bit)\n" +"rpmlib(CompressedFileNames) <= 3.0.4-1\n" +"rpmlib(FileDigests) <= 4.6.0-1\n" +"rpmlib(PayloadFilesHavePrefix) <= 4.0-1\n" +"rpmlib(PayloadIsZstd) <= 5.4.18-1\n" +"rtld(GNU_HASH)\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:655 +msgid "" +"To check which packages in Fedora repositories provide these dependencies, " +"you can use `dnf repoquery`:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:661 +#, no-wrap +msgid "" +"$ dnf -C repoquery --whatprovides 'libc.so.6()(64bit)'\n" +"glibc-0:2.34-11.fc{MAJOROSVER}.x86_64\n" +"glibc-0:2.34-7.fc{MAJOROSVER}.x86_64\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:665 +msgid "" +"You will see that the only dependency of GNU Hello is `+glibc+`, which " +"provides symbols in `+libc.so.6+` as well as `+rtld(GNU_HASH)+`." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:669 +msgid "" +"The `+rpmlib+` requires are special. These specify various rpm features " +"used in the rpm package itself, constraining the version of `+rpm+` that can " +"be used to install the package." +msgstr "" + +#. type: Title === +#: pages/Packaging_Tutorial_GNU_Hello.adoc:670 +#, no-wrap +msgid "Provides" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:673 +msgid "" +"Conversely, to check what capabilities the package provides, you can do:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:679 +#, no-wrap +msgid "" +"$ rpm --query --package --provides results_hello/2.10/1.fc{MAJOROSVER}/hello-2.10-1.fc{MAJOROSVER}.x86_64.rpm\n" +"hello = 2.10-1.fc{MAJOROSVER}\n" +"hello(x86-64) = 2.10-1.fc{MAJOROSVER}\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:684 +msgid "" +"The provides of this package are very simple. It simply provides its own " +"name, in plain and architecture specific forms." +msgstr "" + +#. type: Title === +#: pages/Packaging_Tutorial_GNU_Hello.adoc:685 +#, no-wrap +msgid "Installing" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:688 +msgid "As a final check, the package can be installed and ran:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:694 +#, no-wrap +msgid "" +"$ sudo dnf -C -y install ./results_hello/2.10/1.fc{MAJOROSVER}/hello-2.10-1.fc{MAJOROSVER}.x86_64.rpm\n" +"$ hello --greeting=\"Hello, rpm!\"\n" +"Hello, rpm!\n" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:697 +msgid "To clean up your system, undo the installation:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:700 +#, no-wrap +msgid "$ sudo dnf -C -y history undo last\n" msgstr "" #. type: Title == -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:438 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:702 #, no-wrap -msgid "References" +msgid "Building in Fedora infrastructure" +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:709 +msgid "" +"Even though the package is not part of Fedora distribution yet, a xref:" +"Using_the_Koji_Build_System.adoc#scratch_builds[scratch build] can be " +"performed to ensure that the package builds successfully in Fedora's Koji " +"build system, and that it builds successfully for all architectures " +"supported by Fedora. Such build is started by passing a source rpm package " +"to `fedpkg scratch-build`." +msgstr "" + +#. type: Plain text +#: pages/Packaging_Tutorial_GNU_Hello.adoc:712 +msgid "" +"Note that Koji uses Kerberos for authentication. See xref:" +"Installing_Packager_Tools.adoc#kerberos_ticket[Acquiring Kerberos Ticket] " +"for details." +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:720 +#, no-wrap +msgid "" +"$ fedpkg --release f{MAJOROSVER} scratch-build --srpm results_hello/2.10/1.fc{MAJOROSVER}/hello-2.10-1.fc{MAJOROSVER}.src.rpm\n" +"Building hello-2.10-1.fc{MAJOROSVER}.src.rpm for f{MAJOROSVER}-candidate\n" +"Created task: 92465688\n" +"Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=92465688\n" +"Watching tasks (this may be safely interrupted)...\n" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:441 -msgid "https://rpm-software-management.github.io/rpm/manual/[RPM Reference Manual]" +#: pages/Packaging_Tutorial_GNU_Hello.adoc:725 +msgid "" +"You can open the task info link in a browser to view build progress, logs " +"and results. The command line program also reports on progress as it " +"happens. Successful execution looks something like this:" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:751 +#, no-wrap +msgid "" +"92465688 build (f{MAJOROSVER}-candidate, hello-2.10-1.fc{MAJOROSVER}.src.rpm): free\n" +"92465688 build (f{MAJOROSVER}-candidate, hello-2.10-1.fc{MAJOROSVER}.src.rpm): free -> open (buildvm-ppc64le-25.iad2.fedoraproject.org)\n" +" 92465698 rebuildSRPM (noarch): open (buildvm-s390x-24.s390.fedoraproject.org)\n" +" 92465745 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, x86_64): free\n" +" 92465748 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, s390x): open (buildvm-s390x-19.s390.fedoraproject.org)\n" +" 92465746 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, aarch64): open (buildvm-a64-26.iad2.fedoraproject.org)\n" +" 92465747 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, ppc64le): open (buildvm-ppc64le-11.iad2.fedoraproject.org)\n" +" 92465744 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, i686): open (buildhw-x86-12.iad2.fedoraproject.org)\n" +" 92465698 rebuildSRPM (noarch): open (buildvm-s390x-24.s390.fedoraproject.org) -> closed\n" +" 1 free 5 open 1 done 0 failed\n" +" 92465745 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, x86_64): free -> open (buildhw-x86-06.iad2.fedoraproject.org)\n" +" 92465745 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, x86_64): open (buildhw-x86-06.iad2.fedoraproject.org) -> closed\n" +" 0 free 5 open 2 done 0 failed\n" +" 92465748 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, s390x): open (buildvm-s390x-19.s390.fedoraproject.org) -> closed\n" +" 0 free 4 open 3 done 0 failed\n" +" 92465746 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, aarch64): open (buildvm-a64-26.iad2.fedoraproject.org) -> closed\n" +" 0 free 3 open 4 done 0 failed\n" +" 92465744 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, i686): open (buildhw-x86-12.iad2.fedoraproject.org) -> closed\n" +" 0 free 2 open 5 done 0 failed\n" +"92465688 build (f{MAJOROSVER}-candidate, hello-2.10-1.fc{MAJOROSVER}.src.rpm): open (buildvm-ppc64le-25.iad2.fedoraproject.org) -> closed\n" +" 0 free 1 open 6 done 0 failed\n" +" 92465747 buildArch (hello-2.10-1.fc{MAJOROSVER}.src.rpm, ppc64le): open (buildvm-ppc64le-11.iad2.fedoraproject.org) -> closed\n" +" 0 free 0 open 7 done 0 failed\n" +msgstr "" + +#. type: delimited block - +#: pages/Packaging_Tutorial_GNU_Hello.adoc:753 +#, no-wrap +msgid "92465688 build (f{MAJOROSVER}-candidate, hello-2.10-1.fc{MAJOROSVER}.src.rpm) completed successfully\n" +msgstr "" + +#. type: Title == +#: pages/Packaging_Tutorial_GNU_Hello.adoc:755 +#, no-wrap +msgid "References" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:443 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:758 msgid "" -"https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/[Creating " -"RPM packages]" +"https://rpm-software-management.github.io/rpm/manual/[RPM Reference Manual]" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:445 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:760 msgid "" "https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock " "to test package builds]" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:447 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:762 msgid "xref:Using_the_Koji_Build_System.adoc[Using the Koji build system]" msgstr "" #. type: Plain text -#: ./pages/Packaging_Tutorial_GNU_Hello.adoc:448 +#: pages/Packaging_Tutorial_GNU_Hello.adoc:763 msgid "" "https://www.redhat.com/sysadmin/create-rpm-package[How to create a Linux RPM " "package]" diff --git a/po/fr/master/pages/Reporting_Issues.po b/po/fr/master/pages/Reporting_Issues.po index 8d137b3..a00b0e6 100644 --- a/po/fr/master/pages/Reporting_Issues.po +++ b/po/fr/master/pages/Reporting_Issues.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-12-03 21:58+0000\n" +"POT-Creation-Date: 2023-01-04 22:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,18 +17,13 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #. type: Title = -#: ./pages/Reporting_Issues.adoc:1 +#: pages/Reporting_Issues.adoc:1 #, no-wrap msgid "Reporting Issues" msgstr "" #. type: Plain text -#: ./pages/Reporting_Issues.adoc:3 -msgid ":toc" -msgstr "" - -#. type: Plain text -#: ./pages/Reporting_Issues.adoc:11 +#: pages/Reporting_Issues.adoc:10 msgid "" "When working with Fedora Packaging, you may run across issues in packages, " "with the buildsystem, with policies or process, or with any number of other " @@ -37,13 +32,13 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Reporting_Issues.adoc:13 +#: pages/Reporting_Issues.adoc:12 #, no-wrap msgid "Where to Report Issues" msgstr "" #. type: Plain text -#: ./pages/Reporting_Issues.adoc:19 +#: pages/Reporting_Issues.adoc:18 msgid "" "Any issue that requires direct work on Fedora's infrastructure should be " "reported using the https://pagure.io/fedora-infrastructure/issues[Fedora " @@ -52,26 +47,24 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Reporting_Issues.adoc:23 +#: pages/Reporting_Issues.adoc:22 msgid "" -"For issues within packages, see " -"https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to " -"File a Bug]. This would include typical build errors." +"For issues within packages, see xref:quick-docs::howto-file-a-bug.adoc[How " +"to File a Bug]. This would include typical build errors." msgstr "" #. type: Plain text -#: ./pages/Reporting_Issues.adoc:27 +#: pages/Reporting_Issues.adoc:26 msgid "" -"Any questions about policy or processes should be reported to the " -"https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel] " +"Any questions about policy or processes should be reported to the https://" +"lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel] " "mailing list. This would include questions of spec design, naming " "conventions or review concerns." msgstr "" #. type: Plain text -#: ./pages/Reporting_Issues.adoc:30 +#: pages/Reporting_Issues.adoc:29 msgid "" "If ever you are unsure about which system to use, feel free to report to " -"whichever system seems best to you. Your report can be redirected as " -"needed." +"whichever system seems best to you. Your report can be redirected as needed." msgstr "" diff --git a/po/fr/master/pages/Staying_Close_to_Upstream_Projects.po b/po/fr/master/pages/Staying_Close_to_Upstream_Projects.po index bb77d7b..b202d48 100644 --- a/po/fr/master/pages/Staying_Close_to_Upstream_Projects.po +++ b/po/fr/master/pages/Staying_Close_to_Upstream_Projects.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-01-04 22:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,15 +16,14 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Staying_close_to_upstream_projects #. type: Title = -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:3 +#: pages/Staying_Close_to_Upstream_Projects.adoc:1 #, no-wrap msgid "Staying Close to Upstream Projects" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:15 +#: pages/Staying_Close_to_Upstream_Projects.adoc:12 msgid "" "The Fedora Project focuses, as much as possible, on not deviating from " "upstream in the software it includes in the repository. The following " @@ -36,13 +35,13 @@ msgid "" msgstr "" #. type: Labeled list -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:16 +#: pages/Staying_Close_to_Upstream_Projects.adoc:13 #, no-wrap msgid "upstream (noun)" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:23 +#: pages/Staying_Close_to_Upstream_Projects.adoc:20 msgid "" "In free and open source projects, the _upstream_ of a program or set of " "programs is the project that develops those programs. Fedora is " @@ -52,35 +51,34 @@ msgid "" msgstr "" #. type: Labeled list -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:24 +#: pages/Staying_Close_to_Upstream_Projects.adoc:21 #, no-wrap msgid "to upstream (verb)" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:26 +#: pages/Staying_Close_to_Upstream_Projects.adoc:23 msgid "A short-hand way of saying \"push changes to the upstream project\"." msgstr "" #. type: Title == -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:28 +#: pages/Staying_Close_to_Upstream_Projects.adoc:25 #, no-wrap msgid "What are deviations from upstream?" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:34 +#: pages/Staying_Close_to_Upstream_Projects.adoc:31 #, no-wrap msgid "" -"*Patches*: Patches are the most common and obvious type of change from " -"upstream.\n" +"*Patches*: Patches are the most common and obvious type of change from upstream.\n" "Patches might be written by the package maintainer,\n" "cherry picked or backported from upstream\n" "or picked from other distributions.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:43 +#: pages/Staying_Close_to_Upstream_Projects.adoc:40 #, no-wrap msgid "" "*Running sed or equivalent on a spec file*:\n" @@ -89,13 +87,12 @@ msgid "" "for the purposes of this guide.\n" "Also a patch is preferable\n" "because running sed can sometimes change the software in unintended ways\n" -"especially when the package maintainer is pushing a new upstream release as " -"an update\n" +"especially when the package maintainer is pushing a new upstream release as an update\n" "and such changes might not be obvious compared to a failed patch.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:48 +#: pages/Staying_Close_to_Upstream_Projects.adoc:45 msgid "" "Desktop files, systemd unit files, etc. are sometimes added as *additional " "sources*: If you do this as a package maintainer, you need to notify " @@ -104,45 +101,38 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:57 +#: pages/Staying_Close_to_Upstream_Projects.adoc:54 #, no-wrap msgid "" "*Configuration options*:\n" -"For instance, if a particular upstream software allows both MySQL and " -"Postgres as a database backend,\n" +"For instance, if a particular upstream software allows both MySQL and Postgres as a database backend,\n" "other distributions might have picked Postgres\n" -"and Fedora package might be configured to use the MySQL backend by default " -"instead.\n" -"If upstream or other distributions are favoring one of the options over the " -"others,\n" +"and Fedora package might be configured to use the MySQL backend by default instead.\n" +"If upstream or other distributions are favoring one of the options over the others,\n" "talk to them,\n" "find out why\n" "and rely on well tested and consistent options as much as possible.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:69 +#: pages/Staying_Close_to_Upstream_Projects.adoc:66 #, no-wrap msgid "" "*Underlying libraries and other software components*:\n" "Even without intentional modifications,\n" -"software in Fedora can still be different from upstream or other " -"distributions,\n" -"due to precise library versions or other software components your package " -"depends on.\n" +"software in Fedora can still be different from upstream or other distributions,\n" +"due to precise library versions or other software components your package depends on.\n" "For instance, Firefox may expose a sqlite bug,\n" -"and Fedora might be the only distribution building that precise version of " -"Firefox\n" +"and Fedora might be the only distribution building that precise version of Firefox\n" "against that specific version of sqlite.\n" -"You should talk to upstream and find out whether there are any such known " -"issues,\n" +"You should talk to upstream and find out whether there are any such known issues,\n" "and search through upstream bug trackers \n" "or other popular distribution bug trackers\n" "to figure out such problems.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:81 +#: pages/Staying_Close_to_Upstream_Projects.adoc:78 #, no-wrap msgid "" "*Miscellaneous*:\n" @@ -159,18 +149,17 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:83 +#: pages/Staying_Close_to_Upstream_Projects.adoc:80 #, no-wrap msgid "Why push changes upstream?" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:95 +#: pages/Staying_Close_to_Upstream_Projects.adoc:92 #, no-wrap msgid "" "*Common Benefit And Reduced Maintenance Burden*:\n" -"When Fedora carries patches that are specific to Fedora or deviations from " -"upstream projects,\n" +"When Fedora carries patches that are specific to Fedora or deviations from upstream projects,\n" "those patches are not shared by every distribution.\n" "This puts the burden of maintaining those patches on Fedora,\n" "which includes keeping those patches in a functional state\n" @@ -182,16 +171,14 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:106 +#: pages/Staying_Close_to_Upstream_Projects.adoc:103 #, no-wrap msgid "" "*Documentation*:\n" "Upstream projects are documented formally\n" "(in the form of man/info pages and longer guides)\n" -"and informally in many user forums or mailing lists as answers to user " -"questions.\n" -"Deviations from upstream projects can thus confuse end users and upstream " -"developers\n" +"and informally in many user forums or mailing lists as answers to user questions.\n" +"Deviations from upstream projects can thus confuse end users and upstream developers\n" "when those patches cause changes in behavior that are Fedora specific\n" "and not documented properly,\n" "even where the formal documentation\n" @@ -200,23 +187,21 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:115 +#: pages/Staying_Close_to_Upstream_Projects.adoc:112 #, no-wrap msgid "" "*Translations*:\n" -"Maintaining translations upstream gains the advantage of established " -"translation communities,\n" +"Maintaining translations upstream gains the advantage of established translation communities,\n" "which are most likely more experienced with the project terms.\n" "Downstream projects benefit when using those translations.\n" "In addition, it lifts the burden of hosting,\n" "and of the need to merge often from upstream to downstream and back again.\n" "To make sure translation work continues upstream.\n" -"Any string changes that were introduced by patches should be maintained by " -"the downstream community.\n" +"Any string changes that were introduced by patches should be maintained by the downstream community.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:134 +#: pages/Staying_Close_to_Upstream_Projects.adoc:131 #, no-wrap msgid "" "*Upstream Acceptance*:\n" @@ -225,25 +210,22 @@ msgid "" "or lack expertise in the language(s) the software is written in.\n" "In some cases the software has a large and complex codebase\n" "(such as the kernel or Libreoffice)\n" -"and the package maintainers might not have the same level of understanding " -"in all areas\n" +"and the package maintainers might not have the same level of understanding in all areas\n" "compared to subsystem maintainers or upstream developers.\n" "For this and other reasons,\n" "Fedora needs the acceptance of upstream software developers.\n" "These developers may view any significant patches as a fork\n" "or refuse to take bug reports from Fedora users\n" "due to the differences in the codebase.\n" -"Fedora as a project strives to be welcoming and cooperative with upstream " -"developers\n" +"Fedora as a project strives to be welcoming and cooperative with upstream developers\n" "as much as possible.\n" "We must avoid Fedora specific patches\n" -"and any patches that are useful should be sent upstream to these " -"developers\n" +"and any patches that are useful should be sent upstream to these developers\n" "via mailing lists, bug trackers, or direct email.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:141 +#: pages/Staying_Close_to_Upstream_Projects.adoc:138 #, no-wrap msgid "" "*Quality Assurance*: Patches that are accepted upstream\n" @@ -251,12 +233,11 @@ msgid "" "including developers and testers.\n" "This includes testing by other GNU/Linux distributions.\n" "A deviation from the common codebase used by many\n" -"is a potential chance of introducing a regression that is specific to " -"Fedora.\n" +"is a potential chance of introducing a regression that is specific to Fedora.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:147 +#: pages/Staying_Close_to_Upstream_Projects.adoc:144 #, no-wrap msgid "" "*Security*:\n" @@ -267,25 +248,23 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:158 +#: pages/Staying_Close_to_Upstream_Projects.adoc:155 #, no-wrap msgid "" "*Fast incremental improvements*:\n" "Staying close to upstream versions is helpful\n" "when doing version bumps for updates that bring in new features.\n" "This prevents tedious backporting of only security and bug fixes.\n" -"Deviations from upstream can significantly hamper the speed of delivering " -"improvements\n" +"Deviations from upstream can significantly hamper the speed of delivering improvements\n" "from new versions to end users.\n" "However, regressions are to be avoided,\n" "and potential improvements and new features must be carefully assessed\n" "against the risk of harming the users experience.\n" -"Refer to https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/[Updates " -"Policy] for more details.\n" +"Refer to xref:fesco::Updates_Policy.adoc[Updates Policy] for more details.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:170 +#: pages/Staying_Close_to_Upstream_Projects.adoc:167 #, no-wrap msgid "" "*ABI or API Deviations*:\n" @@ -302,7 +281,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:178 +#: pages/Staying_Close_to_Upstream_Projects.adoc:175 #, no-wrap msgid "" "*Direct End User Feedback*:\n" @@ -315,13 +294,13 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:180 +#: pages/Staying_Close_to_Upstream_Projects.adoc:177 #, no-wrap msgid "Tips On Upstreaming Patches" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:188 +#: pages/Staying_Close_to_Upstream_Projects.adoc:185 msgid "" "Talk to upstream. Maintaining a regular flow of communication with the " "upstream project is helpful in understanding the upstream developers well, " @@ -331,7 +310,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:194 +#: pages/Staying_Close_to_Upstream_Projects.adoc:191 msgid "" "Make the patches generic enough to be maintained by upstream developers. " "Explain the need for your patches, that is, what bugs they fix or what " @@ -340,7 +319,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:200 +#: pages/Staying_Close_to_Upstream_Projects.adoc:197 msgid "" "Do not consider any change to be too small to be sent upstream. Even minor " "changes like fixing a permission problem in a file or excluding an empty " @@ -349,21 +328,21 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:203 +#: pages/Staying_Close_to_Upstream_Projects.adoc:200 msgid "" "Divide patches into small and independent chunks that remain functional, so " "they can be understood, reviewed, and accepted or rejected individually." msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:206 +#: pages/Staying_Close_to_Upstream_Projects.adoc:203 msgid "" "If the patch introduces new strings or changes existing ones, make the " "changes as generic as possible." msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:212 +#: pages/Staying_Close_to_Upstream_Projects.adoc:209 msgid "" "Fix your coding style to match the upstream project's guidelines. This " "might seem trivial but many upstream projects insist on following their " @@ -372,21 +351,21 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:215 +#: pages/Staying_Close_to_Upstream_Projects.adoc:212 msgid "" "Where possible, encourage upstream point-releases that fix bugs and security " "issues only, to avoid the possibility of regressions." msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:218 +#: pages/Staying_Close_to_Upstream_Projects.adoc:215 msgid "" "Test your changes as throughly as you can before you send them upstream. " "Broken patches leave a long-lasting bad impression." msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:229 +#: pages/Staying_Close_to_Upstream_Projects.adoc:226 msgid "" "Be patient and cooperative. If feedback is offered, discuss changes, answer " "questions, and provide revisions that fix any problems. Don't flame or " @@ -399,13 +378,13 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:231 +#: pages/Staying_Close_to_Upstream_Projects.adoc:228 #, no-wrap msgid "Some Examples Of Exceptions" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:250 +#: pages/Staying_Close_to_Upstream_Projects.adoc:247 #, no-wrap msgid "" "*Severe Security Issues Or Major Bug Fixes*:\n" @@ -422,23 +401,18 @@ msgid "" "can leave unexpected security holes still open\n" "or a patch to fix a major problem can worsen the problem.\n" "Get your patches peer reviewed as much as possible.\n" -"Due to differences in release schedules between upstream projects and Fedora " -"releases,\n" -"maintainers would have to keep in mind feature and development freezes in " -"Fedora\n" +"Due to differences in release schedules between upstream projects and Fedora releases,\n" +"maintainers would have to keep in mind feature and development freezes in Fedora\n" "and fix problems accordingly.\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:261 +#: pages/Staying_Close_to_Upstream_Projects.adoc:258 #, no-wrap msgid "" "*Non-free or patent encumbered software*:\n" -"If upstream projects include software that is non-free or has known patent " -"issues,\n" -"such software does not meet the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/[Licensing " -"Guidelines]\n" +"If upstream projects include software that is non-free or has known patent issues,\n" +"such software does not meet the xref:packaging-guidelines::LicensingGuidelines.adoc[Licensing Guidelines]\n" "and Fedora will not include them.\n" "In many instances, such code is optional in the form of plugins\n" "that Fedora simply does not need to include\n" @@ -449,7 +423,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:275 +#: pages/Staying_Close_to_Upstream_Projects.adoc:272 #, no-wrap msgid "" "*Unmaintained Or Unresponsive Upstream Projects*:\n" @@ -462,14 +436,13 @@ msgid "" "Be wary of maintaining software with no upstream\n" "since all the burden of maintaining the codebase\n" "as well as packaging issues are with you.\n" -"If upstream is unresponsive and many distributions are deviating " -"significantly,\n" +"If upstream is unresponsive and many distributions are deviating significantly,\n" "it might be a opportunity for a cross distribution fork\n" "(Similar to XFree86 and Xorg).\n" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:285 +#: pages/Staying_Close_to_Upstream_Projects.adoc:282 #, no-wrap msgid "" "*Patches Heading Upstream*:\n" @@ -484,12 +457,11 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:294 +#: pages/Staying_Close_to_Upstream_Projects.adoc:291 #, no-wrap msgid "" "*Distribution Integration*:\n" -"There are features that are critical or very good to have for Fedora as a " -"distribution\n" +"There are features that are critical or very good to have for Fedora as a distribution\n" "but not been significant enough\n" "for various upstream projects to accept related enhancements just yet.\n" "Use your discretion carefully when choosing to integrate any such patches\n" @@ -499,39 +471,39 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:298 +#: pages/Staying_Close_to_Upstream_Projects.adoc:295 #, no-wrap msgid "" "*Bundling of Libraries*:\n" -"Refer to the " -"https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling[Bundling " -"and Duplication of system libraries] section of the Packaging Guidelines for " -"details.\n" +"Refer to the xref:packaging-guidelines::index.adoc#bundling[Bundling and Duplication of System Libraries] section of the Packaging Guidelines for details.\n" "Fixes related to bundling should of course be sent upstream if possible.\n" msgstr "" #. type: Title == -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:299 +#: pages/Staying_Close_to_Upstream_Projects.adoc:296 #, no-wrap msgid "References" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:302 +#: pages/Staying_Close_to_Upstream_Projects.adoc:299 msgid "http://fedoraproject.org/wiki/Objectives" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:303 -msgid "https://fedoraproject.org/wiki/Packaging/Guidelines#All_patches_should_have_an_upstream_bug_link_or_comment" +#: pages/Staying_Close_to_Upstream_Projects.adoc:300 +msgid "" +"xref:packaging-guidelines::index." +"adoc#_all_patches_should_have_an_upstream_bug_link_or_comment[All patches " +"should have an upstream bug link or comment]" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:304 +#: pages/Staying_Close_to_Upstream_Projects.adoc:301 msgid "http://fedoraproject.org/wiki/PackageMaintainers/TrackingUpstream" msgstr "" #. type: Plain text -#: ./pages/Staying_Close_to_Upstream_Projects.adoc:304 +#: pages/Staying_Close_to_Upstream_Projects.adoc:301 msgid "http://fedoraproject.org/wiki/PackageMaintainers/TrackingDownstream" msgstr "" diff --git a/po/fr/master/pages/Upstream_Release_Monitoring.po b/po/fr/master/pages/Upstream_Release_Monitoring.po index ba5d654..0b72ed3 100644 --- a/po/fr/master/pages/Upstream_Release_Monitoring.po +++ b/po/fr/master/pages/Upstream_Release_Monitoring.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-03-01 22:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,71 +16,76 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Upstream_release_monitoring #. type: Title = -#: ./pages/Upstream_Release_Monitoring.adoc:3 +#: pages/Upstream_Release_Monitoring.adoc:1 #, no-wrap msgid "Upstream Release Monitoring" msgstr "" #. type: Title == -#: ./pages/Upstream_Release_Monitoring.adoc:7 +#: pages/Upstream_Release_Monitoring.adoc:4 #, no-wrap msgid "TLDR; Get Packages Monitored" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:10 +#: pages/Upstream_Release_Monitoring.adoc:7 msgid "" "Get bug reports for a project's releases in Fedora's Bugzilla with three " "steps:" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:12 +#: pages/Upstream_Release_Monitoring.adoc:9 msgid "Add the project to https://release-monitoring.org[Anitya]." msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:13 +#: pages/Upstream_Release_Monitoring.adoc:10 msgid "Map the project to a Fedora package in Anitya." msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:14 +#: pages/Upstream_Release_Monitoring.adoc:11 msgid "" -"Tweak the monitoring setting for your packages at " -"https://src.fedoraproject.org/rpms/[Fedora Package Sources]." +"Tweak the monitoring setting for your packages at https://src.fedoraproject." +"org[Fedora Package Sources]." msgstr "" #. type: Title == -#: ./pages/Upstream_Release_Monitoring.adoc:16 +#: pages/Upstream_Release_Monitoring.adoc:13 #, no-wrap msgid "Bugzilla bugs by the-new-hotness" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:19 +#: pages/Upstream_Release_Monitoring.adoc:16 msgid "" -"https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&bug_status=POST&classification=Fedora&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Copendate&email1=upstream-release-monitoring%40fedoraproject.org&emailreporter1=1&emailtype1=substring&list_id=1733771&order=changeddate%20DESC%2Cbug_id%20DESC&query_based_on=&query_format=advanced[OPEN " +"https://bugzilla.redhat.com/buglist.cgi?" +"bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&bug_status=POST&classification=Fedora&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Copendate&email1=upstream-" +"release-monitoring%40fedoraproject." +"org&emailreporter1=1&emailtype1=substring&list_id=1733771&order=changeddate%20DESC%2Cbug_id%20DESC&query_based_on=&query_format=advanced[OPEN " "bugs]" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:21 +#: pages/Upstream_Release_Monitoring.adoc:18 msgid "" -"https://bugzilla.redhat.com/buglist.cgi?bug_status=CLOSED&classification=Fedora&email1=upstream-release-monitoring%40fedoraproject.org&emailreporter1=1&emailtype1=substring&order=changeddate%20DESC%2Cbug_id%20DESC&query_based_on=&query_format=advanced[CLOSED " +"https://bugzilla.redhat.com/buglist.cgi?" +"bug_status=CLOSED&classification=Fedora&email1=upstream-release-" +"monitoring%40fedoraproject." +"org&emailreporter1=1&emailtype1=substring&order=changeddate%20DESC%2Cbug_id%20DESC&query_based_on=&query_format=advanced[CLOSED " "bugs]" msgstr "" #. type: Title == -#: ./pages/Upstream_Release_Monitoring.adoc:22 +#: pages/Upstream_Release_Monitoring.adoc:19 #, no-wrap msgid "Details" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:29 +#: pages/Upstream_Release_Monitoring.adoc:26 msgid "" "One of the core foundation of Fedora is _First_ which implies having the " "latest versions of software (in rawhide and sometimes in released branches), " @@ -89,60 +94,60 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:32 +#: pages/Upstream_Release_Monitoring.adoc:29 msgid "" "Fedora thus offers a service to help with this. This service is divided " "into three components:" msgstr "" #. type: Title === -#: ./pages/Upstream_Release_Monitoring.adoc:34 -#: ./pages/Upstream_Release_Monitoring.adoc:37 +#: pages/Upstream_Release_Monitoring.adoc:31 +#: pages/Upstream_Release_Monitoring.adoc:34 #, no-wrap msgid "Anitya" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:35 +#: pages/Upstream_Release_Monitoring.adoc:32 msgid "monitoring settings at Fedora Package Sources" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:36 +#: pages/Upstream_Release_Monitoring.adoc:33 msgid "https://github.com/fedora-infra/the-new-hotness/[The-new-hotness]" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:44 +#: pages/Upstream_Release_Monitoring.adoc:41 msgid "" "Available at https://release-monitoring.org[release-monitoring.org], Anitya " "provides a web service where anyone can register a project. Anitya will " -"then broadcast a http://fedmsg.com[fedmsg] message when it finds a new " -"release. Checks are run by cron twice a day." +"then broadcast a https://fedmsg.readthedocs.io/[fedmsg] message when it " +"finds a new release. Checks are run by cron twice a day." msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:48 +#: pages/Upstream_Release_Monitoring.adoc:45 msgid "" "Anitya is not specific to Fedora but we are using it as a way to learn about " "new releases. Edit entries there to your heart's content." msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:50 +#: pages/Upstream_Release_Monitoring.adoc:47 msgid "" -"Bugs, features request and patches should go to " -"https://github.com/fedora-infra/anitya/issues[anitya/issues]." +"Bugs, features request and patches should go to https://github.com/fedora-" +"infra/anitya/issues[anitya/issues]." msgstr "" #. type: Title === -#: ./pages/Upstream_Release_Monitoring.adoc:52 +#: pages/Upstream_Release_Monitoring.adoc:49 #, no-wrap msgid "Monitoring settings at src.fedoraproject.org" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:57 +#: pages/Upstream_Release_Monitoring.adoc:54 msgid "" "Fedora package maintainers can use the bottom left column at the package's " "page at https://src.fedoraproject.org/[src.fedoraproject.org] to have it " @@ -150,13 +155,13 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Upstream_Release_Monitoring.adoc:59 +#: pages/Upstream_Release_Monitoring.adoc:56 #, no-wrap msgid "The-New-Hotness" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:63 +#: pages/Upstream_Release_Monitoring.adoc:60 msgid "" "https://github.com/fedora-infra/the-new-hotness/[The-new-hotness] is an " "application that listens to the fedmsg bus and acts upon receiving messages " @@ -164,7 +169,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:67 +#: pages/Upstream_Release_Monitoring.adoc:64 msgid "" "When it receives a message indicating that a project has a new release, and " "that project is mapped to a Fedora package, it will check in pkgdb2 if the " @@ -172,7 +177,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:75 +#: pages/Upstream_Release_Monitoring.adoc:72 msgid "" "If the package is marked to be monitored, the-new-hotness will open a ticket " "on https://bugzilla.redhat.com[Bugzilla] mentioning the availability of the " @@ -182,17 +187,18 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:77 -msgid "The result of the scratch build is then added to the open bugzilla ticket." +#: pages/Upstream_Release_Monitoring.adoc:74 +msgid "" +"The result of the scratch build is then added to the open bugzilla ticket." msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:79 +#: pages/Upstream_Release_Monitoring.adoc:76 msgid "Subsequent successful koji builds are added to the ticket as well." msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:86 +#: pages/Upstream_Release_Monitoring.adoc:83 msgid "" "In some cases the scratch build will always fail (for example if the " "`Source0` in the spec file cannot be adjusted automatically), if you wish to " @@ -203,27 +209,27 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Upstream_Release_Monitoring.adoc:88 +#: pages/Upstream_Release_Monitoring.adoc:85 #, no-wrap msgid "Related Projects" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:91 +#: pages/Upstream_Release_Monitoring.adoc:88 msgid "" "http://github.com/tannewt/open-source-watershed[OSWatershed] - Monitors " "several distributions at once" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:92 +#: pages/Upstream_Release_Monitoring.adoc:89 msgid "" "https://ppisar.fedorapeople.org/cpandistributionsinfedora.xhtml[Perl package " "monitoring]" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:93 +#: pages/Upstream_Release_Monitoring.adoc:90 msgid "" "http://rpms.famillecollet.com/rpmphp/[Reports from Remi] PECL, pear and R " "extensions upstream comparison and stable repo with rawhide comparison for " @@ -231,34 +237,34 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:94 +#: pages/Upstream_Release_Monitoring.adoc:91 msgid "" -"http://distrowatch.com/table.php?distribution=fedora[DistroWatch.com: " -"Fedora]" +"http://distrowatch.com/table.php?distribution=fedora[DistroWatch.com: Fedora]" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:95 +#: pages/Upstream_Release_Monitoring.adoc:92 msgid "" -"http://youri.zarb.org/[Youri] http://check.mageia.org/[in action] " -"http://svnweb.mageia.org/adm/puppet/modules/youri-check/[puppet modules] A " -"generic framework" +"http://youri.zarb.org/[Youri] http://check.mageia.org/[in action] http://" +"svnweb.mageia.org/adm/puppet/modules/youri-check/[puppet modules] A generic " +"framework" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:96 -msgid "https://github.com/jness/ossvt[ossvt] Developed for https://ius.io/[IUS]" +#: pages/Upstream_Release_Monitoring.adoc:93 +msgid "" +"https://github.com/jness/ossvt[ossvt] Developed for https://ius.io/[IUS]" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:97 +#: pages/Upstream_Release_Monitoring.adoc:94 msgid "" "https://fedorapeople.org/cgit/till/public_git/cnucnu.git/[cnucnu] — the tool " "previously used to provide this service for Fedora" msgstr "" #. type: Plain text -#: ./pages/Upstream_Release_Monitoring.adoc:97 +#: pages/Upstream_Release_Monitoring.adoc:94 msgid "" "http://repology.org/metapackages/outdated-in-repo/fedora_rawhide/[Repology] " "cross distro version comparision" diff --git a/po/fr/master/pages/Using_the_Koji_Build_System.po b/po/fr/master/pages/Using_the_Koji_Build_System.po index 95f0d87..18ae105 100644 --- a/po/fr/master/pages/Using_the_Koji_Build_System.po +++ b/po/fr/master/pages/Using_the_Koji_Build_System.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-06-02 22:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,101 +16,54 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Using_the_Koji_build_system #. type: Title = -#: ./pages/Using_the_Koji_Build_System.adoc:3 +#: pages/Using_the_Koji_Build_System.adoc:3 #, no-wrap msgid "Using the Koji build system" msgstr "" #. type: Title == -#: ./pages/Using_the_Koji_Build_System.adoc:7 +#: pages/Using_the_Koji_Build_System.adoc:6 #, no-wrap msgid "Using Koji in Fedora" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:14 +#: pages/Using_the_Koji_Build_System.adoc:13 msgid "" "The https://fedoraproject.org/wiki/Koji[Koji Build System] is Fedora's RPM " "buildsystem. Packagers use the `koji` client to request package builds and " "get information about the buildsystem. Koji runs on top of Mock to build " -"RPM packages for specific architectures and ensure that they build " -"correctly." +"RPM packages for specific architectures and ensure that they build correctly." msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:16 +#: pages/Using_the_Koji_Build_System.adoc:17 msgid "" -"There is also a " -"https://fedoraproject.org/wiki/Zh/%E4%BD%BF%E7%94%A8Koji%E7%BC%96%E8%AF%91%E6%89%93%E5%8C%85%E7%B3%BB%E7%BB%9F[simplified " -"Chinese edition]." +"You can use the `koji` command directly, or use `fedpkg`, a script that " +"interacts with the RPM Packaging system and other subsystems, like `git` and " +"`koji` itself." msgstr "" #. type: Title === -#: ./pages/Using_the_Koji_Build_System.adoc:18 +#: pages/Using_the_Koji_Build_System.adoc:19 #, no-wrap msgid "Installing Koji" msgstr "" -#. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:21 -#, no-wrap -msgid "Koji Setup" -msgstr "" - #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:25 -msgid "" -"Before using Koji to build packages, you must have the `fedora-packager` " -"package installed:" -msgstr "" - -#. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:28 -#, no-wrap -msgid "dnf install fedora-packager\n" +#: pages/Using_the_Koji_Build_System.adoc:22 +msgid "Follow xref:Installing_Packager_Tools.adoc[Installing Packager Tools]." msgstr "" -#. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:31 -msgid "You must also have a valid kerberos ticket:" -msgstr "" - -#. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:34 -#, no-wrap -msgid "KRB5_TRACE=/dev/stdout kinit your_fas_username@FEDORAPROJECT.ORG\n" -msgstr "" - -#. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:37 -msgid "Here, `FEDORAPROJECT.ORG` must be in capital case." -msgstr "" - -#. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:42 -msgid "" -"Store your FAS username (all lower case) in `~/.fedora.upn`. This is not " -"actually needed for Kerberos but for other tools that use the Fedora client " -"certificate to determine the FAS username." -msgstr "" - -#. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:44 -msgid "" -"For more information, see " -"https://fedoraproject.org/wiki/Infrastructure/Kerberos[Kerberos setup]." -msgstr "" - -#. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:46 +#. type: Title === +#: pages/Using_the_Koji_Build_System.adoc:24 #, no-wrap msgid "Koji Config" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:53 +#: pages/Using_the_Koji_Build_System.adoc:31 msgid "" "The global-local client configuration file for koji is `/etc/koji.conf`. " "You should not need to change this from the defaults for building Fedora " @@ -118,22 +71,14 @@ msgid "" "secondary arch build systems." msgstr "" -#. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:57 -msgid "" -"You can use the `koji` command directly, or use `fedpkg`, a script that " -"interacts with the RPM Packaging system and other subsystems, like git and " -"koji itself." -msgstr "" - #. type: Title === -#: ./pages/Using_the_Koji_Build_System.adoc:59 +#: pages/Using_the_Koji_Build_System.adoc:33 #, no-wrap msgid "Building with fedpkg targets" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:66 +#: pages/Using_the_Koji_Build_System.adoc:40 msgid "" "When building with `fedpkg` within a git repository, every push is " "automatically tagged via git. All you have to do to build the package is to " @@ -141,46 +86,46 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:68 +#: pages/Using_the_Koji_Build_System.adoc:42 msgid "It is also possible to target a specific koji tag:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:71 +#: pages/Using_the_Koji_Build_System.adoc:45 #, no-wrap msgid "fedpkg build --target TARGET\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:78 +#: pages/Using_the_Koji_Build_System.adoc:52 msgid "" "For example, if building on rawhide against a side-tag for updating API for " -"many packages, such as `dist-f14-python`, use the following:" +"many packages, such as `f{NEXTOSVER}-python`, use the following:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:81 +#: pages/Using_the_Koji_Build_System.adoc:56 #, no-wrap -msgid "fedpkg build --target 'dist-f14-python'\n" +msgid "fedpkg build --target 'f{NEXTOSVER}-python'\n" msgstr "" #. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:84 +#: pages/Using_the_Koji_Build_System.adoc:59 #, no-wrap msgid "Chained builds" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:89 +#: pages/Using_the_Koji_Build_System.adoc:64 msgid "" "chain-builds only work when building on rawhide. To chain-build packages to " -"update a released OS version, " -"https://fedoraproject.org/wiki/Bodhi/BuildRootOverrides[set up an override " -"using bodhi] requesting packages to be included in the proper buildroot." +"update a released OS version, https://fedoraproject.org/wiki/Bodhi/" +"BuildRootOverrides[set up an override using bodhi] requesting packages to be " +"included in the proper buildroot." msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:95 +#: pages/Using_the_Koji_Build_System.adoc:70 msgid "" "Sometimes you want to make sure that one build has succeeded before " "launching the next one, for example when you want to rebuild a package " @@ -189,13 +134,13 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:98 +#: pages/Using_the_Koji_Build_System.adoc:73 #, no-wrap msgid "fedpkg chain-build libwidget libgizmo\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:107 +#: pages/Using_the_Koji_Build_System.adoc:82 msgid "" "The current package is added to the end of the CHAIN list. Colons (`:`) can " "be used in the CHAIN parameter to define groups of packages. Packages in " @@ -205,13 +150,13 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:110 +#: pages/Using_the_Koji_Build_System.adoc:85 #, no-wrap msgid "fedpkg chain-build libwidget libaselib : libgizmo :\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:117 +#: pages/Using_the_Koji_Build_System.adoc:92 msgid "" "causes `libwidget` and `libaselib` to be built in parallel, followed by " "`libgizmo`, and then the package in your current directory. If no groups " @@ -219,20 +164,20 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:121 +#: pages/Using_the_Koji_Build_System.adoc:96 msgid "" "If a build fails, following builds are canceled, but the builds that already " "succeeded are pushed to the repository." msgstr "" #. type: Title === -#: ./pages/Using_the_Koji_Build_System.adoc:123 +#: pages/Using_the_Koji_Build_System.adoc:98 #, no-wrap msgid "Scratch Builds" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:128 +#: pages/Using_the_Koji_Build_System.adoc:103 msgid "" "Sometimes it is useful to be able to build a package against the buildroot " "without actually including it in the release. This is called a scratch " @@ -240,40 +185,38 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:132 +#: pages/Using_the_Koji_Build_System.adoc:107 msgid "" "The following section covers using koji directly, as well as the fedpkg " "tool, to do scratch builds." msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:134 +#: pages/Using_the_Koji_Build_System.adoc:109 msgid "" "To create a scratch build from changes you haven't committed, do the " "following:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:138 +#: pages/Using_the_Koji_Build_System.adoc:112 #, no-wrap -msgid "" -"rpmbuild -bs foo.spec\n" -"koji build --scratch rawhide foo.srpm\n" +msgid "fedpkg scratch-build --srpm\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:141 +#: pages/Using_the_Koji_Build_System.adoc:115 msgid "From the latest git commit:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:144 +#: pages/Using_the_Koji_Build_System.adoc:118 #, no-wrap msgid "koji build --scratch rawhide 'git url'\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:150 +#: pages/Using_the_Koji_Build_System.adoc:124 msgid "" "If you have committed the changes to git and you are in the current branch, " "you can do a scratch build with `fedpkg`, which wraps the koji command line " @@ -281,83 +224,83 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:153 +#: pages/Using_the_Koji_Build_System.adoc:127 #, no-wrap msgid "fedpkg scratch-build\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:156 +#: pages/Using_the_Koji_Build_System.adoc:130 msgid "To run a scratch build for a specific architecture:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:159 +#: pages/Using_the_Koji_Build_System.adoc:133 #, no-wrap msgid "fedpkg scratch-build --arches \n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:162 +#: pages/Using_the_Koji_Build_System.adoc:136 msgid "``can be a comma separated list of several architectures." msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:165 +#: pages/Using_the_Koji_Build_System.adoc:139 msgid "" "Finally, it is possible to combine the scratch-build command with a specific " "koji tag in the form:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:168 +#: pages/Using_the_Koji_Build_System.adoc:142 #, no-wrap msgid "fedpkg scratch-build --target TARGET\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:171 +#: pages/Using_the_Koji_Build_System.adoc:145 msgid "" "Run `fedpkg scratch-build --help` or `koji build --help` for more " "information." msgstr "" #. type: Title === -#: ./pages/Using_the_Koji_Build_System.adoc:173 +#: pages/Using_the_Koji_Build_System.adoc:147 #, no-wrap msgid "Build Failures" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:176 +#: pages/Using_the_Koji_Build_System.adoc:150 msgid "If your package fails to build, you get an error, for example:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:181 +#: pages/Using_the_Koji_Build_System.adoc:156 #, no-wrap msgid "" -"420066 buildArch kernel-2.6.18-1.2739.10.9.el5.jjf.215394.2.src.rpm,\n" +"420066 buildArch kernel-2.6.18-1.2739.10.9.el{MAJOREPELVER}.jjf.215394.2.src.rpm,\n" "ia64): open (build-1.example.com) -> FAILED: BuildrootError:\n" "error building package (arch ia64), mock exited with status 10\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:186 +#: pages/Using_the_Koji_Build_System.adoc:161 msgid "" "Investigate why the build failed by looking at the log files. If there is a " "`build.log`, start there. Otherwise, look at `init.log`." msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:189 +#: pages/Using_the_Koji_Build_System.adoc:164 msgid "" "Each job you successfully start gets a unique task ID, which is listed in " "its output." msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:195 +#: pages/Using_the_Koji_Build_System.adoc:170 msgid "" "Logs can be found in the web interface, in the _Task_ pages for the failed " "task. Alternatively, use `koji watch-log`, along with the task ID, to view " @@ -365,27 +308,27 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/Using_the_Koji_Build_System.adoc:197 +#: pages/Using_the_Koji_Build_System.adoc:172 #, no-wrap msgid "Advanced use of Koji" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:202 +#: pages/Using_the_Koji_Build_System.adoc:177 msgid "" "We've tried to make Koji self-documenting wherever possible. The command " -"line tool prints a list of valid commands, and each command supports " -"`--help`. For example:" +"line tool prints a list of valid commands, and each command supports `--" +"help`. For example:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:205 +#: pages/Using_the_Koji_Build_System.adoc:180 #, no-wrap msgid "$ koji help\n" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:213 +#: pages/Using_the_Koji_Build_System.adoc:188 #, no-wrap msgid "" "Koji commands are:\n" @@ -398,13 +341,13 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:217 +#: pages/Using_the_Koji_Build_System.adoc:192 #, no-wrap msgid "$ koji build --help\n" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:220 +#: pages/Using_the_Koji_Build_System.adoc:195 #, no-wrap msgid "" "usage: koji build [options] tag URL\n" @@ -412,7 +355,7 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:227 +#: pages/Using_the_Koji_Build_System.adoc:202 #, no-wrap msgid "" "options:\n" @@ -424,18 +367,18 @@ msgid "" msgstr "" #. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:230 +#: pages/Using_the_Koji_Build_System.adoc:205 #, no-wrap msgid "Using koji to generate a mock config to replicate a buildroot" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:233 +#: pages/Using_the_Koji_Build_System.adoc:208 msgid "koji can be used to replicate a build root for local debugging." msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:238 +#: pages/Using_the_Koji_Build_System.adoc:213 #, no-wrap msgid "" "koji mock-config --help\n" @@ -444,7 +387,7 @@ msgid "" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:253 +#: pages/Using_the_Koji_Build_System.adoc:228 #, no-wrap msgid "" "Options:\n" @@ -453,8 +396,7 @@ msgid "" " --tag=TAG Create a mock config for a tag\n" " --task=TASK Duplicate the mock config of a previous task\n" " --buildroot=BUILDROOT\n" -" Duplicate the mock config for the specified " -"buildroot\n" +" Duplicate the mock config for the specified buildroot\n" " id\n" " --mockdir=DIR Specify mockdir\n" " --topdir=DIR Specify topdir\n" @@ -465,103 +407,101 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:256 -msgid "For example to get the latest buildroot for `dist-f12-build` run:" +#: pages/Using_the_Koji_Build_System.adoc:231 +msgid "For example to get the latest buildroot for `f{MAJOROSVER}-build` run:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:259 +#: pages/Using_the_Koji_Build_System.adoc:235 #, no-wrap -msgid "" -"koji mock-config --tag dist-f12-build --arch=x86_64 " -"--topurl=http://kojipkgs.fedoraproject.org/ dist-f12\n" +msgid "koji mock-config --tag f{MAJOROSVER}-build --arch=x86_64 --topurl=http://kojipkgs.fedoraproject.org/ f{MAJOROSVER}\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:263 +#: pages/Using_the_Koji_Build_System.adoc:239 msgid "" -"You must pass `--topurl=http://kojipkgs.fedoraproject.org/` to any " -"mock-config command to get a working mock-config from Fedora's koji." +"You must pass `--topurl=http://kojipkgs.fedoraproject.org/` to any mock-" +"config command to get a working mock-config from Fedora's koji." msgstr "" #. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:265 +#: pages/Using_the_Koji_Build_System.adoc:241 #, no-wrap msgid "Using Koji to control tasks" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:268 +#: pages/Using_the_Koji_Build_System.adoc:244 msgid "List tasks:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:271 +#: pages/Using_the_Koji_Build_System.adoc:247 #, no-wrap msgid "koji list-tasks\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:274 +#: pages/Using_the_Koji_Build_System.adoc:250 msgid "List only tasks requested by you:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:277 +#: pages/Using_the_Koji_Build_System.adoc:253 #, no-wrap msgid "koji list-tasks --mine\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:280 +#: pages/Using_the_Koji_Build_System.adoc:256 msgid "" "requeue an already-processed task (general syntax is: `koji resubmit " "[options] taskID`):" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:283 +#: pages/Using_the_Koji_Build_System.adoc:259 #, no-wrap msgid "koji resubmit 3\n" msgstr "" #. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:286 +#: pages/Using_the_Koji_Build_System.adoc:262 #, no-wrap msgid "Building a Package with the command-line tool" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:290 +#: pages/Using_the_Koji_Build_System.adoc:266 msgid "" "Instead of using the `fedpkg` target, you can also directly use the command " "line tool, `koji`." msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:292 +#: pages/Using_the_Koji_Build_System.adoc:268 msgid "To build a package, the syntax is:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:295 +#: pages/Using_the_Koji_Build_System.adoc:271 #, no-wrap msgid "koji build \n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:298 +#: pages/Using_the_Koji_Build_System.adoc:274 msgid "For example:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:301 +#: pages/Using_the_Koji_Build_System.adoc:278 #, no-wrap -msgid "koji build dist-f14 'git url'\n" +msgid "koji build f{MAJOROSVER}-candidate 'git url'\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:306 +#: pages/Using_the_Koji_Build_System.adoc:283 msgid "" "The koji build command creates a build task in Koji. By default, the tool " "will wait and print status updates until the build completes. You can " @@ -569,26 +509,26 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:310 +#: pages/Using_the_Koji_Build_System.adoc:287 msgid "" "For fedora koji, the git url MUST be based on pkgs.fedoraproject.org. Other " "arbitrary git repos cannot be used for builds." msgstr "" #. type: Title === -#: ./pages/Using_the_Koji_Build_System.adoc:312 +#: pages/Using_the_Koji_Build_System.adoc:289 #, no-wrap msgid "Koji tags and packages organization" msgstr "" #. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:314 +#: pages/Using_the_Koji_Build_System.adoc:291 #, no-wrap msgid "Terminology" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:321 +#: pages/Using_the_Koji_Build_System.adoc:298 msgid "" "In Koji, it is sometimes necessary to distinguish between a package in " "general, a specific build of a package, and the various rpm files created by " @@ -597,7 +537,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:326 +#: pages/Using_the_Koji_Build_System.adoc:303 #, no-wrap msgid "" "*Package*: The name of a source rpm.\n" @@ -607,7 +547,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:331 +#: pages/Using_the_Koji_Build_System.adoc:308 msgid "" "Build: A particular build of a package. This refers to the entire build: " "all arches and subpackages. For example: kernel-2.6.9-34.EL, " @@ -615,7 +555,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:335 +#: pages/Using_the_Koji_Build_System.adoc:312 msgid "" "RPM: A particular rpm. A specific arch and subpackage of a build. For " "example: kernel-2.6.9-34.EL.x86_64, kernel-devel-2.6.9-34.EL.s390, " @@ -623,40 +563,40 @@ msgid "" msgstr "" #. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:337 +#: pages/Using_the_Koji_Build_System.adoc:314 #, no-wrap msgid "Tags and targets" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:341 +#: pages/Using_the_Koji_Build_System.adoc:318 msgid "" "Koji organizes packages using tags. In Koji a tag is roughly a collection " "of packages:" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:343 +#: pages/Using_the_Koji_Build_System.adoc:320 msgid "Tags support inheritance" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:344 +#: pages/Using_the_Koji_Build_System.adoc:321 msgid "Each tag has its own list of valid packages (inheritable)" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:345 +#: pages/Using_the_Koji_Build_System.adoc:322 msgid "Package ownership can be set per-tag (inheritable)" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:346 +#: pages/Using_the_Koji_Build_System.adoc:323 msgid "When you build you specify a target rather than a tag" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:351 +#: pages/Using_the_Koji_Build_System.adoc:328 msgid "" "A build target specifies where a package should be built and how it should " "be tagged afterward. This allows target names to remain fixed as tags " @@ -664,97 +604,96 @@ msgid "" msgstr "" #. type: Title ==== -#: ./pages/Using_the_Koji_Build_System.adoc:353 +#: pages/Using_the_Koji_Build_System.adoc:330 #, no-wrap msgid "Koji commands for tags" msgstr "" #. type: Title ===== -#: ./pages/Using_the_Koji_Build_System.adoc:355 +#: pages/Using_the_Koji_Build_System.adoc:332 #, no-wrap msgid "Targets" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:358 +#: pages/Using_the_Koji_Build_System.adoc:335 msgid "You can get a full list of build targets with the following command:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:361 +#: pages/Using_the_Koji_Build_System.adoc:338 #, no-wrap msgid "$ koji list-targets\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:364 +#: pages/Using_the_Koji_Build_System.adoc:341 msgid "You can see just a single target with the `--name` option:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:370 +#: pages/Using_the_Koji_Build_System.adoc:348 #, no-wrap msgid "" -"$ koji list-targets --name f30\n" -"Name Buildroot Destination " -"\n" +"$ koji list-targets --name f{MAJOROSVER}\n" +"Name Buildroot Destination \n" "---------------------------------------------------------------------------------------------\n" -"f30 f30-build f30-pending " -"\n" +"f{MAJOROSVER} f{MAJOROSVER}-build f{MAJOROSVER}-updates-candidate\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:375 +#: pages/Using_the_Koji_Build_System.adoc:353 msgid "" -"This tells you a build for target `f30` will use a buildroot with packages " -"from the `f30-build` tag and tag the resulting packages as f30-pending." +"This tells you a build for target `f{MAJOROSVER}` will use a buildroot with " +"packages from the `f{MAJOROSVER}-build` tag and tag the resulting packages " +"as `f{MAJOROSVER}-updates-candidate`." msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:379 +#: pages/Using_the_Koji_Build_System.adoc:357 msgid "" "You probably do not want to build against rawhide. If Fedora N is the " "latest one out, to build to the next one, choose `f\\{N+1}`." msgstr "" #. type: Title ===== -#: ./pages/Using_the_Koji_Build_System.adoc:380 +#: pages/Using_the_Koji_Build_System.adoc:358 #, no-wrap msgid "Tags" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:383 +#: pages/Using_the_Koji_Build_System.adoc:361 msgid "You can get a list of tags with the following command:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:386 +#: pages/Using_the_Koji_Build_System.adoc:364 #, no-wrap msgid "$ koji list-tags\n" msgstr "" #. type: Title ===== -#: ./pages/Using_the_Koji_Build_System.adoc:388 +#: pages/Using_the_Koji_Build_System.adoc:366 #, no-wrap msgid "Packages" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:393 +#: pages/Using_the_Koji_Build_System.adoc:371 msgid "" "As mentioned above, each tag has its own list of packages that may be placed " "in the tag. To see that list for a tag, use the `list-pkgs` command:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:396 +#: pages/Using_the_Koji_Build_System.adoc:375 #, no-wrap -msgid "$ koji list-pkgs --tag dist-f14\n" +msgid "$ koji list-pkgs --tag f{MAJOROSVER}\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:401 +#: pages/Using_the_Koji_Build_System.adoc:380 msgid "" "The first column is the name of the package, the second tells you which tag " "the package entry has been inherited from, and the third tells you the owner " @@ -762,24 +701,24 @@ msgid "" msgstr "" #. type: Title ===== -#: ./pages/Using_the_Koji_Build_System.adoc:403 +#: pages/Using_the_Koji_Build_System.adoc:382 #, no-wrap msgid "Latest Builds" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:406 +#: pages/Using_the_Koji_Build_System.adoc:385 msgid "To see the latest builds for a tag, use the `latest-pkg` command:" msgstr "" #. type: delimited block . -#: ./pages/Using_the_Koji_Build_System.adoc:409 +#: pages/Using_the_Koji_Build_System.adoc:389 #, no-wrap -msgid "$ koji latest-pkg --all dist-f14\n" +msgid "$ koji latest-pkg --all f{MAJOROSVER}\n" msgstr "" #. type: Plain text -#: ./pages/Using_the_Koji_Build_System.adoc:413 +#: pages/Using_the_Koji_Build_System.adoc:393 msgid "" "The output gives you not only the latest builds, but which tag they have " "been inherited from and who built them." diff --git a/po/fr/master/pages/Utilities.po b/po/fr/master/pages/Utilities.po index c130491..1e6d892 100644 --- a/po/fr/master/pages/Utilities.po +++ b/po/fr/master/pages/Utilities.po @@ -17,13 +17,13 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #. type: Title = -#: ./pages/Utilities.adoc:1 +#: pages/Utilities.adoc:1 #, no-wrap msgid "Utilities for package maintainers" msgstr "" #. type: Plain text -#: ./pages/Utilities.adoc:5 +#: pages/Utilities.adoc:5 msgid "" "A number of utilities are available to support package maintainers in " "maintaining their packages. This page attempts to list them, but is not a " @@ -31,60 +31,59 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Utilities.adoc:6 +#: pages/Utilities.adoc:6 #, no-wrap msgid "Testing new builds with pull requests and CI" msgstr "" #. type: Plain text -#: ./pages/Utilities.adoc:11 +#: pages/Utilities.adoc:11 msgid "" "To test updates and changes to packages, package maintainers are encouraged " -"to use the continuous integration (CI) that is available on " -"src.fedoraproject.org through pull requests. Each pull request will " +"to use the continuous integration (CI) that is available on src." +"fedoraproject.org through pull requests. Each pull request will " "automatically run a test scratch build and report results in the pull " "request." msgstr "" #. type: Plain text -#: ./pages/Utilities.adoc:14 +#: pages/Utilities.adoc:14 msgid "" "One may need to re-run the test build in pull requests. A comment with " "`[citest]` will do so." msgstr "" #. type: Plain text -#: ./pages/Utilities.adoc:16 +#: pages/Utilities.adoc:16 msgid "" -"More advanced CI using " -"link:https://fedoraproject.org/wiki/Zuul-based-ci#How_to_attach_a_Pagure_repository_on_Zuul[Zuul] " -"is also available." +"More advanced CI using link:https://fedoraproject.org/wiki/Zuul-based-" +"ci#How_to_attach_a_Pagure_repository_on_Zuul[Zuul] is also available." msgstr "" #. type: Title == -#: ./pages/Utilities.adoc:17 +#: pages/Utilities.adoc:17 #, no-wrap msgid "Checking package update impact: fedrq" msgstr "" #. type: Plain text -#: ./pages/Utilities.adoc:22 +#: pages/Utilities.adoc:22 msgid "" -"Before updating their packages as per the " -"xref:fesco::Updates_Policy.adoc[updates policy], package maintainers should " -"check if/how the update impacts other packages. To list what packages " -"depend on another in each Fedora release, package maintainers can use the " -"link:https://fedrq.gtmx.me/[fedrq] tool. Example usage:" +"Before updating their packages as per the xref:fesco::Updates_Policy." +"adoc[updates policy], package maintainers should check if/how the update " +"impacts other packages. To list what packages depend on another in each " +"Fedora release, package maintainers can use the link:https://fedrq.gtmx.me/" +"[fedrq] tool. Example usage:" msgstr "" #. type: delimited block - -#: ./pages/Utilities.adoc:26 +#: pages/Utilities.adoc:26 #, no-wrap msgid "$ sudo dnf install fedrq\n" msgstr "" #. type: delimited block - -#: ./pages/Utilities.adoc:49 +#: pages/Utilities.adoc:49 #, no-wrap msgid "" "$ fedrq whatrequires-src -b f38 python-pydantic\n" @@ -112,13 +111,13 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Utilities.adoc:52 +#: pages/Utilities.adoc:52 #, no-wrap msgid "Running fedora-review on review tickets using fedora-review service" msgstr "" #. type: Plain text -#: ./pages/Utilities.adoc:56 +#: pages/Utilities.adoc:56 msgid "" "The link:https://github.com/FrostyX/fedora-review-service/[Fedora Review " "Service] automatically runs `fedora-review` on new package review tickets. " @@ -127,22 +126,21 @@ msgid "" msgstr "" #. type: Title == -#: ./pages/Utilities.adoc:57 +#: pages/Utilities.adoc:57 #, no-wrap msgid "Automating package updates: Packit" msgstr "" #. type: Plain text -#: ./pages/Utilities.adoc:61 +#: pages/Utilities.adoc:61 msgid "" "link:https://packit.dev/[Packit] is a service that enables automated pull " "request creation for new upstream releases. More information on configuring " -"dist-git repositories to use Packit can be found " -"link:https://packit.dev/docs/fedora-releases-guide/#pull-from-upstream-job[in " -"the documentation]." +"dist-git repositories to use Packit can be found link:https://packit.dev/" +"docs/fedora-releases-guide/#pull-from-upstream-job[in the documentation]." msgstr "" #. type: Plain text -#: ./pages/Utilities.adoc:62 +#: pages/Utilities.adoc:62 msgid "Please remember to run impact checks before pushing updates." msgstr "" diff --git a/po/fr/master/pages/bug_status.po b/po/fr/master/pages/bug_status.po index 9a2e337..49d2295 100644 --- a/po/fr/master/pages/bug_status.po +++ b/po/fr/master/pages/bug_status.po @@ -17,29 +17,28 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #. type: Title = -#: ./pages/bug_status.adoc:1 +#: pages/bug_status.adoc:1 #, no-wrap msgid "Bug Status Workflow" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:5 +#: pages/bug_status.adoc:5 msgid "" "This document describes best practices for setting Bugzilla status for bugs " "and feature requests. For Change proposal trackers, use the Bugzilla status " -"described in the " -"xref:program_management::changes_policy.adoc#_bugzilla_trackers[Changes " -"policy]." +"described in the xref:program_management::changes_policy." +"adoc#_bugzilla_trackers[Changes policy]." msgstr "" #. type: Title == -#: ./pages/bug_status.adoc:6 +#: pages/bug_status.adoc:6 #, no-wrap msgid "Statuses" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:10 +#: pages/bug_status.adoc:10 msgid "" "The image below presents a general flow chart for bugs in the typical case. " "The flow is bi-directional: a bug can revert to a previous status if, for " @@ -47,45 +46,45 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./pages/bug_status.adoc:11 +#: pages/bug_status.adoc:11 #, no-wrap msgid "program_management::fedora-bug-lifecycle.png" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:15 +#: pages/bug_status.adoc:15 msgid "" "The table below summarizes the statuses. More details, including additional " "keywords, flags, and resolutions are given in the following sections." msgstr "" #. type: Title == -#: ./pages/bug_status.adoc:18 +#: pages/bug_status.adoc:18 #, no-wrap msgid "Resolutions" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:21 +#: pages/bug_status.adoc:21 msgid "" "The table below describes the resolutions that can apply to the _CLOSED_ " "status." msgstr "" #. type: Title == -#: ./pages/bug_status.adoc:24 +#: pages/bug_status.adoc:24 #, no-wrap msgid "Priority and Severity" msgstr "" #. type: Title === -#: ./pages/bug_status.adoc:26 +#: pages/bug_status.adoc:26 #, no-wrap msgid "Severity" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:30 +#: pages/bug_status.adoc:30 msgid "" "The _Severity_ field is used to indicate the bug's importance. The values " "for the severity field should be assigned with reference to the following " @@ -93,35 +92,35 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:32 +#: pages/bug_status.adoc:32 msgid "" "_Urgent_: the bug makes whole system unusable (or it is a security bug, " "which is per definition urgent)" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:33 +#: pages/bug_status.adoc:33 msgid "" "_High_: the bug makes the program in question unusable, or a major packaging " "guideline violation (license problem, bundled library, etc)" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:34 +#: pages/bug_status.adoc:34 msgid "" "_Medium_: a real bug which makes program more difficult to use, at least " "part of the program is available; possibly workarounds are available" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:35 +#: pages/bug_status.adoc:35 msgid "" -"_Low_: anything else - cosmetic issues, corner cases with unusual " -"(non-default) configurations, etc." +"_Low_: anything else - cosmetic issues, corner cases with unusual (non-" +"default) configurations, etc." msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:38 +#: pages/bug_status.adoc:38 msgid "" "The _Urgent_ setting should not usually be used for hardware-specific bugs: " "a bug which causes the entire distribution to be affected but is restricted " @@ -131,7 +130,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:43 +#: pages/bug_status.adoc:43 msgid "" "For most packages, most issues are likely to be of _Medium_ severity. These " "are not hard and fast rules. Use your best judgement in setting the " @@ -141,13 +140,13 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/bug_status.adoc:44 +#: pages/bug_status.adoc:44 #, no-wrap msgid "Priority" msgstr "" #. type: Plain text -#: ./pages/bug_status.adoc:50 +#: pages/bug_status.adoc:50 msgid "" "The _Priority_ field may be used, at their choice, by maintainers to keep " "track of the order in which they wish to address bugs in their package(s). " diff --git a/po/fr/master/pages/index.po b/po/fr/master/pages/index.po index d419ecb..7117047 100644 --- a/po/fr/master/pages/index.po +++ b/po/fr/master/pages/index.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\n" +"POT-Creation-Date: 2023-05-22 21:58+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,122 +16,130 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#. Imported from: https://fedoraproject.org/wiki/Category:Package_Maintainers #. type: Title = -#: ./pages/index.adoc:3 +#: pages/index.adoc:1 #, no-wrap msgid "Fedora Package Maintainers" msgstr "" #. type: Plain text -#: ./pages/index.adoc:8 +#: pages/index.adoc:5 msgid "" "Fedora Packages are maintained collectively by a community of both Red Hat " "members and volunteers." msgstr "" +#. type: Plain text +#: pages/index.adoc:10 +msgid "" +"Fedora package maintenance is governed by policies enacted by xref:fesco::" +"index.adoc[Fedora Engineering Steering Committee (FESCo)]. This " +"documentation site provides supplemental information on tooling and " +"processes, as well as tutorials, guides and howtos." +msgstr "" + #. type: Title == -#: ./pages/index.adoc:10 +#: pages/index.adoc:12 #, no-wrap msgid "Useful links for Package Maintainers" msgstr "" #. type: Title === -#: ./pages/index.adoc:13 +#: pages/index.adoc:15 #, no-wrap msgid "Get Involved" msgstr "" #. type: Plain text -#: ./pages/index.adoc:16 -msgid "xref:Joining_the_Package_Maintainers.adoc[Joining the Package Maintainers]" +#: pages/index.adoc:18 +msgid "" +"xref:Joining_the_Package_Maintainers.adoc[Joining the Package Maintainers]" msgstr "" #. type: Plain text -#: ./pages/index.adoc:19 +#: pages/index.adoc:21 msgid "" "xref:Package_Review_Process.adoc[Package Review Process] — describes the " "formal review process (for both contributors and reviewers)" msgstr "" #. type: Plain text -#: ./pages/index.adoc:22 +#: pages/index.adoc:24 msgid "" "https://fedoraproject.org/wiki/Category:Packaging_SIGs[Packaging SIGs] — " "Informal groups of packagers working on specific areas of the distribution" msgstr "" #. type: Plain text -#: ./pages/index.adoc:25 +#: pages/index.adoc:27 msgid "" "https://fedoraproject.org/wiki/EPEL[EPEL] — Rebuild of Fedora packages for " "RHEL or compatible derivatives" msgstr "" #. type: Title === -#: ./pages/index.adoc:27 +#: pages/index.adoc:29 #, no-wrap msgid "Packaging Guidelines" msgstr "" #. type: Plain text -#: ./pages/index.adoc:32 +#: pages/index.adoc:34 msgid "" "The https://fedoraproject.org/wiki/Packaging_Committee[Packaging Committee] " -"handles the rules and " -"https://docs.fedoraproject.org/en-US/packaging-guidelines[Packaging " +"handles the rules and xref:packaging-guidelines::index.adoc[Packaging " "Guidelines] for writing SPEC files for software in Fedora." msgstr "" #. type: Title === -#: ./pages/index.adoc:34 +#: pages/index.adoc:36 #, no-wrap msgid "Introduction to packaging" msgstr "" #. type: Plain text -#: ./pages/index.adoc:38 +#: pages/index.adoc:40 msgid "" "http://rpm.org/max-rpm-snapshot/[Maximum RPM Book] — most detailed, but " "slightly obsolete." msgstr "" #. type: Plain text -#: ./pages/index.adoc:41 +#: pages/index.adoc:43 msgid "" -"http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html[RPM " -"Guide] — an in-depth guide to RPM." +"https://rpm-packaging-guide.github.io/[RPM Packaging Guide] — an in-depth " +"guide to RPM." msgstr "" #. type: Title === -#: ./pages/index.adoc:43 +#: pages/index.adoc:45 #, no-wrap msgid "Procedures, Policies and Guides" msgstr "" #. type: Plain text -#: ./pages/index.adoc:46 +#: pages/index.adoc:48 msgid "" "https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock " "to test package builds]" msgstr "" #. type: Plain text -#: ./pages/index.adoc:48 +#: pages/index.adoc:50 msgid "" "https://bodhi.fedoraproject.org/docs/user/man_pages/bodhi.html[Using the " "Bodhi CLI tool]" msgstr "" #. type: Plain text -#: ./pages/index.adoc:51 +#: pages/index.adoc:53 msgid "" "https://fedoraproject.org/wiki/Milestone_freezes[Milestone freezes] — how " "the Fedora Beta and Final freezes affect packagers" msgstr "" #. type: Plain text -#: ./pages/index.adoc:55 +#: pages/index.adoc:57 msgid "" "https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle[Fedora Release Life " "Cycle] — information on the Fedora development process, particularly various " @@ -139,101 +147,84 @@ msgid "" msgstr "" #. type: Title === -#: ./pages/index.adoc:57 +#: pages/index.adoc:59 #, no-wrap msgid "Resources for Fedora Package Collection contributors" msgstr "" #. type: Plain text -#: ./pages/index.adoc:60 +#: pages/index.adoc:62 msgid "" "https://fedoraproject.org/wiki/Category:SIGs?rd=SIGs[SIGs] — Fedora Special " "Interest Groups" msgstr "" #. type: Plain text -#: ./pages/index.adoc:62 +#: pages/index.adoc:64 msgid "" -"https://bugzilla.redhat.com/bugzilla/describecomponents.cgi?product=Fedora[Fedora " -"package components in bugzilla]" +"https://bugzilla.redhat.com/bugzilla/describecomponents.cgi?" +"product=Fedora[Fedora package components in bugzilla]" msgstr "" #. type: Plain text -#: ./pages/index.adoc:64 -msgid "https://koji.fedoraproject.org/koji/[koji — Fedora Package Build System]" +#: pages/index.adoc:66 +msgid "" +"https://koji.fedoraproject.org/koji/[koji — Fedora Package Build System]" msgstr "" #. type: Plain text -#: ./pages/index.adoc:66 +#: pages/index.adoc:68 msgid "https://bodhi.fedoraproject.org/[bodhi — Fedora Package Update System]" msgstr "" #. type: Plain text -#: ./pages/index.adoc:69 -msgid "" -"https://calendar.fedoraproject.org/vacation/[Vacation Calendar] —Add a " -"vacation note if you are going to be unavailable for a few days." -msgstr "" - -#. type: Plain text -#: ./pages/index.adoc:72 +#: pages/index.adoc:71 msgid "" -"https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers[Test " -"Machines] — Contributed servers for test, mock build, compile or debug " -"packages before submitting to koji" -msgstr "" - -#. type: Title === -#: ./pages/index.adoc:74 -#, no-wrap -msgid "Important Mailing Lists" +"https://packages.fedoraproject.org/[Fedora Packages] — Web UI for browsing " +"packages." msgstr "" #. type: Plain text -#: ./pages/index.adoc:78 +#: pages/index.adoc:75 msgid "" -"https://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedoraproject.org/[devel-announce] " -"is a low traffic, announcements only list where important development " -"information is posted." +"https://packager-dashboard.fedoraproject.org[Fedora Packager Dashboard] — " +"Service for Fedora package maintainers aiming to provide all relevant data " +"at a single place in an easy to read and filter way." msgstr "" #. type: Plain text -#: ./pages/index.adoc:81 +#: pages/index.adoc:78 msgid "" -"https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/[devel] " -"is a high traffic mailing list where discussions about the development of " -"Fedora are held." +"https://calendar.fedoraproject.org/vacation/[Vacation Calendar] — Add a " +"vacation note if you are going to be unavailable for a few days." msgstr "" #. type: Plain text -#: ./pages/index.adoc:87 +#: pages/index.adoc:81 msgid "" -"https://lists.fedoraproject.org/admin/lists/package-announce@lists.fedoraproject.org/[package-announce] " -"is a very high traffic mailing list where notifications are given for all " -"the commits in any package in the Fedora repository. Note that the Fedora " -"package database sends commit mails for packages you (co-)maintain." +"https://fedoraproject.org/wiki/" +"Test_Machine_Resources_For_Package_Maintainers[Test Machines] — Contributed " +"servers for test, mock build, compile or debug packages before submitting to " +"koji" msgstr "" #. type: Plain text -#: ./pages/index.adoc:90 +#: pages/index.adoc:84 msgid "" -"https://lists.fedoraproject.org/admin/lists/packaging@lists.fedoraproject.org/[packaging] " -"is the mailing list of the " -"https://fedoraproject.org/wiki/Packaging_Committee[Fedora Packaging " -"Committee], who determine the official packaging guidelines for Fedora " -"projects." +"https://sourcegraph.com/search?q=context:global+repo:^src\\.fedoraproject\\." +"org/rpms/.*%24[Sourcegraph] — Search across all dist-git repositories." msgstr "" #. type: Title === -#: ./pages/index.adoc:92 +#: pages/index.adoc:86 #, no-wrap -msgid "Fedora Engineering Steering Committee (FESCo)" +msgid "Important Mailing Lists" msgstr "" #. type: Plain text -#: ./pages/index.adoc:94 +#: pages/index.adoc:90 msgid "" -"Fedora technical management is organized by the " -"https://docs.fedoraproject.org/en-US/fesco/[Fedora Engineering Steering " -"Committee (FESCo)]." +"https://listman.redhat.com/mailman/listinfo/bugzilla-announce-list[bugzilla-" +"announce-list] is where announcements about https://bugzilla.redhat.com[Red " +"Hat Bugzilla] are shared." msgstr "" diff --git a/po/fr/master/partials/attributes.po b/po/fr/master/partials/attributes.po index db5ed6c..e69de29 100644 --- a/po/fr/master/partials/attributes.po +++ b/po/fr/master/partials/attributes.po @@ -1,18 +0,0 @@ -# SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# This file is distributed under the same license as the PACKAGE package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-09-05 22:30+0000\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: 8bit\n" - diff --git a/po/fr/master/partials/mailing_lists.po b/po/fr/master/partials/mailing_lists.po index b0b97fa..6d59d63 100644 --- a/po/fr/master/partials/mailing_lists.po +++ b/po/fr/master/partials/mailing_lists.po @@ -17,27 +17,26 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #. type: Plain text -#: ./partials/mailing_lists.adoc:4 +#: partials/mailing_lists.adoc:4 msgid "" -"https://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedoraproject.org/[devel-announce] " -"is a low traffic, announcements only list where important development " -"information is posted." +"https://lists.fedoraproject.org/admin/lists/devel-announce@lists." +"fedoraproject.org/[devel-announce] is a low traffic, announcements only list " +"where important development information is posted." msgstr "" #. type: Plain text -#: ./partials/mailing_lists.adoc:8 +#: partials/mailing_lists.adoc:8 msgid "" -"https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/[devel] " -"is a high traffic mailing list where discussions about the development of " -"Fedora are held." +"https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/" +"[devel] is a high traffic mailing list where discussions about the " +"development of Fedora are held." msgstr "" #. type: Plain text -#: ./partials/mailing_lists.adoc:12 +#: partials/mailing_lists.adoc:12 msgid "" -"https://lists.fedoraproject.org/admin/lists/packaging@lists.fedoraproject.org/[packaging] " -"is the mailing list of the " -"https://fedoraproject.org/wiki/Packaging_Committee[Fedora Packaging " -"Committee], who determine the official packaging guidelines for Fedora " -"projects." +"https://lists.fedoraproject.org/admin/lists/packaging@lists.fedoraproject." +"org/[packaging] is the mailing list of the https://fedoraproject.org/wiki/" +"Packaging_Committee[Fedora Packaging Committee], who determine the official " +"packaging guidelines for Fedora projects." msgstr ""