I am unclear about what the alleged bug is supposed to be. The bug title looks like correct behaviour. If a package checksum fails, it is normal to clear the RPM cache:
 $ urpmi --clean
and re-commence the update. If one package continues to cause trouble, it can be excluded from the updates (UNticking it) using MCC-Manage Software-Update System.

> incorrectly loaded package. Does not automatically reload that package
If this is the real complaint, do you mean that if a package checksum fails, it should be downloaded again (& how many tries?). That looks like an enhancement request.

The example you give above does not indicate at what point Internet was disconnected - which packages had been fully downloaded (into /var/cache/urpmi/rpms/ ), which one interrupted (looks like glibc). So its checksum fails, and the entire update is aborted. A partial update of these intimately related packages would not have been correct.

Feel free to re-open this bug if I have misunderstood something; or as an enhancement request..

CC: (none) => lewyssmith
Status: NEW => RESOLVED
Resolution: (none) => INVALID

Whenever I start urpmi, I assume a clean cache. A cache is usually only a temporary buffer and should be hidden from the user (French: cache – hide-out). If this behaviour is not desired, at least for files with errors, they should be reloaded once in the cache.

Thanks also for the hint (urpmi --clean).

Heiko

Resolution: INVALID => (none)
Status: RESOLVED => REOPENED

From "man urpmi" ...
       --clean
           Remove all packages from the cache in directory /var/cache/urpmi/rpms.

       --noclean
           Do not remove any package from the cache in directory /var/cache/urpmi/rpms.

From "man urpmi.cfg" (the config file is stored as /etc/urpmi/urpmi.cfg) ...
       pre-clean, post-clean, clean
           Control cache management for urpmi, default is only activated as post-clean.

So the default is to clean the cache only after it has successfully installed
the selected packages. The reason for that being chosen as the default is to
allow the use of urpmi with the --resume option, in the case of an interrupted
download.

If you want the option pre-clean to be the setting used on your system, then
edit /etc/urpmi/urpmi.cfg, and add the line to the global options so that the
start of the file is similar to ...
{
  pre-clean
}

Closing the bug again as this is a design choice, not a bug.

The system may have other global options already set, in which case just
add the pre-clean option.

I've seen what happens when the default is pre-clean, on windows systems where
it silently downloads a failed update, over and over again, costing people a
lot of money due to exceeding their data caps. For that reason, I'm strongly
against changing the default.

As this is the system administrators choice, closing this bug again.

Status: REOPENED => RESOLVED
Resolution: (none) => INVALID
CC: (none) => davidwhodgins

Sorry, I rarely read documentaries. Thanks for the hints! 
I just like fault-tolerant software (one reload is not so critical).

Heiko