I verified this for trusty deployment with maas 1.7.0+bzr3299-0ubuntu3~trusty1 and curtin version was 0.1.0~bzr195-0ubuntu1~14.04.1~ppa0.
The steps to test this was to edit the root-tgz after uncompressing and extracting it, doing a chroot. I then did a sudo apt-get install deja-dup-backend-gvfs which also installed deja-dup and fonts-dejavu-core. The non-ascii characters were in description for deja-dup-backend-gvfs: Remote server support for Déjà Dup. After exiting, I then recreated the compressed tgz image from the modified files and copied the file to cached filename in /var/lib/maas/boot-resources/cache, and to root-tgz file in /var/lib/maas/boot-resources/current/ubuntu/amd64/generic/trusty/daily. Finally, I restarted tgt.
I then deployed trusty through maas which worked. The 2nd test was to do a juju bootstrap which also passed. To make sure that I was dealing with the right image, I verified that the deja-up packages were installed on the deployed node.
I verified this for trusty deployment with maas 1.7.0+bzr3299- 0ubuntu3~ trusty1 and curtin version was 0.1.0~bzr195- 0ubuntu1~ 14.04.1~ ppa0.
The steps to test this was to edit the root-tgz after uncompressing and extracting it, doing a chroot. I then did a sudo apt-get install deja-dup- backend- gvfs which also installed deja-dup and fonts-dejavu-core. The non-ascii characters were in description for deja-dup- backend- gvfs: Remote server support for Déjà Dup. After exiting, I then recreated the compressed tgz image from the modified files and copied the file to cached filename in /var/lib/ maas/boot- resources/ cache, and to root-tgz file in /var/lib/ maas/boot- resources/ current/ ubuntu/ amd64/generic/ trusty/ daily. Finally, I restarted tgt.
I then deployed trusty through maas which worked. The 2nd test was to do a juju bootstrap which also passed. To make sure that I was dealing with the right image, I verified that the deja-up packages were installed on the deployed node.