ANN: snapcraft 2.0 is now available

[Leo Arias]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2016-01-22 11:59, Mark Shuttleworth wrote:
> May be so, but our bad handling of that situation is a bug worth
> fixing nonetheless :)

We have a pull request in flight to use non-ascii
chars only when strictly necessary. I think that will make snapcraft
work even with ascii decoding. (I need to check some more scenarios).
ogra's bug report seems to be the right way to avoid the problem
altogether. Our lxc containers and snappy should just handle UTF-8
always. If after all that we are still finding systems without locales
crashing the build, we can just refuse to start the build and give a
nicer error, but I think this won't be necessary.

pura vida
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWorDFAAoJEIUvYw0No8DgTpgQAI6OO6buLURyIENgplsUqfxy
vpGZ3HBVNfyoDkjg9N47x2u01TwyNeH1QwCzl5L+sytKbPyzTOUgrmG71GN2aadg
5am+9tzeQj4kMRnTScwjyx/ewRQHTTOw9prIfqmFC85PNnZQb8TEl6kE0aBcfCeU
+HhjTb/T3nl7WwmEqJuHYuuzLIcfr+JRg9BoOueWsMD8z7IWGMT8QY7xJufKLM8I
fyrhiZjMonJcpSQ1WhE/cnDOw3b+DhhIRybynLYaLdxfZIlcztzrRaeNmOxUh5Ia
zMVNY/RNjeRxewIfevLpAf+cUBHa/FNZHdEL9J4ipgjl/14v9t3CYNMuqGBVvN2l
i1VeNfLWcWKJ80jKA+HdLEbEMiIB7eiSA99Z7tu+4nMTnbtX1TffFYD/roul0MGg
HVJV//k9rj+ZiyFMdMdzjTlwA3dQ5yDwAhYxQi3r751faBwyaO7QjI6O4mioRjzm
Umrkef123SfV1fM96M6vTMg3qx0fqQzXiDJGjE81FvENnPxy2Q11iEVhMy0QIThu
PdbmhGlr9lavhDa/X5Hko+YtecE/Xl0tne8B66r0dvXLSXB0BRG5g/AFURtMLWN1
BIXlt3+Svo9QIsL15Zh7uuJNKVM1DxCmJhKNjTFkWfaCLuQVD+ZvvXmhCU3nfrIp
b0uAf0er2qdZD5rHOAsK
=ZKdq
-----END PGP SIGNATURE-----