Carolina: Vanguard Edition Release 2 December 2014

[Geoffrey]

Geoffrey, if I may make a request, could you do the same work (yank glibc) for the most recent Chromium 42 that peebee has posted? I can test

I'm downloading chromium_43.0.2357.65 + pepper_17.0.0.188_lx.sfs to see if that will work, it has a newer version of pepperflash so I might slip it in the package I just uploaded if it works, it should I would think.

I had trouble with the sandbox with 42 so I gave up on it, if it won't play nicely without a trillion errors and warnings then it's junk, I'm exaggerating about the errors...My wife has told me a million times to exaggerate

[starhawk]

LOL. Not surprised one bit about the errors.

My tech shop friend is a software wiz, but he tells me he's never successfully built Webkit, let alone a full Chromium. I don't know the nature of the issues, though -- probably just as well, since I wouldn't understand. I'm a hardware guy

[Geoffrey]

Starhawk, I had no luck with the newer Chromium's, same problem with sandbox.

I re-uploaded the chromium-40.0.2214.91 as chromium-40.0.2214.91-17.0.0.188-vlina.sfs

See this post http://www.murga-linux.com/puppy/viewto ... 128#847128

[caiosama]

Geoffrey, do you think the Debtopet thing will work on Carolina?

http://www.murga-linux.com/puppy/viewtopic.php?t=39756

[starhawk]

I can tell you from experience, it does not. PetGet/PPM in Carolina doesn't understand XZ-compressed DEBs, which seem to be the type used by both Ubuntu and Debian now. Workaround: boot TahrPup, make the dotPET there, copy it over to Carolina. It'll work fine once it's a dotPET.

EDIT: Geoffrey -- I'd be interested in the nature of those sandbox issues. Does it just b*tch a little in terminal or does it outright refuse to run? I was getting malloc() errors when I tried to run it on non-AMD systems...

[Deacon]

I can tell you from experience, it does not. PetGet/PPM in Carolina doesn't understand XZ-compressed DEBs, which seem to be the type used by both Ubuntu and Debian now. Workaround: boot TahrPup, make the dotPET there, copy it over to Carolina. It'll work fine once it's a dotPET.

EDIT: Geoffrey -- I'd be interested in the nature of those sandbox issues. Does it just b*tch a little in terminal or does it outright refuse to run? I was getting malloc() errors when I tried to run it on non-AMD systems...

Wow. Thanks Geoffrey, starhawk & caiosama!

If the above is the case generally, I'll get Tahr on a flashdrive and volunteer to make new PETs as often as possible! Keep it up to date!

[Geoffrey]

Geoffrey, do you think the Debtopet thing will work on Carolina?

http://www.murga-linux.com/puppy/viewtopic.php?t=39756

I'm working on the problem, kinda have it sorted.

[starhawk]

Cool!

The biggest thing for me, aside from Chromium, would be an updated CUPS -- maybe from X-Slacko? Dunno. But rcrsn51 seems to be on vacation right now, so I'm not sure that a CUPS upgrade is in the cards...

[Deacon]

Edit: updated the pepper flash to the latest chromium-40.0.2214.91-17.0.0.188-vlina.sfs

For anybody that downloaded my previous one then here is the libpepflashplayer-17.0.0.188 just extract it to /usr/lib/chromium and edit /usr/bin/chromium

Code: Select all

#!/bin/bash

CHROMIUM_FLAGS="--user-data-dir --ppapi-flash-path=/usr/lib/chromium/libpepflashplayer.so --ppapi-flash-version=17.0.0.188"

export CHROME_WRAPPER=$(readlink -f "$0")
export CHROME_DESKTOP=chromium.desktop

exec /usr/lib/chromium/chromium $CHROMIUM_FLAGS "$@"

I've uploaded http://smokey01.com/carolina/Geoffrey/V ... -vlina.sfs, I removed the glibc libraries that were included and replaced pepperflash with version 17.0.0.169.

Appears to run ok from the little testing I've done, it maybe possible I've missed something that I had already installed that it requires, but at a guess it should be fine as is.

MD5 51e271493aa8e5f6d13fbbb12d9c4f62

Downloaded it. Since it wasn't running and I saw there was an error message upon shutdown I ran it in terminal.

I got this. Screenshot attached.

I had read somewhere before on the forum about a "malloc:" error so I'm wondering if this is that thing.

[Geoffrey]

Downloaded it. Since it wasn't running and I saw there was an error message upon shutdown

It runs ok for me, just the usual errors and warnings, I think the problem with"malloc:" is something to do with running on a intel machine?, there isn't much I can do about that as I only repackaged an existing sfs.

Starhawk has tried a number of different versions and had similar problems.

[Deacon]

It runs ok for me, just the usual errors and warnings, I think the problem with"malloc:" is something to do with running on a intel machine?, there isn't much I can do about that as I only repackaged an existing sfs.

Starhawk has tried a number of different versions and had similar problems.

I'll keep fiddling around I guess. I was about to be sure it was an Intel but it's actually AMD Athlon Neo K325 Dual Core.

[Geoffrey]

Geoffrey, do you think the Debtopet thing will work on Carolina?

http://www.murga-linux.com/puppy/viewtopic.php?t=39756

This works, I found a script and modified it, just name it deb2pet, it extracts the deb to tmp and creates a pet and moves it back to the working directory

Code: Select all

#!/bin/sh
sync 
echo 3 > /proc/sys/vm/drop_caches
TMP=`mktemp -d`
DIR=`echo $TMP`
PACKAGE="$1"
PACKAGE_FOLDER="$(basename "$PACKAGE" .deb)"
cd $DIR
mkdir -p "$PACKAGE_FOLDER"
for FILE in $(ar t "$PACKAGE")
do
  case $FILE in 
    data.tar)       ar p "$PACKAGE" data.tar      |tar --extract         --directory "$PACKAGE_FOLDER";;
    data.tar.gz)    ar p "$PACKAGE" data.tar.gz   |tar --extract --gzip  --directory "$PACKAGE_FOLDER";;
    data.tar.bz2)   ar p "$PACKAGE" data.tar.bz2  |tar --extract --bzip2 --directory "$PACKAGE_FOLDER";;
    data.tar.xz)    ar p "$PACKAGE" data.tar.xz   |tar --extract --xz    --directory "$PACKAGE_FOLDER";;
    data.tar.lzma)  ar p "$PACKAGE" data.tar.lzma |tar --extract --lzma  --directory "$PACKAGE_FOLDER";;
esac
done 
dir2pet "$PACKAGE_FOLDER"
mv "$PACKAGE_FOLDER".pet "${1%.*}".pet
rm -fR $DIR

[caiosama]

Thanks Starhawk and Geoffrey!

How i run the script to decompress a specific Deb package?...sorry for my noobness

[rg66]

Does Carolina still have Pack-Tools? Right click on a .deb and click Repack-Extract Packages to extract or convert to .pet or .sfs.

[Geoffrey]

Does Carolina still have Pack-Tools? Right click on a .deb and click Repack-Extract Packages to extract or convert to .pet or .sfs.

Yeah, but pack-tools won't extract debs that are tar.xz as it uses dpkg-deb which is to old and don't support it.

I tried to compile the latest dpkg which will work, but as always it needs more up to date gettext which won't compile for me

[Geoffrey]

Thanks Starhawk and Geoffrey!

How i run the script to decompress a specific Deb package?...sorry for my noobness

Extract deb2pet.tar.gz and place it in /usr/bin if you open a terminal and type

Code: Select all

deb2pet /path/to/the/file.deb

after a small amount of time a gui to create a pet will appear

The pet will found in the same directory as the deb file.

you can add a custom command to the rightclick menu of thunar

deb2pet %f

with the appearance conditions file pattern *.deb and check the box Other Files

[cthisbear]

Where is Mr B lately >> battleshooter ?

Chris.

[Geoffrey]

Where is Mr B lately >> battleshooter ?

Chris.

Don't know, I still have a message sitting in my outbox I sent last friday week and that would be Ms battleshooter.

[caiosama]

Thank you so much Geoffrey!!!!

[caiosama]

Downloaded it. Since it wasn't running and I saw there was an error message upon shutdown

It runs ok for me, just the usual errors and warnings, I think the problem with"malloc:" is something to do with running on a intel machine?, there isn't much I can do about that as I only repackaged an existing sfs.

Starhawk has tried a number of different versions and had similar problems.

Yes, in my Intel based machine, this Chromium does not work. Even i had a Kernel Panic about that!