Typing emerge -1 media-libs/netpbm cause it to fail this way: >>> Emerging (1 of 1) media-libs/netpbm-10.46.00 * netpbm-10.33-manpages.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * netpbm-10.46.00.tar.lzma RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] /var/tmp/portage/media-libs/netpbm-10.46.00/temp/environment: line 2381: syntax error near unexpected token `||' /var/tmp/portage/media-libs/netpbm-10.46.00/temp/environment: line 2381: ` || die' * * ERROR: media-libs/netpbm-10.46.00 failed. * Call stack: * ebuild.sh, line 1776: Called die * The specific snippet of code: * preprocess_ebuild_env || \ * die "error processing environment" * The die message: * error processing environment * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-libs/netpbm-10.46.00/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-libs/netpbm-10.46.00/temp/environment'. * The ||die at line 91 of the ebuild makes it insert a ||die on a line by itself in the environment. I'm using Zsh here if it matters.
Error is in /usr/portage/media-libs/netpbm/netpbm-10.46.00.ebuild, line 158 - there is a or conjunction after the heredoc tag. Fix by removing or commenting out or conjunction: cat config.mk.in /dev/stdin >> config.mk <<-EOF #|| die
*** Bug 282936 has been marked as a duplicate of this bug. ***
Same for the -r1 version, according to the bug I added as a dupe. Reassigning to the graphics maintainers. Also CCed Mike (vapier), as I see he was the last one to touch netpbm to add a sanity check for bug #279549. Guys, we need a working stable version in the tree, stat. Neither the latest stable nor latest ~arch can compile, which is a problem for me in particular as I'm doing a world rebuild for USE="-nls", and the netpbm fail is holding up the show. Thanks. :)
dont cc me on graphics bugs as i'm already in the alias nobody posted their `emerge --info` like the bug reporting page told them to. the code in question works fine on my system. assuming you guys are all stable and thus using bash-3, i imagine it's a difference along those lines.
Created attachment 202471 [details] emerge --info WORKSFORME here, emerge --info attached. Running ~x64 so I'm guessing USE flags or wierd CFLAGS/LDFLAGS? [ebuild R ] media-libs/netpbm-10.46.00-r1 USE="X jpeg jpeg2k png tiff xml zlib -jbig -rle (-svga)" 0 kB
(In reply to comment #1) > Error is in /usr/portage/media-libs/netpbm/netpbm-10.46.00.ebuild, line 158 - > there is a or conjunction after the heredoc tag. > > Fix by removing or commenting out or conjunction: > > cat config.mk.in /dev/stdin >> config.mk <<-EOF #|| die > There's no line 158 in that ebuild. Or, there is, but it's a } and nothing more (last line of ebuild). emerge --sync and retry?
(In reply to comment #6) > There's no line 158 in that ebuild. Or, there is, but it's a } and nothing more > (last line of ebuild). emerge --sync and retry? > 10.46.00 has { at line 158 and 10.46.00-r1 has "doman *.[0-9]". No sign of heredoc tag anywhere.. so the instructions does unfortunately not make sense at the moment :(
(In reply to comment #7) > (In reply to comment #6) > > There's no line 158 in that ebuild. Or, there is, but it's a } and nothing more > > (last line of ebuild). emerge --sync and retry? > > > 10.46.00 has { at line 158 and 10.46.00-r1 has "doman *.[0-9]". > No sign of heredoc tag anywhere.. so the instructions does unfortunately not > make sense at the moment :( > I think he was actually referring to line 91. I did what he proposed but in line 91 and got it working (after calculating new digest of course)
Created attachment 202488 [details] emerge --info
Created attachment 202490 [details] Broken ebuild file that causes netpbm to fail.
Created attachment 202491 [details] Older, but sane, ebuild for exact same version.
(In reply to comment #7) > 10.46.00 has { at line 158 and 10.46.00-r1 has "doman *.[0-9]". > No sign of heredoc tag anywhere.. so the instructions does unfortunately not > make sense at the moment :( Actually - on mine, it does. And having multiple machines has allowed me to find some peculiarities. I have attached the emerge --info from the machine that has the bad ebuild file for netpbm-10.46.00. I just did a new --sync this morning, and the edited one I used yesterday was replaced with the original one that caused the error - which is good, so you can see the error. Transversely, I have other systems - and I have attached the ebuild file for that same exact version - and you can see the error that causes emerge to fail on the newer machine is not there. Here is a short diff to illustrate: diff netpbm-10.46.00.ebuild.broken netpbm-10.46.00.ebuild.sane 3c3 < # $Header: /var/cvsroot/gentoo-x86/media-libs/netpbm/netpbm-10.46.00.ebuild,v 1.9 2009/08/27 10:03:54 vapier Exp $ --- > # $Header: /var/cvsroot/gentoo-x86/media-libs/netpbm/netpbm-10.46.00.ebuild,v 1.7 2009/08/09 12:53:43 nixnut Exp $ 15c15 < KEYWORDS="alpha amd64 arm hppa ~ia64 ~mips ppc ~ppc64 s390 sh ~sparc x86 ~x86-fbsd" --- > KEYWORDS="alpha amd64 ~arm hppa ~ia64 ~mips ppc ~ppc64 ~s390 ~sh ~sparc x86 ~x86-fbsd" 91c91 < cat config.mk.in /dev/stdin >> config.mk <<-EOF || die --- > cat config.mk.in /dev/stdin >> config.mk <<-EOF Yesterday, when I hit this error, I commented out the "||" statement after the heredoc tag "EOF", and then all was good. Now that I see the working ebuild on the older machine, I can see why this just came up yesterday. Does this help the maintainers understand? If you already have netpbm-10.46.00 updated previous to the ebuild put on the repository yesterday (note the CVS date and time for the ebuild that does not work) - then you would never have a problem. I was building a fresh machine yesterday, when this came up, and thus got the bad ebuild and the failure.
netpbm unpacks fine on my stable x86 machine running bash-3.2_p39 maybe bug in stable portage parser
erm, lemme rephrase. it unpacks via `ebuild`, but `emerge` fails. bash-3 does appear to be the problem.
http://sources.gentoo.org/media-libs/netpbm/netpbm-10.46.00.ebuild?r1=1.9&r2=1.10 http://sources.gentoo.org/media-libs/netpbm/netpbm-10.46.00-r1.ebuild?r1=1.2&r2=1.3
