reopen On Sat, Oct 29, 2011 at 4:35 PM, Debian Bug Tracking System <ow...@bugs.debian.org> wrote: > >> 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. > > I'm fairly sure it's not actually a bug in the source code of the Perl > scripts themselves, so that approach won't get far. I see no reason to > think this is a problem within svn-buildpackage itself, it is something > to do with your VM configuration.
That's not helpful. Perl executes ok. Other perl scripts also execute ok. So the problem in the way Perk executed this particular script. Maybe in the way Perl imports external modules. Think about it - you should know. Perhaps the problem is in some binary extension or svn bindings. I don't have experience with that. >> > 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. > > debootstrap wheezy dir/ > chroot dir/ I am running Squeeze, not Wheezy. Is it ok? > It's not hard. Something had to call that to create the VM in the > first place. It's how Debian Installer creates the installation. The machine was created with Xen. Will it create other dirs like pbuilder does somewhere in /var (or /usr)? I'd really like to keep this machine clean of any extra stuff. >> > 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. > > (yet you're expecting to use svn-buildpackage to build Debian packages > to use on presumably other Debian machines?) I need to a stable version 0.6 of Bitten (which is trac-bitten) that was not released yet in Debian. I can't build it on other machine, because latest Python policy (not new version of package) requires versions of packages like buildhelper that are absent on previous versions. >> > 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. ,) > > I think you are blaming the wrong package - just because one package > shows the error does not mean that the bug actually lies in that > package. I suspect a problem in the VM itself and it's the kind of > problem that will show up if you switch to using something else. i.e. > it is likely to be a persistent problem with that one VM. I was about to say that there are no problems with VM, because even `dmesg`... and then I checked dmesg and found this: [7288028.138482] svn-buildpackag[8557] trap invalid opcode ip:7fefad14a8b0 sp:7fffd51ad528 error:0 in ld-2.11.2.so[7fefad137000+1e000] [7288037.187741] svn-buildpackag[8560] trap invalid opcode ip:7fb20fff78b0 sp:7fff59f41e68 error:0 in ld-2.11.2.so[7fb20ffe4000+1e000] [7288040.851023] svn-buildpackag[8561] trap invalid opcode ip:7fb5271a68b0 sp:7fff9bd085e8 error:0 in ld-2.11.2.so[7fb527193000+1e000] [7288046.695367] svn-buildpackag[8562] trap invalid opcode ip:7fc71a79e8b0 sp:7fff0a766438 error:0 in ld-2.11.2.so[7fc71a78b000+1e000] [7288049.664150] svn-buildpackag[8563] trap invalid opcode ip:7f469df398b0 sp:7fffce8d6ad8 error:0 in ld-2.11.2.so[7f469df26000+1e000] [7288091.143575] svn-buildpackag[8573] trap invalid opcode ip:7fa6f27bb8b0 sp:7fffa4b7d068 error:0 in ld-2.11.2.so[7fa6f27a8000+1e000] [7288094.079603] svn-buildpackag[8574] trap invalid opcode ip:7f7841c128b0 sp:7fff321b5aa8 error:0 in ld-2.11.2.so[7f7841bff000+1e000] [7288096.356146] svn-buildpackag[8575] trap invalid opcode ip:7f8e473ba8b0 sp:7fff2ebe8098 error:0 in ld-2.11.2.so[7f8e473a7000+1e000] [7288129.539053] svn-buildpackag[8659] trap invalid opcode ip:7fef85d4a8b0 sp:7fff3715dbf8 error:0 in ld-2.11.2.so[7fef85d37000+1e000] [7288140.879078] svn-buildpackag[8660] trap invalid opcode ip:7feb04c668b0 sp:7fffea506928 error:0 in ld-2.11.2.so[7feb04c53000+1e000] [7288149.588406] svn-buildpackag[8661] trap invalid opcode ip:7fac1d7a48b0 sp:7fff69145048 error:0 in ld-2.11.2.so[7fac1d791000+1e000] [7288152.363837] svn-buildpackag[8662] trap invalid opcode ip:7fdb3595a8b0 sp:7fff52f4e4b8 error:0 in ld-2.11.2.so[7fdb35947000+1e000] [7288952.542530] svn-buildpackag[20366] trap invalid opcode ip:7f9befd4d8b0 sp:7fff3fc0deb8 error:0 in ld-2.11.2.so[7f9befd3a000+1e000] [7347887.781547] svn-buildpackag[27047] trap invalid opcode ip:7f51ed2d48b0 sp:7ffff8b4f768 error:0 in ld-2.11.2.so[7f51ed2c1000+1e000] [7347897.159074] svn-buildpackag[27048] trap invalid opcode ip:7f7252d4b8b0 sp:7ffffd8db788 error:0 in ld-2.11.2.so[7f7252d38000+1e000] [7349043.341234] perl[28518] trap invalid opcode ip:7fe39e8858b0 sp:7fffbdab65b8 error:0 in ld-2.11.2.so[7fe39e872000+1e000] [7349052.444836] perl[28521] trap invalid opcode ip:7f3309e358b0 sp:7fffdb81bea8 error:0 in ld-2.11.2.so[7f3309e22000+1e000] [7349068.116843] perl[28523] trap invalid opcode ip:7fa5e15248b0 sp:7fff7dac6118 error:0 in ld-2.11.2.so[7fa5e1511000+1e000] [7359703.042118] svn-buildpackag[8880] trap invalid opcode ip:7feb20cf08b0 sp:7fff9e8ca3d8 error:0 in ld-2.11.2.so[7feb20cdd000+1e000] [7365220.982547] svn-inject[16036] trap invalid opcode ip:7f3c0996c8b0 sp:7fff3c36d058 error:0 in ld-2.11.2.so[7f3c09959000+1e000] [7365238.791556] svn-upgrade[16039] trap invalid opcode ip:7f77327d48b0 sp:7fffec4767e8 error:0 in ld-2.11.2.so[7f77327c1000+1e000] > If you haven't got time to investigate a problem that only you can > produce, I see no point keeping this bug open because there is nothing > we can do to fix it without you doing the work. Closing. Don't get me wrong. I have time to investigate the problem, but I don't have time to learn the ways how to do this. What I expect from you is to guide me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
