hi

Il 27/10/23 17:34, Stefan Monnier ha scritto:
I'm very happily using `debdelta-upgrade` now that I finally heard about
it (I've been using Debian for 20 years and wishing for something like
DebDelta for a big part of it), so first: thanks!

One think that annoys me is that I find the output unclear.  E.g. I see
[note the output was actually in French, so I translated it by hand, it
probably doesn't match 100% what debdelta would say]:

     Created,    time  0.42sec, speed 202kB/sec, avahi-daemon_0.8-12_i386.deb
     [...]
     The delta est too large: libmbim-glib4_1.28.4-2_1.30.0-1_i386.debdelta
     Delta was not created since new package is too small: 
libmbim-proxy_1.28.4-2_1.30.0-1_i386.debdelta
     [...]
     Created,    time  1.07sec, speed 239kB/sec, 
libedata-book-1.2-27_3.50.1-1_i386.deb
     [...]
     Downloaded, time  0.11sec, speed  8kB/sec, 
libudisks2-0_2.10.1-1_2.10.1-2_i386.debdelta
     Downloaded, time  0.24sec, speed 13MB/sec, 
libreoffice-calc_4%3a7.5.6-1_4%3a7.5.8~rc1-2_i386.debdelta
     [...]
     Downloaded, time  0.02sec, speed 488kB/sec, libmbim-proxy_1.30.0-1_i386.deb
     Downloaded, time  0.03sec, speed 7658kB/sec, 
libmbim-glib4_1.30.0-1_i386.deb
     [...]
     Created,    time 27.30sec, speed 296kB/sec, 
libreoffice-calc_4%3a7.5.8~rc1-2_i386.deb
     [...]
     Statistics of delta-upgrade:
        debs result total, size 115MB time 257sec virtual speed 458kB/sec

by default, debdelta-upgrade tries to be smart: for each package that has to be upgraded,

1)  if there is  a delta, it will download the delta, apply it, and "create" the new deb 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.

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
- Why/how were `libmbim-proxy` and `libmbim-glib4` downloaded (since
   there's a delta missing for them) and from where?
from the standard repository of debs
   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
- The "Downloaded" speed varies very widely (w
I have no idea
- I'd appreciate seeing the actual size of the downloaded data on each
   line (maybe instead of the time?).
add some -v options
- In the final statistics, I'd be interested to see a report comparing
   the amount of bytes that passed over the network compared to the
   number of bytes in the resulting `.deb` files (so as to see how much
   we gained in this).

add some -v options

bye

a.


Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to