Bug#342658: libqt4-core: Locking Issue?

2006-01-11 Thread Jeremy Laine
Hi Brian, Does this still happen with Qt 4.1.0? I can no longer reproduce the problem with Qt 4.1.0 on ia64, QFile::open seems to work fine now. I tried both a simple test program and running lrelease on a Qt translation file. From my point of view, the bug is closed. Cheers, Jeremy --

Bug#347400: Request for advice - Re: Bug#347401

2006-01-11 Thread Mike Williams
Steve Langasek wrote: So maintainers, please take the advice given in that mail and fix your packages to a) not use the output of Magick-config --libs when linking, and b) use the Debian version of libtool (if applicable). (One alternative to using Magick-config --libs seems to be to use

Bug#347400: Request for advice - Re: Bug#347401

2006-01-11 Thread Steve Langasek
Hi Mike, On Wed, Jan 11, 2006 at 10:18:20PM +1100, Mike Williams wrote: So maintainers, please take the advice given in that mail and fix your packages to a) not use the output of Magick-config --libs when linking, and b) use the Debian version of libtool (if applicable). (One alternative

Bug#346029: libqt3-mt: Deadkeys don't work with Qt-based applications and cz keyboard

2006-01-11 Thread Marek Schmidt
I think I've found the source of this problem, cs_CZ.UTF-8 is missing in /usr/X11R6/lib/X11/locale/compose.dir I've reported a bug aginst xlibs-data describing this, see bug #347531 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347531 Marek Schmidt -- To UNSUBSCRIBE, email to [EMAIL

Processing of qt4-x11_4.1.0-2_i386.changes

2006-01-11 Thread Archive Administrator
qt4-x11_4.1.0-2_i386.changes uploaded successfully to localhost along with the files: qt4-x11_4.1.0-2.dsc qt4-x11_4.1.0-2.diff.gz qt4-doc_4.1.0-2_all.deb libqt4-dev_4.1.0-2_i386.deb libqt4-debug-dev_4.1.0-2_i386.deb libqt4-core_4.1.0-2_i386.deb libqt4-gui_4.1.0-2_i386.deb

Bug#346551: kstars: problem persists

2006-01-11 Thread sascha
Package: kstars Version: 4:3.5.0-3 Followup-For: Bug #346551 Still no horzizon after upgrade. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel:

Bug#347600: konqueror will not run, hangs

2006-01-11 Thread Kevin Dalley
Package: konqueror Version: 4:3.4.3-3 Severity: grave Justification: renders package unusable After a recent upgrade, konqueror is no longer usable for Internet browsing. If I open the menu item Location-Open Location and enter http://bugs.debian.org;, The Open Location - Konqueror menu stays

Bug#182366: Missing qvfbhdr.h

2006-01-11 Thread Mary Felkin
Hi, Please, I have just upgraded and I still don't have this qvfbhdr.h file, so I can't compile with qt... If this bug really has been fixed, please tell me where I could get this file so I can add it manually to /usr/include/qt3/ Thank you. Mary -- To UNSUBSCRIBE, email to [EMAIL

Bug#182366: Missing qvfbhdr.h

2006-01-11 Thread Adeodato Simó
* Mary Felkin [Wed, 11 Jan 2006 20:52:17 +0100]: Hi, Hi, Please, I have just upgraded and I still don't have this qvfbhdr.h file, so I can't compile with qt... If this bug really has been fixed, please tell me where I could get this file so I can add it manually to /usr/include/qt3/

Processed: tagging 347218

2006-01-11 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.10 # fixed in svn tags 347218 + pending Bug#347218: kdelibs-data: file confilict with libdjvulibre1 There were no tags set. Tags added: pending End of message, stopping processing

Bug#347600: marked as done (konqueror will not run, hangs)

2006-01-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Jan 2006 19:44:57 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#347600: konqueror will not run, hangs has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#182366: Missing qvfbhdr.h

2006-01-11 Thread Adeodato Simó
* Mary Felkin [Wed, 11 Jan 2006 21:09:14 +0100]: And still I don't have it... Then you're probably in a sarge system, correct? Sarge did not include the fix. What should I do, please? I've put you a copy of the file here: http://people.debian.org/~adeodato/tmp/2006-01-11/qvfbhdr.h

Processing of qt4-x11_4.1.0-2_i386.changes

2006-01-11 Thread Archive Administrator
qt4-x11_4.1.0-2_i386.changes uploaded successfully to localhost along with the files: qt4-x11_4.1.0-2.dsc qt4-x11_4.1.0-2.diff.gz qt4-doc_4.1.0-2_all.deb libqt4-dev_4.1.0-2_i386.deb libqt4-debug-dev_4.1.0-2_i386.deb libqt4-core_4.1.0-2_i386.deb libqt4-gui_4.1.0-2_i386.deb

Bug#282487: marked as done (kmail: Buttons have does not apply to encapsulated messages)

2006-01-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Jan 2006 22:36:55 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in new version has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Bug#327359: marked as done (qmake generates invalid -Lpath linker Option)

2006-01-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Jan 2006 14:58:47 -0800 with message-id [EMAIL PROTECTED] and subject line qmake generates invalid -Lpath linker Option has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Processed: foo

2006-01-11 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: close 327359 4.1.0-1 Bug#327359: qmake generates invalid -Lpath linker Option 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 4.1.0-1, send any further explanations to Sven Geggus [EMAIL

Bug#345801: marked as done (main window empty)

2006-01-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Jan 2006 15:06:23 -0800 with message-id [EMAIL PROTECTED] and subject line main window empty has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to