Re: emsetup bug
On 2007-02-01 19:01 +0000, Neil Williams wrote:
> On Thu, 1 Feb 2007 03:07:29 +0000
> Wookey <firstname.lastname@example.org> wrote:
> > If you run emsetup on a fresh system it fails with:
> OK, that's simple to fix. emdebian-tools depends on apt-cross and if
> apt-cross has not been run, the cache files used by emsetup will not
> exist. I'll add a simple 'apt-cross -u' to the start of emsetup. I
> missed that bit.
Right. I did wonder if the requirement was really 'run apt-cross first'.
Just trying a naive "apt-cross -u" sets things up for unstable, but
emsetup still looks for -testing.
apt-cross -u -S testing
works (aprt from whinging about authentication). Is the idea of the
current script that it takes the targetted suite from the suite on the
host? Perhaps it makes no sense to try to guress a suite?
I'll try and find a mo next week to work out what is actually needed,
but I suspect you'll get to it first.
> apt-cross will do that, it also does a lot more, including setting up
> apt-conf.$suite and the relevant archives/partial and lists/partial
> directory trees and populate the cross-building architecture-specific
> cache, using the value entered via debconf. If that is 'None', emsetup
> will have to assume 'arm' and leave users to run apt-cross --update
> with the relevant --arch option.
I saw that in the docs. Assuming 'arm' seems to me to be the wrong
option (even though it is very convenient for me). Surely if no arch
has been specified then it should just insist on one being specified
somewhere, and halt.
Defaulting to any arch just seems wrong - it will bugger
things up for someone (not targetting arm), somewhere along the way.
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://wookware.org/
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.