Hi! On Mon, 2016-11-21 at 05:00:39 +0530, shirish शिरीष wrote: > On 21/11/2016, Guillem Jover <guil...@debian.org> wrote: > > On Mon, 2016-11-21 at 01:47:45 +0530, shirish शिरीष wrote: > >> The patch didn't work :( > > > > Well that it didn't work was actually also very useful! Because in > > your case it should not have worked due to having debug output > > enabled. If you retry it again w/o debugging enabled it should work, > > and the attached patch should make it impervious to debug settings.
> >> So it seems some issue is still there. I'll reboot and see if the > >> issue still persists. > > > > Yes and no. The original problem should be gone (the problem with the > > exit code, the new problem with the non-empty output string due to the > > debug output is new, but very welcome as it should make the code more > > robust. Thanks for that. Attached new patch. > Anyways, think it got through but for some reason dpkg died/failed it > says , see - I don't think this is related to this problem. The error report from whoever is reporting that is not very helpful though. :/ In any case, I've now implemented an actual set of validators instead of abusing the --compare-versions to do the validation. Which will have defined exit codes and not output stuff on debugging modes. At least I've added a --validate-pkgname and a --validate-version. I'll try to do a release tomorrow or so. Thanks, Guillem
