closed not a support question
Ceel
offlineAdministrator
Oooh yes, you're right again !
Aleksej 2 | Ceel 0
I remember now I left the installation with tazpkg-test to see if the warning message existed too with tazpkg.
Then I wrote the first post and then... I tested the root option but in the "bad" installation...
Sorry.
I hope you enjoyeded your cup of coffee at least ;-)
Aleksej
offlineCoder-hobbyist
Hi Ceel!
It's okay, no need to make excuses. Here's my fault in the fact that one package overwrites files of another package. And tester needs to block original "tazpkg"…
Nevertheless, testing was stretched. Let's wait what mojo to say, and perhaps update the "tazpkg" to the latest version.
(Nevertheless I drink too much coffee :-D)
Ceel
offlineAdministrator
Hi Aleksej,
This is not a bug report, just a warning for those who have removed tazpkg and install tazpkg-test for... tests :-)
When tazpgk-test upgrades sliatz-config-base it re-installs tazpkg:
Tracking dependencies for package "slitaz-configs-base" ================================================================================ Missing package "tazpkg" ================================================================================ 1 missing package to install. Package "tazpkg-839" already in the cache Checksum error for "tazpkg-839.tazpkg" Recharging repository "Main" ================================================================================ Checking... [ Done ] Database timestamp: 11/04/15 02:01 ================================================================================ Repository "Main" is up to date. Installation of package "tazpkg" ================================================================================ SliTaz packages manager -------------------------------------------------------------------------------- Copying package... [ Done ] Extracting package... [ Done ] Remember modified packages... [ Done ] Installing package... [ Done ] Removing all tmp files... [ Done ] Execute post-install commands... [ Done ] Update system databases... [ Done ] ================================================================================ Package "tazpkg" (839) is installed.
Aleksej
offlineCoder-hobbyist
Hi Darjeeling,
Thank you for the reporting.
But, why do I have so different results with you? I write here using that ISO now.
Packages: 247
247 items
247 packages installed.
tux@slitaz:~$ wc -l < /var/lib/tazpkg/installed.info
247Installed packages: 247
Selected packages: 246
Yes, last package in the list, "zlib" is lost. And it lost before, on the default "100 packages per page" settings.
And default Rolling Core ISO have no packages you listed: "xorg-xsetroot" and "yad". Do you installed them later? There are only similar "xorg-xset" and "yad-html".
I confirm that TazPanel shows not full list and missed the last entry in the list.
Thank you!
________
PS. Now I recharged TazPkg databases using TazPanel, and installed packages "xorg-xsetroot" and "yad". There "247" changed into "249" everywhere. But TazPanel "Packages > My packages" now ends with:
xorg-xset
xorg-xsetroot
xterm
yad
yad-htmlLast entry "zlib" is still missed (compared to output of "tazpkg -l").
Then I updated all available updates (15 packages) and installed "tazpkg-test". A bit better in the TazPanel, but still "zlib" missed.
________
PPS. This issue fixed in the "tazpkg-test-859". I do not want to backport all the fixes back to the "tazpkg" package because I plan to remove "tazpkg-test" and to update "tazpkg" to the latest version from day to day.
llev
offlineMember
Hi Aleksej,
Just saw on Hg your huge improvement to "remove" command. Very instructive reading!
Two suggestions:
- I think you can avoid the printf "%s%s\n", root,... thing by using this: xargs -I filename rm -f "$root"/filename < "$files2remove"
- you can avoid the while [ -n "$dir" ]; loop thanks to rmdir -p
Aleksej
offlineCoder-hobbyist
Hi Lucas,
Thank you!
I can use your first suggestion. Just I not well familiar with the "xargs" command :)
But in the second suggestion I see no point. Loop here is to remove only empty sub-folders and folders.
Imagine, we have a large number of files in the "faenza-icon-theme":
/usr/share/icons/Faenza/actions/16/add.png
/usr/share/icons/Faenza/actions/16/add-files-to-archive.png
...We have /var/lib/tazpkg/installed/faenza-icon-theme/files.list where all that files are listed. Note, the folders aren't listed here.
Then we removed all the files, but it's folders still here.
So we tried to remove /usr/share/icons/Faenza/actions/16.
It will error if it not empty (if for example, I put here my own file), and loop will break.
But in the normal case we will remove:
/usr/share/icons/Faenza/actions/16
and then (because it now empty)
/usr/share/icons/Faenza/actions
and
/usr/share/icons/Faenza
and stop. We can't remove
/usr/share/icons
because it contains some other folders.
Can you simplify the algorythm? Current works well as we normally have not very large number of the folders in the packages.
Aleksej
offlineCoder-hobbyist
Many thanks to all who participated in the testing!
From now package "tazpkg-test" discontinued, and maybe used in the future to test some extremely updates.
On the other hand, package "tazpkg" updated to the latest current version (859).
And this tazpkg-859 now installed on our cooking bot http://cook.slitaz.org/ (I was afraid not to break it.)
All of your bug reports / feature requests you can write here as always.
Have a nice day! ;)
Darjeeling
offlineMember
Thanks for investigating and for your reply, Aleksej. So, we've both been using this ISO ...
http://cook.slitaz.org/cookiso.cgi?distro=rolling-core
http://mirror1.slitaz.org/iso/rolling/slitaz-rolling.iso
... and yet, we get different numbers of installed packages? Weird. Except for our different keyboard settings, which don't require the installation of a package, the two live sessions should be identical. Is it possible that, depending on the found hardware, the boot procedure pulls in additional packages?
I will download a fresh copy of the ISO and test everything again thoroughly later this afternoon and let you know if there's any difference.
P.S.:
Are xorg-xsetroot and yad displayed in both, your TazPanel and your 'tazpkg -l' lists?
Aleksej
offlineCoder-hobbyist
No, my Rolling Core a bit different :)
http://mirror1.slitaz.org/iso/rolling/slitaz-rolling-core.iso
I preferring it because I don't need 4-in-1 feature provided by "slitaz-core.iso" (without "core" in the name).
OK, I'll test it now too, out of curiosity...
________
PS. No, 247 packages too, and no "xorg-xsetroot" and "yad" in the Core session.
These packages belongs only to "Gtkonly" session, but absent on a "higher layer" "Core".
Maybe you extracted four rootfs*.gz by hands and concatenated them to single rootfs.gz?
(I just run ISO using Grub4dos without any extractions from ISO.)
Darjeeling
offlineMember
> Maybe you extracted four rootfs*.gz by hands and concatenated them to single rootfs.gz?
Nah, I didn't do this. I'm using a script that downloads and verifies the latest rolling ISO and then extracts a special justX ISO for my own experiments. I've been using this script for some time and it's been working well. The original ISO is not altered by the procedure. I have checked the md5 again earlier this afternoon and it was ok. So, here are the latest results of my investigation :-) ...
pcmanfm /var/lib/tazpkg/installed => 249
present: xorg-xsetroot
present: yad
present: zlib
tazpkg -l => 247
missing: xorg-xsetroot
missing: yad
present: zlib
wc -l < /var/lib/tazpkg/installed.info => 247
missing: xorg-xsetroot
missing: yad
present: zlib
TazPanel Summary => 247
TazPanel My packages (manually counted, 500 lines pp) => 246
missing: xorg-xsetroot
missing: yad
missing: zlib
I've also checked in /usr/bin and in /usr/lib and found that xorg-xsetroot, yad and zlib are definitely installed in the latest rolling ISO (08. Nov.). This means that at some stage /var/lib/tazpkg/installed.info hasn't been updated properly which is a corruption of the package database. The missing zlib in TazPanel is probably just a harmless bug in the page code.
Aleksej
offlineCoder-hobbyist
Seems it will not working this way. I only can suggest you to tweak your script.
You may know it already that every rootfs*.gz has it's own packages database in the /var/lib/tazpkg.
"Graphical" rootfs has some different configuration files (now I writing from smartphone and can't recall) in the /usr/share/applications/ (something like "...default...").
If you unpack "base" flavor, then unpack "justx" over it, then "gtkonly" — all new files will overwrite it's old content, and any problem. No, really problems will appear if you'll unpack rootfs*.gz in a wrong order...
But I don't know how it works (but it works like a charm) that packages "yad" and "xorg-xsetroot" present only on the layer number 3. Next layer, number 4, Core, adds more packages, files, but these two packages not present on this layer. It works when you boot official ISO. But it not works if you (or your script) unpacking rootfs*.gz files.
Bug with missing last list entry I already fixed, you can update tazpkg manually from cook.slitaz.org or wait tomorrow (or maybe later, when this package will appear in mirror you use).
Darjeeling
offlineMember
Thanks for your reply, Aleksej, but I think there's been a misunderstanding. In my previous post I was referring to the original, unaltered rolling ISO (08. Nov.) as it can be downloaded from the mirror. I only mentioned my own private justX extract because you had asked whether I might have been using such a self-made rootfs-gz for these tests. I haven't.
This is about the rolling ISO (08. Nov.) that's currently on the mirror ...
http://mirror1.slitaz.org/iso/rolling/slitaz-rolling.iso
... the packages xorg-xsetroot and yad are pre-installed on this ISO as can be seen in /var/lib/tazpkg/installed. The files of these two installed packages can be found in /usr/bin and in /usr/lib. The problem is that the index file /var/lib/tazpkg/installed.info doesn't match the package-db in /var/lib/tazpkg/installed ...
- 249 entries in /var/lib/tazpkg/installed
- 247 entries in /var/lib/tazpkg/installed.info
... because the entries for xorg-xsetroot and yad are missing in the index file. I think this is the reason why TazPanel and 'tazpkg -l' don't display the complete list of all installed packages. At some stage /var/lib/tazpkg/installed.info hasn't been updated properly which is a corruption of the package database.
This topic has been closed to new replies.
