On Sat, Oct 29, 2011 at 2:35 PM, Neil Williams <codeh...@debian.org> wrote: > On Sat, 29 Oct 2011 13:46:48 +0300 > anatoly techtonik <techto...@gmail.com> wrote: > >> On Sat, Oct 29, 2011 at 1:36 PM, Neil Williams <codeh...@debian.org> wrote: >> > tag 646945 + unreproducible >> > quit > > i.e. you're going to have to do all the tests yourself and it's likely > that unless you work out what is wrong, this bug will not be identified.
I understand that, but I am nor Perl expert, neither have time to become one, so unless somebody tells me what to do, chances that I can do anything on my own are minimal. If that `svn-buildpackage` was written in Python, I'd just run 'python -v -m pdb `which svn-buildpackage`' and could get you the source line with the error in no time. >> > Do you get problems with any other Perl scripts? >> >> None that I know of. Do you have any specific examples that I can run? > > dpkg-buildpackage > dpkg-parsechangelog Both work as expected. > Also try svn-inject and svn-upgrade. Both fail with the same 'Illegal instruction'. > Also try creating a Wheezy chroot and testing in that. Oh no. That's too hardcore. I don't want to pollute this VM more than necessary. >> > (apt-get --reinstall install svn-buildpackage) >> >> Done. Didn't help. This system is brand new VM box - there is no extra >> stuff installed, so it is not usual desktop or server box on steroids. >> Perhaps something is missing from svn-buildpackage dependencies? > > .. or a misconfiguration somewhere in the base system. I suspect that Bcfg2 could break some things, but you've seen the dependencies yourself. There is no hardcore hacking on this box, especially with Perl. > I've tested in a clean pbuilder chroot and svn-bp is fine with it's own > dependencies. Then, when I use `debcheckout svn-buildpackage` and > install it's build-dependencies, it builds itself fine without errors. As I said - I am not a Perl expert, but in Python world if Python code misbehaves so badly that it doesn't even execute - I am able to figure out what happens very quickly regardless of the platform (well, unless it is some web-service that requires os-specific methods to get to the entrypoint). >> > The first commands svn-buildpackage tries are calls to subversion >> > itself and that's probably the first place to check for something which >> > is compiled. >> >> What should I run to check? > > Anything and everything. I can't tell you which ones because this > problem only affects this one single machine. I also use svn-bp on > various virtual environments for buildd operations, again without any > errors. I certainly don't have time for that, and I am not running Debian anywhere else. > If it only persists on this one system, the chances of identifying the > actual problem approach zero. I see. I good reason to consider decoupling our application from Debian. Thanks for trying, though. ,) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
