Bug#198730: apt-cdrom broken after upgrading from potato to woody
Filip Van Raemdonck wrote:
Do you have anything in /var/state/apt/?
I'll let you know after I get home and try it.
Well, I've checked, and there is no /var/state/ on my system. I also
searched the entire system for any trace of the index files, and they
were nowhere to be found.
No need to remove anything. Just rerun apt-cdrom add. Tell us what
happens.
What about those old potato CD's in the cdroms.list?
Will apt remove them in time, or can I safely just ignore them?
Those potato entries can be safely ignored. You may just as well remove
them, though.
OK this went quite well, I think. I did things in this order:
1) Removed those old potato lines from cdroms.list. Did 'apt-get update'.
Expected - no change (for better or worse).
Results - No change occurred - good!
2) Did 'apt-cdrom add' on the first binary CD.
Expected - (a) cdroms.list to be updated to the new format, (b) some
index files to be created in /var/lib/apt/lists, and (possibly) (c)
sources.list to be munged (as another user reported in bug 148073
<mailto:148073@bugs.debian.org>) (d) fewer errors in the 'apt-get update'
Results -
a) One change in cdroms.list, this line:
< CD::e9e80242113c277cd330d98d6262d5fa-2::Label "Debian GNU/Linux 3.0 r0
"Woody" - Official Source-7 (20020718)";
> CD::e9e80242113c277cd330d98d6262d5fa-2::Label "Debian GNU/Linux 3.0
r0 Woody - Official Source-7 (20020718)";
Notes: The quotes around "Woody" have disappeared. Also this line has
nothing to do with the first binary CD. Maybe this is the real format
change to cdroms.list?
b) Four (I think - forgot to write it down) index files created
in /var/lib/apt/lists - looking good!
c) No change at all to sources.list - very good!
d) No errors or warnings relating to the first binary CD - excellent!
3) Added the security updates line to sources.list, and did 'apt-cdrom
add' for the second binary CD, followed by 'apt-get update'.
Expected - (a) cdroms.list to be updated (b) more index files to be
created (c) fewer errors in the 'apt-get update'
Results -
a) No change to cdroms.list - curious (more thoughts to follow)!
b) Six index files created in /var/lib/apt/lists, including two from the
security line - good!
c) No errors or warnings relating to the first two binary CD's
OK, it seems to be fixing itself now, unfortunately I didn't have time
to read in the other 12 CD's last night, but I am expecting them to work
OK. But assuming they do, there is still one issure remaining: the
cdroms.list file.
Mine looks like this now:
<---------- start cdroms.list ------------>
CD::53d141faef013d9e0f0ebdb110a396ea-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official i386 Binary-1 (20020718)";
CD::5723fa1c8d4308a41fb028ba083cd659-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official i386 Binary-2 (20020718)";
CD::8b62869b27d28fa3346de0d1e03cf606-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official i386 Binary-3 (20020718)";
CD::3c0e3b871649869c8a5fdadf0c65800c-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official i386 Binary-4 (20020718)";
CD::ce960eda05cd296347026937df8df816-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official i386 Binary-5 (20020718)";
CD::99e53fc0f7f32fcc5334b7b7adcd4fa8-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official i386 Binary-6 (20020718)";
CD::09fc88a5ec1e450b12b26314fa107698-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official i386 Binary-7 (20020718)";
CD::7147b93e6d7e0d1ddf5de07ab0c4bb9a-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official Source-1 (20020718)";
CD::98030c9dccd61879babc382191b29df8-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official Source-2 (20020718)";
CD::4891bb6b2386ee304c9eb7b5872f71e1-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official Source-3 (20020718)";
CD::6f7fd63cb79ce8279e5a25ab681b3ac8-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official Source-4 (20020718)";
CD::463b780f174f7718603589a43b11a84a-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official Source-5 (20020718)";
CD::892c4e1cb90f3825ff370360c2d6abb1-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official Source-6 (20020718)";
CD::e9e80242113c277cd330d98d6262d5fa-2 "Debian GNU/Linux 3.0 r0 _Woody_
- Official Source-7 (20020718)";
CD::e9e80242113c277cd330d98d6262d5fa-2::Label "Debian GNU/Linux 3.0 r0
Woody - Official Source-7 (20020718)";
"CD::892c4e1cb90f3825ff370360c2d6abb1-2::Label";
"CD::463b780f174f7718603589a43b11a84a-2::Label";
"CD::6f7fd63cb79ce8279e5a25ab681b3ac8-2::Label";
"CD::4891bb6b2386ee304c9eb7b5872f71e1-2::Label";
"CD::98030c9dccd61879babc382191b29df8-2::Label";
"CD::7147b93e6d7e0d1ddf5de07ab0c4bb9a-2::Label";
"CD::09fc88a5ec1e450b12b26314fa107698-2::Label";
"CD::99e53fc0f7f32fcc5334b7b7adcd4fa8-2::Label";
"CD::ce960eda05cd296347026937df8df816-2::Label";
"CD::3c0e3b871649869c8a5fdadf0c65800c-2::Label";
"CD::8b62869b27d28fa3346de0d1e03cf606-2::Label";
"CD::5723fa1c8d4308a41fb028ba083cd659-2::Label";
"CD::53d141faef013d9e0f0ebdb110a396ea-2::Label";
<----------- end cdroms.list ------------->
Take a look about half way down, the first line containing the tag
::Label. In the new format, there is supposed to be one of these after
each CD in the list, (see the good cdroms.list earlier on in this
report). Also there is a bunch of 13 empty ::Label tags following it.
So this file appears to be broken, but does it matter, and what is it
used for? Can I expect further problems down the line because of it(I am
thinking of the upgrade to the next stable, in a year or so)? Can it be
fixed, and if so, how?
<==================== further thoughts =========================>
And now to the root of the problem itself. I checked through my upgrade
transcripts again last night, and found that the problem first showed up
in the 'apt-get install dpkg apt debconf' step. I saw 'Setting up apt
(0.5.4) ...', then 24 other packages were installed, ending with these
two lines:
Unpacking replacement xfree86-common ...
Replacing files in old package xserver-common ...
Then this happened:
Err cdrom://[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-2
(20020718)] unstable/main perl-5.005-base 6.3
Please use apt-cdrom to make this CD recognized by APT. apt-get update
cannot be used to add new CDs
Err cdrom://[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-2
(20020718)] unstable/main perl-5.005 6.3
Please use apt-cdrom to make this CD recognized by APT. apt-get update
cannot be used to add new CDs
Err cdrom://[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-1
(20020718)] unstable/main perl-base 5.6.1-7
Please use apt-cdrom to make this CD recognized by APT. apt-get update
cannot be used to add new CDs
(... deleted 10 similar lines )
Failed to fetch cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386
Binary-2 (20020718)]/pool/main/p/perl-transition/perl-5.005-base_6.3_all.deb
Please use apt-cdrom to make this CD recognized by APT. apt-get update
cannot be used to add new CDs
Failed to fetch cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386
Binary-2 (20020718)]/pool/main/p/perl-transition/perl-5.005_6.3_all.deb
Please use apt-cdrom to make this CD recognized by APT. apt-get update
cannot be used to add new CDs
Failed to fetch cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386
Binary-1 (20020718)]/pool/main/p/perl/perl_5.6.1-7_i386.deb
Please use apt-cdrom to make this CD recognized by APT. apt-get update
cannot be used to add new CDs
(... deleted 10 similar lines )
E: Unable to fetch some archives, maybe try with --fix-missing?
I subsequently ran 'apt-get -f install' a total of three times before I
was satisfied that dpkg, apt and debconf were upgraded OK. I was
prompted to change between Binary CD 1 and Binary CD 2 several times,
without the above problem occurring, so I assumed it had gone away. Then
the 'apt-get --fix-broken --show-upgraded dist-upgrade' went well, and I
forgot about the problem untill it showed up again when I added the
security line to sources.list (where this report started).
My previous suggestion of using dpkg to install apt directly wouldn't
work, as the new apt depends on the new libc6, which would break
everything else on the system. Maybe what is needed is a statically
compiled version of apt that one can install by itself before doing
dist-upgrades. If I had had that then none of this would have happened,
as the CD's would have been read in by the new apt-cdrom, and the new
file locations would have been used from the start. I'm no expert, but
it seems to me that this might be a good idea?
--
Cheers,
.~.
/V\
// \\
/( )\
^`~´^
< hugge >
Reply to: