Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 303459 - stable qscintilla-2.4 qscintilla-python-2.4 can't be emerged due to missing qt4 flag
Summary: stable qscintilla-2.4 qscintilla-python-2.4 can't be emerged due to missing q...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-04 15:15 UTC by Dmitri Pogosian
Modified: 2010-02-04 22:10 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitri Pogosian 2010-02-04 15:15:05 UTC
When I emerge stable qscintilla-python-2.4 it fails due to missing qt4 flag

$ USE='qt4' emerge -pv qscintilla-python

These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds built with USE flags to satisfy "~dev-python/qscintilla-python-2.4[qt4]".
!!! One of the following packages is required to complete your request:
- dev-python/qscintilla-python-2.4 (Missing IUSE: qt4)
(dependency required by "x11-libs/qscintilla-2.4" [ebuild])
(dependency required by "dev-python/qscintilla-python-2.4" [ebuild])
(dependency required by "qscintilla-python" [argument])

However, after some recent upgrada qscintilla-python does not have 'qt4' flag anymore !  (so even explicit USE='qt4' as in example above does not help'

This, of course, blocks all other emerges.



Reproducible: Always

Steps to Reproduce:
1.USE='qt4' emerge qscintilla-python
2.
3.

Actual Results:  
fails requiring qt4 USE flag which does not exist.

Expected Results:  
emerge completed
Comment 1 Rafał Mużyło 2010-02-04 17:52:59 UTC
x11-libs/qscintilla depends on just dev-python/qscintilla-python,
no useflag dep there, at least not in the portage tree.

Any (broken) overlays ?
Comment 2 Dmitri Pogosian 2010-02-04 18:41:10 UTC
(In reply to comment #1)
> x11-libs/qscintilla depends on just dev-python/qscintilla-python,
> no useflag dep there, at least not in the portage tree.
> 
> Any (broken) overlays ?
> 

No, I am runnig very close to 100% stable system. The only local overlays are

polarbear ~ # layman -l
* kde-sunset                [Git       ] (git://git.o.g.o/proj/kde-sunset.git  )
* lightscribe               [Subversion] (http://mars.arge.at/svn/linamh/tru...)

but I don't have any packages installed from them.

The only unstable packages are
polarbear ~ # cat /etc/portage/package.keywords
app-dicts/ispell-ru     ~amd64
app-text/pdftk          ~amd64
media-libs/libgphoto2   ~amd64
media-gfx/gphoto2       ~amd64
www-client/chromium     ~amd64
dev-libs/libevent       ~amd64
mail-client/mozilla-thunderbird ~amd64
dev-util/d-feet         ~amd64
media-video/ffmpeg      ~amd64
net-wireless/blueman    ~amd64
net-im/skype            ~amd64


The sequence of events was the following

1. I had qscintilla-2.4 and qscintilla-pyton-2.4 installed and not complaining
2. I run 'emerge --reinstall changed-use' for another reason and it recompiled qscintilla-python-2.4 because it got (-%qt4)  new flag use.
3. After that all emerges give that error about qt4 USE flag.
4. I have unmerged both qscintilla-2.4 and qscintilla-pyton-2.4, but cannot emerge it back.
5. If I go to unstable ~amd64,  it pulls qscintilla-2.4.2-r1 and qscintilla-python-2.4.2-r1 which do not complain about USE flags, but also unstable PyQT4 and sip, and I prefer not to go unstable for no reason.



Comment 3 Rafał Mużyło 2010-02-04 20:49:49 UTC
Frankly, I was expecting kde-sunset.
And that you don't have any packages from that overlay installed
doesn't matter, it's enough to have it.

To fix it, you'll need to either remove that overlay
or do some creative editing in your personal overlay,
so it overrides kde-sunset.

You may try to get in touch with people running that overlay,
but they really can't fix it (yes, there are reasons).

In official tree, there's no KDE3 and shortly there won't be even
qt:3, so don't expect any fix here.
Comment 4 Dmitri Pogosian 2010-02-04 22:10:07 UTC
Yes, deleting kde-sunset solves the issue