> 2) if there is no delta, it will "download" the new package (this may be
> because, the delta was too big, or the package was too small, or, some
> error)
> 3) after all available deltas have been applied, it may exit, or continue
> downloading all needed new .deb
> This behavior can be tuned with the option --deb-policy option, see
> man page.
I guess my question is: why does it ever download the `.deb` package?
[..time passes..]
Oh.. could it be that you do it as an optimization: if we're still
applying patches, rather than leave the network unused and since we
can't start `apt` yet, download some of the remaining packages, so the
(presumed) subsequent `apt` will be faster?
>> Q uestions that I can't answer based on the above output:
>> - I don't see any other mention of "avahi-daemon" than the "created" line,
>> so how was it created?
> by downloading the delta and applying it
But in the output there was no mention of downloading anything related to
that package, whereas most other packages have two lines, one about the
download and one about the creation (in my sample out, this is the case
for `libreoffice-calc`).
>> There's no subsequent matching "created" line, so IIUC it was
>> downloaded in non-delta form, which I'd expect `debdelta-upgrade`
>> never does (leaving it to `apt upgrade` instead).
> actually, it does
I did not expect that behavior.
>> - I'd appreciate seeing the actual size of the downloaded data on each
>> line (maybe instead of the time?).
> add some -v options
Duh, can't believe I didn't think of that.
This said, with a `-v` I get more output than what I'd like, but well,
one can't satisfy everyone.
Stefan
