The connection between Yast and zypper in regards to software

Ok guys, to my understanding, Yast uses a gui front end for zypper?
I have placed some ‘do not modify’ tags on some software, in Yast. If i do a zypper up, will it take into account my ‘do not modify’ tags?

knightron wrote:

>
> Ok guys, to my understanding, Yast uses a gui front end for zypper?
> I have placed some ‘do not modify’ tags on some software, in Yast. If i
> do a zypper up, will it take into account my ‘do not modify’ tags?
>
>
> –
> knightron
> ------------------------------------------------------------------------
> knightron’s Profile: http://forums.opensuse.org/member.php?userid=66344
> View this thread: http://forums.opensuse.org/showthread.php?t=474181

Yes.
It will honour those settings

As far as I can tell, zypper should recognize these same locks. I find this:

Zypper is a command line package manager, which makes use of libzypp, providing functions like repository access, dependency solving, package installation, etc.
YaST2 and RPM MetaData package repositories are supported. Zypper repositories are similar to the ones used in YaST, which also makes use of libzypp. Zypper can also handle repository extensions like patches, patterns and products.

AND

Package locks

locks or ll addlock or al removelock or rl cleanlocks or cl

Package locks serve the purpose of preventing changes to the packages on the system. Packages matching an active lock can’t change their installed status; installed packages can’t be removed or upgraded, packages not yet installed can’t be installed.

To lock all packages starting with ‘yast2’, do:

# zypper al 'yast2*'

Reading installed packages…
Specified lock has been successfully added.

Again beware of shell expansion, use quotes if there is a possibility that yast* will match some files or directories in the working directory.

To list currently active locks:

# zypper ll
# | Name             | Type    | Repository
--+------------------+---------+-----------
1 | libpoppler3      | package | (any)
2 | libpoppler-glib3 | package | (any)
3 | yast*            | package | (any)

To remove a lock, do:

# zypper rl yast2-packager

Reading installed packages…
The following query locks some of the objects you want to unlock:

type: package
match_type: glob
case_sensitive: on
solvable_name: yast2*
Do you want remove this lock? [YES/no]: y
Lock count has been succesfully decreased by: 1

Other examples:

zypper al zypper # lock package 'zypper' (exact match) zypper al -r repo-oss virtualbox* # restrict the lock to 'repo-oss' repository (allowing installation from others) zypper rl 3 # remove lock by number

You can manipulate the locks also by directly editing the locks file.

I found this at the following site, less the quotes.

"http://en.opensuse.org/SDB:Zypper_usage#Package_management"

So I think it looks good for what you want.

Thank You,

Thanks guys, found my issue. i’d missed some of the packages.

Happy to help knightron and good to hear you discovered the problem.

Thank You,

On 2012-04-07 05:26, knightron wrote:
>
> Ok guys, to my understanding, Yast uses a gui front end for zypper?

No, but both use the same libraries for the actual package management.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)