Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 249646 - PyQt-3.17.4 fails during build
Summary: PyQt-3.17.4 fails during build
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-02 19:43 UTC by James Wall
Modified: 2008-12-03 01:28 UTC (History)
0 users

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

Attachments
emerge --info (system.info,3.36 KB, text/plain)
2008-12-02 19:44 UTC, James Wall 		Details
build logfile (build.log,3.20 KB, text/plain)
2008-12-02 19:45 UTC, James Wall 		Details
environment information (environment,90.48 KB, text/plain)
2008-12-02 19:47 UTC, James Wall 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Wall 2008-12-02 19:43:05 UTC 
I am attempting to install hplip on ~amd64 when PyQt b0rks during configure stage of the build

Reproducible: Always

Steps to Reproduce:
1.emerge hplip 

Actual Results:  
pyQt failed

Expected Results:  
pyqt installed
Comment 1 James Wall 2008-12-02 19:44:00 UTC 
Created attachment 174088 [details]
emerge --info
Comment 2 James Wall 2008-12-02 19:45:10 UTC 
Created attachment 174090 [details]
build logfile
Comment 3 James Wall 2008-12-02 19:47:47 UTC 
Created attachment 174091 [details]
environment information
Comment 4 Patrick Lauer gentoo-dev 2008-12-02 22:07:08 UTC 

*** This bug has been marked as a duplicate of bug 248730 ***
Comment 5 Patrick Lauer gentoo-dev 2008-12-02 22:07:51 UTC 
Aargh. Same symptoms, different package. Not a dupe :)
Comment 6 Patrick Lauer gentoo-dev 2008-12-02 22:42:15 UTC 
Can't reproduce with PyQt-3.17.6. Reopen if you can still trigger it ...
Comment 7 James Wall 2008-12-03 01:28:45 UTC 
(In reply to comment #6)
> Can't reproduce with PyQt-3.17.6. Reopen if you can still trigger it ...
> 

had a bad sync on my local rsync server