Reinstalling/Downgrading Packages in YaST, Previous Version not found?

English Applications
1

Hello All,

I want to start by saying this is a slightly older laptop, which is running OpenSuSE 11.4 i586. So I know it’s an older/obsolete OS, but for the time being I cannot upgrade the laptop OS.

So I had been having issues with the Firefox Version I WAS running, which was version –> Firefox-esr 31.5.0-1.1. Where whenever I wanted to confirm a Securtity Exception for a internal site I was going to, nothing would happen if I clicked ok when the Permanently checkbox was checked. If I unchecked it I could then click ok and continue…

So today I decided to check YaST Software Manager to see if any updates were available for Firefox, and there was. The new Version that was available was 31.7.0-1.2. And I had also seen that just the plain old MozillaFirefox package was available for the same version. So not remembering why I had installed ESR in the first place I decided to update the MozillFirefox package instead of the esr one, which when I click ok to install it it removed esr and install the regular Firefox.

Also, just before I could upgrade Firefox it said I needed some updated NSS packages. So before I did the Firefox Update, I installed the needed NSS packages, which were ALL in version 3.17.4-1.1. The NSS packages udated to version 3.19.2-1.1. Then, after those completed I ran the actual browser update.

After I updated all the packages and started up Firefox I attempted to go to an internal https site in my work’s network. And when I do I get this error message below and I cannot do anything else…

Secure Connection Failed

An error occurred during a connection to 192.168.11.8. SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.

So I Googled that error and found out that it is probably a bug in the NSS versions I installed… So since this is the newest versions I have available in Software Manager my only choice was to dowgrade back to the original versions prior to installing any of the stuff I installed today.

But, when I check Software Manager those versions are not showing under the Versions section of each package. And I thought I remember if you just right-click on the package and choose Remove that it would reinstall the original version before the most recent update, but when I try to do this to any of the NSS packages I just get a huge LONG list of packages that will break if I continue…

***SEE ATTACHED SCREENSHOTS… **I took screenshots of the Summary of Changes page just before I updated the NSS packages and the Firefox Package. So if you look at those you’ll see what was actually updated. The NSS Packages were: libfreebl3, libsoftokn3, mozilla-nss, mozilla-nss-devel, mozilla-nss-certs and mozilla-nss-sysinit.

So I’m kind of stuck here and don’t know what to do now… Can anyone give me some advice?
Is there anyway to revert/undo any packages recently installed…?

Thanks in Advance,
Matt

2

Switch to Evergreen;
https://en.opensuse.org/openSUSE:Evergreen

It’s 11.4 with updates - however it’ll end this July but you might be able to get updates from there.

3

On 2015-06-25 21:56, Miuku wrote:
>
> Switch to Evergreen;
> https://en.opensuse.org/openSUSE:Evergreen
>
> It’s 11.4 with updates - however it’ll end this July but you might be
> able to get updates from there.

It ended officially 27 Sep 2014, but even after the announcement they
continued doing updates.

By all means, Matt, add the Evergreen update repositories and apply all
the patches. Don’t downgrade anything.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

4

Hey Miuku and Robin, thanks for the replies, much appreciated!

Ok cool, I remember “Evergreen” stuff a while ago but didn’t know what version it was for… So thanks, Good to know!

The URL below is the only repo I found in the link you posted on the Evergreen page. Is this the one I would want to use? Also, should I disable any of my old Repos before I try updating any packages?

**This is the Repo I found from the link you posted:**http://download.opensuse.org/evergreen/11.4/openSUSE:Evergreen:11.4.repo
Which contains this URL:
http://download.opensuse.org/repositories/openSUSE:/Evergreen:/11.4/standard/

Is that 2nd URL above the one I want to add to my repos?

Thanks Again,
Matt

5

Hey Carlos,

I guess it’s hard to say for sure, but if I don’t downgrade Firefox and the NSS packages back to the version(s) I had, won’t it still do the same thing that it’s currently doing? It looks like the newest version of Firefox in that Evergreen repo is 31.7.0-140.1…

Thanks Again,
Matt

6

Duhhhh… I just realized I forgot to include those screenshots I mentioned in my OP… They’re in this comment below…

This screenshot contains the Packages I checked off when doing the NSS updates, which was the 1st thing I did:http://i1326.photobucket.com/albums/u658/mrm5102/Installing_Mozilla-NSS_Upgrades---Need_these_for_Installing_Firefox_Browser_Update_zpstgxof1ad.png

This screenshot is the actual Summary of Changes when I clicked apply for the NSS Updates:http://i1326.photobucket.com/albums/u658/mrm5102/Installing_Mozilla-NSS_Upgrades---Summary_of_Changes_zpsd05urvid.png

And this last one is the Summary of Changes for the browser:http://i1326.photobucket.com/albums/u658/mrm5102/Installing_Mozilla-Firefox---Summary_of_Changes_zpshqc6g8il.png

7

On 2015-06-25 23:26, mmartin0926 wrote:
>
> Hey Miuku and Robin, thanks for the replies, much appreciated!
>
> Ok cool, I remember -“Evergreen”- stuff a while ago but didn’t know what
> version it was for… So thanks, Good to know!
>
> The URL below is the only repo I found in the link you posted on the
> Also, should I
> disable any of my old Repos before I try updating any packages?

No.

If in doubt, just post your repo list - the output of the command “zypper lr --details”, inside a code tags section; the ‘#’ button on the forum editor.

> This is the Repo I found from the link you
> posted:
> http://tinyurl.com/d27mz4l
> Which contains this URL:
> http://tinyurl.com/a8exgah

Yes.

just run this command:


sudo zypper ar --refresh -r http://download.opensuse.org/evergreen/11.4/openSUSE:Evergreen:11.4.repo

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

8

On 2015-06-25 23:26, mmartin0926 wrote:

> Hey Carlos,
>
> I guess it’s hard to say for sure, but if I don’t downgrade Firefox and
> the NSS packages back to the version(s) I had, won’t it still do the
> same thing that it’s currently doing? It looks like the newest version
> of Firefox in that Evergreen repo is 31.7.0-140.1…

Yes, but it is the long term support version of it. If you look at the
timestamps, it was updated last May.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

9

Ok gotcha, thanks Carlos!

Alright I added the Repo Using your Zypper command and here is the list of Repos that I have after adding that Evergreen repo:

mmartin:/home/mmartin # zypper lr --details
#  | Alias                            | Name                                                     | Enabled | Refresh | Priority | Type   | URI                                                                                                     | Service
---+----------------------------------+----------------------------------------------------------+---------+---------+----------+--------+---------------------------------------------------------------------------------------------------------+--------
 1 | New_Mozilla_Repo                 | New Mozilla Repo                                         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/mozilla/openSUSE_11.4/                                        |        
 2 | Nvidia                           | Nvidia                                                   | No      | No      |   99     | rpm-md | http://download.opensuse.org/repositories/home:/Kieltux:/nvidia/openSUSE_Evergreen_11.4_standard/       |        
 5 | SUSE_Standard                    | SUSE Standard                                            | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/11.4:/Contrib/standard/                             |        
 6 | Updates-for-openSUSE-11.4-11.4-0 | Updates for openSUSE 11.4 11.4-0                         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/11.4/                                                               |        
 9 | openSUSE-11.4-11.4-0             | openSUSE-11.4-11.4-0                                     | Yes     | No      |   99     | yast2  | cd:///?devices=/dev/disk/by-id/ata-TSSTcorp_DVD+_-RW_TS-U633J_R8706GVB115453,/dev/sr0                   |        
11 | openSUSE_11.4_Update             | Official released updates for openSUSE 11.4 (standard)   | Yes     | No      |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/11.4:/Update/standard/                              |        
12 | openSUSE_Evergreen_11.4          | Evergreen update repository for openSUSE 11.4 (standard) | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Evergreen:/11.4/standard/                           |        
13 | repo-debug                       | openSUSE-11.4-Debug                                      | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/11.4/repo/oss/                                          |        
14 | repo-debug-update                | openSUSE-11.4-Update-Debug                               | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/11.4/                                                         |        
15 | repo-non-oss                     | openSUSE-11.4-Non-Oss                                    | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.4/repo/non-oss/                                            |        
16 | repo-oss                         | openSUSE-11.4-Oss                                        | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.4/repo/oss/                                                |        
17 | repo-source                      | openSUSE-11.4-Source                                     | No      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/11.4/repo/oss/                                         |

Sorry it’s a little hard to read, I figured the CODE tags would prevent Word Wrap and add in a horizontal scroll-bar, but I guess not…

If you go to the 2 Repos labeled, “openSUSE_11.4_Update” and “Updates-for-openSUSE-11.4-11.4-0” in a browser, BOTH redirect you to the same URL, which is → http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.4/…

Thanks Again,
Matt

10

Ah, then the wiki has it listed wrong - it says July 2015.

11

I am going to backup my HDD tonight so tomorrow I can run the updates.

How should I go about doing the updates* → YaST Software Manager, Online Update, or Zypper…?

**1. **At the moment I have a red Icon with a exclamation point in the Notification bar *(*I think its the “Online Update” program) *that shows “There are 206 Updates Available”. This Icon may have already been showing before I added the Evergreen repo so I’m not sure that number is correct…

**2. **YaST > Software Manager, this shows there are 218 Updates.

**3. **And running the **zypper **command below shows 206 Updates. I think with the -r option I am able to specify to only use that specific repo.


# zypper lp -r "openSUSE_Evergreen_11.4" | wc -l
206

What is the best way of performing these updates? Also, there are Kernel Updates as well, I assume I’ll want to do these updates too? I remember the last time I updated a Kernel, the old Kernels were left in /boot and completely filled up my */boot *partition…

Thanks Again,
Matt

12

If you have a separate boot and did not allow enough room yes there could be a problem. I think 11.4 did the trick of multiple kernels. This is good in so much it allows dropping back if a new kernel seriously breaks things. And I do recommend it. But since you have insufficient room you should turn the feature off.

In
/etc/zypp/zypp.conf

find line with multiversion in it should be some instructions near it

If you have problem though you don’t have a convenient fall back

13

On 2015-06-26 00:46, mmartin0926 wrote:
>
> I am going to backup my HDD tonight so tomorrow I can run the updates.
>
> How should I go about doing the updates- → *YaST Software Manager,
> Online Update, or Zypper…?-

Ok, before that. I see that you have a repo for “New_Mozilla_Repo”. I
don’t think you need that one. I think what you get there is the same
version as in the update repo (evergreen), but some days or weeks
earlier, for people that want to do some testing. I think that you
should disable it.

> What is the best way of performing these updates? Also, there are Kernel
> Updates as well, I assume I’ll want to do these updates too? I remember
> the last time I updated a Kernel, the old Kernels were left in /boot and
> completely filled up my -/boot -partition…

I think that you simply should use yast online update (aka YOU), which
does the same as “zypper patch”. There should be a ton of updates, since
you didn’t have the evergreen repo, which has been active many months (2
years?).

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

14

On 2015-06-26 00:36, Miuku wrote:
>
> robin_listas;2716911 Wrote:
>> It ended officially 27 Sep 2014, but even after the announcement they
>> continued doing updates.
> Ah, then the wiki has it listed wrong - it says July 2015.

Maybe not. Maybe they extended maintenance, and they have not sent an
official notice (an email to the security-announce mail list, which is
where these things are announced since… who knows, my archive goes
back to 2002 :wink: and I see them there).

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

15

On 2015-06-26 01:56, gogalthorp wrote:
>
> If you have a separate boot and did not allow enough room yes there
> could be a problem. I think 11.4 did the trick of multiple kernels. This
> is good in so much it allows dropping back if a new kernel seriously
> breaks things. And I do recommend it. But since you have insufficient
> room you should turn the feature off.

Or verify how much free space is in there no, and if not enough for
another kernel, remove the oldest one.

Let me see…


rpm -qa | grep -i kernel
df -h /boot

That will tell us if preventive action is required :wink:

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

16

Hey Guys, thank you again for the replies!!

Carlos
Ok, before that. I see that you have a repo for “New_Mozilla_Repo”. I don’t think you need that one. I think what you get there is the same version as in the update repo (evergreen), but some days or weeks earlier, for people that want to do some testing. I think that you should disable it.

Ok no problem, I have disabled that Mozilla Repo…

After I disabled that repo, I went to YaST** > Online Update**. Once that loaded I got a pop-up with some Conflicts, which are shown below:*Since the pop-up window containing the Conflicts could not be Copied/pasted I took screenshots. It only took 3 screenshots to get the whole thing, see below…
Screenshot #1: YaST-Online-Update_Conflicts_1
**Screenshot #2: YaST-Online-Update_Conflicts_2
Screenshot #3: **YaST-Online-Update_Conflicts_3

Anyidea what I should choose for those conflicts…?

gogalthorp
If you have a separate boot and did not allow enough room yes there could be a problem. I think 11.4 did the trick of multiple kernels. This is good in so much it allows dropping back if a new kernel seriously breaks things. And I do recommend it. But since you have insufficient room you should turn the feature off.

Actually, I forgot that when I swapped out my Original internal HDD for a SSD drive a few months ago, I resized a few of the partitions *(*with GParted) *when I recreated the Hard Drive and the /boot partition was one of them. Originally it was only about 100 MB. But, when I did the new SSD drive I double the /boot partition to 200 MBs. So I think I should be good… Since there is probably enough room in /boot now, I assume I should keep that Kernel feature on…?

Carlos
Or verify how much free space is in there no, and if not enough for
another kernel, remove the oldest one.

Let me see…

 Code:

rpm -qa | grep -i kernel
df -h /boot

That will tell us if preventive action is required :wink:

Ok here is the output from the above commands:


# rpm -qa | grep -i kernel
kernel-devel-2.6.37.6-0.20.1.noarch
kernel-default-2.6.37.6-0.20.1.i586
kernel-desktop-base-2.6.37.6-0.20.1.i586
kernel-default-base-2.6.37.6-0.20.1.i586
kernel-source-2.6.37.6-0.20.1.noarch
kernel-firmware-2.6.38-1.2.1.noarch
kernel-default-devel-2.6.37.6-0.20.1.i586

# df -h /boot
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5             175M   51M  116M  31% /boot

Looks like maybe there are still some Kernels in there from the last time I upgraded…

If I check in /boot/grub/menu.lst I see the following entries for the Kernels which are avaiable to boot to:

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.4 - 2.6.37.6-0.20 (default)
    root (hd0,4)
    kernel /vmlinuz-2.6.37.6-0.20-default root=/dev/disk/by-id/ata-Samsung_SSD_840_EVO_500GB_S1DHNSAF761577P-part7 resume=/dev/disk/by-id/ata-Samsung_SSD_840_EVO_500GB_S1DHNSAF761577P-part6 splash=silent quiet showopts vga=0x314
    initrd /initrd-2.6.37.6-0.20-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.20 (default)
    root (hd0,4)
    kernel /vmlinuz-2.6.37.6-0.20-default root=/dev/disk/by-id/ata-Samsung_SSD_840_EVO_500GB_S1DHNSAF761577P-part7 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x314
    initrd /initrd-2.6.37.6-0.20-default

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.4 - 2.6.37.6-0.20
    root (hd0,4)
    kernel /vmlinuz-2.6.37.6-0.20-desktop root=/dev/disk/by-id/ata-Samsung_SSD_840_EVO_500GB_S1DHNSAF761577P-part7 resume=/dev/disk/by-id/ata-Samsung_SSD_840_EVO_500GB_S1DHNSAF761577P-part6 splash=silent quiet showopts vga=0x314
    initrd /initrd-2.6.37.6-0.20-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.20 (desktop)
    root (hd0,4)
    kernel /vmlinuz-2.6.37.6-0.20-desktop root=/dev/disk/by-id/ata-Samsung_SSD_840_EVO_500GB_S1DHNSAF761577P-part7 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x314
    initrd /initrd-2.6.37.6-0.20-desktop

###Don't change this comment - YaST2 identifier: Original name: windows 1###
title Windows 7
    rootnoverify (hd0,1)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: windows 2###
title Windows Recovery
    rootnoverify (hd0,2)
    chainloader +1

So it looks like basically only the default and desktop Kernels are used…*i.e. vmlinuz-2.6.37.6-0.20-default --and-- vmlinuz-2.6.37.6-0.20-desktop

Thanks AGAIN for the help guys, very much appreciated!!

Thanks,
Matt

17

You should not have multiple flavour kernels unless you have a special needs. It is known that an update while you have incorrect NVIDIA drivers may pull in other (notable default) drivers. Remove the the default unless you have some special need for it. If not deep six it.

On closer look it looks like maybe you use default and that desktop is the incorrect one??? Normally desktop is the one used. Also -base is not needed and should not be installed.

Ok forget the above. You have a mess and short of uninstalling all them kernels and install the correct desktop flavour I’m unsure on how to proceed. And adding that old out of date OS???

18

Yea, I’m a bit confused myself… No sure why I have “Extra” Kernels in there other then maybe accidentaly checking something when using Software Manager or something like that… I was a bit of a NOOB when I first started with this OpenSuSE 11.4 OS.

This is what is in my /boot partition:


# ll /boot
total 45277
-rw-r--r--    1    root    root    1634997     Jun 15    2012    System.map-2.6.37.6-0.20-default
-rw-r--r--    1    root    root    1782652     Jun 15    2012    System.map-2.6.37.6-0.20-desktop
-rw-------    1    root    root    512             May 11    2011    backup_mbr
lrwxrwxrwx  1    root    root    1                 Apr 11    2012    boot    ->    .
-rw-r--r--    1    root    root    1236           Feb 21    2011    boot.readme
-rw-r--r--    1    root    root    124873       Jun 15    2012    config-2.6.37.6-0.20-default
-rw-r--r--    1    root    root    122384       Jun 15    2012    config-2.6.37.6-0.20-desktop
drwxr-xr-x   2    root    root    1024          Jun 8    15:03     grub
lrwxrwxrwx  1    root    root    28              Aug 24    2012    initrd    ->    initrd-2.6.37.6-0.20-default
-rw-r--r--    1    root    root    11065390  Aug 24    2012    initrd-2.6.37.6-0.20-default
-rw-r--r--    1    root    root    10341289  Aug 24    2012    initrd-2.6.37.6-0.20-desktop
drwx------   2    root    root    12288        May 11    2011    lost+found
-rw-r--r--    1    root    root    547840      May 17    2011    message
-rw-r--r--    1    root    root    562916      Jun 15    2012    symtypes-2.6.37.6-0.20-default.gz
-rw-r--r--    1    root    root    199486      Jun 15    2012    symvers-2.6.37.6-0.20-default.gz
-rw-r--r--    1    root    root    195402      Jun 15    2012    symvers-2.6.37.6-0.20-desktop.gz
-rw-r--r--    1    root    root    173299      Nov 4    2014      v
-rw-r--r--    1    root    root    5123288    Jun 15    2012    vmlinux-2.6.37.6-0.20-default.gz
-rw-r--r--    1    root    root    5740638    Jun 15    2012    vmlinux-2.6.37.6-0.20-desktop.gz
lrwxrwxrwx  1    root    root    29              Aug 24    2012    vmlinuz    ->    vmlinuz-2.6.37.6-0.20-default
-rw-r--r--    1    root    root    4017536    Jun 15    2012    vmlinuz-2.6.37.6-0.20-default
-rw-r--r--    1    root    root    4510304    Jun 15    2012    vmlinuz-2.6.37.6-0.20-desktop

I guess I’ll hold-off running Online Update for the moment…

Thanks,
Matt

19

UPDATE:
Well… This doesn’t fix the whole Online Update thing, but I was able to get those internal HTTPS sites working again…

In Software Manager I found the Evergreen Repo had a version of Firefox really really close to what I had before I updated it the other day. So I removed the current version of Firefox-esr 31.7.xx that I had and then installed the version of MozillaFirefox that was very close to my previous version, which is now 31.5.3.

After that I re-opened Firefox and attempted to go to one of those pages, but I still got that Error message and couldn’t continue… So I went back to Software Manager and intalled the Mozilla NSS versions of 3.17.3… Then I restarted Firefox and attempted one of those pages again, and viola it’s working again.!

*Back to the Kernel issue…

So in this screenshot below, couldn’t I just uninstall the one’s I don’t need using Software Manager? I believe all of the one’s from the previous "rpm -qa*"* command are shown in this screenshot.

http://i1326.photobucket.com/albums/u658/mrm5102/YaST_Software-Manager---Kernel_Search_zpsvraokqnl.jpg](http://s1326.photobucket.com/user/mrm5102/media/YaST_Software-Manager---Kernel_Search_zpsvraokqnl.jpg.html)

If that sounds like something you guys think I can do safely from the Software Manager, just let me know and I’ll remove the one’s I don’t need. Speaking of the one’s I don’t need, would I just need to keep the Default and Desktop ones? I know you really only “need” one, but just to be safe, since default and desktop are what’s configured in GRUB *(*which I posted a couple posts back if you need to see what’s in GRUB)…
*Would that be ok?

Thanks Again,
Matt

20

On 2015-06-27 00:26, mmartin0926 wrote:

> So in this screenshot below, couldn’t I just uninstall the one’s I don’t
> need using Software Manager? I believe all of the one’s from the
> previous -“rpm -qa–”- command are shown in this screenshot.
>
> ‘[image:
> http://i1326.photobucket.com/albums/u658/mrm5102/YaST_Software-Manager---Kernel_Search_zpsvraokqnl.jpg]’
> (http://tinyurl.com/nw5vneu)

You want to remove linux-glibc-devel, openSUSE-release, and
virtualbox-4.1? I don’t see what for; and removing openSUSE-release
would possibly in turn trigger removal of about the entire Linux.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))