[Debian-in-workers] Bug#717636: latex-sanskrit package
intrigeri
intrigeri at debian.org
Tue Nov 11 09:38:57 UTC 2014
Hi,
Vasudev Kamath wrote (13 Oct 2014 11:51:51 GMT) :
> On Mon, Oct 13, 2014 at 5:04 PM, intrigeri <intrigeri at debian.org> wrote:
>> On current sid, with texlive-lang-indic installed:
>>
>> $ t1disasm /usr/share/texlive/texmf-dist/fonts/type1/public/sanskrit/sktb10.pfb | grep start
>> dup 3 {systemdict /internaldict known not {pop 3} {1183615869 systemdict
>> /internaldict get exec dup /startlock known {/startlock get exec} {dup /strtlck
>> known {/strtlck get exec} {pop 3} ifelse} ifelse} ifelse} executeonly put
>>
>> ... seems to indicate that the bug is still present.
I could reproduce this today again in an up-to-date sid chroot. I see
that sktb10.pf is shipped by the texlive-lang-indic 2014.20141024-1
binary package.
> Below is mail snippet between me Jaldhar and Norbert, probably
> recorded in texlive mailing list.
Thanks.
> [...]
> We acked to drop binaries and only ship required source as part of
> texlive-lang-indic.
I don't get this part: the file that exposes this bug is still
installed by a binary package. Maybe there are plans to drop it, but
for the time being, it's there.
> So yes the bug still holds right but not sure if
> it should be reassigned to texlive-lang src or kept on latex-sanskrit.
Well, the bug should be assigned to the binary package that ships the
buggy file, that is texlive-lang-indic. What exactly is making you
doubt that it should be the case?
(/me suspects there's still some misunderstanding going on..)
Cheers,
--
intrigeri
More information about the Debian-in-workers
mailing list