How to compare 2 puppies of same tahr flavor? (packages etc)

[johnywhy]

i need to compare an unmodified x-tahr to a modified x-tahr.

Both are exact same puppy release version.

By "modified", i just mean i removed a bunch of builtin packages, installed a bunch of pets and packages, and tweaked the desktop to my liking.

Remaster fails on the modified puppy, but works on the unmodified puppy.

So i want to determine exactly how the 2 puppies differ.

i get:

Code: Select all

# dpkg -l
dpkg: can't open '/var/lib/dpkg/status': No such file or directory

THX

[nic007]

I think your savefile is the problem like I've told you before.

[johnywhy]

in what way? that's what i'm trying to determine.

the test you recommended previously (i thought) was to remaster a puppy that didn't have a save file. That worked.

Now i remastered a puppy with a save-file. That worked too.

thx

[nic007]

You can do remasters without your savefile (that is not customized) but not with that specific savefile of yours. All your tinkering with removing builtin stuff, installing stuff, etc. has an impact (are recorded) in the savefile. Something seems to have gone wrong during these processes which prohibits making a remaster with the savefile loaded. You are looking for answers in all the wrong places, I'm sure it's got something to do with your savefile. Removing the builtin applications with the application from menu does not really remove the applications, they are still in the base sfs but your savefile treats them as so-called "white-out" files which actually just mean that they are "hidden" from view. The only way to actually remove the builtin applications physically is to do a remaster with the savefile running or editing the base sfs file (and making a new one).

[nic007]

in what way? that's what i'm trying to determine.

the test you recommended previously (i thought) was to remaster a puppy that didn't have a save file. That worked.

Now i remastered a puppy with a save-file. That worked too.

thx

Is that the same savefile that you had problems with previously?

[johnywhy]

You can do remasters without your savefile (that is not customized)

and with a savefile (but not customized).

but not with that specific savefile of yours. All your tinkering with removing builtin stuff, installing stuff, etc. has an impact (are recorded) in the savefile. Something seems to have gone wrong during these processes which prohibits making a remaster with the savefile loaded.

exactly. You're saying the mods i did are the problem.

You are looking for answers in all the wrong places, I'm sure it's got something to do with your savefile.

so the mods i did are not the problem?

[nic007]

You had a problem with the old big savefile because you couldn't do a remaster whilst running with it. Is that correct? The assistance I was giving, was to try and save all the work you put into the old savefile (all your pet installations, etc.). That's all I'm talking about. If you got rid of the old savefile and are using another one and are able to do a remaster with the new savefile, that's great. Back to your original question - the remaster attempts to update the packages lists as far as I know. Look in /root/.packages if you can find what you are looking for.

[johnywhy]

Look in /root/.packages

in a new x-tahr (with save file), the file woof-installed-packages is empty.

but in my customized x-tahr, woof-installed-packages is loaded with tons of stuff. But not stuff i installed-- it all looks like built-in stuff. So, how is woof-installed-packages file different from the contents of /root/.packages/builtin_files ? Why is it empty on a non-customized puppy?

Sample contents of woof-installed-packages:

915resolution-0.5.3-patched20110617|915resolution|0.5.3-patched20110617||BuildingBlock|36K||915resolution-0.5.3-patched20110617.pet||add widescreen resolutions to video bios, intel video chips only||||
acpi|acpi|||BuildingBlock|44K||acpi.pet||no description provided|ubuntu|trusty||
acpid-busibox-4|acpid-busibox|4||BuildingBlock|120K||acpid-busibox-4.pet||acpi deamon with dialog box and lid supend||||
align-1.7.1|align|1.7.1||BuildingBlock|40K||align-1.7.1.pet|+perl_tiny|align text into columns||||
alsa-base_1.0.25+dfsg|alsa-base|1.0.25+dfsg|0ubuntu4|Filesystem;filemanager|502K|pool/main/a/alsa-driver|alsa-base_1.0.25+dfsg-0ubuntu4_all.deb|+module-init-tools&ge3.2.1,+linux-sound-base,+udev|ALSA
etc....

[nic007]

Because all builtin packages are not woof-installed packages, I think.

[johnywhy]

Because all builtin packages are not woof-installed packages, I think.

i'm seeing the same packages in both places:

/root/.packages/woof-installed-packages

/root/.packages/builtin_files/

[s243a]

i need to compare an unmodified x-tahr to a modified x-tahr.

Both are exact same puppy release version.

By "modified", i just mean i removed a bunch of builtin packages, installed a bunch of pets and packages, and tweaked the desktop to my liking.

Remaster fails on the modified puppy, but works on the unmodified puppy.

So i want to determine exactly how the 2 puppies differ.

i get:

Code: Select all

# dpkg -l
dpkg: can't open '/var/lib/dpkg/status': No such file or directory

THX

If it uses puppies package manager than look under /root/.packages

dpkg is for debian and ubuntu.

[musher0]

Hello JohnyWhy.

Please forgive lateness coming to this thread.

If I may suggest something:
From console,
-- unsquash both the remastered Puppy sfs and the original Puppy sfs
in each their own directory with

Code: Select all

unsquashfs -d Directory OriginalPup.sfs
unsquashfs -d OtherDirectory RemasteredPup.sfs

-- then compare the files list with

Code: Select all

diff -r -y Directory OtherDirectory | more

This should give you a somewhat sorted two column listing with
differences shown.

IHTH. Best of luck.

[musher0]

Addendum:

You could probably do it also by comparing the listing of files in directory
/root/.packages/builtin_files/*
of the original and the remaster.

(I think that a similar procedure has been mentioned above.)

BFN.

[johnywhy]

thx s243a and musher0.

Does anyone know:
How is /root/.packages/woof-installed-packages file different from the contents of /root/.packages/builtin_files/ directory ?

Why is woof-installed-packages empty on a non-customized puppy?

THX