mirror of
https://github.com/token2/snapd.git
synced 2026-03-13 11:15:47 -07:00
e7f738b3f9
The multipass bridge has an IP address we can use to tell virtual machines where they can reach the packaging proxy. The query has been improved based on feedback from additional environments. Signed-off-by: Zygmunt Krynicki <me@zygoon.pl>
126 lines
6.2 KiB
Makefile
Executable File
126 lines
6.2 KiB
Makefile
Executable File
#!/usr/bin/make -f
|
|
# This program allows one to, relatively easily, iterate on Debian packaging in
|
|
# a way that is extremely close to that occurring in the real Debian archive.
|
|
#
|
|
# The key aspect is that packaging is done on a machine running Debian (either
|
|
# 9 or 10), with the real Debian kernel, with real build-packages (that is,
|
|
# devoid of any patches potentially present only in Ubuntu), with correct
|
|
# pristine build environment, unspoiled by convenience packages often present on
|
|
# workstation environments.
|
|
#
|
|
# The system is "portable", being able to execute on anything capable of
|
|
# running Multipass and apt-cacher-ng. The workflow is as follows:
|
|
#
|
|
# - prepare host environment:
|
|
# $ snap install multipass --classic --edge
|
|
# $ apt install apt-cacher-ng
|
|
# On Debian/Ubuntu:
|
|
# - apt install apt-cacher-ng
|
|
# On openSUSE:
|
|
# - zypper install apt-cacher-ng
|
|
# - echo "Remap-debrep: deb.debian.org/debian ; http://deb.debian.org/debian" >> /etc/apt-cacher-ng/acng.conf
|
|
# - systemctl enable --now apt-cacher-ng.service
|
|
#
|
|
# - prepare scratch build machine:
|
|
# $ ./debian-package-builder create-debian-10
|
|
# $ ./debian-package-builder prepare-debian-10
|
|
# - prepare the source package:
|
|
# On appropriate branch of the git tree compatible with
|
|
# building the debian package, e.g. https://salsa.debian.org/zyga-guest/snapd
|
|
# on the "debian" branch, issue the command
|
|
# $ apt-get build-dep ./
|
|
# $ dpkg-buildpackage -S
|
|
# TIP: you can iterate on the packing and repeat this step!
|
|
# If you need to make patches to upstream snapd parts use the "debian-patches"
|
|
# branch from the same repository, where history is broken down. Then use
|
|
# $ git format-patches 2.37..HEAD (where 2.37 is the release you are working on)
|
|
# ...to export any changes made and place the generated patches as files in the
|
|
# "debian" branch, inside the directory ./debian/patches. Make sure each
|
|
# patch is listed in the file ./debian/patches/series. Then re-run
|
|
# $ dpkg-buildpackage -S
|
|
# The resulting package will be placed in the parent directory of the root of
|
|
# the project, e.g. in $HOME/packaging/src/github.com/snapcore, assuming a
|
|
# setup where the GOPATH was set to $HOME/packaging
|
|
# - build the binary package
|
|
# While being in the directory $HOME/packaging/src/github.com/snapcore issue
|
|
# ./debian-packaging-builder build-on-debian-10
|
|
# This step will copy the source package to an appropriate multipass virtual
|
|
# machine and build it there using sbuild. Any build dependencies obtained in
|
|
# this step are automatically cached and are quick to reuse on subsequent
|
|
# runs.
|
|
#
|
|
# In case the build fails an interactive shell will be spawned by sbuild, still
|
|
# running inside the virtual machine. The package is unpacked twice, you
|
|
# really only care about the files in the _build directory. You can set
|
|
# GOPATH manually to
|
|
# GOPATH=/path/to/directory/called/_build:/usr/share/gocode and run tests and
|
|
# iterate as usual. The source tree alongside the _build directory is useful
|
|
# for comparison and for generating patches..
|
|
|
|
# Multipass uses a bridge to communicate with virtual machines it manages.
|
|
# The query below picks that bridge and prints the associated IP address.
|
|
vm_bridge_ip=$(shell ip --json addr show dev mpqemubr0 | jq --raw-output '.[]|select(.addr_info | length > 0).addr_info[] | select(.scope=="global").local')
|
|
|
|
# There must be an apt-cacher-ng installation on the host.
|
|
proxy_url=http://$(vm_bridge_ip):3142
|
|
|
|
# Packages that are not required for building snapd but are useful for interactive development.
|
|
packages=git sbuild mc devscripts avahi-daemon ssh emacs-nox vim-nox rsync
|
|
|
|
# Helpful function for running a command on the remote machine.
|
|
# Assumes that the target name ends with machine name, like below.
|
|
remote=multipass exec $* --
|
|
|
|
# URLs of openstack cloud images for our virtual machines.
|
|
debian-9-url=https://cdimage.debian.org/mirror/cdimage/openstack/current-9/debian-9-openstack-amd64.qcow2
|
|
debian-10-url=https://cdimage.debian.org/mirror/cdimage/openstack/testing/debian-testing-openstack-amd64.qcow2
|
|
|
|
PHONY: help
|
|
help:
|
|
@echo "Availale targets"
|
|
@echo " create-NAME: create a multipass virtual machine"
|
|
@echo " prepare-NAME: prepare a virtual machine for building packages"
|
|
@echo " destroy-NAME: destroy a multipass virtual machine"
|
|
@echo " build-on-NAME: copy a source package and build it on a virtual machine"
|
|
@echo
|
|
@echo "Available names are: debian-9 debian-10"
|
|
@echo "NOTE: You must provide the source package yourself"
|
|
@echo "Please read the script for additional instructions."
|
|
|
|
.PHONY: create-debian-9
|
|
create-debian-9:
|
|
multipass launch -n debian-9 -c 8 -m 4G $(debian-9-url)
|
|
|
|
.PHONY: create-debian-10
|
|
create-debian-10:
|
|
multipass launch -n debian-10 -c 8 -m 4G $(debian-10-url)
|
|
|
|
.PHONY: prepare-debian-9 prepare-debian-10
|
|
prepare-debian-9 prepare-debian-10: prepare-%:
|
|
$(remote) sudo mkdir -p /etc/apt/apt.conf.d/
|
|
$(remote) sudo sh -c 'echo "Acquire::http::Proxy \"$(proxy_url)\";" > /etc/apt/apt.conf.d/00proxy'
|
|
-$(remote) sudo apt-get update
|
|
$(remote) sudo apt-get dist-upgrade -y
|
|
$(remote) sudo apt-get install -y eatmydata $(packages)
|
|
$(remote) sudo apt-get autoremove -y
|
|
$(remote) sudo sbuild-adduser $(shell $(remote) whoami)
|
|
$(remote) cp /usr/share/doc/sbuild/examples/example.sbuildrc /home/multipass/.sbuildrc
|
|
# XXX: cloud images come with pre-made chroot?
|
|
$(remote) sudo rm -f /etc/schroot/chroot.d/sid-amd64-sbuild-*
|
|
$(remote) sudo rm -rf /srv/chroot/sid-amd64-sbuild
|
|
# NOTE: the chroot is always for sid, this is mainly to test the impact of the kernel.
|
|
$(remote) sudo http_proxy=$(proxy_url) eatmydata sbuild-createchroot --include=eatmydata,ccache,gnupg sid /srv/chroot/sid-amd64-sbuild http://deb.debian.org/debian
|
|
|
|
.PHONY: destroy-debian-9 destroy-debian-10
|
|
destroy-debian-9 destroy-debian-10: destroy-%:
|
|
multipass delete -p $*
|
|
|
|
build-on-debian-9 build-on-debian-10: build-on-%:
|
|
multipass copy-files snapd_*.debian.tar.xz snapd_*.dsc snapd_*.orig.tar.xz snapd-*.tar.gz $*:/home/multipass/
|
|
# NOTE: %s expands to a command that starts an interactive shell for debugging.
|
|
$(remote) sbuild -d sid \
|
|
--chroot-setup-commands='echo "Acquire::http::Proxy \"$(proxy_url)\";" > /etc/apt/apt.conf.d/00proxy'\
|
|
--build-failed-commands=%s \
|
|
--run-autopkgtest \
|
|
$(shell ls snapd_*.dsc | sort -r -n | head -n 1)
|