We just make a complete copy of the repository on specific cut-off dates. They can be whatever makes sense for you. We then use that directory name when we want to have multiple people synch to the same set of maintenance: 20060930/ 20060930/i386 20060930/i386/SUSE-SLES 20060930/i386/SUSE-SLES/10 20060930/i386/SUSE-SLES/10/rpm 20060930/i386/SUSE-SLES/10/rpm/i586 20060930/i386/SUSE-SLES/10/rpm/i586/headers 20060930/i386/SUSE-SLES/10/rpm/i686 20060930/i386/SUSE-SLES/10/rpm/i686/headers 20060930/i386/SUSE-SLES/10/rpm/noarch 20060930/i386/SUSE-SLES/10/rpm/noarch/headers 20060930/i386/SUSE-SLES/10/headers 20060930/i386/SUSE-SLES/9 20060930/i386/SUSE-SLES/9/rpm 20060930/i386/SUSE-SLES/9/rpm/i586 20060930/i386/SUSE-SLES/9/rpm/i586/headers 20060930/i386/SUSE-SLES/9/rpm/i686 20060930/i386/SUSE-SLES/9/rpm/i686/headers 20060930/i386/SUSE-SLES/9/rpm/noarch 20060930/i386/SUSE-SLES/9/rpm/noarch/headers 20060930/i386/SUSE-SLES/9/images 20060930/i386/SUSE-SLES/9/patches 20060930/i386/SUSE-SLES/9/patches.obsolete 20060930/i386/SUSE-SLES/9/sources 20060930/i386/SUSE-SLES/9/sources/headers 20060930/i386/SUSE-SLES/9/headers 20060930/i386/SuSE-SLES 20060930/i386/SuSE-SLES/8 20060930/i386/SuSE-SLES/8/rpm 20060930/i386/SuSE-SLES/8/rpm/i586 20060930/i386/SuSE-SLES/8/rpm/i586/headers 20060930/i386/SuSE-SLES/8/rpm/i686 20060930/i386/SuSE-SLES/8/rpm/i686/headers 20060930/i386/SuSE-SLES/8/rpm/noarch 20060930/i386/SuSE-SLES/8/rpm/noarch/headers 20060930/i386/SuSE-SLES/8/patches 20060930/i386/SuSE-SLES/8/scripts 20060930/i386/SuSE-SLES/8/headers 20060930/i386/SLES-SDK 20060930/i386/SLES-SDK/9 20060930/i386/SLES-SDK/9/patches 20060930/i386/SLES-SDK/9/rpm 20060930/i386/SLES-SDK/9/rpm/i586 20060930/i386/SLES-SDK/9/rpm/i586/headers 20060930/i386/SLES-SDK/9/headers 20060930/i386/SUSE-CORE 20060930/i386/SUSE-CORE/9 20060930/i386/SUSE-CORE/9/images 20060930/i386/SUSE-CORE/9/patches 20060930/i386/SUSE-CORE/9/patches.obsolete 20060930/i386/SUSE-CORE/9/rpm 20060930/i386/SUSE-CORE/9/rpm/i586 20060930/i386/SUSE-CORE/9/rpm/i586/headers 20060930/i386/SUSE-CORE/9/rpm/i686 20060930/i386/SUSE-CORE/9/rpm/i686/headers 20060930/i386/SUSE-CORE/9/rpm/noarch 20060930/i386/SUSE-CORE/9/rpm/noarch/headers 20060930/i386/SUSE-CORE/9/scripts 20060930/i386/SUSE-CORE/9/sources 20060930/i386/SUSE-CORE/9/sources/headers 20060930/i386/SUSE-CORE/9/headers 20060930/i386/UnitedLinux 20060930/i386/UnitedLinux/1.0 20060930/i386/UnitedLinux/1.0/patches 20060930/ia64 20060930/ppc 20060930/x86_64 20060930/x86_64/SUSE-SLES 20060930/x86_64/SUSE-SLES/10 20060930/x86_64/SUSE-SLES/10/rpm 20060930/x86_64/SUSE-SLES/10/rpm/i586 20060930/x86_64/SUSE-SLES/10/rpm/i586/headers 20060930/x86_64/SUSE-SLES/10/rpm/noarch 20060930/x86_64/SUSE-SLES/10/rpm/noarch/headers 20060930/x86_64/SUSE-SLES/10/rpm/nosrc 20060930/x86_64/SUSE-SLES/10/rpm/nosrc/headers 20060930/x86_64/SUSE-SLES/10/rpm/x86_64 20060930/x86_64/SUSE-SLES/10/rpm/x86_64/headers 20060930/x86_64/SUSE-SLES/10/headers 20060930/x86_64/SUSE-SLES/9 20060930/x86_64/SUSE-SLES/9/rpm 20060930/x86_64/SUSE-SLES/9/rpm/i586 20060930/x86_64/SUSE-SLES/9/rpm/i586/headers 20060930/x86_64/SUSE-SLES/9/rpm/noarch 20060930/x86_64/SUSE-SLES/9/rpm/noarch/headers 20060930/x86_64/SUSE-SLES/9/rpm/nosrc 20060930/x86_64/SUSE-SLES/9/rpm/nosrc/headers 20060930/x86_64/SUSE-SLES/9/rpm/x86_64 20060930/x86_64/SUSE-SLES/9/rpm/x86_64/headers 20060930/x86_64/SUSE-SLES/9/patches 20060930/x86_64/SUSE-SLES/9/headers 20060930/x86_64/SuSE-SLES 20060930/x86_64/SuSE-SLES/8 20060930/x86_64/SuSE-SLES/8/rpm 20060930/x86_64/SuSE-SLES/8/rpm/i586 20060930/x86_64/SuSE-SLES/8/rpm/i586/headers 20060930/x86_64/SuSE-SLES/8/rpm/noarch 20060930/x86_64/SuSE-SLES/8/rpm/noarch/headers 20060930/x86_64/SuSE-SLES/8/rpm/x86_64 20060930/x86_64/SuSE-SLES/8/rpm/x86_64/headers 20060930/x86_64/SuSE-SLES/8/patches 20060930/x86_64/SuSE-SLES/8/scripts 20060930/x86_64/SuSE-SLES/8/headers 20060930/x86_64/SLES-SDK 20060930/x86_64/SLES-SDK/9 20060930/x86_64/SLES-SDK/9/patches 20060930/x86_64/SLES-SDK/9/rpm 20060930/x86_64/SLES-SDK/9/rpm/x86_64 20060930/x86_64/SLES-SDK/9/rpm/x86_64/headers 20060930/x86_64/SLES-SDK/9/headers 20060930/x86_64/SUSE-CORE 20060930/x86_64/SUSE-CORE/9 20060930/x86_64/SUSE-CORE/9/patches 20060930/x86_64/SUSE-CORE/9/rpm 20060930/x86_64/SUSE-CORE/9/rpm/i586 20060930/x86_64/SUSE-CORE/9/rpm/i586/headers 20060930/x86_64/SUSE-CORE/9/rpm/noarch 20060930/x86_64/SUSE-CORE/9/rpm/noarch/headers 20060930/x86_64/SUSE-CORE/9/rpm/x86_64 20060930/x86_64/SUSE-CORE/9/rpm/x86_64/headers 20060930/x86_64/SUSE-CORE/9/scripts 20060930/x86_64/SUSE-CORE/9/headers
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ifurung, [EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 11:57 AM To: [email protected] Subject: YOU strategy We want to use YOU (SUSE's Yast Online Update) to keep our linux servers current; the automation helps a great deal. We maintain a local server and currently we sync it with SUSE servers once a week. We have two conflicting needs : 1) We frequently get orders from our security group to apply security patches to our linux servers. The weekly sync of our YOU server keeps it very current and we apply the security patches as needed. Keeps the security folks happy. 2) We have a need to apply patches to a test server; release it for testing; then apply the same patches to a production server. In this case we need a stable YOU server until the test goes to production. The test period could take weeks or months. I was wondering how others do it. Thanks for any info. Ismael ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
