SliTaz Forum
You are not logged in.
Pages: 1
I had the not so brilliant idea of upgrading packages. Tazpanel, updated the list, select all, upgrade... it did that, just now I can't boot it. It's a full HD setup via the liveCD. Is there any way to fix that? it's not a good thing that it happens after like 4 updates to the final distro btw, and it's a shame...
Offline
Probably because you were using one of the RC to do the upgrade and you upgraded to the Cooking Repository and not the Stable one. In short, you should have done tazpkg set-release stable ; tazpkg recharge before upgrading. Even the normal upgrade transition has a few issues, especially if you upgrade from an RC version.
Offline
mmm, it's possible that it was an RC. not really sure of it. I'll reinstall.
Still, it's not the first update I made on that system, and I did update packages list, then checked upgrades, then updated all. the other couples of times I did that it worked flawlessy. Strange.
I think those kind of issued are best to be ironed out once and for all, to make slitaz more "robust", if it were my main system I'd be crying...
On a side note, I tried an upgrade via the tazpanel on the live CD, both with cooking and stable, but x refuses to start, seems like is behaving as earlier RC.
Offline
You need to set the release to stable in tazpkg (tazpkg set-release stable) otherwise it will keep upgrading your version to Cooking, which will break it. Not that the transition to release from one of the RC versions is much better. Most people just download SliTaz 4 and reinstall because of it.
Offline
mmm, I'll "tazpkg set-release stable", after reinstalling the stable.
But I think this should be a default setting on stable slitaz, why releasing a system that can be broken so easily from tazpanel? Not much sense right?
Offline
Pre-April 10, 2012 Cooking: tazpkg set-release 4.0 or tazpkg set-release stable
Check /etc/slitaz-release ,if it's still set to cooking it will break if you update it.
Some programs you may try to install won't work.
Same problem if you run Slitaz-3.0 and don't tazpkg set-release 3.0
You'll install tazpkgs from stable/4.0 and break your system.
A major clue that your using the wrong repo is if you run tazpkg up -c and it lists every tazpkg in your system as needing to be upgraded.
Before you install tazpkgs or update.
Slitaz-3.0: tazpkg set-release 3.0
Pre-April 10,2012 Cooking : tazpkg set-release 4.0
Offline
well, I just formatted and reinstalled.
I still think this behaviour should be "fixed" in some way, maybe via a version check, or a special package (metapackage?): breaking an OS because of pkg management is not a good thing.
Offline
I fully agree with piovrauze's comment above - a version check is mandatory before allowing for upgrades. Last night I did an upgrade on one of my systems and now I cannot log back in at all! In my case it did not matter too much (except for the need to spend time on reinstalling) as this was not a system I use regularly but if this was the only system I had then I would have been more than annoyed.
Offline
Pages: 1
[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]