Bug#711456: Acknowledgement (apt: fails to do an update with "Internal Error, No file name for..." using amd64 and i386 dvd media)
David, thanks for your detailed response!
2013/6/9, David Kalnischkies <kalnischkies+debian@gmail.com>:
> On Fri, Jun 7, 2013 at 6:27 PM, Andrey Gursky <andrey.gursky@e-mail.ua>
> wrote:
>>> P.S. Do you know who is responsible for the cvs browsing feature?
>>
>> I've noticed, you've just silently migrated to git.
>
> We migrated from bzr to git just yet. Michael didn't throw a big party,
> but he announced it to the relevant peers (aka on deity@d.l.o).
> (That the browsing didn't work was a mistake, it should work now)
Yes, the fix of the browsing was, what I spoke about.
> The problem here though is less a debug problem as this can be recreated
> "easily" by having a multi-arch enabled system, an i386- and an amd64-only
> CD-ROM configured and an upgrade for a M-A:same library you have installed
> for i386 and amd64.
I'd like to add a tag: multiarch to the bug, OK?
> The problem is that if APT needs to upgrade a library it has to tell dpkg
> to unpack the i386.deb and the amd64.deb at the same time, so for that to
> work it needs access to both files which it doesn't have if you switch
> CD-ROMs (aka: you need a second drive, usb sticks might work, too).
>
>
> To make it work with one drive, APT would need to copy the amd64.deb
> package
> to disk, ask you to switch, and whola, it has both files. Only problem:
> You would be going to switch a lot as you basically have to switch for
> each library you have installed both architectures (and sometimes back).
>
> So, to prevent people from going insane over switching a thousand times
> APT would need to copy all those library files at once – or at least as
> many as possible without eating all harddrive space.
>
>
> The first should be easy, the second step a bit harder, but both will not
> be fixed by me as I never used APT with CD-ROMs (nor do I use CD-ROMs at
> all
> if I think about it now…). That needs someone with more CD-ROM experience
> to pick it up as this really needs someone who can actually test what
> she/he
> is doing. I am happy to help with pointers/answers/reviews/… on the other
> hand, hence tagged as 'gift' [0].
>
> [0] https://wiki.debian.org/qa.debian.org/GiftTag
I also don't use the drives, but mount images as loop device [1]. I'm
wondering why I didn't encountered this bug before. I assume not to
update i386 libs I installed once. If there are no problems with
installing M-A:same libs, what are good reasons to update them only by
simultaneously unpacking, which seems to be not needed during install?
Regards,
Andrey
[1] (BTW there is another issue with that, I've been wanting to report
that since a while now; will do it shortly)
Reply to: