On 08/31/11 20:26, Burcin Erocal wrote:
> On Wed, 31 Aug 2011 20:52:30 +0200
> Fabian Groffen <email@example.com> wrote:
>> On 31-08-2011 15:09:45 +0200, Burcin Erocal wrote:
>>>> Aha. That explains. Now I understand why the fix fixes it as
>>>> well. I'll apply it ASAP. Thanks a lot!
>>> A better fix might be to replace the + at the end of line 163 with
>>> . This way the parser concatenates the strings and we don't
>>> introduce an extra operation.
>> Since I'm a Python n00b, please tell me if
>> http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commitdiff;h=5551d449dffe531935dcd67 2f37c5cd3abd55a44;hp=3b74444f6684d7696e549cbdb76b8 d1a0795fe2d
>> is supposedly what you meant it to be.
> Exactly. Next time I'll provide a patch instead of trying to describe
> it in words.
Just emerged portage 2.2.01.19120 and this fix doesn't seem to have
Traceback (most recent call last):
File "/usr/bin/emerge", line 44, in <module>
retval = emerge_main()
File "/j/usr/lib/portage/pym/_emerge/main.py", line 1909, in emerge_main
trees, mtimedb, retval)
File "/j/usr/lib/portage/pym/_emerge/main.py", line 370, in post_emerge
infodirs, info_mtimes, retval)
File "/j/usr/lib/portage/pym/_emerge/main.py", line 164, in
"--dir-file=%s/dir %s/%s" % (_unicode_decode(EPREFIX), inforoot,
TypeError: not all arguments converted during string formatting