Bug#495722: Uninstallable Qt-4.4.1 packages in experimental?

2008-09-08 Thread Nathan Scott
On Mon, 2008-09-08 at 08:51 +0200, Sune Vuorela wrote: On Monday 08 September 2008 02:30:21 Nathan Scott wrote: On Sat, 2008-09-06 at 10:55 +0200, Ana Guerrero wrote: No, since this is not targeted for lenny, we are not plannign currently upload it to unstable. Hmmm... but its

Bug#495722: Uninstallable Qt-4.4.1 packages in experimental?

2008-09-07 Thread Nathan Scott
On Sat, 2008-09-06 at 10:55 +0200, Ana Guerrero wrote: No, since this is not targeted for lenny, we are not plannign currently upload it to unstable. Hmmm... but its a bugfix release isnt it? Moving from 4.3 to 4.4 introduced several regressions in just my one app, I'd expect others have

Bug#495722: Uninstallable Qt-4.4.1 packages in experimental?

2008-08-19 Thread Nathan Scott
Package: qt4-x11 Version: 4.4.1-1 Severity: serious I'm trying to install the 4.4.1 packages from experimental, to see if 483790 is really resolved for my app, and I'm struggling - it kinda, sorta, maybe looks like a packaging botch in libqtcore4 vs libqtgui4? Below is what I see from dpkg...

Bug#483790: QTreeView/QTreeWidgetItemIterator bugs

2008-07-31 Thread Nathan Scott
Hi guys, Any idea when 4.4.1 is planned? This seems to be taking a looong time. Any way we could get a patch for this issue included in the meantime, if it looks like it will be still awhile? thanks! -- Nathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.

Bug#477112: libqt4: QTreeView dumps core

2008-04-20 Thread Nathan Scott
Subject: libqt4: QTreeView dumps core Package: libqt4-gui Version: 4.4.0~rc1-4 Severity: normal Hi, I've started to see problems in my QT4 app using the QTreeView widget, since recently upgrading (I believe I upgraded from an earlier 4.4 to the current unstable version - 4.4.0-rc1-4). This

Bug#477112: libqt4: QTreeView dumps core

2008-04-20 Thread Nathan Scott
On Mon, 2008-04-21 at 03:03 +0200, Sune Vuorela wrote: Hi! THanks for your report. It would be nice if you had a minimal test case we could use to reproduce the problem (and forward upstream) Unfortunately this area of my app code is fairly convoluted and not a great test case.