SliTaz Forum
You are not logged in.
Pages: 1
1) It happens again - tazpkg offers a "downgrade":
zann@poop:~$ sudo tazpkg up
Password:
Recharging repository "Main"
================================================================================
Checking... [ Done ]
Database timestamp: 06/27/2016 17:01
================================================================================
Repository "Main" is up to date.
Package Repository Version Status
================================================================================
freetype Main 2.6.1 New build
libwebkit Main 1.8.3 New build
nano Main 2.6.1 → 2.4.3
tazpkg Main 910 → 908
yad Main 0.28.1 New build
================================================================================
You have 5 available upgrades (0 blocked)
386 installed packages scanned in 6s
Do you wish to install them now? (y/N)
Why would tazpkg want to replace nano and itself with earlier versions? I checked the cooker, and it has been quiet for some 8-10 hours prior to my update.
2) There is an issue with [some] packages containing dashes. For whatever reason, tazpkg offers freetype, libwebkit and yad over and over again (for months), but actually installs freetype-infinality, libwebkit-video and yad-html instead. And this vicious cycle never breaks. Any ideas?
Thank you,
-Z.
Offline
Hi Zann,
Very thanks for your link! 
You kindly let me not repeat myself about mirrors. Please, read it again and don't use "mirror.slitaz.org" as your selected mirror.
Now answering fresh questions.
How can tazpkg offer the "downgrades" at all? Really, it not compared packages versions in the terms "newer" or "older". It compare them only in the terms "equal" and "not equal". If package installed on your SliTaz is "not equal" to the version (or build) of the package provided in the mirror — you'll see it.
Really, only few times packages was "downgraded" to the previous versions because of the incompatibility issues. And it is not he case with the "nano" and "tazpkg" versions. Your mirror is unstable, — I wrote it about mirror.slitaz.org — first it give you new packages list with nano-2.6.1 and tazpkg-910, and you upgrade them. Then it give you old packages list with nano-2.4.3 and tazpkg-908, and you see it as "downgrade".
Just select stable mirror. Any, but "mirror.slitaz.org". Updates may be delayed on the half-day or even a day, but it will give you the same packages list now, and 10 minutes later, and 10 minutes later again.
Second question.
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.
I'll working against this bug.
Offline
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.
Offline
Hi Zann,
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.
The whole process:
[*]SliTaz developers make changes to the SliTaz receipts on their computers;
[*]Then they pushed that changes to the wok: hg.slitaz.org/wok;
[*]Cooker (cook.slitaz.org) wake up every 2 hours (or close to next 5 minutes when it been poked by button "Poke cooker") and check the changes on wok:
[c]2016-06-30 17:00 : No revision changes: 19251 vs 19251
2016-06-30 17:00 : Updating wok: /home/slitaz/wok-hg[/c]
or
[c]2016-06-30 19:33 : Packages to cook: 2
2016-06-30 19:30 : Changes found from: 19251 to 19252
2016-06-30 19:30 : Updating wok: /home/slitaz/wok-hg[/c]
[*]Cooker cooks all changed packages (as well as packages with pressed button "Recook <package>" on the corresponding cooker pages);
[*]Late night cooker makes packages databases. The daily log is here: pkgdb.log on cooker main page;
[*]Early morning on the main mirror mirror1.slitaz.org the process is started: it pulled all the new packages and packages databases from cooker server (I know pretty small about this process);
[*]Every "mirror", the servers that mirrors SliTaz packages (with packages databases, of course) synchronized new data on their own, during the day;
If you switch from one mirror to the another during the day, you will see some mirrors are fully updated, some are partially (databases, and/or some packages), and some mirrors are outdated;
[*]When you issue "tazpkg recharge" (or "tazpkg up"), your software (tazpkg) downloads packages database from your selected mirror. And it shows you changes: new packages, updated packages, etc.
[c]--[/c]
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.
Frankly, I don't know how it can be Gatech mirror is unstable (on the Earth, well)... But facts...
I'll try to write simple tool to check all the mirrors every hour, or half an hour, and will check mirrors several days.
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?
The packages in question are alternatives. Not all packages "with dashes" and "without", but "freetype" and "freetype-infinality" are. Really, you need only one at a time. For other alternatives, please see special file from SliTaz packages database on your SliTaz installation: [c]/var/lib/tazpkg/packages.equiv[/c]. Format of the file is not very simple, but here you can see next very clear lines:
[c]freetype=freetype-infinality
hexchat=hexchat-plugin
libwebkit=libwebkit-video[/c]
It's all about alternatives. Also, here you can find next (not very clear) line:
[c]yad=libwebkit:yad-html gtk+3:yad-gtk3[/c]
It means in English: there are alternatives for "yad" package exists. If you have "libwebkit" installed, then alternative to "yad" is "yad-html". If you have "gtk+3" package installed, then alternative to "yad" is "yad-gtk3".
I'll plan to make changes to the tazpkg: it will remove the package automatically before installing the alternative. Now you can do it yourself. Something like:
[c]tazpkg -r yad-html
(confirm removing package; reject removing dependent packages)
tazpkg -r yad
(also as previous)
tazpkg -gi yad-html
(while you installed "yad-html", not just "yad": exactly "yad-html" will be installed)[/c]
Offline
Hello Aleksej,
Great info, as always - thank you very much, I have learned quite a bit.
tazpkg -r yad-html
(confirm removing package; reject removing dependent packages)
tazpkg -r yad
(also as previous)
tazpkg -gi yad-html
(while you installed "yad-html", not just "yad": exactly "yad-html" will be installed)
The second step fails:
zann@poop:~$ sudo tazpkg -r yad-html
Remove package "yad-html" (0.28.1)? (y/N) y
Removing package "yad-html"
================================================================================
Removing all files installed... [ Done ]
Update system databases... [ Done ]
Removing package receipt... [ Done ]
================================================================================
Package "yad-html" (0.28.1) removed.
zann@poop:~$ sudo tazpkg -r yad
Package "yad-html" is not installed.
The same approach worked absolutely fine for "freetype" and "libwebkit", so I tried it on "yad" again and got this:
zann@poop:~$ sudo tazpkg -r yad-html
Remove package "yad-html" (0.28.1)? (y/N) y
Removing package "yad-html"
================================================================================
Removing all files installed... [ Done ]
Update system databases... [ Done ]
Removing package receipt... [ Done ]
================================================================================
Package "yad-html" (0.28.1) removed.
zann@poop:~$ sudo tazpkg -r yad
Package "yad-gtk3" is not installed.
Different, but similar It looks like tazpkg tries to remove an alternative and not the specified package.
Next I did the "tazpkg up" and got this:
zann@poop:~$ sudo tazpkg up
Recharging repository "Main"
================================================================================
Checking... [ Done ]
Database timestamp: 06/30/2016 17:01
================================================================================
Repository "Main" is up to date.
Package Repository Version Status
================================================================================
yad Main 0.28.1 New build
================================================================================
You have 1 available upgrade (0 blocked)
384 installed packages scanned in 0s
Do you wish to install them now? (y/N) y
yad-gtk3-0.28.1.tazp 100% |*******************************| 55232 0:00:00 ETA
Installation of package "yad-gtk3"
================================================================================
Display graphical dialogs from shell scripts or command line (GTK+3)
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
Update system databases... [ Done ]
================================================================================
Package "yad-gtk3" (0.28.1) is installed.
As you can see, "freetype" and "libwebkit" were fixed and no longer offered, but "yad" still is, although this time "yad-gtk3" was installed instead of "yad-html". Consequent "tazpkg up" keep offering "yad" update as New build, and keep installing "yad-gtk3" instead.
I wonder, why did it work with "freetype" and "libwebkit" and does not work with "yad" ?
-Z.
Offline
Pages: 1
[ Generated in 0.024 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]