From: Aleksey Tsalolikhin atsaloli.t...@gmail.com
Let's say your operating policy is no patch updates without testing
first in the test environment. Let's say it takes you 3 weeks to
test. Over the course of the 3 weeks, the repo changes (new
packages added, old removed).
Is there a way
On 09/21/2011 10:13 PM, Aleksey Tsalolikhin wrote:
Hello,
Let's say your operating policy is no patch updates without testing
first in the test environment. Let's say it takes you 3 weeks to
test. Over the course of the 3 weeks, the repo changes (new
packages added, old removed).
Is
I think a local mirror is really your best option. Or possibly two repos.
One for testing, which you sync when you want to test updates and point all
test systems at it. Then a production repo for production systems that
pulls from the frozen test repo. One addition to your idea would be to use
Hello,
Let's say your operating policy is no patch updates without testing
first in the test environment. Let's say it takes you 3 weeks to
test. Over the course of the 3 weeks, the repo changes (new
packages added, old removed).
Is there a way to freeze a set of packages so that when I
run
4 matches
Mail list logo
