First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 188303
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Qt Bug Alias <qt@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
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 188303 depends on: 200630 Show dependency tree
Bug 188303 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: 2007-08-10 08:21 0000
After upgrading to dev-python/sip-4.7 upgrading to dev-python/PyQt-3.17.2
fails:
### sip/qt/qdir.sip:47:28: error: sipqtQFileInfo.h: No such file or directory


Reproducible: Always

Steps to Reproduce:
1. try to emerge "=dev-python/PyQt-3.17.2" after dev-python/sip-4.7 has been
installed.
2.
3.

------- Comment #1 From Jakub Moc (RETIRED) 2007-08-10 09:37:05 0000 -------
*** Bug 188310 has been marked as a duplicate of this bug. ***

------- Comment #2 From Kévin 2007-08-10 15:32:21 0000 -------
Same problem here

------- Comment #3 From Caleb Tennis 2007-08-11 20:40:13 0000 -------
looks like there a 3.17.3 that should fix this.  Look for it in portage in a
little bit, and try again with that version.

------- Comment #4 From Jakub Moc (RETIRED) 2007-08-20 05:30:41 0000 -------
*** Bug 189548 has been marked as a duplicate of this bug. ***

------- Comment #5 From Rora 2007-08-20 14:20:47 0000 -------
(In reply to comment #3)
> looks like there a 3.17.3 that should fix this.  Look for it in portage in a
> little bit, and try again with that version.
> 

3.17.3 isn't in my dev-python portage folder.

# eix -l PyQt
* dev-python/PyQt
     Available versions:
                        3.14.1-r1 [debug doc examples]
                        3.14.1-r2 [debug doc examples]
                        3.17 [debug doc examples]
                (~)     3.17.2 [debug doc examples]
     Homepage:            http://www.riverbankcomputing.co.uk/pyqt/
     Description:         PyQt is a set of Python bindings for the Qt toolkit.

* dev-python/PyQt4
     Available versions:
                (~)     4.2 [debug doc examples]
                (~)     4.3 [debug doc examples]
     Homepage:            http://www.riverbankcomputing.co.uk/pyqt/
     Description:         PyQt is a set of Python bindings for the Qt toolkit.

------- Comment #6 From Caleb Tennis 2007-08-20 14:50:04 0000 -------
Did you resync?  It's been there since the 11th of august.

------- Comment #7 From Rora 2007-08-20 23:33:22 0000 -------
(In reply to comment #6)
> Did you resync?  It's been there since the 11th of august.
> 

How do I do that?

------- Comment #8 From Caleb Tennis 2007-08-21 20:43:44 0000 -------
emerge sync?  how do you normally sync portage?

------- Comment #9 From Steve Arnold 2007-09-17 00:23:12 0000 -------
Although my "fresh" sync today was done last night by my local server, it
appears dev-python/sip-4.7 is stabled for amd64, yet dev-python/PyQt-3.17.3 is
not.  This would be the source of the problem, since with neither one in
package.keywords, you get the latest sip but only PyQt-3.17 so it breaks during
a large update or other rebuild (such as running python-updater, which is what
I just did).  You might want to fix that...

------- Comment #10 From Steve Arnold 2007-09-22 17:22:45 0000 -------
This could have been avoided by having PyQt-3.17.2 and older versions DEPEND on
the older version of sip.  Also because of the above, you have to coordinate
and stable both of them at the same time (ie, PyQt-3.17.3 and sip-4.7).

These are pretty much the only bugs open on PyQt, so it seems time to stable
PyQt-3.17.3 on amd64, since sip-4.7 is already stable on amd64 (done).  When
you stable other arch's for sip-4.7, you'll need to stable the same arch's for
PyQt-3.17.3 at the same time to avoid similar breakage.

You can fix this bug and several others by straightening out the sip DEPENDS in
the older PyQt ebuilds as noted, to separate versions prior to the above from
the most recent one.

------- Comment #11 From Roland Ramthun 2007-11-18 11:49:20 0000 -------
(In reply to comment #10)
> This could have been avoided by having PyQt-3.17.2 and older versions DEPEND on
> the older version of sip.  Also because of the above, you have to coordinate
> and stable both of them at the same time (ie, PyQt-3.17.3 and sip-4.7).
> 
> These are pretty much the only bugs open on PyQt, so it seems time to stable
> PyQt-3.17.3 on amd64, since sip-4.7 is already stable on amd64 (done).  When
> you stable other arch's for sip-4.7, you'll need to stable the same arch's for
> PyQt-3.17.3 at the same time to avoid similar breakage.

PyQT-3.17 is up to now marked as stable on X86, too, which doesn't work with
stable sip-4.7.1 for weeks.

Please stabilize version PyQT-3.17.3 of PyQT for X86, too.

------- Comment #12 From moesasji 2007-11-27 15:55:29 0000 -------
Could this bug get some attention as on x86 it is still not possible to build
pyqt-3.17 as it does not build with sip-4.7.1. The solution appears to have
been given two months ago??

As both PyQt-3.17 and Sip-4.7.1 are marked as stable on x86 (I think) this is
breakage that should not occur. (especially if it is known that this doesn't
work)

------- Comment #13 From Roland Tapken 2007-11-28 12:43:48 0000 -------
Please stabalize 3.17.3 because you cannot emerge amarok (and other tools that
use PyQt) on a "stable" system at the moment.

------- Comment #14 From Caleb Tennis 2007-11-28 12:54:20 0000 -------
I've requested stablization of PyQt-3.17.3 and sip-4.7.1 in bug 200630.

------- Comment #15 From Ingmar Vanhassel (RETIRED) 2008-03-09 20:56:29 0000 -------
(In reply to comment #14)
> I've requested stablization of PyQt-3.17.3 and sip-4.7.1 in bug 200630.
> 
Fixed now, so closing this bug too. :) (thanks Philantrop!)

First Last Prev Next    No search results available      Search page      Enter new bug