1 |
Hello James, |
2 |
|
3 |
I do not know if it is useful for what you're trying to achieve, but using |
4 |
catalyst for few years now, I encountered this problem a dozen times |
5 |
already. |
6 |
|
7 |
I never found a proper/elegant way to solve this issue (blocking packages on |
8 |
an aging stage3 tarball). Actually there is (start from a stage1 but then |
9 |
you can end up struggling with cpp preprocessor missing). I'm too lazy and |
10 |
scripting a chroot is way faster for me. |
11 |
So what I do (and I'm currently having the same issue as you do), I copy a |
12 |
portage snapshot inside the temp dir |
13 |
(/var/tmp/catalyst/tmp/default/whatever/usr/portage/) chroot into it and |
14 |
correct whatever was blocking my build. I then rerun catalyst and here it |
15 |
goes. Before you pack the whole as an iso, don't forget to remove the |
16 |
portage snapshot or your livecd will be oversized. |
17 |
|
18 |
I know it is ugly, but it does the trick. |
19 |
|
20 |
To give an idea, here is my routine to build/patch a stage1. |
21 |
#!/bin/bash |
22 |
set -e |
23 |
set -x |
24 |
vs=0.1.10 |
25 |
pv="20081124" |
26 |
CHROOT="/var/tmp/catalyst/tmp/default/livecd-stage1-x86-genluks-$vs" |
27 |
catalyst -a -f genluks-stage1.spec || { |
28 |
|
29 |
rsync -av /var/tmp/catalyst/snapshot_cache/$pv/portage $CHROOT/usr |
30 |
#echo "emerge autounmask;autounmask |
31 |
app-misc/livecd-tools-1.0.40_pre3;autounmask sys-apps/hwsetup-1.2;emerge |
32 |
livecd-tools hwsetup udev" > $CHROOT/lo |
33 |
echo "emerge -f e2fsprogs e2fsprogs-libs && emerge --unmerge ss |
34 |
com_err e2fsprogs && emerge e2fsprogs e2fsprogs-libs" > $CHROOT/lo |
35 |
chroot $CHROOT bash /lo |
36 |
rm -rf $CHROOT/usr/portage/* |
37 |
rm $CHROOT/lo |
38 |
catalyst -f genluks-stage1.spec |
39 |
} |
40 |
|
41 |
I'm currently running it and it works like a charm. |
42 |
|
43 |
Hope it helps in some way. |
44 |
|
45 |
Erick |
46 |
|
47 |
On Mon, Nov 24, 2008 at 2:29 AM, Andrew Gaffney <agaffney@g.o> wrote: |
48 |
|
49 |
> Dio, James wrote: |
50 |
> |
51 |
>> Thank you for your response, in an effort to make sure that everything |
52 |
>> is using the same snapshot, I have done everything over again and have |
53 |
>> the same issue, and included the spec files I used. |
54 |
>> I had wanted to purge everything catalyst has produced so far, however |
55 |
>> when I ran catalyst --purge, I get the following error: |
56 |
>> !!! catalyst: please specify one of either -f or -C |
57 |
>> When I specify both --purge and -f (some spec file) it attempts to build |
58 |
>> the stage instead of purge. Should I open a bug for this? |
59 |
>> |
60 |
> |
61 |
> No, that's how it's supposed to work. The purge isn't an operation all by |
62 |
> itself. It's just an additional step that's performed before a build. |
63 |
> |
64 |
> |
65 |
> Here's what I did: |
66 |
>> emerge --sync |
67 |
>> catalyst -s rwmc.001 |
68 |
>> catalyst -f rwmc-stage1.spec |
69 |
>> catalyst -f rwmc-stage2.spec |
70 |
>> catalyst -f rwmc-stage3.spec |
71 |
>> |
72 |
>> rwmc-stage1.spec contains: |
73 |
>> subarch: x86 |
74 |
>> target: stage1 |
75 |
>> version_stamp: rwmc.001 |
76 |
>> rel_type: default |
77 |
>> profile: default/linux/x86/2008.0 |
78 |
>> snapshot: rwmc.001 |
79 |
>> source_subpath: default/stage3-i686-2008.0 |
80 |
>> chost: i686-pc-linux-gnu |
81 |
>> |
82 |
>> rwmc-stage2.spec contains: |
83 |
>> subarch: i686 |
84 |
>> target: stage2 |
85 |
>> version_stamp: rwmc.001 |
86 |
>> rel_type: default |
87 |
>> profile: default/linux/x86/2008.0 |
88 |
>> snapshot: rwmc.001 |
89 |
>> source_subpath: default/stage1-x86-rwmc.001 |
90 |
>> chost: i686-pc-linux-gnu |
91 |
>> |
92 |
>> rwmc-stage3.spec contains: |
93 |
>> subarch: i686 |
94 |
>> target: stage3 |
95 |
>> version_stamp: rwmc.001 |
96 |
>> rel_type: default |
97 |
>> profile: default/linux/x86/2008.0 |
98 |
>> snapshot: rwmc.001 |
99 |
>> source_subpath: default/stage2-i686-rwmc.001 |
100 |
>> |
101 |
> |
102 |
> At first glance, everything here looks fine. I'm not sure what to tell you. |
103 |
> |
104 |
> |
105 |
> -- |
106 |
> Andrew Gaffney |
107 |
> http://dev.gentoo.org/~agaffney/ <http://dev.gentoo.org/%7Eagaffney/> |
108 |
> Gentoo Linux Developer Catalyst/Genkernel + Release Engineering |
109 |
> Lead |
110 |
> |
111 |
> |