Closed tazihad closed 4 months ago
Unknown option 'show-progress'
Error: The JuNest image file junest-x86_64.tar.gz does not exist
I suppose you use Fedora 40 and your wget
is a symlink to wget2
@ivan-hc yes, it's Fedora 40 kinoite
remove "--show-progress" from the script, at line 26, and try again
change
wget -q --show-progress https://github.com/ivan-hc/junest/releases/download/continuous/junest-x86_64.tar.gz
to
wget -q https://github.com/ivan-hc/junest/releases/download/continuous/junest-x86_64.tar.gz
to download silently, or to
wget https://github.com/ivan-hc/junest/releases/download/continuous/junest-x86_64.tar.gz
to have the complete output.
Being wget a symlink to wget2, the output should look alike the wget -q --show-progress
one.
This is a known issue, I've already reported it to the Fedora Reddit community
https://www.reddit.com/r/Fedora/comments/1cf5jpu/switching_from_wget_to_wget2_suddenly_in_fedora/
@ivan-hc thanks. I have put --force-progress
instead. Which works. But still get error.
share/wget/.wget-ocsp
share/wget/.wget-ocsp_hosts
sent 840,338 bytes received 1,342 bytes 561,120.00 bytes/sec
total size is 834,970 speedup is 0.99
cp: cannot stat '': No such file or directory
But I have successfully build an appimage using your firest script which is [sample-junest.sh](https://github.com/ivan-hc/ArchImage/blob/main/sample-junest.sh)
some cp/mv/tar errors are normal during the process, the script checks for the needed files, an to do this, it checks where they may be, not always they are in place.
For example, the cp error above is because the script checks for keywords through 4 levels in /usr/lib and /usr/share, if no keyword has been found at one or more of these 4 levels, then you get a error with cp. However, the needed kayword has been found into at least one of the 4 levels, the needed files are been copied... and the final appimage come out.
Thats all. I've not silenced the errors for debug reasons.
@ivan-hc for me errors are stuck. waited 10 min. No appimage came out
at what point the script stops creating the AppImage?
Note that some steps require many time to be finished, so you have to wait. Do not press CTRL+C.
With the latest changes I've reduced the output, mainly busy with the "rsync" messages, so you can debug more.
Please, use the sample-next-junest.sh script.
Also, be sure you have "imagemagik" installed or appimagetool will not work
Sorry, where is your .junest directory?
Is it in $HOME/.local/share/junest and $HOME/.junest ?
Is so, you must remove them.
I suggest to create a new directory and run the script into it, as I do in the video ( $HOME/Desktop/tmp), not to touch your $HOM directory.
Also, I see that you run the whole path, I'm sure you drag/drop the script in the terminal. Its not so that the script works.
This is a know issue, see https://github.com/ivan-hc/ArchImage/issues/19#issuecomment-2002929214
You must run the script into the directory, like this
./firefox-junest.st
@tazihad have you solved?
@ivan-hc no. new script doesn't work. But your old script works perfectly.
its really strange, have you used the new template?
also, have you followed the instructions I added here https://github.com/ivan-hc/ArchImage#usage ?
I've updated this the day you contacted me the last time https://github.com/ivan-hc/ArchImage/issues/23#issuecomment-2175183044
@ivan-hc I have tried your new script. Perhaps it has something to do with our different distro. I am on Fedora Atomic.
@tazihad in your video you drag/drop the script, while you should run it into the directory like this
./script-junest.sh
EDIT: this is why I've added this step to the guide https://github.com/ivan-hc/ArchImage#what-not-to-do
This is already happened into another issue https://github.com/ivan-hc/ArchImage/issues/19#issuecomment-2002929214
Do not run the script with the whole path.
The video I did above (now also on the README) is the correct way to run the script.
The script should work on any distro, I use Debian.
If you are able to use the old and unsupported sample-junest.sh, you're also able to run the new one in Fedora or somewhere else.
Nothing has been changed, apart the use of the more flexiblwe Bubblewrap instead of the more restrictive PROOT.
@tazihad You no longer responded to my question. Are you still dragging the script into the terminal instead of launching it from inside the directory (i.e. with the "dot")?
I ask because after seeing your video, I updated the readme, adding what to do and what NOT to do, and dragging the script exposing the entire path of the same from inside the working directory is wrong, and it is an already known error https://github.com/ivan-hc/ArchImage/issues/19 .
EDIT: also I can't see the video anywhere anymore. But at least we still have the log
@ivan-hc I still get error. Here;s the log. error log
and this is wrong
user1@fedora:/home/user1$ /home/user1/firefox-junest.sh
must be an empty directory
user1@fedora:/home/user1$ mkdir test
user1@fedora:/home/user1$ mv firefox-junest.sh ./test/
user1@fedora:/home/user1$ cd test
and then run the scrip
user1@fedora:/home/user1/test$ ./firefox-junest.sh
its a bit different.
@ivan-hc I just tested it. It's working now. I put all the script in ~/tmp
.
I get error everytime I run the script.