SliTaz Forum
You are not logged in.
Hi Aleksej,
Thank you for the hint on booting an ISO directly with G4D! The documentation of G4D is rather clumsy, so I never tried to understand and do this (only this morning did I find the "--config-file"-and-commands trick, at first I thought I would simply "chainload" G4D with its own menu.lst).
This will save me the time for mounting and copying; more than 3 seconds ;-)
Offline
Hi Aleksej,
I've just updated to the new tazpkg. Here's a behaviour that seems a bit strange. In tazpkg shell:
- recharge
- -cc
- up: this lists ~40 available updates; most of them are tagged "Rebuilt", e.g. avidemux; I answer "n"
- -gi avidemux: package "avidemux" is already installed, use --forced (...)
- up, answer "y": package "avidemux" already in cache, installing avidemux (...)
So: command "-gi" downloads the "rebuilt" package but will not install it. I expect it to install as command "up" does; am I wrong? If I am: why does it download something it's not going to install?
Offline
Also, a RFE: display a message while downloading a package. Even better: some kind of progress bar, if it's not asking too much!
Offline
Hi Lucas,
I tried to implement your requests: http://hg.slitaz.org/tazpkg/rev/8c6346ff1cef
Please, check the functions and report back.
Sorry in advance, Monday is hard day too — I'll free from work late again. On Tuesday I can devote a lot of time solving various issues.
Offline
Thanks for using the little time you have! This can wait Tuesday, really!
[c]tazpkg# -gi lxrandr
Le paquet « lxrandr » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
tazpkg# -gi lxrandr --forced
Le paquet « lxrandr » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.[/c]
:-S
[c]tazpkg# -g lxrandr
Connecting to mirror.slitaz.org (212.83.135.187:80)
Connecting to mirror1.slitaz.org (188.165.229.172:80)
lxrandr-0.3.0.tazpkg 100% |*******************************| 13840 0:00:00 ETA
Fait : lxrandr-0.3.0.tazpkg[/c]
Yipee! :-D
[c]tazpkg# up
Rechargement du dépôt « Main »
================================================================================
Vérification... [ Fait ]
Date des index : 15/11/2015 02:01
================================================================================
Le dépôt « Main » est à jour.
Paquet Dépôt Version Status
================================================================================
java-jre Main 1.8.0_40 → 1.9.9 (Bloqués)
lxde Main 0.3.2.1 Reconstruit
lxinput Main 0.3.4 Reconstruit
lxpanel Main 0.6.2 Reconstruit
lxrandr Main 0.3.0 Reconstruit
lxsession Main 0.4.6.1 Reconstruit
lxsession-edit Main 0.2.0 Reconstruit
pcmanfm Main aa3ca1c Reconstruit (Bloqués)
scilab Main 5.5.2 Reconstruit (Bloqués)
tazpkg Main 863 → 860
================================================================================
Vous avez 7 mises à jour disponibles (3 bloqués)
693 paquets installés scannés en 1s
Voulez-vous les installer maintenant ? (o/N) o
Le paquet « lxde » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxinput » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxpanel » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxrandr » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxsession » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxsession-edit » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « tazpkg » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.[/c]
So, blocked packages indeed are not updated (thanks to your new tazpkg, finally!).
"Rebuilt" packages are not either. But, first of all, what does "rebuilt" mean?
I thought it means a build dependency was changed, so the package is rebuilt even without a version change. If I'm right, then these packages should be updated, otherwise they might become inconsistent with some libs, no?
Offline
Hi Lucas,
Oh, it's all night :-S Thank you for fast report!
what does "rebuilt" mean?
Our building bot, cook.slitaz.org builds a packages using receipts. Cook rebuilds package if receipt changes; it can be upgrade or downgrade, it can be any other changes in the receipt, for example in the post_install(), or it can be due to addition of "description.txt"… In addition, Pascal added special button [Recook package] to the each package log, and any package can be rebuilt in one click.
There's can be rebuild without any changes. For example, "nano" depends on "ncursesw"; if "ncursesw" is updated — it better (in minor changes) or must (in major changes) to rebuild "nano". Whatever, in any rebuilding, the md5sum of package changed (because date of compiled files is changed, and present in the package archive). TazPkg pays attention to the version changes and md5sum of the packages.
How TazPkg indicates the changes:
[*]if version is changed, you'll see something like "863 → 860"
[*]if not — "Reconstruit" (this time no sense to tell about version).
Offline
I tried to run tazlito gen-distro, with:
tazpkg-861 - 42M
tazpkg-862 - 38M
remove this strange 10 lines, and you'll get no missing depends.
http://hg.slitaz.org/tazpkg/rev/8c6346ff1cef#l3.7
Offline
Hi Aleksej,
I installed tazpkg 865. I try to update a package marked as "Rebuilt":
[c]tazpkg# -gi lxrandr
lxrandr-0.3.0.tazpkg 100% |*******************************| 13840 0:00:00 ETA
Le paquet « lxrandr » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
tazpkg# -i lxrandr-0.3.0.tazpkg --forced
Installation du paquet « lxrandr »
================================================================================
LXDE monitor configuration tool
--------------------------------------------------------------------------------
Copie du paquet... [ Fait ]
Extraction du paquet... [ Fait ]
Mémorisation des paquets modifiés... [ Fait ]
Installation du paquet... [ Fait ]
Suppression des fichiers temporaires... [ Fait ]
Mise à jour des fichiers d'index... [ Fait ]
================================================================================
Le paquet « lxrandr » (0.3.0) est installé.
tazpkg# q
root@slitaz:~ # ls
lxrandr-0.3.0.tazpkg[/c]
So, package is downloaded although it will not be installed. It's downloaded into current WD.
Is this normal?
(If it's not normal: I'm not hurrying you! I'm just testing.)
Offline
Found the bug I think. In changeset 864 you moved the block starting with
[c]if [ "$tazpkg_command" == 'get-install' -a -z "$forced" ]; then[/c]
out of tazpkg and into modules/get, but now $i is undefined! (It was the [c]for[/c]-variable, line 458: [c]for i in $@; do[/c])
Offline
Hi Lucas,
Bug again. Seems it is bug in me 
Copy-pasting without testing, with confidence that it must to work. Hurry...
This time I tested my changes 
and now you can test tazpkg-866: http://cook.slitaz.org/cooker.cgi?pkg=tazpkg
What's new:
[*]fixing of packages updating. It should no download, nor update existing packages, until you apply a force;
[*]accidentally found out that packages blocking is broken again. I tested it after fixing this way:
[c]tazpkg# -lb
tazpkg# -b nano
tazpkg# -gi nano
tazpkg# -gi nano --forced
tazpkg# -u nano
tazpkg# -gi nano
tazpkg# -gi nano --forced[/c]
[*]Added command "[c]list-cache[/c]" to display cache content.
Offline
Autoremove, autoremove! xD
Алексей, у нас всё ещё нет возможности автоматом вычистить ненужные зависимости?
Offline
we still have no way to clean the machine unnecessary dependencies (Google-translated)
devl547, what do you call "unnecessary dependencies"? So called "orphaned" libs on a HDD install?
Then your post belongs to http://forum.slitaz.org/topic/tazpkg-improvements ;-)
Offline
Hi Alexander,
Yes, we still missed this necessary function. The system continues bloat from unwanted packages that were downloaded as dependencies and not removed once installed several programs "to see" and removed them. If I am not mistaken, the idea is in the air five years now or so.
I think is necessary to start with order to document the facts, why each of the packages was installed (as desired by the user, or as dependency to the other package with its name). Yet another database.
Offline
As a rough approximation we could remove all lib* packages that have no rdepends? (And iterate until there are no more of them.)
Anyway this "remove unneeded packages" thing will always have pitfalls. E.g. I occasionally compile a program from sources or install it from a tarball: it depends on some libs, but these dependencies are not "registered"...
Offline
This simple script...
[c]#!/bin/sh
awk -F$'\t' '
{
dep[$1] = " " $8 " ";
desc[$1] = $4;
size[$1] = $7;
}
END {
for (i in dep) {
orphan="yes";
for (j in dep) {
if (index(dep[j], " " i " ")) {
orphan = ""; break;
}
}
if (orphan) {
printf "\e[1m%s\e[0m: %s (%s)\n", i, desc, size[i];
++numorphans;
}
}
printf "============\n%s orphans\n", numorphans;
}
' /var/lib/tazpkg/installed.info[/c]
... will show you all your installed packages with their short description and size in which no one other package needs. Something like that:
[c]unzip: Zip dearchiver. (92K 280K)
...
ubuntu-font-family: Set of new libre/open fonts (1.3M 4.1M)
gtk-engines: All standart GTK+2 engines for themes (100K 548K)
linux-firmware: Firmware thats compiled from linux source code. (812K 1.9M)
...
locale-de: German locale pack (452K 2M)
openbox-imlib2: Small-footprint and standard compliant Window Manager (Allow icons in
menus). (168K 552K)
nano: GNU Nano Text Editor (100K 392K)
hicolor-icon-theme: Icon theme that all icon themes automatically inherit from. (16K
164K)
slitaz-icons-faenza-dark: SliTaz icon set based on the Faenza-Dark icons (32K 216K)
qupzilla-locales: Translations for the QupZilla browser (664K 5.4M)
gparted: GTK partition editor. (256K 856K)
tazdev: SliTaz developers tools. (16K 48K)
gnome-calculator: GNOME Calculator is a powerful graphical calculator with financial,
logical and scientific modes. (328K 4.1M)
get-rar: Get RAR packer. (16K 28K)
...
xarchiver: A GTK+ lightweight archive manager (104K 376K)
============
340 orphans[/c]
For better results we must check variable [c]SUGGESTED[/c]. For example, one of the lines above:
[c]qupzilla-locales: Translations for the QupZilla browser (664K 5.4M)[/c]
But I have package "qupzilla" installed:
[c]tazpkg info qupzilla
TazPkg information
================================================================================
Package : qupzilla
State : installed package
Version : 1.8.5 (new build available)
Category : network
Short desc : QupZilla - QtWebKit browser
Maintainer : claudinei@slitaz.org
License : GPL3
Depends : libQtCore libQtDBus libQtGui libQtNetwork libQtScript libQtSql
libQtXml libcrypto xorg-libX11 zlib cacerts xdg-utils libQtWebkit
Suggested : libQtWebkit-video qupzilla-locales
Build deps : wget cacerts Qt4-dev qmake openssl-dev xorg-libX11-dev
Web site : https://github.com/QupZilla/qupzilla
Size : 1.7M/6.7M
Tags : web-browser
================================================================================[/c]
... and this "qupzilla" suggested me to install "qupzilla-locales", and I installed it, so this package is not so useless. This leads me to want to add the contents of the variable "SUGGESTED" into the package database installed.info (it is better and faster to process single DB file than to cycle over hundreds of receipts in the /var/lib/tazpkg/installed, executing each of them as shell script to get content of their variables).
And — of course — we need to know [i]from where came a package, for example libsdl-mixer. Now on my system no package needs it. Most likely, that this package was installed as a dependency for a certain game that I have already removed. Therefore, this package can be deleted automatically.
________
Lucas, your example:
I occasionally compile a program from sources or install it from a tarball: it depends on some libs, but these dependencies are not "registered"...
You understand why the program can not be installed into the system without using the package manager? If so, then assemble the package and install it into the system. Describe it's dependencies in the receipt and all will be well. Do you agree?
Offline
we need to know from where came a package
This doesn't sound easy. I wonder if the feature is worth the effort. Or maybe you just need to add a flag, say "d", in the DB, to packages installed as deps?
Do you agree?
Yes, I know I'd better write a receipt...
Offline
you can test tazpkg-866
1) -gi is now working right
2) blocked packages aren't updated, as expected (with only blocked packages in the list given by "up", tazpkg doesn't even ask, nice!)
3) list-cache: add it to "usage"?
Thanks for these improvements.
Offline
hello folk, on slitaz5-rc3 if try to change repos to another version get this error
root@slitaz:~$ tazpkg setup-mirror
Current mirror(s)
=======================================================================
http://mirror.slitaz.org/packages/5.0/
Please enter URL of the new mirror (http, ftp or local path). You must specify
the complete address to the directory of the packages and packages.list file.
New mirror(s) URL: http://mirror.slitaz.org/packages/4.0/
Setting mirror(s) to: "http://mirror.slitaz.org/packages/4.0/"
root@slitaz:~$ tazpkg recharge
Recharging repository "Main"
=======================================================================
Creating backup of the last packages list... [ Done ]
Getting "bundle.tar.lzma"... [ Failed ]
Recharging failed
Restoring database files... [ Done ]
root@slitaz:~$
bug or locked at fixed repos?
Offline
Hi gibor,
Format of the packages database evolved and don't backward-compatible with the format of SliTaz-4.0 packages DB. I changed it to provide speedup of DB retrieving and some possibilities available only with the new format. I planning to add backward compatibility with the old format but I have not enough time now. Probably it is a task for January.
If you need recognition of (only) old format now, you can manually search, download and install package "tazpkg" from the SliTaz-4.0 on http://pkgs.slitaz.org/ and after that you can change the mirror.
I only want to warn you that almost all of the SliTaz 4.0 packages are unusable in the SliTaz Rolling / 5.0 because they are compiled with the older versions of "glibc" (package "glibc-base") and "gcc" (package "gcc-lib-base"). At the same time, you still can use packages that not including compiled binary executables, for example, icon themes, gtk themes, fonts, python scripts, or shell scripts.
Offline
Hi aleksey, thank for your explained, no problem for me.
Compatibilty not is problem, recompile packages on case,
[ot]
my goal is restructuring slutaz5 on too old format slitaz
And I have make this procedure two time (slitaz 3> to 2 and 4 to 3) and at this time tried to reply 5 to 4.
Or on another word my system mantain the same structure of primary version of slitaz.
This is more important for me, the force of slitaz is the fast script on boot. For the rest (sorry at all) prefer on another style of development (es. like slitaz-archlinux).
[/ot]
thank at all.
Offline
Sorry, I can't understand your quote completely.
Why anyone needs to move to ancient structure?
What the structure is?
What advantages does it give?
To maintain own distribution as a single developer is a hell.
All programs and libraries drops compatibility from time to time, not only SliTaz itself. It is attempt to make them faster, better, to provide new features. Attempt to be compatible with the other recent mainstream libraries and programs. Just progress and evolution...
Offline
Sorry, I can't understand your quote completely.
Why anyone needs to move to ancient structure?
What the structure is?
What advantages does it give?
To maintain own distribution as a single developer is a hell.
answer an order to your post
ancient or old it's a concept very relative, more people are obsessed do this at least...
http://www.linuxfromscratch.org/lfs/view/development/index.html
the basic system linux it performant essential and to run all conventional application, all other flavours added it's optional and only a personal trend.
The first version have more more concept of lfs, other versione are missed this impriting.
To recreate a similar first ambient of linux it simple: remove tazpanel, polkit, webserver and other gnome like, and the system are upgraded from binary/library and perform at same mode on all standard applications.
IMHO
Offline
Thank you for explanation.
Seems all you need is looks like "base" flavor.
But here a lot people for whom base is not enough.
As far as I know, SliTaz not violated packages building rules: all files are in places as mainstream developers expected.
If you want, please give me examples how you change the structure (other than removing tazpanel, polkit and any other removing - I already understand it from your post).
Also, in addition to lfs, the blfs project exist: http://www.linuxfromscratch.org/blfs/view/svn/
It contains Polkit that you removed. And many other useful things...
Offline
Hi aleksej, say to have more difficult to speak on english, and to do explain this step it's an big obstacle.
Anyway polkit I put out of the door since 20year old (window have polkit embedded...) and step by step the more trashware migrate to linux.
I not allowed this invasion, on my home have access only friendly software. All other code it tray out mercylessy.
Whats is my reference so? Simply Slitaz-3.0. If the developer working on this direction well, or another case I self made the my system!
have a nice day.
Offline
Hi gibor,
I see. It's hard to you to speak English.
I do not want to torture you, so I close our discussion.
If I understand you correctly, you using the package list from SliTaz 3.0 with the packages actually from SliTaz Rolling. And that's all.
I respect the right of others, but I doubt I can help you to move current SliTaz back to SliTaz 3.0. At least for me, it will not make me happy.
Respect.
Offline
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.61 MiB (Peak: 1.77 MiB) ]