Hi Michal, Le mardi 13 octobre 2009, Michal Marek a écrit :
Dne 13.10.2009 04:28, Markus Koßmann napsal(a):
Today it happened again that the kernel-source rpm at ftp.suse.com/pub/projects/kernel/kotd/HEAD/ is ahead of the other provided rpms : kernel-source version is 2.6.32-0.0.22.f4164a and and the other rpms are still at 2.6.32-0.0.12.1e3e0f5. The same problem occured allready two times in the last two weeks.
The problem is that the script always copies the latest built package to the ftp server. And because kernel-source builds significantly faster than the binary packages, it can easily lead to the situation you describe. And it could be that my recent fixes made this even more probable, I don't know. Would it help to keep old kernel-source versions that match versions of "important" binary kernels? E.g. for master/{i586,x86_64}/kernel-desktop, SLE11_BRANCH/i586/kernel-pae, SLE11_BRANCH/x86_64/kernel-default, etc, also copy the matching kernel-source if the latest kernel-source is too new. What do you think?
I think the kernel-source package should never be replaced by a new one, but simply added. Removal of old kernel-source packages should be a separate process, triggered by the deletion (replacement) of binary packages. Each time a binary kernel package is deleted, you should check whether it was the last one matching any source package, and if this is the case, that kernel-source package can be deleted. I know this sounds complex, but this is the only safe bet from a legal perspective. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org