Re: trying simple-cdd

[lloyd@paisite.com]

Hi Vagrant,

> On Tue, Jan 02, 2007 at 06:27:17PM -0500, lloyd@paisite.com wrote:

>> Now it gets well into the build process, but hangs at "processing
back-end
>> etch." The cursor just sits there blinking at me. How long should I
expect
>> this step to take?

> that sounds like debpartial-mirror, which is no longer the default, for
that very reason. did you set mirror_tools in simple-cdd.conf or use the
--mirror-tools commandline option?

I'm picking up on the work that my son started, so I may be missing some
steps. Here's what I did:

1. Starting in my own home directory I downloaded etch-simple-cdd

bzr get http://cdd.alioth.debian.org/bzr/simple-cdd/etch-simple-cdd

2. Then:

cd etch-simple-cdd

3. In profiles I created "test.packages," and added:

xfce4
gimp

My goal is the simplest possible build with no pre- or post-seeding until
I understand the basic process. I want to walk before I run.

4. In simple-cdd.conf, I added "profiles="test"

I don't understand what "set mirror_tools" means. Are these the variables
you're talking about:

server= "ftp.us.debian.org"
debian-mirror= "http://$server/debian/";
rsync_debian_mirror= %server::debian"

If so, I left them as shown.

I note in etch-simple-cdd/README that you mention "up.to.date.mirror" but
I don't know what you mean by that.

5. I executed:

debuild -us -uc -I.bzr -b

6. And then:

./build-simple-cdd --profiles test --local-packages
$(pwd)/../simple-cdd-profiles_0.3.0-1_all.udeb

After running for a very long time, the system returned with errors (I
didn't have a printer hooked to dev machine, meant to copy them down, but
accidently closed the console window.)

The system did not return a *.raw file.

Feels closer, but clearly I'm overlooking something.

Many thanks,

Lloyd