This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package curtin - 0.1.0~bzr425-0ubuntu1~16.04.1
---
curtin (0.1.0~bzr425-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
[ Scott Moser ]
* debian/new-upstream-snapshot: add writing of debian changelog entries.
[ Ryan Harper ]
* New upstream
I can verify that the build in xenial-proposed resolves this bug using
the example config attached.
Running an installation using curtin packed on a system with the current curtin
release in xenial-updates installation fails.
Curtin release:
root@tmp:/tmp# apt-cache policy curtin
curtin:
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Fix Released
** Changed in: curtin (Ubuntu Xenial)
Status: New => Fix
