You are not logged in.

#1 2020-04-13 03:09:41

BobCollins
Member
From: Silicon Valley
Registered: 2019-06-13
Posts: 6

[SOLVED] Today's annoucement on manual intervention when upgrading nss

I read the announcement:  nss>=3.51.1-1 and lib32-nss>=3.51.1-1 updates require manual intervention

I checked my installed packages: I had nss installed, but not lib32-nss.

I tried a blind upgrade: 

pacman -Syu

    I got the expected error on nss.

I then tried the alternative in the announcement: 

pacman -Syu --overwrite /usr/lib\*/p11-kit-trust.so

   I got the same error again ???

I stared at the command and tried this: 

pacman -Syu --overwrite /usr/lib/p11-kit-trust.so

   It then proceeded to complete the install, including a change to the link.

QUESTIONS:

Why did the first (given) command fail and my revised command (appear to) succeed?

Is what I did correctly install the package?

Thanks!

Last edited by BobCollins (2020-04-13 04:00:17)

Offline

#2 2020-04-13 03:36:15

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,520
Website

Re: [SOLVED] Today's annoucement on manual intervention when upgrading nss

What you did was fine given that you don't have the lib32 version installed.  The cause of the first one's failure would most likely be due to unusual shell/settings.

What shell do you run?


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2020-04-13 03:43:44

BobCollins
Member
From: Silicon Valley
Registered: 2019-06-13
Posts: 6

Re: [SOLVED] Today's annoucement on manual intervention when upgrading nss

I was using bash without any shell configuration changes that I can remember.

Do you have any idea what shell setting would have affected the command?

Offline

#4 2020-04-13 03:50:45

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,520
Website

Re: [SOLVED] Today's annoucement on manual intervention when upgrading nss

My first thought was that if you were using fish or another "exotic" shell it might explain the symptoms.  In bash, there are settings that affect globbing, but those shouldn't really be relevant as the purpose of the command was to use the backslash to escape the asterisk to prevent globbing by the shell - I don't know off hand of any settings that would bypass this.

You're sure there was no typo or copy/paste error?


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#5 2020-04-13 03:59:14

BobCollins
Member
From: Silicon Valley
Registered: 2019-06-13
Posts: 6

Re: [SOLVED] Today's annoucement on manual intervention when upgrading nss

Trilby wrote:

You're sure there was no typo or copy/paste error?

BINGO! I just checked the command history and I found I had made an error. I had a "forward" slash between "lib" and "\*".

Thank you for your time!

Offline

Board footer

Powered by FluxBB