The latest release of Baserock (Water Bomb) has a broken versions of
/usr/bin/gperf and /usr/lib/libgmpxx.so. This issue only affects the
Corrected versions of the disk image and staging filler have now been
uploaded, and are available from the following URL:
If you have already downloaded Water Bomb, there is a hot fix available
at the following URL:
This file is only 982KB in size, and contains the chunks that were
broken in the original release. In order to apply the fix, please follow
1. download the file into /src on your Water Bomb virtual machine
2. cd / && tar xvf /src/water-bomb-x86_64-fix.tar.gz
3. add the file to the 'staging-filler' field in morph.conf
(this field is a comma-separated list of tarballs)
The problem in the original Water Bomb release is that gperf and
libgmpxx are linked against the shared version of libstdc++, but this is
not currently present in Baserock at all. This means that gperf cannot
be executed, because libstdc++.so is missing. As stated above, this
problem is *only* present in the x86_64 image and the x86_64 staging
filler of Water Bomb.
I apologise for my mistake in building and testing the release.
Water Bomb is released
The [Baserock team], and [Codethink Limited] are proud to announce
the fourth public release of the Baserock system build
infrastructure. In this release, [Water Bomb] we are pleased to
be able to showcase the ability of Baserock to build a system
entirely from [Git repositories].
What is in Water Bomb
Water Bomb is a development release of Baserock. It consists of
four VM images; `base` and `devel` for `x86_32` and `x86_64`.
`base` is a relatively small system, used as an example target
image, and `devel` is a system with all the tools required to
build itself, plus development conveniences like text editors and
debugging tools. The images are available on the [download page].
What has changed since Square Pyramid?
The `morph build` command can now build components directly from a
system branch workspace - so it's possible to make changes and
build a new system without having to push your code anywhere.
We are in the process of migrating the server software on
git.baserock.org. As part of this, the repos that are part of
Baserock itself now have an extra 'baserock/' component in their
URLs, so `baserock:morphs` becomes `baserock:baserock/morphs`, etc.
New command: `morph expand-repo`, to expand URL prefixes on the
$ morph expand-repo baserock:baserock/morphs
New command: `morph status`, to show what repositories in a system
branch have outstanding changes:
$ morph status
On branch baserock/release/water-bomb, root baserock:baserock/morphs
baserock:baserock/morphs: uncommitted changes
e2fsprogs was added to the devel stratum.
util-linux was updated, to fix a problem with `losetup`.
Minor changes and bugfixes:
* Baserock systems have an `/etc/os-release` file, and a .meta
file stored in `/baserock` along with the .meta files for the
chunks and strata.
* Disk images are now compressed with `gzip -1` after building
* `morph --help` output is better organised
* `morph merge` warns if a chunk will be petrified or unpetrified
as the result of a merge.
* Morphologies are validated more thoroughly when processed, to
catch spelling mistakes in key names and other issues.
* Tarball rootfs support now works correctly
How do I get started?
You can find a [quick start] guide on the [Baserock wiki] and also
a short guide on [developing with Baserock] which follows on from
the quick start and shows you how to get to the point of proving
you can build Baserock within Baserock.
From that point on, your imagination is the limit. We're working
on several things we hope to showcase later in the year and you
can follow some of that development in the [Git repositories] we
How do I get in contact
The Baserock project has an [IRC channel] and [mailing list] for
developers to gather and discuss anything associated with
Baserock. It is strongly recommended that you use the IRC and
lists to contact the team for anything associated with the public
development of Baserock. We also have a mailing list for
[announcements] which will be notified of any new releases or big
developments in Baserock.
Should you manage to find a bug in Baserock, we'd like to hear
from you. You can find our [bug reporting guidelines] on the
Baserock wiki and we will do our best to help.
We hope you enjoy experimenting with Baserock and look forward to
hearing about any cool things you do with our work.
(On behalf of the Baserock team)
[Codethink limited]: http://www.codethink.co.uk/
[Baserock wiki]: http://wiki.baserock.org/
[Baserock team]: http://wiki.baserock.org/team/
[Water Bomb]: http://wiki.baserock.org/releases/water-bomb/
[Git repositories]: http://git.baserock.org/cgit/
[IRC Channel]: http://wiki.baserock.org/irc-channel/
[mailing list]: http://wiki.baserock.org/mailinglist/
[download page]: http://wiki.baserock.org/download/
[quick start]: http://wiki.baserock.org/quick-start/
[developing with Baserock]: http://wiki.baserock.org/devel-with/
[bug reporting guidelines]: http://wiki.baserock.org/bug-reporting/