| 1 |
Bardur Arantsson wrote: |
| 2 |
> Hello all, |
| 3 |
> |
| 4 |
[--snip--] |
| 5 |
> I added a print statement for self.settings["source_path"] and that prints |
| 6 |
> |
| 7 |
> /var/tmp/catalyst/builds/stage3-x86-2006.0.tar.bz2 |
| 8 |
> |
| 9 |
> which seems rather strange to me. The (hopefully) relevant portion of my |
| 10 |
> stage2.spec file is as follows: |
| 11 |
> |
| 12 |
> subarch: x86 |
| 13 |
> version_stamp: CURRENT |
| 14 |
> target: livecd-stage2 |
| 15 |
> rel_type: default |
| 16 |
> profile: default-linux/x86/2006.0 |
| 17 |
> snapshot: 20060821 |
| 18 |
> source_subpath: stage3-x86-2006.0 |
| 19 |
|
| 20 |
... and of course the source_subpath was the problem; for some reason |
| 21 |
I'd completely forgotten that it's supposed to be a stage1. Changing this to |
| 22 |
|
| 23 |
source_subpath: default/livecd-stage1-x86-CURRENT |
| 24 |
|
| 25 |
(My version stamp is CURRENT) worked. |
| 26 |
|
| 27 |
I think the livecd_stage2_target.py should probably give the user a |
| 28 |
slightly more informative error message ;). |
| 29 |
|
| 30 |
Maybe something like "Could not find directory $source_path. Your may be |
| 31 |
source_subpath incorrectly set." would be in order? |
| 32 |
|
| 33 |
> |
| 34 |
> The only thing resembling the file name above is the source_subpath |
| 35 |
> setting, but I'm not sure why that would get turned into a .tar.bz2 file |
| 36 |
> name by catalyst when catalyst itself clearly expects a directory name. |
| 37 |
> |
| 38 |
|
| 39 |
The "change to the name of a .tar.bz2" bit still puzzles me and I'm not |
| 40 |
sure it's desirable behavior. |
| 41 |
|
| 42 |
Cheers, |
| 43 |
|
| 44 |
-- |
| 45 |
Bardur Arantsson |
| 46 |
<bardurREMOVE@×××××××××××××××.net> |
| 47 |
|
| 48 |
I haven't slept for ten days... because that would be too long. |
| 49 |
Mitch Hedberg |
| 50 |
|
| 51 |
-- |
| 52 |
gentoo-catalyst@g.o mailing list |
Archives