After installing 10.1 I ran in the yast update problem and none of the solutions I found worked.

I was able to access net with browser so I saved to disk libzypp then copied to cd and used yast to install from cd. After that I could do updates without any problem.

Not as simple as other solutions but it worked and would probably be easier for another newbe like me.

Easier and less work is rug.

>rug lu = list updates

> rug update = installs the updates

Of course, there are options you can use ( man rug ), but this will suffice for most.

uriah: I'd be keenly interested in exactly what file you copied to a cd, and then exactly how you installed it. I have the libzypp.rpm from a SUSE mirror on a cd. I can't make Yast installation source read the cd, no matter if I use proper mount commands. I also tried right-clicking the file under a Konqueror view to try and install with Yast (as an action), no luck there, either. I tried adding the file from a local directory with Yast installation source, also, which fails. Just putting this libzypp.rpm file on my root desktop and doing a right-click Yast install, under actions, causes my system to prompt for the installation media dvd and to re-install the old libzypp version.
As for what leandean suggested, I don't know if I can trust it, because I've read some SUSE postings that the first libzypp patch must be installed with Yast (and at those same postings, the methods described to get the patch to list in yast do not work on my system).

Go here::

http://andreasjaeger.blogspot.com/20...r_archive.html

Then scroll down to the bottom of the page and let the project manager for SuSE 10.1 explain how to get libzypp working properly.

Oh, thanks, I was there yesterday. Trouble is, I saw this as a test situation being conducted by Andreas Jaeger, however he actually stands in relation to SUSE Novell. Reading the upper parts of his page at that URL re-directed me to perform things that do not work on my machine. The libzypp patch will not show up in any Yast module on my machine (amd64), end of story.
I finally started using smart --gui to get the libzypp patch on my machine, but I'm still having trouble with YOU(YOU still does not show the libzypp patch, or anything else).
The thing about smart that misleads me is the way it lists things in the GUI. It definitely works, but doesn't make me feel secure about what I am installing (I'm absolutely sure that the new libzypp is in, now). Maybe my sense of security with YOU was also false, though. Please don't anyone ask me how to describe how to use the smart GUI screens, I couldn't do it without pictures.
Linux has got a ways to go. I shouldn't feel like I need a disk image of yesterday just when I do simple patch updates.

hey leanden,

when I do "rug lu" I only get this:
bogomir:/home/bgorjup # rug lu
No updates are available.

WARNING: Updates are only visible when you are subscribed to a catalog.
bogomir:/home/bgorjup #

How can i subscribe to a catalog?

Thanks

riba43 -- two words, man rug. It explains catalogs and how to subscribe.

DeekBeek -- Installed patches will not show up in YaST.

On my machine, nothing at all ever has displayed in YOU (only in software management). I wasted time obeying a useless posting by actual SUSE affiliates claiming that the first (yes,uninstalled)libzypp patch will show up in YOU if I first get a SUSE mirror url recognized by installation source under Yast. The same posting directed me to start YOU twice, and I would then see the libzypp patch listed in YOU. This never happened. The installation source module of Yast would not accept a click of the finish button nor a push of the enter key to accept a SUSE mirror url, on my machine. I posted the url for these worthless (to my machine, maybe not someone else's, because it's an amd 64, maybe?)instructions elsewhere in the forums, and they are from SUSE, so believe me or not.

I am having big problems with the new online update. This thread looked like it was addressing the same problems I am having. So, I've been following the suggestions but with disturbing results:

I wasn't sure where libzypp was located, even though I assumed it was downloaded somewhere, it may have been from the installation disk. Since it was vague, I moved on the the next post in this thread, which left me feeling like the first post was not a good solution.

I tried the fourth posting:
I followed it exactly and then tried the Yast2 online update which failed with the message:
I then tried rug update and it failed with the following message:
Is this just me making mistakes or is SUSE 10.1 broken?

Thanks,
-Bob

First I am rank newbie--was trying to use smart and even though I had not addressed yast when I told it to start action it deleated parts of yast so that I can not even invoke it. Well back to partial reinstall and start again.

Suse needs to release new iso with this problem corrected. I suspect most people in my place would just try another linux but I am stubborn. Though I may decide to go back to 10.0 and wait for a new version without all these bugs. Like waiting for sp2 on a ms product. Which is the reasion I am trying to switch to linux.

zen package manager is the worst piece of software I have ever seen, it should be wiped from the hisory of space and time.

^^ Nuff said

At work we use Novell servers and they have the Zen packages installed on our Windows PCs. It is such a bloated piece of crap. It looks like Novell is intergrating the Zen crap into Suse now... I hope this is not the end for Suse.

I'm with you. After being forced to use the only updater that would work on my SUSE 10.1 boxed distribution (smart -gui), and installing a mess of updates (that first libzypp patch, then lots of yast and some zen patches), I wasted time tinkering with zen updater. It doesn't even work. Zen updater takes a very long time to "poll" for the updates. If I even just pick one patch to install with that updater, it fails and posts a "transaction failed" message (after wasting more time exhibiting a display that reads "resolving dependencies).
SUSE had better have a big patch disk forthcoming for this version..