[Bug 854946] Re: [SRU] Rampart's configuration on Ubuntu's package doesn't define a default ClockSkewBuffer

[Clint Byrum]

Excerpts from Bfreis's message of Mon Sep 26 19:55:40 UTC 2011:
> Hello.
> 
> I've just installed the update from natty-proposed on my 3 servers (2
> NCs, 1 CC), and they seem to be fine. I will confirm if everything is
> still OK tomorrow, since the errors were intermittent.
> 
> It is the first time I use "-proposed", so I have a question: if
> everything goes smooth, and you publish this update to "main", will I
> have to do anything on my servers, like reinstall the packages, or
> somehow tell the system that the packages now come from "main" instead
> of "-proposed"? Will I be able to simply remove the "deb ... natty-
> proposed ..." line from /etc/apt/sources.list without destroying
> anything?
> 
> Thanks!

No, you won't have to do anything. Apt doesn't care where the latest
package comes from on upgrade, it just gets the latest package*.

* absent any apt-pinning or use of backports. ;)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/854946

Title:
  [SRU] Rampart's configuration on Ubuntu's package doesn't define a
  default ClockSkewBuffer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/854946/+subscriptions