On Mon, Dec 27, 2010 at 3:18 PM, Greg KH firstname.lastname@example.org wrote:
On Sun, Dec 26, 2010 at 04:29:15PM -0500, Greg Freemyer wrote:
On Fri, Dec 17, 2010 at 5:38 PM, Greg KH email@example.com wrote:
On Fri, Dec 17, 2010 at 05:31:31PM -0500, Greg Freemyer wrote:
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.)
Oh, and of course this isn't "stable" at all yet, it's under constant development, and I might accidentally break things at times. I am using the openSUSE:Tumbleweed:Testing repo for "big" tests (like the zypper one currently in there), but I can't guarantee that Tumbleweed will not cause you problems right now at times.
I just tried the Tumbleweed zypper dup process on my laptop. (Previously I was testing with my desktop.)
Zypper ar went fine.
Zypper dup --from still gave warnings.
A sample from today:
Retrieving package git-core-184.108.40.206-5.1.i586 (10/56), 2.2 MiB (10.5 MiB unpacked) Retrieving: git-core-220.127.116.11-5.1.i586.rpm [done (580.5 KiB/s)] Installing: git-core-18.104.22.168-5.1 [done] Additional rpm output: warning: /var/cache/zypp/packages/openSUSE_Tumbleweed/i586/git-core-22.214.171.124-5.1.i586.rpm: Header V3 DSA/SHA1 Signature, key ID a840f92c: NOKEY
Odd, have you ever accepted the tumbleweed gpg key? If not, then I guess this could be happening. But I can't reproduce this at all here on any of my test machines, or my main laptop.
I just tried again at the office. And this time no warnings.
fyi: Yes I had accepted the gpg key during my earlier testing.
I still think the repo (meaning mirrors, etc. not the packages within the project) is somewhat unstable for Tumbleweed. I have no idea why that would be.