> Well I think ~x86 is generally usable, but you do have to be a bit > more cautious. For example, I don't mind --sync every day, but I tend > to delay any updates that involve portage, baselayout, or other > lowlevel system packages until Friday nights, after making a backup, > so I have the whole weekend to pickup the pieces if something should > break.
I agree fully. That doesn't make it any less frustrating when things go wrong ;-) I am fairly cautious. I've learned to not upgrade my servers unless needed, and I use my notebook as the "testing ground". But there are still slight differences that cause me headaches here and there. I've also found that doing these upgrades during the week-days, it's easier to get someone to respond on the list. Friday night and weekends tend to have a delay till Monday -- where your email gets lost in a sea of others and deleted. During the week, people are monitoring their inbox more frequently and theres a better chance of a reply. Plus I do this while at my work, so I have another computer to use to get online and send emails with, if I hose my notebook (like the past few days ) ;-) > And today I think if you encounter anything stable that depends on a > ~x86 package, it is a bug, and should be filed as such. Well, again, that was a while ago, and now I'm used to the package.keywords file... > > My file is empty?! :( > > > > > Is there a way to rebuild this file? > > The job of depscan.sh is to rebuild this file. But if the file exists > and is newer than the configuration in /etc, it will not do anything, > even it if deptree is empty. So delete deptree, and run depscan.sh > again with the --debug option. You should see a bit more happen. Good to know for future reference. > > How did this happen? > > A badly timed Ctrl-alt-del or reboot could be the culprit. There is a > window of opportunity while depscan is running that if it is aborted, > will leave you with an empty file. Ah. Well glad to know it's not anything that couldn't be rebuilt. It seems that 'baselayout' did that for me. As always Richard, I think you for your patience and knowledge. I also really got a kick out of your name/email address... So CLEVER! :D d -- [email protected] mailing list
