| 1 |
wraeth wrote: |
| 2 |
> On 14/09/15 15:34, Dale wrote: |
| 3 |
> > Well, I'd be chicken to have two packages dealing with /dev at the |
| 4 |
> > same time, although portage says it is not a blocker. |
| 5 |
> |
| 6 |
> > For future reference, I went and dug in this path: |
| 7 |
> |
| 8 |
> > /var/db/pkg/sys-fs |
| 9 |
> |
| 10 |
> > It turned out it was just a empty directory and deleting it cleared |
| 11 |
> > it up. Since it was empty, I guess that was safe enough. If |
| 12 |
> > anything was in it, then I'd be wanting to make sure it was safe to |
| 13 |
> > remove first. |
| 14 |
> |
| 15 |
> > So, it's fixed. I get a clean eix run and if its happy, I'm happy. |
| 16 |
> > ;-) |
| 17 |
> |
| 18 |
> Granted I don't know your setup, but having nothing installed from |
| 19 |
> sys-fs/* seems a little odd to me. For example, I have the following |
| 20 |
> packages installed from the sys-fs category: |
| 21 |
> |
| 22 |
> eix -cI\#C sys-fs |
| 23 |
> sys-fs/btrfs-progs |
| 24 |
> sys-fs/cryptsetup |
| 25 |
> sys-fs/e2fsprogs |
| 26 |
> sys-fs/fuse |
| 27 |
> sys-fs/lvm2 |
| 28 |
> sys-fs/ntfs3g |
| 29 |
> sys-fs/udev |
| 30 |
> sys-fs/udev-init-scripts |
| 31 |
> sys-fs/udisks |
| 32 |
> |
| 33 |
> Accordingly, I have the following in /var/db/pkg/sys-fs/ |
| 34 |
> |
| 35 |
> ls -lhn /var/db/pkg/sys-fs |
| 36 |
> total 0 |
| 37 |
> drwxr-xr-x 1 0 0 534 2015-09-14 09:51 btrfs-progs-4.2 |
| 38 |
> drwxr-xr-x 1 0 0 520 2015-09-10 11:14 cryptsetup-1.6.8 |
| 39 |
> drwxr-xr-x 1 0 0 494 2015-09-10 12:56 e2fsprogs-1.42.13 |
| 40 |
> drwxr-xr-x 1 0 0 494 2015-09-10 18:29 fuse-2.9.4 |
| 41 |
> drwxr-xr-x 1 0 0 526 2015-09-10 21:41 lvm2-2.02.116 |
| 42 |
> drwxr-xr-x 1 0 0 520 2015-09-10 11:13 ntfs3g-2015.3.14 |
| 43 |
> drwxr-xr-x 1 0 0 538 2015-09-10 22:21 udev-225 |
| 44 |
> drwxr-xr-x 1 0 0 464 2015-09-10 19:02 udev-init-scripts-30 |
| 45 |
> drwxr-xr-x 1 0 0 512 2015-09-11 03:26 udisks-2.1.6 |
| 46 |
> |
| 47 |
> If you legitimately don't have anything installed from the sys-fs |
| 48 |
> category, then all should be safe I guess; but if you do, then other |
| 49 |
> mysteries may be afoot... |
| 50 |
> |
| 51 |
|
| 52 |
|
| 53 |
I have this: |
| 54 |
|
| 55 |
root@fireball / # equery list sys-fs/* |
| 56 |
* Searching for * in sys-fs ... |
| 57 |
[IP-] [ ] sys-fs/dfc-3.0.5-r1:0 |
| 58 |
[IP-] [ ] sys-fs/dosfstools-3.0.28:0 |
| 59 |
[IP-] [ ] sys-fs/e2fsprogs-1.42.13:0 |
| 60 |
[IP-] [ ] sys-fs/eudev-3.1.2-r10:0 |
| 61 |
[IP-] [ ] sys-fs/fuse-2.9.4:0 |
| 62 |
[IP-] [ ] sys-fs/lvm2-2.02.110:0 |
| 63 |
[IP-] [ ] sys-fs/mdadm-3.3.1-r2:0 |
| 64 |
[IP-] [ ] sys-fs/mtools-4.0.15:0 |
| 65 |
[IP-] [ ] sys-fs/ntfs3g-2014.2.15-r1:0 |
| 66 |
[IP-] [ ] sys-fs/reiser4progs-1.0.9:0 |
| 67 |
[IP-] [ ] sys-fs/reiserfsprogs-3.6.24:0 |
| 68 |
[IP-] [ ] sys-fs/shake-0.999:0 |
| 69 |
[IP-] [ ] sys-fs/treesize-0.54.1:0 |
| 70 |
[IP-] [ ] sys-fs/udev-init-scripts-27:0 |
| 71 |
[IP-] [ ] sys-fs/udisks-2.1.4:2 |
| 72 |
root@fireball / # |
| 73 |
|
| 74 |
I use eudev to manage /dev. Since I know I already have software to |
| 75 |
manage that, I didn't want to emerge that failed one since it could |
| 76 |
clash with what I already have installed. That said, portage didn't |
| 77 |
show it as a blocker or anything. I likely could have emerged it, then |
| 78 |
unmerged it and not cause a problem. I was just to chicken to do it is |
| 79 |
all. |
| 80 |
|
| 81 |
In my search, I was searching for static-dev so it would only show |
| 82 |
matches to that and not the other packages in sys-fs. If I had searched |
| 83 |
for sys-fs/* then it would have shown what was installed in that category. |
| 84 |
|
| 85 |
The biggest thing, I just didn't want to screw something up and google |
| 86 |
wasn't returning anything when I searched. No clue why it didn't tho. |
| 87 |
It's rare that google shows no matches. It usually finds something even |
| 88 |
if it is off the mark a bit. |
| 89 |
|
| 90 |
Dale |
| 91 |
|
| 92 |
:-) :-) |
Archives