This is the first time I've observed this happening, delta rpm did the opposite of what I expected, dunno if I have a problem in this system or if it is in the data received? I thought it interesting if nothing else ...
...................... Is this ok [y/N]: y Downloading Packages: (1/8): greybird-gtk2-theme-3.22.4-1.fc26_3.22.5-1.fc26.noar 8.8 kB/s | 11 (2/8): greybird-gtk3-theme-3.22.4-1.fc26_3.22.5-1.fc26.noar 17 kB/s | 21 (3/8): greybird-xfce4-notifyd-theme-3.22.4-1.fc26_3.22.5-1. 4.4 kB/s | 8.7 [DRPM 1/7] greybird-gtk2-theme-3.22.4-1.fc26_3.22.5-1.fc26.noarch.drpm: don [DRPM 2/7] greybird-gtk3-theme-3.22.4-1.fc26_3.22.5-1.fc26.noarch.drpm: don (4/8): greybird-xfwm4-theme-3.22.4-1.fc26_3.22.5-1.fc26.noa 54 kB/s | 49 [DRPM 3/7] greybird-xfce4-notifyd-theme-3.22.4-1.fc26_3.22.5-1.fc26.noarch. (5/8): libsolv-0.6.29-1.fc26_0.6.29-2.fc26.x86_64.drpm 30 kB/s | 43 [DRPM 4/7] greybird-xfwm4-theme-3.22.4-1.fc26_3.22.5-1.fc26.noarch.drpm: do (6/8): mpg123-libs-1.23.8-5.fc26_1.25.6-1.fc26.x86_64.drpm 88 kB/s | 87 [DRPM 5/7] libsolv-0.6.29-1.fc26_0.6.29-2.fc26.x86_64.drpm: done (7/8): selinux-policy-3.13.1-260.9.fc26.noarch.rpm 274 kB/s | 506 (8/8): selinux-policy-targeted-3.13.1-260.8.fc26_3.13.1-260 1.1 MB/s | 5.8 [DRPM 6/7] mpg123-libs-1.23.8-5.fc26_1.25.6-1.fc26.x86_64.drpm: done /var/lib/selinux/targeted/active/policy.kern: read error (tried to read 8192 bytes from offset 3871320) cannot reconstruct rpm from disk files Some packages were not downloaded. Retrying. selinux-policy-targeted-3.13.1-260.9.fc26.noarch.rpm 1.2 MB/s | 9.4 --------------------------------------------------------------------------- Total 894 kB/s | 16 Failed Delta RPMs increased 10.7 MB of updates to 15.9 MB (-48.1% wasted)
.......................
The size of the update is small and at this time of day it does not matter but it just caught my eye ...
Bob
On 21 September 2017 at 08:47, Bob Goodwin bobgoodwin@fastmail.us wrote:
This is the first time I've observed this happening, delta rpm did the opposite of what I expected, dunno if I have a problem in this system or if it is in the data received? I thought it interesting if nothing else ...
Noticed that too. I've not dug into the cause - my guess would be that the "policy.kern" file was different to that expected by the DRPM for whatever reason - but the file size failure is easy enough to explain. There is not a significant size reduction between the DRPM and the full RPM, so having downloaded the DRPM and failed to create the RPM, DNF then downloaded the RPM as well, effectively doubling the size of the download. Combined with the other files in the update, that's pushed the total amount of data downloaded in DRPMs + RPM to more than the total of the full RPMs.
Regards, Andy
On 09/21/17 04:12, Andy Blanchard wrote:
On 21 September 2017 at 08:47, Bob Goodwin bobgoodwin@fastmail.us wrote:
This is the first time I've observed this happening, delta rpm did the opposite of what I expected, dunno if I have a problem in this system or if it is in the data received? I thought it interesting if nothing else ...
Noticed that too. I've not dug into the cause - my guess would be that the "policy.kern" file was different to that expected by the DRPM for whatever reason - but the file size failure is easy enough to explain. There is not a significant size reduction between the DRPM and the full RPM, so having downloaded the DRPM and failed to create the RPM, DNF then downloaded the RPM as well, effectively doubling the size of the download. Combined with the other files in the update, that's pushed the total amount of data downloaded in DRPMs + RPM to more than the total of the full RPMs.
Regards, Andy
. Yes, increasing the data by roughly 50%. "Delta RPMs increased 10.7 MB of updates to 15.9 MB (-48.1% wasted)"
Since you saw it too, I will assume it is not a problem in my system, and will watch for any recurrence.
Thanks for responding.
Bob
-
Andy Blanchard -
Bob Goodwin