Re: Bug#965323: postinst script deletes custom locales

2020-07-31 Thread Harald Dunkel

On 7/29/20 12:35 PM, Aurelien Jarno wrote:

On 2020-07-27 08:26, Harald Dunkel wrote:


Since the postinst builds just a subset of all locales and since it even 
maintains
a list about it, I would suggest to erase and rebuild only these locales.


This is not so easy as the list evolve from version to version.



I don't get this. The custom locales are not included in your lists, so
how comes they are affected by these internal changes?

What would you suggest me to do to make sure the files I created using
the API provided by your package are not deleted again on the next
opportunity?



Bug#965323: postinst script deletes custom locales

2020-07-29 Thread Aurelien Jarno
On 2020-07-27 08:26, Harald Dunkel wrote:
> Can't be worse than not having the locale at all. Not to mention that there is
> an option --posix to assure compatibility to POSIX.1-2008, AFAICT.

This option doesn't change the output format which is glibc specific. It
only control the source format, which is defined by POSIX.

> If there are
> incompatible changes, then its my job to worry about recreating the custom 
> locales.

This is how *you* consider that. Most users that encounter broken
locales just report a bug.

> Since the postinst builds just a subset of all locales and since it even 
> maintains
> a list about it, I would suggest to erase and rebuild only these locales.

This is not so easy as the list evolve from version to version.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net



Bug#965323: postinst script deletes custom locales

2020-07-29 Thread Harald Dunkel

Can't be worse than not having the locale at all. Not to mention that there is
an option --posix to assure compatibility to POSIX.1-2008, AFAICT. If there are
incompatible changes, then its my job to worry about recreating the custom 
locales.

Since the postinst builds just a subset of all locales and since it even 
maintains
a list about it, I would suggest to erase and rebuild only these locales.

Thanx very much
Harri



Bug#965323: postinst script deletes custom locales

2020-07-19 Thread Aurelien Jarno
control: tag -1 + wontfix

On 2020-07-19 15:55, Harald Dunkel wrote:
> Package: locales
> Version: 2.28-10
> 
> To support MacOS terminal I have to define "UTF-8" using localedef (see 
> #952516).
> Problem is, custom locales are wiped out by the postinst script. Sample:
> 
> # locale -a
> C
> C.UTF-8
> POSIX
> # localedef -i C -f UTF-8 UTF-8
> # locale -a
> C
> C.UTF-8
> POSIX
> UTF-8
> UTF-8.utf8
> # apt reinstall locales
> :
> :
> # locale -a
> C
> C.UTF-8
> POSIX
> 
> See UTF-8 is gone? Shouldn't happen.

Yes, that's normal. locales might not be compatible with the new glibc
version, so all of them are removed and regenerated on upgrade.
Otherwise you might end up with broken locales causing issues.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net



Processed: Re: Bug#965323: postinst script deletes custom locales

2020-07-19 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 + wontfix
Bug #965323 [locales] postinst script deletes custom locales
Added tag(s) wontfix.

-- 
965323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#965323: postinst script deletes custom locales

2020-07-19 Thread Harald Dunkel
Package: locales
Version: 2.28-10

To support MacOS terminal I have to define "UTF-8" using localedef (see 
#952516).
Problem is, custom locales are wiped out by the postinst script. Sample:

# locale -a
C
C.UTF-8
POSIX
# localedef -i C -f UTF-8 UTF-8
# locale -a
C
C.UTF-8
POSIX
UTF-8
UTF-8.utf8
# apt reinstall locales
:
:
# locale -a
C
C.UTF-8
POSIX

See UTF-8 is gone? Shouldn't happen.

Same for locales 2.31-1.


Harri