I (re)installed Opensuse 13.1 now with Gnome and _x64 (my earlier installation was KDE and i686) and it works just fine but then I install Opera from the normal repositories (+packman) and at the first run the software tells me that it’s not at the current version (and that I’m at risk using the installed software).
I download the rpm but the default option the downloader gives me is to remove the software, and I select save as.
Now, I have an Opera rpm for opensuse but I’m a bit at loss: Normally, I’d expect the software to be adapted so that upgrades follow the suse repositories. That seems not to be the case.
So my question:
Do I install the latest Opera and remain safe according to them or do I ignore the upgrade message?
jdeca57 wrote:
>
> I (re)installed Opensuse 13.1 now with Gnome and _x64 (my earlier
> installation was KDE and i686) and it works just fine but then I install
> Opera from the normal repositories (+packman) and at the first run the
> software tells me that it’s not at the current version (and that I’m at
> risk using the installed software).
>
> I download the rpm but the default option the downloader gives me is to
> remove the software, and I select save as.
>
> Now, I have an Opera rpm for opensuse but I’m a bit at loss: Normally,
> I’d expect the software to be adapted so that upgrades follow the suse
> repositories. That seems not to be the case.
>
> So my question:
>
> Do I install the latest Opera and remain safe according to them or do I
> ignore the upgrade message?
>
>
Better to wait for upgrade through the repos
Well I downloaded opera-12.16-1860.x86_64 (.rpm) and the version I have is
(About Opera) Version information
Version 12.15 Build 1748
Platform Linux System x86_64, 3.11.6-4-desktop
I know that.
But I thought, opera from the openSUSE package would not even check if there’s a newer version available.
And as I said, my Opera 12.15 doesn’t notify me of a newer version 12.16.
I now found this in the package’s changelog:
* Fri Feb 01 2013 idonmez@suse.com- Remove update checker application since we don't need it.
This removes the curl dependency as a bonus.
And openSUSE’s package has this in the default preferences:
[User Prefs]
Disable Opera Package AutoUpdate=1
And the package contains a file /usr/share/doc/opera/README.openSUSE with the following content:
Automatic update notification was disabled in order to let
system package manager take control of updating opera.
The system-wide control file is located in /etc/operaprefs_fixed.ini
System administrator can edit it according to their own rules.
See also:
http://www.opera.com/support/usingopera/operaini/
http://www.opera.com/support/mastering/sysadmin/
So is your installed opera package really from openSUSE’s non-oss repo?
rpm -qi opera
If you installed it manually from opera’s home page, you also have to install the updates manually.
Okay, I checked. The opera installed with 13.1 is version 12.15. When I run it, there’s a message telling me to upgrade to 12.16
My own plan – I will wait for an update to come through the regular repos. Unless I run opera as root (and I don’t), the security risk in linux is small enough that I won’t be panicking.
I’m really wanting to see the new webkit based version of opera, but that does not exist for linux.
Name : opera
Version : 12.15
Release : 2.1.6
Architecture: x86_64
Install Date: Sun 24 Nov 2013 05:14:45 PM CET
Group : Productivity/Networking/Web/Browsers
Size : 44701154
License : SUSE-NonFree
Signature : RSA/SHA256, Mon 14 Oct 2013 01:17:58 PM CEST, Key ID b88b2fd43dbdc284
Source RPM : opera-12.15-2.1.6.nosrc.rpm
Build Date : Mon 14 Oct 2013 01:17:05 PM CEST
Build Host : cloud118
Relocations : (not relocatable)
Packager : http://bugs.opensuse.org
Vendor : openSUSE
URL : http://www.opera.com/
Summary : Opera Web Browser (12.15 build 1748)
Description :
Opera is user-friendly, secure, and exceptionally fast. The browser is
small, yet full-featured and functions well on systems with limited
resources. Opera supports all common Web standards and implements them
according to the official recommendations.
Distribution: openSUSE 13.1
OK, I think I found out.
I still have my old configuration around (years old). If I remove .opera/operaprefs.ini I get the message as well.
So apparently that disabling of the update check doesn’t work anymore, but I still have it disabled in operaprefs.ini from times when that worked… (I don’t think I disabled it on purpose)
1/ I installed fresh today - a more virgin system is not possible
2/ I had only a few updates but I checked and the system is completely updated
3/ I installed the version of Opera with Yast in that state
4/ The first time I started Opera I had said message.
5/ Since then, I started Opera a few times. I don’t get that message anymore but I didn’t upgrade.
So I guess it’s a one time ‘bug’ and I’ll do nothing about it.
OK, so maybe the openSUSE config does work, but there’s a glitch in Opera that it does check for updates on first start (i.e. when there’s no user config) never-the-less?
Nothing openSUSE can fix anyway, since Opera is closed-source. The package contains Opera as you can download from the website with just that config file /etc/operaprefs_fixed.ini as I posted before (and the README.openSUSE) and /usr/lib/opera/opera_autoupdatechecker removed.
A question that remains unanswered is why one would hold the update back since eventually the closed version is published unaltered. There is the branding of the rpm, but else?
The package maintainer has to realize there is an update.
Then he submits it to the Maintenance repo, where it will be reviewed and tested.
Then it will be released as online update after some time.