https://bugzilla.novell.com/show_bug.cgi?id=325922 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com AssignedTo|kkaempf@novell.com |jkupec@novell.com QAContact|kkaempf@novell.com |visnov@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=325922#c2 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|ma@novell.com | --- Comment #2 from Michael Andres 2007-09-18 04:59:51 MST --- There are no different kinds of 'package download' callbacks. In fact there is one and it is called 'provide package'. Starting to provide a package, we don't know what will be downloaded. If we find a delta candidate, we may give it a try and download it. If applydeltarpm fails for some reason, we try another delta or look for a patch. And if all fails we try the full package. 'provide package start' is reported, and each file we download is reported. So it should be: Providing package kernel-default-2.6.22.5-12.i586 Downloading delta: kernel-default-2.6.22.5-10_12.i586.delta.rpm, 4.4 M Applying delta: ... Delta failed. Try next: Downloading patch: kernel-default-2.6.22.5-12, 8 M Patch failed. Try next: Downloading package kernel-default-2.6.22.5-12.i586, 20.1 M -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.