Using the updater applet to get updates for any package

Hi folks, I would like the updater applet to offer updates other than security fixes from the base repos. For example I would like to be notified automatically about updates for VLC and Chrome. How do I do that?

I found the following thread on the subject here:

kupdateapplet-zypper missing in 11.3rc?

It seems that you can get what you want if you use openSUSE 11.3 by adding in this repository:

Index of /repositories/YaST:/Head/openSUSE_11.3

You then must downgrade Kupdateapplet & Kupdateapplet-packagekit to 0.9.9.-1.1 and then load the package Kupdateapplet-zypp of the same version. Then, in the configuration of the update applet, you will find the new backend called ZYpp Plugin which will do what you request. I found the following link that shows what the added icons mean:

Kupdateapplet - openSUSE

I can’t say if such a change is recommended or not as the older version may no longer be supported, but I don’t really know for sure. I can say that it seems to work OK, but you must go into YaST / Software / Software Management, search on the update applet and lock in the versions of all three files. Otherwise, it will update itself out of existence, automatically for you. lol!

Thank You,

On 02/04/2011 11:06 PM, tempusfugit wrote:
>
> Hi folks, I would like the updater applet to offer updates other than
> security fixes from the base repos.

updates are security patches and bug fixes to a software package and
generally will not change the package’s version number (it may change
a release number, or date)

upgrades are a different thing, it is not a patch to an existing
version, instead it is a new version…

the updater is not an upgrader…

example: openSUSE 11.3 was released with KDE4.4.4, since release there
have been (i think) patches to 4.4.4 via the updater…

but, the updated is not involved (at all) in moving from 4.4.4 to 4.5.5…

occasionally (rarely actually) new versions of software are offered
for install via YaST without resorting to ‘factory’ repos (where is
helf very unreliable alpha level software and sometime BETA which is
STILL not for use on any machine with data you want to keep)

some other distros have what is known as a “rolling release” wherein
when new a package is stable it is just rolled in…

> For example I would like to be
> notified automatically about updates for VLC and Chrome. How do I do
> that?

you can today go to the source of VLC and download the latest stable
code, compile and install it…

but, if you want an RPM packaged to slide safely into your openSUSE
you do one of these things:

  1. build that package yourself on your machine

  2. use the openSUSE Build Service (a self help place with instructions
    on how to do it <https://build.opensuse.org/>

  3. find someone willing to build it for you

  4. take the chance of failure (or success) by installing from ‘factory’

  5. hope the developers of openSUSE will add the new version to the
    existing repo for your version

  6. wait for a version of openSUSE to be released with the new package
    in it

got it?


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

On 02/05/2011 02:36 AM, jdmcdaniel3 wrote:

> I can’t say if such a change is recommended

i may be wrong (has happened:) but, i don’t think you understood the
OP’s question…at least, you didn’t understand it the way i
did…so, maybe i gave a wholly off base answer…

don’t know…


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

Okay, maybe I didn’t make that clear enough…

I have added some repo for a piece of software for which updates a security critical (eg a browser). The packages in that repo are updated whenever a new version becomes available but the updater applet doesn’t care because it’s “just” some third party repo. Right now I can either scour the repos or some IT news site all the time to be aware of security holes and available patches. That sucks. I’m sitting at a computer and I’ll be ****ed if it couldn’t do that by itself. I don’t care if the updater applet or some other program does the job, but it needs to be automatic, otherwise it’s pointless. Right now the only option I see is to create a bash script involving zypper, grep and some simple if-statements. But surely someone must have thought of this before and have a solution ready?!

tempusfugit Okay, maybe I didn’t make that clear enough…

I have added some repo for a piece of software for which updates a security critical (eg a browser). The packages in that repo are updated whenever a new version becomes available but the updater applet doesn’t care because it’s “just” some third party repo. Right now I can either scour the repos or some IT news site all the time to be aware of security holes and available patches. That sucks. I’m sitting at a computer and I’ll be ****ed if it couldn’t do that by itself. I don’t care if the updater applet or some other program does the job, but it needs to be automatic, otherwise it’s pointless. Right now the only option I see is to create a bash script involving zypper, grep and some simple if-statements. But surely someone must have thought of this before and have a solution ready?!
tempusfugit, I have offered a way to be notified for any file update present. DenverD offered an explanation of how the standard update works. In all cases, you must provide the authority to proceed with the updating and some tasks will take manual intervention to make the updates work. Those are your options and anything else that you might want is simply a wish list which you can make in the form of a suggestion to those that actually write the openSUSE packaging.

Thank You,

Thank you for that possibility, but downgrading the updater doesn’t really appeal to me, that’s why I asked for a non-hack way to do this. I figured I wouldn’t be the first person to want this and there had to be an “official” way. I guess I will resort to scripting something myself then.

Thank you for that possibility, but downgrading the updater doesn’t really appeal to me, that’s why I asked for a non-hack way to do this. I figured I wouldn’t be the first person to want this and there had to be an “official” way. I guess I will resort to scripting something myself then.
Necessity is the mother of invention as they say. If you come up with such a scripting solution, consider sharing it with us in the Development section. That is what I do with the scripts that I have written. By the way, on my main computer, I did downgrade these files and I have not had any issues with it. So, it looks like it works fine with openSUSE 11.3, but will not be carried forth with oipenSUSE 11.4, as far as I know, but it is not too late to make such a suggestion to it.

Thank You,

On 02/05/2011 03:06 PM, tempusfugit wrote:
> But surely someone must have thought of this before and have a solution ready?!

as far as i know (i have been wrong before) YaST Online Updater (YOU)
“learns” that a new update is available by comparing here to the
update repo…

i don’t know if it looks at ALL other repos which are enabled and
updating (is the repo you added enabled and updating?), but it would
seem a huge waste of time for it to do that against repos known to
not ever change (like oss/non-oss)…

maybe it should be possible for users to pick other repos to be
treated like the communities update repo–you could try asking for it
in FATE: https://features.opensuse.org/

as far as i know, every browser which is installed from oss/non-oss
and which has a subsequent security patch released that patch is
placed in the update repo, and automatically propagated to all users
using the update repo…

but, if the browser you want to automatically update is not, perhaps
you could ask the devs why not…or suggest it be added…either of
those would fit into why FATE exists…


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11