Bug 377569

See /etc/zypp/zypp.conf

Set 

download.use_patchrpm=false
download.use_deltarpm=false

Then the packaging of zypper has to be fixed.  rpm -qc zypper doesn't report /etc/zypp/zypp.conf

Also the man page doesn't provide any information regarding this.

The zypper man page does mention /etc/zypp/zypp.conf 

"ZYpp config file (/etc/zypp/zypp.conf)."

Also

benji@lcars:~> rpm -qc libzypp
/etc/zypp/zypp.conf

zypper is not the only thing that uses libzypp.

Ok.  /etc/zypp/zypp.conf belongs to libzypp and there it is packaged as config file.

Independent of this ignoring a missing patch or delta RPM file if the full RPM is available might be an enhancement.  The end user will not care how the system gets to a current state.

And as this is already working if the errors are ignored by hand the implementation shouldn't be hard.

(In reply to comment #4 from Lars Mueller)
> Independent of this ignoring a missing patch or delta RPM file if the full RPM
> is available might be an enhancement.  The end user will not care how the
> system gets to a current state.

Do you mean via a command line option (for the install/update/dist-upgrade/source-install commands) in zypper?

A command line option would require the knowledge about the option by the user.

I have an automatic mechanism in mind.

a) Try to download delta rpm failed -> try to download patch rpm.
b) Try to download patch rpm failed -> try to download full rpm.
c) If the download of the full rpm failed inform the user.

If a) or b) fails a note in the logs might be useful.

AFAIK it should already work exactly this way. What behavior do you see?

The opposite.  YaST or which piece in charge of downloading the packages fails if a requested file is missing.

As mentioned before pressing the 'ignore' button shows this approach is already implemented.  But requesting the user to ignore 100 times is no option.  Even asking once would make the hard YaST work flow superfluous harder.

This is bug. If you can reproduce it, please attach the logs (yast (debug mode) or zypper).

I use a plain openSUSE 10.3.  Please reproduce yourself.  I already spent much to much time on reporting YaST bugs and bugzilla ping pong.

Sorry, i've forgotten that you removed the patch and delta rpms from your repo, so that's why you are getting the error popups. So this is indeed an enhancement request. The patch/delta rpm handling is currently undergoing a change, so maybe this request could be taken into account in time for 11.0.

Ah.. i've forgotten about this, i'll do it after 11.0.

.

.

Still in 11.2

(In reply to comment #4)
> Ok.  /etc/zypp/zypp.conf belongs to libzypp and there it is packaged as config
> file.
> 
> Independent of this ignoring a missing patch or delta RPM file if the full RPM
> is available might be an enhancement.  The end user will not care how the
> system gets to a current state.
> 
> And as this is already working if the errors are ignored by hand the
> implementation shouldn't be hard.

Yes, libzypp just reports the delta download error, but continues afterwards with another delta or the full rpm.

Zypper (2.x.x, maybe also older) already ignores the problemDeltaDownload callback (it only prints the error, does not prompt). Maybe YaST can do the same (simply ignore it), Lado?

(In reply to comment #17)
> Zypper (2.x.x, maybe also older) already ignores the problemDeltaDownload

i mean 1.2.x, of course

I have checked all problemDeltaDownload callbacks in Yast and fixed one place where it displayed an error popup.

Fixed in yast2-2.20.0 (FACTORY, openSUSE-11.4)

*** Bug 629142 has been marked as a duplicate of this bug. ***

This is an autogenerated message for OBS integration:
This bug (377569) was mentioned in
https://build.opensuse.org/request/show/49937 Factory / yast2