Bug#368883: qt4-x11: FTBFS on alpha
Hi, Could this be fixed any time soon? qt4-x11 is currently blocking no less than 83 packages. Samuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#368883: qt4-x11: FTBFS on alpha
tag 368883 + pending thanks Le Sam 3 Juin 2006 10:57, Samuel Thibault a écrit : Hi, Could this be fixed any time soon? qt4-x11 is currently blocking no less than 83 packages. Samuel that one is quite annoying. Brian: will you have time to fix that soon (like in less than a couple of days ?) else I'll do an upload just to fix the alpha FTBFS now that there is a patch. If I've no news from you, I suppose I'll do an upload on sunday. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpbUnwxbLBws.pgp Description: PGP signature
Processed: Re: Bug#368883: qt4-x11: FTBFS on alpha
Processing commands for [EMAIL PROTECTED]: tag 368883 + pending Bug#368883: qt4-x11: FTBFS on alpha Tags were: patch Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#368883: qt4-x11: FTBFS on alpha
Pierre Habouzit [EMAIL PROTECTED] writes: tag 368883 + pending thanks Le Sam 3 Juin 2006 10:57, Samuel Thibault a écrit : Hi, Could this be fixed any time soon? qt4-x11 is currently blocking no less than 83 packages. Samuel that one is quite annoying. Brian: will you have time to fix that soon (like in less than a couple of days ?) else I'll do an upload just to fix the alpha FTBFS now that there is a patch. If I've no news from you, I suppose I'll do an upload on sunday. I should be able to do it today (Saturday). If not, go ahead and upload on Sunday. -- Captain Logic is not steering this tugboat.
Bug#238189: marked as done (xbase-clients: [setxkbmap] manpage needs to describe options syntax better)
Your message dated Sat, 3 Jun 2006 16:47:35 +0200 with message-id [EMAIL PROTECTED] and subject line XKB Options Configuration not working ? 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 reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kcontrol Architecture: i386 Version: 4:3.2.1-1 The definition of XKb options are not effective ... For example last option of this menu, for the Caps Lock ... I would like to remove Caps Lock with the Shift key ... but all the options are not working ... It's not clear if it's necessary or not to restart X each time or not ... I have try like this but nothing more ... setxkbmap -option caps:shift seems to do nothing on my system ... not error message, no reaction ... nothing :o( Help needed ... better documentation may be or a package missing but ... need help please about this menu ! Thanks, Regards, -- Bill Footcow ---End Message--- ---BeginMessage--- Le Lundi 15 Mars 2004 21:53, vous avez écrit : Package: kcontrol Architecture: i386 Version: 4:3.2.1-1 The definition of XKb options are not effective ... For example last option of this menu, for the Caps Lock ... I would like to remove Caps Lock with the Shift key ... but all the options are not working ... To achieve this, you have to check reset old options It's not clear if it's necessary or not to restart X each time or not ... I have try like this but nothing more ... no setxkbmap -option caps:shift seems to do nothing on my system ... not error message, no reaction ... nothing :o( setxkbmap -option -option caps:shift ---End Message---
Packaging of NMM?
Good morning Is there any intention to package NMM - Network-Integrated Multimedia Middleware [1] inside the debian-qt-kde team. NMM seems to become one of the default Phonon [2] (KDE Multimedia System) backends in the KDE 4.x era. thx for your great work Mario [1] http://www.networkmultimedia.org [2] http://phonon.kde.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361733: kxkb: layout tab defaults button corrupts keyboard model list
Version: 4:3.5.2-2 Le Lundi 10 Avril 2006 00:14, vous avez écrit : Package: kdebase-bin Version: 4:3.3.2-1sarge1 Severity: normal I shall describe how to reproduce the bug on a new user account (for which kxkb has never been run). If the user has already made kxkb settings, the screen will look different at step (2). But the bug is always there. (1) start Control Centre -- Regional Accessibility -- Keyboard Layout (2) The keyboard layout module opens with the layout tab active. Note that keyboard layouts are not enabled, so most of the tab is greyed out. You can see that the greyed-out defaults are: keyboard model: Generic 104-key PC active layouts: U.S. English (us) [It is debatable whether those are good defaults. It might make more sense to try and get system-wide defaults from /etc/X11/XF86Config-4, That does not worth the trouble... and only fall back to 104-key (us) if nothing there looks sensible. For example, I have the normal settings for a British keyboard: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout gb EndSection so on my system a better default would be Generic 105-key (intl) PC and United Kingdom (gb). Wishlist bug? But let's carry on for now.] (3) click to enable keyboard layouts; the main box becomes active (not greyed-out) (4) click on the drop-down arrow for choosing the keyboard model; on the drop-down menu, click on Generic 105-key (Intl) PC (5) click on defaults in the bottom left; the main box is greyed-out again, but the keyboard model now says pc104. This is already different from the text we saw in step (2). This is a bug. It is not the case anymore with current kxkb. (6) repeat step (3) (7) try to repeat step (4) You will see that the list contains pc104 at the point where it should say Generic 105-key (Intl) PC. This is a bug! It is also now ok.
Bug#361733: marked as done (kxkb: layout tab defaults button corrupts keyboard model list)
Your message dated Sat, 3 Jun 2006 17:43:40 +0200 with message-id [EMAIL PROTECTED] and subject line kxkb bugs not appearing any more 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 reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kdebase-bin Version: 4:3.3.2-1sarge1 Severity: normal I shall describe how to reproduce the bug on a new user account (for which kxkb has never been run). If the user has already made kxkb settings, the screen will look different at step (2). But the bug is always there. (1) start Control Centre -- Regional Accessibility -- Keyboard Layout (2) The keyboard layout module opens with the layout tab active. Note that keyboard layouts are not enabled, so most of the tab is greyed out. You can see that the greyed-out defaults are: keyboard model: Generic 104-key PC active layouts: U.S. English (us) [It is debatable whether those are good defaults. It might make more sense to try and get system-wide defaults from /etc/X11/XF86Config-4, and only fall back to 104-key (us) if nothing there looks sensible. For example, I have the normal settings for a British keyboard: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout gb EndSection so on my system a better default would be Generic 105-key (intl) PC and United Kingdom (gb). Wishlist bug? But let's carry on for now.] (3) click to enable keyboard layouts; the main box becomes active (not greyed-out) (4) click on the drop-down arrow for choosing the keyboard model; on the drop-down menu, click on Generic 105-key (Intl) PC (5) click on defaults in the bottom left; the main box is greyed-out again, but the keyboard model now says pc104. This is already different from the text we saw in step (2). This is a bug. (6) repeat step (3) (7) try to repeat step (4) You will see that the list contains pc104 at the point where it should say Generic 105-key (Intl) PC. This is a bug! There is a workaround for this bug. If keyboard model XX is missing, select instead model YY. Repeat steps (5)-(7). This time model YY is missing, so you can reselect XX. But most users will be confused before they discover the workaround. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kdebase-bin depends on: ii kdelibs4 4:3.3.2-6.4 KDE core libraries ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libfam0c1022.7.0-6sarge1 client library to control the FAM ii libgcc11:3.4.3-13GCC support library ii libice64.3.0.dfsg.1-14sarge1 Inter-Client Exchange library ii libidn11 0.5.13-1.0GNU libidn library, implementation ii libpam-runtime 0.76-22 Runtime support for the PAM librar ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libpng12-0 1.2.8rel-1PNG library - runtime ii libqt3c102-mt 3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14sarge1 X Window System Session Management ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14sarge1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14sarge1 X Window System miscellaneous exte ii libxrender10.8.3-7 X Rendering Extension client libra ii libxtst6 4.3.0.dfsg.1-14sarge1 X Window System event recording an ii xlibs 4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information ---End Message--- ---BeginMessage--- Version: 4:3.5.2-2 Those kxkb bugs have been corrected ---End Message---
Bug#369291: libqt3-mt: xim patch crashes katepart inside kdevelop
On Sunday 28 May 2006 17:50, Andreas Pakulat wrote: recently I reported a crash of kdevelop to it's -devel mailing list (I'm using their svn version) and it was pointed out to me that the reason for the crash is actually a patched Qt3. Thus I'm reporting this here, the link to the bugreport in KDE's bugzilla is: http://bugs.kde.org/show_bug.cgi?id=89278 The backtrace of kdevelop crashing is attached. I tried to change the XIM input method with qtconfig from on the spot to root but it didn't help. I first couldn't reproduce this anymore after playing around a bit, but today it happened again and thus I'm reporting this. The mailing list thread I opened can be read from here: http://lists.kde.org/?l=kdevelop-develm=114878188129406w=2 I'll try to reproduce this with Debian's kdevelop tomorrow. I can't reproduce any crashes here, but I could be simply failing to trigger the right circumstances. Can you confirm that the bug exists using stock Debian packages? Perhaps some more info on how to reproduce it? Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: bug 357136 is forwarded to http://www.trolltech.com/developer/task-tracker/index_html?method=entryid=111573
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 forwarded 357136 http://www.trolltech.com/developer/task-tracker/index_html?method=entryid=111573 Bug#357136: libqt4-dev sould depend on libqt4-debug-dev Noted your statement that Bug has been forwarded to http://www.trolltech.com/developer/task-tracker/index_html?method=entryid=111573. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369291: libqt3-mt: xim patch crashes katepart inside kdevelop
On 03.06.06 13:53:50, Christopher Martin wrote: On Sunday 28 May 2006 17:50, Andreas Pakulat wrote: The backtrace of kdevelop crashing is attached. I tried to change the XIM input method with qtconfig from on the spot to root but it didn't help. I first couldn't reproduce this anymore after playing around a bit, but today it happened again and thus I'm reporting this. The mailing list thread I opened can be read from here: http://lists.kde.org/?l=kdevelop-develm=114878188129406w=2 I'll try to reproduce this with Debian's kdevelop tomorrow. I can't reproduce any crashes here, but I could be simply failing to trigger the right circumstances. Can you confirm that the bug exists using stock Debian packages? Perhaps some more info on how to reproduce it? kdevelop package from debian works. I will try with a rebuilt qt3.3 without xim patches on Monday/Tuesday. Andreas -- You have an ability to sense and know higher truth. pgpaVoeR728as.pgp Description: PGP signature
Bug#369291: libqt3-mt: xim patch crashes katepart inside kdevelop
On Saturday 03 June 2006 14:25, you wrote: On 03.06.06 13:53:50, Christopher Martin wrote: On Sunday 28 May 2006 17:50, Andreas Pakulat wrote: The backtrace of kdevelop crashing is attached. I tried to change the XIM input method with qtconfig from on the spot to root but it didn't help. I first couldn't reproduce this anymore after playing around a bit, but today it happened again and thus I'm reporting this. The mailing list thread I opened can be read from here: http://lists.kde.org/?l=kdevelop-develm=114878188129406w=2 I'll try to reproduce this with Debian's kdevelop tomorrow. I can't reproduce any crashes here, but I could be simply failing to trigger the right circumstances. Can you confirm that the bug exists using stock Debian packages? Perhaps some more info on how to reproduce it? kdevelop package from debian works. I will try with a rebuilt qt3.3 without xim patches on Monday/Tuesday. OK, so if I understand correctly then, Debian isn't really affected by the crashes? We do include a number of XIM fixes in our Qt packages; it's possible we already have the fix. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: not 4.2
Processing commands for [EMAIL PROTECTED]: severity 369113 serious Bug#369113: FTBFS with GCC 4.2: invalid conversion Severity set to `serious' from `normal' retitle 369113 FTBFS: invalid conversion; FT_Vector Bug#369113: FTBFS with GCC 4.2: invalid conversion Changed Bug title. severity 368884 serious Bug#368884: FTBFS with GCC 4.2: invalid conversion Severity set to `serious' from `normal' retitle 368884 FTBFS: invalid conversion; FT_Vector Bug#368884: FTBFS with GCC 4.2: invalid conversion Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of qt4-x11_4.1.3-1_i386.changes
qt4-x11_4.1.3-1_i386.changes uploaded successfully to localhost along with the files: qt4-x11_4.1.3-1.dsc qt4-x11_4.1.3.orig.tar.gz qt4-x11_4.1.3-1.diff.gz qt4-doc_4.1.3-1_all.deb libqt4-dev_4.1.3-1_i386.deb libqt4-debug-dev_4.1.3-1_i386.deb libqt4-core_4.1.3-1_i386.deb libqt4-gui_4.1.3-1_i386.deb libqt4-sql_4.1.3-1_i386.deb libqt4-qt3support_4.1.3-1_i386.deb qt4-designer_4.1.3-1_i386.deb libqt4-debug_4.1.3-1_i386.deb qt4-dev-tools_4.1.3-1_i386.deb qt4-qtconfig_4.1.3-1_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
