As confirmed by upstream author (Martin Hauner): On Sat, Aug 2, 2008 at 09:45, Martin Hauner wrote: > Sandro Tosi wrote: >> The bug is >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428978 and I'd >> like to know if you can suggest something to be done to fix it >> (for example a patch :D). > > Unfortunately this is a design flaw in subcommander 1.x. > >> You released 1.2.3 (and some beta for 2.0.0) so i might be that >> with the latest stable version, that problem is fixed: what would >> you suggest? If you say, "upgrade and I'll try to release a >> patch" or "upgrade, it's fixed" I'll do. > > The latest 1.2 releases do not fix the problem and I don't have > any plans to fix it in 1.2. > > I just have limited time to work on Subcommander and I'm > concentrating on 2.0.0 beta, which does not have this problem > anymore. > > So my recommendation would be to move to 2.0.0 beta. I think even > in its beta state it is a lot better than 1.2. Allthough it is not > called beta without reason ;)
So the solution for this bug is waiting for a stable 2.x release. Thanks, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
