| Summary: | Portage 2.1.2_rc3-r6 fails with invalid atom: '>=media-sound/madplay\x01.14.2b-r1' | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Sascha Wuestemann <bigfoot> |
| Component: | Core - Dependencies | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | VERIFIED CANTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sascha Wuestemann
2007-01-02 00:11:19 UTC
Run `grep -Rni \>=media-sound/madplay /var/db/pkg` and fix it; we can't fix locally malformed VDB entries... (I reopened the bug, because I believe that additional comments at closed bugs arren't read. If this assumption is wrong, please tell me.) Ah, I see, I didn't know I have to look there, too: /var/db/pkg/media-sound/normalize-0.7.6/RDEPEND and /var/db/pkg/media-video/avifile-0.7.38.20030710/avifile-0.7.38.20030710.ebuild contain a non ascci character which appears as "^A" at vim and should be "-0", I assume. I can't imagine, how this has happened. My system is up for 60 days, memory is fine, no partition had run full and no other strange error had occured. Do you have a clue? I fixed both errors at the files and ran an 'emerge portage' with another error, now: # emerge portage Calculating dependencies | Error occurred while processing sys-kernel/xfs-sources-2.4.20-r2 "Conditional without parenthesis: 'tcltk?'" which is exactly this: /var/db/pkg/sys-kernel/xfs-sources-2.4.20-r2/RDEPEND:5: tcltk? dev-lang/tk grepping "tcltk? dev-lang" gives 4 hits, fixed at: /var/db/pkg/sys-kernel/xfs-sources-2.4.20_pre6/RDEPEND /var/db/pkg/sys-kernel/vanilla-sources-2.4.20/RDEPEND /var/db/pkg/sys-kernel/xfs-sources-2.4.20-r2/RDEPEND /var/db/pkg/sys-kernel/xfs-sources-2.4.20-r3/RDEPEND to "tcltk? ( dev-lang/tk ) Now emerge portage gives this error: Error occurred while processing net-misc/mknbi-1.4.0 "invalid atom: '>=perl-5.6.1'" I found /var/db/pkg/net-misc/mknbi-1.4.0/DEPEND:1:>=perl-5.6.1 /var/db/pkg/net-misc/mknbi-1.4.0/RDEPEND:1:>=perl-5.6.1 /var/db/pkg/net-misc/mknbi-1.4.0/mknbi-1.4.0.ebuild:13:DEPEND=">=perl-5.6.1 and now I am stuck because I don't know how to fix that. On the other hand, what if this error correction has no end? What about and how to rebuild all the files at /var/db/pkg instead? Please, stop reopening this bug. As already said, we can't fix your local cruft in VDB. Fix the broken atoms there, and then upgrade to latest portage version. Ok, understood. So there is no way to rebuild all the files at /var/db/pkg, right? And you can't give any reasons how that happened, I assume? Is there a readme how to fix the files at /var/db/pkg? (In reply to comment #4) > Is there a readme how to fix the files at /var/db/pkg? Open them in $EDITOR and fix the wrong dependency atoms portage is complaining about. |
