Question about zypper updates on TW
I'm on Tumbleweed. Does zypper dup reload the current status of my repositories with newer packages, or do I have to run zypper ref first? Or is that what the man page means by "auto-refresh", and in that case, how do I configure that? The info I found online is conflicting. Wiki says zypper dup is enough, but it also says I get a notification about new packages, which I don't. I'm guessing that's only valid for Leap, but not sure about this either. Thanks.
Op donderdag 25 februari 2021 16:29:25 CET schreef Felix Meessen:
I'm on Tumbleweed.
Does zypper dup reload the current status of my repositories with newer packages, or do I have to run zypper ref first?
Or is that what the man page means by "auto-refresh", and in that case, how do I configure that?
The info I found online is conflicting. Wiki says zypper dup is enough, but it also says I get a notification about new packages, which I don't. I'm guessing that's only valid for Leap, but not sure about this either.
Thanks. Only 'zypper dup' is enough. It triggers the refresh of the repos.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
Am 25.02.21 um 16:33 schrieb Knurpht-openSUSE:
Op donderdag 25 februari 2021 16:29:25 CET schreef Felix Meessen:
I'm on Tumbleweed.
Does zypper dup reload the current status of my repositories with newer packages, or do I have to run zypper ref first?
Or is that what the man page means by "auto-refresh", and in that case, how do I configure that?
The info I found online is conflicting. Wiki says zypper dup is enough, but it also says I get a notification about new packages, which I don't. I'm guessing that's only valid for Leap, but not sure about this either.
Thanks. Only 'zypper dup' is enough. It triggers the refresh of the repos.
If you like to stay a little bit longer on a specific snapshoot, install with yast2: tumbleweed-cli this will gave you a new command "tumbleweed": # tumbleweed Usage: /usr/bin/tumbleweed [options] command [arguments] Options: --version Print version string and exit --force Force on operation to occur regardless of checks. --install Initiate install after command. -h, --help Display this message and exit Commands: init Initialize repos to point to snapshot repos. status Show status information (latest, target, and installed). latest Show latest snapshot available. installed|version Show current installed snapshot. target Show the target of the repositories. list List available snapshots. history List history of snapshots targetted. update|upgrade Switch to and install the latest available snapshot. switch %version Switch to a new snapshot (none for latest). revert Revert to the previous snapshot or repo state. uninit Revert back to a snapshotless repository setup. migrate Migrate from boombatower hosting to download.opensuse.org. unmigrate Revert migration to official hosting. https://review.tumbleweed.boombatower.com/ simoN -- www.becherer.de
* Knurpht-openSUSE <knurpht@opensuse.org> [02-25-21 10:35]:
Op donderdag 25 februari 2021 16:29:25 CET schreef Felix Meessen:
I'm on Tumbleweed.
Does zypper dup reload the current status of my repositories with newer packages, or do I have to run zypper ref first?
Or is that what the man page means by "auto-refresh", and in that case, how do I configure that?
The info I found online is conflicting. Wiki says zypper dup is enough, but it also says I get a notification about new packages, which I don't. I'm guessing that's only valid for Leap, but not sure about this either.
Thanks. Only 'zypper dup' is enough. It triggers the refresh of the repos.
it is provided one has not altered "autorefresh=1" in the repo config. default action is the automagically refresh. I personally prefer it off, autorefresh=0 and I download *all* in advance, zypper -v ref;zypper -v dup -d -l && zypper -v dup -l -y zypper refreshes, shows me relevant file changes, and I accept or deny. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
25.02.2021 19:24, Patrick Shanahan пишет:
* Knurpht-openSUSE <knurpht@opensuse.org> [02-25-21 10:35]:
Op donderdag 25 februari 2021 16:29:25 CET schreef Felix Meessen:
I'm on Tumbleweed.
Does zypper dup reload the current status of my repositories with newer packages, or do I have to run zypper ref first?
Or is that what the man page means by "auto-refresh", and in that case, how do I configure that?
The info I found online is conflicting. Wiki says zypper dup is enough, but it also says I get a notification about new packages, which I don't. I'm guessing that's only valid for Leap, but not sure about this either.
Thanks. Only 'zypper dup' is enough. It triggers the refresh of the repos.
a) it is possible to globally disable automatic refresh b) automatic refresh is suppressed for refresh interval (I think 10 minutes by default), so not every invocation of "zypper dup" will do it. It is possible to hit mirror update in this interval.
On Thu, 2021-02-25 at 16:29 +0100, Felix Meessen wrote:
I'm on Tumbleweed.
Does zypper dup reload the current status of my repositories with newer packages, or do I have to run zypper ref first?
Or is that what the man page means by "auto-refresh", and in that case, how do I configure that?
The info I found online is conflicting. Wiki says zypper dup is enough, but it also says I get a notification about new packages, which I don't. I'm guessing that's only valid for Leap, but not sure about this either.
Thanks.
The automatic refreshing option is enabled on a per-repository basis. You can check which repos on your system auto- refresh by listing the repos and looking at the associated 'refresh' flags. Looking at which repositories have auto- refresh enabled is also possible using yast if you prefer. Usually zypper dup is enough because the base repos have auto-refresh enabled by default, but I think if you add repos manually using zypper (e.g. zypper ar ...) then auto-refresh is not enabled. Best is to first check what the status is on your system and adjust accordingly. You can see that I have all my repositories listed as auto-refreshing below: $ zypper repos Repository priorities in effect: (See 'zypper lr -P' for details) 98 (raised priority) : 3 repositories 99 (default priority) : 19 repositories # | Alias | Name | Enabled | GPG Check | Refresh ---+----------------------------------+-----------------------------------------------+---------+-----------+-------- 1 | code | Visual Studio Code | Yes | (r ) Yes | Yes 2 | devel-scala | devel:languages:scala | Yes | (r ) Yes | Yes 3 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes 4 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes 5 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes 6 | libdvdcss | libdvdcss repository | Yes | (r ) Yes | Yes 7 | packman | Packman Repository | Yes | (r ) Yes | Yes 8 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- 9 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- 10 | science | science | Yes | (r ) Yes | Yes Cheers, Chris
participants (6)
-
Andrei Borzenkov -
Chris Coutinho -
Felix Meessen -
Knurpht-openSUSE -
Patrick Shanahan -
Simon Becherer