Bug 64386 – Portage give strange "mylines" errors

• Product: Portage Development
• Status: RESOLVED INVALID

[Description Richard Torkar 2004-09-17 04:56:04 UTC]

I recently installed portage-2.0.51_rc1 and now a strange behaviour has popped up. I might add that this behaviour was showing itself previously as well but on a different place.

As seen here when I use portage in anyway the first two lines I get is a "mylines" error. With older portage thhose two lines only popped up at the end of an "emerge unmerge package". Now they always show up, even when I try to use emerge in a simple way such as the below.

tux ~ # emerge -p portage
mylines: ['MD5', 'fc0df31ef4ad90b83ee133929afbcc83', 'id3ed-1.10.4.tar.gz', '31610']
list index out of range
mylines: ['MD5', 'fc0df31ef4ad90b83ee133929afbcc83', 'id3ed-1.10.4.tar.gz', '31610']
list index out of range

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-apps/portage-2.0.51_rc1

The mylines error started with an older version of portage, but since it only showed up in the end of an unmerge I never put any thought into it. At that time, as well as now, the behaviour and functionality of portage is normal otherwise. This leads to me setting the Severity to "minor".

Any ideas what might be wrong here? I've done a "fixpackages" and "revdep-rebuild".

[Comment 1 Nicholas Jones (RETIRED) 2004-09-17 08:43:33 UTC]

fgrep -r fc0df31ef4ad90b83ee133929afbcc83 /var/db/pkg

If that shows up for a PROVIDE or a USE file, then you've
got a rather weird case of corruption. Post any of the USE
or PROVIDE files your get in that grep, please.

[Comment 2 Richard Torkar 2004-09-20 06:40:18 UTC]

Something weird was definitely going on. Now the latest glibc update b0rked my system anyway so I can't get the info you wanted :( Closing the bug...