On Feb 11, Steve McIntyre wrote:
> Marco: this is continuing fallout from *your* changes. If you wish to
> keep any shred of credibility, you might want to follow through here
> and test your proposed fix yourself. Jason has helpfully posted a test
> case that demonstrates the problem...
I do not
On Wed, Feb 10, 2016 at 12:39:20AM +0100, Marco d'Itri wrote:
>On Feb 10, Jason Heeris wrote:
>
>> I've just tried a live-build cross build of an armhf image from a stretch
>> amd64
>> VM, with debootstrap 1.0.78, and had it fail this way too.
>This is about #813232. I posted a candidate patch, bu
On Feb 10, Jason Heeris wrote:
> I've just tried a live-build cross build of an armhf image from a stretch
> amd64
> VM, with debootstrap 1.0.78, and had it fail this way too.
This is about #813232. I posted a candidate patch, but nobody cared.
Feel free to test it and report if it works.
--
ci
I've just tried a live-build cross build of an armhf image from a stretch
amd64
VM, with debootstrap 1.0.78, and had it fail this way too.
live-build: 1:20151215 (but reports as 5.0~a11-1)
debootstrap: 1.0.78
qemu: 1:2.5+dfsg-5
The command to reproduce the error is:
lb config \
--apt-indic
4 matches
Mail list logo