Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore x86_64 => Topic started by: jusjason on September 08, 2024, 04:58:03 AM
-
I am am a new dCore user and am trying to add foxclone (https://foxclone.org/index.html) to dCore-bionic64.
For testing sake I am working in a Qemu session created with sudo qemu-system-x86_64 -m 2G -smp 4 -cdrom dCore-bionic64.iso -machine q35
I am doing this to find a working process that I will later use with a USB drive on actual hardware.
The steps I have tried are to download the .deb file from here (https://foxclone.org/downloads/foxclone52_amd64.deb) to the /opt/debextra folder and then run sce-import foxclone52_amd64.deb
The sce-import does not seem to be finding the deb package quite the way I would expect. It seems like something is found and decompressed to terminal, but errors out in the end that the package is not available. This would be partially correct, as the package is not available in the Ubuntu nor dCore repos, but judging by the long splurge of decompressed bin ( ? I guess ?) that is displayed on terminal when sce-import is run I suspect that it is finding the package in the /opt/debextra/ folder but not processing it as I would hope.
Additionally I did try to run sudo deb2sce ....
of the downloaded foxclone.deb package , but this was not successful and errors with - not a standard Ubuntu ,dCore or metapackage.
Are there other steps needed to add this external deb package ?
-
Where's the disk in the qemu?
-
Where's the disk in the qemu?
I am not using/creating any permanent storage in Qemu. I am creating a temp system to check and learn how to import the FoxClone deb package. The VM will not be used nor required after I have solved the issue.
Importing other packages that can be found in the Ubuntu/dCore repos that require only the use of sce-import has been successfully tested - so this is not part of the issue.
-
Some more findings -
There seem to be 2 possible ways to using the deb2sce command
sudo deb2sce foxclone52_amd64.deb
or importing + loading + running
sce-import -o sce-deb2sce
sce-load sce-deb2sce
sce-deb2sce foxclone52_amd64.deb
using sudo deb2sce - the error returned is foxclone is not a standard Ubuntu , dCore or mettapacakge - exiting
while using the other method results in invalid tar magic.
I have tested the deb file on an Ubuntu machine , and had no issue installing it there.
For clarity the steps so far :
Create temp machine with Qemu from a freshly downloaed iso
sudo qemu-system-x86_64 -m 2G -smp 4 -cdrom dCore-bionic64.iso -machine q35
once running - in dCore
import + load ca-certificates
sce-import -n ca-certificates && sce-load ca-certificates
fetch the deb package
wget https://foxclone.org/downloads/foxclone52_amd64.deb
Try conversion
sudo deb2sce foxclone52_amd64.deb
or
sce-import -o sce-deb2sce
sce-load sce-deb2sce
sce-deb2sce foxclone52_amd64.deb
-
Hi jusjason
Welcome to the forum.
I did a little searching in the forum and found a post with
an error like yours from about 9 years ago:
https://forum.tinycorelinux.net/index.php/topic,18321.msg111752.html#msg111752
-
Thank you @Rich for the reply
I have tried two ideas that I think have grasped from that thread - compatibly issue between versions -
dCore-bionic64.iso + sudo deb2sce ....
https://foxclone.org/downloads/foxclone.deb
https://foxclone.org/downloads/foxclone34_amd64.deb
https://foxclone.org/downloads/foxclone38_amd64.deb
https://foxclone.org/downloads/foxclone40_amd64.deb
https://foxclone.org/downloads/foxclone45_amd64.deb
https://foxclone.org/downloads/foxclone50_amd64.deb
https://foxclone.org/downloads/foxclone52_amd64.deb
All were unable to be converted with the error that this is not a standard Ubuntu , dCore or mettapacakge
and -
Although I have no experience with creating or adding a deb package to a repo, this was my guess after following the README
Add the download link as an extra repo in /opt/debextra
echo "https://foxclone.org/downloads/" > /opt/debextra/foxclone
then try import
sce-import foxclone
This returns " The following repository is not availibe : https://foxclone.org/downloads/"
What would be the correct way to add this as an extra repo ? Am I on the right path ?
-
It was version issues after all.
dCore-bionic64.iso + https://foxclone.org/downloads/foxclone45_amd64.deb
is converted without error, newer versions fail
Good progress !
Tying to run the package results in dependency issues - I would expect that, but this is new waters for me - Is there a way to get a list of missing required dependencies to install ?
-
Hi jusjason
Some more findings -
There seem to be 2 possible ways to using the deb2sce command
sudo deb2sce foxclone52_amd64.deb
or importing + loading + running
sce-import -o sce-deb2sce
sce-load sce-deb2sce
sce-deb2sce foxclone52_amd64.deb
using sudo deb2sce - the error returned is foxclone is not a standard Ubuntu , dCore or mettapacakge - exiting
while using the other method results in invalid tar magic. ...
I think I found something.
I downloaded the foxclone52 deb and took a look inside.
In the past when I've done this I found .deb archives contained:
control.tar.gz and data.tar.gz.
The foxclone52 archive contained:
control.tar.zst and data.tar.zst.
It's zstd compression instead of gzip. The tar command
being used is probably the busybox version which can't
handle zstd. That's likely the source of the invalid tar magic.
It's also possible that may be the source of the not a standard
Ubuntu , dCore or mettapacakge error.
I think you need to install tar and zstd.
-
I had a look in the control file contained in the deb package and found a list of dependencies which I installed . I did not get a full start, as I am running only dCore ( no GUI) an foxclone is a GUI based tool, but I think that I now have a working method for installing the package so I can move onto a full setup on USB.. This is still a bit of a clunky process , the dependency list is quite tedious. I appreciate even more the value of scripts like deb2sce now.
Depends: policykit-1,mount,grep,parted,partclone,coreutils,util-linux,diffutils,psmisc,os-prober,pigz,qpdfview,hdparm,nvme-cli,util-linux
Thanks @Rich for the tips and pointers
-
Hi jusjason
You are quite welcome. Keep us apprised on your progress.