Changes
Page history
Create Debian Castle Game Engine Packaging
authored
Apr 11, 2021
by
Abou Al Montacir
Show whitespace changes
Inline
Side-by-side
Debian-Castle-Game-Engine-Packaging.md
0 → 100644
View page @
2c401142
# Get sources
## Clone with SSH
```
sh
git clone git@salsa.debian.org:pascal-team/castle-game-engine
```
## Clone with HTTPS
```
sh
git clone https://salsa.debian.org/pascal-team/castle-game-engine
```
## Update local copy
```
sh
git remote update
# or $(git fetch)
git checkout pristine-tar
git rebase
git checkout upstream
git rebase
git checkout master
git rebase
```
# Integrate a new upstream release
## Apply upstream changes
Normally one would execute the following command.
```
sh
gbp import-orig
--uscan
```
and if you want to push to experimental first (make sure your experimental and upstream-experimental branches are up-to-date and/or are properly created)
```
sh
gbp import-orig
--uscan
\
--debian-branch
=
experimental
--upstream-branch
=
upstream-experimental
```
## Update dch log
```
sh
gbp dch
-c
-R
```
But please review and enhance the generated changelog, not everything needs to be mentioned
## Build packages
```
sh
gbp buildpackage
```
or
```
sh
pbuild
```
or source only
```
sh
cd
..
dpkg-source
-i
\.
git
-b
castle-game-engine
cd
-
dpkg-genchanges
-sa
-S
>
../castle-game-engine
${
DEBIAN
-VERSION##*
:
}
_source.changes
```
or whatever you like to build
## Git tag release
```
sh
git tag debian/
${
DEBIAN
-VERSION_with_tildes_converted_to_underscore
}
\
-m
"Debian release
${
DEBIAN
-VERSION
}
"
```
## Push changes
```
sh
git push origin pristine-tar upstream master
--tags
```
\ No newline at end of file