Does the publisher support some sort of "lingering" for already published, but stale, packages? If a republish of the repository happens after libzypp has downloaded the metadata, but before it actually downloads the binary package, the attempted download fails with ENOENT because the old package will be just removed. It would be cool if the old binaries will remain for a short period of time until they are finally wiped from the download repository. Neither YaST nor libzypp handles such ENOENT, as a result unattended installations will run into a hard error. It will eventually help if the published binary packages do not change name. I think it will be more robust if they are published as 'arch/name.rpm' instead of 'arch/name-version-revision.arch.rpm'. Does the publisher support that? Olaf