All Versions
20
Latest Version
Avg Release Cycle
35 days
Latest Release
-
Changelog History
Page 1
Changelog History
Page 1
-
v3.1.0 Changes
- Introduced
getVirtualSizeForRawImage
,cmdStdout
,hostCmdStdoutEither
,HostCommandStdout
. - ๐ More stable parsing of qemu-img info output in
getVirtualSizeForRawImage
. - ๐ Fixes a bug were size files contain garbage if newer versions of qemu-img are used.
- Introduced
-
v3.0.0 Changes
- ๐ Run the libvirt_lxc builder in an artificial pseudo-terminal if b9c is run outside a terminal.
- ๐ Relax version constraints for
hashable
dependency
๐ฅ Breaking Changes
- ๐ Change B9 configuration API: Change the field to a list
-
v2.1.0 Changes
- โ Add a new config parameter for the default Ext4 file system attributes.
- ๐ง
Ext4_64
is deprecated from now on, please useExt4
and configure theext4_attributes: ["64bit"]
.
-
v2.0.0 Changes
๐ฅ Breaking Changes
- Specify upper version bounds for all project dependencies
- ๐ Move the
interactive
flag from theB9Config
to theBuildInfo
isInteractive
now requires theBuildInfoReader
effect- Add the
runB9Interactive
function, that can by used to make thebsIsInteractive
field inBuildInfo
True
- Add the
cmdInteractive
function, that executes a command with inherited stdin/stdout ifrunB9Interactive
was called. - Remove the interactivity functionality from the
cmd
function
Minor Changes
- ๐ Fix bug in the parsing of
console
key in thesystemd-nspawn
configuration section: When a user specifiesconsole: pipe
this effects will be the same as ifconsole: read-only
was specified. - ๐ Fix bug where the timeout factor configuration option given in a configuration file is ignored.
-
v1.1.1 Changes
- ๐ When
unique_build_dirs
is enabled: use a truely random build-id, such that no matter how much or how little time passes between two consequitive builds, theBUILD_ID
s will always differ with the same probability.
- ๐ When
-
v1.1.0 Changes
- ๐ Fix unintended deletion of images that are wrongly classified as obsolete.
- โ Add a configuration parameter for guarding operations, for which
no timeout values was specified:
default_timeout_seconds
. - โฑ Introduce a configuration parameter to specify an optional timeout factor.
Since the introduction of SystemdNspawn support, most invokation of
external system commands, e.g.
mount
, are guarded by short timeouts. During testing I discovered that some systems are just slower and might run into a timeout. To mitigate that, a user can now configure a timeout factor that is applied to the internal, hard-coded time values. - ๐ Change NIX expressions to use
haskellPackages
instead ofmyHaskellPackages
.
-
v1.0.1 Changes
- โ Remove dhall
- Cleanup
b9.cabal
- Replace
fail
witherror
-
v1.0.0 Changes
- โ Add
SystemdNspawn
support - ๐ Improve command execution
- ๐ Improve nix build expressions
- โ Add
-
v0.5.69.0 Changes
February 10, 2020- โ Add new
ImageResize
optionShrinkToMinimumAndIncrease
- โ Remove the byte unit from
SizeUnit
- โ Add new utility functions to
B9.DiskImages
for image size calculations
- โ Add new
-
v0.5.68 Changes
March 11, 2019- ๐ Allow version specific config file resolution
B9 changes the config file format from time to time. To enable simultaneous use of different B9 versions with conflicting config file formats the user may provide version specific default config files, and B9 will prefer the file matching its own version most closely.
When loading its config file, B9 will now look for, and prefer config files suffixed with the longest matching version.
For example: If B9 has version 0.5.68 these config files will be tried:
- ~/.b9/b9.conf.0.5.68
- ~/.b9/b9.conf.0.5
- ~/.b9/b9.conf.0
- ~/.b9/b9.conf
If custom config file path are passed to B9 they will be tried first, and also with the version appended. For example, when runing
b9c -c other-config-path list
these paths would be tried:- other-config-path.0.5.68
- other-config-path.0.5
- other-config-path.0
- other-config-path
- /home/sven/.b9/b9.conf.0.5.68
- /home/sven/.b9/b9.conf.0.5
- /home/sven/.b9/b9.conf.0
- /home/sven/.b9/b9.conf