SliTaz Forum
You are not logged in.
Hi All,
I just installed Slitaz rolling and when trying to update the packages there's a notification to update Tazpkg firstly. However when checking the installed version of Tazpkg vs the Tazpkg mentioned in the update list both are version 5.7.
Not sure if this is a bug but updating doesn't work due to this, not sure if this only on my end or not?
Many thanks in advance for your reply.
Offline
Hi cg5216,
Can you post the return of
[c]tazpkg info tazpkg[/c]
Didn't you forget to use [c]--forced[/c] when trying to update:
[c]tazpkg -gi tazpkg --forced[/c]
EDIT: what ISO did you use? All are 2026-05-25 on the mirror and should have tazkg 5.4 (if my memory serves me good)
Offline
Hi Ceel,
I did the tazpkg info tazpkg which returned v5.6. After that i ran tazpkg -gi tazpkg --forced and did tazpkg info tazpkg which returned v5.7 (new build available).
After that i ran the Package manager gui and did Recharge list and then Check Upgrades. When scrolling down I still see the "You need to upgrade tazpkg first" warning again.
Used ISO for install is Slitaz core rolling dated 25 May 2026 which has v5.6 onboard.
Thank you for helping out, I'm not new to Linux (Arch user here) but new to Slitaz. My device where I installed Slitaz on is a EEEPC 701SD, old device but still useful thanks to Slitaz 
Offline
Took some info off the terminal and the Package Manager just now also.
[attachment=54048,3862] [attachment=54048,3863]
Offline
See tazpkg.txt for the terminal feedback on tazpkg info tazpkg and tazpkg -gi tazpkg --forced
Offline
Hmm. yes there is something wrong.
I'm going to try to test that this afternoon.
Offline
Thank you again Ceel, really appreciate it.
Offline
I can reproduce it. The new build seems broken.
@devs,
Couldn't it linked at this new extension [c]-any[/c] that has appeared for some packages recently cooked?
[attachment=54052,3864]
Offline
Hi Ceel,
Thx for confirming, I was actually planning to ask what the diff was between these 2 packages.
[attachment=54053,3865]
Offline
Issue stil not fixed. And still more [c]*-any[/c] packages on the mirror:
[c]
Recharging repository "Main"
======================================================
Checking... [ Done ]
Database timestamp: 06/15/2026 22:17
Creating backup of the last packages list... [ Done ]
Getting "bundle.tar.lzma"... [ Done ]
Getting "files-list.lzma"... [ Done ]
======================================================
Last database is ready to use.
Mirrored packages diff
======================================================
qt5-locale-de-5.14.2-any
jdk7-langtools-2.5.1-any
qt5-locale-pt-5.14.2-any
fast-lzma2-dev-1.0.1-any
qt5-locale-sv-5.14.2-any
lame-dev-3.100-any
qt5-locale-sl-5.14.2-any
notecase-lang-1.9.8-any
jdk7-hotspot-2.5.1-any
qt5-locale-uk-5.14.2-any
qt5-locale-zh_TW-5.14.2-any
pulseaudio-man-13.0-any
qt5-locale-zh_CN-5.14.2-any
linux-libre-btrfs-3.18.129-gnu-any
gpxe-pxe-0.9.3-any
qt5-locale-fr-5.14.2-any
libgtop-lang-2.40.0-any
pulseaudio-locale-13.0-any
pulseaudio-vala-13.0-any
glew-dev-2.1.0-any
qt5-locale-cs-5.14.2-any
linux-libre-without-modules-3.18.129-gnu-any
qt5-locale-pl-5.14.2-any
openjdk-7-src-b147-27_jun_2011-any
qt5-locale-da-5.14.2-any
qt5-locale-hu-5.14.2-any
pulseaudio-dev-13.0-any
palemoon-26.5.0-any
qt5-locale-ru-5.14.2-any
linux-libre-source-3.18.129-gnu-any
linux-libre-udf-3.18.129-gnu-any
qt5-locale-es-5.14.2-any
pam-dev-1.2.0-any
openjdk-6-src-b20-21_jun_2010-any
gpxe-0.9.3-any
======================================================
39 new packages on the mirror.
[/c]
Offline
Fixed: https://hg.slitaz.org/cookutils/rev/4eb82e7378ad
The tricky and hard part was to handle no suffix for the i486 arch (legacy, history) for 5.1 but also prepare for slitaz 6.0 who will get a suffix for all arch (already the case for -x86_64 or -arm).
Tested here locally with ~300 packages rebuild, audited by Claude Opus. The build host will get the fix shortly.
Online
Hello Ceel, Pankso,
Thank you so much for looking into this and fixing the issue, really love Slitaz so far and happy my good old EEEPC 701 is back in action thanks to your efforts.
I'll keep an eye out for the updated/fixed package.
Thanks again!!!
Offline
@pankso,
Issue fixed for [c]cook[/c] but not for [c]tazpkg[/c].
The problem is [c]packages.md5[/c] knows [c]tazpkg-5.7-any.tazpkg[/c]
I did a [c]tazpkg recharge[/c], "wgeted" [c]tazpkg-5.7-any.tazpkg[/c] and install it with [c]--forced[/c] but still blocked with "you must udpate tazpkg first"
The mirror needs to be cleaned of all the [c]-any[/c] packages, and then recook these packages.
Offline
I was wondering what was going on and whether I'd messed something up somehow. Glad to know the problem is almost resolved.
Offline
Hi Ceel, Pankso,
I saw that the -any packages are removed from the mirrors and just tried installing Tazpkg again after clearing the computer cache firstly and recharging the list.
Used Sakura with the command tazpkg -gi tazpkg --forced which installed Tazpkg 5.7.
Afterwards i went to the package manager, recharged the list again and did check upgrades.
Result: The message You need to upgrade tazpkg is still in place for some reason.
Offline
Simply a shame 
All SliTaz users who want update their system are blocked because of this.
I see in Cook that the packages haven't been rebuilt; so the [c]packages.md5[/c] file has probably the md5 of the [c]-any[/c] packages...
Offline
Let's hope the issue gets solved, really like using Slitaz and don't wanna switch to something else. Anyway we'll see
Thanks for your help Ceel, fingers crossed here!!
Offline
checked tazpkg md5 in [c]packages.md5[/c]
[c]tazpkg recharge[/c]
Database timestamp: 06/18/2026 11:34, tazpkg md5 in [c]packages.md5[/c] modified
[c]tazpkg -gi tazpkg --forced[/c]
[c]md5sum tazpkg-5.7.tazpkg[/c]
compared md5 with the one in [c]packages.md5[/c] : \o/
[c]tazpkg up -r[/c]
You need upgrade tazpkg first !
@"devs"
Did you really test your commits before pushing them?
Offline
Hi all,
Several of you have hit this: on a system that's actually up-to-date, tazpkg up
reports hundreds of available updates ("You have 298 available upgrades…"), often
followed by the "You need upgrade tazpkg first!" message that loops forever.
Meanwhile spk-up correctly reports "System is up-to-date". Here's what's going on.
The root cause
To decide whether a package needs upgrading, you compare the installed package
against the one on the mirror. The problem: the two sides weren't comparing the same
thing.
- On the installed side, tazpkg records the checksum of the .tazpkg file (the real
md5 of the package).
- On the mirror side, the database is built by cook-pkgdb, which writes a "release
checksum" (RSUM) into that same field — a hash computed from the contents, the
receipt and the description, not the file md5.
So tazpkg was comparing two checksums of different kinds. They could never match, so
every installed package was flagged as a new build — hence the 298 phantom updates.
And because tazpkg itself was in that list, you'd get "upgrade tazpkg first" with no
way out.
On top of that, RSUM is itself unreliable: its value drifts between the moment the
mirror is built and install time. It was never a dependable basis for upgrade
detection — and since the .md5 lists already carry exactly what we need (the file
checksum), RSUM serves no purpose here.
This is a long-standing bug — it's been there for years, quietly turning every tazpkg
up into a wall of false positives.
Why spk gets it right
spk (the next-gen package manager) sidesteps the whole thing: for upgrade detection
it ignores that field entirely and compares the package file md5 directly, via
installed.md5 vs packages.md5. Both sides hold the same, reliable value — so spk up
gives the correct answer today.
The plan
The fix is to align tazpkg with spk: compare the package file checksum instead of the
mismatched field. Because this is critical and touches every user's upgrades, I'm
landing it in spk first (it's the safer place to validate the behavior), then porting
the same fix into tazpkg once it's confirmed solid.
Good news: the fix is entirely client-side — no mirror rebuild needed. Existing
systems are corrected automatically once the fixed manager is in place.
What to do now
Option A — use spk today (recommended). spk already does the right thing. Install it
and run your upgrades through it:
tazpkg get-install spk
spk up
(spk up recharges the lists and upgrades, the same as tazpkg up. Use spk up --check
to just see what's upgradable without installing.)
Option B — wait for the tazpkg fix. If you'd rather stay on tazpkg, just wait: the
fix will ship in a tazpkg update. Once it's on the mirror, a normal upgrade picks it
up and tazpkg up behaves correctly again — no manual steps, nothing to reinstall.
In the meantime, if tazpkg up nags you to "upgrade tazpkg first", it's the
false-positive bug described above — it's safe to ignore, and using spk up avoids it
entirely.
Thanks for the reports that helped pin this down.
— pankso
Online
Hi Pankso,
Thank you for your reply, will be trying out spk for sure seen this will be the long term solution to the issue as far as i understand.
Edit: just installed spk and played around with it a bit while typing this reply. Good solution and 100% terminal for now which is great and fast on my good old EEEPC.
Thank you very much for spending time on this tazpkg issue and for suggesting spk as future package manager.
Thanks again!!
Offline
So welcome dear! That's all about an open-source project driven by voluntaries. We all do our best for the community. Even if we do many test we can't get all bugs alone, we need community feedback.
Thank you being part of a more stable SliTaz OS!
Dont's hesitate to post any bug you discover, we are listening.
BTW: the current process is a FULL rebuild of all packages for better consistent (some will get dropped, other fixed). Don't be afraid if you get daily update those next weeks.
BONUS: > Good solution and 100% terminal for now!
Try out spk-tui! In between a real graphical interface and the old time terminal ;-)
PS: Some old folks will shout of if I make spk the default (even with my args of slitaz founder), so tazpkg will stay in place, hopefully getting fixes and improvment from my work on spk). Spk let me implemt new features wihle tazpkg stays the legacy packages manager.
Enjoy you EEpc.
A smile,
- Pankso
Online
Hi Pankso,
Thank you for the kind words, I'll definitely will be trying out spk-tui. On arch i also always use tui apps as much as possible so spk-tui will be very useful for sure.
As Linux user I very much respect the people putting so much effort and free time in developing distros and packages. Thank you for the support people like yourself and Ceel bring to the community!!
No worries on the now very old one core celeron M EEEPC, as long as it runs it will be used and running Slitaz
Tanks mate!!
Offline
Yep, the new installer is working for me as well. Thanks!
Offline
@pakso Sorry to bother you again, i was just wondering how to upgrade spk from v2.0 to 2.1 which is now on the mirrors (at least on https://distro.ibiblio.org/slitaz/packages/5.0/).
I tried doing upgrade in spk 2.0 as described in the help function by entering upgrade in the search field but except for the message "System upgrade" on the first line and "You mu" on the second line nothing happens. Unless this is not functional yet of course.
Offline
sorry forgot to attach the screenshot
[attachment=54081,3866]
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]