Hello, I've recently adopted ghostscript, so I can't answer the direct question of why libgsN-common ships a dangling symlink. I am curious what folks think of this. It's not clear to me whether there are bad consequences of a dangling symlink. For example is it treated differently than a completely missing file? The target of the link is shipped in package fonts-droid-fallback -- should the symlink be created there instead? Other options? Thanks, -Steve On Mon, 08 Oct 2018 17:59:12 +0200 Michael Prokop <mika@debian.org> wrote: > Package: libgs9-common > Version: 9.25~dfsg-2 > Severity: normal > > Hi, > > is there any specific reason why libgs9-common ships a symlink which > is a dangling one/dead end until the fonts-droid-fallback package is > installed? > > ,---- [ demo ] > | root@buster-demo:~# ls -la /usr/share/ghostscript/9.25/Resource/CIDFSubst/ > | total 8 > | drwxr-xr-x 2 root root 4096 Oct 8 17:21 . > | drwxr-xr-x 11 root root 4096 Oct 8 17:21 .. > | lrwxrwxrwx 1 root root 58 Sep 15 14:18 DroidSansFallback.ttf -> ../../../../fonts/truetype/droid/DroidSansFallbackFull.ttf > | root@buster-demo:~# ls -la /usr/share/ghostscript/9.25/Resource/CIDFSubst/ DroidSansFallback.ttf > | lrwxrwxrwx 1 root root 58 Sep 15 14:18 /usr/share/ghostscript/9.25/ Resource/CIDFSubst/DroidSansFallback.ttf -> ../../../../fonts/truetype/droid/ DroidSansFallbackFull.ttf > | root@buster-demo:~# readlink -f /usr/share/ghostscript/9.25/Resource/ CIDFSubst/DroidSansFallback.ttf > | root@buster-demo:~# > | > | root@buster-demo:~# apt-cache show libgs9-common | grep fonts-droid- fallback > | Recommends: fonts-droid-fallback > `---- > > JFTR, #613912 might be related. > > regards, > -mika- > >
Attachment:
signature.asc
Description: This is a digitally signed message part.