Hi Goswin, I have a question about this bug report. It's not 100% clear to me what the intended working of the pdiff option is.
> > I don't think that's the problem, since I was already using the > > --pdiff=mirror option (see my previous mail). > > Right you are. Just found another bug then. Somwhere some "if" > statement must have been lost or forgotten and --pdiff=mirror just > doesn't work as promised. It still uses the pdiff files. You have to > use --pdiff=none to actualy work around the problem. The man page says: --pdiff=use|mirror|none If the Release file contains entries for pdiff files then debmirror will attempt to update the Packages and Sources files with them but will not include them in the mirror. This is the default ’use’ behavior and avoids having time consuming pdiff files for a fast local mirror. Spec‐ ifying --pdiff=mirror will include the downloaded pdiff files in the mirror while specifying --pdiff=none will completely ignore pdiff files. From your comments in this BR it seems the intention is: - use: use to update Packages/Sources but don't include on mirror - mirror: include on mirror but do *not* use to update Packages/Sources - none: ignore them completely However, it seems more logical to me to have: - use: use only to update Packages/Sources but don't include on mirror - mirror: include on mirror but *and* use to update Packages/Sources - none: ignore them completely And IIUC that is exactly how it currently works. IMO the first set of definitions only makes sense if there was also an option "full" or "both" or something like that. I'd appreciate your input. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
