You are not logged in.
- Topics: Active | Unanswered
#1 2009-05-12 00:49:25
- Paingiver
- Member
- Registered: 2008-03-01
- Posts: 83
About careful update,system maintaning and dangerous packages to hold
-I want to know about which packages you usually prevent from updating?And how to do it?
-With what command i can delete everything the package i have installed?Including config files.
-Upgrading often is more convenient way for ArchLinux?
-If you reinstall or install Arch on other machines,have you written install guide or script for yourself,can you share it?
-Best aides for pacman(yaourt is a good one i know)
Offline
#2 2009-05-12 00:53:39
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,477
- Website
Re: About careful update,system maintaning and dangerous packages to hold
-I want to know about which packages you usually prevent from updating?And how to do it?
man pacman.conf
-With what command i can delete everything the package i have installed?Including config files.
man pacman
-Upgrading often is more convenient way for ArchLinux?
Yes
-If you reinstall or install Arch on other machines,have you written install guide or script for yourself,can you share it?
Yes
-Best aides for pacman(yaourt is a good one i know)
Offline
#3 2009-05-12 01:08:50
- Paingiver
- Member
- Registered: 2008-03-01
- Posts: 83
Re: About careful update,system maintaning and dangerous packages to hold
1-But which packages do you hold?
3-Will you share them?
4-No,i mean like colorizing,numbering the results in pacman in console.
Offline
#4 2009-05-12 01:22:21
- bangkok_manouel
- Member
- From: indicates a starting point
- Registered: 2005-02-07
- Posts: 1,556
Re: About careful update,system maintaning and dangerous packages to hold
1-But which packages do you hold?
Holding packages will bring you more troubles in the long run unless you know what you are doing. Given your question, you may not really know.
3-Will you share them?
http://aur.archlinux.org/packages.php?ID=22747 ?
4-No,i mean like colorizing,numbering the results in pacman in console.
Offline
#5 2009-05-12 01:28:22
- Paingiver
- Member
- Registered: 2008-03-01
- Posts: 83
Re: About careful update,system maintaning and dangerous packages to hold
Wow packup seems a great idea. And what about your config files. Do you just copy them to their place or using a program or a script for them?
Offline
#6 2009-05-12 08:57:23
- bangkok_manouel
- Member
- From: indicates a starting point
- Registered: 2005-02-07
- Posts: 1,556
Re: About careful update,system maintaning and dangerous packages to hold
Wow packup seems a great idea. And what about your config files. Do you just copy them to their place or using a program or a script for them?
It should be quite easy and straight forward to simply copy them. OTOH, I see more and more people using github to store and manage their dotfiles.
Offline
#7 2009-05-12 11:15:56
- onguarde
- Member
- Registered: 2008-09-14
- Posts: 144
Re: About careful update,system maintaning and dangerous packages to hold
-I want to know about which packages you usually prevent from updating?And how to do it?
-Upgrading often is more convenient way for ArchLinux?
I've been thinking more seriously about update frequencies recently. Especially considering the varying levels of brokenness I experience which takes quite some time to fix. This includes minor software compatibilities eg. firefox extensions. Or major functionality problems eg. broken suspend. Or worse, superhard to track show-stopping evil bugs.
The consensus seems to be update often and fix/downgrade as you go along.
http://wiki.archlinux.org/index.php/Downgrade_packages
However, if you want to fix stuff less often, you should update less often. Afterall, bugs introduced by bleeding edge packages might be fixed later on even newer ones. Updating less often allows you to see less of these buGs. Of course, this still doesn't solve the issue of experiencing "bugs" when you finally decide to update.
http://arm.nrk.cc/ (More info in the wiki)
To minimise this issue, I'm thinking of using the "Arch Roll back machine". The idea is that you update at a lower frequency of 3 months(variable) and when you finally do update, sync your system 1 week(variable) late. The idea is that by the time you sync, all the show-stoppers or bugs and their "solutions/fixes" are clearly spelt out in forums and the net. Thus, allowing you to fix stuff easily.
On the whole this results in a highly maintainable system which is as bleeding edge as you desire. If you need specific applications to be updated more frequently, just update those alone. Conversely, if you want your all your apps to be bleeding edge but not the kernel and other hardware stuff, you can blacklist those in pacman.conf.
Last edited by onguarde (2009-05-12 11:18:17)
Offline
#8 2009-05-12 12:06:51
- mapr
- Member
- Registered: 2008-06-29
- Posts: 20
Re: About careful update,system maintaning and dangerous packages to hold
I some time ago read a writing about keeping up arch servers. Tips there included reading forum for problems other people have had with updates recently... Expecially after important packages(or many) have been updated I'd say it is better to wait a while before updating, unless you are bored.
So far I have been using "Update often and rollback when needed" -method for my Desktop and eee. With my vdr/samba/etc. server I have been updating much less frequently and only after updating Desktop and eee.
Have to admit that sometimes it would be nice to have one more repo for 'proven' packages. Maintaining such in useful way might be bit too worksome, but for server usage I would happily choose such repo. So, it just depends a lot to what system is used and how much time freetime you have.
Offline
#9 2009-05-12 12:33:54
- bangkok_manouel
- Member
- From: indicates a starting point
- Registered: 2005-02-07
- Posts: 1,556
Re: About careful update,system maintaning and dangerous packages to hold
Have to admit that sometimes it would be nice to have one more repo for 'proven' packages. Maintaining such in useful way might be bit too worksome, but for server usage I would happily choose such repo. So, it just depends a lot to what system is used and how much time freetime you have.
FTR, all core packages have to be signed-off by at least two developers and will automatically spend some time in testing. That's what I would call 'proven'.
Offline
#10 2009-05-12 12:55:46
- mapr
- Member
- Registered: 2008-06-29
- Posts: 20
Re: About careful update,system maintaning and dangerous packages to hold
FTR, all core packages have to be signed-off by at least two developers and will automatically spend some time in testing. That's what I would call 'proven'.
I'd call that 'tested' 
Offline