Re: Can't create an i386 ISO, but amd64 works fine
On 14 July 2011 20:14, Daniel Ellison <firstname.lastname@example.org> wrote:
> On 11-07-14 01:06 PM, Ben Armstrong wrote:
>>> Does that sound like the behaviour expected from archive issues?
>> More like a completely broken archive mirror (or broken apt caching
> I was using:
> --mirror-bootstrap http://ftp.ca.debian.org/debian/
> --parent-mirror-bootstrap http://ftp.ca.debian.org/debian/
> I just switched it to:
> --mirror-bootstrap http://ftp.us.debian.org/debian/
> --parent-mirror-bootstrap http://ftp.us.debian.org/debian/
> (removing binary, bootstrap, chroot, common and source from config/ for good
> measure) with the same result.
> fyi, this is my auto/config:
> lb config noauto \
> --distribution squeeze \
> --architectures i386 \
> --mirror-bootstrap http://ftp.us.debian.org/debian/ \
> --parent-mirror-bootstrap http://ftp.us.debian.org/debian/ \
> --volatile false \
> --bootstrap debootstrap \
> --binary-images iso-hybrid \
> --syslinux-theme 'syrinx-debussy' \
> --hostname debussy \
> --username live \
> --debian-installer live \
> --debian-installer-gui true \
> If I can't figure this out soon, I might skip the i386 build for now and
> concentrate on getting the source to a public repository, setting up a bug
> tracker, website, etc.
Note that this might be a dependency issue rather than mirror issue.
Singular pinning does not work well with apt, it insists on getting
all packages from the preferred release. If you pin cairo and it needs
some dependency from testing which is not pinned it will not be
installed (and you should get a message about "package xxx requires
yyy >= something but something_lower is going to be installed").
With aptitude this tends to work better. It tries random solutions
until it finds one that matches but tends to upgrade/downgrade
unrelated packages in the process or it might find a solution that
does not install anything.
Now i386 and amd64 are quite different architectures wrt dependencies.
i386 has "split libs" like libc6 + libc6-i686. If your pinning needs
upgrade to one of these split libs it would not be surprising that
the solution differs. Also some package builds may occasionally lag on
i386 due to split lib error which is not present on other archs.