Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 48280 - anjuta-1.2.2 fails compilation
Summary: anjuta-1.2.2 fails compilation
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Lisa Seelye (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on: 46284
Blocks:
  Show dependency tree
 
Reported: 2004-04-18 18:07 UTC by Guy
Modified: 2004-04-20 02:23 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guy 2004-04-18 18:07:54 UTC
See forum thread: http://forums.gentoo.org/viewtopic.php?p=1056744

This may be the same bug as closed bug: http://bugs.gentoo.org/show_bug.cgi?id=46284

Reproducible: Always
Steps to Reproduce:




Work around:

# FEATURES="-sandbox" emerge -uv anjuta
Comment 1 foser (RETIRED) gentoo-dev 2004-04-19 01:58:55 UTC
we don't see forum threads, those seem to be 2 issues btw. please post a full bugreport here.
Comment 2 Guy 2004-04-19 18:04:14 UTC
To try and give you some output to work with, I issued the commands:

# emerge -C anjuta

# emerge -v anjuta

The package unmerged properly.

The package then emerged properly.

I don't know why it works now when it didn't work before. In order to get it to emerge the first time, I had to have FEATURES="-sandbox".

Go figure!

Anyway, since it now works on this machine, please feel free to close.
Comment 3 Lisa Seelye (RETIRED) gentoo-dev 2004-04-19 18:21:20 UTC
I guess this one is invalid since the user can't reproduce it..

reopen if this crops up again
Comment 4 foser (RETIRED) gentoo-dev 2004-04-20 02:23:48 UTC
actually, that is quite likely because with '-sandbox' a file/dir got touched on the live filesystem and now with '+sandbox' it checked if the file/dir existed and didn't try to create it outside of sandbox because of that reason. But this report lacks what file(s) exactly made it trip on sandbox, so there is not much to start with. 

@ reporter : do you stil have the sandbox log in your tmp dir by any chance ?