Mailinglist Archive: zypp-devel (56 mails)
| < Previous | Next > |
Re: [zypp-devel] Getting a refresh to work
- From: Martin Vidner <mvidner@xxxxxxx>
- Date: Fri, 14 Dec 2007 19:09:17 +0100
- Message-id: <20071214180917.GA21274@xxxxxxxxxxxxxxxx>
On Tue, Dec 11, 2007 at 02:36:07PM -0700, Boyd Timothy wrote:
Maybe you can find out yourself from the zypp log. Or try strace,
the universal hammer of blackbox debugging.
Or look for similar code in other code using libzypp:
http://svn.suse.de/svn/zypp/trunk/zypper/
http://svn.suse.de/svn/yast/trunk/pkg-bindings/
http://svn.suse.de/svn/yast/trunk/ncurses/src/pkg/
http://svn.suse.de/svn/yast/trunk/qt/src/pkg/
Well, looking at refresh_raw_metadata in zypper, I don't see what is
different in your case.
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
PackageKit defines two types of cache refreshes. One of them forces a
refresh and the other doesn't. If you take a look at our code here:
http://pastebin.ca/812559
...are we doing anything wrong. A standard refresh (one without a
force) seems to work okay. When I do a force refresh, I get an error,
"Valid metadata not found at specified URL(s)".
Suggestions?
Maybe you can find out yourself from the zypp log. Or try strace,
the universal hammer of blackbox debugging.
Or look for similar code in other code using libzypp:
http://svn.suse.de/svn/zypp/trunk/zypper/
http://svn.suse.de/svn/yast/trunk/pkg-bindings/
http://svn.suse.de/svn/yast/trunk/ncurses/src/pkg/
http://svn.suse.de/svn/yast/trunk/qt/src/pkg/
Well, looking at refresh_raw_metadata in zypper, I don't see what is
different in your case.
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |