[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#910605: marked as done (libgs9-common: ships dangling symlink /usr/share/ghostscript/9.25/Resource/CIDFSubst/DroidSansFallback.ttf)

Your message dated Sun, 24 Nov 2024 16:36:54 -0600
with message-id <3849098.kQq0lBPeGt@riemann>
and subject line Re: ghostscript ships dangling symlink /usr/share/ghostscript/X.Y/Resource/CIDFSubst/DroidSansFallback.ttf
has caused the Debian Bug report #910605,
regarding libgs9-common: ships dangling symlink /usr/share/ghostscript/9.25/Resource/CIDFSubst/DroidSansFallback.ttf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
910605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910605
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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-

--- End Message ---
--- Begin Message --- 
On Sun, 25 Feb 2024 14:58:18 -0600 Steven Robbins <steve@sumost.ca> wrote:
> 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?

There were no responses.  So I guess the honest answer to your question

> > 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?

is that there is no specific reason.

However, there appears to be no adverse consequences, so I am closing this 
issue.

-Steve

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: