On Fri, Dec 17, 2010 at 05:31:31PM -0500, Greg Freemyer wrote:
On Fri, Dec 17, 2010 at 5:24 PM, Greg KH firstname.lastname@example.org wrote:
On Fri, Dec 17, 2010 at 05:02:25PM -0500, Greg Freemyer wrote:
For the second time today I've deleted the tumbleweed repo from zypper and re-added it via:
This time is seems to have really worked and suddenly I'm seeing packages in the Tumbleweed repo.
I have no idea why it wasn't working a few hours ago, nor why it did work this time.
Maybe the repo file itself was still mirroring out some key info.
Sorry for the noise,
No problem, glad it's working now for you. Please let me know if you have any future problems with it.
Now I'm upgrading to Tumbleweed, but all the packages are giving warnings. Is that expected? (The repo just doesn't feel stable yet to me.)
Retrieving package samba-client-32bit-3.5.6-1.3.x86_64 (30/66), 995.0 KiB (3.3 MiB unpacked) Retrieving: samba-client-32bit-3.5.6-1.3.x86_64.rpm [done (218.2 KiB/s)] Installing: samba-client-32bit-3.5.6-1.3 [done] Additional rpm output: warning: /var/cache/zypp/packages/openSUSE_Tumbleweed/x86_64/samba-client-32bit-3.5.6-1.3.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID a840f92c: NOKEY
Did you accept the Tumbleweed gpg key as valid?
What are you using to upgrade, 'zypper dup'? I've never seen this on my systems here.