First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 238586
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Fernando J. Pereda (RETIRED) <ferdy@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Arfrever Frehtes Taifersar Arahesis <arfrever@gentoo.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 238586 depends on: 221931 223747 Show dependency tree
Bug 238586 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: 2008-09-24 17:19 0000 
dev-util/git with USE="subversion" should require that dev-util/subversion be
built with USE="-dso". Please add appropriate built_with_use check.

See bug #221931 and bug #223747.

------- Comment #1 From Karl Hiramoto 2008-10-08 13:01:36 0000 ------- 
Verifying that this workaround works for me. My system is x86

------- Comment #2 From Leszek Ciesielski 2008-10-11 11:17:14 0000 ------- 
Worked for me, x86 (pentium3 and prescott).

------- Comment #3 From Robin Johnson 2008-10-11 21:57:45 0000 ------- 
Arfrever: I'd actually prefer not to add that check. There are cases when the
actual problem (best described in bug 223747) doesn't occur, because the unload
order is different, due to interactions from prelink.

The upstream bug really does need fixing.

------- Comment #4 From Robert Buchholz 2008-10-12 02:37:36 0000 ------- 
(In reply to comment #3)
> Arfrever: I'd actually prefer not to add that check. There are cases when the
> actual problem (best described in bug 223747) doesn't occur, because the unload
> order is different, due to interactions from prelink.
> 
> The upstream bug really does need fixing.

Upstream has not fixed the bug since they were made aware of it half a year
ago, and has not responded to the lastest mails on the list or the bug report.
The fact that it might work in some cases doesn't mean we should accept the
fact that a feature that merely enhances performance breaks for for others
(with no obvious solution).
I'd vote for a built_with_use check in stable (with an ewarn), and a negative
USE dep in ~arch.

------- Comment #5 From Robin Johnson 2008-11-24 01:17:50 0000 ------- 
Ok, it prints a warning now. I'm avoiding EAPI=[12] for the moment for git,
until we have the 1.6 series in stable.

------- Comment #6 From Robert Buchholz 2009-01-31 10:32:14 0000 ------- 
(In reply to comment #5)
> Ok, it prints a warning now. I'm avoiding EAPI=[12] for the moment for git,
> until we have the 1.6 series in stable.

1.6.0.6 is stable, any chances for this bug now? What's the reason for
hesitation concerning an EAPI bump?

------- Comment #7 From Robin Johnson 2009-03-06 06:55:12 0000 ------- 
In CVS for 1.6.2.
First Last Prev Next    No search results available      Search page      Enter new bug