SliTaz Forum

Upgrade from 4.0 to Cooking

(13 posts) (4 voices)

• Started 10 years ago by shann
• Latest reply from Aleksej
• This topic is not a support question

Tags:

No tags yet.

1. 

   shann
   

   offline

   Administrator

   I test upgrade from 4.0 (up to date) to cooking in VM.

   I found two bugs:

   1/ When type tazpkg, a link appear
   
   2/ Desktop bug.
   

   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.
   

   Attachments

   1. Deskop_after_upgrade.png (7 KB, 1,224 downloads) 10 years old
   2. Desktop_after_pango_command.png (12.4 KB, 1,302 downloads) 10 years old
   3. tazpkg_upgrade-cooking_bug.png (11.3 KB, 1,280 downloads) 10 years old

   Posted 10 years ago #
2. 

   shann
   

   offline

   Administrator

   I try to change icon theme (use humanity icon theme) with lxappearance, not change, but when i try to use SliTaz icon set, i have error in Terminal.

   

   Attachments

   1. lxappearance_error.png (53.5 KB, 1,428 downloads) 10 years old

   Posted 10 years ago #
3. 

   subreptice
   

   offline

   Member

   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.

   Posted 10 years ago #
4. 

   shann
   

   offline

   Administrator

   Ok, I don't see your post.

   My goals is to use slitaz gtkonly for create my own desktop, but for now cooking doesn't have this flavor.

   Then, i use set-release for upgrade to cooking.

   Posted 10 years ago #
5. 

   shann
   

   offline

   Administrator

   if the upgrade from 4.0 to 5.0 pre-release is impossible.
   I can't imaginate the work that will have to make to successfully upgrade from 4.0 to 5.0 final :)

   Posted 10 years ago #
6. 

   Aleksej
   

   offline

   Coder-hobbyist

   1/ When type tazpkg, a link appear
   

   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.

   Posted 10 years ago #
7. 

   shann
   

   offline

   Administrator

   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.

   Posted 10 years ago #
8. 

   mojo
   

   offline

   Key Master

   When a tazpkg receipt has the CONFIG_FILES=
   tazpkg repack-config includes those files with the users custom configurations in config-1.0.tazpkg
   tazpkg list-config 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

   Posted 10 years ago #
9. 

   shann
   

   offline

   Administrator

   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
   ================================================================

   Posted 10 years ago #
10. 

    mojo
    

    offline

    Key Master

    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?

    Posted 10 years ago #
11. 

    Aleksej
    

    offline

    Coder-hobbyist

    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).

    Posted 10 years ago #
12. 

    mojo
    

    offline

    Key Master

    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"

    Posted 10 years ago #
13. 

    Aleksej
    

    offline

    Coder-hobbyist

    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?

    Posted 10 years ago #

RSS feed for this topic

Reply

You must log in to post.