I got an incorrect filesize error for the latest version of xcmiscproto (i synced again to make sure, and it's still a digest problem). Obviously it was fixed easily by `ebuild /path/to/ebuild digest`, but it should be dealt with in the ebuild. Thanks.
I'm going to mark this as invalid. Turns out it's happening with a lot of packages and I'm going to assume I've cocked up somewhere or other because I can't see how it can be a problem with so many packages (unless it's a problem with the new portage). Apologies for the waste of time.
No, you're right, it's messed. Portage version?
Oh, and which other files are messed up? I'd like to fix them.
I didn't keep a record of all of them, but most of them were X files IIRC (I run an unstable system, so that's modular X). How it happened... I lost my system a couple of weeks ago to a power failure, but i managed to back up my portage directory (i built binary packages of everything). I restored as many binary packages as I could, then portage upgraded itself and I got on with compiling the remaining packages listed in my worldfile. I decided to change my LDFLAGS so I emerge -e'd everything, where I ran into this problem. I had to get a list of packages to merge, so i wrote a perl one liner to tidy up the output of `emerge -e world`. I then passed portage that list of files to merge. What I assumed had happened is that i had messed up somewhere along the line, since TAR is also reporting errors about invalid archives, despite them matching the checksums after having been downloaded. I have a list of these if anyone wants them, however, the critical one is binutils... The version would be the latest version of portage available in portage, but I can't get the output because i've already started on my new gentoo from scratch. Thanks
Alright. I'll close this bug for now, but if you come across any X packages that you're sure are broken please re-open (or file a new bug - I'm happy either way).
I'm reopening as requested for another broken X package. The digests are correct this time, but the depencies are not. x11-apps/xkbcomp-1.0.2 fails during configure because the perl XML::Parser module is not installed. I've since installed this myself and now it appears to compile fine, but the dependency should be added to the ebuild. Thanks
You probably should have opened a bug for this issue, since it's unrelated ;) xkbcomp itself doesn't need XML-Parser, but one of its dependencies must. I just re-installed X over the weekend without this issue. It might be a USE-flag thing.
I think xkeyboard-config uses it.
It failed during the configure for xkbcomp, so I had assumed that it was directly related to this package. Why would the configure script check dependencies of dependencies?
It shouldn't. If you ever reproduce it, I'd appreciate the config.log.
I'm fine about reproing it, i'll just unmerge the perl and reemerge the package. Where can I get the config.log?
It will be in your Portage tmp directory, so normally: /var/tmp/portage/<package>/work/<internal package name+ver>/ I believe. It should say after failure.
