Bug#873919: make dpkg-buildpackage default locale UTF-8

2017-09-21 Thread Guillem Jover
On Thu, 2017-09-07 at 17:47:46 +0200, Michael Biebl wrote: > On Fri, 1 Sep 2017 10:57:42 +0200 Guillem Jover wrote: > > As long as the project considers debian/rules the main entry point to a > > package build, I'm not planning on predefining new general purpose > > environment variables from dpkg

Bug#873919: make dpkg-buildpackage default locale UTF-8

2017-09-07 Thread Michael Biebl
On Fri, 1 Sep 2017 10:57:42 +0200 Guillem Jover wrote: > As long as the project considers debian/rules the main entry point to a > package build, I'm not planning on predefining new general purpose > environment variables from dpkg-buildpackage that would otherwise not > be set by the builder. >

Bug#873919: make dpkg-buildpackage default locale UTF-8

2017-09-01 Thread Ivan Shmakov
> Hans-Christoph Steiner writes: > Package: dpkg-dev > More and more packages are adding unicode files I assume you mean “UTF-8 filenames” here (per below), right? > as unicode support has become more reliable and available. What are the use cases for such filenames?

Bug#873919: make dpkg-buildpackage default locale UTF-8

2017-09-01 Thread Guillem Jover
Control: forcemerge -1 843776 Hi! On Fri, 2017-09-01 at 10:23:59 +0200, Hans-Christoph Steiner wrote: > Package: dpkg-dev > > More and more packages are adding unicode files as unicode support has > become more reliable and available. The package building process is not > guaranteed to happen i

Bug#873919: make dpkg-buildpackage default locale UTF-8

2017-09-01 Thread Hans-Christoph Steiner
Package: dpkg-dev More and more packages are adding unicode files as unicode support has become more reliable and available. The package building process is not guaranteed to happen in a unicode locale since the Debian default locale is LC_ALL=C, which is ASCII not UTF-8. Reading UTF-8 filename