Re: [gentoo-catalyst] perl-cleaner during stage4?
On 06/22/2010 08:55 AM, Peter Stuge wrote: Hi, I'm building another stage4, and since perl was updated I needed to run perl-cleaner --all-modules for modules to be found by other ebuilds. Since the package (e.g. Archive-Zip) was already installed (just against older perl version) the dependency didn't trigger a rebuild. I hacked perl-cleaner into stage4-chroot.sh, but maybe there is a better way to do it? I guess the same question goes also for python and python-updater. //Peter The proper way to do it is build your own stage 1, 2, and 3 along with the stage 4, all with the same snapshot, so that you don't have "upgrades". -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Circular dependencies.
The x86 autobuilds have been affected by this same issue for the past 2 weeks.
All other architectures have been fine. I haven't taken the time to investigate
it yet.
On 03/03/2010 08:25 PM, Juan Luis Pérez Pérez wrote:
> I'm having circular dependencies issue starting with portage snapshot
> 20100216. When I use 20100125 snapshot there is no problem.
>
> When doing catalyst -f stage3.spec, it throws this error:
>
>>>> Regenerating /etc/ld.so.cache...
> emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps virtual/portage
> !!! CANNOT IMPORT HTTP.CLIENT: cannot import name HTTPSConnection
> emerge --quiet --usepkg --buildpkg --newuse -e system
> !!! CANNOT IMPORT HTTP.CLIENT: cannot import name HTTPSConnection
>
>
> [nomerge ] sys-devel/automake-1.11.1
> [ebuild N] sys-apps/help2man-1.36.4-r1 USE="nls"
> [ebuild N] dev-perl/Locale-gettext-1.05-r1
> [ebuild R ]dev-lang/perl-5.8.8-r8 USE="berkdb* gdbm* -build*"
> [ebuild N] sys-libs/gdbm-1.8.3-r4 USE="berkdb"
> [ebuild N] sys-libs/db-4.7.25_p4 USE="-doc -java -nocxx -tcl -test"
> [ebuild NS ] sys-devel/automake-1.10.3 [1.11.1]
>
> * Error: circular dependencies:
>
> ('ebuild', '/', 'dev-lang/perl-5.8.8-r8', 'merge') depends on
> ('ebuild', '/', 'sys-libs/gdbm-1.8.3-r4', 'merge') (buildtime)
> ('ebuild', '/', 'sys-libs/db-4.7.25_p4', 'merge') (buildtime)
> ('ebuild', '/', 'sys-libs/gdbm-1.8.3-r4', 'merge') depends on
> ('ebuild', '/', 'sys-libs/db-4.7.25_p4', 'merge') (buildtime)
> ('ebuild', '/', 'dev-perl/Locale-gettext-1.05-r1', 'merge') depends on
> ('ebuild', '/', 'dev-lang/perl-5.8.8-r8', 'merge') (buildtime)
> ('ebuild', '/', 'sys-apps/help2man-1.36.4-r1', 'merge') depends on
> ('ebuild', '/', 'dev-perl/Locale-gettext-1.05-r1', 'merge') (buildtime)
> ('ebuild', '/', 'dev-lang/perl-5.8.8-r8', 'merge') (buildtime)
> ('ebuild', '/', 'sys-libs/db-4.7.25_p4', 'merge') depends on
> ('ebuild', '/', 'sys-devel/automake-1.10.3', 'merge') (buildtime)
> ('ebuild', '/', 'sys-devel/automake-1.10.3', 'merge') depends on
> ('ebuild', '/', 'dev-lang/perl-5.8.8-r8', 'merge') (buildtime)
> ('ebuild', '/', 'sys-apps/help2man-1.36.4-r1', 'merge') (buildtime)
>
> * Note that circular dependencies can often be avoided by temporarily
> * disabling USE flags that trigger optional dependencies.
>
> !!! catalyst: run script failed.
>
>
> Traceback (most recent call last):
> File "modules/generic_stage_target.py", line 1204, in run_local
> "run script failed.",env=self.env)
> File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd
> raise CatalystError,myexc
> CatalystError
> None
>
> !!! catalyst: Stage build aborting due to error.
>
> Traceback (most recent call last):
> File "/usr/lib/catalyst/catalyst", line 209, in build_target
> mytarget.run()
> File "modules/generic_stage_target.py", line 1260, in run
> apply(getattr(self,x))
> File "modules/generic_stage_target.py", line 1209, in run_local
> raise CatalystError,"Stage build aborting due to error."
> CatalystError
> !!! catalyst: Error encountered during run of target stage3
> Catalyst aborting
> lockfile does not exist
> '/var/tmp/catalyst/tmp/default/stage3-i686-kmdevelop-20100303/.catalyst_lock'
>
> Here is my spec file:
>
> subarch: i686
> target: stage3
> version_stamp: 20100303
> rel_type: default
> profile: default/linux/x86/10.0/desktop
> snapshot: 20100303
> source_subpath: default/stage2-i686-20100303
>
>
> I have no idea about how to deal with circular dependencies in catalyst...
> Is there any change in portage tree provoking this issue?
>
--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] LiveCD without Initrd
On 11/27/2009 07:49 AM, Shinkan wrote: > Hi again, > > I would like to build a stage2 livecd which would contain a kernel > without initrd. The CD will not boot without an initramfs. The linuxrc in it is what mounts the squashfs on the ISO and calls switch_root. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] emerge under catalyst not quiet?
On 11/16/2009 03:29 AM, Amit Dor-Shifer wrote: > What is overriding '--quiet'? Can I force '--quiet' to de-clutter the > output? That's likely an issue with portage. Catalyst isn't doing anything except running the command you see. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Too many problems with groupadd when creating stage3
On 10/29/2009 08:36 PM, Peter Stuge wrote: > Andrew Gaffney wrote: >> catalyst-3 > > Are there nice new features besides the system target? :) There are planned features that aren't fully implemented (such as specifying multiple targets in a single spec file). > Info? Samples? Will check it out. No, not really :P -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Too many problems with groupadd when creating stage3
On 10/29/2009 08:56 AM, Mike Frysinger wrote: > On Thursday 29 October 2009 08:34:48 Andrew Gaffney wrote: >> On 10/28/2009 03:42 PM, Mike Frysinger wrote: >>> not sure why we're still even using this stage[123] system. seems like >>> catalyst could be implemented in all of three commands: >>> ROOT=/tmp/stage3_pre emerge system -e >>> chroot /tmp/stage3 env ROOT=/tmp/stage3 emerge system -e >>> >>> then we wouldnt need these USE="build bootstrap" hacks nor would we need >>> the packages.build cruft >> >> I added a target called 'system' over 6 months ago in the catalyst-3 branch >> in git (now the master branch) that does exactly this. There are a few >> things missing compared to a "real" stage3, but it's just stuff like .ph >> files and other random things that can't be generated when $ROOT != "/". > > i'm not entirely sure the second ROOT= is necessary if a clean up script does > a sufficient job of catching all accumulated cruft. i was just throwing the > idea out there again, but seems it isnt terribly necessary if it's been > picked > up at some point. > -mike I didn't pay too much attention to what you actually said (aside from ROOT and 'emerge -e system'). The catalyst-3 'system' target just does the first command. It's basically the stage1 procedure with @system instead of packages.build. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Too many problems with groupadd when creating stage3
On 10/28/2009 03:42 PM, Mike Frysinger wrote: > not sure why we're still even using this stage[123] system. seems like > catalyst could be implemented in all of three commands: > ROOT=/tmp/stage3_pre emerge system -e > chroot /tmp/stage3 env ROOT=/tmp/stage3 emerge system -e > > then we wouldnt need these USE="build bootstrap" hacks nor would we need the > packages.build cruft I added a target called 'system' over 6 months ago in the catalyst-3 branch in git (now the master branch) that does exactly this. There are a few things missing compared to a "real" stage3, but it's just stuff like .ph files and other random things that can't be generated when $ROOT != "/". I had considered backporting it to catalyst-2, but I'd rather not touch the catalyst-2 code any more than necessary at this point. If anyone wants to play with it, you can get catalyst-3 by using the dev-util/catalyst- ebuild in the tree. However, I cannot guarantee that it's in a working state at any given time. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] catalyst & arm
On 09/20/2009 03:22 PM, Alan Hourihane wrote: > On Sun, 2009-09-20 at 14:41 -0500, Andrew Gaffney wrote: >> On 09/20/2009 01:13 PM, Alan Hourihane wrote: >>> ImportError: No module named cache.metadata_overlay >> >> You're getting this because you're using portage-2.2_rc41 (or thereabouts), >> which introduces a number of incompatibilities with the way that catalyst >> assumed portage-2.1.x worked. >> >> You can bypass this error by removing 'metadata_overlay' from 'options' in >> /etc/catalyst/catalyst.conf. It really doesn't even make sense to have the >> option anymore, since portage uses it by default these days. > > Hi Andrew, > > Thanks for the response, removing that didn't seem to make much > difference Run catalyst with -a so it clears the autoresume points. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] catalyst & arm
On 09/20/2009 01:13 PM, Alan Hourihane wrote: > ImportError: No module named cache.metadata_overlay You're getting this because you're using portage-2.2_rc41 (or thereabouts), which introduces a number of incompatibilities with the way that catalyst assumed portage-2.1.x worked. You can bypass this error by removing 'metadata_overlay' from 'options' in /etc/catalyst/catalyst.conf. It really doesn't even make sense to have the option anymore, since portage uses it by default these days. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Stage1 app-arch/lzma-utils-4.32.7 fails
On 08/28/2009 03:17 AM, "Andreas Rückert" wrote: Hi! Original-Nachricht Datum: Tue, 25 Aug 2009 00:07:04 +0200 Von: Michael Zanetta An: gentoo-catalyst@lists.gentoo.org Betreff: Re: [gentoo-catalyst] Stage1 app-arch/lzma-utils-4.32.7 fails Well, that might not solve your blockers anyway... You can eventually remove all the binary packages, remove the autoresume point and try to rebuild the stage1. Thanks a lot for your hint! That solved some of my problems. I did as you proposed, then ran stage1-3, livecd-stage1 and now I'm stuck at livecd-stage2. world has util-linux-2.16, genkernel requires e2fsprogs and e2fsprogs blocks util-linux-2.16 . I could try to remove util-linux from my stage3 source before building stage1-3 (already did that with man-pages-2.x, which was blocking man-pages-3), but I'm not sure yet, if util-linux is actually required by something. But then I wonder why genkernel depends on e2fsprogs? I could create a livecd without a ext2 filesystem, right? (using other fs types). genkernel could have a use-flag for e2fs then, or so. Or did I miss something? It sounds like you're using mismatched snapshots and/or stage seeds. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Stage1 app-arch/lzma-utils-4.32.7 fails
On 08/24/2009 04:09 AM, "Andreas Rückert" wrote: Hi! Original-Nachricht Datum: Sun, 23 Aug 2009 15:35:55 -0500 Von: Andrew Gaffney An: gentoo-catalyst@lists.gentoo.org Betreff: Re: [gentoo-catalyst] Stage1 app-arch/lzma-utils-4.32.7 fails Catalyst doesn't see that non-zero exit code. All catalyst does it call portage, which then does the extracting. And portage passes the exit code to catalyst which stops the build process, right? Yes, but that's not a catalyst problem. Hmmh...what's the solution, you would propose? It's just because in console, portage installs (and obviously extracts) the lzma-utils just fine, which confuses me a bit... It's a binpkg that failing to emerge in catalyst. Are you absolutely positive that you're testing with the same binpkg? You can try just deleting that particular binpkg and letting it compile again. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Stage1 app-arch/lzma-utils-4.32.7 fails
On 08/23/2009 02:22 PM, "Andreas Rückert" wrote: Hi! Original-Nachricht Datum: Sun, 23 Aug 2009 10:15:21 -0500 Von: Andrew Gaffney An: gentoo-catalyst@lists.gentoo.org Betreff: Re: [gentoo-catalyst] Stage1 app-arch/lzma-utils-4.32.7 fails On 08/23/2009 05:34 AM, "Andreas Rückert" wrote: A manual tar tjvf complains about trailing garbage. emerge in console works just fine. Could it be, that catalyst is confused by a non-0 return value from tar (although tar ignores the problem) and stops the build? Catalyst doesn't see that non-zero exit code. All catalyst does it call portage, which then does the extracting. And portage passes the exit code to catalyst which stops the build process, right? Yes, but that's not a catalyst problem. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Stage1 app-arch/lzma-utils-4.32.7 fails
On 08/23/2009 05:34 AM, "Andreas Rückert" wrote: A manual tar tjvf complains about trailing garbage. emerge in console works just fine. Could it be, that catalyst is confused by a non-0 return value from tar (although tar ignores the problem) and stops the build? Catalyst doesn't see that non-zero exit code. All catalyst does it call portage, which then does the extracting. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Catalyst examples with newer profiles
On 08/18/2009 04:20 AM, "Andreas Rückert" wrote: Hi! I'm trying to create a livecd, but I'm running into problems with the e2fsprogs(-libs) stuff. So I wanted to check the latest examples (spec-files). But it seems, they still use the 2006.x profiles? Are there current example files with 2008 profiles? The profile does not matter. Your problem is that you're using older stages. You need to build a full set of stages with the same snapshot that you're using to build the LiveCD. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Creating an iso image with no snapshot
On 08/06/2009 11:34 PM, Tom Stellard wrote: I noticed that when I build a liveCD, the portage snapshot I used to build the stages is included in the iso file. Is there a config value I can set so that the snapshot is not included in the iso? Use generic-livecd instead of release-livecd for livecd/type. The release-livecd is intended for use by releng, and you'll get all the "automatic" behaviors that releng expects. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Feature Request: mount tmpfs on /var/tmp/portage
On 08/03/2009 02:15 AM, Tom Stellard wrote: I would like to have the ability to mount a tmpfs on /var/tmp/portage when I am building a stage. I have attached a patch that adds this functionality to catalyst. This patch adds a new option "tmpfs" and the config value "tmpfs_opts". tempfs_opts can be used to set the size of the tmpfs. It uses the same syntax as options passed to mount -o. For example tempfs_opts="size=1G,nr_inodes=10". -Tom Please file a bug for this. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Mounting squashfs fails
On 08/03/2009 07:44 AM, lurker wrote: Mounting squashfs filesystem mount: mounting /dev/loop0 on /newroot/mnt/livecd failed: Invalid argument This is caused either by having an too-old kernel with squashfs-tools-4.0 or a too-new kernel with squashfs-tools-3.x. If you're using a >=2.6.29 kernel, you'll need squashfs-tools-4.0 to create the squashfs image. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Building x11-base/xorg-server with the proper INPUT_DEVICES and VIDEO_CARDS
On 08/01/2009 04:10 AM, Tom Stellard wrote: I am trying to build a gentoo liveCD using catalyst, and I would like to build x11-base/xorg-server using the exact same configuration that is used by the official gentoo liveCD. Do I need to define INPUT_DEVICES and VIDEO_CARDS somewhere before building the liveCD, or does catalyst take care of this for me? Catalyst doesn't do anything here. However, the profiles define a default INPUT_DEVICES and VIDEO_CARDS that should work for everyone in most cases. The only real reason to define them yourself is to make it build *less*. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] DT_RPATH DT_RUNPATH in x86 stage4 binaries built on amd64
On 07/25/2009 11:43 AM, Peter Stuge wrote: I just filed a bug about this: http://bugs.gentoo.org/show_bug.cgi?id=279071 Would appreciate any input. That has nothing to do with catalyst, except that it's a stage4. For building packages, catalyst just calls emerge. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Should catalyst depend on dosfstools?
On 06/18/2009 04:54 PM, Juan Luis Pérez Pérez wrote: So, if catalyst needs mkdosfs maybe it would depend on dosfstools. Do I report this to bugzilla? Please file a bug against catalyst. Instead of having the ebuild unconditionally depend on something that's only needed for ia64 and x86/amd64 (when using EFI support), I'd rather add a run-time check into catalyst for tools that it will need. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Gentoo install LiveCDs autobuild spec files
On 06/18/2009 05:23 AM, Juan Luis Pérez Pérez wrote: Hi, where could I download install-x86-minimal LiveCD spec file? I would like to base my own LiveCD on this one, but the newest ones I found are specs for gentoo-2007.1, I know there is autobuilds for Gentoo LiveCDs, but I don't know where they are in sources.gentoo.org. http://sources.gentoo.org/viewcvs.py/releng/trunk/releases/weekly/specs/ -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] ccache cache deleted during stage2 build
Please file a bug about this. Tom Stellard wrote: > I am using the latest version of catalyst from git(commit > 16745ae35961557a1205b5c86419d1aa496fcdf7). I noticed that when the > stage2-preclean-chroot.sh script calls cleanup_stages() in > chroot_functions.sh, it deletes everything in $CHROOT_PATH/var/tmp, > but since $CHROOT_PATH/var/tmp/ccache is still bound to > /var/tmp/ccache my cache that lives outside of the chroot is cleared > as well. I have attached a patch that appears to fix the problem. I > am not sure if there are any ill side-effects from this patch, but > since the "clean" action sequence also clears /var/tmp/*, is it really > necessary to do it in the stage2-preclean-chroot.sh script? > > -Tom Stellard > -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] GSOC: Making the cluster LiveCD bootable from USB
Tom Stellard wrote: > For Google Summer of Code, I am interested in working on a project to > make the current Gentoo cluster LiveCD bootable from a USB device. I > have been using catalyst to build the current version of the LiveCD, > so I can test it out, and I have a few questions: > > It was mentioned on the gentoo-soc list that the next version of > catalyst would allow you to build stages 1-4 with only one call. Is > this feature planned, and if so what is the current progress? This is a planned feature for catalyst 3.x, which I have started work on, but it's not ready for use yet. > When catalyst is building a stage, is there a way to execute a script > after catalyst has entered the chroot environment to do something like > mount tmpfs on /var/tmp/portage? No. However, I'm entertaining the idea for catalyst 3.x. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Almost all files in /dev disapeared in stage2
Guillermo M. Narvaja wrote: > My generated stage2 lacks many files in /dev. You need to use catalyst-3.4.10.903 (or maybe even -). This was a bug that releng ran into recently once portage-2.1.6.x was stabilized. Some old questionable code in catalyst finally broke due to a behavior change in portage which causes the default /dev nodes to not be generated in the stage1 creation. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] root console on boot
lurker wrote: > On 10/02/09 23:27, Andrew Gaffney wrote: >> lurker wrote: >>> On 10/02/09 22:28, Mike Frysinger wrote: >>>> try grepping the init.d scripts. or look at the source scripts >>>> from catalyst itself (iirc, there's a "livecd support" dir or >>>> some such). >>> I've recursively grepped every file in /usr/lib/catalyst, >>> /usr/share/genkernel, /etc and the initrd, and I found nothing. >>> Have I missed anything (I must have!)? >> The files you're looking for are part of livecd-tools. There's a >> function called livecd_fix_inittab() in livecd-functions.sh that >> rewrites the CD's inittab to call the bashlogin script instead of a >> login process. > > Thanks a lot! > >> However, I'm not sure what actually calls the livecd_fix_inittab() >> function in the first place. > > FYI, after some grepping I found from where it is called: /sbin/rc, > around row 500 (this is with baselayout-1.12.11.1). > > I could be off here, but wouldn't it be better if catalyst made these > changes to /etc/inittab in livecd-stage2 instead? If you look at the livecd_fix_inittab() function, it makes decisions on what to write to /etc/inittab based on the /dev nodes that are present. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] root console on boot
lurker wrote: > On 10/02/09 22:28, Mike Frysinger wrote: >> try grepping the init.d scripts. or look at the source scripts from >> catalyst itself (iirc, there's a "livecd support" dir or some such). > > I've recursively grepped every file in /usr/lib/catalyst, > /usr/share/genkernel, /etc and the initrd, and I found nothing. Have I > missed anything (I must have!)? The files you're looking for are part of livecd-tools. There's a function called livecd_fix_inittab() in livecd-functions.sh that rewrites the CD's inittab to call the bashlogin script instead of a login process. However, I'm not sure what actually calls the livecd_fix_inittab() function in the first place. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] chroot: cannot run command `/tmp/livecd-stage1-chroot.sh': Permission denied
Caleb Cushing wrote: > chroot: cannot run command `/tmp/livecd-stage1-chroot.sh': Permission denied My guess is that you've got /var, /var/tmp, or /var/tmp/catalyst mounted with noexec. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] mkisofs failed with "Unknown charset" error
Fred Elno wrote: > I have found that the error must come from the -l option which is passed with > catalyst, when I manually run the > command, -l option change the charset to ISO-8859-1 which one is found in my > locale, but when the command is run from > catalyst > the script failed and mkisofs is unable to find my ISO-8859-1 charset from my > locale. I'm not sure where you got the impression that the -l option has anything to do with character sets. According to the man page, it just controls whether filenames are allowed to be 31 characters vs. the MS-DOS 8.3 restriction. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] blocked packages com_err ss e2fsprogs during stage3
Dio, James wrote: Thank you for your response, in an effort to make sure that everything is using the same snapshot, I have done everything over again and have the same issue, and included the spec files I used. I had wanted to purge everything catalyst has produced so far, however when I ran catalyst --purge, I get the following error: !!! catalyst: please specify one of either -f or -C When I specify both --purge and -f (some spec file) it attempts to build the stage instead of purge. Should I open a bug for this? No, that's how it's supposed to work. The purge isn't an operation all by itself. It's just an additional step that's performed before a build. Here's what I did: emerge --sync catalyst -s rwmc.001 catalyst -f rwmc-stage1.spec catalyst -f rwmc-stage2.spec catalyst -f rwmc-stage3.spec rwmc-stage1.spec contains: subarch: x86 target: stage1 version_stamp: rwmc.001 rel_type: default profile: default/linux/x86/2008.0 snapshot: rwmc.001 source_subpath: default/stage3-i686-2008.0 chost: i686-pc-linux-gnu rwmc-stage2.spec contains: subarch: i686 target: stage2 version_stamp: rwmc.001 rel_type: default profile: default/linux/x86/2008.0 snapshot: rwmc.001 source_subpath: default/stage1-x86-rwmc.001 chost: i686-pc-linux-gnu rwmc-stage3.spec contains: subarch: i686 target: stage3 version_stamp: rwmc.001 rel_type: default profile: default/linux/x86/2008.0 snapshot: rwmc.001 source_subpath: default/stage2-i686-rwmc.001 At first glance, everything here looks fine. I'm not sure what to tell you. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] blocked packages com_err ss e2fsprogs during stage3
Dio, James wrote: I had initially set out to create a new livecd, but ran into problems with blocks involving com_err ss e2fsprogs. I then realized that creating a livecd with a recent snapshot (Nov 20 2008) and the 2008.0 stage 3 wasn't the best way to go. I set out to create new stage 1, 2 and 3 tarballs. I was able to create the stage 1 and 2 (using the new snapshot) and am running into problems attempting stage3. Stage3 fails and below are the last few lines: [ebuild N] sys-libs/e2fsprogs-libs-1.41.2 [blocks B ] sys-libs/ss (is blocking sys-libs/e2fsprogs-libs-1.41.2) [blocks B ] If you're encountering blockers, then you did not build your seed stage2 (or stage1) correctly. The initial stage1 you built should have already had e2fsprogs-libs and the new e2fsprogs from the start. The fact that you're hitting the blocker tells me that your stage 1 or 2 was still using the 2008.0 snapshot instead of the one you're trying to build the stage3 with. You need to make sure you build *everything* with the same snapshot to prevent issues like this. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] How do I get /dev entries onto a livecd image?
Amit Dor-Shifer wrote: Sorry. Wrong there. I meant I want /dev/watchdog inside the loop, in the squashfs image. Does that change the answer? No, it doesn't. The only reason it works on your normal install is because a tmpfs is already mounted on /dev and udev is managing it. In the case of a LiveCD, it doesn't matter what you put in /dev in the squashfs, since it gets "hidden" when the tmpfs is mounted over it at boottime. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] How do I get /dev entries onto a livecd image?
Amit Dor-Shifer wrote: Hello again. I'm trying to get /dev/watchdog onto my CD. I'm using a squashfs fstype. The device is properly created by the kernel build stage, yet it doesn't end-up in the image. Seems the 'unbind' action unmounts /dev from the source before calling mksquashfs. Any ideas how to circumvent this problem? /dev is managed by udev on the LiveCD, the same as a normal install. You'll have to create a udev rule file that creates this device and add it to the LiveCD with livecd/overlay. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] Autoresuming hides modifications in config file?
Amit Dor-Shifer wrote: Is that the way autoresume's intended to work? If so, should I clear autoresume points upon every modification in a conf file? Catalyst doesn't store any metadata about the spec file for a particular build, so it has no way to know if the spec has changed. That will probably chance in the future. For now, just make sure to use -a when you change the spec file. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] How did package XYZ get into the liveCD?
Amit Dor-Shifer wrote: Here's /sbin/sfdisk in my stage1: disk_replace ~ # md5sum /var/tmp/catalyst/tmp/replace_disk/livecd-stage1-i686-101/sbin/sfdisk 68f84ca6f42380cb8594051dc7fd6e13 /var/tmp/catalyst/tmp/replace_disk/livecd-stage1-i686-101/sbin/sfdisk Andrew Gaffney wrote: Amit Dor-Shifer wrote: when catalyst builds a stage1, the stage1 itself does not inherit any binaries or libraries from the seed that is used. Is that FAQ obsolete? the "seed" is the original stage3, right? Looks like my stage1 (and the livecd stage too) did in-fact inherit binaries from the seed. That is true *only* of the stage1. Everything else inherits everything from its seed. livecd-stage1 != stage1 -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] How did package XYZ get into the liveCD?
Amit Dor-Shifer wrote: when catalyst builds a stage1, the stage1 itself does not inherit any binaries or libraries from the seed that is used. Is that FAQ obsolete? the "seed" is the original stage3, right? Looks like my stage1 (and the livecd stage too) did in-fact inherit binaries from the seed. That is true *only* of the stage1. Everything else inherits everything from its seed. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] How did package XYZ get into the liveCD?
Amit Dor-Shifer wrote: So, I'm confused. Which parts of the liveCD get built and which are just copied from the initial stage3 tarball? *Everything* is copied from the stage3 tarball. That's how catalyst works. Each step builds upon the previous step. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux DeveloperCatalyst/Genkernel + Release Engineering Lead
Re: [gentoo-catalyst] stage4 glibc ebuild stomps my locale.gen
Peter Stuge wrote: Hello, am new on this list but have been using catalyst a few years to build x86 stage4 systems. Lovely tool. glibc ebuilds insist on generating all locales. I find this quite annoying because I do not want them and it takes a lot of time. I find no relevant bug on b.g.o and want to check with you that I'm not just doing something silly. I think someone else should also have noticed this too. Yes, we've noticed. However, releng doesn't build stage4 tarballs, so we didn't care. I tried to add /etc/locale.gen to stage3-x86-2008.0.tar.bz2 but no. And how did you add a locale.gen to the stage3? You can't do it with catalyst, since stage <=3 doesn't support an overlay, so I can only assume you unpacked it, added the file, and repacked it, which we obviously don't support :) -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
Re: [gentoo-catalyst] Lions and Tigers and Forks, Oh My!
lurker wrote: On 28/07/08 18:18, Chris Gianelloni wrote: Just a little FYI for everybody on the list... I've gone and forked most of the Release Engineering tools. I no longer plan on maintaining the "Gentoo" versions of catalyst, genkernel, hwdata, or livecd-tools. Instead, I am working on these projects under my own domain and will be releasing them as "standalone" applications, not under the Gentoo moniker. Now, these projects always have been "Gentoo Hosted Projects" and not really owned by the Gentoo project, but continued issues from other developers has proven that many don't understand this case. As such, it was simply easier to break away from the main project. This also allows us greater flexibility in making changes that would otherwise not be accepted within Gentoo. All of the current maintainers of these forks will be working on them in their new homes, making the Gentoo-hosted versions essentially dead. Interesting development. Can we be confident that the new independent catalyst will not break the current interfaces (ignoring trivial changes) and the use of portage? More to the point: what does this mean for existing catalyst projects that are using portage and intend to stay with it? No, you cannot be confident of that. You never have been able to. We tend to "break" things all the time. However, we do our best not to :) Catalyst will always be compatible with portage (at least, we won't intentionally break it). We'll also be adding support for pkgcore and perhaps focusing more on that particular PM in the future. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
Re: [gentoo-catalyst] how do you resolve package conflict in stag4 builds
Joshua Hoblitt wrote: Hello, I attempted to rebuild my 2007.0 stage4 tarball today after making a new portage snapshot and it dies because of these conflicts (stage[123] builds OK). How exactly did you attempt to rebuild it? -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] HPPA catalyst liveCD won't boot
Derek Davis wrote: I'm trying to make an HPPA live CD using catalyst, but it seems that nothing is working correctly for me. The main problem that I'm running into now is that when I try to boot, palo says that it can't find any 32-bit kernels. I've even gone so far as to grab the kernel right from the working Gentoo liveCD, and I still get the same error, so I'm figuring that my problem is either how I'm making the iso or how I'm running palo on the iso, but both of those commands I pulled right from catalyst. First you say you're using catalyst and then you say that you're running commands by hand that you copied from catalyst. Which is it? -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] Making emerge's catalyst use a proxy
Daniel van Ham Colchete wrote: The question is: how do I make catalyst use my proxy to download things? I would have to change emerge's make.conf inside the package and I don't know how to do it. Set HTTP_PROXY (or whatever the var is) in your envscript (/etc/catalyst/catalystrc by default). -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] [RFC] Summer of Code Proposal: GNAP Love
Philipp Riegger wrote: Good morning, I have some ideas for Summer of Code which i'd like to discuss with you. I'm mostly interested in making GNAP usable and my proposal includes lots of tasks in GNAP and catalyst, of which i'd like to finish as many as possible and do some research on the rest. catalyst tasks: • Squashfs snapshot support I don't like it, that it takes so much time to unpack a new snapshot and it takes so much disk space to store it. Plan is: distribute tree snapshots as squashfs images, mount them directly into the workdir, use /mnt/distfiles and /mnt/packages instead of snapshot subdirectories. Eh, I've never found unpacking a new snapshot to be all that cumbersome. While it probably wouldn't take much to implement this, I don't like the idea. At least, I'd never use it, since it would remove the ability to poke around in the snapshot_cache. • (Squashfs seedstage support) Maybe the same is possible for stages? A future plan for this could be to mount the squashfs image directly and use unionfs for the real work, but i have no idea how deleting files in such a setup works. Research is necessary here. This isn't really feasible. • uclibc-cross-compiling support Cross compiling is hard, but it should be possible to build arch-uclibc from arch. Research, what needs to be done combined with the implementation, if possible. This would also make GNAP more flexible. If you want a uclibc stage, use a profile that has uclibc as the default virtual/libc provider. • Documentation In an email from some days ago i read, that documentation is planed for after the release. I could support this and proofread it, since i need the knowledge anyway. It's planned for some time in the future when the people who have the knowledge to write the documentation find the time and motivation. • (Code cleanups) I write this everywhere, but since i need a basic understanding, i have to read (parts of) the source and maybe i find something worth improving. Catalyst is definitely in need of code cleanups. However, that's just a result of a codebase that's changed hands multiple times over many years. We do random cleanups already as we encounter code that needs it. • Cross compiling research This is the continuation of the uclibc stuff with some plans on what could be done how. Like I said on IRC, this is vapier's territory. • Non-root builds research Wouldn't it be nice if being root was not necessary for using catalyst? I would like to look into the possibilities there and what is needed to make it reality. Mostly, this would require the ability to do "random" bind-mounts and chroot. The only "sane" way to do this is to make catalyst suid root. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] livecd-stage1 problem
Robert C Corsaro wrote: The catalyst page points to the newbie wiki as the best source of documentation. What catalyst page? We don't point to gentoo-wiki in any official gentoo documents. If you're talking about the catalyst page on gentoo-wiki, again, we don't know or care :P -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] livecd-stage1 problem
Robert C Corsaro wrote: Andrew Gaffney wrote: Robert C Corsaro wrote: Perhaps I need a newer stage3? Yes, you do. You should *always* build a full set of stages (1-3) using the same snapshot you're using to build your CD. This avoids upgrade problems like this. Should I update that howto? It recommends getting the stage3 off a mirror. If you want. We didn't write it, nor do we maintain it. Everything on gentoo-wiki is completely unofficial, which usually means that it's wrong to some degree or another. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] livecd-stage1 problem
Robert C Corsaro wrote: Perhaps I need a newer stage3? Yes, you do. You should *always* build a full set of stages (1-3) using the same snapshot you're using to build your CD. This avoids upgrade problems like this. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] concerning USE flags
Lanza Fabrizio wrote: Hi, I'm sorry if this question might have been asked a thousand times, but I cannot find a solution. I also read the howtos that I could find, included the documentation that is currently removed from the gentoo site. The question is, where do I tell Catalyst the correct USE flags for a specific program? I tried in portage.config. It did not catch it. I put it in /var/tmp/catalyst/tmp/mycd/livecd-stage1.../etc/portage/package.use. Same. I put it in /var/tmp/catalyst/tmp/mycd/livecd-stage2.../etc/portage/package.use. Same. I know that Catalyst does not read package.use as expected. But I don't see how to do then. I suspected that, if I run catalyst again without removing the whole livecd-stage, it won't rebuild my package with the new USE flags. So, I removed the whole livecd-stage2, modified the USE flags, added my package that needed a rebuild with the correct flags, and rebuilt livecd-stage2 completely. But still it was built with the wrong flags and failed. I will appreciate if you can point me to the right direction. Thank you! Are you using 'livecd/use: -* ...' in your spec? if so, this will cause portage to completely ignore package.use. This is "normal" behavior and has nothing to do with catalyst. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] filesystem not readable
Lanza Fabrizio wrote: Hi, I'm using the last dev version of catalyst, r9. When my .iso was There has't been a -r9 of catalyst in a long time, if ever. If you're referring to _pre9, that's not the latest. It's also package.mask'd, which implies that there's a good chance it's broken, and if you choose to use it, you should have some skill in tracking down, or at least reporting, bugs. completed and burned, I noticed that I can read the contents of the CD only from linux. Windows cannot read it, and sees it as blank. I found that it was a bug, but I lost the link now. A bug in what? Catalyst? cdrkit/cdrtools? Are we supposed to track it down for you? Does anybody know how I can fix this? Which packages does Catalyst use in order to prepare the iso? If I update those, probably the error won't happen any more. The only error report we've seen recently that's somewhat recently was on this mailing list. The ISO image was rejected by Nero when it was larger than 700MB. There is no "fix", since there's nothing broken (except Nero). -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: R: [gentoo-catalyst] producing a DVD
Lanza Fabrizio wrote: Unless catalyst has some "magic" to figure out to build an image with a UDF filesystem instead of ISO9660 (and I'm pretty sure it doesn't), you can burn a 700MB ISO to a DVD and it will work just fine. That is exactly what I cannot do. I insert a DVD in the CD/DVD drive. I start Nero, choose "burn image", I select my .iso, and it ejects the DVD saying that I have the wrong medium, and that it is supposed to be a CD. Every CD/DVD mastering software will check what you are going to burn. If it has a CD project/filesystem, it won't burn it on a DVD. Also, since qemu does not load CDs larger than 700M... there is a problem. I also noticed a curious thing. When I mount the .iso (larger than 700M) with a program such as Daemon Tools, it won't show the filesystem. It shows as it is completely empty. I managed to convert the big .iso to a DVD .nrg with Nero, and I could burn it indeed. It boots fine, but it has the same problem that the filesystem is not visible. I would rather find out the way I can get a DVD iso with Catalyst. I already told you. Catalyst doesn't do anything special for DVDs, and the larger ISO images it generates work just fine. There is zero support for creating UDF images in catalyst. Use another program to burn the image. Nero obviously has an issue. Burning a larger ISO with cdrecord works without a problem. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] mkxf86config: Virtualbox experience
Pongracz Istvan wrote: Hi, I use virtualbox/qemu to test the livecds. I know, I will not really popular, but I expected that, if mkxf86 could not detect the video card, it left empty the driver, instead of vesa driver. Their video card name is a really strange name. Is that possible to make the default driver to "vesa", instead of ""? It should already do this. Are you sure you have x11-drivers/xf86-video-vesa on your CD? I believe it checks to make sure the driver exists before sticking it in the xorg.conf. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] producing a DVD
Lanza Fabrizio wrote: Hi, I need to produce a DVD instead of a CD .iso. How do I tell catalyst to produce a DVD? Should I change fstype? Thank you. Ugh, please don't reply to another thread to start a new one. It screws up the threading in Thunderbird (and probably other mail clients). Unless catalyst has some "magic" to figure out to build an image with a UDF filesystem instead of ISO9660 (and I'm pretty sure it doesn't), you can burn a >700MB ISO to a DVD and it will work just fine. For the past few releases, we've released >1GB standard ISO images for use on a DVD, and nobody has reported a problem booting them. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] Catalyst 2.0.6_pre9 mksquashfs hangs building squashfs + solution
Chris Gianelloni wrote: On Mon, 2008-02-25 at 22:58 +0100, Pongracz Istvan wrote: Probably the situation is not the same, I did not compared it to my version (3.3). This also happens if you're using mksquashfs 3.3 and trying to make a 3.1 squashfs, like would be done if your kernel is 2.6.23 and you're using ~arch on your build machine. We *want* the sparse option, so the "fix" is to use the right version of mksquashfs for the kernel you're building/deploying. Eh, he was talking about mksquashfs hanging while creating the squashfs image, not about the kernel freaking out while trying to mount it. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] Req: non-standard lcd displays
Pongracz Istvan wrote: Hi, I use catalyst to create customized livecd-s with preinstalled X, database and web servers to demonstrate open source applications to the public, usually non-technical people. Some of them use laptops and/or non standard LCD displays (1280x800, 1400x900 etc.). AFAIK catalyst uses the x11-misc/mkxf86config tool to detect and setup the X. Catalyst doesn't use anything. You are specifying mkxf86config in your spec, and it's getting run automatically by autoconfig (part of livecd-tools). You are free to use something else. The main problem is, it cannot setup the dimension properly and the display shows an ugly, stretched image, which is not really looks good on a presentation. Example: the X uses 1024x768 on a 1280x800 display. The result is a working, but ugly X. My question, is that possible to improve it? Do you have a patch? I read that, the author of mkxf86 knows this issue and he/she is open to improve it, but I do not know his mail :) He wrote, this is hard-wired to make it cross-compatible. Anyway, what about that to look into ubuntu/mandriva, how they solved this issue? I know, for example the i915 chipset has a problem, which needs a bios patch to get it work (it is a crap, I have this on my laptop). I'm pretty sure, this is not a trivial task, but it would be really good :) If you're building this CD for a specific computer, use livecd/root_overlay to put a custom pre-made xorg.conf on the CD and remove mkxf86config from the package list. This will "solve" your problem. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] Catalyst 2.0.6_pre9 mksquashfs hangs building squashfs + solution
Pongracz Istvan wrote: Hi, This evening I run into a problem, when I built my custom livecd. It contains an installed and configured postgresql and one of its file had something, which caused to mksquashfs hanged up. So, after I append the -info (mksquashfs argument), I caught a file, which caused the problem several times. After asking my old spanish friend (Manual) and google, I used the -no-sparse argument to avoid hanging mksquashfs. After it I succeed to create the image. I am not sure, but it seems, it is safe to use the -no-sparse argument to avoid some problems. Just my experience. Are you sure it was hung? Was it just trying to squash a very "large" sparse file? Can you give us the URL that gave you the idea to use -no-sparse? -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] Build stage4 ssmtp conflicts with postfix.
Chris Gianelloni wrote: On Fri, 2008-02-22 at 11:34 -0600, Andrew Gaffney wrote: I am building stage4, but he return error where ssmtp conflicts with postfix. I trying configure virtuals in my profile to set postfix virtual mta, but not work. Somebody can help me? This is a portage bug and has nothing to do with catalyst. You'd encounter this same problem when emerging the same packages in a stage3 chroot. No, it is a portage feature. You cannot install two packages which block each other. If you want postfix in your stage4, build a set of lower stages (you should *always* do this, anyway) with your customizations (like virtual/mta being postfix) and then rebuild your stage4. The "bug" I was referring to was that portage will show a blocker when you do something like 'emerge vixie-cron postfix', even though postfix satisfies the virtual/mta that vixie-cron RDEPENDs on. Like Chris said, the only way around this is to change the default provider for virtual/mta in the profile you're using in your snapshot. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] catalyst related kernel problem?
lurker wrote: On 21/02/08 05:40, Chris Gianelloni wrote: On Wed, 2008-02-20 at 21:38 +0100, lurker wrote: genkernel fails to add busybox with cpio (this is with genkernel-3.4.9 and catalyst-2.0.6_pre6): Please try catalyst-2.0.6_pre8, which is pretty new and should work just fine for whatever you need. Also, check out genkernel-3.4.10_pre3, which I literally just added to the tree. Also, my system runs stable amd64 Gentoo, but I run catalyst in a i686 chroot to protect my main system. Could that have anything to do with this? Ehh, this very well could be causing you all kinds of problems. I have now tried running catalyst-2.0.5 natively from my amd64 system (i.e. no chroot) and I still got the same error. Even with the latest genkernel. I emerged 2.0.6_pre9, but it crashed during action sequence clean on livecd-stage1, complaining about that the chroot's kerncache directory couldn't be deleted. I might file a bug for this later if I get time, it's just that I'm really pressed getting catalyst to actually build an iso as I have a release schedule... You must have a really weird setup. Again, as part of the release cycle, many of us have been testing the latest versions of catalyst and genkernel, and we have not hit this issue, either. Kerncache has been functioning beautifully for me. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] Build stage4 ssmtp conflicts with postfix.
Oliveiros Peixoto wrote: Hi. I am building stage4, but he return error where ssmtp conflicts with postfix. I trying configure virtuals in my profile to set postfix virtual mta, but not work. Somebody can help me? This is a portage bug and has nothing to do with catalyst. You'd encounter this same problem when emerging the same packages in a stage3 chroot. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] catalyst related kernel problem?
lurker wrote: When I set up that chroot I didn't know that catalyst was able to generate x86 stages from amd64 systems, so that was my reason for creating it. I will install catalyst and genkernel on my main system instead and work from there, and if that fails upgrading to the latest versions. You don't need genkernel on your host system. It's emerged inside catalyst's chroot when it's needed. But even if that fixes it, I would very much like to know what was going on. From my debugging I have pretty much confirmed that it's that find/cpio call that fails, but I cannot grasp why at all. Few bugs have left me this perplexed. We are right in the middle of a release cycle with a couple of people doing repeated catalyst builds, and nobody is hitting this bug. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] reference manual gone?
M. Edward (Ed) Borasky wrote: Chris Gianelloni wrote: On Thu, 2008-02-14 at 03:41 +0100, lurker wrote: What's going on? I removed it because it was incorrect and I got tired of people using it, then complaining that it's incorrect when the entire top of the manual explained how it was incorrect. Basically, I got tired of people not reading, then complaining to me about it. We'll be putting up a new manual once we get one written. Realize that the "2.x" manual was *nothing* more than the 1.x manual renamed. It had no useful content for anyone, really. The best (and only) official documentation is the example specs, which are installed automatically by catalyst. Speaking of example specs, are the ones for 2008.0 available publicly yet? Yes, but they're still a work in progress, which they will be right up until we actually release. They're available from the shiny new releng repo in gentoo's SVN. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] fooling uname
lurker wrote: On 14/02/08 04:01, Andrew Gaffney wrote: lurker wrote: Greetings list, Currently catalyst (2.0.5, 2.0.6pre4) doesn't seem to change what uname outputs. uname -r, for example, prints the version of the kernel running catalyst, not the kernel that's in the stage. Of course, that's how it is, but isn't it possible to hack that somehow? It's a bit tedioius to patch everything that depends on uname (e.g. the raling-rt61 ebuild). Can the "uname string" be set by some envirnoment variable in an env script specified in the spec file? Any ebuild that depends upon the output of uname is broken and should be fixed. Sorry, I meant the compile scripts, e.g. the Makefile of ralink-rt61. Whether it's the ebuild or the package's build system, it's still broken. Doing crap like this makes it impossible to build a package for another machine that's not running the same kernel. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] forcing a package to recompile
Lanza Fabrizio wrote: Hi, I am using catalyst for a livecd. When I reached livecd-stage1, one package failed because it needs qt compiled with different USE flags. I have all the autoresume, autochache, and whatever, set for catalyst. I already put the correct USE flags in package.use, but basically I cannot get qt recompiled. So, it always hangs at the same place. Is there a way to tell catalyst that qt is not installed, so that it will install it again? Or a way to force its reinstall? I could delete it also from the temp snapshot... but what would I have to delete? Are you using -* in your livecd/use? If so, that overrides anything set in package.use. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] fooling uname
lurker wrote: Greetings list, Currently catalyst (2.0.5, 2.0.6pre4) doesn't seem to change what uname outputs. uname -r, for example, prints the version of the kernel running catalyst, not the kernel that's in the stage. Of course, that's how it is, but isn't it possible to hack that somehow? It's a bit tedioius to patch everything that depends on uname (e.g. the raling-rt61 ebuild). Can the "uname string" be set by some envirnoment variable in an env script specified in the spec file? Any ebuild that depends upon the output of uname is broken and should be fixed. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] livecd
Tais M. Hansen wrote: The other part is sqashfs. Apparently something is wrong with the generated squashfs image. I'm getting "Invalid argument" error when trying to mount it on the livecd and the following errors when I try to mount it on the build system, where catalyst is run: Nothing is "wrong" with squashfs. It's just that squashfs-tools-3.3 generate the squashfs in a different format than 3.2, and gentoo-sources-2.6.24 is the first kernel that's patched with support for the new 3.3 format. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] livecd
Tais M. Hansen wrote: Hi, I'm trying to build a new livecd with catalyst but it seems like no matter what I do, when the cd boots, it fails miserably mounting the cd. Booting with the debug option gives me a shell and I can manually mount the cd just fine. There must be some problem with the init script but I can't seem to figure out what? This is a problem with genkernel-3.4.9. It's already fixed in SVN, and we'll be releasing 3.4.10_pre1 soon. In the mean time, you can apply the patch 208477 or use genkernel-3.4.9_pre6. Also, you'll likely run into a problem with mounting the squashfs loopback. You need to make sure you're using =gentoo-sources-2.6.24. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] setarch blocked by util-linux
Mike Frysinger wrote: On Tuesday 05 February 2008, Derek Fedel wrote: Ah, silly me. I should've figured it was something along those lines, but I had read mention of catalyst not forcing setarch anymore in the ChangeLog and got confused, I guess. Thanks, and sorry for the now seemingly inane question. please fix your quoting ... top posting is the devil I concur :P On Feb 5, 2008 8:16 AM, Andrew Gaffney <[EMAIL PROTECTED]> wrote: Derek Fedel wrote: I know! I know! 2.0.5 isn't supposed to have this problem. Let me explain, I've got a brand new install of 2007.0, a fresh copy of portage, and this as my spec file: How many times do we have to say this? :P If you're going to build your own CD, you also need to build your own set of stages with the same snapshot. This is the *only* way to completely avoid the various upgrade blockers that occur in the tree. is there a catalyst/stages FAQ ? if not, there should be ... Are you volunteering? :) -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] setarch blocked by util-linux
Derek Fedel wrote: I know! I know! 2.0.5 isn't supposed to have this problem. Let me explain, I've got a brand new install of 2007.0, a fresh copy of portage, and this as my spec file: How many times do we have to say this? :P If you're going to build your own CD, you also need to build your own set of stages with the same snapshot. This is the *only* way to completely avoid the various upgrade blockers that occur in the tree. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] livecd stage1 kernel .config
Greg Fitzgerald wrote: Thanks for correcting me. I had already gone about setting -gnome though and solved that. Moved onto the livecd-stage2.spec and that went fine. Now when I boot the iso imagine I get the following error. mount: Mounting /dev/loop0 on /mnt/newroot/livecd failed: invalid argument Started searching around for this error. Found a possible solution by editing the squashfs imagine but I have no idea if that will work and its very hackish. Wondering if someone might know what I did wrong. Using the stable version of genkernel of course. Two things I did read about was some people had luck with squashfs compiled as a module others had better luck with it compiled into the kernel. I have tried both ways now. Are you sure you have loop device and squashfs support enabled in your kernel? -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] catalyst related kernel problem?
Åsmund Grammeltvedt wrote: On Tuesday 08 January 2008 15:34:09 lurker wrote: Greetings, Often when I build systems with catalyst I encounter the following kernel freeze after the boot loader has completed: [ ... lots of kernel loading stuff which seems ok ... ] Freeing unused kernel memory: 172k freed request_module: runaway loop modprobe binfmt- request_module: runaway loop modprobe binfmt- request_module: runaway loop modprobe binfmt- request_module: runaway loop modprobe binfmt- request_module: runaway loop modprobe binfmt- I had an issue with the same symptoms. It turned out that after some builds, the initramfs would contain empty files instead of links to busybox. In my case, the only way I could get it to work consistently was to patch genkernel to use symbolic links instead, when setting up the initramfs. It would be nice if you would file a bug about this with as much information as you have. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] livecd stage1 kernel .config
Greg Fitzgerald wrote: I went and created stages 1-3 and I am now working on my livecd stage1. My spec file is as follows: subarch: amd64 version_stamp: installer-2007.0 target: livecd-stage1 rel_type: default profile: default-linux/amd64/2007.0/desktop snapshot: 20080104 source_subpath: default/stage3-amd64-20080104 livecd/use: branding livecd socks5 livecd/packages: --- lots of packages here --- It compiles around 400 packages then dies on gnome-menus which requires a .config file in my kernel sources directory. Wondering how to solve this issue. I am new to making a livecd with catalyst, but my understanding is you set the .config file for your kernel in your livecd stage2. I tried to copy it to the livecd cache directory under /usr/src/linux and starting again with -a but it appears to get deleted when I start again. Can anyone let me know how I should proceed from here? There are a couple of ways around this, but you probably won't like any of them. 1) switch to xfce4, which doesn't bring in gnome-menus (the way I'd go) 2) modify the ebuild in your snapshot to bypass the kernel feature check 3) modify linux-info.eclass in your snapshot to not fail like this 4) give up -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list
Re: [gentoo-catalyst] chost setting for later stages
John Eckhart wrote: I just upgraded from catalyst-2.0.4 to catalyst-2.0.5_pre6 and some of my existing build scripts broke. One of the scripts broke because chost is now only valid in stage1 and stage2 builds. This was introduced in svn ver 1237, the ChangeLog reads: 22 Aug 2007; Andrew Gaffney <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> modules/generic_stage_target.py, modules/stage1_target.py modules/stage2_target.py 'chost' option is only valid in stage 1/2 specs. have catalyst error otherwise How do I chose what chost to build later stages? Is this always set by the stage2 chost? I was never changing it from stage2 on but previously it was always set in the spec file. Setting chost in stage3.spec is a no-op. Catalyst doesn't do anything with it. I added this error so people wouldn't think it was doing something that it wasn't. It's a very bad idea to change CHOST between stage 2 and 3. If you think you have a reason to do it, you're wrong :) -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Building stage3 fails because of no C++ compiler
Stephen Fromm wrote: I resolved this by specifying unique pkgcache_path values for all catalyst targets (eg /var/tmp/catalyst/packages//). Or just don't specify pkgcache_path at all and catalyst will provide a sane default. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] no stage1 created
Andrew Gaffney wrote: Nelson Batalha wrote: Citando Andrew Gaffney <[EMAIL PROTECTED]>: Robert Šmol wrote: Hello, I'm trying to follow the guide at http://gentoo-wiki.com/HOWTO_build_a_LiveCD_with_Catalyst_for_newbies , There's your first problem. I wrote that guide, there's no problem there. I was referring to gentoo-wiki in general. However, when I last looked at that article on the wiki, there were quite a few "inaccuracies". I fixed a bunch of them at the time, but I haven't looked at it since, and I don't recall what they were. Actually, I take that back. It was the "HOWTO build a LiveCD with Catalyst" article I was thinking about. I've never looked at your entry. I apologize. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] no stage1 created
Nelson Batalha wrote: Citando Andrew Gaffney <[EMAIL PROTECTED]>: Robert Šmol wrote: Hello, I'm trying to follow the guide at http://gentoo-wiki.com/HOWTO_build_a_LiveCD_with_Catalyst_for_newbies , There's your first problem. I wrote that guide, there's no problem there. I was referring to gentoo-wiki in general. However, when I last looked at that article on the wiki, there were quite a few "inaccuracies". I fixed a bunch of them at the time, but I haven't looked at it since, and I don't recall what they were. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] no stage1 created
Robert Šmol wrote:
OK, I was reading official docs yesterday and it seems there is only
reference guide, but no high level view on how things works together. So
first, thanks for the newbie guide. Is there any documentation about
what exactly is catalyst trying to do at any specific moment?
A more "high level" guide for catalyst will come later as we "stabilize" the
inner workings of catalyst-2.x and get the reference guide finished.
Anyway:
At livecd-stage2_template.spec you refer to livecd1:
source_subpath:default/livecd-stage1_example-2007.1
and form reference guide:
source_subarch: "Location of seed stage, path relative to
${clst_sharedir}/builds"
and I actually found it at:
/var/tmp/catalyst/tmp/default/
Well, catalyst actually looks in two places. It will first look under
/var/tmp/catalyst/tmp/${source_subpath} and try to rsync the contents. If that's
not found, it will look for /var/tmp/portage/builds/${source_subpath}.tar.bz2
and try to untar that.
In the case of livecd-stage1->livecd-stage2, there is no .tar.bz2 file, but
there will be stuff in the first location from the livecd-stage1 build.
* Creating minimal kernel package
cp: cannot stat `/var/tmp/genkernel/System.map- 2.6.22-gentoo-r8': No
such file or directory
* ERROR: Could not copy System.map for the kernel package!
You need to stabilize a newer genkernel (3.4.9_preX is fine) in your snapshot.
This is a bug in genkernel-3.4.8.
--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] no stage1 created
Robert Šmol wrote: Hello, I'm trying to follow the guide at http://gentoo-wiki.com/HOWTO_build_a_LiveCD_with_Catalyst_for_newbies , There's your first problem. However no livecd-stage1 was created. What are you expecting? Do I miss anything obvious (I have 2.0.5_pre3 installed)? Yes, you're missing knowledge of what livecd-stage1 actually does. livecd-stage1 is nothing but "part 1" of the livecd creation process. It doesn't actually create anything. You need to complete a livecd-stage2 build to actually get an ISO output. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Missing /root
Åsmund Grammeltvedt wrote: On Wednesday 03 October 2007 16:12:29 Andrew Gaffney wrote: I just tried to reproduce it with a stage3-amd64-2007.0, and I can't. The only reason is that there is a .keep file in /root, which was put there by baselayout's mkdirs.sh script. Unless something has changed with baselayout in the tree since the 2007.0 snapshot, your problem lies elsewhere. Looking at the current stable in the tree (1.12.9-r2), it still does 'kdir /root' unconditionally. Are you using baselayout-2 or something? Great, now I can't reproduce it either. I disabled ccache, rebuilt the stages and observed that /root was present. However, after re-enabling ccache, /root's still there. Odd, but at least it works for me now. Hurray! Another catalyst heisenbug! -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Missing /root
Åsmund Grammeltvedt wrote: On Wednesday 03 October 2007 14:00:58 Andrew Gaffney wrote: Åsmund Grammeltvedt wrote: On Wednesday 19 September 2007 18:24:33 Chris Gianelloni wrote: On Wed, 2007-09-19 at 17:23 +0200, Ã…smund Grammeltvedt wrote: However, it may just create it with USE=build. Check the vdb in your stage1 to see what package owns the /root directory. ccache, apparently. Baselayout _should_ also create /root, but something seems to go wrong along the way. I guess I should rebuild and check the logs. Please do. If you find it to be an issue with baselayout, please file a bug so we can get it fixed before we start our next release. Hm, I haven't had time to actually check if this happens, but the current theory is this: Baselayout creates /root, but avoids becoming the owner by generating /usr/share/baselayout/mkdirs.sh and then running it in pkg_preinst. When ccache is unmerged at the end of the stage build, it removes /root, since its the sole owner. Does that seem plausible? Sure, that explanation is very plausible. Since ccache isn't enabled by default and most of us don't use it for release building, we never would have seen it. It may even be the reason that wolf31o2 recommends that it not be used. In that case, may I suggest the following? :) -# ccache = enables build time ccache support (highly recommended) +# ccache = enables build time ccache support (not recommended) I just tried to reproduce it with a stage3-amd64-2007.0, and I can't. The only reason is that there is a .keep file in /root, which was put there by baselayout's mkdirs.sh script. Unless something has changed with baselayout in the tree since the 2007.0 snapshot, your problem lies elsewhere. Looking at the current stable in the tree (1.12.9-r2), it still does 'kdir /root' unconditionally. Are you using baselayout-2 or something? -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Zero-sized busybox binaries in livecd stage2
Åsmund Grammeltvedt wrote: Hi all. This may be more of a problem with genkernel (3.4.8), but perhaps someone here has an idea of what's wrong. On building x86 livecd stage2 on amd64, the initramfs _sometimes_ ends up containing mostly empty files: -rwxr-xr-x 8 asmundg asmundg 0 Oct 3 13:00 [ -rwxr-xr-x 8 asmundg asmundg 0 Oct 3 13:00 ash -rwxr-xr-x 8 asmundg asmundg 0 Oct 3 13:00 busybox -rwxr-xr-x 8 asmundg asmundg 0 Oct 3 13:00 cut -rwxr-xr-x 8 asmundg asmundg 0 Oct 3 13:00 echo -rwxr-xr-x 1 asmundg asmundg 479420 Oct 3 13:00 insmod -rwxr-xr-x 8 asmundg asmundg 0 Oct 3 13:00 mount -rwxr-xr-x 8 asmundg asmundg 0 Oct 3 13:00 sh -rwxr-xr-x 1 asmundg asmundg396 Oct 3 13:00 udhcpc.scripts -rwxr-xr-x 8 asmundg asmundg 0 Oct 3 13:00 uname There are no obvious errors in the output, and subsequent rebuilds often get it right again. I would blame the hardware, if not for the fact that nothing else is failing. Is anyone familiar with these symptoms? I haven't seen that before, but you're obviously using an "older" (not 3.4.9_pre3) version of genkernel, since you've got an actual insmod binary instead of it being built into busybox. You should try using _pre3, because we always need testing :) Also, most of those 0-length files are supposed to be symlinks to /bin/busybox. Do you have a /bin/bb? -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Missing /root
Åsmund Grammeltvedt wrote: On Wednesday 19 September 2007 18:24:33 Chris Gianelloni wrote: On Wed, 2007-09-19 at 17:23 +0200, Ã…smund Grammeltvedt wrote: However, it may just create it with USE=build. Check the vdb in your stage1 to see what package owns the /root directory. ccache, apparently. Baselayout _should_ also create /root, but something seems to go wrong along the way. I guess I should rebuild and check the logs. Please do. If you find it to be an issue with baselayout, please file a bug so we can get it fixed before we start our next release. Hm, I haven't had time to actually check if this happens, but the current theory is this: Baselayout creates /root, but avoids becoming the owner by generating /usr/share/baselayout/mkdirs.sh and then running it in pkg_preinst. When ccache is unmerged at the end of the stage build, it removes /root, since its the sole owner. Does that seem plausible? Sure, that explanation is very plausible. Since ccache isn't enabled by default and most of us don't use it for release building, we never would have seen it. It may even be the reason that wolf31o2 recommends that it not be used. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Files inside /home/user
John Eckhart wrote: Sorry to hijack the thread, I am planning to look at unionfs on livecd soon as well as unionfs with other distribution methods (i.e. netboot). Could you could explain (briefly) the problems you encountered? Was it a problem with genkernel (applying the patches, building a correct initramfs, etc.?) or was it trying to boot a gentoo system with a unionfs backed root? Also, did you try any of the unionfs clones (such as aufs)? I suspect the problems were not specific to unionfs, but if they were related to quirks of unionfs then I will investigate trying one of the clones instead. Any help or direction you could give would be appreciated. The problems were in the code in the initramfs that sets up and mounts the unionfs. Just grab a 2007.0 minimal CD and boot with 'unionfs' on the kernel commandline. You'll see the problem. We have not tries unionfs alternatives, but we also haven't put too much effort into figuring out the cause of the current problem, since unionfs isn't the "default" method when booting the CD. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Missing /root
Åsmund Grammeltvedt wrote: Hi. I just noticed that /root is missing from my stage3 (stage 2 as well. It's present in stage1). Do I need to take some special care in order to have it show up? I thought that baselayout owned it, but it doesn't appear that it does (on my local system). However, it may just create it with USE=build. Check the vdb in your stage1 to see what package owns the /root directory. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Files inside /home/user
Luca Casagrande wrote: Hello Chris. Il giorno 11/set/07, alle ore 19:40, Chris Gianelloni ha scritto: On Tue, 2007-09-11 at 16:38 +0200, Luca Casagrande wrote: Hello everybody. In my LiveCD, I have got about 100 MB of data inside the the user folder; if i boot the LiveCD on machine with 512 Mb of ram, I have got a lof of cp error during the "Copying Read-Write to tmpfs" phase. I think that the reason of this trouble is that /home/ is copied inside the tmpfs during the boot and it's being fulled with all my data. Is there a way for solving this? Don't put the data in /home. You can also look into figuring out the (now broken, again) unionfs support in genkernel. I'll try to use the unionfs support; is there a genkernel version that you know support it? You missed his point. The latest gk versions have the unionfs support, but it keeps breaking for some reason. He was dropping a "subtle" hint for you to take a look at it and try to fix it ;) -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Can't start catalyst -f tinderbox.spec
Yes, please do.
Daniel van Ham Colchete wrote:
Found the problem!
There are 2 pkgcache_path lines on
/usr/share/doc/catalyst-2.0.4/examples/tinderbox_template.spec. So my
copy also had it and this is what was causing the problem. Should I file
a bug?
Best,
Daniel
On 9/6/07, *Daniel van Ham Colchete* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I'll test it on catalyst-2.0.5-pre3 first just to be on the safe
side. In 15 more minutes I'll open the bug.
Thanks Andrew!
Daniel
On 9/6/07, * Andrew Gaffney* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Daniel van Ham Colchete wrote:
> Hello yall,
>
> after using catalyst to successfully build a stage4 for my
servers, I'm
> now trying to play a little bit with tinderbox.
I don't think anybody has played with catalyst's tinderbox
support in a while.
Please file a bug, and we'll take a look at it.
--
Andrew Gaffney
http://dev.gentoo.org/~agaffney/
<http://dev.gentoo.org/%7Eagaffney/>
Gentoo Linux Developer Catalyst/Installer + x86
release coordinator
--
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
mailing list
--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Can't start catalyst -f tinderbox.spec
Daniel van Ham Colchete wrote: Hello yall, after using catalyst to successfully build a stage4 for my servers, I'm now trying to play a little bit with tinderbox. I don't think anybody has played with catalyst's tinderbox support in a while. Please file a bug, and we'll take a look at it. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] build fail at stage2
Luca Casagrande wrote: Il giorno 05/set/07, alle ore 14:34, Raboo Treed ha scritto: Hey, I get a error message when i try to compile stage2 of my livecd Could anyone look at the typescript and the spec file and see what i'm doing wrong? I'm replying here, because I don't feel like trimming all of the crap out of the original email :) Some things are wrong: 1- You are not building the stage2, but the livecd-stage2. I did the same error of you and this can create troubles when posting here. Sounds like a vote for the implentation of bug #145001 :P 2- Your error come from Genkernel...take a look at the log. You've hit a known bug in genkernel-3.4.8, which has been fixed. Try "unmasking" genkernel-3.4.9_pre2 in your snapshot. 3- Please, the next time post just the error and not all the process.. Yes, I had considered just deleting the original email because it was so long. Next time, only put the relevant info in the email. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] expat and stage4
Graham Murray wrote: I am trying to build a stage4 and this is failing during the update of 'system' following the unpacking of the stage3 tarball. The problem is that the stage3 tarball contains expat-1.x (which generates libexpat.so.0) and catalyst is upgrading this to expat-2.0.1 (which replaces libexpat.so.0 with .so.1) as package number 14, but it had already upgraded gettext which uses expat. Then when it comes to build net-tools, which uses gettext, it fails because the linker cannot find libexpat.so.0! Is there any way to tell catalyst to upgrade expat before it upgrades any packages which use it? The proper way to fix this problem is to build a full set of stages starting at stage1 using the same portage snapshot. If you take a stage3 that was built using an older snapshot and use it to build a stage4 or a livecd, you are just asking for trouble. If you don't want to build a full set of stages, there are a few methods to get around this problem, but I'll leave that as an exercise for you to figure out what they are, since anything other than the above method isn't supported :) -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] use flags for stage4?
Joshua Hoblitt wrote: Is there a keyword for setting use flags for stage4 (similar to livecd/use)? Yes, stage4/use (who'd have thunk it? :P) -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Python 2.5 Livecd
Luca Casagrande wrote: Thanks for your answer Chris, i l'll rebuild the whole stages. I'll use 2007.0 profile, but i have read that is missing the use flag ATI for Xorg. Can work if i add by hand those missing useflag in the etc/package.use ? That was fixed in the tree post-release. You can always check yourself instead of just going by hearsay. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] pre-kmerge failed???
rek2GNU/Linux wrote: Chris Gianelloni escribió: On Tue, 2007-08-14 at 23:49 -0400, rek2GNU/Linux wrote: ok this always worked. now all of the blue I get this.. any idea? No clue. Run it again with -a and see if it persists. That work, thanks now I get to this: * ERROR: Could not find device-mapper source tarball: /usr/share/genkernel/pkg/device-mapper.1.02.07.tgz. Please place it there, or place another version, changing /etc/genkernel.conf as necessary! Well, I'd say that error is very straightforward. It even tells you how to fix it. What's the problem? -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] changing inittab
Joshua Hoblitt wrote: The result is pretty much the same as with the gentoo-nofb kernel on the CD built with the splash enabled. The vga console does dead as soon as the kernel starts to load. While you can have getty running on both virtual consoles and serial, I don't believe you can get boot messages to go to both. However, livecd-tools is currently setup to only add /etc/inittab entries for one, not both. I don't see any reason it can't do the virtual terminals by default and add the serial consoles if needed, though, unless the kernel/agetty will get uppity about it. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] changing inittab
Joshua Hoblitt wrote: On Fri, Aug 03, 2007 at 12:01:23PM -0700, Chris Gianelloni wrote: On Thu, 2007-08-02 at 19:01 -0500, Andrew Gaffney wrote: Joshua Hoblitt wrote: On Wed, Aug 01, 2007 at 05:26:03PM -0700, Chris Gianelloni wrote: Normally, yes, it would only be good for kernel output, but as someone else mentioned, you have livecd-functions.sh that re-writes the inittab. Well, guess what triggers it? That's right, a "console=" option on the command line. If you type (or via catalyst, add) console=something, livecd-functions.sh (via functions.sh in baselayout) will interpret it and modify inittab accordingly before we ever even hit runlevel 3, so it starts a console on that serial line for login. So I tried setting 'livecd/bootargs: console=ttyS0,115200' in installcd-stage2-minimal.spec and indeed it does setup a tty on the serial line. However, it doesn't actually seem to pass "bootargs" to the kernel or there is some other wierdness going on as the dmesg information AND all of the sysvinit output remains only on the vga console. The last output on the fbconsole is some wierd error message about bootsplash right before attaching a tty to the serial line. This is an improvement for me but I would really like to see the kernel output/etc. so I can see if the boot processes has hung. You're positive that it's not being passed to the kernel? I'm pretty sure that livecd-tools would read it from /proc/cmdline, which is the arguments passed to the kernel. If it shows up in /proc/cmdline, then it's the kernel that isn't honoring it, not catalyst/genkernel/isolinux that is doing something wrong. I think it is an ordering issue, rather than it not being passed. I just checked the code and the splash code appends to the very end of the kernel command line, meaning it takes precedence. I won't be able to test anything until Monday. Would an option to completely disable the splash be reasonable? That's what the -nofb kernel does. However, there isn't currently an option to have a framebuffer without splash. I'm not sure if it would still pass the splash options if you don't enable splash stuff in livecd-stage2.spec, but I bet it would. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] changing inittab
Joshua Hoblitt wrote: On Wed, Aug 01, 2007 at 05:26:03PM -0700, Chris Gianelloni wrote: Normally, yes, it would only be good for kernel output, but as someone else mentioned, you have livecd-functions.sh that re-writes the inittab. Well, guess what triggers it? That's right, a "console=" option on the command line. If you type (or via catalyst, add) console=something, livecd-functions.sh (via functions.sh in baselayout) will interpret it and modify inittab accordingly before we ever even hit runlevel 3, so it starts a console on that serial line for login. So I tried setting 'livecd/bootargs: console=ttyS0,115200' in installcd-stage2-minimal.spec and indeed it does setup a tty on the serial line. However, it doesn't actually seem to pass "bootargs" to the kernel or there is some other wierdness going on as the dmesg information AND all of the sysvinit output remains only on the vga console. The last output on the fbconsole is some wierd error message about bootsplash right before attaching a tty to the serial line. This is an improvement for me but I would really like to see the kernel output/etc. so I can see if the boot processes has hung. You're positive that it's not being passed to the kernel? I'm pretty sure that livecd-tools would read it from /proc/cmdline, which is the arguments passed to the kernel. If it shows up in /proc/cmdline, then it's the kernel that isn't honoring it, not catalyst/genkernel/isolinux that is doing something wrong. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] ~arch builds
Philipp Riegger wrote: Hi! I'm just curious (and did not find anything about that yet). Is it possible to build ~arch stages and livecds without changing the tree or using portage_confdir? Yes, just set ACCEPT_KEYWORDS="~whatever" in your envscript. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] changing genkernel's configuration files as invoked by Catalyst
Joshua Hoblitt wrote: I don't know if this is intersting but here is a diff between the genkernel 3.4.6 ebuild and what I put in my overlay tree to add the arcmsr driver. The diff isn't all that useful to us, since it's *really* easy to add the new driver to the list in SVN. It's just a pain to do it the way you're doing it...patching the source in the ebuild in a custom snapshot in a catalyst build. Thanks, though. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Automount machine partition
Luca Casagrande wrote: Hi to all! I have updated my livecd with today portage and right now it detect machine partition..That's very cool!! They are shown on the desktop and I could aslo write on ext3 one. Is this coming from new livecd-tools or it's a matter of baselayout? If it's on the GNOME (or whatever DE you're using) desktop, it's likely just a feature of a new version of that DE and not anything from livecd-tools or baselayout, as neither touch anything on the desktop. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Error trying to build uclibc stages
Philipp Riegger wrote: Hi! I got a strange error here building uclibc stages: I used experimental/x86/embedded/stages/stage3-x86-uclibc-2006.1.tar.bz2 from a mirror as seed stage and i used cflags, ldflags, arch and profile from the make.conf/make.profile in that stage. When i try to build my stage1 i get the following: You didn't post the spec you used, so there's not really much we can help you with. However, you're using an experimental stage as seed and likely using an experimental profile, and you're surprised that it broke? :) If you're doing anything like this, you should be able to easily debug this problem. My bet is that there's something screwed up in the profile (like glibc is p.masked and virtual/libc only has glibc listed). -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] GNAP in Google SoC
Philipp Riegger wrote: On Thu, 2007-07-05 at 13:45 -0700, Chris Gianelloni wrote: I'm working on the GSoC project which aims at enabling gnap builds on non-x86 and which enables cross-compiling for gnap. I did not work that much on the last point so far, since i'd like to know what is already done, first. So... How's the status on this one? What is the status of what? Cross-compiling? I was talking about the status of vapiers' cross compile patches for catalyst. I talked to him since and he said he would file a bug with the patches. Catalyst should be able to cross cmpile stage1 he said, only not all stage1 packages work with cross compilation. I'm still waiting for the bug. Vapier's original cross-compilation patches to catalyst from 6 months or so ago only added the foundation for cross-compiling and none of the guts, afaict. He has been pretty busy lately, and none of the catalyst devs really have any idea what he was intending or the time/inclination to work on it ourselves. If you require catalyst cross-compiling functionality for your SoC project, you'd better start working on it yourself or just give up on your project :) -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Livecd License
Luca Casagrande wrote: Hi to all! My livecd, will be used during a postgresql meeting to show some application. Organizing team, has asked me for the media's license; i told him that each application has got a own license and the full work can be release in gpl3. Am I correct? I doubt it. We can't really give you that answer as we have no idea what packages you are using on the LiveCD. You need to do the legwork of figuring out which license each package uses and if said license can be "transferred" to GPLv3. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] catalyst as non-root
Philipp Riegger wrote: Did anybody else try running catalyst as non-root and can give me hints on how to do it? We don't support catalyst running as non-root. If you want to do it, you're on your own. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] stage4 tarball's /usr/src/linux is a symlink to /tmp/kerncache/[kernelname]/usr/src/linux
Charles Duffy wrote: Per subject. I'm presuming that this is not desired behavior. This is using catalyst-2 r1234 (patched, but not in any respects which should impact this particular functionality). Since we do not use stage4 functionality for releases, this is not going to be a priority. If you provide a patch, it's a lot more likely to get fixed in a timely manner :) -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] Problem on the final ISO
Luca Casagrande wrote: Hi to all. Don't know if this is a bug, but sometimes it happen that the iso created with catalyst, contains just 1 file: image.squashfs. In my tests, i noticed that it happen at random..once it happen, if i rebuild the livecd-stage2 with the same spec file, all it's ok. Using catalyst 2.0.4. I've noticed something similar before. The ISO will end up far smaller than it's supposed to be, but re-running livecd-stage2 with no changes generates a normal build. Nobody has ever found the cause of this, since it happens to infrequently and is easy to "fix". -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
