Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.suse    |    Suse is actually not that bad    |    138,051 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 137,355 of 138,051    |
|    Carlos E. R. to Paul R Schmidtbleicher    |
|    Re: Locking Software from Updates    |
|    13 Oct 21 07:26:58    |
      From: robin_listas@es.invalid              On 13/10/2021 02.56, Paul R Schmidtbleicher wrote:       > On Tue, 12 Oct 2021 22:39:47 +0200, Carlos E. R. wrote:       >       >> On 12/10/2021 18.39, Paul R Schmidtbleicher wrote:       >>> This post is dealing specifically with "dosbox" under Tumbleweed. My       >>> earlier version of 0.74.3 works far better with (what used to be)       >>> Geos/Emsemble than the new version 0.77.x. I tried locking my old       >>> version under Yast Software assuming LOCKING could not be overridden       >>> except by me. I do want other Tumbleweed updates, but when I accept       >>> them, they also update "dosbox" even as the "Lock symbol" remains on       >>> it. This is my problem.       >>       >> Not possible. Something else must be going on.       >>       >>       >>> (1) Is there a better answer?       >>> (2) I thought about changing the name of my 0.74.3 version of "dosbox,"       >>> but noticed in the file list given under "Yast Software" that the       >>> executable in /bin isn't even listed. There may be others??? Would       >>> this work or does Yast keep track of name changes and it would still be       >>> updated?       >>       >> No, the packages have names inside.       >>       >>       >> zypper ll       >>       >> should list the locks.       >>       >> And       >>       >> cat /etc/zypp/locks       >       > First: I was using the Yast Graphic Interface of Tumbleweed. I log into       > Tumbleweed. It says, "X Number of Updates." I click install.                     Well, consider this a "forbidden procedure" on Tumbleweed :-P              On tumbleweed you must only use:              zypper dup              everytime. Never "zypper patch" nor "zypper up" or the YaST equivalents.              > In the       > "Yast Software" under "System" I put a "lock" (little padlock) on dosbox.       > This obviously did nothing!       >       > Your "cat etc/zupp/locks" yielded nothing              Did you forget the "/" before etc?              > I tried Malcolm's advise as Superuser: "zypper al dosbox"       > This worked! Thanks       > A second try at "cat /etc/zupp/locks" showed "dosbox" as locked (SUCCESS)              Well, being Tumbleweed, a bug in YaST is possible.              >       > Now, in an effort to understand the MAN Page on zypper please define the       > "al" in the command Malcolm gave me.              al is short of addlock. So just search for that word.               addlock (al) [options] lock-spec...        Add a package lock. Specify packages to lock as explained above.               -r, --repo alias|name|#|URI        Restrict the lock to the specified repository.               -t, --type type        Lock only packages of specified type (default: package).       See section Package Types for list of available package types.                            --       Cheers,        Carlos E.R.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca