(old)Puppy Linux Discussion Forum

Hello all.

As the title says.

I spent the past hour building a Xenial Pooch 32-bit with the woof-CE.

It sort of aborted close to the end, during the last stretch.

There is no *.iso file in sight.

Please find attached the complete list of files in directory
woof-out_x86_x86_ubuntu_xenial

A number of questions:
1) According to your expertise, have all files been built? (I have that impression.)

2) If so, which sub-directories of the above do I put where in a directory
called "Xenial-Pooch-build" to be compacted with mksquashfs

3) Once that is created, what goes where in directory
iso-build (the directory mkisofs will take its files from to create the iso).

Thanks in advance.

~~~~~~~~~~

Again, please no novels, no novelettes, no sermons, not even explanations, no
void comments, and most of all no interpretations. Just the straight goods.

The rage I'm in because the woof-CE process has failed me again doesn't need
any more fuel than it already has. I hope you understand that. I love Puppy, but it
seems the love is not mutual.

So please give only the straight goods, straight problem-solving in simple words
based on the attached list of files.

I'll be most grateful if you help me.

~~~~~~~~~~~~~
That list is split in two parts because of forum restrictions. Please use the attached
script to reassemble the zip.

Again, many thanks.

~~~~~~~~~~~~~

Did the puppy .sfs mksquashfs build finish correctly? It's contents are in:
woof-out_x86_x86_***/sandbox3/rootfs-complete

The build should be in:

woof-out_x86_x86_***/sandbox3/build

The command to make the iso run from a terminal in sandbox3 is:

mkisofs -D -R -o ***.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table ./build/

peebee wrote:Did the puppy .sfs build finish correctly?

The build should be in:

woof-out_x86_x86_***/sandbox3/build

The command to make the iso run from a terminal in sandbox3 is:

mkisofs -D -R -o ***.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table ./build/

Thanks, peebee, for your quick reeply.

No sfs was created for the puppy itself. Please see attached pic.
Where should the sfs contents be taken from?

BTW, the devx question did not appear in the terminal, so there is no devx to be
found either.

Again thanks.

BFN.

musher0 wrote:

peebee wrote:Did the puppy .sfs build finish correctly?

The build should be in:

woof-out_x86_x86_***/sandbox3/build

The command to make the iso run from a terminal in sandbox3 is:

mkisofs -D -R -o ***.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table ./build/

Thanks, peebee,

Please see attached.

You only have the kernel there so the build has failed before /sandbox3/build has been completed.

sfs contents should be in woof-out_x86_x86_***/sandbox3/rootfs-complete

peebee wrote:

musher0 wrote:

peebee wrote:Did the puppy .sfs build finish correctly?

The build should be in:

woof-out_x86_x86_***/sandbox3/build

The command to make the iso run from a terminal in sandbox3 is:

mkisofs -D -R -o ***.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table ./build/

Thanks, peebee,

Please see attached.

You only have the kernel there so the build has failed before /sandbox3/build has been completed.

sfs contents should be in woof-out_x86_x86_***/sandbox3/rootfs-complete

What would the solution be, then, aside from re-running the woof script,
which appears to be faulty?

musher0 wrote:

peebee wrote:

musher0 wrote: Thanks, peebee,

Please see attached.

You only have the kernel there so the build has failed before /sandbox3/build has been completed.

sfs contents should be in woof-out_x86_x86_***/sandbox3/rootfs-complete

What would the solution be, then, aside from re-running the woof script,
which appears to be faulty?

You need to rerun 3builddistro-Z and capture any error messages to show why it is failing.

What system are you doing the build on? I presume you have devx installed? What filesystem type is the disk partition?

Which version of woof-ce are you using? which branch? what date?

A number of questions:
1) According to your expertise, have all files been built? (I have that impression.)

2) If so, ...

You have a file called DOWNLOAD-FAILS and ERROR-2CREATEPACKAGES, so I'm gonna go with No.

Sailor Enceladus wrote:

A number of questions:
1) According to your expertise, have all files been built? (I have that impression.)

2) If so, ...

You have a file called DOWNLOAD-FAILS and ERROR-2CREATEPACKAGES, so I'm gonna go with No.

Contents of DOWNLOAD-FAILS:

busybox-1.24.2-i686.pet
fpm2_NLS-0.75-i686.pet
goffice-0.8.17-i686.pet
simplescreenrecorder-0.3.6.pet
uget-1.4.8.5-1-pup4.pet

Package ERROR etc. is attached. It has 2,700 lines.

BTW, Sailor, - I - do not have fails and error packages. The woof-CE process does.
Am I being clear? I followed the instructions in the panel/tabs faithfully.

~~~~~~~~~~

peebee wrote:

musher0 wrote:

peebee wrote:You only have the kernel there so the build has failed before /sandbox3/build has been completed.

sfs contents should be in woof-out_x86_x86_***/sandbox3/rootfs-complete

What would the solution be, then, aside from re-running the woof script,
which appears to be faulty?

You need to rerun 3builddistro-Z and capture any error messages to show why it is failing.

What system are you doing the build on? I presume you have devx installed? What filesystem type is the disk partition?

Which version of woof-ce are you using? which branch? what date?

Thanks for your questions, peebee.

I am using the latest woof-CE-testing downloaded two days ago from git-hub.

The partition type is as follows:
/mnt/sda7 Total: 29G Used: 1,4G Free: 26G Type: ext3
Additionally this is a fast SSD hard drive.

I am building from a Slim-6 slacko with the devx loaded.

How do I capture errors on the woof-CE? The utility doesn't offer a way to show
them as it performs. Unless you mean the two files Sailor mentioned, which I've
attached.

Thanks to both of you. BFN.

The xenial option in woofce is still a work in progress and will be updated when I release the next iso

I know the present recipe fails if you try to build a uefi iso..

I'll be updating xenials build recipe soon which will fix the problem above

Try running 3builddistro-z in a terminal

666philb wrote:The xenial option in woofce is still a work in progress and will be updated when I release the next iso

I know the present recipe fails if you try to build a uefi iso..

I'll be updating xenials build recipe soon which will fix the problem above

Try running 3builddistro-z in a terminal

Hi phil.

I just did. Same result as before. (See below.)
How did you create your alpha builds?
Can I pluck the 675 "missing packages from there?

OTOH, 210 packages in the packages-xenial directory seem to be ready. Are they?

BFN.

Hi @musher0

I suspect that your distro name change to Xenial Pooch has resulted in woof-ce being unable to locate the repositories.....

You have to get DISTRO_SPECS
DISTRO_COMPAT_REPOS-***
DISTRO_PET_REPOS

all consistent and all pointing at repositories that exist.....and contain the items specified in
DISTRO_PKGS_SPECS-***
Packages-***-official
etc

Building a distro requires a puppy? Why can't I do it in Ubuntu or unstable debian? I have tried over and over again and failed every time.

peebee wrote:Hi @musher0

I suspect that your distro name change to Xenial Pooch has resulted in woof-ce being unable to locate the repositories.....

You have to get DISTRO_SPECS
DISTRO_COMPAT_REPOS-***
DISTRO_PET_REPOS

all consistent and all pointing at repositories that exist.....and contain the items specified in
DISTRO_PKGS_SPECS-***
Packages-***-official
etc

Hello again, peebee.

Why would it matter if I call my distro Xenial Pooch, Xenial Pup or Toutou Xenial?

And please, do not personalize. Suspicions are not acceptable arguments. As I
told Sailor, none of these errors are my doing. I followed the instructions in the
panel and tabs to a t. The woof-CE process did the fails and mishaps all by itself.

Not that I want to be critical or aggressive. As I also said, I do not want
novelettes, etc., as answers, I would like to have the straight goods. So I am not
going to write you a novelette myself about this or interpret anything.

Mick has built many slackware Puppies, you have built Tahr and Xenial Puppies,
and josejp2424 has built a Debian Jessie Puppy, all from the woof-CE process.

Why can't I build one of those? Are you people using your own unpublished scripts
and / or tricks?

BFN.

Doglover wrote:Building a distro requires a puppy? Why can't I do it in Ubuntu or unstable debian? I have tried over and over again and failed every time.

Hello doglover.

Building a Puppy distro requires a Puppy distro. I don't think that there is such a
thing as a cross-distro building process.

Concerning the other Linux distributions, they have their own building or re-
mastering process. You shouldn't have to dig too deep in the Debian or Ubuntu
sites to find their how-tos. Their building processes are publicly available.

There is also a well known general process to build a Linux distribution called
"Linux from Scratch".

FWIW, here's a reference (among many others):
http://www.tuxradar.com/content/build-y ... n-easy-way

IHTH.

.

I wouldn't worry too much about it, I think the savefile feature in Woof-CE is broken right now anyway (in both testing and rationalise). I always get strange behavior during boot and during shutdown on next boot, at least on my slower main laptop. Have not tried Master branch yet but I'm guessing it's the same since they're pretty close in date. Will do more tests later.

Sailor Enceladus wrote:I wouldn't worry too much about it, I think the savefile feature in Woof-CE is broken right now anyway (in both testing and rationalise). I always get strange behavior during boot and during shutdown on next boot, at least on my slower main laptop. Have not tried Master branch yet but I'm guessing it's the same since they're pretty close in date. Will do more tests later.

I was told six months ago (by iguleder? Can't remember.) not to use the Master branch
any more... It was deprecated or something else was wrong with it.

Just my luck. I tried again this time to build the devuan Pup and...
1) There's an endless loop around the nano editor:

Checking syntax of PKGS_SPECS_TABLE...
NUMDELS=4
YESNO=nano
SYNTAX ERROR LINE 327: 'nano|libslang|libslang2|exe,dev>null,doc,nls|'
grep: status/findpkgs_FINAL_PKGS-devuan-jessie: No such file or directory

2) It has only 248 packages missing in the ERROR-Shmurf file. Better than the 700
missing in the Xenial woof, eh?

Let's laugh about it! Or...

Here's an idea: let's fork LFS and build Puppies that way!

.

jlst wrote:On a quick test I don't seem to have issues with the savefile, but will test some more.

The DISTRO_SPECS are not updated often, that's why it's a bit difficult to produce a puppy, and that's why older versions are already deleted in testing.

People are busy with life, anikin was right. Although me and gyro have been toying with woofce, the amount of changes is huge, so releasing alpha versions that will be deleted later makes sense, i must admit that i'm tired but i have to finish this and hopefully i'll be fixing more bugs, or in the end everything can just reverted to the legacy branch and evverything is dust in the wind.

Building a slackware 14.1 based puppy seems to produce a complete and usable puppy, that's the only one i built so far.

Hi jlst.

I (and probably a lot of other Puppyists too) am grateful for your dedication and
appreciate your honesty.

However, where can I download the "legacy" branch from? The Puppy that I want to
build cannot stay in limbo forever.

Thanks in advance.

Sailor Enceladus?

If all else fails, I've got your pupsave needs covered, here

BFN.