documentation-packages team mailing list archive
Mailing list archive
[Bug 1701047] Re: Renaming of conf file fails
This bug was fixed in the package fonts-orya-extra - 2.0-5ubuntu0.1
fonts-orya-extra (2.0-5ubuntu0.1) bionic-proposed; urgency=medium
* Handle migration of conffile from wrong subdir (LP: #1701047).
-- Gunnar Hjalmarsson <gunnarhj@xxxxxxxxxx> Sat, 09 Jun 2018 23:53:00
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to fonts-beng-extra in
Renaming of conf file fails
Status in fonts-beng-extra package in Ubuntu:
Status in fonts-deva-extra package in Ubuntu:
Status in fonts-gujr-extra package in Ubuntu:
Status in fonts-guru-extra package in Ubuntu:
Status in fonts-orya-extra package in Ubuntu:
Status in fonts-beng-extra source package in Bionic:
Status in fonts-deva-extra source package in Bionic:
Status in fonts-gujr-extra source package in Bionic:
Status in fonts-guru-extra source package in Bionic:
Status in fonts-orya-extra source package in Bionic:
Status in fonts-beng-extra package in Debian:
Status in fonts-deva-extra package in Debian:
Status in fonts-gujr-extra package in Debian:
Status in fonts-guru-extra package in Debian:
Status in fonts-orya-extra package in Debian:
The fix of <https://bugs.debian.org/853848> wasn't accomplished properly. Renamings of conf files weren't addressed in maintainer scripts, upgrades from previous versions fail in this respect, and the package system generates warning messages.
The problem has been reported in Debian, and the purpose of this bug
report is to keep track of the progress.
This config file is broken in xenial and will still be broken on upgrade to bionic, which means the fonts in question will not be available to the system as intended if the user has upgraded.
For each of
* Purge the package if installed and clean up possible leftovers
due to the issue.
* Install the Xenial version of the package and find that the symlink
in /etc/fonts/conf.d incorrectly points to a directory.
* Install the version in bionic-release and find that the attempt
to fix the issue fails
* Install the version in bionic-proposed and find that it fixes the
issue and that the symlink now correctly points to the conf file.
Because this modifies maintainer scripts there is possibility of introducing a regression that will cause the package to fail to unpack.
To manage notifications about this bug go to: