Hi Tim, On Sat, Jan 26, 2013 at 04:31:52PM +0000, Tim Day wrote: > Severity: minor [...] > Hoping you've time to address this before a Wheezy release
Since we're already in deep freeze, it's very likely too late to fix such an issue for the upcoming stable release. See https://lists.debian.org/[email protected] and http://release.debian.org/wheezy/freeze_policy.html for what kind of bugs still can be fixed for Wheezy. I hope that you're not too disappointed. > I note the last couple of evolvotrons ie 0.6.1 on wheezy and 0.6.2 > currently on unstable are missing the intended content from the > built-in user manual (accessed from Help->User Manual), although > the 0.6.1 on Squeeze includes the expected text just fine. That's strange. Because the version in Squeeze and Wheezy are nearly identical (just one RC bug fix plus recompilation). I could reproduce this issue with the source version of Squeeze built for Sid i386 on 2012-04-07 15:46:33, i.e. with the i386 binary package available at http://snapshot.debian.org/package/evolvotron/0.6.1-1/#evolvotron_0.6.1-1:2b:b1 On the other hand the evolvotron package from Squeeze i386 and amd64 indeed does work as expected -- even on Sid (tested the i386 Squeeze package on Sid and the amd64 Squeeze on Squeeze via remote X tunneled through SSH). So I'm confused: a rebuild from the same source package can cause this issue? Could this be caused by e.g. a different python version (2.6 vs 2.7)? > This is likely the result of evolvotron's convoluted build process' > python script which processes the necessary content from the USAGE > file (with a failover to the "documentation not available" message > currently displayed, but upstream I've just admitted defeat and from > 0.6.3 (just released) Hrm, I neither can find 0.6.3 on http://freecode.com/projects/evolvotron nor on http://sourceforge.net/projects/evolvotron/. Where can I find the 0.6.3 tar ball? > the previously build-product problem files are now under source > control and included in the tarball. (This is the only change from > the 0.6.2 release). Ok, so this is rather an upstream build system issue and not caused by how Debian builds the packages (as I understood it initially)? Kind regards, Axel -- ,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
