https://bugzilla.redhat.com/show_bug.cgi?id=1806272
--- Comment #17 from Hans de Goede <hdegoede(a)redhat.com> ---
(In reply to Nicolas Mailhot from comment #12)
Those are just symlinks. No different from a so bump. You don’t write
change
pages for so bumps.
so-bumps are automatically picked up by dependent packages with just a rebuild,
that is not the case here. Also in case of so-bumps the person doing the
so-bump typically also does the rebuilds of dependent packages.
I seem to be spending most of my working hours lately on fixing breakage caused
by others and I'm totally fed up with having to keep fixing things which other
people broke!
My vision here is really clear: you broke it, you fix it!
I've proposed 3 different ways how *you* can fix the things which *you* broke:
1. Check which packages are affected and file bugs against them, IOW do the
minimum amount of coordination so that other people at least know that there is
breakage which needs to be fixed
2. Provide compat symlinks with the old file-paths to the files
3. Revert the part of the changes where the directory in which the font files
are stored changes. I'm fine with all the other changes, the one causing the
problem is that the directory in which the files are stored has changed.
And I'll add a 4th option:
4. By far most packages which Require dejavu-*-fonts seem to Require the
dejavu-sans-fonts package, so how about adding an /usr/share/fonts/dejavu
symlink to /usr/share/fonts/dejavu-sans-fonts, this will fix the issues for
apps relying on the file-path to the fonts in most cases. This reduces the list
of apps which needs to be checked and potentially fixed because they rely on
the serif or mono version to 24 pkgs, which is a lot better then 59.
So let me repeat myself: you broke it, you fix it, so please select one of the
options from above (I suggest combining 1 + 4) and let me know how you plan to
proceed with fixing this.
--
You are receiving this mail because:
You are on the CC list for the bug.