- Jan 15, 2020
-
-
Simon McVittie authored
This was a prototype runtime based on Ubuntu 18.04 'bionic'. It was replaced with 'soldier', based on Debian 10 'buster', because Debian allows redistribution of unmodified binary packages. (A side benefit is that Debian 10 is about a year newer than Ubuntu 18.04.) Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 09, 2020
-
-
Simon McVittie authored
We don't install the default version of python3, which is python3.2 in scout, because that's rather old. Make "#!/usr/bin/env python3" and "#!/usr/bin/python3" scripts work anyway. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 02, 2020
-
-
Simon McVittie authored
We no longer use this. Instead, Steam Runtime containers are built as part of the official Steam Runtime infrastructure. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 28, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Ubuntu 12.04 somehow has libnss3-dbgsym and libnspr4-dbgsym packages that are Multi-Arch: no, even though their corresponding libraries are Multi-Arch: same. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 27, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 25, 2019
-
-
Simon McVittie authored
If we have (for example) 400 -dbgsym packages to install, invoking apt 400 times is rather slow due to startup overhead (locking, reading and updating the database). Instead, invoke apt-cache once to find out what is available, and use that to compose a single very large apt-get command-line. Similarly, we can summarize what was and wasn't installed from the information we already have, without having to invoke apt a lot. 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>
-
- Oct 08, 2019
-
-
Simon McVittie authored
-
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>
-
Simon McVittie authored
We distribute the SDK and sysroot in tarballs, so they don't need this. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 07, 2019
-
-
Simon McVittie authored
-
Simon McVittie authored
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>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 03, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
-
Simon McVittie authored
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>
-
- Oct 02, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Most Linux distributions either use Red-Hat-style biarch (lib and lib64) or Debian-style multiarch (lib/i386-linux-gnu and lib/x86_64-linux-gnu), and configure glibc to look for locales in /usr/lib/locale. glibc itself has special cases to do this for common "lib64" architectures like x86_64. This is analogous to the way systemd user units and tmpfiles are always in /usr/lib/systemd, never in /usr/lib64/systemd or /usr/lib/*-linux-gnu/systemd. However, Arch Linux and its derivatives use currently a variation of biarch with lib32 and a 64-bit lib, and create a symlink /usr/lib32/locale -> ../lib/locale rather than configuring the 32-bit glibc to look in /usr/lib/locale in the first place. When using pressure-vessel we might have to use a host system glibc, so we need to make locales available in both locations. Create the same symlink that Arch Linux does. For symmetry, also create one in /usr/lib64 when we build 64-bit-capable runtimes. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 19, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Current flatdeb ignores these anyway. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
-
Simon McVittie authored
It's rather out of place there. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
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>
-
Simon McVittie authored
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>
-
Simon McVittie authored
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>
-
- Sep 11, 2019
-
-
Simon McVittie authored
This locale is frequently hard-coded in places that need to parse C-style floating point constants or get a predictable sorting order, even though those places should ideally be using C (if the C locale didn't lead to misbehaviour in the presence of non-ASCII characters) or C.UTF-8 (if the C.UTF-8 locale from Debian and Fedora had been accepted upstream[1], which at the moment it hasn't). [1] https://sourceware.org/bugzilla/show_bug.cgi?id=17318 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 10, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 22, 2019
-
-
Simon McVittie authored
-
Simon McVittie authored
This should speed up packing and rsync'ing of the sysroot and base tarballs. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 21, 2019
-
-
Simon McVittie authored
apt doesn't seem to be clever enough to fall back to the version from stable if the version in proposed-updates isn't installable. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
-