+++ Julian Andres Klode [2014-01-30 15:42 +0100]: > On Thu, Jan 30, 2014 at 12:27:21PM +0000, Wookey wrote: > > +++ Julian Andres Klode [2014-01-30 08:12 +0100]: > > > On Thu, Jan 30, 2014 at 03:13:16AM +0000, Wookey wrote: > > > > Package: apt > > > > Version: 0.9.15 > > > > Severity: important > > > > > > > > In the sources I have my own bootstrap repository containing a lot of > > > > (unstable) packages built for arm64, and plain debian unstable and > > > > saucy repos > > > > > > > > apt-get install <arch-all-package> (that is available in all 3 repos) > > > > results in a size mismatch error. It seems that apt is using the > > > > checksum from one repo but downloading the package from another. > > > > > > > > The packages used is just an example it seems to be the same for any > > > > arch all package > > > > > > > > (debian-arm64)# apt-cache policy x11proto-scrnsaver-dev > > > > x11proto-scrnsaver-dev: > > > > Installed: (none) > > > > Candidate: 1.2.2-1 > > > > Version table: > > > > 1.2.2-1 0 > > > > 500 http://people.debian.org/~wookey/bootstrap/debianrepo2/ > > > > debianstrap/main arm64 Packages > > > > 500 http://ftp.uk.debian.org/debian/ unstable/main amd64 > > > > Packages > > > > 500 http://ports.ubuntu.com/ubuntu-ports/ saucy/main arm64 > > > > Packages > > > > > > > > > > Right, and that's a problem, as having two different packages with the > > > same version is not really supported.
> > OK. That makes sense. I see what's going on now. > > > > The problem is that in order to debootstrap you need all the packages in > > one repo so leaving the arch all packages in ftp.uk.debian.org means you > > can't debootstrap if you only uploaded the new-arch 'any' packages to > > the 'bootstrap' repo. It's also important to test that the arch-all > > build actually works, and not just the arch-any part so doing those > > builds and testing the results can be good. > > A work around might be to reorder sources.list entries. The order of > those entries determines from which source a package is retrieved, I > believe the first match takes precedence. Ha. That does indeed provide a working workaround :-) Moving the repo that the 'all' packages are being download from, to the top of the list makes it work. so moving ftp.uk.debian.org above p.d.o/~wookey/bootstrap # apt-cache policy x11proto-scrnsaver-dev x11proto-scrnsaver-dev: Installed: 1.2.2-1 Candidate: 1.2.2-1 Version table: *** 1.2.2-1 0 550 http://ftp.uk.debian.org/debian/ unstable/main amd64 Packages 1001 http://people.debian.org/~wookey/bootstrap/debianrepo2/ debianstrap/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports/ saucy/main arm64 Packages 100 /var/lib/dpkg/status means that both downloads and checksums come from ftp.uk.debian.org I'll use it like this for a bit and see if it always works, or just sometimes :-) This isn't really any sort of actual 'solution', but it's a very handy suggestion. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org