Active Topics
-
Phone Camera Competition April 2021: "Funny & Foolish" (33)
to General by Fellfrosch - 1 hr, 54 mins ago -
What's the best Handheld gnu/linux machine for 20XX? (78)
to Competitors by clort - 6 hrs, 40 mins ago -
Unofficial Storage for camera phone competition... (62)
to General by catbus - 15 hrs, 1 min ago -
Maemo-Leste pre-alpha announcement (512)
to Maemo 7 / Leste by nonsuch - 1 day, 16 hrs ago -
The Intel RealSense Smartphone prototype (0)
to Competitors by n950 - 1 day, 18 hrs ago -
Maemo Leste Playground (57)
to Maemo 7 / Leste by clort - 2 days, 15 hrs ago -
A Palm OS thread ... and a thank you to the community (23)
to Alternatives by bradvesp - 3 days, 15 hrs ago -
SailfishOS on Sony Z3 Compact Tablet (180)
to SailfishOS by ogustbiller - 6 days, 19 hrs ago - more...
|
2010-02-10
, 08:47
|
|
Posts: 242 |
Thanked: 97 times |
Joined on Sep 2009
|
#12
|
Originally Posted by fatalsaint
when i write that, i get following:
if you disabled both and updated.. just try doing:
apt-get install python2.5-qt4-gui
Or there is a python2.5-qt4 something (-docs?) that shows up in package manager that you can install.
The following packages have unmet dependencies:
python2.5-qt4-gui: Depends: python2.5-qt4-core (= 4.7-maemo2) but 4.7-maemo5 is to be installed
E: Broken packages
i have extras testing enabled and did the apt-get update as well.
|
|
2010-02-10
, 08:50
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#13
|
People, please, stand down, there is an issue with the repositories (the issue is not PyQt specific, just affected by it). I will report back when everything is sorted out. Until then, you're only risking getting yourself in an unupdateable state.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
| The Following 2 Users Say Thank You to attila77 For This Useful Post: | ||
|
|
2010-02-11
, 00:31
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#14
|
Originally Posted by attila77
I did what now?
Okay, plot unfolding, versioning mixup is a result of fatalsaint apparently triggering a logic flaw in the promotion system
Working on the issue.
 |
|
2010-02-11
, 00:32
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#15
|
well, it had to be someone... 
__________________
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
|
|
2010-02-11
, 00:40
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#16
|
Originally Posted by SubCore
O I C! I'm the FALL guy!!!!
well, it had to be someone...
Ya'all better watch it.... I know where you ..... Forum!
|
|
2010-02-11
, 00:43
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#17
|
i'm sure there's a karma point in it for you 
__________________
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
| The Following User Says Thank You to SubCore For This Useful Post: | ||
|
|
2010-02-11
, 01:02
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#18
|
Originally Posted by fatalsaint
Not your fault really, you just triggered it... Promoted a package (pianobar ?) to testing while PyQt itself was in testing. Now, things set as they were, this meant you promoted a NEWER version of PyQt into testing, so when the time came for ME to promote to Extras from testing, I was not promoting the package I originally submitted, but the newer, Qt4.6 ready version your package brought along. Still with me ? 'Cause the plot is about to thicken - as your package depends on just a few of the PyQt modules, we actually ended up with a mix of versions, some packages being available as -maemo5 and some as -maemo3. Nobody's fault really except for the procedure itself, I've been cuckooing about potential race conditions for a while now, it's just that this time around we broke quite a few things in the process
I did what now?
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
| The Following 3 Users Say Thank You to attila77 For This Useful Post: | ||
|
|
2010-02-11
, 01:10
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#19
|
Originally Posted by attila77
That's... awesome!
Not your fault really, you just triggered it... Promoted a package (pianobar ?) to testing while PyQt itself was in testing. Now, things set as they were, this meant you promoted a NEWER version of PyQt into testing, so when the time came for ME to promote to Extras from testing, I was not promoting the package I originally submitted, but the newer, Qt4.6 ready version your package brought along. Still with me ? 'Cause the plot is about to thicken - as your package depends on just a few of the PyQt modules, we actually ended up with a mix of versions, some packages being available as -maemo5 and some as -maemo3. Nobody's fault really except for the procedure itself, I've been cuckooing about potential race conditions for a while now, it's just that this time around we broke quite a few things in the process
. Everything breaks around me!! 
It would have had to have been pyPianobar, that's the one that depends on pyQt.. and it only depends on:
python2.5-qt4-gui, python2.5-qt4-webkit, python2.5-qt4-network
Which in turn depend on a few more.. but yeah - that's pretty interesting.
It's truly surprising to me though that by promoting *mine*.. it somehow dragged yours along with it?
I am guessing that assumption is - if a package is promoted it is assumed that all packages it depends on are good to go as well? Also, when a package receives 10 votes in testing and then promoted, is it also assumed again that all packages it depends on must also be good to go - since the user package was obviously tested by 10 people to get the votes?
I had an idea that dependency hell was going to cause a problem with this system a while back.. wondering how a package was supposed to move forward if it's dependencies were left behind... but this is very interesting.
|
|
2010-02-11
, 02:50
|
|
Posts: 113 |
Thanked: 44 times |
Joined on Feb 2010
|
#20
|
This might be related to a problem I started having tonight. I went to reinstall pyPianobar and it's telling me python2.5-qt4-core (= 4.7-maemo4) is missing. I just downloaded pyPianobar the other day and it worked fine.
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc