From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-catalyst+bounces-2084-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1K9ls5-00030m-VX
for garchives@archives.gentoo.org; Fri, 20 Jun 2008 19:02:06 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id EE205E0328;
Fri, 20 Jun 2008 19:02:04 +0000 (UTC)
Received: from yx-out-1718.google.com (yx-out-1718.google.com [74.125.44.157])
by pigeon.gentoo.org (Postfix) with ESMTP id AFE31E0328
for <gentoo-catalyst@lists.gentoo.org>; Fri, 20 Jun 2008 19:02:04 +0000 (UTC)
Received: by yx-out-1718.google.com with SMTP id 4so288268yxp.46
for <gentoo-catalyst@lists.gentoo.org>; Fri, 20 Jun 2008 12:02:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:mime-version:content-type;
bh=1QpO+pGIci87omI9j54B7Zvp3tOunekKJQhSXn1aMs4=;
b=g9dMQPh5XxQpIMJLfu82P4Wkn3r5x++4OLwlF+R/RUP4JdSzVlc+qQ7qMMazAZHQDK
34yxFp5CSHTkSUPVTRhWX90A/HqTp/WyZ8T4dvx/ghPdQU+sDgHeS3DUxI0lNUBvODBi
UayGF8EA7gFC6Y90WJgEY2fbprjqVXltzsMAU=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:mime-version:content-type;
b=kAI2tRZWW3WDCJKeHezc6Lxy0mmzBio3+E4w9JQQ1ceon/HFCfbO9xhjjpwuCovm5l
/yC7IgCmVij9vSdRrci4u5u/fwzLlHul1P7+mBkMxnna8jGkBJ0IzBk2sNdAQZpLW1pr
4NY+NvBXuT7ql52KtAeTFvGz240usoK4b4DrY=
Received: by 10.142.52.9 with SMTP id z9mr1731745wfz.70.1213988523031;
Fri, 20 Jun 2008 12:02:03 -0700 (PDT)
Received: by 10.143.14.13 with HTTP; Fri, 20 Jun 2008 12:02:02 -0700 (PDT)
Message-ID: <8a0c7af10806201202p43163c87ye45d7761613d960e@mail.gmail.com>
Date: Fri, 20 Jun 2008 16:02:02 -0300
From: "Daniel van Ham Colchete" <daniel.colchete@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Updating deployed stage4 servers
Precedence: bulk
List-Post: <mailto:gentoo-catalyst@lists.gentoo.org>
List-Help: <mailto:gentoo-catalyst+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-catalyst+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-catalyst+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-catalyst.gentoo.org>
X-BeenThere: gentoo-catalyst@lists.gentoo.org
Reply-to: gentoo-catalyst@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_3032_26330286.1213988523024"
X-Archives-Salt: e79d3459-3ec8-4bae-8852-8b47f03940e9
X-Archives-Hash: ebb5396dc4eabbf367523f49f686ba07
------=_Part_3032_26330286.1213988523024
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi yall again!
I've made a stage4 11 months ago for some servers, and this stage4 is simply
amazing! It really works. Tuesday I had to reinstall a server and I did it
really quickly. Them I'm using the tinderbox target to generate packages
with security upgrades and cfengine to deploy it. Everything works but there
are a few cases where I start thinking whether doing the right way.
The big question I want to make here is: what is the right way to maintain
(upgrade) a stage4?
Right now I use tinderbox. But, it will not generate a seed for the next
tinderbox. If I upgrade something like wvstreams from 4.2 to 4.4, the next
tinderbox will not know that, because it's using the very first stage4 as
seed. My solution was, after building everything, open the stage4, update it
manually, close the stage4 with a new name and use it as your seed. A very
manual process.
The second problem is that if something is linked to libwvstreams-4.2.so I
will not know, so things can get really messy. The solution here is to build
the tinderbox, open the stage4, install the updates and run revdep-rebuild
inside the chroot. Keep the resulted package list, close the updated stage4
to another name. Use this updated stage4 as the seed to a second tinderbox
target witch will rebuild the affected packages. I never did it, but it
seems to be a way to go. There is a chance that will have a big loop here.
Again, very manual process, very very error prone, I would like to avoid.
What I noticed is that here on this list there are a lot of people using
catalyst to build and maintain a customized version of Gentoo too! What are
you people doing? How are you doing kernel upgrades? What about kernel
dependand packages (fuse, etc...).
How should I use the tool to make better use of it?
Thank you very much!
Best regards,
Daniel Colchete
------=_Part_3032_26330286.1213988523024
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi yall again!<br><br>I've made a stage4 11 months ago for some servers, and this stage4 is simply amazing! It really works. Tuesday I had to reinstall a server and I did it really quickly. Them I'm using the tinderbox target to generate packages with security upgrades and cfengine to deploy it. Everything works but there are a few cases where I start thinking whether doing the right way.<br>
<br>The big question I want to make here is: what is the right way to maintain (upgrade) a stage4?<br><br>Right now I use tinderbox. But, it will not generate a seed for the next tinderbox. If I upgrade something like wvstreams from 4.2 to 4.4, the next tinderbox will not know that, because it's using the very first stage4 as seed. My solution was, after building everything, open the stage4, update it manually, close the stage4 with a new name and use it as your seed. A very manual process. <br>
<br>The second problem is that if something is linked to <a href="http://libwvstreams-4.2.so">libwvstreams-4.2.so</a> I will not know, so things can get really messy. The solution here is to build the tinderbox, open the stage4, install the updates and run revdep-rebuild inside the chroot. Keep the resulted package list, close the updated stage4 to another name. Use this updated stage4 as the seed to a second tinderbox target witch will rebuild the affected packages. I never did it, but it seems to be a way to go. There is a chance that will have a big loop here. Again, very manual process, very very error prone, I would like to avoid.<br>
<br>What I noticed is that here on this list there are a lot of people using catalyst to build and maintain a customized version of Gentoo too! What are you people doing? How are you doing kernel upgrades? What about kernel dependand packages (fuse, etc...).<br>
<br>How should I use the tool to make better use of it?<br><br>Thank you very much!<br><br>Best regards,<br>Daniel Colchete<br>
------=_Part_3032_26330286.1213988523024--
--
gentoo-catalyst@lists.gentoo.org mailing list