yum update behavior plugin

hi guys,

anyone fancy a shot at writing a yum plugin that would
change the yum
update behavior a bit.

what I'd like to end up with is that if in a yum update
process, there
is an update to yum itself - that yum update should run
first, once
done, yum should then restart and run through the rest of
yum update.

- K
-- 
Karanbir Singh : http://www.karan.org/ :
2522219icq
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Karanbir Singh napsal(a):
> hi guys,
> 
> anyone fancy a shot at writing a yum plugin that would
change the yum
> update behavior a bit.
> 
> what I'd like to end up with is that if in a yum
update process, there
> is an update to yum itself - that yum update should run
first, once
> done, yum should then restart and run through the rest
of yum update.
> 
> - K
Well,
plugin to remove all packages but yum, if yum is within
updated
packages, is easy to write. But plugin can only stop yum
execution and I
can't see way to run yum again after yum update by itself.
What is the
purpose of that plugin?
David
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

David Hrbáč wrote:
>> what I'd like to end up with is that if in a yum
update process, there
>> is an update to yum itself - that yum update should
run first, once
>> done, yum should then restart and run through the
rest of yum update.
> plugin to remove all packages but yum, if yum is within
updated
> packages, is easy to write. But plugin can only stop
yum execution and I
> can't see way to run yum again after yum update by
itself. What is the
> purpose of that plugin?

Hi David, thanks for picking up on this.

Just displaying a message will be enough for now - if the
process can 
exit with a 'yum has been updated, you need to now run yum
again in 
order to process the other updates' - that should be fine,
i think.

purpose of the plugin is to fix an issue with yum itself,
where it 
breaks into bits when there is functionality changes in a
yum update, 
and can leave other packages in a not-completely-installed
state.

in specific terms, the issue we have is updating yum 2.0 to
yum 2.4 / 
2.2 where there is a change in the way kernel packages are
installed. If 
yum is updated along with a new kernel package - the kernel
package isnt 
installed properly.

And besides this, I think packages in a repository should be
able to 
assume the functional process of the package manager
included in the 
repository.

-- 
Karanbir Singh : http://www.karan.org/ :
2522219icq
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

El vie, 11-08-2006 a las 16:54 +0100, Karanbir Singh
escribió:
> hi guys,
> 
> anyone fancy a shot at writing a yum plugin that would
change the yum
> update behavior a bit.
> 
> what I'd like to end up with is that if in a yum
update process, there
> is an update to yum itself - that yum update should run
first, once
> done, yum should then restart and run through the rest
of yum update.
> 
> - K

Hi Karan,

Don't know how are you folks in that plugin state but if
this can be
useful... feel free to pkg and try it or use it if it's
what you
expected. First approach, new with pyton, new with yum... 2
be tested.

Jose.


_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

On Sat, 12 Aug 2006, David Hrbá�~M wrote:

> Karanbir Singh napsal(a):
>>
>> what I'd like to end up with is that if in a yum
update process, there
>> is an update to yum itself - that yum update should
run first, once
>> done, yum should then restart and run through the
rest of yum update.
>
> Well, plugin to remove all packages but yum, if yum is
within updated 
> packages, is easy to write. But plugin can only stop
yum execution and I 
> can't see way to run yum again after yum update by
itself.

I don't see why yum couldn't update yum, then exec the new
yum program, 
listing the remaining packages as install arguments. You'd
need to unlock 
the lock file before calling execve.

---
Charlie_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

> I don't see why yum couldn't update yum, then exec
the new yum program,
> listing the remaining packages as install arguments.
You'd need to unlock
> the lock file before calling execve.

But IMHO that wouldn't be very pretty, it would be nicer if
a plugin could
trigger a jump back in the processing chain.

-- Daniel

_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Charlie Brady wrote:
>> Well, plugin to remove all packages but yum, if yum
is within updated 
>> packages, is easy to write. But plugin can only
stop yum execution and 
>> I can't see way to run yum again after yum update
by itself.
> 
> I don't see why yum couldn't update yum, then exec
the new yum program, 
> listing the remaining packages as install arguments.
You'd need to 
> unlock the lock file before calling execve.

no! yum, on re-entry, needs to re-parse the metadata - its
possible 
remote end metadata has changed for the new yum as well.


-- 
Karanbir Singh : http://www.karan.org/ :
2522219icq
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

On Sun, 13 Aug 2006, Karanbir Singh wrote:

> Charlie Brady wrote:
>>> Well, plugin to remove all packages but yum, if
yum is within updated 
>>> packages, is easy to write. But plugin can only
stop yum execution and I 
>>> can't see way to run yum again after yum
update by itself.
>> 
>> I don't see why yum couldn't update yum, then
exec the new yum program, 
>> listing the remaining packages as install
arguments. You'd need to unlock 
>> the lock file before calling execve.
>
> no! yum, on re-entry, needs to re-parse the metadata -
its possible remote 
> end metadata has changed for the new yum as well.

For a while I couldn't see what you were saying
"no!" to - certainly my 
assertion about the lock file is true.

OK, so you want the first yum to exec a new yum with the
same arguments 
that it itself was called with. It will then calculate its
own transaction 
set.

Hopefully it will not itself try to replace itself with the
old yum 
package.

---
Charlie
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Charlie Brady wrote:
>> Charlie Brady wrote:
>>>> Well, plugin to remove all packages but
yum, if yum is within 
>>>> updated packages, is easy to write. But
plugin can only stop yum 
>>>> execution and I can't see way to run yum
again after yum update by 
>>>> itself.
>>>
>>> I don't see why yum couldn't update yum, then
exec the new yum 
>>> program, listing the remaining packages as
install arguments. You'd 
>>> need to unlock the lock file before calling
execve.
>>
>> no! yum, on re-entry, needs to re-parse the
metadata - its possible 
>> remote end metadata has changed for the new yum as
well.
> 
> OK, so you want the first yum to exec a new yum with
the same arguments 
> that it itself was called with. It will then calculate
its own 
> transaction set.

yes 

> Hopefully it will not itself try to replace itself with
the old yum 
> package.

humm ? after the yum package has updated, there really
should be no hint 
of the old yum stuff.....

-- 
Karanbir Singh : http://www.karan.org/ :
2522219icq
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

On Sun, 2006-08-13 at 12:13 +0100, Karanbir Singh wrote:
> Charlie Brady wrote:
> >> Charlie Brady wrote:
> >>>> Well, plugin to remove all packages
but yum, if yum is within 
> >>>> updated packages, is easy to write.
But plugin can only stop yum 
> >>>> execution and I can't see way to run
yum again after yum update by 
> >>>> itself.
> >>>
> >>> I don't see why yum couldn't update yum,
then exec the new yum 
> >>> program, listing the remaining packages as
install arguments. You'd 
> >>> need to unlock the lock file before
calling execve.
> >>
> >> no! yum, on re-entry, needs to re-parse the
metadata - its possible 
> >> remote end metadata has changed for the new
yum as well.
> > 
> > OK, so you want the first yum to exec a new yum
with the same arguments 
> > that it itself was called with. It will then
calculate its own 
> > transaction set.
> 
> yes 
> 
> > Hopefully it will not itself try to replace itself
with the old yum 
> > package.
> 
> humm ? after the yum package has updated, there really
should be no hint 
> of the old yum stuff.....


You could also put a shell or python wrapper around yum for
this thing
if you wanted to:

parse the arguments on the cli and see if it is just running
'update'
for all packages w/o looking for any other specific thing.
If so then
first run a yum update yum. If that completes successfully
then run the
rest of the update.

that might be easiest, actually.

-sv


_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel