Summary: | emerge fileutils fails to install /usr/bin/install | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ole Tange <bugs.gentoo.org> |
Component: | Current packages | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bugs.gentoo.org, kevin, mholzer |
Priority: | High | ||
Version: | 1.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
output from emerge xcdroast
output from emerge fileutils |
Description
Ole Tange
2002-08-21 09:09:15 UTC
Created attachment 3259 [details]
output from emerge xcdroast
ls -la /usr/bin/install
lrwxrwxrwx 1 root root 17 Jun 11 14:37 /usr/bin/install -
> ../../bin/install
this command is in the fileutils
which version of fileutils do you use ?
4.1.8-r2 has this sym-link in it
/usr/bin/install -> ../../bin/install
# epm -q fileutils fileutils-4.1.8-r2 Which version would you like me to try? Oh by the way: it is not a symlink: # ls -l /usr/bin/install -rwxr-xr-x 1 root root 43292 aug 31 2001 /usr/bin/install* Sorry. Wrong machine. Here is the correct. $ ls -l /usr/bin/install ls: /usr/bin/install: No such file or directory $ ls -l /bin/install -rwxr-xr-x 1 root root 47444 08-21 10:27 /bin/install try emerge fileutils (same version) and watch for the symb link. create an attachment if it doesn't create the symb link. Created attachment 3303 [details] output from emerge fileutils /usr/bin/install is still not there. Wierd because the following line is there: >>> /usr/bin/install -> ../../bin/install If I set the link manually then emerge xcdroast completes. There is a minor error: chown: failed to get attributes of `/var/tmp/portage/xcdroast-0.98_alpha10-r2/image//usr/bin/xcdrgtk': No such file or directory but it does not seem to hurt. I have just tried qpkg -c sys-apps/fileutils -vv and it fails. So fileutils registers /usr/bin/install as installed but does not do it. I would say this is not a xcdroast bug but a fileutils bug. Can I change the bug to a fileutils bug or should I just close this bug and submit a new? simply change it is the best i think emerge fileutils works giving the attached output. But qpkg run immediately after emerge gives: # qpkg -c -v fileutils sys-apps/fileutils-4.1.8-r2 * /usr/bin/dd !not exist! /usr/bin/cp !not exist! /usr/bin/df !not exist! /usr/bin/du !not exist! /usr/bin/ln !not exist! /usr/bin/ls !not exist! /usr/bin/mv !not exist! /usr/bin/rm !not exist! /usr/bin/dir !not exist! /usr/bin/sync !not exist! /usr/bin/vdir !not exist! /usr/bin/chgrp !not exist! /usr/bin/chmod !not exist! /usr/bin/chown !not exist! /usr/bin/mkdir !not exist! /usr/bin/mknod !not exist! /usr/bin/rmdir !not exist! /usr/bin/shred !not exist! /usr/bin/touch !not exist! /usr/bin/mkfifo !not exist! /usr/bin/dircolors !not exist! /usr/bin/install !not exist! 22/154 Bug 6983 seems to be related to this: # emerge /usr/portage/packages/sys-apps/fileutils-4.1.8-r2.tbz2 ... >>> /usr/bin/install -> ../../bin/install ... <<< sym /usr/bin/install It seems emerge installs the link allright, but then uninstalls the link. Precisely the same behaviour as bug 6983. A workaround is to execute the following commands: 563 ln -s /bin/cp . 564 ln -s /bin/df . 565 ln -s /bin/du . 566 ln -s /bin/ln . 567 ln -s /bin/ls . 568 ln -s /bin/mv . 569 ln -s /bin/rm . 570 ln -s /bin/dir . 571 ln -s /bin/sync . 572 ln -s /bin/vdir . 573 ln -s /bin/chgrp . 574 ln -s /bin/chmod . 575 ln -s /bin/chown . 576 ln -s /bin/mkdir . 577 ln -s /bin/mknod . 578 ln -s /bin/rmdir . 579 ln -s /bin/shred . 580 ln -s /bin/touch . 581 ln -s /bin/mkfifo . 582 ln -s /bin/dircolors . 583 ln -s /bin/install . 584 ln -s /bin/dd . This will make 'qpkg -v -c' happy. The important question that you have not yet answered: what version of Portage are you using? I can't replicate this with 2.0.30_alpha # emerge --version Portage 2.0.28 I have just tried 2.0.30_alpha. Same problem: <<< sym /usr/bin/shred removes the symlink that is created earlier. How can I see why it is doing the <<< sym /usr/bin/shred ? *** This bug has been marked as a duplicate of 6983 *** OK, I seem to remember that in a previous bug report you said that your /usr was a symlink? Is this true? If so, that is important information that is probably required for replicating and fixing this bug. Right now, I cannot replicate this bug so I need more detailed information about your system and how you configured it. This goes for the many other bugs that you filed too. |