Re: backports
On 03-09-15 15:33, Sven Geggus wrote:
> In article <[🔎] 55E81FEE.2020403@xs4all.nl> you wrote:
>
>> For the packaging in git this should be sufficient. You need to update
>> branch in gbp.conf and Vcs-Git URL to use the jessie-backports branch.
>
> The branch should be called "jessie-backports" not "jessie", right?
Yes, the branch name is generally the codename of the distribution.
The jessie branch is for stable updates, not backports.
> Vcs-Git URL would then be like this?
> Vcs-Git: git://anonscm.debian.org/pkg-grass/sfcgal.git jessie-backports
>
> Or how is the branch supposed to be specified?
Using -b as documented in the Policy:
"
In the case of Git, the value consists of a URL, optionally followed
by the word -b and the name of a branch in the indicated repository,
following the syntax of the git clone command. If no branch is
specified, the packaging should be on the default branch.
"
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-VCS-fields
See for example the first commit of the mapserver backport:
http://anonscm.debian.org/cgit/pkg-grass/mapserver.git/commit/debian?h=jessie-backports&id=1aeaafbe4edf96f3091ce42679b2ec268f3c0483
The debian/gbp.conf uses:
# The default name for the Debian branch is "master".
# Change it if the name is different (for instance, "debian/unstable").
debian-branch = jessie-backports
And debian/control:
Vcs-Git: git://anonscm.debian.org/pkg-grass/mapserver.git -b
jessie-backports
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Reply to: