[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-09-30 Thread Launchpad Bug Tracker
This bug was fixed in the package xdeb - 0.6.5 --- xdeb (0.6.5) unstable; urgency=low [ Steve Langasek ] * If a package is Multi-Arch: foreign, we don't need to build it unless we also want to install it in its own right. * When calling apt-cache show, qualify the package n

[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-09-30 Thread Launchpad Bug Tracker
** Branch linked: lp:debian/xdeb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/731079 Title: xdeb fails if dpkg-cross has nothing to do To manage notifications about this bug go to: https://bugs.la

[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-09-16 Thread Colin Watson
** Changed in: xdeb (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/731079 Title: xdeb fails if dpkg-cross has nothing to do To manage notifications

[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-07-29 Thread Launchpad Bug Tracker
** Changed in: xdeb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/731079 Title: xdeb fails if dpkg-cross has nothing to do To manage notifications about thi

Re: [Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-04-18 Thread Steve Langasek
On Mon, Apr 18, 2011 at 03:48:06PM -, Wookey wrote: > So the real problem here is that xdeb thought libidn11-java was a > crossable package, downloaded it and tried to cross it. The question is > should we fix this by telling xdeb that it's not meaningfully crossable, > or by having it automati

[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-04-18 Thread Wookey
No that scratch directory was deliberately blanked. Not sure what was going on there. I've reproduced the problem now. Here is a rather simpler test-case: After downloading libidn11 packages wget -N http://ports.ubuntu.com/ubuntu-ports/pool/universe/libi/libidn/idn_1.18-1build1_armel.deb wget -N

[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-04-14 Thread Steve Langasek
** Changed in: xdeb (Ubuntu) Assignee: (unassigned) => Wookey (wookey) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/731079 Title: xdeb fails if dpkg-cross has nothing to do -- ubuntu-bugs ma

Re: [Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-03-10 Thread Steve Langasek
On Fri, Mar 11, 2011 at 12:18:29AM -, Wookey wrote: > #./xdeb.py -a armel -d xdeb-scratch -b xdeb-scratch --only-explicit > --prefer-apt qemu-linaro > Building source package cache ... > Using file archive.ubuntu.com_ubuntu_dists_natty_main_source_Sources for apt > cache > Using file archive.

[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-03-10 Thread Wookey
I tried to reproduce this with the just-merged xdeb-graph branch and get the log below. Which fails differently to the above. It seems to be entirely failing to install any host-arch packages, so falls over as soon as configure looks for one (zlib). I'll look in to that. #./xdeb.py -a armel -d xd

[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-03-10 Thread Steve Langasek
Example: $ ./xdeb/xdeb.py -a armel -d xdeb-scratch -b xdeb-scratch --only-explicit --prefer-apt qemu-linaro [...] dpkg-cross -a armel -b -X heimdal-dev -X krb5-multidev -X ssh-krb5 libkrb5-dev_1.8.3+dfsg-4ubuntu1_armel.deb libkrb5-3_1.8.3+dfsg-4ubuntu1_armel.deb libgssapi-krb5-2_1.8.3+dfsg-4u

[Bug 731079] Re: xdeb fails if dpkg-cross has nothing to do

2011-03-07 Thread Steve Langasek
>From what I'm seeing, this also causes more problems than just requiring xdeb to be restarted. Especially when using --only-explicit, the import failure means that, since the package has already been downloaded and the .changes file generated, the package is treated as "built" which stops any fur