1 |
On 2 Sep 2008, at 17:56, Mick wrote: |
2 |
>> ... |
3 |
>> WARN: postinst |
4 |
>> Broken symlink for a certificate at //etc/ssl/certs/SPI_CA_2006- |
5 |
>> cacert.pem |
6 |
>> ... |
7 |
>> $ ls -l /etc/ssl/certs/SPI_CA_2006-cacert.pem |
8 |
>> lrwxrwxrwx 1 root root 61 Aug 30 03:37 /etc/ssl/certs/SPI_CA_2006- |
9 |
>> cacert.pem -> /usr/share/ca-certificates/spi-inc.org/SPI_CA_2006- |
10 |
>> cacert.crt |
11 |
>> $ |
12 |
> |
13 |
> I assume that the above links are shown as red (or whatever) |
14 |
> indicating that |
15 |
> the links are borked? |
16 |
|
17 |
Yes, indeed. |
18 |
|
19 |
> I believe that it is left as an exercise for the reader to manually |
20 |
> remove |
21 |
> such broken lists as your WARN message tells you: |
22 |
> |
23 |
>> WARN: postinst |
24 |
>> Broken symlink for a certificate at //etc/ssl/certs/SPI_CA_2006- |
25 |
>> cacert.pem |
26 |
>> Broken symlink for a certificate at |
27 |
> [snip...] |
28 |
>> You MUST remove the above broken symlinks" |
29 |
> |
30 |
|
31 |
I kinda feel this is a poor error message for Portage / an ebuild. |
32 |
|
33 |
I have now already deleted the links manually, but I rather think |
34 |
it'd've been nearer to say "You should now run `find /etc/ssl/certs/ - |
35 |
type broken-symlinks -exec rm \{} \;` as root. |
36 |
|
37 |
The reason I posted was because I felt slightly unclear. |
38 |
|
39 |
Stroller. |