Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 100523
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Linux Gnome Desktop Team <gnome@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Drake Wyrm <lilwyrm@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 100523 depends on: Show dependency tree
Bug 100523 blocks: 69343
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-07-27 15:19 0000 
While updating gnome-base/eel from 2.10.0 to 2.10.1, I received the following
error during the test phase:

>>> Test phase [enabled]: gnome-base/eel-2.10.1
>>> Test phase [check]: gnome-base/eel-2.10.1
Making check in eel
make[1]: Entering directory `/var/tmp/portage/eel-2.10.1/work/eel-2.10.1/eel'
make  check-TESTS
make[2]: Entering directory `/var/tmp/portage/eel-2.10.1/work/eel-2.10.1/eel'
Could not set mode 0700 on private per-user gnome configuration directory
`/root/.gnome2_private/': Permission denied
FAIL: check-eel
===================
1 of 1 tests failed
===================
make[2]: *** [check-TESTS] Error 1
make[2]: Leaving directory `/var/tmp/portage/eel-2.10.1/work/eel-2.10.1/eel'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory `/var/tmp/portage/eel-2.10.1/work/eel-2.10.1/eel'
make: *** [check-recursive] Error 1

I don't think any of my `emerge --info` info is relevant; let me know if I'm wrong.

------- Comment #1 From Attila Stehr 2005-08-03 10:11:51 0000 ------- 
same here

------- Comment #2 From John N. Laliberte (RETIRED) 2005-08-06 04:43:42 0000 ------- 

*** This bug has been marked as a duplicate of 69343 ***

------- Comment #3 From Drake Wyrm 2005-10-08 10:07:19 0000 ------- 
Please add RESTRICT=test to ebuild if no other solution seems likely.

------- Comment #4 From Jakub Moc (RETIRED) 2006-03-05 08:58:58 0000 ------- 
*** Bug 125094 has been marked as a duplicate of this bug. ***

------- Comment #5 From John N. Laliberte (RETIRED) 2006-03-30 18:34:18 0000 ------- 

*** This bug has been marked as a duplicate of 69343 ***

------- Comment #6 From Jakub Moc (RETIRED) 2006-10-10 11:12:04 0000 ------- 
*** Bug 150707 has been marked as a duplicate of this bug. ***

------- Comment #7 From Jakub Moc (RETIRED) 2007-01-08 23:06:43 0000 ------- 
Reopen.

------- Comment #8 From Gilles Dartiguelongue 2007-06-13 13:53:17 0000 ------- 
Updating title wrt to duplicates

in reply to comment #3, I think the current resolution in gnome herd is to not
hide potential bugs but fix them upstream. We don't always necessary time to
fix test though.

@dang, anything to add ?

------- Comment #9 From Daniel Gryniewicz 2007-06-13 16:33:56 0000 ------- 
Anyone is, of course, free to fix tests.  But we don't have a policy of fixing
them, because we just wouldn't have time.  If bugs get patches, we'll
definitely apply them and push them upstream.

------- Comment #10 From Daniel Gryniewicz 2007-06-13 20:38:52 0000 ------- 
Okay, tests now pass on 2.18.0.1.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug