- 04 Jan, 2018 1 commit
-
-
intrigeri authored
-
- 16 Dec, 2017 1 commit
-
-
intrigeri authored
-
- 10 Nov, 2017 1 commit
-
-
intrigeri authored
Fix reproducibility of builds of topic branches that lag behind their base branch with the mergebasebranch build option enabled (refs: #14946) Two otherwise identical merge commits done at different times get different IDs, and we happen to embed in the ISO the ID of the commit we're building from.
-
- 09 Nov, 2017 1 commit
-
- 08 Nov, 2017 1 commit
-
-
intrigeri authored
-
- 15 Sep, 2017 1 commit
-
-
intrigeri authored
-
- 14 Aug, 2017 2 commits
- 22 May, 2017 1 commit
-
-
intrigeri authored
-
- 18 May, 2017 1 commit
-
-
intrigeri authored
It has replaced 4.9.0-2 in Debian testing so that's necessary for Stretch-based builds using recent APT snapshots to work.
-
- 17 Apr, 2017 2 commits
-
-
intrigeri authored
Due to a mistake I did wrt. shell quoting in commit:6fcb2323, we were actually passing "--id '1490015021'" (with the single quotes), which is an invalid ID. So isohybrid was aborting. As a result isohybrid stopped creating non-reproducible ISOs, but the resulting ISO images were not hybrid'ed. Let's not bother passing $SOURCE_DATE_EPOCH, and just pass a fixed value.
-
intrigeri authored
Pass --verbose to isohybrid, to debug test regressions introduced by the reproducible builds branch.
-
- 15 Mar, 2017 1 commit
-
-
intrigeri authored
-
- 14 Mar, 2017 1 commit
-
-
intrigeri authored
Otherwise, a random one is used, that makes the build unreproducible even when the content of the ISO filesystem matches.
-
- 08 Mar, 2017 1 commit
-
-
intrigeri authored
-
- 02 Mar, 2017 3 commits
-
-
intrigeri authored
-
- 28 Feb, 2017 1 commit
-
- 30 Jan, 2017 1 commit
-
-
intrigeri authored
-
- 27 Dec, 2016 1 commit
-
-
intrigeri authored
-
- 20 Dec, 2016 1 commit
-
-
intrigeri authored
-
- 19 Dec, 2016 1 commit
-
- 06 Dec, 2016 1 commit
-
-
intrigeri authored
It's the default on x86_64 since 4.8.4-1~exp1; according to Documentation/kernel-parameters.txt the vsyscall= option only makes sense on x86_64 anyway.
-
- 20 Nov, 2016 1 commit
-
-
intrigeri authored
-
- 15 Nov, 2016 1 commit
-
-
intrigeri authored
-
- 07 Nov, 2016 1 commit
-
- 03 Nov, 2016 1 commit
-
- 30 Oct, 2016 1 commit
-
- 21 Sep, 2016 1 commit
-
- 20 Sep, 2016 1 commit
-
-
anonym authored
This reverts commits: * ab562fd4 * c0bc655c * 80d0667a The last minute attempt to include it in Tails 2.6 was a bad (too hasty) idea, e.g. USB installations don't boot (pre-init results in "FAT-fs (sdb1): IO charset ascii not found"). Also it seems that the backport of Linux 4.7 hasn't gone through the proper Debian QA process.
-
- 19 Sep, 2016 1 commit
-
-
anonym authored
While preparing Tails 2.6 it was discovered that our previous last minute bump of the 'debian' snapshot (to get Jessie 8.6) caused linux-compiler-gcc-4.9-x86 to be updated to a version from another Linux source version (4.7) than what we planned to install (4.6), resulting in the tagged snapshot being impossible to create since it would require two different linux source packages which we do not support. Note that this includes bumping the aufs4-standalone Git submodule to the latest branch for Linux 4.7.
-
- 14 Jul, 2016 1 commit
-
-
intrigeri authored
4.5.0-0.bpo.2 is not available anymore.
-
- 09 Jun, 2016 1 commit
-
- 08 Jun, 2016 1 commit
-
- 07 Jun, 2016 1 commit
-
-
intrigeri authored
This is essentially a squashed version of feature/8415-overlayfs, purged of its overlayfs-specific bits, and that fetches the kernel from jessie-backports (instead of from sid) to ease compiling out-of-tree and dkms modules. At this stage, the resulting ISO won't boot since it'll lack both aufs and overlayfs. refs: #10298 To achieve that: * Install the 686 kernel flavour instead of the obsolete 586 one. * Rename the amd64 kernel via binary_local-hooks. lb_binary_syslinux depends on --linux-flavours, but we can't pass amd64 in there anymore (due to lack of multiarch support) so we need to rename the second (amd64) kernel ourselves. * APT, dpkg: add amd64 architecture. The amd64 kernel flavour is not built anymore for the i386 architecture, so we need to use multiarch now. * Temporary disable dkms modules building. Building them for the amd64 kernel requires installing an amd64 toolchain, that conflicts with the i386 one and with lots of packages we need. Let's come back to it later (refs: #9969).
-
- 28 Feb, 2016 1 commit
-
- 17 Jan, 2016 1 commit
-
-
intrigeri authored
Recent live-boot now defaults to overlayfs, which we don't support yet.
-
- 01 Jan, 2016 1 commit
-
-
intrigeri authored
Since live-boot (3.0~a27-1) and this commit: commit 4e54d60d7f69ae3441e519e5611bd7ea48a8be19 Author: Daniel Baumann <daniel@debian.org> Date: Sun Apr 8 18:29:45 2012 +0200 Using 'persistence' (noun) rather than 'persistent' (adjective/adverb) everywhere. ... we should have been passing 'nopersistence' instead of 'nopersistent' on the kernel command line. Will-fix: #10831
-
- 15 Sep, 2015 1 commit
-
-
Signed-off-by:
Chris Lamb <lamby@debian.org>
-