[Bug 1916935] Re: Major changes in sorting method of glibc on Ubuntu 18.04 after upgrading to Ubuntu 18.04.5

[Christian Ehrhardt ]

FYI - This happens only to a login shell

$ ssh ubuntu at 192.168.122.177 "env | grep LC_NUM";
LC_NUMERIC=de_DE.UTF-8
ssh ubuntu at 192.168.122.177 -t 'bash -l -c "env | grep LC_NUM"'
LC_NUMERIC=C.UTF-8


And while downgrading I saw the suspicious
/etc/profile.d/01-locale-fix.sh: line 2: /usr/bin/locale-check: No such file or directory

$ cat /etc/profile.d/01-locale-fix.sh
# Make sure the locale variables are set to valid values.
eval $(/usr/bin/locale-check C.UTF-8)

And indeed on "release" Bionic that binary used there isn't present.

I checked where it came from:
$ dpkg -S /usr/bin/locale-check
base-files: /usr/bin/locale-check


So it seems this check was always meant to work, but on bionic-release
calls a file that isn't present and therefore is not in effect to
"fixup" the locales on a login shell.


Now that I know that I was able to swicth between old/new behavior by switching "just" base files 10.1ubuntu2 <-> 10.1ubuntu2.10.

That change was introduced back in 2018 via bug 1134036 as far as I
found.

I'm not sure what to do, this is "longer in the field with the new behavior" and not new at all.
So changing it either way might regress people.
But in any case we can re-target this bug against base-files for re-consideration now that we know all that.

** Also affects: base-files (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: postgresql-10 (Ubuntu)
       Status: Incomplete => Invalid

** No longer affects: postgresql-10 (Ubuntu Bionic)

** Changed in: glibc (Ubuntu)
       Status: New => Invalid

** No longer affects: glibc (Ubuntu Bionic)

** Summary changed:

- Major changes in sorting method of glibc on Ubuntu 18.04 after upgrading to Ubuntu 18.04.5
+ Major changes in sorting method upgrade 18.04->18.04.5 due to base-files change

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1916935

Title:
  Major changes in sorting method upgrade 18.04->18.04.5 due to base-
  files change

Status in base-files package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Invalid
Status in postgresql-10 package in Ubuntu:
  Invalid
Status in base-files source package in Bionic:
  New

Bug description:
  I had an Ubuntu 18.04.0 with Postgres 9.6.

  Before Ubuntu upgrade following command result was:

  [code]
  vodka at ubuntu140:~$  ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort
  1-1
  11
  [/code]

  But after upgrading Ubuntu 18.04 to latest release via apt upgrade
  (18.04.5) result of the command above totally changed:

  [code]
  vodka at ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort
  11
  1-1
  [/code]

  Due to this our production Postgres database started work very slowly
  and we had a long downtime for REINDEX. Sorting method is very
  important for Postgres database:
  https://wiki.postgresql.org/wiki/Locale_data_changes

  Please, read "Testing collation" part.

  Is it normal behavior for Ubuntu? Why glibc totally changed within LTS
  release without 'major upgrade'? I did not expect this...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libc-bin 2.27-3ubuntu1.4
  ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18
  Uname: Linux 4.15.0-136-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Thu Feb 25 13:13:03 2021
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1.4
   libgcc1 1:8.4.0-1ubuntu1~18.04
  InstallationDate: Installed on 2021-02-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1916935/+subscriptions