Will KDE make it into Woody?
The current status of KDE in Woody is less then perfect. kdenetwork and kdegraphics is still v2.1.1, buggy and missing on some platforms. kdelibs is buggy, and seem to wait for libglib1.3 before it will enter Woody. Several KDE programs fail to build because libkmid is unable to install. I'm getting worried that the KDE not will make it into Woody. The release maintainer have already started to remove buggy packages from Woody, and several of the KDE packages will -- probably -- get new bugs registered when they finally compile on all the required platforms. Do I have reason to worry or should I just relax?
Re: Will KDE make it into Woody?
[EMAIL PROTECTED] > This will benefit not just the users trying to plan their KDE useage > activities, but also allow others with the ability to contribute to > packaging KDE, or fixing bugs, etc, to know when & where their > skills might be needed, so that they, too, could help contribute to > the development & progress of KDE in Debian. Checking BTS and sending patches is the correct solution for everyone who want to contribute to the development and progress of KDE in Debian. I've done it several times, but I'm sure it will help even more if more people submit patches to BTS. Of course it would be nice with status updates, and I really would like to get more information on the current progress, but if you want to contribute there is only one way. Send patches.
Re: the non-existence of libglib1.3-12
[Rene Horn] > I tried finding a copy of libglib1.3-12 so I could install it on my > own, but had no luck. Is this the problem currently blocking the autobuilders? Perhaps KDE should link glib statically?
Re: Will KDE make it into Woody?
[ben] > hey petter, i'm totally willing to offer whatever effort i can, but > what is BTS and how do i check it? can i contribute? as far as > patches are concerned, i wouldn't know where to begin, but i am > definitely willing to contribute whatever i can. Ah, sorry for using unknown TLAs[1]. :-) BTS is Debians bug tracking system. It is found at http://bugs.debian.org/ >. If you visit the following pages, you should find most of the registered bugs with central KDE packages: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kdelibs > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kdebase > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kdenetwork > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kdegraphics > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kdeadmin > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kdeutils > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kdetoys > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=kdegames > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=koffice > Checking http://ftp-master.debian.org/testing/update_excuses.html.gz > will tell you the current status in testing. Sending patches, testing patches, testing if bugs are still present and asking for more information needs to be done for a lot of the registered bugs. (BTW: I believe emails asking for more info must be sent to <@bug>[EMAIL PROTECTED] in addition to <#bug>@bugs.debian.org). Footnotes: 1 http://www.tuxedo.org/~esr/jargon/html/entry/TLA.html >
Re: gcc 3.0.4, kde in Debian: status?
[Christophe Prud'homme] > I was wondering if the new gcc 3.0.4 in sid has the patch > [contrib/PR3145.patch] applied to fix some arts compilation. Did you try to ask the GCC 3.0 maintainer?
Re: Getting xscreensaver to work...
[Michael Hoodes] > xhost + 'xhost +' is a very bad idea. Letting every user on the system record the keys pressed do not sound like the correct solution.
Is autobuilding kde packages broken in Unstable?
The autobuilders seem to fail for all KDE packages. The problem seem to be related to kdebase and kdelibs. Checking http://buildd.debian.org/fetch.php?&pkg=koffice&ver=1%3A1.1.1-6&arch=arm&stamp=1014541962&file=log&as=raw>, I see this: The following information may help to resolve the situation: Sorry, but the following packages have unmet dependencies: kdebase-dev: Depends: kdebase-audiolibs (= 4:2.2.2-13) but it is not going to be installed kdelibs-dev: Depends: libkmid-dev (= 4:2.2.2-11) but it is not going to be installed E: Sorry, broken packages Anyone know what the problem is? kgeo, kdegames, koffice, kdetoys, kdeutils, kdenetwork, kdemultimedia and kdeadmin seem to have problems (not sure if everyone have this problem).
Re: KDE status update
[Chris Cheney] > kdelibs - should go into woody once m68k builds > kdebase - should go into woody once m68k, arm, mips builds > > kdeadmin - should go into woody once arm, m68k, s390, sparc builds > kdegraphics - needs new upload to remove kamera > kdemultimedia - needs build on all arch > kdenetwork- should go into woody once alpha, hppa, ia64, m68k, sparc > builds > kdepim- only god can save this package[*] > kdeutils - needs new upload to remove ark Current testing status is kdelibs- Missing m68k build. kdebase- Missing m68k, mips build. kdeadmin - Missing m68k build. kdegraphics- Still needs new upload. kdemultimedia - Missing arm, m68k, powerpc build. kdenetwork - Missing alpha, hppa, ia64, m68k, sparc build. kdepim - Needs upload to fix bug. Missing alpha, arm, ia64, m68k, sparc build.. kdeutils - Needs upload to fix bug. Missing alpha, hppa, ia64, m68k and sparc build.. And a few others I'm interested in: kdegames - Ready to go into Woody. Possibly waiting for kdelibs. kdetoys- Missing m68k build. koffice- Missing arm build. kseg - Ready to go into Woody, needs 8 more days. kgeo - Missing ia64, m68k build. krecord- Needs upload to fix alpha compile problem. Missing alpha build. noteedit - Missing ia64, m68k, powerpc, sparc build. Anyone know how to help the m68k and arm autobuilders?
Re: Two Kmail users in one X session
[Oleg Cherkasov] > Remote shell could help to do that: > > rsh -l localhost kmail > > In ~/.rhosts add: > > + my_user_name But it would open up a security hole.
Re: kdekillall command
[Rene Horn] > The kdekillall command requires gawk to work, so perhaps it's a good > idea to make it dependent on this package? Did you submit this to bugs.debian.org? I believe it is a better place to report it than debian-kde, to make sure no one forgets it.
Re: KDE startup hangs and 'commits suicide'
[Fabian Dortu] >> Maybe one can add >> >> ifup lo >> >> to the kde-startupscript. dcop seems to need the loopback interface. [...] > > It works ! Thanks a lot. If this is a fresh install, you have probably been bitten by the bug in the install system failing to configure the loopback interface. The correct fix is probably to add the following to /etc/network/interfaces: # The loopback interface auto lo iface lo inet loopback It should have been added by the install program, but sometimes it failed to do so. The bug is believed fixed in the latest source.
Re: Debian KDE Status Update - 20020314
[Chris Cheney] > It may be possible for KDE 2.2.2 to be in woody by sunday (except for > kdegraphics/kdeutils) Not quite, but close. Output from grep-excuses: * kdesdk (2.2.2-2 to 2.2.2-3) + Maintainer: Ben Burton + Too young, only 4 of 10 days old + Not considered * kdegraphics (4:2.1.1-6 to 4:2.2.2-6.4) + Maintainer: Christopher L Cheney + 5 days old (needed 2 days) + out of date on arm: kamera, kcoloredit, kfract, kghostview, kiconedit, kooka, kpaint, kruler, ksnapshot, kview, libkscan-dev, libkscan1 (from 4:2.2.2-6) + out of date on m68k: kamera, kcoloredit, kfract, kghostview, kiconedit, kooka, kpaint, kruler, ksnapshot, kview, libkscan-dev, libkscan1 (from 4:2.2.2-6) + Not considered + Depends: kdegraphics gphoto2 + Depends: kdegraphics libusb + Depends: kdegraphics sane-backends * kde-i18n (4:2.2.2-1 to 4:2.2.2-2) + Maintainer: Debian QA Group + Too young, only 7 of 10 days old + Not considered * kdeutils (4:2.2.2-5 to 4:2.2.2-9) + Maintainer: Christopher L. Cheney + 24 days old (needed 10 days) + ark (alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc) is buggy! (1 > 0) + Not considered * kdetoys (4:2.2.2-2 to 4:2.2.2-3) + Maintainer: Ben Burton + 28 days old (needed 10 days) + Valid candidate * noteedit (- to 1.16.1-1.1) + Maintainer: Brian Russo + 20 days old (needed 2 days) + out of date on ia64: noteedit (from 1.12.3-1) + Not considered -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Remember Password? Nope
[Robert Tilley] > I have filed numerous bug reports at bugs.kde.org with no results. Do you have bug numbers to look up in the database? It would be interesting to see why nothing happened. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kde packages broken?
I believe a better audience for you question is the debian-kde list. I have reformatet your message for better readability and sent it there. [Juha Jäykkä] > What is wrong with the various woody kde packages (knode, > kdebase3, keystone, kdebase3-bin...), since almost every time I > upgrade my woodys some of them fail. Usually because dpkg tries to > unpack a file from package A over a file which also exists in > package B? > > I have noticed this many times upgrading from potato to woody with > various packages but kde packages are the only ones I have seen > doing this in a woody -> woody upgrade! > > Usually this is fixed by removing the other for a while and then > reinstalling it later or simply saying "apt-get -f install A B" - > luckily when kdebase3 and kdebase3-bin were borken, this helped > since removing either... > > Now keystone and knode are not fixable by this, though. I would > hate to file bug reports against woody packages at this time - > especially since this seems to happen again and again with kde > packages. Is there some reason why it is only kde? > > -- > --- > | Juha Jäykkä, [EMAIL PROTECTED]| > | home: http://www.utu.fi/~juolja/ | > --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.0rc3 Debs???
[Chris Cheney] > KDE 3.0 final has been tagged and I am working on finishing up the debs > for it currently. It will probably take a few more days. Do you plan to include KDE 3.0 in Woody instead of KDE 2.2.2? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Audio permissions
[Anders Ellenshøj Andersen] > Probably. Easiest sollution is usually to add the particular user to > the audio group (# adduser user audio), however if you have a lot of > users you might have to change permissions on the audio device. I believe redhat changes the owner of some devices to the user logging into the console, and changes it back when the user logs out. This is probably a good idea for Debian as well. This is done using /etc/security/console.perms and pam_console, I think.
Re: how send "arab text" mail with woody+KDE 3.1+ mozilla mail 1.2.1 ?
Never mind the people finding the current witch hunt for terrorist funny. [Manuel Segura] > Please, if some one know how to configure debian to be able > to send arab mail, it would be great. If not, i would be obliged > to switch to another distrib for this user :-( Sounds like you might be using the wrong display font. Or perhaps the fonts are not installed? I have no experience with arabic, but for saami, the unifont package needed to be installed, and the KDE font had to set to ISO-10646.
Re: I'm back
[Chris Cheney] > I just wanted to send this email to let everyone know I am still > alive and reading through my email backlog now. I didn't have email > or linux access for about 6 weeks. Welcome back. I hope you have a good spam filter. :)
Will KDE in etch support hotplug devices in large installations?
A common setup for installations with a lot of user is to leave it to the PAM modules to add the console user to the groups required for local access. A summary of this setup is available from http://lists.debian.org/debian-devel/2006/10/msg00752.html> under the pam_group heading. This worked just fine with KDE in etch earlier. It does not work any more. I'm told the reason is that KDE no longer uses pmount, but passes the hotplug event on to hald. hald do not know of the groups given to the console user by the PAM system, and thus do not mount anything. The reason is that pmount was running as the logged in user and inheriting all the groups of the logged in user, while hald is a system daemon looking up the user in the group database. The latter do not include the user as a member of the local device groups, and can not do it either in an enterprise environment with 4 users and heterogenous unix environments. Are there any hopes of having this problem fixed in time for etch? KDE without support for hotplugged devices is a very big problem for enterprise desktop settings. The KDE/hald problem is explained in details in http://bugs.debian.org/377689 >. Friendly, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
