Bug#350506: marked as done (ITP: gbdfed -- Bitmap Font Editor)
Your message dated Sun, 16 Jul 2006 08:59:18 -0700
with message-id <E1G291a-0002hA-1T@spohr.debian.org>
and subject line Bug#350506: fixed in gbdfed 1.1-1
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: wnpp
severity: wishlist
* Package name : gbdfed
Version : 1.0
Upstream Author :
* URL :
* License : GPL
Description : X11 font editor
XmBDFEditor is a BDF font editor with the following features:
.
o Automatic correction of certain metrics when a font is loaded.
o Generation of XLFD font names for fonts without XLFD names.
o Update an XLFD font name from the font properties.
o Update the font properties from an XLFD font name.
o Font property editor.
o Font comment editor.
o Supports unencoded glyphs (ENCODING of -1).
o Display of glyph encodings in octal, decimal, or hex.
o Imports PK/GF fonts.
o Imports Linux console fonts (PSF, CP, and FNT).
o Imports Sun console fonts (vfont format).
o Imports fonts from the X server.
o Imports Windows FON/FNT fonts.
o Imports TrueType fonts and collections.
.
Homepage: http://crl.nmsu.edu/~mleisher/gbdfed.html
This package replaces xmbdfed with a switch from Motif to GTK+, xmbdfed
is no longer being maintained.
Hints on how to do the transition in the best way are solicited. Should
I provide a xmbdfed package from gbdfed that will just depend on gbdfed
for transition purposes? Do I need to request the removal of xmbdfed
before I upload this package?
Baruch
--- End Message ---
--- Begin Message ---
Source: gbdfed
Source-Version: 1.1-1
We believe that the bug you reported is fixed in the latest version of
gbdfed, which is due to be installed in the Debian FTP archive:
gbdfed_1.1-1.diff.gz
to pool/main/g/gbdfed/gbdfed_1.1-1.diff.gz
gbdfed_1.1-1.dsc
to pool/main/g/gbdfed/gbdfed_1.1-1.dsc
gbdfed_1.1-1_i386.deb
to pool/main/g/gbdfed/gbdfed_1.1-1_i386.deb
gbdfed_1.1.orig.tar.gz
to pool/main/g/gbdfed/gbdfed_1.1.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 350506@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Baruch Even <baruch@debian.org> (supplier of updated gbdfed package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 14 Jul 2006 17:37:18 +0100
Source: gbdfed
Binary: gbdfed
Architecture: source i386
Version: 1.1-1
Distribution: unstable
Urgency: low
Maintainer: Baruch Even <baruch@debian.org>
Changed-By: Baruch Even <baruch@debian.org>
Description:
gbdfed - X11 font editor
Closes: 350506
Changes:
gbdfed (1.1-1) unstable; urgency=low
.
* Initial release (Closes: #350506)
Files:
cf8015b734dc003a08fffac688bfa2d8 643 x11 optional gbdfed_1.1-1.dsc
54ba894dc9885b91a7651ca949ad01cf 286571 x11 optional gbdfed_1.1.orig.tar.gz
0d12e2b174b1077b1a8171aaf1664739 312590 x11 optional gbdfed_1.1-1.diff.gz
e3650820bd461d8aac8cbe6693657813 206536 x11 optional gbdfed_1.1-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEuDOhHCar6qtHRZgRAn2mAJ45cDz73QMfpzOS9k/i/cdVgg/2vACgs3/Z
ysVWfaoQbCWZiemaoCqXTq8=
=wWa9
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: