Bug#319951: Not sure that #319951 is still here
tags 319951 - unreproducible found 319951 0.4-1 thanks Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): Actually, I'm morei interested in unstable as there's nothing we can do to fix such bugs in stable. Yes, but you still need to find out whether the lack of a warning is because (1) the font system has been upgraded to support spaces in font names (2) somebody has silently taken the space out of the hints file in the unstable version of your fonts packages (3) some change in defoma means that the warning has gone away but the system still doesn't support spaces in names (which would mean that in future it might all break again, perhaps worse than before). The action you need to take to resolve this bug report differs in each case. I'm actually lost here, honestly. Maybe help from other font people would be good. As a more general point, if users find that bug reports are always met with an attitude that they will be ignored if they aren't reproducible in unstable they may drift away to other distributions :-( Sorry if this has been your feeling. That wasn't the intent. My main point is that if something is broken in stable versions of either the font or defoma, there is a very little chance that we can fix it. I'm sure you know about this. signature.asc Description: Digital signature
Bug#319951: Not sure that #319951 is still here
Christian Perrier wrote: Could you please purge/install the package again [As before, this is running stable on an Alpha. I get the same message on a stable ix86 box as well, though.] Actually, I'm morei interested in unstable as there's nothing we can do to fix such bugs in stable. Yes, but you still need to find out whether the lack of a warning is because (1) the font system has been upgraded to support spaces in font names (2) somebody has silently taken the space out of the hints file in the unstable version of your fonts packages (3) some change in defoma means that the warning has gone away but the system still doesn't support spaces in names (which would mean that in future it might all break again, perhaps worse than before). The action you need to take to resolve this bug report differs in each case. As a more general point, if users find that bug reports are always met with an attitude that they will be ignored if they aren't reproducible in unstable they may drift away to other distributions :-( -- PMM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319951: Not sure that #319951 is still here
Could you please purge/install the package again [As before, this is running stable on an Alpha. I get the same message on a stable ix86 box as well, though.] Actually, I'm morei interested in unstable as there's nothing we can do to fix such bugs in stable. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319951: Not sure that #319951 is still here
tags 319951 unreproducible thanks Hello, I've just taken ttf-farsiweb over and while cleaning out the bug log, I went on this one. Actually, installing ttf-farsiweb results in : Dépaquetage de ttf-farsiweb (à partir de .../ttf-farsiweb_0.4-3_all.deb) ... Paramétrage de ttf-farsiweb (0.4-3) ... Use of uninitialized value in print at /var/lib/defoma/scripts/gs.defoma line 108. .../... (a lot of these) but that's alland it seems harmless. I'm not sure that this is what you reported. I'm even inclined to think that these problems are more problems in defoma than problems in the package itself. Indeed the same messages show up when I purge/install *other* font packages such as ttf-arabeyes. Could you please purge/install the package again and see whether the problems -- signature.asc Description: Digital signature
Bug#319951: Not sure that #319951 is still here
Christian Perrier wrote:
I've just taken ttf-farsiweb over and while cleaning out the bug log,
I went on this one.
Actually, installing ttf-farsiweb results in:
[Use of uninitialized value in print]
but that's alland it seems harmless.
I'm not sure that this is what you reported. I'm even inclined to
think that these problems are more problems in defoma than problems
in the package itself. Indeed the same messages show up when I
purge/install *other* font packages such as ttf-arabeyes.
See bug 267433 (same bug in ttf-arabeyes) and bug 318854 (same bug in
ttf-{bengali,devanagari,gujarati,punjabi,tamil}-fonts)...
The other font packages have taken the approach of removing the spaces
from the font names in the .hints file. I think you should either do
the same or find some definite defoma documentation that says it's OK
to have spaces (in which case it is a defoma bug because it doesn't
work, perhaps a bug that has been fixed in unstable?) See also bug
134593 (wishlist against defoma suggesting that it support spaces).
I think the 'uninitialized value' stuff is probably bug 325598 in
defoma, and not related.
Could you please purge/install the package again
[As before, this is running stable on an Alpha. I get the same message on
a stable ix86 box as well, though.]
golanth:/home/pm215# dpkg --purge ttf-farsiweb
(Reading database ... 52680 files and directories currently installed.)
Removing ttf-farsiweb ...
Regenerating /etc/vfontcap... done
Purging configuration files for ttf-farsiweb ...
dpkg - warning: while removing ttf-farsiweb, directory
`/usr/share/fonts/truetype/ttf-farsiweb' not empty so not removed.
golanth:/home/pm215# apt-get install ttf-farsiweb
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
ttf-farsiweb
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/136kB of archives.
After unpacking 356kB of additional disk space will be used.
Selecting previously deselected package ttf-farsiweb.
(Reading database ... 52670 files and directories currently installed.)
Unpacking ttf-farsiweb (from .../ttf-farsiweb_0.4-1_all.deb) ...
Setting up ttf-farsiweb (0.4-1) ...
Debian::Defoma::Id::defoma_id_register at line 60 in
/var/lib/defoma/scripts/vflib2.defoma: (Nazli Bold,
/usr/share/fonts/truetype/ttf-farsiweb/nazlib.ttf, 20): Illegal argument.
Regenerating /etc/vfontcap... done
golanth:/home/pm215#
-- PMM
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
