[gentoo-user] portage broken because of Unicode bugs
After my last update, portage stopped working. Google led me to believe it was this bug: http://bugs.gentoo.org/show_bug.cgi?id=317775 Which was said to be fixed in portage 2.1.9. So I upgraded from 2.1.8.X to 2.1.9.1, and now portage is even more broken. Now I can't even use it to downgrade to the older version of portage (which would at least work if you ran it using --quiet). This is a fine kettle of fish alpha grante # emerge --quiet portage Traceback (most recent call last): File "/usr/bin/emerge", line 43, in retval = emerge_main() File "/usr/lib/portage/pym/_emerge/main.py", line 1678, in emerge_main myopts, myaction, myfiles, spinner) File "/usr/lib/portage/pym/_emerge/actions.py", line 286, in action_build settings, trees, myopts, myparams, myaction, myfiles, spinner) File "/usr/lib/portage/pym/_emerge/depgraph.py", line 5947, in backtrack_depgraph myaction, myfiles, spinner) File "/usr/lib/portage/pym/_emerge/depgraph.py", line 5966, in _backtrack_depgraph success, favorites = mydepgraph.select_files(myfiles) File "/usr/lib/portage/pym/_emerge/depgraph.py", line 1426, in select_files self._load_vdb() File "/usr/lib/portage/pym/_emerge/depgraph.py", line 320, in _load_vdb fake_vartree.sync() File "/usr/lib/portage/pym/_emerge/FakeVartree.py", line 119, in sync self._sync() File "/usr/lib/portage/pym/_emerge/FakeVartree.py", line 171, in _sync pkg = self._pkg(cpv) File "/usr/lib/portage/pym/_emerge/FakeVartree.py", line 195, in _pkg type_name="installed") File "/usr/lib/portage/pym/_emerge/Package.py", line 63, in __init__ self._validate_deps() File "/usr/lib/portage/pym/_emerge/Package.py", line 92, in _validate_deps self._metadata_exception(k, e) File "/usr/lib/portage/pym/_emerge/Package.py", line 241, in _metadata_exception "%s: %s in '%s'" % (k, e, path)) UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 23: ordinal not in range(128) -- Grant Edwards grant.b.edwardsYow! I'm in direct contact at with many advanced fun gmail.comCONCEPTS.
Re: [gentoo-user] portage broken
On Thursday 14 September 2006 18:17, Drew wrote: > Hi Frank, > > Daniel's solution was one suggested in an earlier thread. The other > was to delete your portage tree and reinstall it via web-rsync > followed by a regular sync. The problem has been documented and the > patch is supposed to work it's way into portage soon: > > [1] http://bugs.gentoo.org/show_bug.cgi?id=147010 > > -- > -Drew Hi Drew, thank you for the hint!! That did the trick. Also a big thank you to Bo Ørsted! Kind regards Frank -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] portage broken
On 9/14/06, Frank Baumeister <[EMAIL PROTECTED]> wrote: On Thursday 14 September 2006 14:48, Daniel Iliev wrote: > Try this: > > rm /usr/portage/metadata/timestamp.chk > emerge --sync Unfortunately that didn't fix the problem. Regards Frank -- gentoo-user@gentoo.org mailing list Hi Frank, Daniel's solution was one suggested in an earlier thread. The other was to delete your portage tree and reinstall it via web-rsync followed by a regular sync. The problem has been documented and the patch is supposed to work it's way into portage soon: [1] http://bugs.gentoo.org/show_bug.cgi?id=147010 -- -Drew -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] portage broken
On Thursday 14 September 2006 14:34, Frank Baumeister wrote: > whenever I run emerge it aborts with the following error message: > [SNIP] > pTraceback (most recent call last): > File "/usr/bin/emerge", line 4049, in ? > emerge_main() > File "/usr/bin/emerge", line 3770, in emerge_main > portage.global_updates(settings, trees, mtimedb["updates"]) > File "/usr/lib/portage/pym/portage.py", line 6656, in global_updates > myupd) > File "/usr/lib/portage/pym/portage_update.py", line 198, in > update_config_files > write_atomic(updating_file, "".join(file_contents[x])) > File "/usr/lib/portage/pym/portage_util.py", line 728, in > write_atomic > f.close() > File "/usr/lib/portage/pym/portage_util.py", line 696, in close > os.rename(self.name, self._real_name) > OSError: [Errno 16] Device or resource busy > localhost # http://bugs.gentoo.org/show_bug.cgi?id=147010 -- Bo Andresen pgp3osaLZ02P7.pgp Description: PGP signature
Re: [gentoo-user] portage broken
On Thursday 14 September 2006 14:48, Daniel Iliev wrote: > Try this: > > rm /usr/portage/metadata/timestamp.chk > emerge --sync Unfortunately that didn't fix the problem. Regards Frank -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] portage broken
Try this: rm /usr/portage/metadata/timestamp.chk emerge --sync Frank Baumeister wrote: > Hello, > > whenever I run emerge it aborts with the following error message: > > localhost # emerge --sync > > Performing Global Updates: /usr/portage/profiles/updates/3Q-2006 > (Could take a couple of minutes if you have a lot of binary packages.) > .='update pass' *='binary update' @='/var/db move' > s='/var/db SLOT move' S='binary SLOT move' > p='update /etc/portage/package.*' > > pTraceback (most recent call last): > File "/usr/bin/emerge", line 4049, in ? > emerge_main() > File "/usr/bin/emerge", line 3770, in emerge_main > portage.global_updates(settings, trees, mtimedb["updates"]) > File "/usr/lib/portage/pym/portage.py", line 6656, in global_updates > myupd) > File "/usr/lib/portage/pym/portage_update.py", line 198, in > update_config_files > write_atomic(updating_file, "".join(file_contents[x])) > File "/usr/lib/portage/pym/portage_util.py", line 728, in > write_atomic > f.close() > File "/usr/lib/portage/pym/portage_util.py", line 696, in close > os.rename(self.name, self._real_name) > OSError: [Errno 16] Device or resource busy > localhost # > > I have no clue how to solve this problem, so any help would be greatly > appreciated! > > Kind regards > Frank > -- Best regards, Daniel -- gentoo-user@gentoo.org mailing list
[gentoo-user] portage broken
Hello, whenever I run emerge it aborts with the following error message: localhost # emerge --sync Performing Global Updates: /usr/portage/profiles/updates/3Q-2006 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' pTraceback (most recent call last): File "/usr/bin/emerge", line 4049, in ? emerge_main() File "/usr/bin/emerge", line 3770, in emerge_main portage.global_updates(settings, trees, mtimedb["updates"]) File "/usr/lib/portage/pym/portage.py", line 6656, in global_updates myupd) File "/usr/lib/portage/pym/portage_update.py", line 198, in update_config_files write_atomic(updating_file, "".join(file_contents[x])) File "/usr/lib/portage/pym/portage_util.py", line 728, in write_atomic f.close() File "/usr/lib/portage/pym/portage_util.py", line 696, in close os.rename(self.name, self._real_name) OSError: [Errno 16] Device or resource busy localhost # I have no clue how to solve this problem, so any help would be greatly appreciated! Kind regards Frank -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] portage broken?
Hi, On (18/12/05 07:54), Martins Steinbergs wrote: > I was running update world and after portage was updated to 2.1_pre1 look > what > etc-update did to me. I dont have detailed build log, at least emerge.log > shows nothing suspicious. good there is portage-rescue. Should I file bug? > Yes, sometimes must pay for running ~amd64. > ...SKIP... > File "/usr/lib/portage/pym/portage_db_cdb.py", line 17, in ? > import portage_db_template > ImportError: No module named portage_db_template > Scanning Configuration files... > Exiting: Nothing left to do; exiting. :) > > > martins > -- > Linux 2.6.14-gentoo-r5 AMD Athlon(tm) 64 Processor 3200+ > 07:42:50 up 1 day, 11:11, 6 users, load average: 1.11, 1.22, 1.25 A known problem with the new portage cache rewrite, solutions: 1.this ML sometime yesterday (three liner script); 2.this ML-mail from jstubbs (shortly do "emerge metadata") and disable 'cdb' if using it. 3.Check on http://dev.gentoo.org/~jstubbs (check again the name here); 4.Solution is also in Gentoo Forums. HTH.Rumen pgpO7WL3sTOhY.pgp Description: PGP signature
[gentoo-user] portage broken?
I was running update world and after portage was updated to 2.1_pre1 look what
etc-update did to me. I dont have detailed build log, at least emerge.log
shows nothing suspicious. good there is portage-rescue. Should I file bug?
Yes, sometimes must pay for running ~amd64.
mar bin # etc-update
Traceback (most recent call last):
File "/usr/lib/portage/bin/portageq", line 270, in ?
main()
File "/usr/lib/portage/bin/portageq", line 260, in main
import portage
File "/usr/lib/portage/pym/portage.py", line 6786, in ?
portdb=portdbapi(settings["PORTDIR"])
File "/usr/lib/portage/pym/portage.py", line 4779, in __init__
self.auxdbmodule =
self.mysettings.load_best_module("portdbapi.auxdbmodule")
File "/usr/lib/portage/pym/portage.py", line 1287, in load_best_module
return load_mod(best_mod)
File "/usr/lib/portage/pym/portage.py", line 145, in load_mod
mod = __import__(modname)
File "/usr/lib/portage/pym/portage_db_cdb.py", line 17, in ?
import portage_db_template
ImportError: No module named portage_db_template
Traceback (most recent call last):
File "/usr/lib/portage/bin/portageq", line 270, in ?
main()
File "/usr/lib/portage/bin/portageq", line 260, in main
import portage
File "/usr/lib/portage/pym/portage.py", line 6786, in ?
portdb=portdbapi(settings["PORTDIR"])
File "/usr/lib/portage/pym/portage.py", line 4779, in __init__
self.auxdbmodule =
self.mysettings.load_best_module("portdbapi.auxdbmodule")
File "/usr/lib/portage/pym/portage.py", line 1287, in load_best_module
return load_mod(best_mod)
File "/usr/lib/portage/pym/portage.py", line 145, in load_mod
mod = __import__(modname)
File "/usr/lib/portage/pym/portage_db_cdb.py", line 17, in ?
import portage_db_template
ImportError: No module named portage_db_template
Traceback (most recent call last):
File "/usr/lib/portage/bin/portageq", line 270, in ?
main()
File "/usr/lib/portage/bin/portageq", line 260, in main
import portage
File "/usr/lib/portage/pym/portage.py", line 6786, in ?
portdb=portdbapi(settings["PORTDIR"])
File "/usr/lib/portage/pym/portage.py", line 4779, in __init__
self.auxdbmodule =
self.mysettings.load_best_module("portdbapi.auxdbmodule")
File "/usr/lib/portage/pym/portage.py", line 1287, in load_best_module
return load_mod(best_mod)
File "/usr/lib/portage/pym/portage.py", line 145, in load_mod
mod = __import__(modname)
File "/usr/lib/portage/pym/portage_db_cdb.py", line 17, in ?
import portage_db_template
ImportError: No module named portage_db_template
Scanning Configuration files...
Exiting: Nothing left to do; exiting. :)
martins
--
Linux 2.6.14-gentoo-r5 AMD Athlon(tm) 64 Processor 3200+
07:42:50 up 1 day, 11:11, 6 users, load average: 1.11, 1.22, 1.25
pgp3x85RdnWL1.pgp
Description: PGP signature
Re: [gentoo-user] Portage broken, can't load module cache_errors
On Sunday 18 December 2005 01:27, Graham Murray wrote: > Bruno Lustosa <[EMAIL PROTECTED]> writes: > > Just synced and tried to update world. > > Portage updated itself, and then died when trying to exec itself. > > I updated from 2.0.53 to 2.1_pre1. The error is: This error has been fixed. I was going to post on the mailing list but found that the fix had made it's way here already. > Luckily I did not get that error but emerge then took 'an eternity' to > calculate the world dependencies before actually building any > packages. I added a message about three hours ago that is displayed after portage is installed noting this. The default cache format has changed so you'll need to run `emerge metadata` to get the local cache back up to date. -- Jason Stubbs -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Portage broken, can't load module cache_errors
Bruno Lustosa <[EMAIL PROTECTED]> writes: > Just synced and tried to update world. > Portage updated itself, and then died when trying to exec itself. > I updated from 2.0.53 to 2.1_pre1. The error is: Luckily I did not get that error but emerge then took 'an eternity' to calculate the world dependencies before actually building any packages. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Portage broken, can't load module cache_errors
On Sat, Dec 17, 2005 at 01:00:59PM +, replica-solutions.de wrote:
> > > Well, can't even run portage now to check things.
> > > I filed bug 115841 on bugzilla. Is anyone here experiencing the same
> > > thing?
> > Yes :(
> > I can't even back out the update, because every major portage command
> > relies on a working python.
> See here : http://replica-solutions.de/board/index.php?topic=34
Ah, thanks!
I better replicate the information for people with the same problem:
(1) cd ~
(2) tar jxf ${DISTDIR}/portage-2.1_pre1.tar.bz2
(3) cp -R portage-2.1_pre1/pym/{cache,elog_modules} /usr/lib/portage/pym
(4) rm -r portage-2.1_pre1
Ciao, Heiko...
--
"Wer zu Hause bleibt, wenn der Kampf beginnt, und läßt andere kämpfen für
seine Sache, der muß sich vorsehen, denn: Wer den Kampf nicht teilt, wird
teilen die Niederlage. Nicht einmal den Kampf vermeidet, wer den Kampf
vermeiden will: Denn er wird kämpfen, für die Sache des Feindes, wer für
seine eigene Sache nicht gekämpft hat."
-- Bertolt Brecht
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Portage broken, can't load module cache_errors
On Saturday 17 December 2005 11:52, Heiko Nock wrote: > On Sat, Dec 17, 2005 at 09:44:19AM -0200, Bruno Lustosa wrote: > > Just synced and tried to update world. > > Portage updated itself, and then died when trying to exec itself. > > I updated from 2.0.53 to 2.1_pre1. The error is: > > > > !!! Failed to complete python imports. There are internal modules for > > !!! python and failure here indicates that you have a problem with python > > !!! itself and thus portage is not able to continue processing. > > > > !!! You might consider starting python with verbose flags to see what has > > !!! gone wrong. Here is the information we got for this exception: > > No module named cache.cache_errors > > Well, can't even run portage now to check things. > > I filed bug 115841 on bugzilla. Is anyone here experiencing the same > > thing? > > Yes :( > > I can't even back out the update, because every major portage command > relies on a working python. > > Ciao, Heiko... > -- See here : http://replica-solutions.de/board/index.php?topic=34 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Portage broken, can't load module cache_errors
On Sat, Dec 17, 2005 at 09:44:19AM -0200, Bruno Lustosa wrote: > Just synced and tried to update world. > Portage updated itself, and then died when trying to exec itself. > I updated from 2.0.53 to 2.1_pre1. The error is: > > !!! Failed to complete python imports. There are internal modules for > !!! python and failure here indicates that you have a problem with python > !!! itself and thus portage is not able to continue processing. > > !!! You might consider starting python with verbose flags to see what has > !!! gone wrong. Here is the information we got for this exception: > No module named cache.cache_errors > Well, can't even run portage now to check things. > I filed bug 115841 on bugzilla. Is anyone here experiencing the same thing? Yes :( I can't even back out the update, because every major portage command relies on a working python. Ciao, Heiko... -- -- gentoo-user@gentoo.org mailing list
[gentoo-user] Portage broken, can't load module cache_errors
Just synced and tried to update world. Portage updated itself, and then died when trying to exec itself. I updated from 2.0.53 to 2.1_pre1. The error is: !!! Failed to complete python imports. There are internal modules for !!! python and failure here indicates that you have a problem with python !!! itself and thus portage is not able to continue processing. !!! You might consider starting python with verbose flags to see what has !!! gone wrong. Here is the information we got for this exception: No module named cache.cache_errors Well, can't even run portage now to check things. I filed bug 115841 on bugzilla. Is anyone here experiencing the same thing? -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Developper | ICQ: 1406477 Rio de Janeiro - Brazil | -- gentoo-user@gentoo.org mailing list
