On 2013-02-14, James wrote: > So, my latest ideas is to "sync up" and then wait one week > before acutally installing those new packages. This would > allow the fodder that the good folks on this list catch, > bitch about (um, I mean file bug reports) and fix, to > occur first; then I can complete the package update > cautiously avoiding an "emerge sync".
The fun thing is that this is supposed to be why we do have unstable keywords. Some of the breakage which happened and hit the stable tree with no timely news item was actually discussed for some time before in the -devel list. You may want to follow that list too. That "sync up" you talk about is effectively equivalent to having ~amd64 for amd64. > But when you "emerge sync" if to do the updates immediately, they'll be > the latest packages. If I do a "emerge sync" and wait > 7 days to begin updating the packages, I'll be delayed > by one week, and have a one week of buffered fixes for added > problem filtering. But those fixes might not be available > without a fresh "emerge sync"? > > > When time permits I CAN CHOOSE to "emerge sync" and then immediately > update the packages and parse through the issues mostly. Call > this the stable-stable approach to gentoo updates. > > Does anyone see any problems or a better way to stay one-week-delayed ? Packages with problems simply shouldn't hit stable. I'd rather just do --sync and perform world upgrades, and I would just keep an eye on the triggered updates, in order to spot any potentially problematic package (like c++-based libraries). > I'm increasingly managing more Gentoo systems, particularly embedded > and server based gentoo systems and that is the source that compounds these > time-sink-issues for me. Maybe some external-integrated management approach > such as CFengine is my answer? > > Your comments and thoughts are most welcome. Your problem does not seem to be emerge --sync, but that you run commands that cause existing upgrades to be applied on a system-wide basis. If there is a fix you need/want, re-emerge that specific package, and let the others wait. Only the strictly needed dependencies should be pulled this way. You're not forced to use "-DuN world" or even "-DuN" every time you want to upgrade something. -- Nuno Silva (aka njsg) http://njsg.sdf-eu.org/
