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

Seeking pre-approval for unifont update for Lenny



Right before the freeze, my sponsor uploaded an updated version of the
"unifont" package, unifont-1:5.1.20080706-1.  This update fixed a
"Severity: important" bug in the existing Debian version (incomplete
copyright/licensing information).

Current policy seems to indicate that a package can't even be included
without complete copyright & licensing information.

The uploaded package also closes every other bug for "unifont" except
one for including unifont-bin utilities including unitopbm (the
unitopbm author hasn't replied to my inquiry about licensing, so I
couldn't include his program and I'm leaving the bug open for now).
Also, for the first time for this package, there is a glyph for every
visible code point in the Unicode Basic Multilingual Plane (Plane 0,
the first 65,536 code points) -- it is a very major update to the old
Debian package that adds almost 20,000 previously missing glyphs.
Here are the bugs closed:

#455101: "Severity: important" bug - lack of full copyright/license info fixed

#178204: spacing - new TrueType version is spaced properly, including
combining characters such as accents (as well as being scalable)
#218720: contains most recent version of "unifont" glyphs
#356594: adopted "unifont" package, orphaned in 2006
#441357: incorporates Rich Felker's Tibetan glyphs

Unfortunately, an omission in the debian/control of "Conflicts" and
"Replaces" for one of the entries created a new bug of "Severity:
grave" (#493711) -- if the old "unifont" package is already installed,
an attempt to install "xfonts-unifont" would fail (the package names
differ, and they both use the same unifont.pcf.gz file).  I turned
"unifont" into "xfonts-unifont" (for the PCF version) and
"ttf-unifont" (for the TrueType version) upon the recommendation of
someone on these mailing lists.  That new bug is easy to fix but I
wanted to wait a few days now that the new "unifont" is in unstable
and see if anyone spots anything else.  This was my very first attempt
at Debian packaging, so it is possible that I overlooked something
else.

After doing that upload, in preparing for an upload to Ubuntu, I am
adding improvements made in the Ubuntu version of "unifont" that
weren't ported back to Debian (or anywhere else for that matter, since
there was no upstream for "unifont" for quite a while).  I hadn't been
running Ubuntu (just Sarge and then Etch) while working on unifont, so
I didn't know about the Ubuntu changes earlier.

I also cleaned up the final block of glyphs, in the U+FFxx range
(something I didn't have time to do while trying to upload before the
Lenny freeze).  I also made a few very minor changes to the src/
directory to make a couple of programs a little more resilient to
user-fed data.  A simple diff would show almost 1000 lines changed,
but they are almost all improvements to glyphs.  Changes to src/ are
minor.

Can I upload a new version of ".orig.tar.gz" with all of the changes
(including additions that others previously made for Ubuntu that had
never been brought into Debian) rather than just a "-2" that only
fixes the missing Conflicts/Replaces control file entry for inclusion
into testing?

Can I wait until Friday to give a few days for any other problems to
be spotted and corrected in the package uploaded before the freeze?


Paul Hardy
unifoundry@unifoundry.com


Reply to: