[Pkg-systemd-maintainers] Package build process

[Michael Stapelberg]

Hi Ryan,

Ryan Kuester <rkuester at insymbols.com> writes:
> While we're on the subject of the systemd package's build process
> (gitpkg vs. git-buildpackage), would someone please explain what the
> current process looks like? I'm not familiar with gitpkg other than
> studying the manpage, and I can't figure out how to rebuild 204-5, for
> example.
That’s an excellent question, and the fact that this needs special
documentation is a point in support of my quest to switch to
git-buildpackage, I think :).

Here is what works for me:

git clone git+ssh://git.debian.org/git/pkg-systemd/systemd.git
cd systemd
git checkout upstream-fixes
git checkout pristine-tar
git checkout debian
cat >> .git/config <<'EOT'
[gitpkg]
    pre-export-hook = /usr/share/gitpkg/hooks/pristine-tar-pre-export-hook
    deb-export-hook = ./debian/systemd-hack-up-the-source.hook
    orig-compressor = xz
    create-fake-orig = false
    force-overwrite-orig = false
EOT
gitpkg debian
cd ../deb-packages/systemd
cowbuilder *.dsc

Note that currently you also need to throw in the following to make the
“gitpkg debian” step actually work:

git checkout upstream-fixes
git tag upstream-fixes_204-8
git checkout debian

But I am not sure whether I should push that tag or not. We’d need to
force-update it every time we push a new commit to the upstream-fixes
branch.

-- 
Best regards,
Michael