Re: Qt3 removal rational
On Wednesday 09 February 2011 01.12:57 Lisandro Damián Nicanor Pérez Meyer wrote: > Of course, we can simply orphan Qt 3, and hope somebody will step up to > maintain it; we are unconvinced this is a responsible step for us to take > as it would place the maintenance burden of a large package onto the QA > team. If qt3 is really popular with scientific apps, which presumably are slow moving targets which are not esaily /quickly ported to qt4, it should be enough motivation for the people who need qt3 to take on the maintenance, so no need to burden the QA team. You need a piece of software, you do the necessary packaging work - it's that simple, at least in theory. cheers -- vbi -- Today is Setting Orange, the 40th day of Chaos in the YOLD 3177 signature.asc Description: This is a digitally signed message part.
Re: Qt3 removal rational
On Tuesday 08 February 2011 08:42:38 Bastien ROUCARIES wrote: > I comaintain upstream qucs a simulator of electronics circuit and the > only free one able to simulate radio frequency circuit. > > In the scientific field a lot of software depend of qt3. And a lot of > uptream lack ressource to port to qt4. At my workplace (university) we > are using a lot this kind of software for in house use. > > We are not ready to scitch to qt4, and I am willing to ask more > explanation about removal of qt lib. [snip] Hi Bastien! As you may know, Qt3 has been dead upstream for more than four years, and thus without any kind of maintenance. Our team's interests in Qt 3 was due to KDE 3, which will be removed now. So, there is no further interest on Qt 3 and people in this team do not want to be upstream of it or do not have the time to do so. Our original idea was to remove Qt 3 from Debian. This will be for us the best decision. Of course, we can simply orphan Qt 3, and hope somebody will step up to maintain it; we are unconvinced this is a responsible step for us to take as it would place the maintenance burden of a large package onto the QA team. Kinds regards, Lisandro, in name of the Qt/KDE team -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#595483: marked as done (kde: KDE4 Crashes system)
Your message dated Tue, 8 Feb 2011 23:36:05 +0200 with message-id <201102082336.12362.mo...@debian.org> and subject line Re: Bug#595483: kde: KDE4 Crashes system has caused the Debian Bug report #595483, regarding kde: KDE4 Crashes system 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 595483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kde Version: KDE4 Severity: critical Justification: breaks the whole system KDE4 invariably crashes the system. This system is running on an AMD Athlon 64 x 2 processer under Debian "Squeeze" and kernel 2.6.32-3-amd64. The same symptoms (only worse) are also observed on a Pentium IV system running 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner or later - usually within an hour or two, the system will crash hard. One then cannot reach the system via telnet, XDMCP, or from the console. Often, it will not even reply to pings. The only option is to hit the power switch. If no KDE session is active, both machines are 100% stable, up continuously for months at a time without issues. If a KDE4 session is active, then after between 30 minutes and 24 hours, the system will crash. No activity is required on the KDE session for the failure to occur, but it seems that changing window foocus often triggers an event. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kde depends on: pn kde-core (no description available) pn kdeaccessibility (no description available) pn kdeaddons (no description available) pn kdeadmin (no description available) pn kdeartwork (no description available) pn kdeedu (no description available) pn kdegames (no description available) pn kdegraphics(no description available) pn kdemultimedia (no description available) pn kdenetwork (no description available) pn kdepim (no description available) pn kdetoys(no description available) pn kdeutils (no description available) pn kdewebdev (no description available) kde recommends no packages. Versions of packages kde suggests: pn kde-i18n (no description available) pn x-window-system-core (no description available) --- End Message --- --- Begin Message --- Hello, On antradienis 08 Vasaris 2011 09:48:21 Leslie Rhorer wrote: > I believe this bug report can be closed. I've upgraded two systems to the > stable release, and both have been up for more than 24 hours without a > failure. One system has been up nearly 3 days. Doing as reporter says -- Modestas Vainius signature.asc Description: This is a digitally signed message part. --- End Message ---
Re: Processed (with 1 errors): Raise severity for KDE3 / Qt3 removal reminder bugs (squeeze has been released)
On Tuesday 08 February 2011 16:12:38 Lisandro Damián Nicanor Pérez Meyer wrote: [snip] > Please, see http://wiki.debian.org/kdelibs4c2aRemoval and > http://wiki.debian.org/qt3-x11-freeRemoval on how we were tracking each of > this issues. s/we were/we are/ :-) -- Evite los parámetros estáticos. Si son inevitables, haga que el emisor y el receptor negocien un valor. Andrew S. Tanenbaum, de su libro "Computer Networks" Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: Processed (with 1 errors): Raise severity for KDE3 / Qt3 removal reminder bugs (squeeze has been released)
On Tuesday 08 February 2011 08:38:04 Julien Cristau wrote: > On Tue, Feb 8, 2011 at 11:29:11 +, Debian Bug Tracking System wrote: > > Processing commands for cont...@bugs.debian.org: > > > severity 604260 serious > > > > Bug #604260 [src:abakus] Preparations for the removal of the KDE3 and Qt3 > > libraries Severity set to 'serious' from 'wishlist' > > [snip tons of others] > > Please revert this. The way to go about something like this is to first > work on getting as many of these off of kde3/qt3. And then when/if > you're close, and there's still time, upgrade the rest to serious and > remove the packages. Not make an insane number of packages > insta-RC-buggy with no prior discussion. > > Cheers, > Julien Hi Julien! Work on that direction has already started some time ago, when Eckhart sent those wishlist mails to the maintainers of the related packages. Please, see http://wiki.debian.org/kdelibs4c2aRemoval and http://wiki.debian.org/qt3-x11-freeRemoval on how we were tracking each of this issues. I hope we will be sending a mail to debian-devel about the qt3 status soon. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: Qt3 removal rational
On Tue, Feb 08, 2011 at 12:42:38PM +0100, Bastien ROUCARIES wrote: > In the scientific field a lot of software depend of qt3. And a lot of Same for kpicosim, but I'm pretty confident that I can run qt3to4 on it and simply link with qt4's qt3 support library. Last time I tried, the whole process was pretty straight forward and took less than 15mins. Just in case you're looking for a quick workaround. HTH -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110208120800.gd15...@ltw.loris.tv
Qt3 removal rational
I comaintain upstream qucs a simulator of electronics circuit and the only free one able to simulate radio frequency circuit. In the scientific field a lot of software depend of qt3. And a lot of uptream lack ressource to port to qt4. At my workplace (university) we are using a lot this kind of software for in house use. We are not ready to scitch to qt4, and I am willing to ask more explanation about removal of qt lib. I have also seen that it exist some projet to package trinity for debian, that could offer an alternative and some delay. What is the status of inclusion under debian? Bastien -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinaogrdzn7wo293nx_npk6suve1ftx-q7gc9...@mail.gmail.com
Re: Processed (with 1 errors): Raise severity for KDE3 / Qt3 removal reminder bugs (squeeze has been released)
On Tue, Feb 8, 2011 at 11:29:11 +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > severity 604260 serious > Bug #604260 [src:abakus] Preparations for the removal of the KDE3 and Qt3 > libraries > Severity set to 'serious' from 'wishlist' > [snip tons of others] Please revert this. The way to go about something like this is to first work on getting as many of these off of kde3/qt3. And then when/if you're close, and there's still time, upgrade the rest to serious and remove the packages. Not make an insane number of packages insta-RC-buggy with no prior discussion. Cheers, Julien signature.asc Description: Digital signature
Bug#609441: [Pkg-alsa-devel] Bug#609441: Here are some important notes from the ALSA team
Hi, here some Testresults for PC2. (There are about 3 PC's with exact this hardware and problems now.) Am 07.02.2011 20:22, schrieb Elimar Riesebieter: Please do a test as follows: logoff from X. Switch to a console via. logon as user. Please test your soundsystem with i.e $ mplayer somesundfile It's not so easy to catch the complete output here. mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. waitpid(): No child processes AO: [pulse] Init failed: Internal error Failed to initialize audio driver 'pulse' [AO_ALSA] alsa-lib: confmisc.c:768:(parse_card) cannot find card '0' [AO_ALSA] alsa-lib: conf.c:4170:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory [AO_ALSA] alsa-lib: confmisc.c:392:(snd_func_concat) error evaluating strings [AO_ALSA] alsa-lib: conf.c:4170:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory [AO_ALSA] alsa-lib: confmisc.c:1251:(snd_func_refer) error evaluating name [AO_ALSA] alsa-lib: conf.c:4170:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory [AO_ALSA] alsa-lib: conf.c:4649:(snd_config_expand) Evaluate error: No such file or directory [AO_ALSA] alsa-lib: pcm.c:2190:(snd_pcm_open_noupdate) Unknown PCM default [AO_ALSA] Playback open error: No such file or directory Failed to initialize audio driver 'alsa' [AO SDL] Unable to open audio: No available audio device Failed to initialize audio driver 'sdl:aalib' Could not open/initialize audio device -> no sound. or $ mocp some soundfile or $ aplay somewavefile.wav You will find the result above in my mail from Sun, 16 Jan 2011 You can tweak your mixer with $ alsaplayer Elimar You can see that Alsa don't play sound even without KDE started. That's the reason this bug is related to ALSA. Regards Karsten -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d510231.8040...@dct.mine.nu
