1 |
I am having a same issue with mailx. It fails upon unmerge: |
2 |
|
3 |
|
4 |
|
5 |
mail-client/mailx |
6 |
selected: 8.1.2.20021129-r2 8.1.2.20021129-r4 |
7 |
protected: none |
8 |
omitted: none |
9 |
|
10 |
>>> 'Selected' packages are slated for removal. |
11 |
>>> 'Protected' and 'omitted' packages will not be removed. |
12 |
|
13 |
>>> Waiting 5 seconds before starting... |
14 |
>>> (Control-C to abort)... |
15 |
>>> Unmerging in: 5 4 3 2 1 |
16 |
>>> Unmerging mail-client/mailx-8.1.2.20021129-r2... |
17 |
No package files given... Grabbing a set. |
18 |
|
19 |
QA Notice: ECLASS 'ccc' inherited illegally in |
20 |
mail-client/mailx-8.1.2.20021129-r2 |
21 |
|
22 |
|
23 |
QA Notice: ECLASS 'flag-o-matic' inherited illegally in |
24 |
mail-client/mailx-8.1.2.20021129-r2 |
25 |
|
26 |
|
27 |
QA Notice: ECLASS 'eutils' inherited illegally in |
28 |
mail-client/mailx-8.1.2.20021129-r2 |
29 |
|
30 |
|
31 |
QA Notice: ECLASS 'toolchain-funcs' inherited illegally in |
32 |
mail-client/mailx-8.1.2.20021129-r2 |
33 |
|
34 |
/usr/lib/portage/bin/ebuild.sh: |
35 |
/var/db/pkg/mail-client/mailx-8.1.2.20021129-r2/mailx-8.1.2.20021129-r2.e= |
36 |
build: |
37 |
line 43: unexpected EOF while looking for matching `"' |
38 |
/usr/lib/portage/bin/ebuild.sh: |
39 |
/var/db/pkg/mail-client/mailx-8.1.2.20021129-r2/mailx-8.1.2.20021129-r2.e= |
40 |
build: |
41 |
line 70: syntax error: unexpected end of file |
42 |
|
43 |
!!! ERROR: mail-client/mailx-8.1.2.20021129-r2 failed. |
44 |
!!! Function , Line 1560, Exitcode 1 |
45 |
!!! error sourcing ebuild |
46 |
!!! If you need support, post the topmost build error, NOT this status |
47 |
message. |
48 |
|
49 |
!!! FAILED prerm: 1 |
50 |
|
51 |
|
52 |
maybe a portage problem? I've done numerous 'emerge sync's, but to no ava= |
53 |
il. |
54 |
|
55 |
|
56 |
|
57 |
|
58 |
|
59 |
> I updated to a newer version of the Shorewall firewall. The install went |
60 |
> fine. But when portage was cleaning up it failed to remove the old |
61 |
> version. It was an older version of Shorewall that had already been |
62 |
> removed from portage. |
63 |
> |
64 |
> This is from emerge.log |
65 |
> |
66 |
> 1097088830: === (1 of 1) Cleaning |
67 |
> (sys-apps/man-1.5m-r2::/usr/portage/sys-apps/man/man-1.5m-r2.ebuild) |
68 |
> 1097088832: === (1 of 1) Compiling/Merging |
69 |
> (sys-apps/man-1.5m-r2::/usr/portage/sys-apps/man/man-1.5m-r2.ebuild) |
70 |
> 1097088882: === (1 of 1) Post-Build Cleaning |
71 |
> (sys-apps/man-1.5m-r2::/usr/portage/sys-apps/man/man-1.5m-r2.ebuild) |
72 |
> 1097088883: >>> AUTOCLEAN: sys-apps/man |
73 |
> 1097088888: === Unmerging... (sys-apps/man-1.5m-r1) |
74 |
> 1097088891: >>> unmerge success: sys-apps/man-1.5m-r1 |
75 |
> 1097088892: ::: completed emerge (1 of 1) sys-apps/man-1.5m-r2 to / |
76 |
> 1097088892: *** Finished. Cleaning up... |
77 |
> 1097088901: === Unmerging... (net-firewall/shorewall-1.4.7c) |
78 |
> 1097088902: *** terminating. |
79 |
> |
80 |
> When I run emerge --update now it will install new packages, but always |
81 |
> dies when it tries to remove shorewall. How can I clean this up? |
82 |
> |
83 |
> --Karl |
84 |
> |
85 |
> |