When I'd installed -r3 of mailx portage tried to unmerge the old -r2 package. Unfortunately that did not work: tux ~# emerge clean mail-client/mailx selected: 8.1.2.20021129-r2 protected: 8.1.2.20021129-r3 omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging mail-client/mailx-8.1.2.20021129-r2... No package files given... Grabbing a set. /usr/sbin/ebuild.sh: /var/db/pkg/mail-client/mailx-8.1.2.20021129-r2/mailx-8.1.2.20021129-r2.ebuild: line 43: unexpected EOF while looking for matching `"' /usr/sbin/ebuild.sh: /var/db/pkg/mail-client/mailx-8.1.2.20021129-r2/mailx-8.1.2.20021129-r2.ebuild: line 70: syntax error: unexpected end of file !!! ERROR: mail-client/mailx-8.1.2.20021129-r2 failed. !!! Function , Line 1291, Exitcode 1 !!! error sourcing ebuild !!! FAILED prerm: 1 In /var/db/pkg/mail-client I have the following: tux ~# ls -l /var/db/pkg/mail-client/ total 16 -rw-r----- 1 root root 0 Jun 7 15:05 -MERGING-mailx-8.1.2.20021129-r2.portage_lockfile drwxr-xr-x 2 root root 4096 Jun 5 12:49 evolution-1.5.9.1 drwxr-xr-x 2 root root 4096 Jun 7 13:32 mailx-8.1.2.20021129-r2 -rw-r----- 1 root root 0 Jun 7 15:05 mailx-8.1.2.20021129-r2.portage_lockfile drwxr-xr-x 2 root root 4096 Jun 7 07:21 mailx-8.1.2.20021129-r3 drwxr-xr-x 2 root root 4096 Feb 19 20:20 mailx-support-20030215
Same here. I've tried editing the ebuild to fix the EOF errors, but nothing I tried worked.
ok. a simple work-around: just edit the /var/db/pkg/mail-client/mailx-8.1.2.20021129-r2/mailx-8.1.2.20021129-r2.ebuild and add the missing '"' (I think it's directly after the depend-section. but I'm not completely sure, as portage removes this file, once the update is completed.)
Yes, Florian is right. That fixes the problem. :) The question is how to fix this so that it gets pushed out to all the people with a broken ebuild...
There's a script on the other bug that fixes most cases except this one. However, you've just given me an idea on how to fix most of these cases, too. Will add a new script later. *** This bug has been marked as a duplicate of 46096 ***
*** Bug 53398 has been marked as a duplicate of this bug. ***