| 1 |
OK, I think I narrowed down the cause a bit. I am getting this msg |
| 2 |
during hal installation, and before it fails: |
| 3 |
|
| 4 |
>>> /etc/conf.d/hald |
| 5 |
--- /sbin/ |
| 6 |
>>> /sbin/umount.hal |
| 7 |
--- /lib/ |
| 8 |
--- /lib/udev/ |
| 9 |
>>> /lib/udev/hal_unmount |
| 10 |
--- /media/ |
| 11 |
!!! copy |
| 12 |
/var/tmp/portage/sys-apps/hal-0.5.11-r8/image/media/.keep_sys-apps_hal-0 |
| 13 |
-> /media/.keep_sys-apps_hal-0 failed |
| 14 |
. |
| 15 |
!!! [Errno 2] No such file or directory: '/media/.keep_sys-apps_hal-0#new' |
| 16 |
|
| 17 |
>>> Failed to install sys-apps/hal-0.5.11-r8, Log file: |
| 18 |
|
| 19 |
>>> '/var/tmp/portage/sys-apps/hal-0.5.11-r8/temp/build.log' |
| 20 |
|
| 21 |
* Messages for package sys-apps/hal-0.5.11-r8: |
| 22 |
|
| 23 |
* This package will overwrite one or more files that may belong to other |
| 24 |
* packages (see list below). You can use a command such as `portageq |
| 25 |
* owners / <filename>` to identify the installed package that owns a |
| 26 |
* file. If portageq reports that only one package owns a file then do |
| 27 |
* NOT file a bug report. A bug report is only useful if it identifies at |
| 28 |
* least two or more packages that are known to install the same file(s). |
| 29 |
* If a collision occurs and you can not explain where the file came from |
| 30 |
* then you should simply ignore the collision since there is not enough |
| 31 |
* information to determine if a real problem exists. Please do NOT file |
| 32 |
* a bug report at http://bugs.gentoo.org unless you report exactly which |
| 33 |
* two packages install the same file(s). Once again, please do NOT file |
| 34 |
* a bug report unless you have completely understood the above message. |
| 35 |
* |
| 36 |
|
| 37 |
|
| 38 |
Trying to create a file manually under /media is failing, even as a root |
| 39 |
I don't have permission to write to that folder! Which is really strange. |
| 40 |
|
| 41 |
$ ls -l / |
| 42 |
total 127196 |
| 43 |
drwxr-xr-x 2 root root 4096 Apr 25 18:39 bin |
| 44 |
drwxr-xr-x 3 root root 4096 Apr 26 00:32 boot |
| 45 |
drwxr-xr-x 13 root root 14160 Apr 28 04:16 dev |
| 46 |
drwxr-xr-x 83 root root 4096 Apr 28 13:29 etc |
| 47 |
drwxr-xr-x 4 root root 4096 Apr 18 12:38 home |
| 48 |
lrwxrwxrwx 1 root root 6 Dec 6 16:37 lib -> lib64/ |
| 49 |
drwxr-xr-x 4 root root 4096 Dec 6 16:37 lib.backup |
| 50 |
drwxr-xr-x 10 root root 4096 Apr 25 18:44 lib64 |
| 51 |
drwx------ 2 root root 4096 Nov 13 19:03 lost+found |
| 52 |
drwxr-xr-x 2 root root 0 Apr 28 04:15 media |
| 53 |
drwxr-xr-x 6 root root 0 Apr 28 13:36 mnt |
| 54 |
drwxr-xr-x 20 root root 4096 Apr 27 18:54 opt |
| 55 |
dr-xr-xr-x 108 root root 0 Apr 28 04:15 proc |
| 56 |
drwx------ 34 root root 4096 Apr 28 13:35 root |
| 57 |
drwxr-xr-x 2 root root 4096 Apr 28 13:32 sbin |
| 58 |
-rw-r--r-- 1 root root 130053783 Nov 13 16:44 stage3-amd64-2008.0.tar.bz2 |
| 59 |
drwxr-xr-x 12 root root 0 Apr 28 04:15 sys |
| 60 |
drwxrwxrwt 6 root root 4096 Apr 28 13:40 tmp |
| 61 |
drwxr-xr-x 19 root root 4096 Apr 20 19:08 usr |
| 62 |
drwxr-xr-x 14 root root 4096 Dec 1 20:41 var |
| 63 |
|
| 64 |
I will keep on looking, in the mean while if anyone has an idea, please |
| 65 |
let me know. |
| 66 |
|
| 67 |
Thanks |
| 68 |
|
| 69 |
|
| 70 |
Drake Donahue wrote: |
| 71 |
> On Tue, 2009-04-28 at 12:52 -0300, Mansour Al Akeel wrote: |
| 72 |
>> I have been trying to install hal, but no luck. Everytime, I end up |
| 73 |
>> getting an error, and couldn't find enough information to resolve the issue: |
| 74 |
>> |
| 75 |
>> >>> Installing sys-apps/hal-0.5.11-r8 |
| 76 |
>> * checking 171 files for package collisions |
| 77 |
>> * This package will overwrite one or more files that may belong to other |
| 78 |
>> * packages (see list below). You can use a command such as `portageq |
| 79 |
>> * owners / <filename>` to identify the installed package that owns a |
| 80 |
>> * file. |
| 81 |
> |
| 82 |
> What does running |
| 83 |
> portageq owners / /usr/lib64/libhal.so.1.0.0 |
| 84 |
> tell you? |
| 85 |
> |
| 86 |
>> If portageq reports that only one package owns a file then do |
| 87 |
>> * NOT file a bug report. A bug report is only useful if it identifies at |
| 88 |
>> * least two or more packages that are known to install the same file(s). |
| 89 |
>> * If a collision occurs and you can not explain where the file came from |
| 90 |
>> * then you should simply ignore the collision since there is not enough |
| 91 |
>> * information to determine if a real problem exists. Please do NOT file |
| 92 |
>> * a bug report at http://bugs.gentoo.org unless you report exactly which |
| 93 |
>> * two packages install the same file(s). Once again, please do NOT file |
| 94 |
>> * a bug report unless you have completely understood the above message. |
| 95 |
>> * |
| 96 |
>> * Detected file collision(s): |
| 97 |
>> * |
| 98 |
>> * /usr/lib64/libhal.so.1.0.0 |
| 99 |
>> * /usr/lib64/libhal.la |
| 100 |
>> * /usr/lib64/libhal.a |
| 101 |
>> * /usr/lib64/libhal-storage.so.1.0.0 |
| 102 |
>> * /usr/lib64/libhal-storage.la |
| 103 |
>> * /usr/lib64/libhal-storage.a |
| 104 |
>> * /usr/lib64/hal/scripts/hal-luks-setup |
| 105 |
>> * /usr/lib64/hal/scripts/hal-luks-teardown |
| 106 |
>> |
| 107 |
>> ..... |
| 108 |
>> |
| 109 |
>> |
| 110 |
>> * /usr/lib64/hal/scripts/linux/hal-system-wol-supported-linux |
| 111 |
>> * |
| 112 |
>> * Searching all installed packages for file collisions... |
| 113 |
>> * |
| 114 |
>> * Press Ctrl-C to Stop |
| 115 |
>> * |
| 116 |
>> * None of the installed packages claim the file(s). |
| 117 |
>> * |
| 118 |
>> * Package 'sys-apps/hal-0.5.11-r8' merged despite file collisions. If |
| 119 |
>> * necessary, refer to your elog messages for the whole content of the |
| 120 |
>> * above message. |
| 121 |
>> |
| 122 |
>> |
| 123 |
>> Hal is still not installed. It doesn't show under /var/db/pkg/sys-apps/ |
| 124 |
>> |
| 125 |
>> Any one got in the same situation ? |
| 126 |
>> |
| 127 |
>> |
| 128 |
> |
| 129 |
> |
Archives