SliTaz Forum
You are not logged in.
Pages: 1
I test upgrade from 4.0 (up to date) to cooking in VM.
I found two bugs:
1/ When type tazpkg, a link appear
[attachment=25817,1143]
2/ Desktop bug.
[attachment=25817,1146]
For second bug, i resolv partially with old post (http://forum.slitaz.org/topic/desktop-icons-and-font-problems)
i execute in root pango-querymodules > '/etc/pango/pango.modules'
The font is now normal, but icons not appear.
[attachment=25817,1145]
Offline
Hello shann
I was told here
http://forum.slitaz.org/topic/trying-to-tazpkg-set-release-cooking
they are too many differencies to do succesfully a tazpkg set-release cooking.
Offline
1/ When type tazpkg, a link appear
[attachment=25817,1143]
Main SliTaz's configuration file: /etc/slitaz/slitaz.conf
It exists in the package slitaz-base-files (see receipt)
File /etc/slitaz/slitaz.conf exists in the CONFIG_FILES variable in this receipt. What it mean?
Configuration files not upgraded when you upgrade your packages. Huh...
You get new slitaz-base-files and old config file for near all system.
If package upgrade not change these configs, then what a way to change them? I think, only manually.
Where to get latest /etc/slitaz/slitaz.conf? In the Hg repo: http://hg.slitaz.org/slitaz-base-files/raw-file/tip/rootfs/etc/slitaz/slitaz.conf
Log in as root (or open PCManFM as root), navigate to /etc/slitaz directory, and open file slitaz.conf in your text editor.
Remove all file content, copy content from Hg repo and paste to text editor, save and exit.
I think, its all with this bug/feature.
Offline
hi Aleksej,
Infact, /etc/slitaz/slitaz.conf doesn't upgrade, i try your solution, work.
1/ Tazpkg bug => Fixed.
2/ In the case of desktop, I think is a same problem, severals config files doesn't upgrade for icon set.
Offline
When a tazpkg receipt has the CONFIG_FILES=
[c]tazpkg repack-config[/c] includes those files with the users custom configurations in config-1.0.tazpkg
[c]tazpkg list-config[/c] shows every CONFIG_FILE on your system.
This creates a tazpkg with your custom configs for reloading/auto-installing on boot if placed in
/home/boot/packages folder of frugal install.
This is a way of creating a persistant system without repacking rootfs.gz
When /etc/init.d/bootopts.sh installs config-1.0.tazpkg it's config files overwrite the defaults.
Reference: http://doc.slitaz.org/en:cookbook:receipt => $CONFIG_FILES
Offline
This is list sort by tazpkg list-config
I reduce no significant folder
================================================================
[/boot/isolinux/] somes files
/etc/adduser.conf
/etc/daemons.conf
/etc/dnsd.conf
[/etc/dropbear/] somes files
/etc/filesystems
/etc/fstab
/etc/group
/etc/gshadow
/etc/gtk-2.0/gtk.immodules [! important ? ]
/etc/host.conf
/etc/hostname
/etc/hosts
/etc/httpd.conf
/etc/inetd.conf
/etc/init.d/local.sh
/etc/inittab
/etc/issue
/etc/keymap.conf
/etc/locale.conf
/etc/lxpanel/default/config [! important ? ]
/etc/lxpanel/default/panels/panel [! important ? ]
/etc/network.conf
/etc/networks
/etc/nsswitch.conf
/etc/pango/pango.modules [ ! important, need use pango-querymodules for upgrade manually ]
/etc/passwd
[/etc/ppp/] somes files
/etc/profile
/etc/rcS.conf
/etc/resolv.conf
/etc/securetty
/etc/services
/etc/shadow
/etc/shells
/etc/slim.conf
/etc/slitaz/applications.conf
/etc/slitaz/slitaz.conf
/etc/tazlito/distro-packages.list
/etc/TZ
/etc/udhcpd.conf
/etc/wpa_supplicant.conf
================================================================
Offline
CONFIG_FILES has nothing to do with preventing a package,file,or folder from being overwritten during an upgrade.
It's a feature of tazpkg which allows the user to pack the listed files into a tazpkg for re-installation.
Did you use tazinst to do the upgrade?
Offline
mojo,
http://doc.slitaz.org/en:cookbook:receipt#variables-optional
$CONFIG_FILES : Some packages provide customized configuration files. The $CONFIG_FILES variable provides a list of these files that can be saved by the 'tazpkg repack-config' command. These files are not overwritten when reinstalling the package if they already exist and the package can be successfully recreated with 'tazpkg repack', (even if they have been modified since).
Offline
Aleksej,
I stand corrected 
It makes sense you wouldn't want a package update that includes a configuration file to overwrite the users configuration with the default file.
shann,
/etc/slitaz/applications.conf => WINDOW_MANAGER="lxde-session"
Offline
mojo,
clue that sometimes we should overwrite old default config file with the new default config file. Like in this case with slitaz.conf.
I propose next behavior. If user not changed config -- then it md5sum is unchanged -- then tazpkg should overwrite this config. In other hand, if "power user" changed config once, he knows what to do with it to change it again.
Do you agree? Let's coding?
Offline
Pages: 1
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]