Daniel de Kok wrote on Sun, 07 May 2006 23:24:56 +0200:
I have attached the plugin gzipped. The instructions for enabling the plugin are at the top of the file. The default priority for repositories is 99, a lower number is a higher priority.
So far seems to be okay, lists at the moment the same as with protectbase since only the packages are left for updating that aren't in any repo.
Kai
On Mon, 2006-05-08 at 01:31 +0200, Kai Schaetzl wrote:
Daniel de Kok wrote on Sun, 07 May 2006 23:24:56 +0200:
I have attached the plugin gzipped. The instructions for enabling the plugin are at the top of the file. The default priority for repositories is 99, a lower number is a higher priority.
So far seems to be okay, lists at the moment the same as with protectbase since only the packages are left for updating that aren't in any repo.
Kai
I actually think that the priorities plugin works better and we are looking at it now for inclusion into CentOS.
Not sure if it will go in exactly as is or not right now.
It also breaks at the update stage with the old packages for clamav between dag and kbs repos ... letting you know you need to block one of them.
I believe that kbs might have already incorporated the required changes to fix this update issue.
Johnny Hughes wrote on Mon, 08 May 2006 06:42:43 -0500:
I actually think that the priorities plugin works better and we are looking at it now for inclusion into CentOS.
Not sure if it will go in exactly as is or not right now.
It also breaks at the update stage with the old packages for clamav between dag and kbs repos ... letting you know you need to block one of them.
I believe that kbs might have already incorporated the required changes to fix this update issue.
Everything perfect then until the next package obsoletes a matching name ;-)
Kai
On Mon, 2006-05-08 at 17:31 +0200, Kai Schaetzl wrote:
Johnny Hughes wrote on Mon, 08 May 2006 06:42:43 -0500:
I actually think that the priorities plugin works better and we are looking at it now for inclusion into CentOS.
Not sure if it will go in exactly as is or not right now.
It also breaks at the update stage with the old packages for clamav between dag and kbs repos ... letting you know you need to block one of them.
I believe that kbs might have already incorporated the required changes to fix this update issue.
Everything perfect then until the next package obsoletes a matching name ;-)
And we are working on that for the priorities plugin :)
and we may backport that fix to the protectbase plugin too later.
-
Johnny Hughes -
Kai Schaetzl