Your message dated Sun, 20 May 2007 11:24:17 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#425201: duplicate of the msttcorefonts package?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ttf-root-installer
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Doesn't this package install the same fonts as the msttcorefonts
package? A quick reading of the postinst shows that it puts the fonts in
a different directory than msttcorefonts, but maybe symlinks would
suffice?
- -- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (130, 'unstable'), (120, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.18-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGT9mf+z+IwlXqWf4RAuLCAJ9YNtnA6+2ojW+r7iosMmgr325mdwCgkCcE
mjuIh8k6H9QRC+B6UAocX5Y=
=1zs8
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi Anthony,
On Sun, 2007-05-20 at 01:16 -0400, Anthony DeRobertis wrote:
> Package: ttf-root-installer
> Severity: normal
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Doesn't this package install the same fonts as the msttcorefonts
> package?
Not quite. The fonts distributed from the ROOT FTP server are not the
same version as the ones distributed with msttcorefonts. What's more
important is, that ROOT will not work with the fonts from msttcorefonts
(some change in layout or something).
Font handling in ROOT has long been an issue. ROOT is rather poor at
handling different kinds of fonts installed on the system. It would be
good if ROOT would use some sort of `standard' way of getting the
available fonts, but currently, font names, file names, and font tables
are hard coded into the source. I've suggest to upstream on many
occasions to fix this, but the problem is, that upstream supports very
old Linux installations, as well as other Un*x installations that does
not have the same high level of font support as GNU/Linux does.
> A quick reading of the postinst shows that it puts the fonts in
> a different directory than msttcorefonts, but maybe symlinks would
> suffice?
Unfortunately not. I investigated this option with Kevin McCarty some
time ago, but, for the above mentioned reason (incompatible fonts) it is
not possible.
Hence, I'm closing this bug.
> - -- System Information:
> Debian Release: lenny/sid
> APT prefers testing
> APT policy: (500, 'testing'), (130, 'unstable'), (120, 'experimental')
> Architecture: amd64 (x86_64)
If you're building ROOT on amd64, and you get it done, could you post
the resulting packages somewhere public? I'll then grab them an put
them on the unofficial repository at
deb http://mirror.phys.bnl.gov/debian-root unstable main contrib
Thanks.
Yours,
--
___ | Christian Holm Christensen
|_| | -------------------------------------------------------------
| | Address: Sankt Hansgade 23, 1. th. Phone: (+45) 35 35 96 91
_| DK-2200 Copenhagen N Cell: (+45) 24 61 85 91
_| Denmark Office: (+45) 353 25 404
____| Email: [EMAIL PROTECTED] Web: www.nbi.dk/~cholm
| |
signature.asc
Description: This is a digitally signed message part
--- End Message ---
