livecd-rootfs/debian/install

auto-markable-pkgs usr/share/livecd-rootfs
live-build usr/share/livecd-rootfs
get-ppa-fingerprint usr/share/livecd-rootfs
minimize-manual usr/share/livecd-rootfs
magic-proxy usr/share/livecd-rootfs
lp-in-release usr/share/livecd-rootfs
Mark packages as autoinstalled using apt-mark in the chroot instead of using python-apt that potentially starts talking to the build system's dbus causing various problems. LP: #1835406 2019-11-12 16:10:35 +01:00			`auto-markable-pkgs usr/share/livecd-rootfs`
start live-build configuration 2011-06-10 18:59:01 +01:00			`live-build usr/share/livecd-rootfs`
The EXTRA_ARCHIVES environment variable defined in 2.212 doesn't quite work properly because it doesn't allow for signing key configuration. Rename it to the more domain-specific EXTRA_PPAS (which is now a space-separated sequence of <ppa-owner>/<ppa-name> pairs), and fetch signing keys for those from Launchpad using python3-software-properties. 2014-05-19 15:28:05 +01:00			`get-ppa-fingerprint usr/share/livecd-rootfs`
Reorganize minimal-manual file location. This also gets rid of the change to debian/rules 2018-09-18 11:44:06 +02:00			`minimize-manual usr/share/livecd-rootfs`
Inject a proxy into the build providing a snapshot view of the package repo. When the REPO_SNAPSHOT_STAMP variable is set, the auto/build script will attempt to launch a transparent HTTP proxy on port 8080, and insert an iptables rule to redirect all outgoing HTTP requests to this proxy. The proxy, contained in the `magic-proxy` Python script, examines each request and silently overrides those pointing to InRelease files or files that are listed in InRelease files. It will instead provide the contents of the requested file as it was at REPO_SNAPSHOT_STAMP, by downloading the corresponding asset "by hash". 2018-12-17 10:19:35 +01:00			`magic-proxy usr/share/livecd-rootfs`
			`lp-in-release usr/share/livecd-rootfs`