oh yesss... .DEB-installer (Beta)
I just rebooted, and most applications are gone
It seems it was no good idea, to call pupget for deinstallation first, when you install a deb that was installed already before.
After deinstallation, you might have to reboot immedeatly before you install the new program (due to unionfs).
How can I solve that?
Force the installation to stop with an urgent message to reboot - the cleanest way, but annoying.
Or do not use pupget.
I could create an extra-file (xxx.links), that stores the names of the symlinks created by update-alternatives on first installation.
Then when you re-install over an existing package of the same name, it will create a new xxx.files, this time without the symlinks. So the installer had to add now in a second step the entrys from the first xxx.links to xxx.files.
Like this you could re-install without uninstalling first.
This would not be 100% correct in cases, when a package of the same name contains less symlinks, but I think that risk would be acceptable.
This has priority, must do that tomorrow.
Until then, reboot when re-installing, after pupget uninstalled the old package.
Mark
It seems it was no good idea, to call pupget for deinstallation first, when you install a deb that was installed already before.
After deinstallation, you might have to reboot immedeatly before you install the new program (due to unionfs).
How can I solve that?
Force the installation to stop with an urgent message to reboot - the cleanest way, but annoying.
Or do not use pupget.
I could create an extra-file (xxx.links), that stores the names of the symlinks created by update-alternatives on first installation.
Then when you re-install over an existing package of the same name, it will create a new xxx.files, this time without the symlinks. So the installer had to add now in a second step the entrys from the first xxx.links to xxx.files.
Like this you could re-install without uninstalling first.
This would not be 100% correct in cases, when a package of the same name contains less symlinks, but I think that risk would be acceptable.
This has priority, must do that tomorrow.
Until then, reboot when re-installing, after pupget uninstalled the old package.
Mark
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Mark,
Another complication is that pupget is slightly modified to work in puppy2.
I think you mentioned that you are using a cutdown version of pupget.
The new pupget is better, it doesn't write to a unionfs layer directly. The pupget
in puppy1 does, which can badly upset unionfs management and you have to
reboot.
So, in puppy2, should be able to uninstall then immediatelly reinstall, without
rebooting.
The problem is, puppy2 is better all round, and personally I think, dependent on
the next two snapshots becoming highly stable, development should focus on
puppy2. Just a suggestion of course!
I'll be uploading another snapshot real soon.
Another complication is that pupget is slightly modified to work in puppy2.
I think you mentioned that you are using a cutdown version of pupget.
The new pupget is better, it doesn't write to a unionfs layer directly. The pupget
in puppy1 does, which can badly upset unionfs management and you have to
reboot.
So, in puppy2, should be able to uninstall then immediatelly reinstall, without
rebooting.
The problem is, puppy2 is better all round, and personally I think, dependent on
the next two snapshots becoming highly stable, development should focus on
puppy2. Just a suggestion of course!
I'll be uploading another snapshot real soon.
No, in the Debinstaller I call pupget directly
pupget -xxx.deb
The cutdown version I use just in the Pet-creator, as it seems not to have the option to install an alien package passed as a parameter like
pupget +/tmp/xxx.deb.tar.gz
This is simply a symlink to /WhereYouDownloaded/xxx.deb.tar.gz.pet000
The pet000 is a simple alien package with 2 additional files (xxx.menu and xxx.desc , which were created by the debian-installer or added manually per texteditor).
Ok, I will try your new Puppy2 when it comes out.
If that solves my problems, I would add the "you must reboot now" for Puppy1, and use it as it is now for Puppy2
Thanks for that info, Mark (didn't I want to go asleep 12 hours ago?)
pupget -xxx.deb
The cutdown version I use just in the Pet-creator, as it seems not to have the option to install an alien package passed as a parameter like
pupget +/tmp/xxx.deb.tar.gz
This is simply a symlink to /WhereYouDownloaded/xxx.deb.tar.gz.pet000
The pet000 is a simple alien package with 2 additional files (xxx.menu and xxx.desc , which were created by the debian-installer or added manually per texteditor).
Ok, I will try your new Puppy2 when it comes out.
If that solves my problems, I would add the "you must reboot now" for Puppy1, and use it as it is now for Puppy2
Thanks for that info, Mark (didn't I want to go asleep 12 hours ago?)
instead of rebooting, you can unmount/mount using unionfs, using the same commands that mounted the drive originally ... however, this would require that you know how the files systems were originally mounted ... maybe Puppy could create a re-mount script when it boots, that programs could use for deinstallation purposesAfter deinstallation, you might have to reboot immedeatly before you install the new program (due to unionfs).
How can I solve that?
i think the tabbed Dillo does support the clipboard, but the official version doesn't (or didn't)Dillo can be so frustrating... doesn't even support the clipboard
yes, tabbed dillo supports the clipboard
Hm.. unmounting.. ok, that starts getting complicated due to the wide variety how Puppy is used... I think I really should concentrate on Puppy2, and leave in just a basic, non-optimized support for Puppy1.
There still is so much to code, like better menu-handling etc. (just recognized the menu is "pushed down" by new installed dotpups.
I think the whole menu-stuff has to be rewritten including puppys backup-scripts.
In this installer I already added 2 new things: submenus and comments in jwmrc used as markers.
I love puppy1, but somewhen the biggest love finds an end
Thanks, Mark
Hm.. unmounting.. ok, that starts getting complicated due to the wide variety how Puppy is used... I think I really should concentrate on Puppy2, and leave in just a basic, non-optimized support for Puppy1.
There still is so much to code, like better menu-handling etc. (just recognized the menu is "pushed down" by new installed dotpups.
I think the whole menu-stuff has to be rewritten including puppys backup-scripts.
In this installer I already added 2 new things: submenus and comments in jwmrc used as markers.
I love puppy1, but somewhen the biggest love finds an end
Thanks, Mark
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Mark,
I tested the alpha08 again in puppy2, and had a closer look where it goes wrong
at step4. This is when installing windowmaker. Installing the wmaker .deb file,
at step 4 the pb-debianinstaller reports various dependencies missing.
So, I looked in your check-dependencies script, just a very quick look, I don't
know anything about puppybasic -- but, it seems you are using 'ldd'.
So, I went to /tmp and checked all the wmaker executables, and ldd works
perfectly. So, it would logically seem that there's a bug in the
check-dependencies script.
I converted pb-debianinstaller into an unleashed package -- even though it's
not quite ready!
I noticed two files, dpkg-deb and dpkg-deb2 -- what is the story there, why
two? Also, is the Busybox dpkg-deb not good enough?
I tested the alpha08 again in puppy2, and had a closer look where it goes wrong
at step4. This is when installing windowmaker. Installing the wmaker .deb file,
at step 4 the pb-debianinstaller reports various dependencies missing.
So, I looked in your check-dependencies script, just a very quick look, I don't
know anything about puppybasic -- but, it seems you are using 'ldd'.
So, I went to /tmp and checked all the wmaker executables, and ldd works
perfectly. So, it would logically seem that there's a bug in the
check-dependencies script.
I converted pb-debianinstaller into an unleashed package -- even though it's
not quite ready!
I noticed two files, dpkg-deb and dpkg-deb2 -- what is the story there, why
two? Also, is the Busybox dpkg-deb not good enough?
I currently cannot reproduce your error in windowmaker.
Here is a screenshot of puppy2:
http://dotpups.de/pics/puppy/debinstp2bugtmp.jpg
I marked 3 areas in red:
in the left panel, of the filemanager, you see /tmp
It does NOT show the temporary folder from Debianinstaller.
In the right panel, you see the same folder in /initrd
Here, the folder is visible.
This prevents my installer from working correctly, for example at startup it does not recognize temporary files that should be deleted.
This is, what I described too in the developperforum:
http://www.puppyos.com/nfphpbb/viewtopic.php?t=79
Until this filesystem-problem is not solved, I will not be able to do more testing in Puppy2 unfortunately
In Puppy 1, it worked fine, so I'm currently without idea, why you have these troubles
Maybe they are related to the problems I have myself in Puppy2.
But note, that on the screenshot just libwraster is mentioned as missing (I have no extension xxx_003.sfs installed).
Mark
Here is a screenshot of puppy2:
http://dotpups.de/pics/puppy/debinstp2bugtmp.jpg
I marked 3 areas in red:
in the left panel, of the filemanager, you see /tmp
It does NOT show the temporary folder from Debianinstaller.
In the right panel, you see the same folder in /initrd
Here, the folder is visible.
This prevents my installer from working correctly, for example at startup it does not recognize temporary files that should be deleted.
This is, what I described too in the developperforum:
http://www.puppyos.com/nfphpbb/viewtopic.php?t=79
Until this filesystem-problem is not solved, I will not be able to do more testing in Puppy2 unfortunately
In Puppy 1, it worked fine, so I'm currently without idea, why you have these troubles
Maybe they are related to the problems I have myself in Puppy2.
But note, that on the screenshot just libwraster is mentioned as missing (I have no extension xxx_003.sfs installed).
Mark
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
When I got to step4 of the install, I used Rox-Filer to browse the /tmpMU wrote: It does NOT show the temporary folder from Debianinstaller.
In the right panel, you see the same folder in /initrd
directory, and the temporary wmaker files were visible -- I was able to use Rox
to go into all directories of wmaker and open terminals and run ldd.
Also, I think that the invisibility problem you report applies to the GUI file
managers. If you try
Code: Select all
# ls /tmp/PB-Debinstall
...at least, I remember that when I earlier encountered this bug.
Note, I have only got the invisiblity bug when extra .sfs files are loaded.
Just booting from the live-cd, nothing no other unionfs layers, everything
seems to be visible.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Mark,
Can you check something. Can you look in /initrd/pup_rw/tmp and see if there
is any hidden file that seems related to this directory name, that is has the string
"PB-Debinstall" in it:
/tmp/PB-Debinstall
Note, I just tested installing wmaker again, I can't reproduce your invisibility
problem. Using Rox, everything in /tmp is visible.
...but, I am running a pristine system, running totally in ram, so no prior
history to worry about.
Can you check something. Can you look in /initrd/pup_rw/tmp and see if there
is any hidden file that seems related to this directory name, that is has the string
"PB-Debinstall" in it:
/tmp/PB-Debinstall
Note, I just tested installing wmaker again, I can't reproduce your invisibility
problem. Using Rox, everything in /tmp is visible.
...but, I am running a pristine system, running totally in ram, so no prior
history to worry about.
The bug appears after you rebooted the first time, what creates pup_safe.3fs (I use a frugal install, pupmode 12, as I have no CD-burner).
So the bug seems to be caused when Puppy mounts pup_safe.3fs.
It affects the whole filesystem , /root /tmp /usr
The easiest way to reproduce it:
Create this script in a new folder:
http://www.puppyos.com/nfphpbb/viewtopic.php?p=278#278
run it, it should create 300 textfiles.
If you encounter the bug, less than 100 textfiles are visible.
Mark
So the bug seems to be caused when Puppy mounts pup_safe.3fs.
It affects the whole filesystem , /root /tmp /usr
The easiest way to reproduce it:
Create this script in a new folder:
http://www.puppyos.com/nfphpbb/viewtopic.php?p=278#278
run it, it should create 300 textfiles.
If you encounter the bug, less than 100 textfiles are visible.
Mark
Last edited by MU on Tue 18 Apr 2006, 01:11, edited 1 time in total.
Code: Select all
sh-3.00# ls -al /tmp
drwxr-xr-x 13 root root 2048 Apr 18 01:31 .
drwxr-xr-x 15 root root 1024 Apr 14 00:28 ..
-rw------- 1 root root 167061 Apr 15 04:54 2006-03-nagiosoncd.pdf
-rw-r--r-- 1 root root 0 Apr 12 00:41 bootcnt.txt
-rw-r--r-- 1 root root 77425 Apr 17 22:55 DOTfvwm95.pwizard_patched.backup
-rw-r--r-- 1 root root 77564 Apr 18 00:01 DOTfvwm95rc
-rw-r--r-- 1 root root 18747 Apr 18 00:01 DOTicemenu
-rw-r--r-- 1 root root 21841 Apr 18 00:01 DOTindex.html
-rw-r--r-- 1 root root 30199 Apr 17 22:55 DOTjwm.pwizard_patched.backup
-rw-r--r-- 1 root root 30350 Apr 18 00:01 DOTjwmrc
-rwxr-xr-x 1 root root 103 Apr 17 23:59 dotpup.sh
-rw-r--r-- 1 root root 2 Apr 17 22:55 dpimenu.txt
-rw-r--r-- 1 root root 86 Apr 18 00:00 forcealienpkgremove.txt
-rw-r--r-- 1 root root 77564 Apr 18 00:01 fvwm95rcBACKUP
drwxr-xr-x 2 root root 1024 Apr 12 08:56 hsperfdata_root
-rw-r--r-- 1 root root 18747 Apr 18 00:01 icemenuBACKUP
drwxrwxrwt 2 root root 1024 Apr 14 00:42 .ICE-unix
-rw-r--r-- 1 root root 18612 Apr 17 22:55 icewmmenu.pwizard.backup
-rw-r--r-- 1 root root 30350 Apr 18 00:01 jwmrcBACKUP
drwx------ 2 root root 1024 Apr 14 00:41 kde-root
drwx------ 3 root root 1024 Apr 14 00:42 ksocket-root
-rw-r--r-- 1 root root 8267 Apr 18 00:00 livepackages.txt
-rw-r--r-- 1 root root 0 Apr 18 00:02 missinglibs0.txt
-rw-r--r-- 1 root root 10042 Apr 18 00:02 missinglibs.txt
srwxr-xr-x 1 root root 0 Apr 12 10:43 OSL_PIPE_0_SingleOfficeIPC_bfa67ba891bd9b76f67a649f29db7e59
-rwxr-xr-x 1 root root 9820 Apr 18 00:00 pkgdialog
drwx------ 2 root root 1024 Apr 15 03:56 plugtmp
-rw-r--r-- 1 root root 3682 Apr 12 08:45 profile
-rw-r--r-- 1 root root 401 May 20 2005 readme.txt
-rw-r--r-- 1 root root 177 Apr 18 00:01 rettags.txt
-rw-r--r-- 1 root root 5 Apr 12 08:45 rettag.txt
drwx------ 2 root root 1024 Apr 17 23:55 root-c8ejlf
-rw-r--r-- 1 root root 325 Apr 18 2006 scanmodulemsgs.txt
-rw------- 1 root root 125524 Apr 15 04:09 synaptics-0.14.4.tar.bz2
-rw-r--r-- 1 root root 1392 Apr 12 08:35 taglocales.txt
-rw-r--r-- 1 root root 8267 Apr 18 00:00 templive.txt
-rw-r--r-- 1 root root 148 Apr 18 01:31 testeide.txt
drwx------ 4 root root 1024 Apr 12 16:41 .wine-0
-rw-r--r-- 1 root root 1 Apr 18 01:31 wmexitmode.txt
-r--r--r-- 1 root root 11 Apr 18 01:31 .X0-lock
drwxrwxrwt 2 root root 1024 Apr 18 01:31 .X11-unix
-rw-r--r-- 1 root root 1048 Apr 18 01:31 xerrs.txt
-rw-r--r-- 1 root root 8689 Apr 18 00:00 zippidoodah.txt
sh-3.00#
Code: Select all
sh-3.00# ls -al /initrd/pup_rw/tmp
drwxr-xr-x 11 root root 2048 Apr 18 01:31 .
drwxr-xr-x 13 root root 1024 Apr 14 00:28 ..
-rw------- 1 root root 167061 Apr 15 04:54 2006-03-nagiosoncd.pdf
-rw-r--r-- 1 root root 422 Apr 18 00:00 alienpackages.txt
-rw-r--r-- 1 root root 0 Apr 12 00:41 bootcnt.txt
-rw-r--r-- 1 root root 77425 Apr 17 22:55 DOTfvwm95.pwizard_patched.backup
-rw-r--r-- 1 root root 77564 Apr 18 00:01 DOTfvwm95rc
-rw-r--r-- 1 root root 18747 Apr 18 00:01 DOTicemenu
-rw-r--r-- 1 root root 21841 Apr 18 00:01 DOTindex.html
-rw-r--r-- 1 root root 30199 Apr 17 22:55 DOTjwm.pwizard_patched.backup
-rw-r--r-- 1 root root 30350 Apr 18 00:01 DOTjwmrc
-rwxr-xr-x 1 root root 103 Apr 17 23:59 dotpup.sh
-rw-r--r-- 1 root root 2 Apr 17 22:55 dpimenu.txt
-rw-r--r-- 1 root root 86 Apr 18 00:00 forcealienpkgremove.txt
-rw-r--r-- 1 root root 86 Apr 18 00:00 forcepkgremove.txt
-rw-r--r-- 1 root root 77564 Apr 18 00:01 fvwm95rcBACKUP
drwxr-xr-x 2 root root 1024 Apr 12 08:56 hsperfdata_root
-rw-r--r-- 1 root root 18747 Apr 18 00:01 icemenuBACKUP
drwxrwxrwt 2 root root 1024 Apr 14 00:42 .ICE-unix
-rw-r--r-- 1 root root 18612 Apr 17 22:55 icewmmenu.pwizard.backup
-rw-r--r-- 1 root root 30350 Apr 18 00:01 jwmrcBACKUP
drwx------ 2 root root 1024 Apr 14 00:41 kde-root
drwx------ 3 root root 1024 Apr 14 00:42 ksocket-root
-rw-r--r-- 1 root root 8267 Apr 18 00:00 livepackages.txt
-rw-r--r-- 1 root root 0 Apr 18 00:02 missinglibs0.txt
-rw-r--r-- 1 root root 10042 Apr 18 00:02 missinglibs.txt
srwxr-xr-x 1 root root 0 Apr 12 10:43 OSL_PIPE_0_SingleOfficeIPC_bfa67ba891bd9b76f67a649f29db7e59
drwxr-xr-x 4 root root 1024 Apr 17 23:31 PB-Debinstall
-rwxr-xr-x 1 root root 9820 Apr 18 00:00 pkgdialog
drwx------ 2 root root 1024 Apr 15 03:56 plugtmp
-rw-r--r-- 1 root root 3682 Apr 12 08:45 profile
-rw-r--r-- 1 root root 401 May 20 2005 readme.txt
-rw-r--r-- 1 root root 866 Apr 18 00:01 removefileslist.txt
-rw-r--r-- 1 root root 177 Apr 18 00:01 rettags.txt
-rw-r--r-- 1 root root 5 Apr 12 08:45 rettag.txt
drwx------ 2 root root 1024 Apr 17 23:55 root-c8ejlf
-rw-r--r-- 1 root root 325 Apr 18 2006 scanmodulemsgs.txt
-rw------- 1 root root 125524 Apr 15 04:09 synaptics-0.14.4.tar.bz2
-rw-r--r-- 1 root root 1392 Apr 12 08:35 taglocales.txt
-rw-r--r-- 1 root root 8267 Apr 18 00:00 templive.txt
-rw-r--r-- 1 root root 148 Apr 18 01:31 testeide.txt
drwx------ 4 root root 1024 Apr 12 16:41 .wine-0
-rw-r--r-- 1 root root 1 Apr 18 01:31 wmexitmode.txt
-r--r--r-- 1 root root 11 Apr 18 01:31 .X0-lock
drwxrwxrwt 2 root root 1024 Apr 18 01:31 .X11-unix
-rw-r--r-- 1 root root 1048 Apr 18 01:31 xerrs.txt
-rw-r--r-- 1 root root 8689 Apr 18 00:00 zippidoodah.txt
sh-3.00#
- Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
I've noticed that this relies on ghttpd, and was wondering how hard it would be to get it to work with a different webserver. For instance, Grafpup-103 is set to come with Monkey preinstalled (since Monkey can use things like php I figured it was more useful for web designers).
I'm not asking you to port it over, just asking how hard you think it would be to do.
Nathan
I'm not asking you to port it over, just asking how hard you think it would be to do.
Nathan
Bring on the locusts ...
it might work , but I did not try.
move
/root/ghttpd/cgi-bin/easycgi.cgi
and
/root/ghttpd/cgi-bin/runcommand
to the cgi-folder of your webserver.
Move
/root/ghttpd/htdocs/assi1
to the htdocs-folder of your webserver.
Edit
/usr/local/PB-Debian-installer/PB-Debianinstaller
to use your webserver instead of ghttpd.
Mark
move
/root/ghttpd/cgi-bin/easycgi.cgi
and
/root/ghttpd/cgi-bin/runcommand
to the cgi-folder of your webserver.
Move
/root/ghttpd/htdocs/assi1
to the htdocs-folder of your webserver.
Edit
/usr/local/PB-Debian-installer/PB-Debianinstaller
to use your webserver instead of ghttpd.
Mark
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Yes, I do recall reading about this in the unionfs mail-list archives.MU wrote:The easiest way to reproduce it:
Create this script in a new folder:
http://www.puppyos.com/nfphpbb/viewtopic.php?p=278#278
run it, it should create 300 textfiles.
If you encounter the bug, less than 100 textfiles are visible.
This may be due to the old version of unionfs we have to use, and it
probably(?) happens in puppy1 also.
The invisibility bug when installing wmaker is different.
Anyway, I'll do some more testing.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I have investigated further.
There may be a difference, running Puppy2 totally in ram compared with
having a pup_save.3fs file.
I'm doing some testing with puppy running in ram only, k2.6.16.7...
I have tracked down the problem reported above, about the empty box at step2.
The above code is from /root/ghttpd/assi1-scripts/fileselect.
xwin_exec() is returning 'result' value of -1, even though it is working.
By removing the 'if result != 0 then' test, step2 works.
I tried your alternative line using xdialog(), but same bug.
I extracted just this section of code to a separate small PB script, and it
works -- 'result' value is zero.
So, I would say this invalid return value is what is causing all the trouble,
it would be causing the incorrect testing of dependencies also.
Another bug has emerged, didn't get this before.
When testing dependencies, if I am not online, the wget windows do not
terminate. Testing wmaker .deb, which has all these incorrect dependencies,
multiple wget windows are created. Previously, each one terminated then
the next one appears. Now however, I have to manually close each wget
window -- perhaps that same invalid return value bug?
Anyway, I've narrowed down the bug, but don't know what is causing it.
It must be in the xwin_exec() and xdialog() functions, or somehow the
mechanism used to call them -- which would be a bug in wxbasicscript
itself. Whatever, I don't know how to track it further.
There may be a difference, running Puppy2 totally in ram compared with
having a pup_save.3fs file.
I'm doing some testing with puppy running in ram only, k2.6.16.7...
I have tracked down the problem reported above, about the empty box at step2.
Code: Select all
'result , choice = xdialog("--fselect \"\" 30 80 1>/dev/null 2>/dev/null")
DIM xdmsg = "--fselect \"\" 30 80 1>/dev/null 2>/dev/null"
result = xwin_exec("cd " & fsfolder & " && Xdialog " & xdmsg & " 2> /tmp/wxbxdmenu.tmp" )
choice = readfiletail( "/tmp/wxbxdmenu.tmp" )
cleanup()
if result != 0 then
end
end if
xwin_exec() is returning 'result' value of -1, even though it is working.
By removing the 'if result != 0 then' test, step2 works.
I tried your alternative line using xdialog(), but same bug.
I extracted just this section of code to a separate small PB script, and it
works -- 'result' value is zero.
So, I would say this invalid return value is what is causing all the trouble,
it would be causing the incorrect testing of dependencies also.
Another bug has emerged, didn't get this before.
When testing dependencies, if I am not online, the wget windows do not
terminate. Testing wmaker .deb, which has all these incorrect dependencies,
multiple wget windows are created. Previously, each one terminated then
the next one appears. Now however, I have to manually close each wget
window -- perhaps that same invalid return value bug?
Anyway, I've narrowed down the bug, but don't know what is causing it.
It must be in the xwin_exec() and xdialog() functions, or somehow the
mechanism used to call them -- which would be a bug in wxbasicscript
itself. Whatever, I don't know how to track it further.
oh yesss... .DEB-installer (Alpha)
Hello,
I have 108 on my HD.
at "step 1" - "free Diskspace" it just says "MB". It doesn't have a numerical value before it.
I noticed in the screenshots that have been uploaded, it actually says how many mb's are left.
at "step 3" - after i chose a file to install it will hang, showing the file I picked,
underneath "informations on file"
Did I miss something when I installed your file?
I have 108 on my HD.
at "step 1" - "free Diskspace" it just says "MB". It doesn't have a numerical value before it.
I noticed in the screenshots that have been uploaded, it actually says how many mb's are left.
at "step 3" - after i chose a file to install it will hang, showing the file I picked,
underneath "informations on file"
Did I miss something when I installed your file?