On Sat, Aug 01, 2020 at 07:16:23PM +1000, Zenaan Harkness wrote: > On Sat, Aug 01, 2020 at 10:41:26AM +0200, Sven Joachim wrote: > > On 2020-08-01 17:35 +1000, Zenaan Harkness wrote: > > > > > So I have a local sid+testing mirror I've been using for years, and just > > > updated it: > > > > > > nice /usr/bin/debmirror --nocleanup --verbose --progress > > > --allow-dist-rename --arch=amd64 > > > --section=main,main/debian-installer,contrib,non-free > > > --dist=sid,testing --host=ftp.iinet.net.au --method=http > > > --root=pub/debian --diff=none --rsync-extra=trace,doc,tools > > > --exclude-deb-section=debug --exclude='/Translation-.*\.bz2$' > > > --include='/Translation-en.*\.bz2$' > > > /Library/Lpools/zen/p1-setups_misc/repos/debian/d00-sid+tst+src-64 > > > > > > > > > The only "recent" change is adding i386 arch a couple weeks back. > > > > Seems you should use "--arch=amd64,i386" rather than "--arch=amd64" > > then. > > Why does the fact that my local mirror only having one of my 2 enabled > mirrors, cause apt update to stop working? > > Would this require full i386 binary local mirror? I'm using debmirror, and > the --exclude-deb-section=... seems like it effects all arch's for this > mirror. I only added i386 to get Android studio to work... >
Take 2: Why does the fact my local mirror only has one of my 2 enabled architectures, cause apt upgrade to stop working altogether? Does fixing this mean I requile a local mirror of both my architectures?