On 05/03/2026 13:53, Samuel Thibault wrote:
Michael Kelly, le jeu. 05 mars 2026 13:51:08 +0000, a ecrit:
2) The package versions of those in my sample are moving on and failing
build dependencies. I can remove the odd one but that defeats the point of
reproducing the build sequence that boralus used. Is it realistic for me to
somehow setup a repository that has copies of packages that I can rely on?
You can use a snapshot.debian.net snapshot to always use the same set of
available packages.
What an amazing resource. I had no idea that snapshots were taken so
frequently.
There's a sequence of 33 package built by boralus between 28/02/26:2327
and 01/03/26:0411 so I've selected the following for the core of the
chroot and for the apt configuration:
deb http://snapshot.debian.org/archive/debian-ports/20260228T200326Z sid
main
deb http://snapshot.debian.org/archive/debian-ports/20260228T200326Z
unreleased main
deb http://snapshot.debian.org/archive/debian-ports/20260228T200326Z
experimental main
deb-src http://snapshot.debian.org/archive/debian/20260228T200326Z sid main
The first 11 packages build but I can't build haskell-skylighting due to
unmet dependencies:
libghc-skylighting-core-dev-0.14.7-ec73a is available
but
libghc-skylighting-core-dev-0.14.7-4725a seems to be required.
Can someone explain this to me? Is it to do with the 'incoming'
repositories?
3) I had tried running the build script without a mach-defpager running at
all (like boralus) but my system soon locks awaiting pages. I'm puzzled how
boralus manages to run for longer periods of time.
It has 3G ram.
My VM also has 3G ram. I'll look again at dropping mach-defpager because
it is important to mimic the buildd as closely as possible.
Thanks,
Mike.
