Mailinglist Archive: zypp-devel (83 mails)
| < Previous | Next > |
[zypp-devel] Help on gpk-update-icon
- From: "Scott Reeves" <sreeves@xxxxxxxxxx>
- Date: Thu, 26 Jun 2008 19:12:01 -0600
- Message-id: <4863E9A5.EBB0.0076.0@xxxxxxxxxx>
The GM version of the gnome updater, gpk-update-icon, after applying a (set of)
updates, gets in a state that it stops looking for new updates until it is
restarted. So we need a patch that will lay down a new fixed gpk-update-icon
that loops properly and we need to kill the old running gpk-update-icon
instance and start the new fixed one.
When getting available updates if the updater finds a relevant patch marked
with restart_suggested it immediately returns just that patch. After discussion
it was decided that if it finds a restart_suggested patch it should return all
relevant restart_suggested patches.
We have a patch (tagged with restart_suggested so it gets returned first) that
fixes these code issues and restarts the currently running updater instance. It
does this by laying down a restart-gpk-update-icon.sh file and running that
shell file in the gnome-packagekit post install script. The
restart-gpk-update-icon.sh file waits until the current update is finished and
then restarts the updater.
The problem is when there are multiple restart_suggested patches available. The
gnome-packagekit update needs to be done as the first update as if a different
update is applied first, then the user will need to manually restart the
updater (ie logout / login). There are now 2 restart_suggested patches (in the
11.0-test repo) and will probably be more in the future. So we are looking for
a way to solve this given that the GM updater will just return the first
restart_suggested patch it is given.
some suggestions we have tried that have problems
Manipulate the patch setup (date, name, release tag, ...) so that we could
guarantee this patch would be returned first from the libzypp iterators but
that does not appear possible.
Setting up all restart_suggested patches so that if and only if
gnome-packagekit is installed then it will upgrade gnome-packagekit. I based
my proposal of a refresh atom on the description here
(http://en.opensuse.org/Libzypp/Patches/Rationale) and that is evidently out of
date and this is not possible in 11.0 as it will install gnome-packagekit on
non gnome setups.
Setting up a dummy package that just contains the restart-gpk-update-icon
script and having all restart_suggested patches install this. This will not
work as say a new GM install 9 months down the road goes to apply updates and
there are multiple restart_suggested patches relevant. If the gnome-packagekit
patch is not returned first then the dummy package will be installed and the
updater restarted. But if the next patch is also not the gnome-packagekit patch
then the dummy package will not be reinstalled so the script won't be executed.
Also ideally we would like to get the new updater on in the first update
rather than multiple rounds required.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
updates, gets in a state that it stops looking for new updates until it is
restarted. So we need a patch that will lay down a new fixed gpk-update-icon
that loops properly and we need to kill the old running gpk-update-icon
instance and start the new fixed one.
When getting available updates if the updater finds a relevant patch marked
with restart_suggested it immediately returns just that patch. After discussion
it was decided that if it finds a restart_suggested patch it should return all
relevant restart_suggested patches.
We have a patch (tagged with restart_suggested so it gets returned first) that
fixes these code issues and restarts the currently running updater instance. It
does this by laying down a restart-gpk-update-icon.sh file and running that
shell file in the gnome-packagekit post install script. The
restart-gpk-update-icon.sh file waits until the current update is finished and
then restarts the updater.
The problem is when there are multiple restart_suggested patches available. The
gnome-packagekit update needs to be done as the first update as if a different
update is applied first, then the user will need to manually restart the
updater (ie logout / login). There are now 2 restart_suggested patches (in the
11.0-test repo) and will probably be more in the future. So we are looking for
a way to solve this given that the GM updater will just return the first
restart_suggested patch it is given.
some suggestions we have tried that have problems
Manipulate the patch setup (date, name, release tag, ...) so that we could
guarantee this patch would be returned first from the libzypp iterators but
that does not appear possible.
Setting up all restart_suggested patches so that if and only if
gnome-packagekit is installed then it will upgrade gnome-packagekit. I based
my proposal of a refresh atom on the description here
(http://en.opensuse.org/Libzypp/Patches/Rationale) and that is evidently out of
date and this is not possible in 11.0 as it will install gnome-packagekit on
non gnome setups.
Setting up a dummy package that just contains the restart-gpk-update-icon
script and having all restart_suggested patches install this. This will not
work as say a new GM install 9 months down the road goes to apply updates and
there are multiple restart_suggested patches relevant. If the gnome-packagekit
patch is not returned first then the dummy package will be installed and the
updater restarted. But if the next patch is also not the gnome-packagekit patch
then the dummy package will not be reinstalled so the script won't be executed.
Also ideally we would like to get the new updater on in the first update
rather than multiple rounds required.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |