Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

This can be useful for (derivatives of) older Debian suites like jessie,
which don't have automatic debug symbols.

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

This reduces the need to have a giant metapackage with all the shared
libraries' detached debug symbols; now we only need to do that for
libraries that are still using legacy debug symbols (foo-dbg).

This also means we tolerate transient uninstallability for debug
symbols: we'll simply produce a runtime without those debug symbols.
This is particularly important when taking binaries from
debian-security, which does not have a corresponding debug symbols
archive (although when security updates get mirrored into
proposed-updates, their detached debug symbols do appear there).

Finally, it also means we don't run into problems with version skew
between debug symbols and the actual libraries, particularly when
adding buster-proposed-updates-debug (which, in general, will be
strictly newer than buster + buster-security) in the hope of getting
detached debug symbols for buster-security.

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

It's rather out of place there.

Signed-off-by: Simon McVittie <smcv@collabora.com>

This hasn't actually worked since I switched to using debos, and doesn't
seem to have been necessary.

Signed-off-by: Simon McVittie <smcv@collabora.com>

The only Ubuntu precise derivative I'm interested in is now
self-contained, so flatdeb doesn't need to be able to debootstrap
from precise any more.

Signed-off-by: Simon McVittie <smcv@collabora.com>

In some older suites, building packages will fail in a merged-/usr
chroot (#843073). Building packages in a merged-/usr chroot is also,
in general, not guaranteed to result in binaries that work correctly in
an unmerged-/usr environment, so we should probably prefer to build a
more traditional sysroot.

Signed-off-by: Simon McVittie <smcv@collabora.com>

This should speed up packing and rsync'ing of the sysroot and
base tarballs.

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

This is faster than gzip, and apparently more rsyncable.

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

This points to a Github repository that is no longer up, and was never
as polished as the version of Steam maintained by the Flathub community.

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

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>

Signed-off-by: Simon McVittie <smcv@collabora.com>

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>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Fixes: 5128513c


Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

If the runtime is to be used as an unmanaged extension or with a
non-Flatpak container-runner, or if it's going to be postprocessed or
transferred as a tarball to somewhere where it can be committed to a
libostree repository, it's time-consuming and not necessarily useful
to commit it here.

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>