after rebuilding thuban in a clean sid chroot (and confirming this with 
pbuilder) I can say that a simple binNMU fixes this bug.

As we are in a permanent BSP (where 0-day NMUs are allowed (*)) and this bug 
is open for more than a week, I plan to do a (sponsored) binNMU tomorrow.

If you're preparing a new upload within few _days_ anyway, please let me know, 
so I dont have to bother someone with sponsoring. (As there is no new 
upstream version, no activity in the BTS or the pkg-grass-devel list (in may) 
about thuban I somewhat doubt this - but of course I would be happy to be 
proven wrong :-)


*) http://lists.debian.org/debian-devel-announce/2006/05/msg00015.html
--- thuban-1.0.1/debian/changelog	2006-05-31 23:26:52.000000000 +0000
+++ thuban-1.0.1+b1/debian/changelog	2006-05-31 23:16:13.000000000 +0000
@@ -1,3 +1,11 @@
+thuban (1.0.1-1+b1) unstable; urgency=low
+  * Non-maintainer upload
+  * binNMU so that it gets compiled with the right version of wxPython
+    (closes: #368060)
+ -- Holger Levsen <[EMAIL PROTECTED]>  Wed, 31 May 2006 23:12:54 +0000
 thuban (1.0.1-1) unstable; urgency=high
   [ Francesco Paolo Lovergine ]

Attachment: pgpPSwQOo2UW0.pgp
Description: PGP signature

Pkg-grass-devel mailing list

Reply via email to