.dejan555 wrote:Here's fluxbox pet compiled on buster 64:
fluxbox-1.3.7-dpupbuster64.pet 882kb
fluxbox-1.3.7-DOC-dpupbuster64 43kb
thanks dejan555 .
downloading and testing fluxbox
.dejan555 wrote:Here's fluxbox pet compiled on buster 64:
fluxbox-1.3.7-dpupbuster64.pet 882kb
fluxbox-1.3.7-DOC-dpupbuster64 43kb
I would have to recognize your audio card.linux28 wrote:No Audio on ALC887?
sound wizardjosejp2424 wrote:I would have to recognize your audio card.linux28 wrote:No Audio on ALC887?
you should try boosting sound wizard
Code: Select all
run-as-spot /usr/bin/google-chrome-stable
Code: Select all
pkg --repo-update
Code: Select all
# now call petget 0setup.. [add argument]
/usr/local/petget/0setup x &>$TMPDIR/update_repo_results
https://github.com/puppylinux-woof-CE/w ... -543370726Pkg was not compatible with current stuff in the testing branch
This Pkg is somewhat fixed to work with current woofce
https://github.com/puppylinux-woof-CE/Pkg/commits
But requires a patched 0setup:
f99cf47
In puppy/woof/fyhk everything is tightly integrated and the design is terrible, it's surprisingly easy to break stuff for everyone else just by making improvements to the code. It's not that hard to understand that.
.s243a wrote:I installed DpupBuster CE 64 because I wanted a more official version of pkg for testing purposes. Since the version that I use in my tiny_puduan is "heavily modified" or at least it is according to sc0ttman it won't be acceptable as a testing environment if I want to contribute to the official version of pkg.
Some differences that I noticed for pkg in dpup buster vs the official version of pkg:
The file ppa2pup, doesn't seem to exist. Also ppa2pup no longer seems to be referenced in /usr/sbin/pkg.
See:
https://gitlab.com/sc0ttj/Pkg/blob/mast ... /pkg#L1493
https://gitlab.com/sc0ttj/Pkg/blob/mast ... /pkg#L1803
Please let me know of any modifications that you made to pkg?
BTW, the following command doesn't seem to work properly:It hangs because 0seup is looking for user input. Pressing "enter" a few times helps the script finish but the prompt doesn't show.Code: Select all
pkg --repo-update
I haven't tried it yet but you might be interested in wdlkmpx changes here:
https://github.com/puppylinux-woof-CE/P ... 2a6c2381a7Code: Select all
# now call petget 0setup.. [add argument] /usr/local/petget/0setup x &>$TMPDIR/update_repo_results
https://gitlab.com/sc0ttj/Pkg/issues/71
When I tested this I missed the part where wdlkmpx said that it required a patched 0setup:
https://github.com/puppylinux-woof-CE/w ... -543370726Pkg was not compatible with current stuff in the testing branch
This Pkg is somewhat fixed to work with current woofce
https://github.com/puppylinux-woof-CE/Pkg/commits
But requires a patched 0setup:
f99cf47
In puppy/woof/fyhk everything is tightly integrated and the design is terrible, it's surprisingly easy to break stuff for everyone else just by making improvements to the code. It's not that hard to understand that.
Or as an alternative to using 0setup, one can use ppa2pup. I have created a faster version of ppa2pup. See:
github.com/s243a/.../usr/sbin/ppa2pup
http://www.murga-linux.com/puppy/viewtopic.php?t=117436
sc0ttman, wants to keep the old version of ppa2pup (see post). Therefore, I'll probably rename my awk version of ppa2pup to something like ppa2pup_gawk.
Anyway, I would be interested to know of any changes that you made to pkg. I recall reading something about dpup buster having issues with the multi-arch symlink, when using pkg. For testing, I want to use as official code as possible but I need to be aware of any potential issues like the multi-arch symlink that you previously mentioned. I can copy sc0ttman's official code into dpup buster but I need to know of any potential issues than need to be resolved, that you patched.
There is a merge request now:josejp2424 wrote: I will test your modifications, which you mention and I will be commenting on you.
https://gitlab.com/sc0ttj/Pkg/merge_req ... _251616106BTW, how we use ppa2pup or ppa2pup_gawk as a fallback to 0setup when 0setup doesn't exist needs more work:
ppa2pup only works on .deb based pups,
IIRC, in standard Puppy only third-party repos go in /etc/sources.list and /etc/slackpkg/mirrors, not system repos, so they would't get updated
we need to also handle Slackware pups if 0setup doesn't exist (fall back to slack2pup?)
We need to check $DISTRO_BINARY_COMPAT:
if .deb based pup, and no 0setup, use ppa2pup
if slack based pup, and no 0setup, use slack2pup
if no repos in /etc/sources.list or /etc/mirrors/slackpkg.... ?????
Does this mean the latest from gitlab? That is the the latest.. Or do you mean the PET file from the Pkg forum thread? (cos that is not the latest.. )josejp2424 wrote:hi s243a.
The pkg I use is the official one.
You're right sc0ttman. use 1.9.22. and pkg-apt-wrapper-0.1-noarch.sc0ttman wrote:Does this mean the latest from gitlab? That is the the latest.. Or do you mean the PET file from the Pkg forum thread? (cos that is not the latest.. )josejp2424 wrote:hi s243a.
The pkg I use is the official one.
Ah OK, the latest version on Gitlab has lots of fixes & improvements since then..josejp2424 wrote:You're right sc0ttman. use 1.9.22. and pkg-apt-wrapper-0.1-noarch.sc0ttman wrote:Does this mean the latest from gitlab? That is the the latest.. Or do you mean the PET file from the Pkg forum thread? (cos that is not the latest.. )josejp2424 wrote:hi s243a.
The pkg I use is the official one.
http://www.murga-linux.com/puppy/viewtopic.php?t=112927
Code: Select all
#/bin/sh
/opt/google-chrome/chrome/google-chrome --no-sandbox --user-data-dir=/root/.config/google-chrome --disk-cache-size=10000000 --media-cache-size=10000000 --disable-metrics