!!! povuni_s.tgz: message digests do not match! !!! povuni_s.tgz is corrupt or incomplete. >>> our recorded digest: bac59e7a86172a5bd0c63af2516e7045 >>> your file's digest: 4df1711c15d39ee6265ada8ceff78f52 >>> Please delete /usr/portage/distfiles/povuni_s.tgz and refetch. ...deleted and refetched ... then same message, so # ebuild povray-3.50c.ebuild digest >>> Generating digest file... >>> Computed message digests. [23:32 root@penguin: /usr/portage/media-gfx/povray] # emerge povray Calculating dependencies ...done! >>> emerge (1 of 1) media-gfx/povray-3.50c to / >>> md5 ;-) povuni_s.tgz >>> Unpacking source... >>> Unpacking povuni_s.tgz to /var/tmp/portage/povray-3.50c/work >>> Source unpacked. !!! ERROR: media-gfx/povray-3.50c failed. !!! Function econf, Line 275, Exitcode 1 !!! no configure script found
Hi, I just cleared out my distfiles and /var/tmp/portage folders, and after fetching the povray archive again, the correct digest is in fact: bac59e7a86172a5bd0c63af2516e7045 Can you manually download the file in the SRC_URI into your distfiles directory and see if this helps?
I did the same thing yesterday. The Gentoo mirrors still carry the old povuni_s.tgz file (which contains povray-3.50a) and AFAIK only www.povray.org has the latest "right" version for which the md5sum digest is correct. I have written a request for the POV-Ray developers on the news.povray.org server to change the naming of the source tarball into a versioning scheme, and others has done the same as well. This would make things much easier.
OK, that did it. BTW, the SRC_URI="ftp://ftp.povray.org/pub/povray/Official/Unix/povuni_s.tgz" is a symlink to ftp://ftp.povray.org/pub/povray/Official/Linux/povuni_s.tgz
In the future, would it be possible to change the name of the tarballs on the Gentoo mirrors to reflect the version being used, and have some other means of downloading/renaming/verifying the povuni_s.tgz file from www.povray.org? The POV team seem reluctant to changing the naming scheme at this time.
any chance this could be masked out in portage? it'll break "emerge -u world" for most people without manual intervention... either that, or have the updated povuni_s.tgz on the mirrors?
I'm confirming malverian's bug. Same exact problem.
I've mirrored the new povray tarball with the rest of the gentoo mirrors, could take some time to propagate, but hopefully this will resolve any problems.
*** Bug 18303 has been marked as a duplicate of this bug. ***
The UK mirror service now has http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/distfiles/povuni_s_3.1.tgz but portage wants: http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/distfiles/povuni_s.tgz so it's still broken.
Also, it seems that it is not calculating dependancies correctly for my gentoo 1.2 machine (w/gcc 2.95.3)...I've got 3.50a installed, and it claims to want to update to 3.50c despite it requiring gcc 3.2 for that... bash-2.05b# emerge -u povray (also happens with emerge -u world) .... 13:25:07 (2.75 MB/s) - `/usr/portage/distfiles/povuni_s.tgz' saved [6602380] >>> md5 ;-) povuni_s.tgz * This build needs gcc-3.2 or later !!! ERROR: media-gfx/povray-3.50c failed. !!! Function pkg_setup, Line 28, Exitcode 0 !!! (no error message)
emerge can't just upgrade to gcc 3.x wanna do so ? please read http://www.gentoo.org/doc/en/new-upgrade-to-gentoo-1.4.xml
I think all issues with this package have been dealt with, if anyone still has problems, feel free to reopen.
I still think this ebuild should have correct dependancy checking for which version of gcc someone has installed. Here's how (I think) it should work: If user has gcc 2.95.3 (GENTOO 1.2), then emerge -u world should NOT show this povray-3.50c because it absolutely needs gcc 3.2...this causes ALL emerge -u world commands to fail if the user already has 3.50a installed If user has gcc 3.2 (GENTOO 1.4), then emerge -u world should show 3.50c as latest available. Upgrading to 1.4 is not always possible...I'm not asking for someone to make povray work on a 2.95.3 machine, just to make the ebuild work as it should. Can't reopen bug b/c I'm not owner, but I would like to..
gentoo-1.2 is fixed through portage.mask
