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