I’m running openSUSE Tumbleweed, upgrading all packages every single day. Since several days I’m getting a checksum error on package kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm and now I’m concerned someone could try to push modified packages to my system. That is usually the point where I break up the update. Does anybody else here experience this stuff? What is the recommended procedure when this happens? Wait till nerw packages come out?
On another side-note: How about the security signing-keys of several repositories like the OBS which expire in 12 days from today? Will they be renewed in time or do they change? Is it recommended to trust these keys long-term or just for the time of the update?
In short, apparently some mirror has broken packages at the moment.
Nobody is tying to push modified packages, probably the install would just fail even if you would force it.
On another side-note: How about the security signing-keys of several repositories like the OBS which expire in 12 days from today? Will they be renewed in time or do they change? Is it recommended to trust these keys long-term or just for the time of the update?
I guess they will be renewed in time.
It is your own decision whether you trust them or not, but it doesn’t matter much if you trust them for the time of the update or long-term I’d say.
@hcvv, thanks for moving my thread. With todays update to kdebase4-workspace-branding-openSUSE-13.1-2.10.x86_64.rpm everything worked as expected and I’m back to a normal life without paranoia. Cheers, folks! rotfl!
181 packages to upgrade, 8 new, 8 to change vendor.
Overall download size: 417.9 MiB. After the operation, additional 701.8 MiB will be used.
Continue? [y/n/? shows all options] (y):
Retrieving package kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64 (1/189), 740.7 KiB (839.6 KiB unpacked)
Retrieving: kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm ................................................................................................[error]
File './x86_64/kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/'
Here’s what it says on the factory mailing list from a Jiri slabi
On 04/21/2014 12:45 PM, ellanios82 wrote: Hello List,
in case of interest, i read :
[Tumbleweed|http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/]
Can’t provide file
‘./x86_64/kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm’ from
repository ‘Tumbleweed’
History:
kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm has wrong
checksum
Abort, retry, ignore? [a/r/i] (a): a
I triggered a rebuild. I see it fixed now and you?
–
js
suse labs
and a reply to that from Hendrik Woltersdorf:
Today I was able to install this package and two similar ones (in the
32bit version) without checksum errors.
Thanks,
Hendrik
I saw the other thread about using a tumbleweed backup repo but didn’t fancy that for a work(a)round one bit.
Maybe I just have to wait longer for a mirror near me (NZ) to sync…perhaps,
You’re still trying to install the package version 13.1-2.9, that one does not exists any more in the Tumbleweed repo (there’s only 13.1-2.10 now at the moment).
So it seems your repo cache is outdated.
Try to run “zypper ref” before running “zypper dup”.
If that doesn’t help, you will have to wait I suppose, until the mirror you get redirected to has fully synced.
You do have Auto-refresh enabled for the Tumbleweed repo, I hope?
Hi, I also waited then yesterday (UTC+1) saw the ML post from Jiri, and upgraded without issue. Seems ok so far, and hopefully your mirror will get there.
But the Tumbleweed repo is constantly changing (that’s its purpose, isn’t it?), so you should run “zypper ref” before any other zypper operation.
A refresh is only done when the repo metadata changes, anyway.
And without a metadata refresh, “zypper dup” won’t even see new updates, or you will get such errors that you have seen when trying to install packages.
So I don’t think it makes much sense to have Auto-Refresh disabled for the Tumbleweed repo. But well, it really is your decision in the end…
Of course.
“zypper dup” only automatically refreshes repos for which Auto-Refresh is enabled, obviously.
Like any other zypper command (except “zypper ref”).
Otherwise it relies on its own view of the repos, in the metadata cache.
> Are you saying that “zypper dup” doesn’t automatically apply the state
> of the repositories onto the system i.e it doesn’t always perform a
> refresh?
That’s right. If “automatic refresh” is disabled, there is not automatic
refresh when you call any zypper or yast function that installs,
removes. or updates any package…
It is is obvious.
If you disable “autorefresh”, you are expected to do “manual refreshing”
when needed
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Hmm, I recall you have posted before that “zypper dup” does a refresh (by default) and that doing a “zypper refresh” is therefore unnecessary. Not exactly the same as your last post! Of course most users will retain the distro’s default auto refresh setting for the main repositories, but you shouldn’t rely on it.
> Hmm, I recall you have posted before that “zypper dup” does a refresh
> (by default) and that doing a “zypper refresh” is therefore unnecessary.
> Not exactly the same as your last post! Of course most users will retain
> the distro’s default auto refresh setting for the main repositories, but
> you shouldn’t rely on it.
Yes, if I said that, in that way, it is confusing. Let me try again.
A “zypper dup”, or any zypper/yast operation that does modifications
(and some that do not), include an automatic refresh of those folders
that are marked for automatic refresh.
Thus, in a typical system, as all repos are marked for automatic
refresh, manually doing a “zypper ref” is not necessary.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
“zypper dup” does a refresh by default, on repos that have Auto-Refresh enabled. But only every 10 minutes (by default; this is changeable in /etc/zypp/zypp.conf, option “repo.refresh.delay”). And if the repo hasn’t changed, it doesn’t do a refresh either, because it’s not necessary.
It does not do a refresh for repos that have Auto-Refresh disabled. That’s the whole point of the Auto-Refresh setting.
“zypper refresh” is unnecessary only if you have set the repos to Auto-Refresh. Or for repos that don’t change anyway, like the main OSS and Non-OSS repos.
PS: Oops, I thought you were addressing me.
Sorry.
“zypper dup” only automatically refreshes repos for which Auto-Refresh is enabled, obviously.
Like any other zypper command (except “zypper ref”).
Otherwise it relies on its own view of the repos, in the metadata cache.
It might be likely but not so “obvious” to anyone seeking confirmation. What might be obvious is that a dist-upgrade without refreshed metadata makes no sense, so a user might expect that a refresh would always be performed.
For “dup”, the zypper man page says: “This command applies the state of (specified) repositories onto the system; upgrades (or even downgrades) installed packages to versions found in repositories,…”. To be clear, it’s not the actual “state of repositories”, it’s the state of the metadata in the cache or so-called database that gets applied.
It does make sense, for repos that don’t change anyway.
Why should zypper refresh the metadata if the user/admin explicitely told it not to?
For “dup”, the zypper man page says: “This command applies the state of (specified) repositories onto the system; upgrades (or even downgrades) installed packages to versions found in repositories,…”. To be clear, it’s not the actual “state of repositories”, it’s the state of the metadata in the cache or so-called database that gets applied.
Well, “zypper dup” does apply the state of the repositories onto the system.
But without refresh there might be a difference between what zypper believes about the state of the repos and their actual state.
That’s the nature of a cache. And if you would refresh all the time, the whole cache would be pointless.
It does not do a refresh for repos that have Auto-Refresh disabled. That’s the whole point of the Auto-Refresh setting.
Yes, that probably is obvious as a general point.
“zypper refresh” is unnecessary only if you have set the repos to Auto-Refresh. Or for repos that don’t change anyway, like the main OSS and Non-OSS repos.
Yes, on my system the Update repos, Tumbleweed, and Packman repos are set to auto-refresh, whereas Oss and Non-oss are not (as on my standard systems). It might save a bit of delay opening YaST.
On 2014-04-23 14:46, consused wrote:
> Yes, on my system the Update repos, Tumbleweed, and Packman repos are
> set to auto-refresh, whereas Oss and Non-oss are not (as on my standard
> systems). It might save a bit of delay opening YaST.
Not really, or not much.
Zypper should see fast enough that the metadata has not changed, and not
download it again.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
