[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#627488: No problem when using the businesscard.iso



On 26.05.2012 13:47, H.A.J. Koster wrote:
> Ran into the same problem with the debian-testing-amd64-netinst.iso. Specifically, the installer screen goes red when trying to install the busybox package, the log shows indeed that it cannot find the source image, while it is still mounted. I should add that I am installing in a VM from a downloaded .iso file -- tried both a Parallels VM and a VirtualBox VM, same problem in either one of them.


This is apparently an apt-cdrom issue, has nothing to do with busybox ;)

In /target, when I run `apt-get install busybox' (or anything else
for that matter), I see the following output (typed into email from
a virtual machine, so expect typos):

# apt-get install busybox
Reading archive lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
  busybox
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/397 kB of archives.
After this operation, 688 kB of additional disk space will be used.
Err cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot amd64 NETINST Binary-1 20120526-09:20]/ wheezy/main busybox amd64 1:1.19.3-7
  Please use apt-cdrom to make this CD-ROM recognized by APT.  apt-get update cannot be used to add new CD-ROMs
Failed to fetch cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot amd64 NETINST Binary-1 20120526-09:20]/pool/main/b/busybox/busybox_1.19.3-7_amd64.deb   Please use apt-cdrom to make this CD-ROM recognized by APT.  apt-get update cannot be used to add new CD-ROMs
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

The file in question (busybox_..deb) is present in /media/cdrom0/poll/main/b/busybox/
directory. So it appears to be apt-cdrom which is at fault, or cdrom: apt handler.

Thanks,

/mjt



Reply to: