Results 1 to 6 of 6

Thread: The connection between Yast and zypper in regards to software

  1. #1
    Join Date
    Feb 2012
    Location
    Australia
    Posts
    142

    Default 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?

  2. #2
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: The connection between Yast and zypper in regards to software

    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

  3. #3
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Smile Re: The connection between Yast and zypper in regards to software

    Quote Originally Posted by knightron View Post
    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?
    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:

    Code:
    # 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:

    Code:
    # zypper ll
    Code:
    # | Name             | Type    | Repository
    --+------------------+---------+-----------
    1 | libpoppler3      | package | (any)
    2 | libpoppler-glib3 | package | (any)
    3 | yast*            | package | (any)
    To remove a lock, do:

    Code:
    # zypper rl yast2-packager
    Reading installed packages...
    The following query locks some of the objects you want to unlock:

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

    Code:
    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.

    Code:
    "http://en.opensuse.org/SDB:Zypper_usage#Package_management"
    So I think it looks good for what you want.

    Thank You,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  4. #4
    Join Date
    Feb 2012
    Location
    Australia
    Posts
    142

    Default Re: The connection between Yast and zypper in regards to software

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

  5. #5
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Default Re: The connection between Yast and zypper in regards to software

    Quote Originally Posted by knightron View Post
    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,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  6. #6
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: The connection between Yast and zypper in regards to software

    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)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •