SliTaz Forum
You are not logged in.
Starting with the forced update of tazpkg works without any problems.
Any change that is not backward compatible causes problems.
Perhaps the package dependencies need to prioritize the update of tazpkg, although I don't think this is possible on previous versions.
Offline
Yes, it's my fault, stupid don't think when i said in other thread about HDS for Virtualbox to use packages-ng, what's uo if try to install package without update tazpkg first.
Good catch, don't possible to do on previous installation, but i can check to add function on tazpkg install modules to check if tazpkg need to do upgrade first but that implied run each time that package install 
.
I check history of tazpkg repository to see how switch from fs.cpio.gz > fs.cpio.lzma managed.
tazpkg updated to use lzma on recompress feature and next commit it to use fs.cpio.lzma instead fs.cpio.gz.
Don't really understand how migration managed
https://hg.slitaz.org/tazpkg/diff/14cd3fec0297/tazpkg (rev 297)
https://hg.slitaz.org/tazpkg/diff/2affdd0c18e2/tazpkg (rev 298)
Offline
Given the consequences directly, the first thing that comes to mind is to add a check script to the e2fsck phase that checks the existence of all files contained in the files.list of /var/lib/tazpkg/installed. In case of error, force the update of tazpkg and then the forced installation of all those in error (missing files, not md5sum).
I believe this script would be simple and lightweight to insert into the base file.
It would not weigh on the installation of all packages, and the operation would be initiated once during the boot checkfs.
Although the best solution remains to force the tazpkg update before the others.
Offline
I check to do script, he take more than 20s to action
break in for loop it's to not parse all files, if we found once is enough
#!/bin/sh
# We need check for each package if files exist
for pkg in $(ls /var/lib/tazpkg/installed);
do
for file in $(cat /var/lib/tazpkg/installed/$pkg/files.list);
do
# Exclude dotnew files
if ! echo "$file" | grep -q ".new" ; then
if [ ! -e "$file" ]; then
echo $pkg >> /tmp/pkgs_wrong_consistency.list
break
fi
fi
done
done
if [ -s /tmp/pkgs_wrong_consistency.list ]; then
# Upgrade tazpkg
tazpkg -gi tazpkg --forced
# Reinstall packages corrupted
for pkg in $(cat /tmp/pkgs_wrong_consistency.list); do
tazpkg -gi $pkg --forced
done
fi
Unfortunately i create situation that can be break system, best way for this feature it's to introduce it on new version.
If i check CHANGELOG of Slackware, when they switch to .txz from .tgz, it's introduce it on 13.0, and first step on UPGRADE.TXT it's to upgrade pkgtools.
At this time i need to more doing tests and various users cases to ensure no breaking change.
Offline
Hi,
I'm doing test for upgrade 32 bits version on my dell x300 with mirror point to packages-ng (new compress tar.xz) in livemode, for remind it's Pentium M (single core 1.2Ghz), 1Go memory.
Take 12m30s for doing upgrade (417 packages upgraded), i don't include fetch time.
Concerning consistency of packages, think script at boot that check if tazpkg need update and create lock file that block install of any package (exception in case of tazpkg of course).
Offline
Hi Shann,
Yes, I tried it too and found that it's too long a process to include it by default. However, it could work well as a package to install on demand, and start manually if there are doubts about the system. Similar to antivirus programs that perform a scan.
Offline
I implement same feature i doing for tazpkg upgrade.
Create /etc/init.d/check_tazpkg_up.sh goal to check if tazpkg need to be update and create /var/lock/tazpkgup.lock
On [c]/usr/libexec/tazpkg/install[/c], i add if condition to check if lock file exist before install package
[attachment=53504,3764]
Offline
Another obstacle for tazpkg:
I wanted to install scanbd, but it's not in the repository. I decide to compile it. It requires libconfuse. That's missing too. I try to compile it from source, but it fails. I try to convert a Debian package, but conversion is not supported.
root@slitaz:/home/tux# tazpkg convert libconfuse-dev_3.3-4_amd64.deb
Incorrect target: amd64 (i386 was expected)
root@slitaz:/home/tux# tazpkg --version
SliTaz package manager - Version: 944
================================================================================
Packages installed: 387
Files installed: 20994
Blocked packages: 0
Upgradeable packages: 0
Online repository: Main
Last update Yesterday at 11:51.
Database time: 11/20/2025 10:08
Synchronized packages: 1790
================================================================================
edit: I managed to compile the libconfuse and scanbd packages from source. The only thing missing is support for tazpkg convert on 64-bit.
Offline
Hi Gibor,
Infact, seem tazpkg convert don't have stuff to know x86_64 arch
I adjust convert_deb() function to add amd64 on target supported [c]i386|all)[/c] to [c]i386|amd64|all[/c]
I doing test for libconfuse-dev, it's convert to libconfuse
[attachment=53506,3765]
Need to review convert module to be full compliance with x86_64 target
Offline
I don't know how many people are helping you develop the system. Knowing how complex it is to manage, I have no problem with that. I just pointed out this lack of a package manager. After all, the 64-bit version is the biggest news on SliTaz in at least 10 years ;-)
Thanks Shann, and thanks to everyone for all your hard work.
Offline
I don't know how many people are helping you develop the system. Knowing how complex it is to manage, I have no problem with that. I just pointed out this lack of a package manager. After all, the 64-bit version is the biggest news on SliTaz in at least 10 years ;-)
Thanks Shann, and thanks to everyone for all your hard work.
Offline
Hi Gibor,
Thanks very much, and thanks for you report and tests.
For "current/6.0" version, i'm work on it myself but with help of alanyih, Ceel and other members that help or found fix when i'm blocked.
Generally, version couldn't be exist without previous stuff begin by Alanyih and Aleksej specially stuff over x86_64 target, many thanks and congrats them for they work
I rework/fix init script to support softraid / virtio, check for opportunity to use SliTaz as baremetal host for infrastructure instead proxmox.
Test doing on qemu with two disk, we can boot with softraid (need initrd of course), same for vm with full virtio support 
.
I already doing test with rent hourly server on Scaleway provider, EM-L101X-SATA (behind it's Dell PowerEdge R320), "6.0" version boot successfully (in live mode) and recognized all devices (cpu, netcard tg3/bnx3, sata disk).
Offline
Hi shann,
That’s really kind of you to include me in the development of Current but my contribution to the project is insignificant.
Thanks again for all your job and your great support to fix problems.
Offline
Hi Ceel,
Thanks
Below test i doing with hourly rent server before rent with commitment.
If i would like store all vms, need more cpu that previous test i do with EM-L101X (4c/8t).
tank / pangolin / mirror combined 10 vCPUs, 25Gb of ram, and lot of disk space (150Go + 100Go, for tank i clean my wok and next wok, keep chroot and packages, we gain ~320Gb free, only 432Go used now)
AMD Ryzen 6c/12t (3.6Ghz), 32Go DDR4, 2 nvme 1.02To.
Boot on SliTaz 6.0 x86_64 in efi mode.
I create raid1 with mdadm on nvme disks, format ext4 and mount it on /home, and doing some tests :
- cook gcc, take 6mns
- doing test to perf disk
- create qemu vm with disk on /home (in raid device, to test perf)
Connect on spice protocol with ssh tunnel, and doing again disk test, seem good (average 1Gb/s).
Of course only one vm and nothing other process run.
Edit: for spice field "VMs Infos" it's wip stuff i'm doing for migration plan.
[attachment=53518,3766]
Disk perf on host
root@slitaz:/home/slitaz/wok# dd if=/dev/zero of=/mnt/tempfile bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 0.297464 seconds, 3.4GB/s
root@slitaz:/home/slitaz/wok# dd if=/dev/zero of=/mnt/tempfile bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 0.361886 seconds, 2.8GB/s
root@slitaz:/home/slitaz/wok# echo 3 > /proc/sys/vm/drop_caches
root@slitaz:/home/slitaz/wok# dd if=/dev/zero of=/mnt/tempfile bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 0.370066 seconds, 2.7GB/s
root@slitaz:/home/slitaz/wok# dd if=/dev/zero of=/mnt/tempfile bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.0GB) copied, 0.368664 seconds, 2.7GB/s
root@slitaz:/home/slitaz/wok# dd if=/mnt/tempfile of=/dev/null bs=7M count=1024
146+1 records in
146+1 records out
1073741824 bytes (1.0GB) copied, 0.142907 seconds, 7.0GB/s
root@slitaz:/home/slitaz/wok# dd if=/mnt/tempfile of=/dev/null bs=7M count=1024
146+1 records in
146+1 records out
1073741824 bytes (1.0GB) copied, 0.121600 seconds, 8.2GB/s
Offline
Hi,
Improve test i doing real install on test instance, it's work well.
Due of boot efi, need to create /boot/efi partition no raid, but / and /home as under softraid with mdadm.
I order server on AMS and PAR region, plan to install end of week-end if possible.
Monthly cost reduced (~twice), and main goal i wish it's preserved, capacity to have failover.
Due of disk space, need to rework backup process.
Migration need to be plan for middle January, commitment ending January 12th / 20th.
[attachment=53522,3767]
Offline
I understand that this is an almost extreme case, but in case of doubt, reinstalling a package should restore the normal state established by that package.
I would therefore like to point out that the manager (tazpkg-944) does not guarantee the integrity of the package, because it does not overwrite any existing files, but renames those in the package to *.new, rendering them unusable.
total 328
-rw-r--r-- 1 tux tux 25 Dec 1 10:26 abaton.conf
-rw-r--r-- 1 tux tux 13 Dec 1 10:26 agfafocus.conf
-rw-r--r-- 1 tux tux 24 Dec 1 10:26 apple.conf
-rw-r--r-- 1 tux tux 25 Dec 1 10:26 artec.conf
-rw-r--r-- 1 tux tux 4157 Dec 1 10:26 artec_eplus48u.conf
-rw-r--r-- 1 tux tux 547 Dec 1 10:26 avision.conf
-rw-r--r-- 1 tux tux 29 Dec 1 10:26 bh.conf
-rw-r--r-- 1 tux tux 193 Dec 1 10:26 canon630u.conf
-rw-r--r-- 1 tux tux 26 Dec 1 10:26 canon.conf
-rw-r--r-- 1 tux tux 4110 Dec 1 10:26 canon_dr.conf
-rw-r--r-- 1 tux tux 258 Dec 1 10:26 canon_lide70.conf
-rw-r--r-- 1 tux tux 552 Dec 1 10:26 cardscan.conf
-rw-r--r-- 1 tux tux 753 Dec 1 10:26 coolscan2.conf
-rw-r--r-- 1 tux tux 753 Dec 1 10:26 coolscan3.conf
-rw-r--r-- 1 tux tux 34 Dec 1 10:26 coolscan.conf
-rw-r--r-- 1 root root 983 Oct 21 10:58 dc210.conf
-rw-r--r-- 1 root root 983 Oct 21 10:58 dc240.conf
-rw-r--r-- 1 tux tux 703 Dec 1 10:26 dc25.conf
-rw-r--r-- 1 root root 490 Oct 21 10:58 dell1600n_net.conf
-rw-r--r-- 1 root root 447 Dec 1 10:26 dll.conf
drwxr-xr-x 2 tux tux 40 Dec 1 10:26 dll.d
drwxr-xr-x 2 root root 40 Oct 21 10:58 dll.d.new
-rw-r--r-- 1 tux tux 12 Dec 1 10:26 dmc.conf
-rw-r--r-- 1 tux tux 2734 Dec 1 10:26 epjitsu.conf
-rw-r--r-- 1 tux tux 374 Dec 1 10:26 epson2.conf
-rw-r--r-- 1 tux tux 792 Dec 1 10:26 epson.conf
-rw-r--r-- 1 tux tux 3858 Dec 1 10:26 fujitsu.conf
-rw-r--r-- 1 tux tux 2597 Dec 1 10:26 genesys.conf
-rw-r--r-- 1 tux tux 7951 Dec 1 10:26 gt68xx.conf
-rw-r--r-- 1 tux tux 395 Dec 1 10:26 hp3900.conf
-rw-r--r-- 1 tux tux 76 Dec 1 10:26 hp4200.conf
-rw-r--r-- 1 tux tux 238 Dec 1 10:26 hp5400.conf
-rw-r--r-- 1 tux tux 497 Dec 1 10:26 hp.conf
-rw-r--r-- 1 tux tux 24 Dec 1 10:26 hs2p.conf
-rw-r--r-- 1 tux tux 38 Dec 1 10:26 ibm.conf
-rw-r--r-- 1 tux tux 2597 Dec 1 10:26 kodakaio.conf
-rw-r--r-- 1 tux tux 367 Dec 1 10:26 kodak.conf
-rw-r--r-- 1 tux tux 39 Dec 1 10:26 kvs1025.conf
-rw-r--r-- 1 tux tux 112 Dec 1 10:26 leo.conf
-rw-r--r-- 1 tux tux 119 Dec 1 10:26 lexmark.conf
-rw-r--r-- 1 tux tux 33 Dec 1 10:26 lexmark_x2600.conf
-rw-r--r-- 1 tux tux 187 Dec 1 10:26 ma1509.conf
-rw-r--r-- 1 tux tux 1253 Dec 1 10:26 magicolor.conf
-rw-r--r-- 1 tux tux 665 Dec 1 10:26 matsushita.conf
-rw-r--r-- 1 tux tux 279 Dec 1 10:26 microtek2.conf
-rw-r--r-- 1 tux tux 268 Dec 1 10:26 microtek.conf
-rw-r--r-- 1 tux tux 2118 Dec 1 10:26 mustek.conf
-rw-r--r-- 1 tux tux 808 Dec 1 10:26 mustek_usb.conf
-rw-r--r-- 1 tux tux 13 Dec 1 10:26 nec.conf
-rw-r--r-- 1 root root 593 Dec 1 10:26 net.conf
-rw-r--r-- 1 tux tux 365 Dec 1 10:26 p5.conf
-rw-r--r-- 1 tux tux 75 Dec 1 10:26 pie.conf
-rw-r--r-- 1 tux tux 669 Dec 1 10:26 pieusb.conf
-rw-r--r-- 1 tux tux 1246 Nov 28 09:08 pixma.conf
-rw-r--r-- 1 tux tux 4140 Dec 1 10:26 plustek.conf
-rw-r--r-- 1 tux tux 942 Dec 1 10:26 plustek_pp.conf
-rw-r--r-- 1 tux tux 391 Dec 1 10:26 qcam.conf
-rw-r--r-- 1 tux tux 29 Dec 1 10:26 ricoh.conf
-rw-r--r-- 1 tux tux 183 Dec 1 10:26 rts8891.conf
-rw-r--r-- 1 tux tux 13 Dec 1 10:26 s9036.conf
-rw-r--r-- 1 root root 1116 Dec 1 10:26 saned.conf
-rw-r--r-- 1 tux tux 48 Dec 1 10:26 sceptre.conf
-rw-r--r-- 1 tux tux 1458 Dec 1 10:26 sharp.conf
-rw-r--r-- 1 root root 69 Nov 19 19:56 sm3800.conf
-rw-r--r-- 1 tux tux 115 Dec 1 10:26 sm3840.conf
-rw-r--r-- 1 tux tux 2239 Dec 1 10:26 snapscan.conf
-rw-r--r-- 1 tux tux 10 Dec 1 10:26 sp15c.conf
-rw-r--r-- 1 tux tux 2225 Dec 1 10:26 st400.conf
-rw-r--r-- 1 tux tux 178 Dec 1 10:26 stv680.conf
-rw-r--r-- 1 tux tux 27 Dec 1 10:26 tamarack.conf
-rw-r--r-- 1 tux tux 355 Dec 1 10:26 teco1.conf
-rw-r--r-- 1 tux tux 634 Dec 1 10:26 teco2.conf
-rw-r--r-- 1 tux tux 217 Dec 1 10:26 teco3.conf
-rw-r--r-- 1 tux tux 1807 Dec 1 10:26 test.conf
-rw-r--r-- 1 tux tux 1494 Dec 1 10:26 u12.conf
-rw-r--r-- 1 tux tux 386 Dec 1 10:26 umax1220u.conf
-rw-r--r-- 1 tux tux 3083 Dec 1 10:26 umax.conf
-rw-r--r-- 1 tux tux 1681 Dec 1 10:26 umax_pp.conf
-rw-r--r-- 1 tux tux 4295 Dec 1 10:26 xerox_mfp.conf
----------------------------------------------------------
tazpkg -gi sane-backends
----------------------------------------------------------
total 576
-rw-r--r-- 1 tux tux 25 Dec 1 10:26 abaton.conf
-rw-r--r-- 1 tux tux 13 Dec 1 10:26 agfafocus.conf
-rw-r--r-- 1 tux tux 24 Dec 1 10:26 apple.conf
-rw-r--r-- 1 tux tux 25 Dec 1 10:26 artec.conf
-rw-r--r-- 1 tux tux 4157 Dec 1 10:26 artec_eplus48u.conf
-rw-r--r-- 1 tux tux 547 Dec 1 10:26 avision.conf
-rw-r--r-- 1 tux tux 29 Dec 1 10:26 bh.conf
-rw-r--r-- 1 tux tux 193 Dec 1 10:26 canon630u.conf
-rw-r--r-- 1 tux tux 26 Dec 1 10:26 canon.conf
-rw-r--r-- 1 tux tux 4110 Dec 1 10:26 canon_dr.conf
-rw-r--r-- 1 root root 3961 Oct 21 10:58 canon_dr.conf.new
-rw-r--r-- 1 tux tux 258 Dec 1 10:26 canon_lide70.conf
-rw-r--r-- 1 tux tux 552 Dec 1 10:26 cardscan.conf
-rw-r--r-- 1 tux tux 753 Dec 1 10:26 coolscan2.conf
-rw-r--r-- 1 tux tux 753 Dec 1 10:26 coolscan3.conf
-rw-r--r-- 1 tux tux 34 Dec 1 10:26 coolscan.conf
-rw-r--r-- 1 root root 983 Oct 21 10:58 dc210.conf
-rw-r--r-- 1 root root 983 Oct 21 10:58 dc240.conf
-rw-r--r-- 1 tux tux 703 Dec 1 10:26 dc25.conf
-rw-r--r-- 1 root root 490 Oct 21 10:58 dell1600n_net.conf
-rw-r--r-- 1 root root 447 Dec 1 10:26 dll.conf
-rw-r--r-- 1 root root 1134 Oct 21 10:58 dll.conf.new
drwxr-xr-x 2 tux tux 40 Dec 1 10:26 dll.d
drwxr-xr-x 2 root root 40 Oct 21 10:58 dll.d.new
-rw-r--r-- 1 tux tux 12 Dec 1 10:26 dmc.conf
-rw-r--r-- 1 root root 12 Oct 21 10:58 dmc.conf.new
-rw-r--r-- 1 tux tux 2734 Dec 1 10:26 epjitsu.conf
-rw-r--r-- 1 root root 2734 Oct 21 10:58 epjitsu.conf.new
-rw-r--r-- 1 tux tux 374 Dec 1 10:26 epson2.conf
-rw-r--r-- 1 root root 374 Oct 21 10:58 epson2.conf.new
-rw-r--r-- 1 tux tux 792 Dec 1 10:26 epson.conf
-rw-r--r-- 1 root root 792 Oct 21 10:58 epson.conf.new
-rw-r--r-- 1 root root 293 Oct 21 10:58 epsonds.conf.new
-rw-r--r-- 1 tux tux 3858 Dec 1 10:26 fujitsu.conf
-rw-r--r-- 1 root root 3355 Oct 21 10:58 fujitsu.conf.new
-rw-r--r-- 1 tux tux 2597 Dec 1 10:26 genesys.conf
-rw-r--r-- 1 root root 2416 Oct 21 10:58 genesys.conf.new
-rw-r--r-- 1 root root 1140 Oct 21 10:58 gphoto2.conf.new
-rw-r--r-- 1 tux tux 7951 Dec 1 10:26 gt68xx.conf
-rw-r--r-- 1 root root 7951 Oct 21 10:58 gt68xx.conf.new
-rw-r--r-- 1 tux tux 395 Dec 1 10:26 hp3900.conf
-rw-r--r-- 1 root root 395 Oct 21 10:58 hp3900.conf.new
-rw-r--r-- 1 tux tux 76 Dec 1 10:26 hp4200.conf
-rw-r--r-- 1 root root 76 Oct 21 10:58 hp4200.conf.new
-rw-r--r-- 1 tux tux 238 Dec 1 10:26 hp5400.conf
-rw-r--r-- 1 root root 238 Oct 21 10:58 hp5400.conf.new
-rw-r--r-- 1 tux tux 497 Dec 1 10:26 hp.conf
-rw-r--r-- 1 root root 497 Oct 21 10:58 hp.conf.new
-rw-r--r-- 1 tux tux 24 Dec 1 10:26 hs2p.conf
-rw-r--r-- 1 root root 24 Oct 21 10:58 hs2p.conf.new
-rw-r--r-- 1 tux tux 38 Dec 1 10:26 ibm.conf
-rw-r--r-- 1 root root 38 Oct 21 10:58 ibm.conf.new
-rw-r--r-- 1 tux tux 2597 Dec 1 10:26 kodakaio.conf
-rw-r--r-- 1 root root 2597 Oct 21 10:58 kodakaio.conf.new
-rw-r--r-- 1 tux tux 367 Dec 1 10:26 kodak.conf
-rw-r--r-- 1 root root 367 Oct 21 10:58 kodak.conf.new
-rw-r--r-- 1 tux tux 39 Dec 1 10:26 kvs1025.conf
-rw-r--r-- 1 root root 39 Oct 21 10:58 kvs1025.conf.new
-rw-r--r-- 1 tux tux 112 Dec 1 10:26 leo.conf
-rw-r--r-- 1 root root 112 Oct 21 10:58 leo.conf.new
-rw-r--r-- 1 tux tux 119 Dec 1 10:26 lexmark.conf
-rw-r--r-- 1 root root 119 Oct 21 10:58 lexmark.conf.new
-rw-r--r-- 1 tux tux 33 Dec 1 10:26 lexmark_x2600.conf
-rw-r--r-- 1 tux tux 187 Dec 1 10:26 ma1509.conf
-rw-r--r-- 1 root root 187 Oct 21 10:58 ma1509.conf.new
-rw-r--r-- 1 tux tux 1253 Dec 1 10:26 magicolor.conf
-rw-r--r-- 1 root root 1253 Oct 21 10:58 magicolor.conf.new
-rw-r--r-- 1 tux tux 665 Dec 1 10:26 matsushita.conf
-rw-r--r-- 1 root root 665 Oct 21 10:58 matsushita.conf.new
-rw-r--r-- 1 tux tux 279 Dec 1 10:26 microtek2.conf
-rw-r--r-- 1 root root 279 Oct 21 10:58 microtek2.conf.new
-rw-r--r-- 1 tux tux 268 Dec 1 10:26 microtek.conf
-rw-r--r-- 1 root root 268 Oct 21 10:58 microtek.conf.new
-rw-r--r-- 1 tux tux 2118 Dec 1 10:26 mustek.conf
-rw-r--r-- 1 root root 2118 Oct 21 10:58 mustek.conf.new
-rw-r--r-- 1 tux tux 808 Dec 1 10:26 mustek_usb.conf
-rw-r--r-- 1 root root 808 Oct 21 10:58 mustek_usb.conf.new
-rw-r--r-- 1 tux tux 13 Dec 1 10:26 nec.conf
-rw-r--r-- 1 root root 13 Oct 21 10:58 nec.conf.new
-rw-r--r-- 1 root root 593 Dec 1 10:26 net.conf
-rw-r--r-- 1 root root 573 Oct 21 10:58 net.conf.new
-rw-r--r-- 1 tux tux 365 Dec 1 10:26 p5.conf
-rw-r--r-- 1 root root 365 Oct 21 10:58 p5.conf.new
-rw-r--r-- 1 tux tux 75 Dec 1 10:26 pie.conf
-rw-r--r-- 1 root root 75 Oct 21 10:58 pie.conf.new
-rw-r--r-- 1 tux tux 669 Dec 1 10:26 pieusb.conf
-rw-r--r-- 1 root root 554 Oct 21 10:58 pieusb.conf.new
-rw-r--r-- 1 tux tux 1246 Nov 28 09:08 pixma.conf
-rw-r--r-- 1 root root 1246 Oct 21 10:58 pixma.conf.new
-rw-r--r-- 1 tux tux 4140 Dec 1 10:26 plustek.conf
-rw-r--r-- 1 root root 4140 Oct 21 10:58 plustek.conf.new
-rw-r--r-- 1 tux tux 942 Dec 1 10:26 plustek_pp.conf
-rw-r--r-- 1 root root 942 Oct 21 10:58 plustek_pp.conf.new
-rw-r--r-- 1 tux tux 391 Dec 1 10:26 qcam.conf
-rw-r--r-- 1 root root 391 Oct 21 10:58 qcam.conf.new
-rw-r--r-- 1 tux tux 29 Dec 1 10:26 ricoh.conf
-rw-r--r-- 1 root root 29 Oct 21 10:58 ricoh.conf.new
-rw-r--r-- 1 tux tux 183 Dec 1 10:26 rts8891.conf
-rw-r--r-- 1 root root 183 Oct 21 10:58 rts8891.conf.new
-rw-r--r-- 1 tux tux 13 Dec 1 10:26 s9036.conf
-rw-r--r-- 1 root root 13 Oct 21 10:58 s9036.conf.new
-rw-r--r-- 1 root root 1116 Dec 1 10:26 saned.conf
-rw-r--r-- 1 root root 1052 Oct 21 10:58 saned.conf.new
-rw-r--r-- 1 tux tux 48 Dec 1 10:26 sceptre.conf
-rw-r--r-- 1 root root 48 Oct 21 10:58 sceptre.conf.new
-rw-r--r-- 1 tux tux 1458 Dec 1 10:26 sharp.conf
-rw-r--r-- 1 root root 1458 Oct 21 10:58 sharp.conf.new
-rw-r--r-- 1 root root 69 Nov 19 19:56 sm3800.conf
-rw-r--r-- 1 tux tux 115 Dec 1 10:26 sm3840.conf
-rw-r--r-- 1 root root 115 Oct 21 10:58 sm3840.conf.new
-rw-r--r-- 1 tux tux 2239 Dec 1 10:26 snapscan.conf
-rw-r--r-- 1 root root 2239 Oct 21 10:58 snapscan.conf.new
-rw-r--r-- 1 tux tux 10 Dec 1 10:26 sp15c.conf
-rw-r--r-- 1 root root 10 Oct 21 10:58 sp15c.conf.new
-rw-r--r-- 1 tux tux 2225 Dec 1 10:26 st400.conf
-rw-r--r-- 1 root root 2225 Oct 21 10:58 st400.conf.new
-rw-r--r-- 1 tux tux 178 Dec 1 10:26 stv680.conf
-rw-r--r-- 1 root root 178 Oct 21 10:58 stv680.conf.new
-rw-r--r-- 1 tux tux 27 Dec 1 10:26 tamarack.conf
-rw-r--r-- 1 root root 27 Oct 21 10:58 tamarack.conf.new
-rw-r--r-- 1 tux tux 355 Dec 1 10:26 teco1.conf
-rw-r--r-- 1 root root 355 Oct 21 10:58 teco1.conf.new
-rw-r--r-- 1 tux tux 634 Dec 1 10:26 teco2.conf
-rw-r--r-- 1 root root 634 Oct 21 10:58 teco2.conf.new
-rw-r--r-- 1 tux tux 217 Dec 1 10:26 teco3.conf
-rw-r--r-- 1 root root 217 Oct 21 10:58 teco3.conf.new
-rw-r--r-- 1 tux tux 1807 Dec 1 10:26 test.conf
-rw-r--r-- 1 root root 1807 Oct 21 10:58 test.conf.new
-rw-r--r-- 1 tux tux 1494 Dec 1 10:26 u12.conf
-rw-r--r-- 1 root root 1494 Oct 21 10:58 u12.conf.new
-rw-r--r-- 1 tux tux 386 Dec 1 10:26 umax1220u.conf
-rw-r--r-- 1 root root 386 Oct 21 10:58 umax1220u.conf.new
-rw-r--r-- 1 tux tux 3083 Dec 1 10:26 umax.conf
-rw-r--r-- 1 root root 3083 Oct 21 10:58 umax.conf.new
-rw-r--r-- 1 tux tux 1681 Dec 1 10:26 umax_pp.conf
-rw-r--r-- 1 root root 1681 Oct 21 10:58 umax_pp.conf.new
-rw-r--r-- 1 root root 204 Oct 21 10:58 v4l.conf.new
-rw-r--r-- 1 tux tux 4295 Dec 1 10:26 xerox_mfp.conf
-rw-r--r-- 1 root root 4069 Oct 21 10:58 xerox_mfp.conf.new
Offline
Hi Gibor,
Sorry, good catch, i found why this happen, mistake in case of folder empty
config_dotnew prefix next files with folder.
/etc/sane.d/dll.d is empty folder, list files after prefix with /etc/sane.d/dll.d and mv function not work properly.
I update tazpkg and slitaz-base-files to fix it.
After check on wok, seem only packages impacted by this is :
root@arion:/home/slitaz/wok# find */taz/*/fs/etc -type d -name "*.new"
fail2ban/taz/fail2ban-0.11.2/fs/etc/fail2ban/filter.d/ignorecommands.new
postfix/taz/postfix-3.4.5/fs/etc/postfix/postfix-files.d.new
samba-pam/taz/samba-pam-3.6.7/fs/etc/samba/private.new
samba/taz/samba-3.6.7/fs/etc/samba/private.new
sane-backends/taz/sane-backends-1.0.32/fs/etc/sane.d/dll.d.new
Below diff of config_dotnew function :
config_dotnew() {
for file in $1; do
# In case of folder we need config files inside
if [ -d $root/$file ]; then
- dir=$file
- for f in $(ls $root/$dir |grep '.new'); do
- config_dotnew $dir/${f%.new}
- done
+ if [ "$(ls -A $root/$file)" ]; then
+ dir=$file
+ for f in $(ls $root/$dir |grep '.new'); do
+ config_dotnew $dir/${f%.new}
+ done
+ else
+ # Folder config is empty, we can remove .new
+ rmdir $root/$file.new
+ fi
else
# If no config file, mv it over
if [ ! -r $root/$file ]; then
if [ -r $root/$file.new ]; then
mv $root/$file.new $root/$file
fi
elif [ "[c]cat $root/$file | md5sum[/c]" = "[c]cat $root/$file.new | md5sum[/c]" ]; then
rm $root/$file.new
fi
fi
done
}
tazpkg on rolling by default keep also config_files except if [c]--newconf[/c] passed to overwrite config, for 6.0 i need to readd this feature, by default if config file don't have local change we overwrite it unless keep package config file with .new suffix
Offline
Hi gibor,
Sorry to read this 
.
If understand man /etc/passwd- and /etc/group- it's backup file used by shadow utils.
What actions you doing before /etc/passwd broken ?
I try to reproduce with iso, cook setup and hg clone wok-current repo, and cook packages try "slitaz-base-files" that contain /etc/passwd, don't see no issue.
Offline
Sorry, but I made a mistake. I removed the archive.cpio package that I had shared (saned-scanbd-files), which also contained the passwd and group files.
I will also remove the report.
Thank you.
Offline
Hello Shann, Yes, I restored those files. maybe it's just me, but does the cookutils package work on slitaz-6.0-x64?
I say this because after running the command
cook setup --wok
I get that all receipts are for i486 and I have to manually add
HOST_ARCH=“i486 arm x86_64”
Furthermore, the “xz” package is missing from the dependencies.
Once installed, it seems to work.
cook test
nodev overlay
Setup aufs chroot...
Cook: cooktest 1.0
================================================================================
QA: checking package receipt...
Executing: compile_rules
CFLAGS : -march=x86_64 -Os -pipe -fomit-frame-pointer
./configure && make && make install
-----------------------------------
* Log file : /home/slitaz/log/cooktest.log
* Package : make is installed
================================================================================
================================================================================
Pack: cooktest 1.0-x86_64
================================================================================
Executing: genpkg_rules
cp -a $install/usr/bin $fs/usr
------------------------------
* $fs : /home/slitaz/wok/cooktest/taz/cooktest-1.0/fs
* $stuff : /home/slitaz/wok/cooktest/stuff
* $install : /home/slitaz/wok/cooktest/install
* $src : /home/slitaz/wok/cooktest/source/cooktest-1.0
NOTE: Create, copy files from $install or $stuff
End of receipt: press ENTER to continue
Copying "receipt"... Fatto
Executing strip on all files... Fatto
Creating the list of files... Fatto
Creating md5sum of files... Fatto
Compressing the FS... Fatto
Updating receipt sizes... Fatto
Creating full cpio archive... Fatto
Restoring original package tree... Fatto
QA: checking for empty package... Fatto
Removing old package "cooktest-1.0-x86_64.tazpkg" Fatto
================================================================================
Package "cooktest-1.0-x86_64.tazpkg" created
Summary for: cooktest 1.0
================================================================================
Produced : 4.0K
Packed : 28.0K
Compressed : 2.2K
Files : 1
Cook time : 3s
Cook date : 2025-12-17 10:27
Host arch : x86_64
================================================================================
Leaving aufs chroot...
Offline
Hi Gibor,
nice to read recover
Bad, shame on me .
First forgot to add xz as depend of cookutils.
Normally wok-current have x86_64 HOST_ARCH, but think by default fetch http://hg.slitaz.org/wok and not wok-current.
For issue of build, it's me fault, CFLAGS on /etc/slitaz/cook.conf need to be adjust.
I add comment of this but don't add post_install step to update it automatically on x86_64 host.
[c]CFLAGS="-march=$ARCH -Os -pipe -fomit-frame-pointer"[/c] should be change to
[c]CFLAGS="-march=nocona -Os -pipe -fomit-frame-pointer -fPIC"[/c]
Offline
Hi Shann, don't worry, I don't use cook very often. Anyway, after changing the two lines, it's better, but I still need to understand how it works properly.
I was checking the sane-backend, libconfuse, and scanbd packages with mine; I found differences such as:
the libconfuse package inexplicably lacks the libconfuse.so.2.1.0, libconfuse.so.2, and libconfuse.so libraries
The sane-backends package requires autoconf-archive for compilation (it automatically applies patches during the ./autogen.sh process), which is missing from the receipt.
But I'll take my time and see what the next steps are.
Offline
Hi gibor,
I rebuild cookutils to fix issues you find.
Not sure to understand, if check libconfuse package, i see on /usr/lib three libs
(current64) root@eretria:/home/slitaz/wok# ls -l libconfuse/taz/libconfuse-3.3/fs/usr/lib/
total 52
lrwxrwxrwx 1 root root 19 Nov 27 16:56 libconfuse.so -> libconfuse.so.2.1.0
lrwxrwxrwx 1 root root 19 Nov 27 16:56 libconfuse.so.2 -> libconfuse.so.2.1.0
-rwxr-xr-x 1 root root 52016 Nov 27 16:56 libconfuse.so.2.1.0
For sane-backends, if understand i need to add ./autogen.sh step with autoconf bdep ?
Offline
[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.67 MiB (Peak: 1.77 MiB) ]