You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

RELEASE_NOTES 1.7KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344
  1. 2017-02-14
  2. ----------
  3. - VirtualBox launches are now headless. You can use the VirtualBox Manager to open the console UI if needed.
  4. - Debian on VirtualBox is supported via Vagrant Cloud images
  5. - Note that Debian on kvm is currently not supported because vmbuilder fails in the grub install stage
  6. - git submodule support - any submodules are cloned and checked out
  7. - Note that lxc-execute in Ubuntu 17.10 has a showstopper bug in stdin handling
  8. 2015-12-12
  9. ----------
  10. Since OpenSSH removed support for DSS, Gitian now uses RSA keys instead. Base images should be regenerated.
  11. 2015-05-16
  12. ----------
  13. LXC support has been revamped:
  14. * debootstrap is now used directly, so that no kernel or grub packages are installed
  15. * 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
  16. 2015-03-23
  17. ----------
  18. Now ensuring that `apt-get dist-upgrade` occurs at least once before package manifest
  19. is computed. This is because distributions usually don't store old versions of packages
  20. in the repos, so we can't download the exact package version we have installed if it's
  21. out of date.
  22. gbuild now has a --upgrade flag that forces an upgrade after the first one.
  23. Other Notes
  24. ===========
  25. Important:
  26. 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.
  27. To enable this now (required for Ubuntu 14.04), do:
  28. export LXC_EXECUTE=lxc-execute
  29. 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.