Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore X86 => dCore x86 Imported Extensions => Topic started by: Jason W on November 04, 2014, 10:42:06 PM
-
I am now testing my first run of an automated "one command" sce directory update. Updating SCE"s that are made from list files, those that use .dep files and depend on other SCE's, as well as standard packages. It would not be possible without the creating the SCE in $SCEDIR/update if the SCE was mounted and in use, nor if we did not use and respect existing .dep or .lst files for dependencies and file lists used in the initial creation of the SCE. And for these three concepts we have JLS to thank, I honestly was hesitant to incorporate each one of them as I am resistent to change, but looking back I am glad I did.
This should amount to a time and troubleshooting saver especially for those using more unstable repos like the current Jessie or Trusty. One command and you know your install is square again.
-
Testing and putting some finishing touches on this concept. Next update will support a 'one command' update of the sce directory for standard Debian packages, SCE's that were imported via a list file, and either of those that make use of a .dep file to use one or more existing SCE's as a dependency..
-
I am considering working an update function into importsce and the existing deb* scripts instead of having a separate update script that would have to duplicate a whole lot of what is existing in the others. "importsce -u" would copy an existing sce to the normal merging directory, then only what has been updated in Debian compatible repos or our prebuilt section or in the startup scripts and *-data.tar.gz will be merged. If you have a huge sce that has only one package from Debian updated since you imported that sce, then only that one package will be re-merged to the updated sce. It will some time calculating the md5sums, but should overall be a huge time and hardware energy saver.
EDIT: A simple change to the getMd5sum function that uses the same logic as determining deps or size has brought performance from about one second per package to 865 .deb files in my import/debs directory getting their md5sums checked in 16 seconds. So an sce made from 865 packages would be updated in the time it takes to unpack it, 16 seconds to check for updated debs, downloading the startup scripts, downloading/merging of any updated debs, then repacking. If few updated debs or prebuilts, then very fast update. I think I will use a list of available startup scripts that is downloaded once per import session the way we are now using a list of *-data.tar.gz files to save time and bandwidth. With these changes it will probably be next week by the time I have a public testing release.
-
hi jason,
well thought out concept!
i'm looking forward testing this new feature :)
keep on hacking.
-
+1 :)
-
There are some issues I did not forsee in mounting and updating an extension in place. One of them and the deal killer is the potential for stale files when files have been changed in the Debian package. This would most likely happen in Debian testing or Ubuntu. I would rather stay with a dependable and solid result of a re-import than risk breakage from file conflicts. That and dependencies of packages can change, though that could be handled it would mean basically having to go through the entire import process anyway. Also, massive code changes to importsce and it's support scripts would have to occur.
Updating is not something that has to happen on a frequent basis, unless using a testing repo that has not stabilized. But in any case, I am working on some streamlining of the import process to make it even quicker as well as the 'one command' update of existing SCE's. Though it may take more time than an update in place method, it can be done unattended requiring little effort from the user and reliably update existing SCE's whether they are from a file list, have dependency SCE's or are a custom built package.
-
updatesce is now in base. Use as follows:
$ updatesce
$ updatesce -r
This will bring up a menu of existing SCEs to choose from. The second one will use the -r RAM option. The non-interactive and size options are by default. The update session will stop at the point when it is found you do not have enough room to update the next SCE. You can choose more than one, up to all.
$ updatesce file
This will update the SCE named file.
$ updatesce all
This will update all the existing SCEs in your SCE directory.
-
Hi Jason and the others
issuing updatesce I get permission denied on /tmp/select.ans
If I chown that file I get
libmatroska5_1.3.0-2_i386.deb is not available as a package. Exiting...
that file is asked from a deb list when I imported minitube
ps minitube doesn t contain the minitube binary
-
hi jason,
i get for a couple of deb2sce-scripts following error messages:
Merging Tiny Core custom start script for libgdk-pixbuf2.0-0: libgdk-pixbuf2.0-0.deb2sce
cat: /tmp/libgdk-pixbuf2.0-0.deb2sce: No such file or directory
rm: cannot remove '/tmp/libgdk-pixbuf2.0-0.deb2sce': No such file or directory
dito for the following deb2sce-scripts.
as a result i get an unusable sce-package that causes permission errors.
-
JLS - I think I have a fix for yours.
netnomad - there seems to be an issue with the tinycorelinux.net network. That would produce your error, I am getting it too off and on. Lets wait until the network issue is resolved, I would need it working to upload a fix anyway.
-
...
Merging Tiny Core custom start script for libgdk-pixbuf2.0-0: libgdk-pixbuf2.0-0.deb2sce
cat: /tmp/libgdk-pixbuf2.0-0.deb2sce: No such file or directory
rm: cannot remove '/tmp/libgdk-pixbuf2.0-0.deb2sce': No such file or directory
...
md5sum: firmware-all.tar.gz.md5.txt: No such file or directory
...
there is no change, always the same behavior :(
the result are broken packages :(
-
Hi,
I have tried updatesce with my first big SCE (openbox, wireless, xfe, alsa, cups, Conky, etc.) having a .lst and .dep associated files and the updatesce worked flawless. No errors.
Now I will updatesce all my others big sce's (multimedia, office, work, mail, etc.) but surely works perfect.
Many thanks for the effort. It makes the maintenance very easy.
-
netnomad - I have not had time today to upload the fix now that the network is back up, I will be able to when I get back to my machine in the next day or so.
-
Netnomad - I have adjusted and uploaded the x86 dCore*.gz files. Please download and test, I will add to git later.
-
hi jason,
i tried and tested
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz.md5.txt
a5a407a7557405532af256c46d8865dc dCore-jessie.gz
btw
the boot-message shows as the version i guess something like 5.14.11.13...
sorry for your efforts, but i get the same results, error messages like:
Merging Tiny Core custom start script for python2.7-minimal: python2.7-minimal.deb2sce
cat: /tmp/python2.7-minimal.deb2sce: No such file or directory
rm: cannot remove '/tmp/python2.7-minimal.deb2sce': No such file or directory
Merging python2.7-minimal
Merging Tiny Core custom start script for python2.7: python2.7.deb2sce
cat: /tmp/python2.7.deb2sce: No such file or directory
rm: cannot remove '/tmp/python2.7.deb2sce': No such file or directory
Merging python2.7
Merging Tiny Core custom start script for python: python.deb2sce
cat: /tmp/python.deb2sce: No such file or directory
rm: cannot remove '/tmp/python.deb2sce': No such file or directory
thank you for your help and commitment,
thank you for your hacking :)
-
netnomad - which package are you trying to import? Name a specific one so I can try the same just to make sure.
I can't reproduce those errors, all is working as expected here, though I see a few odds and ends I can clean up in /tmp once the import session is over.
Does anyone else have the same issue involving the startup scripts?
-
I have added a few fixes to the dCores. Please download a new copy and test.
-
hi jason,
sorry, i did not mention that i have now problems with the importsce-comand, too.
but it makes no difference, because the same error messages appear with updatesce.
i took your last copy
tc@box:~/.MNT/sdb1/live/dcore-testing/boot$ md5sum dCore.gz
26a24bc62db2ede967b8789100ef1257 dCore.gz
this is my lst-file
tc@box:~/.TCE/sce$ cat 000-base-jessie.sce.lst
console-setup
console-data
bash
mc
ssh
rsync
screen
grep
tar
zip
unzip
gzip
bzip2
xz-utils
p7zip-full
nmap
iptables
fail2ban
redsocks
pdnsd
tcpdump
gnupg
laptop-mode-tools
pm-utils
importupdatecheck
man-db
wifi
wpasupplicant
firmware-all
ntfs-3g
lvm2
cryptsetup
libsmartcols1
this is my importsce-command:
tc@box:~$ importsce -n 000-base-jessie
Using the -n option.
debian
#################### 100.0% 0.0 kBps DONE
verifying download...checksum matches OK
used 10950656 local, fetched 0
Using the repo http://ftp.us.debian.org/debian debian jessie main
Creating 000-base-jessie.sce from package list /mnt/sdb2/tce/sce/000-base-jessie.sce.lstUsing Package Index: /etc/sysconfig/tcedir/debian_jessie_main_i386_Packages
Using debian Mirror: http://ftp.us.debian.org/debian
000-base-jessie is from your own custom package list:
Gathering dependency info..
Merging libsmartcols1
Merging libcryptsetup4
Merging cryptsetup-bin
Merging cryptsetup
Merging liblvm2cmd2.02
Merging dmeventd
Merging libreadline5
Merging dmsetup
Merging libudev1
Merging libdevmapper1.02.1
Merging libdevmapper-event1.02.1
Merging lvm2
Merging libtasn1-6
Merging libp11-kit0
Merging libnettle4
Merging libhogweed2
Merging libgmp10
Merging libgnutls-deb0-28
Merging ntfs-3g
Merging b43-fwcutter:
Merging zd1211-firmware:
Merging prism2-usb-firmware-installer:
Merging libertas-firmware:
Merging intel-microcode-amd64:
Merging intel-microcode:
Merging firmware-realtek:
Merging firmware-ralink:
Merging firmware-qlogic:
Merging firmware-netxen:
Merging firmware-myricom:
Merging firmware-linux-nonfree:
Merging firmware-linux-free:
Merging firmware-libertas:
Merging firmware-iwlwifi:
Merging firmware-ivtv:
Merging firmware-ipw2x00:
Merging firmware-intelwimax:
Merging firmware-brcm80211:
Merging firmware-bnx2x:
Merging firmware-bnx2:
Merging firmware-b43legacy-installer:
Merging firmware-b43-lpphy-installer:
Merging firmware-b43-installer:
Merging firmware-atheros:
Merging bluez-firmware:
Merging atmel-firmware:
md5sum: firmware-all.tar.gz.md5.txt: No such file or directory
Merging libpcsclite1
Merging libnl-genl-3-200
Merging libnl-3-200
Merging libdbus-1-3
Merging wpasupplicant
Merging libiw30
Merging wireless-tools
Merging wifi:
Merging less
Merging libpipeline1
Merging bsdutils
Merging bsdmainutils
Merging groff-base
Merging man-db
Merging importupdatecheck:
Merging powermgmt-base
Merging pm-utils
Merging psmisc
Merging tzdata
Merging Tiny Core custom start script for util-linux: util-linux.deb2sce
cat: /tmp/util-linux.deb2sce: No such file or directory
rm: cannot remove '/tmp/util-linux.deb2sce': No such file or directory
Merging util-linux
Merging laptop-mode-tools
Merging libusb-0.1-4
Merging gpgv
Merging gnupg
Merging tcpdump
Merging pdnsd
Merging libevent-2.0-5
Merging redsocks
Merging libpython-stdlib
Merging Tiny Core custom start script for python-minimal: python-minimal.deb2sce
cat: /tmp/python-minimal.deb2sce: No such file or directory
rm: cannot remove '/tmp/python-minimal.deb2sce': No such file or directory
^C
tc@box:~$
i stopped the importsce-process with strg-c.
thank you for your help.
-
The current md5sum of dCore.gz is
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
eea5fd24728c69141d92e90183e3bcd2 dCore.gz
-
netnomad - What are the owner/perms of your /tmp directory?
And what is the outcome of the below commands?
sudo rm /tmp/deb2sce.tar.gz
wget -O /tmp/deb2sce.tar.gz -cq http://repo.tinycorelinux.net/5.x/import/deb2sce.tar.gz
Also, you mentioned the md5sum of dCore.gz when you are apparently using dCore-jessie.gz.
-
i have revamped importsce and it's support scripts to be more robust in issuing an md5sum on each deb in storage rather than relying on a local md5sum file, does not seem to cost any noticable time but will be more resistant to potential breakage of local files. I will upload the results soon.
-
The current md5sum of dCore.gz is
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
eea5fd24728c69141d92e90183e3bcd2 dCore.gz
it's my fault, in the past i renamed dCore-jessie to dCore to make my config-files so multifunctional as possible.
i changed that now to avoid further misunderstandings...
sudo rm /tmp/deb2sce.tar.gz
wget -O /tmp/deb2sce.tar.gz -cq http://repo.tinycorelinux.net/5.x/import/deb2sce.tar.gz
i get no message, no output in the terminal, but the import-process fails :(
owner/perms of /tmp
drwxrwxrwt 10 tc staff 1020 Nov 16 09:06 tmp/
thank you for your help.
-
There seems to be an issue with the /tmp/deb2sce.tar.gz that gets downloaded once per import session. Yet there is a check for import to fail if it does not exist. I am trying to wrap my head around it. I will upload some more changes in the next few hours, then we can try again.
-
Uploaded another fix, this time to actually md5sum the existiing .tar.gz or .deb files if they exist rather than relying on an md5.txt file for more security with little cost in efficiency. Please test, and if anyone is having any deb2sce issue let me know as all is working on my setup.
-
hi jason,
sorry, that i have to give a disappointing reply.
i tried your last cut 3 times and the error message occured 3 times at the same packages:
...
Merging tzdata
ash: 1c34c5663fdaeea6f48f90d18228f398: unknown operand
Merging Tiny Core custom start script for util-linux: util-linux.deb2sce
cat: /tmp/util-linux.deb2sce: No such file or directory
rm: cannot remove '/tmp/util-linux.deb2sce': No such file or directory
Merging util-linux
...
Merging libpython-stdlib
Merging Tiny Core custom start script for python-minimal: python-minimal.deb2sce
cat: /tmp/python-minimal.deb2sce: No such file or directory
rm: cannot remove '/tmp/python-minimal.deb2sce': No such file or directory
Merging extra files for python-minimal: python-minimal-data.tar.gz
Merging python-minimal
...
Merging libpython2.7-minimal
Merging Tiny Core custom start script for python2.7-minimal: python2.7-minimal.deb2sce
cat: /tmp/python2.7-minimal.deb2sce: No such file or directory
rm: cannot remove '/tmp/python2.7-minimal.deb2sce': No such file or directory
Merging python2.7-minimal
Merging Tiny Core custom start script for python2.7: python2.7.deb2sce
cat: /tmp/python2.7.deb2sce: No such file or directory
rm: cannot remove '/tmp/python2.7.deb2sce': No such file or directory
Merging python2.7
Merging Tiny Core custom start script for python: python.deb2sce
cat: /tmp/python.deb2sce: No such file or directory
rm: cannot remove '/tmp/python.deb2sce': No such file or directory
Merging python
...
could it be that my usbstick-filesystem is overloaded and stops for a moment to save the transfered data?
i happens that my sytem seems to freeze, even the fluxbox-clock is not updated for up to 20s,
but after some time everything reactivates fine again.
i guess my stick is pretty fast, but after 100-200mb it needs some time to be able for further transfers.
thank you for your patience.
-
Ok, usb, should not make a difference but I will try via usb and see if I can reproduce.
-
netnomad - I see the same issue on USB. It should not be, but it is. I will fix it.
-
hi jason,
luckily we've met at the same point :)
thank you for your commitment.
-
Uploading what is hopefully the fix. What works for hard drives seems not always so for USB unfortunately. Thanks for testing.
-
Found some bugs again, uploaded all dCores with fix. Please download and test.
-
hi jason,
the last cut looks really good. :)
i successfully imported my base-package twice! :)
there are only some little issues that are probably easier to solve:
cat: md5sum: No such file or directory
Merging b43-fwcutter:
cat: md5sum: No such file or directory
Merging zd1211-firmware:
cat: md5sum: No such file or directory
Merging prism2-usb-firmware-installer:
cat: md5sum: No such file or directory
Merging libertas-firmware:
cat: md5sum: No such file or directory
Merging intel-microcode-amd64:
cat: md5sum: No such file or directory
Merging intel-microcode:
cat: md5sum: No such file or directory
Merging firmware-realtek:
cat: md5sum: No such file or directory
Merging firmware-ralink:
cat: md5sum: No such file or directory
Merging firmware-qlogic:
cat: md5sum: No such file or directory
Merging firmware-netxen:
cat: md5sum: No such file or directory
Merging firmware-myricom:
cat: md5sum: No such file or directory
Merging firmware-linux-nonfree:
cat: md5sum: No such file or directory
Merging firmware-linux-free:
cat: md5sum: No such file or directory
Merging firmware-libertas:
cat: md5sum: No such file or directory
Merging firmware-iwlwifi:
cat: md5sum: No such file or directory
Merging firmware-ivtv:
cat: md5sum: No such file or directory
Merging firmware-ipw2x00:
cat: md5sum: No such file or directory
Merging firmware-intelwimax:
cat: md5sum: No such file or directory
Merging firmware-brcm80211:
cat: md5sum: No such file or directory
Merging firmware-bnx2x:
cat: md5sum: No such file or directory
Merging firmware-bnx2:
cat: md5sum: No such file or directory
Merging firmware-b43legacy-installer:
cat: md5sum: No such file or directory
Merging firmware-b43-lpphy-installer:
cat: md5sum: No such file or directory
Merging firmware-b43-installer:
cat: md5sum: No such file or directory
Merging firmware-atheros:
cat: md5sum: No such file or directory
Merging bluez-firmware:
cat: md5sum: No such file or directory
...
Merging wireless-tools.
cat: md5sum: No such file or directory
...
Merging man-db.
cat: md5sum: No such file or directory
...
Merging fluxbox
cat: md5sum: No such file or directory
Merging wbar:
cat: md5sum: No such file or directory
Merging fltk-1.1.10:
cat: md5sum: No such file or directory
Merging Xtc:
cat: md5sum: No such file or directory
...
the rest seems to be really promising :)
thank you for all your efforts!
-
Ok, great. What you are seeing is cosmetic and I will upload the fix sometime today.
-
even "updatesce all" works now without problems :)
-
Uploaded what hopefully is the final fix for this set of changes.
-
hi jason,
i can confirm that the packaging with updatesce works flawless :)
the last cut
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz
de6dd77599c7f04477e4eecf2fda1541 dCore-jessie.gz
has new cosmetical error messages like:
...
Fetching updated firmware-all.tar.gz..
md5sum: can't open 'firmware-all.tar.gz': No such file or directory
md5sum: can't open 'firmware-all.tar.gz': No such file or directory
Merging firmware-all:
tar: firmware-all.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
...
Merging tzdata
ash: 1c34c5663fdaeea6f48f90d18228f398: unknown operand
Merging Tiny Core custom start script for util-linux: util-linux.deb2sce
...
Merging tar
ash: ccee8de1757937762d805539a708a4cd: unknown operand
Merging grep
...
Merging libdb5.3
ash: a69a6dfee236962dc0b94b5199aa11dc: unknown operand
Merging perl-modules
ash: 8b9049162e4b704f4b3f393766eb8d3a: unknown operand
Merging perl
...
Merging libssh2-1
ash: 21da1a3d46929b916271ddcdb818e6b3: unknown operand
Merging libslang2
...
Merging base-files
ash: 07a436e0a80dbdc7e0b71a446677460e: unknown operand
Merging bash
...
Merging sensible-utils
ash: 4dfe7f79e86e92f01f9173875ca8cf64: unknown operand
Merging Tiny Core custom start script for debianutils: debianutils.deb2sce
...
the result is still a good working package :)
perhaps the cut before had some advantages?
tc@box:~/.MNT/sdb1/live/dcore-current/boot$ md5sum dCore-jessie.gz
1d9b0bc6aa86aa2468c24d3c0caa4c75 dCore-jessie.gz
as you see in my message above there was no process-problem,
only few specific packages caused an error-message:
the firmware-files, wireless-tools, man-db, fluxbox, wbar, fltk, xtc.
i guess that the new cut causes more random process-errors?
at the end the packaging itself works flawless now and that's good :)
-
Ok, I will check it out when I get in tonight.
It has been a bumpy road with this latest set of changes, but the performance increase and updatesce is going to be worth it.
-
Yes, I can confirm that in the last cut (5d94df6684badea0fa8494ce9896f7af ub-dCore-trusty.gz)
tc@ubt-dC5x-ordjd:~$ updatesce jduLO1t
Existing dep file found and will be used.
Using the -s option.
Using the -n option.
ubuntu
#################### 100.0% 11.7 kBps DONE
verifying download...checksum matches OK
used 11321344 local, fetched 0
Using the repo http://us.archive.ubuntu.com/ubuntu trusty multiverse
Using the repo http://archive.ubuntu.com/ubuntu trusty universe
Using the repo http://archive.canonical.com/ precise partner
Using the repo http://archive.getdeb.net/ubuntu trusty-getdeb apps
Using the repo http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu trusty main
Using the repo http://us.archive.ubuntu.com/ubuntu ubuntu trusty main
Creating jduLO1t.sce from package list /mnt/sda1/ubtdc5/sce/jduLO1t.sce.lstchmod: invalid mode: 'tc:staff'
Try 'chmod --help' for more information.
Using Package Index: /etc/sysconfig/tcedir/ubuntu_trusty_main_i386_Packages
Using ubuntu Mirror: http://us.archive.ubuntu.com/ubuntu
jduLO1t is from your own custom package list:
Gathering dependency info..
The below SCE's in your SCE directory will be used as
to provide dependencies for jduLO1t.sce.
jdudesk1t
Determining HD and RAM space needed..
0.00 MB of downloads required.
648.52 MB needed for unpacking archives.
246.00 MB of compressed archives will be used.
1140.52 MB is a good estimate of /mnt/sda1/ubtdc5 space needed, 13707.20 MB is available.
Merging libreoffice4.1-es-langpack:
Merging ure
Merging uno-libs3
Merging libmhash2
Merging libgmp10
Merging librasqal3
Merging libyajl2
Merging libxslt1.1
Merging libraptor2-0
Merging librdf0
Merging libneon27-gnutls
Merging libmythes-1.2-0
Merging libhyphen0
Merging libhunspell-1.3-0
ash: f6781b7b808b6887c6f8db3818c43ac0: unknown operand
Merging libdb5.1
Merging libsystemd-login0
Merging libapparmor1
Merging Tiny Core custom start script for dbus: dbus.deb2sce
Merging dbus
Merging dbus-x11
Merging psmisc
Merging gconf2
Merging gconf2-common
Merging libgconf-2-4
Merging gconf-service-backend
Merging gconf-service
Merging fonts-opensymbol
Merging libatk-wrapper-java
Merging libatk-wrapper-java-jni
Merging libxtst6
Merging openjdk-7-jre
Merging libnss3-1d
Merging java-common
Merging tzdata-java
Merging libnss3-nssdb
ash: 98d239c9f0e9416a21c415cab791edcf: unknown operand
Merging libnspr4-0d
Merging libnspr4
Merging libnss3
Merging ca-certificates-java
Merging openjdk-7-jre-headless
Merging default-jre-headless
Merging default-jre
Merging libreoffice4.1:
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on /etc/sysconfig/tcedir/sce/update/jduLO1t.sce, block size 4096.
[=========================================================\] 167046/167046 100%
Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 4096
compressed data, compressed metadata, compressed fragments, no xattrs
duplicates are removed
Filesystem size 298060.18 Kbytes (291.07 Mbytes)
45.91% of uncompressed filesystem size (649236.93 Kbytes)
Inode table size 397329 bytes (388.02 Kbytes)
42.14% of uncompressed inode table size (942839 bytes)
Directory table size 80686 bytes (78.79 Kbytes)
38.23% of uncompressed directory table size (211042 bytes)
Number of duplicate files found 1388
Number of inodes 9068
Number of files 7916
Number of fragments 1362
Number of symbolic links 129
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 1023
Number of ids (unique uids + gids) 2
Number of uids 1
root (0)
Number of gids 2
root (0)
staff (50)
Done.
tc@ubt-dC5x-ordjd:~$
-
Ok, updated to 5.x/x86/release_candidates with what I hope is the conclusion of the fixes of this latest set of improvements. All 4 x86 dCore ports updated, I updated the dCore Wheezy iso as I have some confidence in this fix.
-
hi jason,
hopefully you are not offended by my post.
the last cut has remarkable improvements:
all firmware-files, virtual or non-existing files are handled fine,
but some packages still cause this "unknown operand"-error message.
i guess that this happens always wtih the same package, so it's no random mistake:
...
Merging tzdata
ash: 1c34c5663fdaeea6f48f90d18228f398: unknown operand
Merging Tiny Core custom start script for util-linux: util-linux.deb2sce
...
Merging tar
ash: ccee8de1757937762d805539a708a4cd: unknown operand
Merging grep
...
Merging libdb5.3
ash: a69a6dfee236962dc0b94b5199aa11dc: unknown operand
Merging perl-modules
ash: 8b9049162e4b704f4b3f393766eb8d3a: unknown operand
Merging perl
...
Merging libssh2-1
ash: 21da1a3d46929b916271ddcdb818e6b3: unknown operand
Merging libslang2
...
Merging base-files
ash: 07a436e0a80dbdc7e0b71a446677460e: unknown operand
Merging bash
...
Merging sensible-utils
ash: 4dfe7f79e86e92f01f9173875ca8cf64: unknown operand
Merging Tiny Core custom start script for debianutils: debianutils.deb2sce
...
thank you for your patience and all your efforts.
####
i can confirm that always the same packages are affected, i tested it 3 times.
####
-
Ok, please list what you are importing as I can't get any of those to issue an error message.
-
hi jason.
these are my main 3 lists, especially the first one, 000-base-jessie.sce.lst, causes the error messages i mentioned above.
000-base-jessie.sce.lst:
##############
console-setup
console-data
bash
mc
ssh
rsync
screen
grep
tar
zip
unzip
gzip
bzip2
xz-utils
p7zip-full
nmap
iptables
fail2ban
redsocks
pdnsd
tcpdump
gnupg
laptop-mode-tools
pm-utils
importupdatecheck
man-db
wifi
wpasupplicant
firmware-all
ntfs-3g
lvm2
cryptsetup
libsmartcols1
100-desktop-jessie.sce.lst:
################
xorg-all
Xprogs
wbar
fluxbox
iceweasel
icedove
evince
jpilot
xvnc4viewer
200-multimedia.sce.lst:
##############
alsa-base
alsa-utils
alsamixergui
cdparanoia
vlc
faad
lame
cups
cups-driver-gutenprint
hplip
avahi-daemon
gimp
xsane
minitube
pulseaudio
pavucontrol
gnucash
gthumb
gnome-calculator
-
hi jason,
the last cut broke my system.
the importsce does merge many packages under ../import/debs (i guess that wasn't your purpose).
so they are not merged in the path ../import/<package-name>.
the result are small, broken packages that miss some packages of the filelist.
i guess that the files merged under ../import/debs are not included in the merged package.
:(
-
Ok, I will check into it tonight when I get in (8pm EST).
-
Netnomad, I don't see the untarring of packages under import/debs, but I did find a few bugs dealing with the md5sum function. Uplolading a new copy, please test, and also please keep a good copy of a working dCore-jessie.gz and your sce's before testing just to be sure. Thanks.
-
I see one more bug whe dealing with USB tce directory. Bear with me, I have about 2 hours available each night to deal with this, I want to get it right so allow me a few days to try and test and I will soon upload a good working copy of dCore.
-
hi jason,
i could help me with backups :)
the last cut breaks for the reason that firmware-all.tar.gz seems to have no md5sum stored at the server?
...
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum failed for firmware-all.tar.gz, exiting..
tc@box:~$
thank you for all your contributions.
-
Thanks, I added a check for that in.
I am almost there, I will polish and test it tonight and use it a day or so to make sure things are ok, I should upload by sometime Thurs.
-
Much progress in the migration from tinycorelinux/5.x to tinycorelinux/dCore. That part should be not noticable to the user.
Also, finishing testing of the importsce routine as it relates to the recent changes and improvements. Reliability and speed improvements have been worked in.
Plan is to release tomorrow (Thurs) and also create the stable and testing versions of all the dCore x86 ports.
-
Ok, fix uploaded in the release candidates area.
-
Hi
importsce reports wrong file system space:
Determining HD and RAM space needed..
0.00 MB of downloads required.
117.10 MB needed for unpacking archives.
43.74 MB of compressed archives will be used.
204.59 MB is a good estimate of /mnt/sda1/tce space needed, 0.00 MB is available.
WARNING: You do not have enough /mnt/sda1/tce space, you should not proceed.
The above errors have occured. Do you wish to continue
while
jls@portatile:/mnt/sda1/tce/sce$ df /mnt/sda1
Sys. fich. Taille Util. Dispo Uti% Monté sur
/dev/sda1 8,6G 7,8G 767M 92% /mnt/sda1
-
What package are you importing?
And is it a file list? if so, what are the contents of the list?
-
I'm importing base which contains:
base-locale
alsa-modules-3.8.13-tinycore
alsa-utils
graphics-3.8.13-tinycore
i2c-3.8.13-tinycore
Xprogs
vim
util-linux-locales
xorg-trident
wireless-tools
wireless-3.8.13-tinycore
After the update I've rebooted and did another updatesce to the same package and it was re-imported, even no package changes
-
Ok, I can't reproduce any error with that same set of packages and naming the file "base".
I will try with a usb boot tonight when I get in, but if it imported fine after a reboot it may have been a fluke.
-
It was suggested to me by JLS that updatesce only update an sce if there are updates available, and that makes sense though it was going to be a big code change which is why I left it for after the last changes were stabilized. So far here are the concepts I have working on my box. Updatesce has a -c option that will simply check if an sce has updates available and state if it does or not, placing the details in a file in /tmp if one wants specifics.
Below will check if iceweasel has updates available and not update even if there are:
updatesce -c iceweasel
Below will update iceweasel if there are updates available:
updatesce iceweasel
Below will update any of the existing sces in the sce directory:
updatesce all
Below will simply let you know what has updates available
updatesce -c all
Below will bring up a menu to either just check or check and update a selection if updates are available:
updatesce -c
updatesce
Also, importsce has a new option "-u" or "use existing debinx" that will not fetch new Packages/debinx files from the main or extra repos. A big time saver when importing several things over a short time period not having to wait on fetched Packages files. Updatesce by default fetches new Packages/debinx files since the purpose is to check for new updates. This may also help with stability across multiple sces as the same debs are used though updates startup scripts and data files are fetched each import.
Extra repo debinx files will now be stored in the /etc/sysconfig/tcedir directory as to not have to be imported each time if one chooses not to. If a deb is no longer available, importsce stops and lets you know so you can either choose from available debs or simply choose to reimport with new debinx data.
Also, importupdatecheck is no longer a standalone utility but rather called by updatesce and will be in base. "updatesce -c" is the new importupdatecheck once the changes are uploaded to a new release candidate cut.
Let me know if this sounds like a plan.
-
Hi Jason W
Below will update any of the existing sces in the sce directory:
updatesce all
Below will simply let you know what has updates available
updatesce -c all
Just wondering, but since you are using all as a keyword, wouldn't it make sense to precede it with a - or -- ? What happens if
you encounter a package called all ?
-
Good point, parsing the command line for --all. It would have to be double dash "--" and separate from the other options since the GETOPTS options can only be one letter as far as I know. Either way, yeah, we will make it something other than a non-dashed word.
Also, I think the "importsce -u" should perhaps be to update the debinx while "importsce -p" would preserve existing, seems to sound more logical and the -p option is not taken yet.
Please anyone bring up any ideas or changes as the best time for that is now and I will hold off a few days after I make sure things are working right before uploading a release candidate as I am sure there will be ways to streamline or adjust things.
-
Everything seems to be in place and working as expected, I will test some more tonight and hopefully upload the results.
-
hi jason,
i'm looking forward...
keep on hacking :)
-
hi jason,
did you notice that after a fresh update of a package-list and a reboot with loading the new package-list.sce,
afterwards the tool importupdatecheck still reports that these fresh downloaded packages would need an update?
this happens also after a reboot, that means although all packages in the new sce are up-to-date,
importupdatecheck still thinks that these packages need an update.
thank you for your help.
-
Ok, there are lots and lots of changes in the new updatesce/importupdatecheck I hope to upload soon. The existing importupdatecheck extension is surely broken by now, I would wait to do any testing until the new stuff is uploaded.
-
Ok, I am satisfied with my own testing and have uploaded a new cut to each of the dCore x86 ports in their release candidate section. Lots of changes, I will try to summarize them here. The command you use is updatesce. Importupdatecheck has been removed as an extension and the old extension can't be installed alongside the new changes or it will cause problems. Below are the command options.
updatesce - Will open up a select menu of existing SCEs to choose from. You can choose one, several, or up to all.
updatesce -c - will do as above but is in the "check only" mode and will not update the SCE but let you know if updates are available. Can be combined with the other options.
updatesce -a - will update all existing SCEs. Can be combined with the other options, combining with -c will just check all of them and -n will prevent having to answer any questions.
updatesce -n - Non-interactive mode. Only if you don't enter either an SCE name or the "-a" option will a select menu appear. Can be combined with the other options. Spits out the results to /tmp/updateavailable rather than asking you do you want to view that file.
As with importsce, installing GNU grep beforehand very much enhances performance.
Also, importsce has 2 new options.
importsce -u - that will fetch a new debinx for the main Debian one and any in /opt/debextra. This is the default and will trump the "-p" option whether it is listed in /etc/sysconfig/sceconfig or the command line. UPDATEDEBINXMODE=TRUE is the entry in /etc/sysconfig/sceconfig.
importsce -p - that will use the existing debinx files, useful if you are importing several packages overa short time and don't need to sync new debinx files. This option is overridden by either an entry in /etc/sysconfig/sceconfig or the command line option of "-u". The relevant entry in /etc/sysconfig/sceconfig is PRESERVEDEBINXMODE=TRUE.
-
hi jason,
very good first impression, all works as expected!
i keep on testing :)
-
I am continuing to test the new functions with the different SCE types here - made from list, has a dep file, etc. Hopefully this one is a keeper and can be moved to release soon without much more ado.
-
Uploaded for the x86 dCore ports in release testing a very minor cosmetic change to the /tmp/updateavailable file that gets created.
-
Found a major bug in regards to the fetching and merging of the data.tar.gz files, all 4 x86 dCore ports. Please re-download and test.
-
Hi Jason,
Is possible to rename the dCore release candidates to ub-dCore-trusty-rc.gz for example? So is easily to recognize in the boot file.
And, Is possible to make a new entrance in the Download page for dCore x86 in the release and release candidates or in other ports? (in release is only the 5.x version, in the release candidates only the 6.x version, and in others ports are the x86 Pure 64, dCore Arm V7hf and Raspberry Pi)
Thanks.
-
To rename the release candidate files as -rc.gz would mean I would have to rename each of the four dCore files and give them new md5sums whenever I copied to release. Since the user is dealing with one file, it is much easier to download to /home/tc/ub-dCore-trusty.gz and move it with "mv /home/tc/ub-dCore-trusty.gz /mnt/sda2/boot/ub-dCore-trusty-rc.gz". That would be easier than the burden being placed on me for the four files all of the time. The dCore files can be renamed by the user at any time to whatever name they want to as long as it is reflected in the boot loader of course.
After moving the dCore location from tinycorelinux/5.x/ to tinycorelinux/dCore I had proposed an example Downloads page to the team pending approval that added dCore to the Downloads and Ports page. We may just need to be happy accessing dCore through this forum section.
Oh, and I am getting ready to upload a fix that prevents /usr/share/doc and /usr/share/man from getting deleted prior to the squashing of the final package directory, some packages like pysolfc have /usr/share/doc files that are in thier -data.tar.gz.
-
hi jason,
i agree to your point of view.
i guess that there exist so many opinions as colors in the rainbow ;)
for me i prefered to rename the dCore-jessie.gz-file to dCore.gz for compatibility-reasons
(easier copying of various bootloader-alternatives and so on),
but after i caused some misunderstandings in the forum with quoting my renamed file,
i got back to use the standard-filenames.
thank you for your contributions, keep on hacking.
-
Hi Jason,
I understand too your point of view, and agree your efforts.
Maybe I'm going to rename by myself the release candidate, so I can prove them in my normal workspace.
-
Thanks Onyarian, renaming on your part will save me a lot of time.
I have uploaded another cut to release_candidates, all dCore x86 ports, please download and test.
One fix deals with since we are storing extra Packages files in the form of /etc/sysconfig/tcedir/debinx.* files, if the relevant entries in /opt/debextra are not there, then those debinx.* files are deleted to avoid error during import.
-
Uploaded a new fix in this series for the x86 dCore ports, this one fixing the addition of imported sce's to sceboot.lst when the -b option was not called nor was it specified in /etc/sysconfig/sceconfig. It was a typo in importsce.
-
I am taking it by the quiet that no news is good news. Lots of changes, so I will give it about a week and copy the release candidates over to release..
-
hi jason,
heavy testing confirmed the last cut as a stable system for my setup :)
i'm very happy with it, i'm mainly wishless, only suspend-to-ram remains a long-term wish...
keep on hacking.
-
Ok, we are due a kernel update, maybe that will help in the suspend to ram thing.
I also plan to get CDE working so SCEs in the /cde directory will load on boot. The initial code porting is missing something.
-
My proves in my normal workspace are also OK.
Checking with -c founding there is an update (cups) in the big .sce and then without -c to run this update, no errors.
Thanks
-
It sounds like this would make at least as stable of a release as the last one.
I will copy the files over and announce it later today.
-
Uploaded ub-dCore-utopic, working fine here and posting from it with Firefox. Since as of Jessie and Trusty we have been able to work around that abomination known as systemd, the update was simple, Trusty and Utopic have pretty much the same file names in base so copying files to the new base .gz was simple.
I found a couple of bugs in regards to the "importsce -l" option, fixed now and uploaded to both the release and release candidates area for all dCore x86 ports.