<feed xmlns='http://www.w3.org/2005/Atom'>
<title>propellor/doc/todo/bug_in_diskimage_finalization.mdwn, branch master</title>
<subtitle>gnusosa's centralized propellor repository for hosts spin-up.
</subtitle>
<id>https://git.gnusosa.net/propellor/atom?h=master</id>
<link rel='self' href='https://git.gnusosa.net/propellor/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.gnusosa.net/propellor/'/>
<updated>2017-03-24T17:58:13Z</updated>
<entry>
<title>fix diskimage finalization bug</title>
<updated>2017-03-24T17:58:13Z</updated>
<author>
<name>Joey Hess</name>
<email>joeyh@joeyh.name</email>
</author>
<published>2017-03-24T17:57:47Z</published>
<link rel='alternate' type='text/html' href='https://git.gnusosa.net/propellor/commit/?id=25114d92a53f519aaf874dc0df9bfdd9f8dd9964'/>
<id>urn:sha1:25114d92a53f519aaf874dc0df9bfdd9f8dd9964</id>
<content type='text'>
  * Fix bug when using setContainerProps with a chroot that prevented
    properties added to a chroot that way from being seen when propellor
    was running inside the chroot. This affected disk image creation, and
    possibly other things that use chroots.

The problem was, propagateChrootInfo was being passed the initial
version of the Chroot, but then the Chroot got more properties
added, and so those were not recorded in the _chroot info.

Fix was simply to make InfoPropagator be passed the Chroot as an
additional parameter, so Chroot.provisioned' can pass in the final
Chroot to it.
</content>
</entry>
<entry>
<title>bug report</title>
<updated>2017-03-24T14:59:44Z</updated>
<author>
<name>Joey Hess</name>
<email>joeyh@joeyh.name</email>
</author>
<published>2017-03-24T14:59:44Z</published>
<link rel='alternate' type='text/html' href='https://git.gnusosa.net/propellor/commit/?id=4d3a3caa6bd3ebea92bdcf3122922c881a4b2a3a'/>
<id>urn:sha1:4d3a3caa6bd3ebea92bdcf3122922c881a4b2a3a</id>
<content type='text'>
</content>
</entry>
</feed>
