


  1. 2019-05-23
  2. ----------
  3. - Add `--skip-fetch` argument that skips fetching the latest remote source
  4. 2019-05-13
  5. ----------
  6. - No longer fetch repository from remote when the directory already exists
  7. 2017-02-14
  8. ----------
  9. - VirtualBox launches are now headless. You can use the VirtualBox Manager to open the console UI if needed.
  10. - Debian on VirtualBox is supported via Vagrant Cloud images
  11. - Note that Debian on kvm is currently not supported because vmbuilder fails in the grub install stage
  12. - git submodule support - any submodules are cloned and checked out
  13. - Note that lxc-execute in Ubuntu 17.10 has a showstopper bug in stdin handling
  14. 2015-12-12
  15. ----------
  16. Since OpenSSH removed support for DSS, Gitian now uses RSA keys instead. Base images should be regenerated.
  17. 2015-05-16
  18. ----------
  19. LXC support has been revamped:
  20. * debootstrap is now used directly, so that no kernel or grub packages are installed
  21. * an attempt has been made to eliminate cases where an update of a package can fail because the container is missing a real init/upstart process
  22. 2015-03-23
  23. ----------
  24. Now ensuring that `apt-get dist-upgrade` occurs at least once before package manifest
  25. is computed. This is because distributions usually don't store old versions of packages
  26. in the repos, so we can't download the exact package version we have installed if it's
  27. out of date.
  28. gbuild now has a --upgrade flag that forces an upgrade after the first one.
  29. Other Notes
  31. Important:
  32. We are planning on switching from using lxc-start to using lxc-execute. lxc-execute requires lxc-init (or init.lxc) to be available on the guest at one of the expected places. You might have to manually install lxc on your base VM image or recreate the image.
  33. To enable this now (required for Ubuntu 14.04), do:
  34. export LXC_EXECUTE=lxc-execute
  35. If your guest is more recent than the host, all bets are off, since lxc-execute may not be able to find the lxc init.