Re: Final polishing of the KDE 3.3 transition
On Sun, Jan 02, 2005 at 08:32:20PM +0100, Adeodato Simó wrote: > The gcc-3.4/libunwind transition having happened on Dec 31st, KDE 3.3 > is mostly ready to enter sarge. In this mail, I will make a summary of > the last issues that need to be addressed: > (a) #266478, the dummy bug "new kdelibs should not enter testing > alone", should be closed now. If some RM mails to -done, that > would be nice. (But see (d) below - I have not already closed > it since I wanted some feedback first.) This bug is now closed. > (c) Unless some RM objects, the latest security bugs won't get fixed > before the transition, and uploads to address them will be done > shortly after the transition with urgency=high. > I talked to Andreas about this too, and he agreed to it since > all the vulnerabilities are present in the current sarge > packages as well. I agree that the impact of the KDE blockage is sufficient that we shouldn't be holding KDE out of testing for bugs that aren't specific to unstable. > We now request for instructions about how to proceed so that the > affected bugs are not included in the RC bug count. One of: > 1. those security bugs will have to be temporarily > downgraded > 2. the only other way is to use force hints, and > using force hints would override the safety we were trying > to put in place. > 3. you could set a temporary sarge-ignore tag? > 4. or temporaly leave all of them as +sarge only, right? > (but: I think I prefer to lie about the severity > rather than lie about the tags; Kamion may have a different > opinion as a bugmaster.) This preference isn't strong enough that I would want it to hold anything up; all the options are kludges, so we might as well pick one and get on with things. > (d) Given the number of packges that are stalled by kdelibs [1] and > not covered by this transition (i.e., not in the hands of the > KDE packagers), I expressed two concerns back in November [last > section of 2]. > [1] http://bjorn.haxx.se/debian/testing.pl?waiting=kdelibs > [2]http://lists.debian.org/debian-release/2004/11/msg00154.html > As for the second concern, I'm only mildly drawing some > attention from RMs to it: kdelibs entering sarge will mean a > bunch of packages with *big* differences migrating, so I always > thought that the Release Team would prefer these migrations to > happen smoothly, and semi-controlled (plus what I say in the > mail), and the only scheme I could came up with was the mass > bug-filing. This is not really a major concern; if there are RC bugs that haven't been detected yet, there's no sense in sitting around waiting for them to be filed. If you have specific issues in mind that you suspect may be RC, it would be best to investigate them before the affected packages reach testing, of course. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#266478: marked as done (new kdelibs should not enter testing alone)
Your message dated Sun, 2 Jan 2005 18:07:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line new kdelibs should not enter testing alone 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) -- Received: (at submit) by bugs.debian.org; 17 Aug 2004 22:52:27 + >From [EMAIL PROTECTED] Tue Aug 17 15:52:27 2004 Return-path: <[EMAIL PROTECTED]> Received: from mail-out.m-online.net [212.18.0.9] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BxCod-0005oa-00; Tue, 17 Aug 2004 15:52:27 -0700 Received: from mail.m-online.net (svr14.m-online.net [192.168.3.144]) by svr8.m-online.net (Postfix) with ESMTP id 0F5DF62AEF for <[EMAIL PROTECTED]>; Wed, 18 Aug 2004 00:52:26 +0200 (CEST) Received: from sol.so.argh.org (ppp-62-245-208-19.mnet-online.de [62.245.208.19]) by mail.m-online.net (Postfix) with ESMTP id ECE8EFF1D0 for <[EMAIL PROTECTED]>; Wed, 18 Aug 2004 00:52:25 +0200 (CEST) Received: from aba by sol.so.argh.org with local (Exim 4.22 #1 (Debian) [+prerelease]) id 1BxCoa-0007my-UJ for <[EMAIL PROTECTED]>; Wed, 18 Aug 2004 00:52:24 +0200 Date: Wed, 18 Aug 2004 00:52:24 +0200 From: Andreas Barth <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: KDE 3.3 is not released by upstream, and unfit for sarge Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Editor: Vim http://www.vim.org/ Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_20,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kdelibs Version: 4:3.3.0-1 Tags: sid Severity: serious Hi, kdelibs 3.3 is not fit for inclusion into sarge. Reason: Will cause a lot of breakage, and a heavy delay in the release plan. Also, 3.3 is not released till now by upstream, but only betas are available. Actually, this upload should never have happened. Cheers, Andi See http://lists.debian.org/debian-release/2004/08/msg00222.html: | As some of you probably already know, a number of packages from KDE 3.3 | have been uploaded today to unstable. This upload of a major new | upstream release was not discussed with the release team prior to | upload; actually, it's caused quite a bit of consternation and generally | made for a crappy day on account of the impact on the libtiff freeze. | | The problems for libtiff have, however, been sorted at this point. | Consequently, this note is to let maintainers of KDE packages know that | the release team does not plan to delay the freeze for KDE3.3. After | discussing with Ben Burton, it is clear that allowing only part of KDE | 3.3 into sarge so close to the freeze is likely to lead to new bugs, and | that any attempt to get all of KDE3.3 into sarge at this point would | unacceptably delay the release schedule. -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C --- Received: (at 266478-done) by bugs.debian.org; 3 Jan 2005 02:07:13 + >From [EMAIL PROTECTED] Sun Jan 02 18:07:13 2005 Return-path: <[EMAIL PROTECTED]> Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1ClHcn-0003ui-00; Sun, 02 Jan 2005 18:07:13 -0800 Received: by localhost.localdomain (Postfix, from userid 1000) id 7A5681720C5; Sun, 2 Jan 2005 18:07:10 -0800 (PST) Date: Sun, 2 Jan 2005 18:07:10 -0800 From: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: new kdelibs should not enter testing alone Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable The current kdeli
Bug#286690: Reproduced
Hi, I just reproduced the bug. Both with korganizer and kontact, so it must be a problem on the common KPart they share for the calendar function. How to reproduce it: 1) Create a new 'contact' resource on an LDAP source (from kcontrol, kaddressbook, etc) if you don't have one. 2) Create a random event on korganizer if you don't have one. Then, close korganizer. 3) Launch korganizer and double click on the event. It crashes. If you remove the LDAP contact resource, calendar stops crashing the application. So, the mere presence of said resource will get you a crash. I also found that using the right-click way to edit the event instead of double-clicking on it works (ie., doesn't crash). Once you have succesfully launched the edit dialog and in advance, you can happily double-click on any event without a crash, so I'd suggest it as a temporary workaround while it gets fixed. Regards, Ricardo
Processed: moving old pending bugs to my current e-mail
Processing commands for [EMAIL PROTECTED]: > submitter 194554 ! Bug#194554: goats: no menu entry available to add applet to panel Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 214056 ! Bug#214056: gnome-cups-manager: 'Make Default' does not produce any visible change? Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 215672 ! Bug#215672: gxine: does not respect saved volume or default volume set in preferences Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 215853 ! Bug#215853: icepref: Python bug prevents launch Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 218801 ! Bug#218801: apt-howto-en: required precisions on sections 3.5 and 3.10 Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 231894 ! Bug#231894: boot-icons: on HPPA, icons appear as half-height images Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 240019 ! Bug#240019: dhcp3-server: lease file remains empty, except for the boilerplate text Changed Bug submitter from =?iso-8859-15?q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 246280 ! Bug#246280: khelpcenter: GNOME menu entry should have a KDE logo Changed Bug submitter from "Martin-Ãric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 248277 ! Bug#248277: pterm: Change Settings dialog does not save preferences for future use Changed Bug submitter from "Martin-Ãric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 249143 ! Bug#249143: gtk2-engines-thingeramik: ignores the GNOME font settings from Desktop Preferences Changed Bug submitter from "Martin-Ãric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 251173 ! Bug#251173: Creative Content crashes Straw systematically Changed Bug submitter from "Martin-Ãric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 170275 ! Bug#170275: evolution: 1.2: Tools, Settings: dialog too big to fit 800x600 screen on laptop Changed Bug submitter from =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 171108 ! Bug#171108: sash: should provide tab completion for paths and command line history Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 216869 ! Bug#216869: remove Composer from mozilla-browser by creating mozilla-composer Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 216952 ! Bug#216952: openoffice.org-gnome: OpenOffice should have its own folder in the Gnome menu, just like KDE Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 220610 ! Bug#220610: pdsh: gender support broken? Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 221398 ! Bug#221398: grub: provide a sample bootsplash image and corresponding menu.lst stanzas Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 233870 ! Bug#233870: xserver-xfree86: [debconf] write defoma font paths to generated XF86Config files Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 235800 ! Bug#235800: gnome-themes-extra: matching gnome-themes-extras-1 using equivalent gtk-engines would be desirable Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 238662 ! Bug#238662: dazuko-source: should be packaged using module-helper Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 240222 ! Bug#240222: tidy: formatting of comments should always start with a newline Changed Bug submitter from "Martin-Éric Racine" <[EMAIL PROTECTED]> to =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]>. > submitter 244041 ! Bug#244041: streamtuner: should us
Bug#287811: kregexpeditor: exit when edit Pos. (or Neg.) Look Ahead
tags 287811 fixed-upstream
thanks
On Thursday, 30 de December de 2004 10:49, Kazuhiro NISHIYAMA wrote:
> When right click and edit Positive Look Ahead or Negative Look Ahead,
> kregexpeditor writes `This method should be overridden if needed!' to
> stderr and exits with status 1.
The right fix is this one:
RegExpWidget* LookAheadWidget::findWidgetToEdit( QPoint globalPos )
{
return _child->findWidgetToEdit( globalPos );
}
It's been fixed upstream. Thanks for reporting.
--
temp: http://temp.roncero.org
Out: 8.56 ºC -- In: 21.19 ºC
Processed: Re: Bug#287811: kregexpeditor: exit when edit Pos. (or Neg.) Look Ahead
Processing commands for [EMAIL PROTECTED]: > tags 287811 fixed-upstream Bug#287811: kregexpeditor: exit when edit Pos. (or Neg.) Look Ahead There were no tags set. Tags added: fixed-upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#287811: kregexpeditor: exit when edit Pos. (or Neg.) Look Ahead
forwarded 287811 http://bugs.kde.org/96185 stop here > Ok, I am able to reproduce it. I'll have a look at the source code and > bugs.kde.org. Ok, so I have filed a bug upstream indicating the problem. I have also sent a little patch for those who would like to fixit themselves (Warning, it's a quick hack that avoids the app exiting, but I don't know if its ok to do that). You can get it here: http://bugs.kde.org/96185 -- temp: http://temp.roncero.org Out: 10.12 ºC -- In: 21.50 ºC
Processed: Re: Bug#287811: kregexpeditor: exit when edit Pos. (or Neg.) Look Ahead
Processing commands for [EMAIL PROTECTED]: > forwarded 287811 http://bugs.kde.org/96185 Bug#287811: kregexpeditor: exit when edit Pos. (or Neg.) Look Ahead Noted your statement that Bug has been forwarded to http://bugs.kde.org/96185. > stop here Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Final polishing of the KDE 3.3 transition
Hi, just two comments by me: * Adeodato Simó ([EMAIL PROTECTED]) [050102 20:35]: > (b) kdeedu is missing a mipsel build. This is a timeout issue, which > needs to be increased. kdeedu was retried on mipsel on Dec 25th, > but with the timeout unchanged, so Andreas Barth offered to do a > porter build+upload. Yesterday, he told me he was starting the > build with a 1500 min. timeout. Just uploading. > (c) Unless some RM objects, the latest security bugs won't get fixed > before the transition, and uploads to address them will be done > shortly after the transition with urgency=high. > > I talked to Andreas about this too, and he agreed to it since > all the vulnerabilities are present in the current sarge > packages as well. > > We now request for instructions about how to proceed so that the > affected bugs are not included in the RC bug count. One of: > > 1. those security bugs will have to be temporarily > downgraded > > 2. the only other way is to use force hints, and > using force hints would override the safety we were trying > to put in place. > > 3. you could set a temporary sarge-ignore tag? > > 4. or temporaly leave all of them as +sarge only, right? > > (but: I think I prefer to lie about the severity > rather than lie about the tags; Kamion may have a different > opinion as a bugmaster.) > > The bugs in question are these (all of them are tagged sarge,sid): > > #285128: kdelibs: CAN-2004-1165: FTP command injection bug > #286516: kdebase: CAN-2004-1158: Konqueror Window Injection Vuln. > #286521: kdelibs: CAN-2004-1145: Konqueror Java Vulnerability 4. doesn't work, because the current bugs implementation doesn't do bug version tracking. For that reason, I personally tend to prefer to lie about the status (with setting sarge-ignore), because if everything would work well, britney would know that we in reality lower the number of RC bugs by this transition. However, because britney can't know currently, we have to shield light on it by other means. However, I don't really mind to lower them to important currently - but it need of course to be documented why we do it. Cheers, Andi -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Processed: tagging 288251
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.5 > tags 288251 sarge Bug#288251: build dependencies for kdelibs fails Tags were: sarge Tags added: sarge > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Final polishing of the KDE 3.3 transition
Hi all! The gcc-3.4/libunwind transition having happened on Dec 31st, KDE 3.3 is mostly ready to enter sarge. In this mail, I will make a summary of the last issues that need to be addressed: (a) #266478, the dummy bug "new kdelibs should not enter testing alone", should be closed now. If some RM mails to -done, that would be nice. (But see (d) below - I have not already closed it since I wanted some feedback first.) (b) kdeedu is missing a mipsel build. This is a timeout issue, which needs to be increased. kdeedu was retried on mipsel on Dec 25th, but with the timeout unchanged, so Andreas Barth offered to do a porter build+upload. Yesterday, he told me he was starting the build with a 1500 min. timeout. This is the biggest stopper atm, aiui. (c) Unless some RM objects, the latest security bugs won't get fixed before the transition, and uploads to address them will be done shortly after the transition with urgency=high. I talked to Andreas about this too, and he agreed to it since all the vulnerabilities are present in the current sarge packages as well. We now request for instructions about how to proceed so that the affected bugs are not included in the RC bug count. One of: 1. those security bugs will have to be temporarily downgraded 2. the only other way is to use force hints, and using force hints would override the safety we were trying to put in place. 3. you could set a temporary sarge-ignore tag? 4. or temporaly leave all of them as +sarge only, right? (but: I think I prefer to lie about the severity rather than lie about the tags; Kamion may have a different opinion as a bugmaster.) The bugs in question are these (all of them are tagged sarge,sid): #285128: kdelibs: CAN-2004-1165: FTP command injection bug #286516: kdebase: CAN-2004-1158: Konqueror Window Injection Vuln. #286521: kdelibs: CAN-2004-1145: Konqueror Java Vulnerability (d) Given the number of packges that are stalled by kdelibs [1] and not covered by this transition (i.e., not in the hands of the KDE packagers), I expressed two concerns back in November [last section of 2]. [1] http://bjorn.haxx.se/debian/testing.pl?waiting=kdelibs [2]http://lists.debian.org/debian-release/2004/11/msg00154.html The first concern, "one has really to check that the existing version in sarge will work correctly in a KDE 3.3 environment, as newer versions may or may not make sarge", can be considered solved: we received positive feedback from users that had upgraded their KDE to 3.3 in sarge systems. As for the second concern, I'm only mildly drawing some attention from RMs to it: kdelibs entering sarge will mean a bunch of packages with *big* differences migrating, so I always thought that the Release Team would prefer these migrations to happen smoothly, and semi-controlled (plus what I say in the mail), and the only scheme I could came up with was the mass bug-filing. So please, just let us know what to do about this. Cheers. -- dato, on behalf of the KDE Packaging Team -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Listening to: isan - cutlery favours The first step on the road to wisdom is the admission of ignorance. The second step is realizing that you don't have to blab it to the world.
Bug#286690: korganizer: clicking on an event causes segfault, related to LDAP
severity 286690 important stop Hello, I can't reproduce any crashes with korganizer, but I don't use anything to do with LDAP. Someone who does use LDAP has volunteered to look at the problem in the near future. In the meantime, I'm lowering the severity of this bug to important, since most users wouldn't be affected by an LDAP-related crash, and the definition of the important severity level is "a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone." Cheers, Christopher Martin
Processed: Re: Bug#288251: build dependencies for kdelibs fails
Processing commands for [EMAIL PROTECTED]: > tags 288251 sarge Bug#288251: build dependencies for kdelibs fails There were no tags set. Tags added: sarge > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: korganizer: clicking on an event causes segfault, related to LDAP
Processing commands for [EMAIL PROTECTED]: > severity 286690 important Bug#286690: korganizer: clicking on an event causes segfault, related to LDAP Severity set to `important'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#288251: build dependencies for kdelibs fails
Package: kdelibs Version: 4:3.2.3-2 Severity: serious Justification: no longer builds from source Package libtiff3g-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package libtiff3g-dev has no installation candidate E: Failed to satisfy Build-Depends dependency for kdelibs: libtiff3g-dev -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-rc2 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages kdelibs depends on: ii kdelibs-bin 4:3.2.3-2 KDE core binaries ii kdelibs-data 4:3.2.3-2 KDE core shared data ii kdelibs4 4:3.2.3-2 KDE core libraries -- no debconf information
Bug#287811: kregexpeditor: exit when edit Pos. (or Neg.) Look Ahead
On Sunday, 2 de January de 2005 18:03, Kazuhiro NISHIYAMA wrote: > > Could you please write a sequence on how to reproduce the bug? I am > > trying to do it but fail to. > > 1. run kregexpeditor > 2. click a button of `Positive Look Ahead' or `Negative Look Ahead' >in the toolbar > 3. click in the gray area > 4. right click the `Pos. Look Ahead' (or `Neg. Look Ahread') > 5. select `Edit' in the context menu > Then kregexpeditor writes `This method should be overridden if needed!' > and exits. Ok, I am able to reproduce it. I'll have a look at the source code and bugs.kde.org. -- temp: http://temp.roncero.org Out: 12.31 ºC -- In: 21.12 ºC
Bug#287811: kregexpeditor: exit when edit Pos. (or Neg.) Look Ahead
In <[EMAIL PROTECTED]> On Thu, 30 Dec 2004 15:11:08 +0100 <[EMAIL PROTECTED]> wrote: > > When right click and edit Positive Look Ahead or Negative Look Ahead, > > kregexpeditor writes `This method should be overridden if needed!' to > > stderr and exits with status 1. > > Could you please write a sequence on how to reproduce the bug? I am trying to > do it but fail to. 1. run kregexpeditor 2. click a button of `Positive Look Ahead' or `Negative Look Ahead' in the toolbar 3. click in the gray area 4. right click the `Pos. Look Ahead' (or `Neg. Look Ahread') 5. select `Edit' in the context menu Then kregexpeditor writes `This method should be overridden if needed!' and exits.
Bug#288160: marked as done (kdelibs4: Audio KDE System Notifications does not work in experimental)
Your message dated Sun, 2 Jan 2005 17:21:44 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#288160: kdelibs4: Audio KDE System Notifications does not work in experimental 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) -- Received: (at submit) by bugs.debian.org; 2 Jan 2005 02:11:03 + >From [EMAIL PROTECTED] Sat Jan 01 18:11:03 2005 Return-path: <[EMAIL PROTECTED]> Received: from (yamazaki.spalletti.it) [62.94.208.40] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CkvCw-0001UC-00; Sat, 01 Jan 2005 18:11:02 -0800 Received: from zero (zero.int.spalletti.it [192.168.1.10]) by yamazaki.spalletti.it (Postfix) with ESMTP id CADEB9D239; Sun, 2 Jan 2005 03:10:57 +0100 (CET) Received: by zero (Postfix, from userid 1000) id EC18B68269D1; Sun, 2 Jan 2005 03:10:58 +0100 (CET) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Iacopo Spalletti <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kdelibs4: Audio KDE System Notifications does not work in experimental X-Mailer: reportbug 3.2 Date: Sun, 02 Jan 2005 03:10:58 +0100 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kdelibs4 Version: 4:3.3.2-0pre1 Severity: important Tags: experimental Since upgrading to kdelibs4 4:3.3.2-0pre1 audio system notifications does not work anymore. Arts is correctly configured with ALSA as all other audio applications (kaffeine, amarok etc) work normally. knotify and arts processes are active. All other actions (visual notifications, logging etc) work as expected. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (910, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-k7 Locale: LANG=it_IT, LC_CTYPE=it_IT (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages kdelibs4 depends on: ii kdelibs-bin 4:3.3.2-0pre1 KDE core binaries ii kdelibs-data 4:3.3.2-0pre1 KDE core shared data ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libarts1 1.3.2-1aRts Sound system ii libasound21.0.7-4ALSA library ii libaspell15 0.50.5-5 The GNU Aspell spell-checker runti ii libaudio2 1.7-1 The Network Audio System (NAS). (s ii libaudiofile0 0.2.6-5Open-source version of SGI's audio ii libbz2-1.01.0.2-1A high-quality block-sorting file ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libcupsys2-gnutls10 1.1.20final+rc1-10 Common UNIX Printing System(tm) - ii libesd0 0.2.35-2 Enlightened Sound Daemon - Shared ii libfam0c102 2.7.0-6client library to control the FAM ii libgcc1 1:3.4.3-6 GCC support library ii libglib2.0-0 2.4.8-1The GLib library of C routines ii libice6 4.3.0.dfsg.1-10Inter-Client Exchange library ii libidn11 0.5.2-3GNU libidn library, implementation ii libjack0.80.0-0 0.99.0-2 JACK Audio Connection Kit (librari ii libjasper-1.701-1 1.701.0-2 The JasPer JPEG-2000 runtime libra ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libmad0 0.15.1b-1 MPEG audio decoder library ii libogg0 1.1.0-1Ogg Bitstream Library ii libopenexr2 1.2.1-2Runtime files for the OpenEXR imag ii libpcre3 4.5-1.1Perl 5 Compatible Regular Expressi ii libpng12-01.2.8rel-1 PNG library - runtime ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v ii libsm64.3.0.dfsg.1-10X Window System Session Management ii libstdc++51:3.3.5-5 The GNU Standard C++ Library v3 ii libtiff4 3.6.1-4Tag Image File Format library ii libvorbis0a 1.0.1-1The Vorbis General Audio Compressi i
Bug#266478: Uh - file conflict between OOo in testing and KDE3.3
* Andreas Barth [Sun, 02 Jan 2005 14:17:24 +0100]: > Just to make sure our irc-talk is not lost: > 14:10 < aba> _rene_: I think we should continue the discussion here :) (for > the rest of you: There is a file conflict between kde3.3 and OOo in testing) > 14:11 < aba> we need to fix that _before_ KDE3.3 may enter testing. > 14:11 < _rene_> that would break sid's openoffice.org-mimelnk :-) > 14:11 < _rene_> if kde removes those files that is > 14:12 < _rene_> and kde should keep those files > 14:12 < aba> well, other ways are e.g. to fix OOo so that OOo and KDE3.3 can > enter together. > 14:12 < _rene_> I am just working on -4 > 14:12 < aba> good. But I think this calls for an conflict between KDE3.3 and > OOo in testing. > 14:13 < _rene_> iirc kde Replaces: -mimelnk > 14:13 < _rene_> no, it doesn't anymore... > 14:14 < aba> even if it does - wouldn't help if people install KDE3.3 first, > and OOo later. > 14:14 < _rene_> right this was further discussed on #d-release, and the version of kdelibs-data with the missing Conflicts entry is the one in experimental. I raised the severity of #287097 so that we really don't forget fixing it in the next upload. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Taking any religion too seriously --even the Church of Emacs-- can be hazardous to your health. -- Richard Stallman
Processed: klaptopdaemon shutdown problems is probably fixed in sid
Processing commands for [EMAIL PROTECTED]: > severity 252670 grave Bug#252670: klaptopdaemon: session-shutdown instantaneously when running on batteries Severity set to `grave'. > tags 252670 + sarge Bug#252670: klaptopdaemon: session-shutdown instantaneously when running on batteries Tags were: fixed-upstream Tags added: sarge > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#266478: Uh - file conflict between OOo in testing and KDE3.3
Just to make sure our irc-talk is not lost: 14:10 < aba> _rene_: I think we should continue the discussion here :) (for the rest of you: There is a file conflict between kde3.3 and OOo in testing) 14:11 < aba> we need to fix that _before_ KDE3.3 may enter testing. 14:11 < _rene_> that would break sid's openoffice.org-mimelnk :-) 14:11 < _rene_> if kde removes those files that is 14:12 < _rene_> and kde should keep those files 14:12 < aba> well, other ways are e.g. to fix OOo so that OOo and KDE3.3 can enter together. 14:12 < _rene_> I am just working on -4 14:12 < aba> good. But I think this calls for an conflict between KDE3.3 and OOo in testing. 14:13 < _rene_> iirc kde Replaces: -mimelnk 14:13 < _rene_> no, it doesn't anymore... 14:14 < aba> even if it does - wouldn't help if people install KDE3.3 first, and OOo later. 14:14 < _rene_> right -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Re: Desktop task broken on !(i386/powerpc)
[Sven Luther] > I think the real solution to this recuring problem is to split the > dekstop patch into a "just X", "gnome" and "KDE" task. This is much > more friendlier to our non-broadband users, and it makes the task > stuff actually usable. As it stands, we could as well not show it. Personally, I use both KDE, Gnome and "just X" programs. Why do you believe a desktop user want to limit herself to only one of these classes of programs?
Processed: klaptopdaemon shutdown problems
Processing commands for [EMAIL PROTECTED]: > forwarded 252670 http://bugs.kde.org/show_bug.cgi?id=74530 Bug#252670: klaptopdaemon: session-shutdown instantaneously when running on batteries Noted your statement that Bug has been forwarded to http://bugs.kde.org/show_bug.cgi?id=74530. > severity 252670 important Bug#252670: klaptopdaemon: session-shutdown instantaneously when running on batteries Severity set to `important'. > tags 142866 + fixed-upstream woody Bug#142866: klaptopdaemon: Reports 0 minutes remaining when power unplugged Tags were: upstream Tags added: fixed-upstream, woody > tags 252670 + fixed-upstream Bug#252670: klaptopdaemon: session-shutdown instantaneously when running on batteries There were no tags set. Tags added: fixed-upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Desktop task broken on !(i386/powerpc)
On Sat, Jan 01, 2005 at 08:08:16PM +0100, Adeodato Simó wrote: > * Martin Michlmayr [Sat, 01 Jan 2005 18:09:39 +]: > > The "Desktop environment" task is broken on non-i386/powerc machines > > because of kdegraphics: > > I don't know what response is expected from the KDE Team. just to do a > catch-all reply: yes, we are aware of the issue but it's out of our > domain. as you probably already know, it is caused by a t-p-u > kdegraphics upload being forced into sarge with missing builds (in the > days of the libtiff transition). this was regarded, we can imagine, as > the lesser of all evils by the Release Team. > > I believe the Release Managers would have allowed for individual > kdegraphics 4:3.2.3-1.1 builds to trickle into testing, but afaict no > arches other than i386 and powerpc managed to build it (I have no > ACCEPTED mail, and no binaries in the mirrors either). some RM should > be able to say why no other arch could build it. > > please let us know if we can be of any help. I think the real solution to this recuring problem is to split the dekstop patch into a "just X", "gnome" and "KDE" task. This is much more friendlier to our non-broadband users, and it makes the task stuff actually usable. As it stands, we could as well not show it. Friendly, Sven Luther
Bug#288185: juk: crashes with gstreamer output, stops play with arts output
Package: juk Version: 4:3.2.2-1 Severity: normal On particular tracks (mp3), juk will either crash (SEGV) if using gstreamer for output, or stop playing if arts is being used. With gstreamer, juk crashes reliably at the same point every time. With arts, playback of that file is not even started, and does not proceed to the next track. mpg321 plays the file(s) perfectly. Cheers, Nick -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8nwp2 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages juk depends on: ii kdelibs4 4:3.2.3-2 KDE core libraries ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libarts1 1.3.2-1aRts Sound system ii libasound21.0.7-4ALSA library ii libaudio2 1.7-1 The Network Audio System (NAS). (s ii libaudiofile0 0.2.6-5Open-source version of SGI's audio ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libesd-alsa0 [libesd0]0.2.35-2 Enlightened Sound Daemon (ALSA) - ii libfam0c102 2.7.0-6client library to control the FAM ii libgcc1 1:3.4.3-6 GCC support library ii libglib2.0-0 2.4.8-1The GLib library of C routines ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library ii libkdegst0.6 0.6.1-8KDE bindings for GStreamer (shared ii libmad0 0.15.1b-1 MPEG audio decoder library ii libmusicbrainz2 2.0.2-9Second generation incarnation of t ii libogg0 1.1.0-1Ogg Bitstream Library ii libpng12-01.2.8rel-1 PNG library - runtime ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v ii libsm64.3.0.dfsg.1-8 X Window System Session Management ii libstdc++51:3.3.4-13 The GNU Standard C++ Library v3 ii libtag1 1.3.1-1TagLib Audio Meta-Data Library ii libtunepimp-bin [trm] 0.3.0-2libtunepimp simple tagging applica ii libvorbis0a 1.0.1-1The Vorbis General Audio Compressi ii libvorbisfile31.0.1-1The Vorbis General Audio Compressi ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-8 X Window System miscellaneous exte ii libxrender1 0.8.3-7X Rendering Extension client libra ii libxt64.3.0.dfsg.1-8 X Toolkit Intrinsics ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m ii zlib1g1:1.2.2-3 compression library - runtime -- no debconf information
Bug#288160: kdelibs4: Audio KDE System Notifications does not work in experimental
As a further report I got this problem on another box, the problem in knotifyrc lies in "Arts Init" and "Use Arts" parameters which were "false". I don't know how and when those parameters were modified, but it surely wasn't apt-getting new packages. So please disregard this bug as bogus Thanks for you work -- IS Iacopo Spalletti i dot spalletti at iast dot it PGP key block: http://www.nephila.it/pgp
Bug#288160: kdelibs4: Audio KDE System Notifications does not work in experimental
Alle 04:01, domenica 2 gennaio 2005, Adeodato Simó ha scritto: > * Iacopo Spalletti [Sun, 02 Jan 2005 03:10:58 +0100]: > > Since upgrading to kdelibs4 4:3.3.2-0pre1 audio system notifications does > > not work anymore. > > Arts is correctly configured with ALSA as all other audio applications > > (kaffeine, amarok etc) work normally. > > knotify and arts processes are active. > > All other actions (visual notifications, logging etc) work as expected. > > seems to work here, e.g. if I configure kopete to play a sound upon > receiving a message, it works. > > can other people check whether it works for them or not? > > Iacopo, I think it would be best if you describe the exact steps that > you follow, e.g. what application, what event, what sound... perhaps > we can have a look at it in the following days. Weel, i should have done more troubleshooting before reporting the bug. I just deleted knotifyrc and killed knotify; at the first event knotify restarted and emitted the long awaited sound. Maybe something wrong occurred during apt-get upgrade from kdelibs4 4:3.3.1? Seems so. -- IS Iacopo Spalletti i dot spalletti at iast dot it PGP key block: http://www.nephila.it/pgp
Bug#281507: kdepim-3.3.1/debian/patches (revision 4:3.3.1-1) fails on rebuild
Oh yes, true. Thank you very much, Cheers, Jean-Damien. On Saturday 01 January 2005 11:14 pm, Adeodato Simó wrote: AS > * Jean-Damien Durand [Sat, 01 Jan 2005 22:52:16 +0100]: AS > The reason that using dpkg-buildpackage fails for you is that you pass AS > the '-nc' when calling it:
