On Friday, 12. September 2003 02:24, Matt Zimmerman wrote: > On Thu, Sep 11, 2003 at 10:22:06PM +0200, Jens Seidel wrote: > > I got the following bug report from a user, so I don't know the used > > version of apt-cdrom and cannot give a detailed explanation. But the > > same happened to me a few month ago too. > > Can you or the user try the following patch? > > --- apt-cdrom.cc.~1.43.~ 1969-12-31 19:00:01.000000000 -0500 > +++ apt-cdrom.cc 2003-09-11 20:06:48.000000000 -0400 > @@ -101,7 +101,8 @@ > //strcmp(Dir->d_name,"source") == 0 || > strcmp(Dir->d_name,".disk") == 0 || > strcmp(Dir->d_name,"experimental") == 0 || > - strcmp(Dir->d_name,"binary-all") == 0) > + strcmp(Dir->d_name,"binary-all") == 0 || > + strcmp(Dir->d_name,"debian-installer") == 0) > continue; > > // See if the name is a sub directory > > I don't know much about how the new CDs are constructed, but I think this > will fix it.
Yes, you're right. This fixes the bug. Thanks, you are very fast! I suggest that you post a message to debian-boot and debian-cd to inform all about this fix. I'm sure that other people (will) know this problem too. It's also possible that another directory name containing "udeb" (such as udeb-dir ??) was used in the past instead of debian-installer. If this is true, than you should exclude this path as well. Nevertheless it's important that the debian-installer and CD creator people know that apt-cdrom needs to be patched, whenever they change the directory name. Let's hope that *.udeb's are not available in default paths such as main, contrib, non-free. Again thanks, Jens
