It says there are 143 updates
and when I tried to update, it
gave me this error message
File ‘./suse/noarch/branding-openSUSE-13.2-2.32.noarch.rpm’ not found on medium ‘http://download.opensuse.org/factory/repo/oss’
I have the factory repos enabled did they change?
I’m in the middle of updating (on a different computer). I did “ignore” on that one.
Then I ran into a separate problem for glibc-devel. That did not look like something to ignore, so I aborted.
I ran into a vaguely similar problem a few days ago, on a different computer. I was updating, and ran into a similar message about a file in packman.
As best I could tell, this is what happened:
I was updating a file x to the version “next”. It could not find that version.
Apparently, the rpms in the packman repo had been updated to “next+1”, but the metadata still said “next”.
This probably happens because a mirror is in the middle of being updated. So best to try again after a few hours to allow things to settle down.
Do i need a pacman repo enabled?
I just have the main factory ones
I just have factory on my factory install. My packman example was for a straight 13.1 system. But it illustrates the point that there can be times when the metadata does not match the actual data on the mirror that you are using. Waiting for a few hours seems like the best choice.
I think this discussion should have been in the Beta forum, though the metadata not matching data on a mirror can be a general problem.
Yes i was thinking that if someone can move this post for
me to the beta-forum, if i’m using factory as my main system
so ill ask questions there if i run into problems
It is of course also possible that the corresponding package got updated on the mirror between your last metadata refresh and the time the package is being downloaded.
And libzypp doesn’t refresh the metadata if the last refresh was less than 10 minutes ago.
Those cases could be resolved by aborting the update, running “zypper ref” manually, and doing the update again.
I did see such a mismatch between the metadata and the actual data on Packman’s mirrors a few times as well though. So this problem (that you describe) really does exists, at least for Packman. I suppose it depends on how often the particular mirror is refreshed…
Regarding this particular case as described in the OP:
I do see branding-openSUSE-13.2-2.32.noarch.rpm in http://download.opensuse.org/factory/repo/oss/suse/noarch/ so it really seems to be caused by an outdated (at the time you tried to update) mirror. But that package is dated 25-Jun-2014…
Maybe download and install it manually.
Which repo URL do you have really?
zypper lr -d
If it’s the factory-snapshot URL, that doesn’t work at the moment, as it redirects to a wrong directory AFAIK. Use [noparse]http://download.opensuse.org/factory/repo/oss/[/noparse] directly. But you would get a different error message in that case I suppose.
In cache branding-openSUSE-13.2-2.32.noarch.rpm (1/135), 13.6 KiB ( 1.6 KiB unpacked)
In cache bundle-lang-common-en-13.2-2.14.noarch.rpm (2/135), 206.4 KiB ( 1.4 MiB unpacked)
In cache ca-certificates-mozilla-1.97-2.1.noarch.rpm (3/135), 200.9 KiB (362.5 KiB unpacked)
In cache gfxboot-branding-openSUSE-13.2-2.32.noarch.rpm (4/135), 2.7 MiB ( 4.7 MiB unpacked)
Retrieving package kdelibs4-branding-openSUSE-13.2-2.32.noarch (5/135), 1.5 MiB ( 1.4 MiB unpacked)
Retrieving: kdelibs4-branding-openSUSE-13.2-2.32.noarch.rpm ....................................................................[error]
File './suse/noarch/kdelibs4-branding-openSUSE-13.2-2.32.noarch.rpm' not found on medium 'http://download.opensuse.org/factory/repo/oss'
Abort, retry, ignore? [a/r/i/? shows all options] (a):
It still says this, I get the feeling I need another repo besides factory?
zypper lr -d
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
--+------------------+------------------+---------+---------+----------+-------+-------------------------------------------------------+--------
1 | repo-debug | repo-debug | Yes | Yes | 99 | yast2 | http://download.opensuse.org/factory/repo/debug |
2 | repo-non-oss | repo-non-oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/factory/repo/non-oss |
3 | repo-oss | repo-oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/factory/repo/oss |
4 | repo-src-non-oss | repo-src-non-oss | No | Yes | 99 | yast2 | http://download.opensuse.org/factory/repo/src-non-oss |
5 | repo-src-oss | repo-src-oss | No | Yes | 99 | yast2 | http://download.opensuse.org/factory/repo/src-oss |
No.
This is a different package now.
Apparently that mirror is being synced (i.e. the packages are being copied there) right now as you try to update, and some packages are still missing.
You could download and install kdelibs4-branding-openSUSE-13.2-2.32.noarch.rpm manually from the URL in my previous post.
But probably you’ll just get a different error later on then.
Wait a few hours and do the update then. The already downloaded packages will stay in the cache and shouldn’t be downloaded again.
Your repo list is ok.
On second though this was to be expected anyway, otherwise you wouldn’t have seen any updates and not been able to install any package. 
I have already tried to download everything like 4
times will my frequent attempts mess up the install
once its synced? or since it’s in cache will it be
ok?
Will be moved to Pre-release/Beta and is CLOSED for the moment.
Moved from Install/Boot/Login and open again.
No.
or since it’s in cache will it be
ok?
The cache is irrelevant here.
The cache is just that: a cache.
If libzypp wants to install a package, it downloads it to the cache before it installs it.
If the package is already downloaded and in the cache, it is just being installed from there and not downloaded again.
If there already is a newer package in the repo, the older version in the package cache is just being ignored and the newer one downloaded (to the cache).
In this particular case (those branding packages) you could even tell zypper to just ignore the download error.
The packages themselves have not changed except for the version number.
This is of course not to be taken as general advise though, as it can severely break your system.
Yes, I just choose the abort option
if zypper has a problem so I do not
break the system, I’m going to ignore
that update flag that keeps bugging me
and just try again later today as you
said.
Yes, I got that in my last attempt.
But notice that this is a different file from the one you were originally stuck on.
The evidence is still that the repo is in the middle of being updated and might not be consistent until the update is complete.
For your information, I just ran “zypper dup” on my Factory installation (I got 148 updates, including those branding packages that failed to download for you), and it worked without a hitch.
So if you still get those errors, it’s definitely a problem with some specific mirror(s) being outdated I’d say.
You’ll just have to wait in that case until they are fully up to date again. Might take days though.
Or try to set a specific mirror in your repo URL instead of the general “download.opensuse.org” redirector.
A list of mirrors is available here:
http://mirrors.opensuse.org/
Ok thank you for the list of mirrors. 
I just tried again (after a 1 hour delay). The update completed without a problem (166 updates).
Gnome still doesn’t work (seems to be a problem with Gnome and Intel graphics – see Bug 883904).
Apart from that, all seems to be fine.
Appears to be a bug in the intel driver 2.99.912 (as suggested in the bug report):
http://lists.opensuse.org/opensuse-factory/2014-06/msg00299.html