Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 86352
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 87429
Assigned To: foser (RETIRED) <foser@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jonathan Briggs <zlynx@acm.org>
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 86352 depends on: Show dependency tree
Bug 86352 blocks:
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-03-23 00:28 0000 
dbus-0.23.4 fails to emerge because it can't add messagebus group and user,
which is stupid because that group and user already exist.

I patched it by adding "if ! groupmod messagebus; then" and "if ! id
messagebus; then" before the add commands (stolen from another ebuild).

Reproducible: Always
Steps to Reproduce:
1. emerge sys-apps/dbus-0.23.2-r1
2. emerge sys-apps/dbus-0.23.4

Actual Results:  
Failed to emerge.

Expected Results:  
Successful emerge.

------- Comment #1 From foser (RETIRED) 2005-03-23 08:42:54 0000 ------- 
the function may error, but it shouldn't fail the ebuild. Either the eclass
changed or you have something odd going on locally.

------- Comment #2 From Jonathan Briggs 2005-03-23 09:03:47 0000 ------- 
enewgroup messagebus || die "Problem adding messagebus group"

It could be that "|| die ..." that is screwing it up.

------- Comment #3 From Jonathan Briggs 2005-03-23 09:14:40 0000 ------- 
I just realized that
echo test:more | cut -d: -f1
returns a blank line on my system.  It also fails doing the getent group messagebus | cut ... etc, thing.

I'll have to figure this out.  Sorry, looks like something wrong with my system.  Or something wrong with the cut program.  But since I'm playing with some weird optimization flags and GCC 4, it could easily be a compiler bug.

Close this bug, I guess, unless there's some reason to leave it open.  If it _is_ a bug, it looks like a bug in cut.

------- Comment #4 From Jonathan Briggs 2005-04-04 08:51:33 0000 ------- 

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

------- Comment #5 From Jakub Moc (RETIRED) 2005-05-19 12:00:07 0000 ------- 
*** Bug 93234 has been marked as a duplicate of this bug. ***

------- Comment #6 From Jakub Moc (RETIRED) 2005-05-19 12:01:22 0000 ------- 
Reopening - not related to Bug 87429.

------- Comment #7 From Jonathan Briggs 2005-05-19 12:31:53 0000 ------- 
Yes, this bug was filed by me, and marked duplicate by me when I found the real
problem.  The ebuild was failing because my cut program was broken.  Please
close it again.

------- Comment #8 From Jakub Moc (RETIRED) 2005-05-19 12:44:29 0000 ------- 
(In reply to comment #7)
>  Please close it again.

Why should it be closed when it

------- Comment #9 From Jakub Moc (RETIRED) 2005-05-19 12:44:29 0000 ------- 
(In reply to comment #7)
>  Please close it again.

Why should it be closed when it´s not fixed? See the duplicate Bug 93234 -
coreutils patch does not fix it...

------- Comment #10 From Jonathan Briggs 2005-05-19 12:57:27 0000 ------- 
Okay, but the reason given for reopening this bug is incorrect.  When I
experienced this problem, it *was* coreutils and the cut program causing the
bug.  Fixing cut fixed the dbus ebuild.  This must be a different problem.

------- Comment #11 From foser (RETIRED) 2005-05-19 13:19:47 0000 ------- 
closing this one again

*** This bug has been marked as a duplicate of 87429 ***
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug