fedora-docs-l10n/package-maintainers/master/pages/New_Package_Process_for_Existing_Contributors — Spanish @ Fedora Weblate: If everything goes well, it should queue up your branch …

Translation

English type: Plain text

Spanish

Needs editing

Skip

	English	Spanish	Actions
	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.	Solicite un repositorio distgit con `fedpkg request-repo PACKAGE-NAME BUGZILLA-TICKET-NUMBER`. xref:Package_Maintenance_Guide.adoc[Package Maintenance Guide] (Guía de Mantenimiento de Paquete) tiene más información sobre `fedpkg`.) Es posible que necesite obtener un pagure-API-token antes de poder solicitar correctamente el repositorio.
	When the repo is created, it only contains the `rawhide` branch. If you want to bring the package to other Fedora releases, see xref:Package_Maintenance_Guide.adoc#requesting_branches[Requesting branches].	Cuando se crea el repositorio, solo contiene la rama `rawhide`. Si desea traer el paquete a otras versiones de Fedora, solicite ramas con `fedpkg request-branch --repo PACKAGE-NAME BRANCH`.
	Once the requests have been processed, checkout the distgit repository with `fedpkg clone <packagename>`.	Una vez que se hayan procesado las solicitudes, consulte el repositorio distgit con `fedpkg clone <packagename>`.
	Import your srpm	Importe su srpm
	First `fkinit -u username`	Primero `fkinit -u username`
	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 (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.	Después puede importar el SRPM aprobado en la rama rawhide ejecutando`fedpkg import libfoo-x.x.x.src.rpm; git commit -m "Initial import (fedora#nnnnnn)."`(donde `nnnnnn` es su número de revisión de errores de paquete Bugzilla). Si su paquete está usando _autochangelog_, al escribir el número de error como se específica hará que Bodhi automáticamente cierre el error cuando su paquete se envíe al repositorio Rawhide estable.
	Obviously, replace `libfoo-x.x.x.src.rpm` with the full path to your approved SRPM.	Obviamente, reemplace `libfoo-x.x.x.src.rpm` con la ruta completa a su SRPM aprobado.
	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. This is normal.	Debería ver que carga las fuentes y finaliza correctamente. Si no configuró `ssh-agent` le pedirá con frecuencia su contraseña de clave ssh. Esto es normal.
	Now run `git push` to get the final versions in your rawhide branch.	Ahora ejecute `git push` para obtener las versiones finales en su rama rawhide.
	You can now import the package to your branches (which you requested in Step 7) too	Usted puede ahora importar el paquete a sus ramas (que solicitó en el Paso 7) también
	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).	La manera más rápida de hacer esto es utilizar `fedpkg switch-branch BRANCH` para cambiar la rama (donde `BRANCH` puede ser `f13` etcétera).
	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 branch and create an identical commit.	Ahora usted puede`git merge rawhide`. Esto conseguirá archivo `.spec`, `.gitignore` y archivo fuente junto con cualquier parche y otros archivos de la rama rawhide y crea una confirmación idéntica.
	Previous step already created commit for you, now you can push the results using `fedpkg push` or `git push`.	El paso anterior ya creó la confirmación para usted, ahora puede enviar los resultados utilizando `fedpkg push` o `git push`.
	Request builds	Solicitar compilaciones
	For each branch that you'd like to request a build for, switch using `fedpkg switch-branch` and run `fedpkg build`.	Para cada rama para la que desee solicitar compilaciones, cambie usando `fedpkg switch-branch` y ejecute `fedpkg build`.
	If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done!	Si toda va bien, debería poner en cola su rama para construcción, el paquete se construirá limpiamente y ¡listo!
	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 the spec release number and request a new build.	Si falla al compilar, el sistema de compilación le enviará un correo electrónico para informarle del fallo y le enlazará los registros. Confirme los cambios necesarios en git, aumente el número de versión en las especificaciones y solicite una nueva compilación.
	Close the Bugzilla ticket (assuming that the package built successfully)	Cierre el ticket Bugzilla (asumiendo que el paquete se ha compilado con éxito)
	You should close it with resolution `NEXTRELEASE` or `RAWHIDE`, depending on where you built the package. The resolution field will appear after you set the status field to `CLOSED`.	Debería cerrarlo con la resolución `NEXTRELEASE` o `RAWHIDE`, dependiendo de donde haya compilado el paquete. El campo resolución aparecerá después de que usted establezca el campo estado a `CLOSED`.
	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.	Si este paquete se creará para cualquier versión de Fedora que ya esté publicada, envíelo para incluirlo en el repositorio `fedora-updates` para esas versiones de Fedora. Vea más detalles en xref:Package_Update_Guide.adoc#Later_Branched_and_stable_releases[Package Update Guide] (Guía de Actualización de Paquete).
	Add the package to the https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups[comps file(s)] if appropriate.	Añada el paquete a los https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups[archivos de compilación] si corresponde.
	Consider enabling xref:Upstream_Release_Monitoring.adoc[Upstream Release Monitoring] for the package.	Considere habilitar xref:Upstream_Release_Monitoring.adoc[Upstream Release Monitoring] (Monitorizar Versiones Upstream) para el paquete.
	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].	Sabemos que este proceso, a veces, puede ser tan claro como el barro, siempre estamos intentando hacerlo mejor. Si tiene problemas o alguna consulta, pregunte en la https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[lista de desarrollo de Fedora].
	xref:Package_Maintenance_Guide.adoc[Package Maintenance Guide] may also be of use.	También puede usar xref:Package_Maintenance_Guide.adoc[].

Loading…

vareli Translation added fedora-docs-l10n/package-maintainers master/pages/New_Package_Process_for_Existing_Contributors Spanish	English If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done! Spanish 112 characters edited Current translation Translated Si toda va bien, debería poner en cola su rama para construcción, el paquete se construirá limpiamente y ¡listo! 5 months ago
vareli Suggestion removed fedora-docs-l10n/package-maintainers master/pages/New_Package_Process_for_Existing_Contributors Spanish	English If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done! Spanish 118 characters edited Si todo va bien, debería poner en cola su rama para la construcción, el paquete se construirá limpiamente y ¡listo! 5 months ago
mt:weblate-translation-memory Suggestion added fedora-docs-l10n/package-maintainers master/pages/New_Package_Process_for_Existing_Contributors Spanish	English If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done! Spanish 118 characters edited Si todo va bien, debería poner en cola su rama para la construcción, el paquete se construirá limpiamente y ¡listo! 5 months ago
None String added in the repository fedora-docs-l10n/package-maintainers master/pages/New_Package_Process_for_Existing_Contributors Spanish	English If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done! Spanish 0 characters edited Empty 5 months ago

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Spanish
No related strings found in the glossary.

String information

Source string description

type: Plain text

Flags

placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?"

Source string location

pages/New_Package_Process_for_Existing_Contributors.adoc:105

String age

5 months ago

Last updated

4 months ago

Source string age

10 months ago

Translation file

po/es/master/pages/New_Package_Process_for_Existing_Contributors.po, string 35

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.