- Aug 13, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 08, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This is faster than gzip, and apparently more rsyncable. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 16, 2019
-
-
Simon McVittie authored
Legacy path-based names are more difficult to use against a sysroot: if your sysroot is in ~/sysroot and your detached debug symbols are in ~/symbols, and you want to find detached debug symbols for ~/sysroot/usr/lib/x86_64-linux-gnu/libfoo.so.0 by using "gdb -iex set-debug-file-directory /home/me/symbols:/usr/lib/debug", then you would have to create a symlink ~/symbols/home/me/sysroot/usr pointing to ~/symbols/usr. Build-ID-based names do not have this issue. This change is based on code in steam-runtime, which uses symbolic links. Hard links are a somewhat better fit for OSTree, since they are automatically deduplicated, and also have the advantage that multiple .build-id directories can easily be combined with rsync. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 03, 2019
-
-
Simon McVittie authored
This file is read by the default /etc/bash.bashrc in Debian and included as a prefix to the prompt, in this style: (contents of /etc/debian_chroot) user@host:~$ It is automatically populated with the chroot name by schroot, but not by other container tools like Docker and Flatpak. We might as well give it a useful value for all Flatdeb-generated containers. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 16, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 08, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
For example, the image can be built with a local mirror or an unreleased version of the distribution, then configured to use a generic public mirror or the release version of the distribution to download any subsequent packages. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 11, 2019
-
-
Simon McVittie authored
This tells us the runtime name (package set) and architecture. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Mar 13, 2019
-
-
Simon McVittie authored
This makes it easier to tell what has been run. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Mar 12, 2019
-
-
Simon McVittie authored
One prominent use for the sysroot tarball is with schroot, but schroot assumes that it can safely copy /etc/passwd and /etc/group from the host system into the chroot. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Mar 07, 2019
-
-
Simon McVittie authored
This means all the packages we install are consistent with the apt lists from the base tarball. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Mar 04, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 28, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 27, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 26, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 15, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 14, 2019
-
-
Simon McVittie authored
This gets confusing if we start introducing apt archives, commonly referred to as repositories. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 12, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 10, 2019
-
-
Simon McVittie authored
Also purge them again after a user-defined post_script, in case it removed further packages. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 09, 2019
-
-
Simon McVittie authored
There's no substitute for this if what you want to process is the complete apt-format metadata. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 27, 2018
-
-
Simon McVittie authored
In principle it can work, but in practice writing to the artifact directory via the 9p (Plan 9) virtual filesystem imposes a limit on open files. Export the Flatpak runtime from the virtual machine as a tarball instead, and commit it on the host system. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 12, 2018
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
For the moment flatdeb wraps debos, creating a new, temporary recipe directory and writing out overlays and other auxiliary files based on flatdeb's own configuration. At some point it might make sense to turn this inside out, with debos driving the process and flatdeb just providing a series of hooks and template files, but while we're using two separate debos runs it's easier this way round. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-