Alex Becjert wrote in various emails: > Since we're already in deep freeze, it's very likely too late to > fix such an issue for the upcoming stable release.
Thought that might be the case; no worries, the app itself works fine and has been around long enough that one Debian "cycle" with missing internal docs won't hurt it. > Where can I find the 0.6.3 tar ball? Sorry forgot to tick the Sourceforge file metadata tickboxes for "default download". Fixed. > It's rather python vs no python. I suspect that for Squeeze, python > was indirectly in the build-dependencies while it wasn't for Wheezy. Makes sense. I know in my own dabbling in packaging using (now deprectated) yada I always declared python as a build dependency: https://sourceforge.net/p/evolvotron/code/688/tree/tags/release-0-6-2/mkdeb not sure whether Gurkan or whoever set up the official packaging ever spotted it though. > If there wouldn't have been such a fallback, that glitch would have > been noticed and fixed. But due to the fallback, the error went > through unnoticed. Interesting philosophical question there... it's the way it was because: - I used to be religiously opposed to having "build products" under version control. - Too many folks attempting to build from source were choking on the doc building stage, hence the fallback so at least they'd have more chance of getting a working but doc-free app. But these days I'm less bothered by the first point, and I'm more inclined to regard packagers as the primary customers for the project, especially as the number of folks requesting help building has massively dropped since the Debian world packages appeared. So yes it makes more sense to fail than build something which then gets bugs filed against it. Thanks this is useful insight (although the included in the tarball version controlled built docs now sidestep the issue). Thanks for looking into the policy side; it's not the end of the world if the docs are absent from a stable wheezy. Tim -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
