Your message dated Sat, 29 Oct 2011 14:18:54 +0100
with message-id <[email protected]>
and subject line Re: [Svn-bp-devel] Bug#646945: svn-buildpackage: 'Illegal
instruction' when executing
has caused the Debian Bug report #646945,
regarding svn-buildpackage: 'Illegal instruction' when executing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
646945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646945
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: svn-buildpackage
Version: 0.8.3
Severity: important
svn-buildpackage doesn't execute at all failing with the message
Illegal instruction
-- System Information:
Debian Release: 6.0.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages svn-buildpackage depends on:
ii devscripts 2.10.69+squeeze1 scripts to make the life of a Debi
ii file 5.04-5 Determines file type using "magic"
ii libcapture-tiny-perl 0.08-1 module to capture STDOUT and STDER
ii libfile-libmagic-perl 0.96-1 Perl interface to libmagic for det
ii liblocale-gettext-perl 1.05-6 Using libc functions for internati
ii libsvn-perl 1.6.12dfsg-6 Perl bindings for Subversion
ii liburi-perl 1.54-2 module to manipulate and access UR
ii perl 5.10.1-17squeeze2 Larry Wall's Practical
Extraction
ii subversion 1.6.12dfsg-6 Advanced version control system
ii unp 2.0~pre4 unpack (almost) everything with on
ii wget 1.12-2.1 retrieves files from the web
Versions of packages svn-buildpackage recommends:
ii debhelper 8.0.0 helper programs for debian/rules
svn-buildpackage suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
notfound 646945 0.8.3
quit
On Sat, 29 Oct 2011 15:24:41 +0300
anatoly techtonik <[email protected]> wrote:
> > 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.
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.
> > 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/
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.
> > 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?)
> > 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.
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.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
pgpYFQ1Q53RkD.pgp
Description: PGP signature
--- End Message ---
