Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Newbie question re patching Leap / keeping Leap up-to-date

  1. #11

    Default Re: Newbie question re patching Leap / keeping Leap up-to-date

    Quote Originally Posted by Tuner View Post
    Just like Tumbleweed, but without the critical 'd' in front of the 'up.'
    Indeed.
    There is absolutely no difference between "zypper up" and "zypper dup" in *this* regard (i.e. refreshing the repos)...

  2. #12
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    3,974

    Default Re: Newbie question re patching Leap / keeping Leap up-to-date

    Quote Originally Posted by Tuner View Post
    Thank you for the feedback, Henk, Sauerland, dcurtisfra and wolfi323!

    My impression from reading these threads is that:

    Code:
    zypper ref; zypper up
    (and emphatically not zypper dup)

    ... should cover all bases for me. The zypper ref might not be necessary, but won't hurt.

    If you disagree, please let me know!
    I simply use
    Code:
    zypper up
    Does everything desired, has since the stone age.
    -Gerry Makaro
    Fraser-Bell Info Tech
    Solving Tech Mysteries since the Olden Days!
    ~~
    If I helped you, consider clicking the Star at the bottom left of my post.

  3. #13
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,972

    Default Re: Newbie question re patching Leap / keeping Leap up-to-date

    As @Fraser_Bell (and I above) said, many simply use
    Code:
    zypper up
    It will include zypper ref, except when it was already done (either by itself or by inclusion) in another zypper/YaST action a short time (I think 10 minutes) ago. That will save time and you would only force a new zypper ref in such a short time span if you think new software is published within that time span.

    But we are now jumping into all sorts of personal preferences, where it is up to you to do what you like most.

    E.g. many would like to change your suggestion into
    Code:
    zypper ref && zypper up
    because then the second command will only run when the first finished successful.

    Personal, while doing a lot with the CLI, I am a YaST fan for many things, including using YaST > Software > Online Update (the equivalent of zypper patch), because I then see short descriptions about what the security and recommended updates are for. I can then still deselect some (which I btw almost never do).
    I have only one extra repo: Packman. And for that I use YaST > Software > Software Management > View > Repositories. Then select Packman and do the "Update if a newer version is available". Again by, after that selection, clicking on Installation Summary, I can see what will be done. Gives me a feeling of being the boss.
    Henk van Velden

  4. #14
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,869

    Default Re: Newbie question re patching Leap / keeping Leap up-to-date

    Quote Originally Posted by wolfi323 View Post
    And even if you do have PackageKit installed, it will not periodically refresh the repos. (unless you are running some frontend/applet that does it, or you explicitly enable that cron job)
    Going back to Wolfi323's explanation and, taking the KDE Plasma 5 case with the "plasma5-pk-updates" package installed -- the KDE Software Manager (PackageKit) plasmoid:
    AFAICS from the package source and, from personal experience with a Laptop with WLAN, the plasmoid checks for:

    1. isNetworkOnline
    2. isNetworkMobile
    3. isOnBattery

    Also, I seem to remember that, the KDE plasmoid was recently modified to only check once per day (once every 86 400 seconds) for updates.

    The thought is, is there a "doing things twice" conflict here between the KDE plasmoid and "zypp"?

    • "zypp" is checking all repositories which have "autorefresh" enabled for updates once every "repo.refresh.delay" minutes.
    • The KDE Software Manager plasmoid is checking for updates once a day.


    I'll be checking the Laptop's behaviour over the next few weeks with the (zypp) "autorefresh" of all the repositories disabled.

  5. #15

    Default Re: Newbie question re patching Leap / keeping Leap up-to-date

    Quote Originally Posted by dcurtisfra View Post
    Also, I seem to remember that, the KDE plasmoid was recently modified to only check once per day (once every 86 400 seconds) for updates.
    It additionally checked on every login in the past (i.e. when it got "started"), but this got fixed for 42.2.

    The thought is, is there a "doing things twice" conflict here between the KDE plasmoid and "zypp"?
    Why should it conflict?
    There is only *one* package management system underneath, that all other options use.


    "zypp" is checking all repositories which have "autorefresh" enabled for updates once every "repo.refresh.delay" minutes.
    No, it does *not* check anything automatically (or once every xxx minutes) at all.

    It will only refresh repos if you actually run something like "zypper up".



    IMHO, you are making it much more complicated than it is.
    The point is: repos are refreshed automatically whenever *something* checks for updates.

    (unless auto-refresh is disabled for a repo)

  6. #16
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,869

    Question Re: Newbie question re patching Leap / keeping Leap up-to-date

    Quote Originally Posted by wolfi323 View Post
    No, it does *not* check anything automatically (or once every xxx minutes) at all.
    Given that the KDE Software Manager (PackageKit) plasmoid is indicating "Last update 22 hours ago" and no updates pending, this "zypper search" output seems to be indicating that, ZYpp has found some changes in the repositories flagged with 'autorefresh':
    Code:
     > LANG=C zypper search fdhgd
    Repository 'openSUSE BuildService - PHP:Applications' is out-of-date. You can run 'zypper refresh' as root to update it.
    Repository 'Aktualisierungs-Repository (DEBUG)' is out-of-date. You can run 'zypper refresh' as root to update it.
    Repository 'Hauptaktualisierungs-Repository' is out-of-date. You can run 'zypper refresh' as root to update it.
    Repository 'openSUSE Virtualization' is out-of-date. You can run 'zypper refresh' as root to update it.
    Repository 'Packman Repository' is out-of-date. You can run 'zypper refresh' as root to update it.
    Loading repository data...
    Reading installed packages...
    No matching items found.
     >
    My interpretation of the comment text in /etc/zypp/zypp.conf related to "repo.refresh.delay" and the "Refresh" section of the "zypper" (8) man page is:
    • If, there were no zypper commands issued within the last "repo.refresh.delay" minutes then, the indexes of repositories will be checked for any changes made since the last "zypper refresh".
    • If, any zypper commands are issued within "repo.refresh.delay" minutes of the last zypper command which checked the repositories for changes then, the repositories will ** NOT ** be checked again.
    • This behaviour also applies to "zypper update" and "zypper patch" despite the intrinsic behaviour that these two commands execute a "zypper refresh" before attempting to apply either the pending patches and/or updates.

    In other words, if you apply "no" to "zypper update" and then, wait at least 10 minutes before re-executing "zypper update", another implicit "zypper refresh" will be performed.

    Question: is this interpretation correct?

  7. #17

    Default Re: Newbie question re patching Leap / keeping Leap up-to-date

    Quote Originally Posted by dcurtisfra View Post
    Given that the KDE Software Manager (PackageKit) plasmoid is indicating "Last update 22 hours ago" and no updates pending
    That has nothing to do with when the repos have been refreshed the last time.
    It just means what it says, that the update applet checked for updates 22 hours ago (which of course did refresh the repos as well).

    this "zypper search" output seems to be indicating that, ZYpp has found some changes in the repositories flagged with 'autorefresh':
    Yes, and as you are running it as user, so it cannot refresh the repos.
    This needs root privileges.

    PackageKit can do it (if it's not disallowed via polkit rules), as it does run as root. (but it is only started if the applet checks for updates)

    Question: is this interpretation correct?
    More or less, yes.

    Except that it doesn't matter whether you ran zypper commands in the last "repo.refresh.delay" minutes or not, only when the repos actually have been refreshed the last time (you could also have run YaST->Software Management e.g.).
    Last edited by wolfi323; 24-Jan-2018 at 05:15.

Page 2 of 2 FirstFirst 12

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
  •