s243a wrote:25 Aprl 19
TazPup64-PreAlpha-12.iso is looking promising but I've done very little testing on it (see (post)), since the GDbus error has been bothering me.
New ISO available (23 Mar 2019):
TazPup64-PreAlpha-7.iso (338M)
I'm still not booting directly from the ISO. Instead I'm copying the files to the hard drive, booting with the screen=text option and starting the desktop with a script I made called "startx_jwm"
I added VLC in this ISO and the xine plugin for firefox. Some videos play on youtube but not all.
More info in post:
p=1022875#1022875
Edit: 25-Mar-19: a temparary link to the build-kit:
BuildKit(TazPup64)-PreAlpha7-un…lean.tar.gz but this is 1.7Gig because:
1. I didn't run the clean scripts
2. There are more packages in the archive then needed to build the ISO
3. I think I also accidently packed an iso or two into the archive.
Anyway, I'll make a much smaller versions of the build kit for easier sharing.
New ISO available (17 Mar 2019) :
TazPup64-PreAlpha-6.iso (324.5MB)
The ISO works for me and my computer is running much faster with this ISO than with Slack64-6.9.9.9. However, it is still very raw so I will likely be aware of most reported issues.
However, there are two things that I need help with (although I'll try to figure them out on my own). The big one is fixing the XDG field code issue. My work around was to modify the desktop file of pcmanfm and change "%U" to "~" in the execute command. pcmanfm isn't really needed at this point though because I am working with jwm and rox
However, I'm also trying to get lxde to work since I think that is what mistfire's TazPup uses. When the system is more mature, I will create one or more slimmer versions that only have one of these two window manager installed.
The other issue, which I need help with, is that for some reason the menus are double nested (e.g. utilities->utilities. I would like to put the most important applications in the first level of nesting and the other applications nested deeper in the menus. I think I have to dig into the menu templates to figure this out. Once I get this sorted out I can use PupMenu-6.2
(installed) to move applications around within the menu.
Changes since last release outlined at p=1022230#1022230
Previous 1st Post: (Info still applies but links are out dated)
=============================================
I have a semi working iso
https://www.dropbox.com/s/sywi28v38esbx ... 5.iso?dl=0
323.4 MiB (There is a lot that I can trim out)
I tested booting from the files in the iso (not the iso its-self). I booted with boot option screen=text
To start jwm type:To start lxde type:Code: Select all
startx_jwmWithin jwm:Code: Select all
root/.xsession_lxde
1. The file manager and terminal emulator work in the top panel (but the file manager does not work in the "bottom panel" (or desktop menu) `due to field code issues.
2. Firefox works in the bottom panel
To configure internet in the menu go to:
system -> system -> SliTaz Panel
and then go to the network tab. You can manually type in the information here. The process is a bit awkward. There is an easier tool to get it to work that I haven't tested yet.
So anyway, it's a start. I still recommend that people wait before trying it though.
The default file manager in jwm is rox but if you are in a terminal you can type "pcmanfm" to start pcmanfm"/
There is a build kit also available:
https://www.dropbox.com/s/cfhewxce26ak5 ... ar.gz?dl=0
I did make some (untested) code changes to the build kit though since this current ISO was made.
TazPup64 (pre-alpha17) - getting close to alpha quality
Re: TazPup64 (pre-alpha12) - Looks Promising but I've done very
The first post in this thread will be revamped. This post is for record purposes.
I think we're getting close to alpha quality with TazPup64-PreAlpha-15
Some notes, the ISO will automatically log you into tux in the lxde desktop. On the bottom left (in the panel) there is a red logout/shutdown/reboot button that looks like the power symbol. If you click on it you can log out and then log in as root in the jwm desktop. The password for root is "root".
To use gparted you must install gtkmm.
I recommend starting gparted from the command line. If for some reason you get an error try it one more time from the command line.
The puppy universal installer works. I verified after installing and creating a save file that tux still works but I think there is a catch. If you install any software (e.g. gtkmm) in the pfx=ram mode then creating a save file might mess up the permissions for non root users.
In puppy this is less of an issue because when running as root in puppy directors are created with user=root, group=spot. However, when running as root in TazPup64 new folders are created with user=root, group=root. In both cases new folders only have executable permissions for user and group (not world). If for instance you install a package which has a file in /etc then the default permissions will be assigned to /etc rather than the permissions given for the directories on the base sfs. However, if you first create the save file before installing any packages then the correct permissions are assigned to /etc as well as directories defined in the PATH variable and the folders in the LD_LIBRARY_PATH variable.
Well actually this is likely only also partly true. The only folders which will be assigned the correct permissions are those on the base sfs included in the ISO. The LD_LIBRARY_PATH variable in TazPup64 is designed to handle folder structures from a wide range of distributions but not all these LD_LIBRARY_PATH directors and also not all PATH directories are included int he base SFS. Therefore if you install an alien package, I cannot guarantee the permissions will be correct if the package installs files in a non standard folder.
One can either re-organize the package so that it installs in standard folders or verify the permissions are correct if files are installed in "alien" places.
Edit 1 The first post is updated with more concise instructions than this post.
Some notes, the ISO will automatically log you into tux in the lxde desktop. On the bottom left (in the panel) there is a red logout/shutdown/reboot button that looks like the power symbol. If you click on it you can log out and then log in as root in the jwm desktop. The password for root is "root".
To use gparted you must install gtkmm.
Code: Select all
tazpkg get-install gtkmm
The puppy universal installer works. I verified after installing and creating a save file that tux still works but I think there is a catch. If you install any software (e.g. gtkmm) in the pfx=ram mode then creating a save file might mess up the permissions for non root users.
In puppy this is less of an issue because when running as root in puppy directors are created with user=root, group=spot. However, when running as root in TazPup64 new folders are created with user=root, group=root. In both cases new folders only have executable permissions for user and group (not world). If for instance you install a package which has a file in /etc then the default permissions will be assigned to /etc rather than the permissions given for the directories on the base sfs. However, if you first create the save file before installing any packages then the correct permissions are assigned to /etc as well as directories defined in the PATH variable and the folders in the LD_LIBRARY_PATH variable.
Well actually this is likely only also partly true. The only folders which will be assigned the correct permissions are those on the base sfs included in the ISO. The LD_LIBRARY_PATH variable in TazPup64 is designed to handle folder structures from a wide range of distributions but not all these LD_LIBRARY_PATH directors and also not all PATH directories are included int he base SFS. Therefore if you install an alien package, I cannot guarantee the permissions will be correct if the package installs files in a non standard folder.
One can either re-organize the package so that it installs in standard folders or verify the permissions are correct if files are installed in "alien" places.
Edit 1 The first post is updated with more concise instructions than this post.
Here's a ".vdi" file for virtualbox (with guest additions insalled):
TazPup64-PreAlpha-15.vdi
to use it add it you need to add it as one of the hard drives in a virtual machine.
I was wrong about having fixed the permission issues but hopfully I patched them in the ".vdi' file.
If you run as a user other than root, use the "su" command to make changes as root. Currently tazbox isn't working which allows a graphical version of su. I think this this is an issue with the yad package. I'll check to see if I'm missing any dependencies for yad. At this point running as root will be easier but users tux and spot should work.
I verified that you can log-in to lxde as tux and that the vbox guest services properly starts when doing so.
TazPup64-PreAlpha-15.vdi
to use it add it you need to add it as one of the hard drives in a virtual machine.
I was wrong about having fixed the permission issues but hopfully I patched them in the ".vdi' file.
If you run as a user other than root, use the "su" command to make changes as root. Currently tazbox isn't working which allows a graphical version of su. I think this this is an issue with the yad package. I'll check to see if I'm missing any dependencies for yad. At this point running as root will be easier but users tux and spot should work.
I verified that you can log-in to lxde as tux and that the vbox guest services properly starts when doing so.
s243a wrote:I think we're getting close to alpha quality with TazPup64-PreAlpha-15
Some notes, the ISO will automatically log you into tux in the lxde desktop. On the bottom left (in the panel) there is a red logout/shutdown/reboot button that looks like the power symbol. If you click on it you can log out and then log in as root in the jwm desktop. The password for root is "root".
To use gparted you must install gtkmm.I recommend starting gparted from the command line. If for some reason you get an error try it one more time from the command line.Code: Select all
tazpkg get-install gtkmm
The puppy universal installer works. I verified after installing and creating a save file that tux still works but I think there is a catch. If you install any software (e.g. gtkmm) in the pfx=ram mode then creating a save file might mess up the permissions for non root users.
In puppy this is less of an issue because when running as root in puppy directors are created with user=root, group=spot. However, when running as root in TazPup64 new folders are created with user=root, group=root. In both cases new folders only have executable permissions for user and group (not world). If for instance you install a package which has a file in /etc then the default permissions will be assigned to /etc rather than the permissions given for the directories on the base sfs. However, if you first create the save file before installing any packages then the correct permissions are assigned to /etc as well as directories defined in the PATH variable and the folders in the LD_LIBRARY_PATH variable.
Well actually this is likely only also partly true. The only folders which will be assigned the correct permissions are those on the base sfs included in the ISO. The LD_LIBRARY_PATH variable in TazPup64 is designed to handle folder structures from a wide range of distributions but not all these LD_LIBRARY_PATH directors and also not all PATH directories are included int he base SFS. Therefore if you install an alien package, I cannot guarantee the permissions will be correct if the package installs files in a non standard folder.
One can either re-organize the package so that it installs in standard folders or verify the permissions are correct if files are installed in "alien" places.
Edit 1 The first post is updated with more concise instructions than this post.
I was having an issue where yad dialogs (e.g. those used in tazbox); were the yad dialog was closing on me when I started to type. Installing yad-html seemed to fix have fixed this (further testing needed). Prior to installing this I had yad-gtk3 installed. Both yad-html and yad-gtk3 seem to have a file called /usr/bin/yad. I don't know if these two files are different or not.
I do know that the yad dialog that was causing problems did have html in it (see below).
----------------
On another note based on the way I have permissions set up /usr/local/bin/default_packagemanager needs executable permissions for user, group and world. Previously, I had not set executable permissions for world because I didn't know I needed it. The alternative would be to have all users a member of some command group that had executable permissions.
------------------
Just for reference, here is the yad dialog that was caussing me problems:
which is found on line 85 to 94 of /usr/bin/tazbox.
Edit 1:
Now that I got tazbox working. The script "/usr/local/bin/default_packagemanager" sould be:
as a side-note, the virtuabox shared clipboard seems to work for root but not tux. Perhaps there are good reasons for it to be this way or maybe there is a way around it?
Edit 2 I also need to add executable permission for "world" on /usr/bin/wmexit.
I do know that the yad dialog that was causing problems did have html in it (see below).
----------------
On another note based on the way I have permissions set up /usr/local/bin/default_packagemanager needs executable permissions for user, group and world. Previously, I had not set executable permissions for world because I didn't know I needed it. The alternative would be to have all users a member of some command group that had executable permissions.
------------------
Just for reference, here is the yad dialog that was caussing me problems:
Code: Select all
yad --fixed --title="$(_n 'SliTaz admin password')" --window-icon=$icon \
--width=520 --on-top --center \
--image=$icon --image-on-top \
--text="$(_n 'Please enter root password (default root) to execute:')\n
<span foreground=\"red\"><tt><b>$(basename "$CMD1")</b></tt></span>\n" \
--form \
--field="$(_n 'Password:'):H" $PASSWD \
--field="$(_n 'Autosave password'):CHK" $CHECKED \
--button="gtk-ok:0" \
--button="gtk-cancel:1"
Edit 1:
Now that I got tazbox working. The script "/usr/local/bin/default_packagemanager" sould be:
Code: Select all
#!/bin/sh
if [ "`id -u`" -eq 0 ]; then
exec tazpanel pkgs
else
exec tazbox su tazpanel pkgs
fi
Edit 2 I also need to add executable permission for "world" on /usr/bin/wmexit.
this file has been updated (see notes below):s243a wrote:Here's a ".vdi" file for virtualbox (with guest additions insalled):
TazPup64-PreAlpha-15.vdi
to use it add it you need to add it as one of the hard drives in a virtual machine.
This issue has been fixed in the savefile within the virtual machine by installing yad-htlm with the command:If you run as a user other than root, use the "su" command to make changes as root. Currently tazbox isn't working which allows a graphical version of su. I think this this is an issue with the yad package. I'll check to see if I'm missing any dependencies for yad. At this point running as root will be easier but users tux and spot should work.
Code: Select all
tazpkg get-install yad-html --forced
1. populated items in the lxde desktop folder for spot, root and tux and called "tazbox su" in the run command where appropariate:
2. changed the desktop for user spot to jwm
3. made changes to the logout script called on the tint2 panel (running in lxde) so that it exits the window if and only if it was started from the console; whereas if the desktop was started from the graphical version of slim then it logs the user out instead of exiting the windows manager.
4. Fixed logout/wmexit issues with non root users.
I actually don't know much about the differences between lxde and jwm. I just included lxde because that is what is used in mistfire's version of tazpup and I incuded jwm because that is what puppy usually uses.Lobster wrote:Bravo
Lobster interlude
I am using and getting used to LXDE on Raspberrian, which runs on the Raspberry Pi and x86 processors
Normal pre-alpha service is now resumed
I find that I interact much more with the desktop than the window manager with the exception that jwm provides a panel by default whereas I'm not sure if lxde provides a default panel so I installed tint2 as the panel because I had problems with lxpanel.
I've updated the ".vdi" save file again to fix issues with rox-pinboard not starting for users root and spot when started via the graphical version of slim. See post.s243a wrote:this file has been updated (see notes below):s243a wrote:Here's a ".vdi" file for virtualbox (with guest additions insalled):
TazPup64-PreAlpha-15.vdi
to use it add it you need to add it as one of the hard drives in a virtual machine.
This issue has been fixed in the savefile within the virtual machine by installing yad-htlm with the command:If you run as a user other than root, use the "su" command to make changes as root. Currently tazbox isn't working which allows a graphical version of su. I think this this is an issue with the yad package. I'll check to see if I'm missing any dependencies for yad. At this point running as root will be easier but users tux and spot should work.I've also for (the save file only):Code: Select all
tazpkg get-install yad-html --forced
1. populated items in the lxde desktop folder for spot, root and tux and called "tazbox su" in the run command where appropariate:
2. changed the desktop for user spot to jwm
3. made changes to the logout script called on the tint2 panel (running in lxde) so that it exits the window if and only if it was started from the console; whereas if the desktop was started from the graphical version of slim then it logs the user out instead of exiting the windows manager.
4. Fixed logout/wmexit issues with non root users.
http://murga-linux.com/puppy/viewtopic. ... 47#1026847
I also made it so that on the rox pinboard, non root users could use the "package manager" and "puppy universal installer". This was done by making sure that "tazbox su" was called if the user wasn't root.
These changes will eventually be incorporated into a new ISO release.
Here are some more releases:
TazPup64-PreAlpha-16.iso
TazPup64-PreAlpha-17.iso
And .vdi files for Virtualbox (and other virtual machines/emulators):
TazPup64-PreAlpha16.vdi
PreAlpha17, is untested and I was exprerminting with the premissions in the .vdi for preALpha16. I recommend that people wait until I test PreAlpha17 and creat a .vdi file for PreAlpha17.
I added urxvt to PreAlpha17 because some people think it's essential. See thread:
http://murga-linux.com/puppy/viewtopic.php?t=116050
I also added vim because nano doesn't seem to work well for TazPup64.
TazPup64-PreAlpha-16.iso
TazPup64-PreAlpha-17.iso
And .vdi files for Virtualbox (and other virtual machines/emulators):
TazPup64-PreAlpha16.vdi
PreAlpha17, is untested and I was exprerminting with the premissions in the .vdi for preALpha16. I recommend that people wait until I test PreAlpha17 and creat a .vdi file for PreAlpha17.
I added urxvt to PreAlpha17 because some people think it's essential. See thread:
http://murga-linux.com/puppy/viewtopic.php?t=116050
I also added vim because nano doesn't seem to work well for TazPup64.
Here are two .vdi (for virtualbox and other virtualizaiton/emulation tools):
TazPup64-PreAlpha-17-spot.vdi - auto logs into spot (jwm window manager)
TazPup64-PreAlpha-17.vdi (newer) - auto logs into tux (lxde window manager)
The one above that ends in "-spot" is older and it auto logs into spot because I broke the lxde desktop for tux in this version. My workaround was to log in as root and start tux's desktop using the su command. See thread:
http://murga-linux.com/puppy/viewtopic.php?t=116065
Somehow this seems to have fixed the issues with logging into tux (using the lxde desktop). I'm not sure why this fixed the issue but I might compare each .vdi file and see if I can identify the issue.
note: While I did some stuff to make things smoother for non-root users, it is probably still easy to run as root. For instance the virtualbox shared clipboard is currently only working as root.
Other Notes:
Also there are no passwords for tux and spot (just press enter for the password). The password for root is "root".
If you boot with the screen=text option (as root) you can type startlxde to start lxde or startx_jwm to start jwm. These commands may or maynot work with other users.
If you want to boot into text mode (i.e. boot parameter screen=text) and switch to another users destktop/WM, then follow the scrips in the thread:
http://murga-linux.com/puppy/viewtopic.php?t=116065
TazPup64-PreAlpha-17-spot.vdi - auto logs into spot (jwm window manager)
TazPup64-PreAlpha-17.vdi (newer) - auto logs into tux (lxde window manager)
The one above that ends in "-spot" is older and it auto logs into spot because I broke the lxde desktop for tux in this version. My workaround was to log in as root and start tux's desktop using the su command. See thread:
http://murga-linux.com/puppy/viewtopic.php?t=116065
Somehow this seems to have fixed the issues with logging into tux (using the lxde desktop). I'm not sure why this fixed the issue but I might compare each .vdi file and see if I can identify the issue.
note: While I did some stuff to make things smoother for non-root users, it is probably still easy to run as root. For instance the virtualbox shared clipboard is currently only working as root.
Other Notes:
Also there are no passwords for tux and spot (just press enter for the password). The password for root is "root".
If you boot with the screen=text option (as root) you can type startlxde to start lxde or startx_jwm to start jwm. These commands may or maynot work with other users.
If you want to boot into text mode (i.e. boot parameter screen=text) and switch to another users destktop/WM, then follow the scrips in the thread:
http://murga-linux.com/puppy/viewtopic.php?t=116065
http://murga-linux.com/puppy/viewtopic. ... 14#1025914s243a wrote:I see that rather than installing python3-pygobject, that I can build it using pip:s243a wrote:
dropbox-2019.02.14-x86_64.tazpkg
built from deb file, with nautilus patch (see post) (untested)
Edit: I get the following error when I try to run dropbox:
I also had to install python3-pygobject manually for some reason. Adding the dependency didn't seem to atomically install this for me. I'll check to see if I spelled it right.Code: Select all
sh-4.4# dropbox start -i Starting Dropbox...Traceback (most recent call last): File "/usr/bin/dropbox", line 1443, in start download() File "/usr/bin/dropbox", line 295, in download gi.require_version('Gdk', '3.0') File "/usr/lib/python3.6/site-packages/gi/__init__.py", line 127, in require_version raise ValueError('Namespace %s not available' % namespace) ValueError: Namespace Gdk not availablehttps://pygobject.readthedocs.io/en/lat ... arted.htmlCode: Select all
Execute pip3 install pycairo to build and install Pycairo Execute pip3 install PyGObject to build and install PyGObject
Presumably having a devx will be helpful to build these python packages. Fortunately I just built devX:
https://www.dropbox.com/s/0nbhvhfyw6lts ... 4.sfs?dl=0
using a modified version of mistfires /usr/bin/mk-devx script.
Since I already have this installed (via python3-gobject. I ran the following command:but it didn't work so I have some troubleshooting to do. The first step is to add the "--no-clean" option so that pip doesn't delete the temporary files.Code: Select all
pip3 install --upgrade --force-reinstall PyGObject
Edit 2:Now nativate to tmp folder. In my case:Code: Select all
pip3 install --no-clean --upgrade --force-reinstall PyGObjectthen try to build with the command:Code: Select all
/tmp/pip-install-r57wjyvc/PyGObjectand I get the error:Code: Select all
python3 setup.py installI have installed xorg-pixman maybe I need to tell pkg-config how to find it.Code: Select all
Package 'pixman-1', required by 'cairo', not found Command '('pkg-config', '--print-errors', '--exists', 'cairo >= 0')' returned non-zero exit status 1.
Edit 3:
The solution was to install xorg-pixman-dev. I also needed to install libpng-dev libpng16-dev
I get now get the error:I'll try installing the following packages to fix the error:Code: Select all
Package 'xcb-shm', required by 'cairo', not found Command '('pkg-config', '--print-errors', '--exists', 'cairo >= 0')' returned non-zero exit status 1.
xorg-libxshmfence-dev xcb-util-xrm-dev xorg-libxcb-dev xorg-xcb-util-dev xorg-xcb-util-cursor-dev xorg-xcb-util-image-dev xorg-xcb-util-keysyms-dev xorg-xcb-util-renderutil-dev xorg-xcb-util-wm-dev
That seemd to solve the issue. I now get the error:I'll try installing xorg-dev-proto to fix this error. That fixed the error.Code: Select all
Package 'xproto', required by 'xau', not found Command '('pkg-config', '--print-errors', '--exists', 'cairo >= 0')' returned non-zero exit status 1.
I now get the errorI'll install python3-pycairo-dev to see if that fixes the error. That fixed the error.Code: Select all
Package py3cairo was not found in the pkg-config search path. Perhaps you should add the directory containing `py3cairo.pc' to the PKG_CONFIG_PATH environment variable No package 'py3cairo' found Command '('pkg-config', '--print-errors', '--exists', 'py3cairo >= 1.11.1')' returned non-zero exit status 1.
I new get the error.I'll try installing python3-dev to fix this error.Code: Select all
gi/gimodule.c:24:10: fatal error: Python.h: No such file or directory #include <Python.h> ^~~~~~~~~~ compilation terminated. error: command 'x86_64-slitaz-linux-gcc' failed with exit status 1
I now get the error:I think that limits.h comes from the kernal sources.Code: Select all
/usr/include/bits/local_lim.h:38:10: fatal error: linux/limits.h: No such file or directory #include <linux/limits.h> ^~~~~~~~~~~~~~~~ compilation terminated. error: command 'x86_64-slitaz-linux-gcc' failed with exit status 1
I built an updated version of devX.
devx_tazpup-0.2.sfs
First I went though the files that I was missing when I was trying to build python3-pygobject see post:
http://murga-linux.com/puppy/viewtopic. ... 14#1025914
except that I haven't yet included gir1.2-gtk-3.0_3.22.11-1_x86_64.tazpkg into devx. See post:
http://murga-linux.com/puppy/viewtopic. ... 70#1025970
I also went though the repository (manually) and added any missing file I noticed that had "-dev" in its name. I created a spreadsheet showing all the packages and I want to fix the headings before I explain the spreadsheet.
Note: I haven't yet tested this build of devX.
I put the buildkit source on github.
https://github.com/s243a/TazPup64_BuildKit
Currently, you cannot build from the github source alone because I didn't yet code a way to download binaries based on the ".binary.meta" files. See post:
Copy a directory structure except for binaries
The actual binaries are avialable in:
BuildKit%28TazPup64%29-PreAlpha17%28unclean%29.tar.gz
but I made a fair bit of changes without testing the build kit. Instead I've been modifying the rootfs via the command:
mount_rootfs64
and then making the iso from the modified rootfs with the command:
make_ISO_Fm_slitaz-rootfs
The actual command to build TazPup64 from scratch is:
make-tazpup.sh
but I recommend waiting until I do my next "from scratch build" before trying this last command.
However, if one disregards this advice the configuration file for make-tazpup.sh is:
defaults
https://github.com/s243a/TazPup64_BuildKit
Currently, you cannot build from the github source alone because I didn't yet code a way to download binaries based on the ".binary.meta" files. See post:
Copy a directory structure except for binaries
The actual binaries are avialable in:
BuildKit%28TazPup64%29-PreAlpha17%28unclean%29.tar.gz
but I made a fair bit of changes without testing the build kit. Instead I've been modifying the rootfs via the command:
mount_rootfs64
and then making the iso from the modified rootfs with the command:
make_ISO_Fm_slitaz-rootfs
The actual command to build TazPup64 from scratch is:
make-tazpup.sh
but I recommend waiting until I do my next "from scratch build" before trying this last command.
However, if one disregards this advice the configuration file for make-tazpup.sh is:
defaults
Find me on [url=https://www.minds.com/ns_tidder]minds[/url] and on [url=https://www.pearltrees.com/s243a/puppy-linux/id12399810]pearltrees[/url].