Adam D. Barratt wrote: > [Apologies for the delay in getting back to you on this] > > On Sat, 2011-09-17 at 14:50 -0400, Michael Gilbert wrote: > > I've decided that it's too risky to disable t1lib in lenny as the > > version of freetype there has some known issues. > > What's the feasibility of fixing the issues in freetype?
So, they're (in my opinion minor) font rendering issues, but I imagine there will be many complaints if those do get broken in any way. That being the fact, those changes are rolled up into various upstream commits that I haven't really sat down to figure out, and backporting them to lenny seems a rather tedious for little gain. > > Attached is a new debdiff for this proposed-update. > > - dh_installchangelogs -pxpdf-common CHANGES > + dh_installchangelogs -pxpdf-common CHANGES debian/NEWS.Debian > > If the file's named "debian/NEWS", dh_installchangelogs should just > dtrt. If I recall, it didn't seem to do the right thing, which is why I added that, but I'll recheck. > In any case, I'm not entirely convinced that a NEWS file is the > right location to be making a statement that seems in danger of > approaching "this package isn't getting security support in lenny". So, an EOL could be declared on t1lib, but there are many dependencies on it. So, I saw the news file as more of a tool to educate the user on what to do to disable t1lib if they actually see these issues as concerns. Another possibility would be to set t1lib=no in the default xpdfrc (which disables it) with instructions in NEWS.Debian on how to reenable it. Best wishes, Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
