[Bug 2007124] Re: Move available config files from /etc to /usr

[Gunnar Hjalmarsson]

This was uploaded to lunar after a brief IRC conversation:

https://irclogs.ubuntu.com/2023/02/23/%23ubuntu-desktop.html#t14:18

** Changed in: fontconfig (Ubuntu)
       Status: New => Fix Committed

** Changed in: fontconfig (Ubuntu)
     Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Move available config files from /etc to /usr

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  At the upgrade to fontconfig 2.10 a decade ago, the directory for
  storing available config files was changed from /etc/fonts/conf.avail
  to /usr/share/fontconfig/conf.avail. It was done upstream as well as
  in Debian, but Ubuntu delayed the transition for some reason. I think
  we should do that transition in Ubuntu too. That will get Ubuntu in
  sync with the upstream documentation and the delta to Debian gets
  reduced a little.

  The changes needed are straightforward. I put a proposed upload in
  this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig

  and I would appreciate someone's eyes on it.

  So, what's the caveat? The only thing I can think of is that distros,
  system admins and individual users may have tweaked the font
  configuration by including symlinks which point to the moved files.
  While I don't have the impression that such symlinks are very frequent
  — custom conf files put directly in /etc/fonts/conf.d or equivalent
  places in $HOME seem to be more common — to the extent they exist,
  they will be silently disabled.

  Bug #2005124 revealed an example of a symlink which pointed to a file
  which will be moved if we do this. OTOH, in that case upstream added a
  symlink with the very same name, so we had to deal with that conflict.
  If the name of Kubuntu's link had been something else, we might not be
  aware of it yet.

  The changelog for this upload:

  https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1

  states that the transition will be done "later with another upload
  once the details are sorted". Are there other details which I have
  missed? If not, I suppose that the potential inconvenience is
  approximately as big today as it was 2012. And since next LTS release
  is more than one year ahead, this ought to be an appropriate time to
  make the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2007124/+subscriptions