fedora-docs-l10n/packaging-guidelines/master/pages/SourceURL — English @ Fedora Weblate: Source: https://github.com/OWNER/PROJECT/archive/%{commit}/%{name}-%{shortcommit}.tar.gz [GitHub] Source: https://bitbucket.org/OWNER/PROJECT/get/%{commit}.tar.gz#/%{name}-%{shortcommit}.tar.gz [BitBucket] Source: https://gitlab.com/OWNER/PROJECT/-/archive/%{commit}/%{name}-%{shortcommit}.tar.gz [GitLab] Source: …

Zen

Source string Source string

English

Source:  https://github.com/OWNER/PROJECT/archive/%{commit}/%{name}-%{shortcommit}.tar.gz               [GitHub]
Source:  https://bitbucket.org/OWNER/PROJECT/get/%{commit}.tar.gz#/%{name}-%{shortcommit}.tar.gz        [BitBucket]
Source:  https://gitlab.com/OWNER/PROJECT/-/archive/%{commit}/%{name}-%{shortcommit}.tar.gz             [GitLab]
Source:  https://git.sr.ht/~OWNER/PROJECT/archive/%{shortcommit}.tar.gz#/PROJECT-%{shortcommit}.tar.gz  [Sourcehut]
...

Needs editing

The string is read only.

Skip

	English	Actions
	Sourceforge.net
	For packages hosted on sourceforge, use
	changing `.tar.gz` to whatever matches the upstream distribution. Note that we are using `downloads.sourceforge.net` instead of an arbitrarily chosen mirror. You may use the package name/package version instead of the `+%{name}+` and `+%{version}+` macros, of course.
	Please note that the correct url is `+downloads.sourceforge.net+`, and NOT `+download.sourceforge.net+`.
	Git Hosting Services
	If the upstream does create tarballs you should use them as tarballs provide an easier trail for people auditing the packages.
	Git web-based hosting services provide a mechanism to create tarballs on demand, either from a specific commit revision, or from a specific tag. If the upstream does not create tarballs for releases, you can use this mechanism to produce them.
	The full 40-character hash and associated git tag may be obtained by issuing the following git command:
	https://git-scm.com/docs/git-ls-remote[git ls-remote] \https://HOSTING-SERVICE/OWNER/%\{name}.git
	HOSTING-SERVICE: name of the service, i.e. "github.com", "bitbucket.org", "gitlab.com", etc. OWNER: username for the repository owner PROJECT: upstream project name (if it's identical to the package name, use %{name} instead)
	You may also obtain the 40-character hash and associated git tag via the web-interface of the HOSTING-SERVICE, or by cloning the repository and issuing the https://git-scm.com/docs/git-show-ref[git show-ref] command.
	Once the commit hash and git tag are known, you can define them in your spec file as follows:
	%global commit 40-CHARACTER-HASH-VALUE %global gittag GIT-TAG %global shortcommit %(c=%{commit}; echo ${c:0:7}) [GitHub] %global shortcommit %(c=%{commit}; echo ${c:0:11}) [Bitbucket] %global shortcommit %(c=%{commit}; echo ${c:0:7}) [GitLab] %global shortcommit %(c=%{commit}; echo ${c:0:8}) [Sourcehut]
	Commit Revision
	For the source tarball, you can use the following syntax:
	Source: https://github.com/OWNER/PROJECT/archive/%{commit}/%{name}-%{shortcommit}.tar.gz [GitHub] Source: https://bitbucket.org/OWNER/PROJECT/get/%{commit}.tar.gz#/%{name}-%{shortcommit}.tar.gz [BitBucket] Source: https://gitlab.com/OWNER/PROJECT/-/archive/%{commit}/%{name}-%{shortcommit}.tar.gz [GitLab] Source: https://git.sr.ht/~OWNER/PROJECT/archive/%{shortcommit}.tar.gz#/PROJECT-%{shortcommit}.tar.gz [Sourcehut] ...
	%prep %autosetup -n PROJECT-%{commit} [GitHub] %autosetup -n OWNER-PROJECT-%{shortcommit} [BitBucket] %autosetup -n PROJECT-%{commit} [GitLab] %autosetup -n PROJECT-%{shortcommit} [Sourcehut]
	If the release corresponds to a git tag with a sane numeric version, you must use that version to populate the `Version:` tag in the spec file. If it does not, look at the source code to see if a version is indicated there, and use that value. If no numeric version is indicated in the code, you may set `Version` to 0, and treat the package as a "pre-release" package (and make use of the `+%{shortcommit}+` macro). See xref:Versioning.adoc#_prerelease_versions[Prerelease versions] for details.
	Alternately, if you are using a specific revision that is either a pre-release revision or a post-release revision, you must follow the "snapshot" guidelines. They are documented here: xref:Versioning.adoc#_snapshots[Snapshots]. You can substitute `+%{shortcommit}+` for the git hash in `+%{checkout}+` in that section.
	Git Tags
	https://git-scm.com/docs/git-tag[Git tags] represent a particular code point that upstream deems important; and are typically used to mark release points.
	Bitbucket uses the `+%{shortcommit}+` identifier as part of the archive directory structure; regardless of whether you use git tag or Commit Revision to retrieve it. This is shown in the %prep section example.
	Source: https://github.com/OWNER/PROJECT/archive/%{gittag}/%{name}-%{version}.tar.gz [GitHub] Source: https://bitbucket.org/OWNER/PROJECT/get/%{gittag}.tar.gz#/%{name}-%{version}.tar.gz [BitBucket] Source: https://gitlab.com/OWNER/PROJECT/-/archive/%{gittag}/%{name}-%{version}.tar.gz [GitLab] Source: https://git.sr.ht/~OWNER/PROJECT/archive/%{version}.tar.gz#/PROJECT-%{version}.tar.gz [Sourcehut] ...
	%prep %autosetup -n PROJECT-%{gittag} [GitHub] %autosetup -n OWNER-PROJECT-%{shortcommit} [BitBucket] %autosetup -n PROJECT-%{version} [GitLab] %autosetup -n PROJECT-%{version} [Sourcehut]
	Using %\{version}
	Using `+%{version}+` in the `Source:` makes it easier for you to bump the version of a package, because most of the time you do not need to edit `Source:` when editing the spec file for the new package.
	Troublesome URLs
	When upstream has URLs for the download that do not end with the tarball name rpm will be unable to parse the tarball out of the source URL. One workaround for many cases is to construct a URL where the tarball is listed in a "URL fragment":
	Source: https://example.com/foo/1.0/download.cgi#/%{name}-%{version}.tar.gz
	rpm will then use `+%{name}-%{version}.tar.gz+` as the tarball name. If you use `+spectool -g foo.spec+` to download the tarball, it will rename the tarball for you.
	Sometimes this does not work because the upstream cgi tries to parse the fragment or because you need to login or fill in a form to access the tarball. In these cases, you have to put just the tarball's filename into the `Source:` tag. To make clear where you got the tarball, you should leave notes in comments above the `Source:` line to explain the situation to reviewers and future packagers. For example:

Loading…

None

String updated in the repository

English

Source: https://github.com/OWNER/PROJECT/archive/%{commit}/%{name}-%{shortcommit}.tar.gz [GitHub]
Source: https://bitbucket.org/OWNER/PROJECT/get/%{commit}.tar.gz#/%{name}-%{shortcommit}.tar.gz [BitBucket]
Source: https://gitlab.com/OWNER/PROJECT/-/archive/%{commit}/%{name}-%{shortcommit}.tar.gz [GitLab]
Source: https://git.sr.ht/~OWNER/PROJECT/archive/%{shortcommit}.tar.gz#/PROJECT-%{shortcommit}.tar.gz [Sourcehut]
...

English 462 characters edited Current translation Read only

a year ago

Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English	English
No related strings found in the glossary.

12562501 String information

Source string description

type: delimited block .

Flags

no-wrap, read-only

Source string location

./pages/SourceURL.adoc:209

String age

a year ago

Last updated

a month ago

Source string age

a year ago

Translation file

pot/master/pages/SourceURL.pot, string 60

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.