| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
Alan McKinnon wrote: |
| 5 |
| On Sunday 02 March 2008, Chris Walters wrote: |
| 6 |
|> Alan McKinnon wrote: |
| 7 |
| I don't -O3 can ever be considered "standard". Also you say you don't |
| 8 |
| think that's it, then admit -O3 changes the code substantially. I'm |
| 9 |
| having horrible visions that you are taking a shotgun approach to |
| 10 |
| fault-finding |
| 11 |
|
| 12 |
Say again? How am I "taking a shotgun approach to fault-finding"? |
| 13 |
|
| 14 |
|> The problem has to do the the Service Dependencies not being able to |
| 15 |
|> be scanned, and I am advised to run /sbin/depscan.sh |
| 16 |
|> |
| 17 |
|> When I run that, I just get the same error - which also involves a |
| 18 |
|> missing /bin/mktemp file. It seems that that package blocks that |
| 19 |
|> latest version of coreutils... |
| 20 |
| |
| 21 |
| What you wrote doesn't make sense. depscan.sh is installed by baselayout |
| 22 |
| and mktemp is installed by coreutils. You have depscan.sh Which package |
| 23 |
| is blocking which? You don't have to guess which one, portage will tell |
| 24 |
| you when an emerge fails. |
| 25 |
|
| 26 |
Well, apparently either the latest ~amd64 keyword masked version of coreutils |
| 27 |
does not install /bin/mktemp, or makes changes so that /sbin/depscan.sh cannot |
| 28 |
find it, because "/bin/mktemp missing" is a part of the error message, I |
| 29 |
receive. When I mask the latest version of coreutils, and merge the older one |
| 30 |
and the mktemp ebuild, the problem disappears (yes, I was able to get emerge to |
| 31 |
work - finally). |
| 32 |
|
| 33 |
| You really should supply more information so that we can help you. You |
| 34 |
| have now posted 4 times on this thread, and have not supplied any |
| 35 |
| relevant info at all apart from your arch is ~amd64 and you have a |
| 36 |
| problem. So let's do this the right way which involves you supplying |
| 37 |
| the following: |
| 38 |
| |
| 39 |
| - when your system "broke twice", what exactly does this mean? What no |
| 40 |
| longer works, and how does the system's behaviour differ from what you |
| 41 |
| expect? |
| 42 |
| - relevant logs |
| 43 |
| - command(s) run before the problem manifests |
| 44 |
| - console output that demonstrates a problem |
| 45 |
|
| 46 |
I asked for specific and general information in my original message to this |
| 47 |
list. That was what packages had others, using the "ACCEPT_KEYWORDS=~amd64", |
| 48 |
had trouble with. If you have no answer to that question, then you should just |
| 49 |
say so, or not have bothered to reply. I am not liking the attitude on this |
| 50 |
list one bit. I didn't ask you, or anyone else to solve a specific problem for |
| 51 |
me, just a simple general question. If I wanted specific help, I would have |
| 52 |
provided all that you are claiming I should provide. |
| 53 |
|
| 54 |
Chris |
| 55 |
-----BEGIN PGP SIGNATURE----- |
| 56 |
|
| 57 |
iD8DBQFHyv3mUx1jS/ORyCsRChqaAJsHpoz1bA6ry3id6SXVjdTY5YZasACaAsGE |
| 58 |
TVslqDzdm1KxKhJNI3t+xi4= |
| 59 |
=s/VG |
| 60 |
-----END PGP SIGNATURE----- |
| 61 |
-- |
| 62 |
gentoo-user@l.g.o mailing list |
Archives