On Sun, 2006-09-04 at 11:42 -0700, Zac Medico wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Brian wrote: > > Just a word of caution. I don't know why but sometimes after an upgrade > > of portage a reload(portage) in porthole fails and porthole crashes. I > > don't remember the details atm and have not investigated the reasons. > > In all cases restarting porthole, all works fine again. It may not ever > > happen to your code though. > > If you're able to reproduce that with the latest ~arch version of portage > then I would appreciate it if you'd file a bug. > > Zac
upgrading from 2.1_pre7-r3 to -r5, then re-loading portage in the running porthole session went smooth this morning. I believe the last time might have been upgrading to pre7-r3, maybe from -r2. If I remember correctly it usually reports failing to import one of the modules. Restarting porthole and trying a portage reload always works. I don't think it is a portage fault, but maybe a python one involving changes to the pym directory and path changes that a running python session is not detecting and using the old now stale module paths. -- Brian <[EMAIL PROTECTED]> -- [email protected] mailing list
