reopen 506688 severity 506688 serious fixed 506688 1.04.93-1 fixed 506688 1.04.92.dfsg-4 fixed 506688 1.04.92.dfsg-3 fixed 506688 1.04.92.dfsg-2 fixed 506688 1.04.92.dfsg-1 found 506688 1.04.92-1 thanks <h01ger> hmm. ttf-liberation 1.04.92-1 is seriously buggy (missing source, doh) and in lenny, sid has 1.04.92.dfsg-4 since 11 days. but i only asked for an unblock of -1 so far (-4 should go to lenny). now i would like to upload 1.04.93 (only fixing one letter, the greek m) today, but i wonder if it would be better to get 1.04.92-4 into lenny first. what do you think? <h01ger> any comment on ttf-liberation? (12:03) - do you want that unblock request via mail? (for 1.04.92-4 (the version in sid atm, that is) <dato> wow, big packaging change <dato> h01ger: I'll unblock -4, and you can upload .93 once it has migrated, ok? <h01ger> dato, cool, thanks! <dato> hm <h01ger> hm cause big packaging change? <dato> hm I assumed #506688 would be RC. <dato> but then <h01ger> dato, well, it is rc <h01ger> there is no source <dato> yeah, though I assume there are tons of fonts in the archive whose .tar.gz contains the ttf files directly? <dato> (not that I'm saying -liberation should not ship the source in the source package, I'm not saying that) <h01ger> i'm not so sure (that there are tons of equally broken fonts packages), and even if :) <dato> well <h01ger> anyway, reopen 506688, severity 506688 serious just for the sake of it sounds unneeded to me, but i can do <dato> I'm just concerned that switching to build the ttf at build time can introduce regressions, and we're very late in the release cycle <dato> (that was the "big packaging change") <h01ger> i know. * h01ger just uploaded 1.04.93-1 to unstable <h01ger> following: if 1.04.92-4 is suitable, then is 1.04.93-1 as well. 1.04.93-1 (and 1.04.92.dfsg-?) is a bit packaging change indeed, but I think its the approriate thing to do. (Ship the source!) Besides that it also fixes some glyphs which were reported as errors and which should be fixed as an ugly font is not really usable neither. So far, bugs in ttf-liberation have always been spotted fast and so far, noone has reported any bugs related to the packaging change which happened in unstable 2.5 weeks ago. regards, Holger
Attachment:
pgpCCeVX_TQur.pgp
Description: PGP signature