Thank you, Aleksej,
It compare them only in the terms "equal" and "not equal".
Oh, I see: tazpkg will always prefer a package on the mirror over the local one. I guess the question then becomes how a mirror can become unstable like that - I would think that once a newer version has arrived to the mirror from whatever the source (cooker?) it would be impossible for this mirror to revert back to the previous version. Maybe this is a subject for another discussion some other day :)
Just select stable mirror. Any, but "mirror.slitaz.org".
I am using http://www.gtlib.gatech.edu/pub/slitaz/packages/5.0/ I guess it became unstable too momentarily, next time I will try something else.
I guess, you have already installed "freetype-infinality", "libwebkit-video", and "yad-html". But due to bugs in the tazpkg, packages "freetype", "libwebkit", and "yad" was not removed properly.
Yes I have both "namesake" and "dashed" installed, but I am not sure the "namesake" packages should always be removed. For example, don't we need both "freetype" and "freetype-infinality" packages installed for the latter to work properly?
Also, this is not the first time this happens to me. The first time it happened back in March at the same time I had issues updating noted in the link above, but then I blamed it on the overloaded cooker, unstable mirror and all of that, and did not raise the alarm. The misbehaving dash-packages were the same ones as now, plus "hexchat" and "hexchat-plugins". I almost fixed everything then by first removing the "dash" package, then removing the "namesake" package, then installing "namesake" package and the installing the "dash" package again. Almost - because it worked for all troubled packages but "yad" and "yad-html" - that pair simply refused to cooperate, meaning that I could not remove either. Here is some terminal output from those attempts:
zann@poop:~$ sudo tazpkg remove yad
Package "yad-html" is not installed.
zann@poop:~$ sudo tazpkg -gi yad
"yad" package is already installed.
You can use the --forced option to force installation.
zann@poop:~$ sudo tazpkg -gi yad --forced
yad-html-0.28.1.tazp 100% |*******************************| 57604 0:00:00 ETA
Installation of package "yad-html"
================================================================================
Display graphical dialogs from shell scripts or command line (with HTML widget)
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
Update system databases... [ Done ]
================================================================================
Package "yad-html" (0.28.1) is installed.
You see what I mean? Weird, huh? I just could not get rid of "yad" at all. Since then every single time I would call "tazpkg up" it would offer an update for "yad" as New build, but install "yad-html" instead, over and over again. And recently the other three packages came back, I guess triggered by their recent legitimate updates.
I could try "fixing" it now as I did back in March, but I would rather try your suggestions that could lead to finding the root of the problem.
By the way, this happens only on one of the two SliTaz installations that I operate. The other one started from a more recent rolling release, not sure if this matters, though. And I could not find any differences between the two setups that could lead to this "dash-package" issue.
Anyway, I would be glad to try anything you may suggest.
Thank you,
-Z.