Re: audio io slave, ogg, and incorrect bitrates.
Woody has been frozen since last april (roughly 76 days). This bug is fixed in KDE 3 though. Chris On Tue, Jul 16, 2002 at 11:17:38AM +0800, Alwyn Schoeman wrote: Apparently there is a patch for kde 2.2.2 here: http://homepage.usask.ca/~aco907/audiocd-vorbisrc3.patch I cannot see how this is still broken in the current 2.2.2 that is in testing, but it is. Does it mean that the kde developers have not fixed the problem yet themselves or is it the Debian packager's responsibility to patch in the distribution? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Just how long does it take to compile?
måndagen den 15 juli 2002 21.34 skrev John Gay: So, my question is, just how long can I expect the rest of KDE3 to take to compile? Yes, I know I can now get unstable deb's, but I want to try it for myself. The tar balls are from around Jan this year. I doubt you can do it in reasonable time with 16MB of memory. That kind of memory no one wants anymore, so you should be able to get it second hand for almost nothing, or even for free. If you have enough RAM, my guess is that you can count on a week for compilation time on your CPU. -- Karolina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Just how long does it take to compile?
why don't you compile it on your faster hardware, and shift it over to the slower machine for install? John Gay [EMAIL PROTECTED]To: debian-kde@lists.debian.org om.net cc: Subject: Just how long does it take to compile? 15/07/02 20:34 I've been playing arould with Debain for several years now, but I've always been aware of the delay between software release and Debian release, especially when freeze is approching. I've been toying with the idea of building my own custom box for a while, and since I have some spare hardware and several source tar balls around, I decided to give it a go. Unfortunately, the box is rather old, 200Mhz Pentium MMX with 16M ram. I installed a base Debian from Woody CD's and most of the development files. Next, I compiled X4.2.0 from sources I have on CD to support my GVX1 card. Now I am in the process of compiling KDE3. I say in the process, Actually qt libs have been compiling now for over 24 hours! I did have a problem with memory limitations, and had to re-size both my root and swap partitions. I realise 16M is far too little memory, but I am hoping that if I get this box running, I can swap it for my daughters box which has 64M of the same type of memory. So, my question is, just how long can I expect the rest of KDE3 to take to compile? Yes, I know I can now get unstable deb's, but I want to try it for myself. The tar balls are from around Jan this year. Cheers, John Gay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify [EMAIL PROTECTED] This footnote also confirms that this email message has been checked for all known viruses. ** SCEE 2002 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: noatun crashes on startup
On Tuesday 16 July 2002 12:38 am, David Gibb wrote: stderr gives: mcop warning: user defined signal handler found for SIG_PIPE, overriding ASSERT: mPlaylist in ../../../noatun/library/pluginloader.cpp (259) KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = noatun path = unknown pid = 20174 ERROR: KUniqueApplication: DCOP communication error! Hmmm, I am no expert in matter of noatun but it looks like an assertation fails. Maybe some plugin causes trouble? Is this running a vanilla configuration? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: noatun crashes on startup
On Tuesday 16 July 2002 01:38, David Gibb wrote: system info: athlon 1.4GHz 256MB memory debian woody/sid stderr gives: mcop warning: user defined signal handler found for SIG_PIPE, overriding ASSERT: mPlaylist in ../../../noatun/library/pluginloader.cpp (259) KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = noatun path = unknown pid = 20174 ERROR: KUniqueApplication: DCOP communication error! Remove the $KDEHOME/share/config/noatunrc file. Then it will work. (a new one will be created at first start of noatun) Regards Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.1
Ben Burton said, and I quote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 kdelibs, kdebase, kdemultimedia are at version 3.0.6 FWIW, 3.0.6 is the official code version for 3.1-alpha1. kdeartwork, kdeedu, kdesdk, kdetoys are at version 3.0.2 These are Ben Burtons packages I'll be updating these to 3.1 once the 3.1 core packages are available; for one thing it seems sane to wait till the core packages are settled enough to actually be made public, and for another I'm running KDE3 in a chroot on my KDE2.2.2 machine so I can support my woody/sid packages, and I'd rather not rebuild all the core packages myself. :) The core packages are in a constant state of flux. I just found 108 files in kdebase which were not in any package. Last time I did kdebase, a couple of weeks ago, there were none. But kde 3.1 packages are mostly buildable from CVS if you have the time to fix the added, moved or removed files. kdegames is at version 3.0.0 rc4 I think that is also one of Bens. I'd need to check Nope. Daniel Schepler [EMAIL PROTECTED]. Ben. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] http://baasil.humbug.org.au/bab/ Public Key: finger [EMAIL PROTECTED] I use innocence in my demeanor like a Venus flytrap. - Tori Amos -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9M4d1MQNuxza4YcERAg/iAJ9HsaEe4gd1k94xTHcsxPUF7yczCgCgpK92 aVanF04+IfXiQ2JKQtIUj/k= =4lE/ -END PGP SIGNATURE- -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpNvMDzq2Xmn.pgp Description: PGP signature
Re: patch for wine to compile against new libarts
Tomasz Wegrzanowski said, and I quote: Because wine in debian depends on kde2 (libarts, libarts-dev) i think that wine compiled against kde3 (libarts1, libarts1-dev) should be put along with the rest of kde3 on unofficial kde3 .debs repository. Here is the patch that allows that. I didn't check if sound works :) Just that it compiles, installs and works in general. (wine maintainer in cc) This is where it should be fixed, but as libarts1 is not in the archive, I don't think the maintainer would be wrong in not making the change. --- control.orig Mon Jul 15 15:36:03 2002 +++ control Mon Jul 15 14:10:19 2002 @@ -5,7 +5,7 @@ Build-Depends: debhelper (= 3.0), docbook-utils | cygnus-stylesheets, c2man, flex, bison, xlibs-dev | xlib6g-dev, libxpm4-dev | xpm4g-dev, xlibmesa-dev | libgl-dev, libncurses5-dev, libcupsys2-dev | cupsys-dev, - libjpeg-dev, libfreetype6-dev | xlib6g-dev ( 4.0), libarts-dev, + libjpeg-dev, libfreetype6-dev | xlib6g-dev ( 4.0), libarts-dev | libarts1-dev, libsane-dev, libusb-dev, libperl-dev Standards-Version: 3.5.6 -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpWtDu80BMgz.pgp Description: PGP signature
Re: mcopidl
David Gibb said, and I quote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I recently installed kde 3.0.2 and I was trying to get compiling within kdevelop to work. I installed qt3-mt-dev, kdebase-dev, and kdelib-dev, but kdevelop still complains with configure: error: The important program mcopidl was not found! Please check whether you installed KDE correctly. *** failed *** What did I fail to install? thanks! Dave -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9MwqH/ti8gaoY4P8RAn8BAJ9DxzKzZw0zEgOvA9WY18GVUU17JACgpTdi VrWfuLxYtva5MYQp2Z+5mYM= =dlYq -END PGP SIGNATURE- It is in libarts1-dev. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpqAB9VCenDF.pgp Description: PGP signature
Re: patch for wine to compile against new libarts
On Tue, Jul 16, 2002 at 11:40:54AM +0100, David Pashley wrote: Tomasz Wegrzanowski said, and I quote: Because wine in debian depends on kde2 (libarts, libarts-dev) i think that wine compiled against kde3 (libarts1, libarts1-dev) should be put along with the rest of kde3 on unofficial kde3 .debs repository. Here is the patch that allows that. I didn't check if sound works :) Just that it compiles, installs and works in general. (wine maintainer in cc) This is where it should be fixed, but as libarts1 is not in the archive, I don't think the maintainer would be wrong in not making the change. I think that maintainer of wine should just apply the patch as it doesn't break anything, and that patched and recompiled wine should be available with the rest of kde3. I put patched and recompiled .debs on my server but it has really slow connection and is not 24/7 on, so I'd prefer if someone put them on some better server. It's just a directory, not apt repository. https://taw.pl.eu.org/~taw/kde/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.1
On Tuesday 16 July 2002 11:37 am, David Pashley wrote: But kde 3.1 packages are mostly buildable from CVS if you have the time to fix the added, moved or removed files. I've just done this. But many of the builds fail. A lot of autoconf stuff needs fixing too. It's enough for a basic system though ;) Shame dpkg cannot handle 'test' installs. Ie something that would allow packages like kde2 and kde3.1 beta to co-exist. Then again, which packaging system does? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.1
tisdagen den 16 juli 2002 12.37 skrev David Pashley: But kde 3.1 packages are mostly buildable from CVS if you have the time to fix the added, moved or removed files. It is mostly not buildable into debian packages. And I think it is the debian packages which is the very good thing with debian. You can as easily add packages, as you can remove, and which file belongs to what is taken care of automatically. Otherwise you system tend to get full of orphan files after a while. A system can also be mostly reproduced by reinstalling all the same packages. If new builds are just appended to the kde binary tree, after a while you get a lot of files that does not belong to anywhere, and they screw up kde. If you reinstall kde completely everytime, your build environment can't be kde. So debian packages is the solution on how you can rebuild KDE on your working system, and it works beautifully. It is really not hard to keep track on the added, moved or removed files. Most is handled automatically, and require manual work only when something really new has happened. And such situation might need investigation anyway. The hard part is not packaging, but finding the specific debian problems and patches. I don't even try to do that. -- Karolina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: noatun crashes on startup
On Tue, 2002-07-16 at 04:15, Michael Schmitz wrote: On Tuesday 16 July 2002 01:38, David Gibb wrote: system info: athlon 1.4GHz 256MB memory debian woody/sid stderr gives: mcop warning: user defined signal handler found for SIG_PIPE, overriding ASSERT: mPlaylist in ../../../noatun/library/pluginloader.cpp (259) KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = noatun path = unknown pid = 20174 ERROR: KUniqueApplication: DCOP communication error! Remove the $KDEHOME/share/config/noatunrc file. Then it will work. (a new one will be created at first start of noatun) Damned screwed-up ML config, I meant this to go to the list. Your suggestion doesn't work here. It still bombs with: $ rm -f noatunrc $ noatun mcop warning: user defined signal handler found for SIG_PIPE, overriding Couldn't instanciate artsobject Noatun::Session. (This is normally caused by a broken package or compiling kdemultimedia in a --prefix different from arts. It may also be from two conflicting packages, so uninstall every arts/artsd package you have installed and try againe. KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = noatun path = unknown pid = 31613 ERROR: KUniqueApplication: DCOP communication error! -- Brad Felmey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Launching an application with the keyboard
Hi Is it possible to launch an application with a keboard shortcut in KDE 3.02 ? With WindowMaker or Sawfish which I can assign say Alt t to launch a terminal session. Can I assign a such a keyboard shortcut to Konsole using KDEs window manager, I cant seem to find such an option in control panel ? Thanks Pat -- --- Pat Colbeck E-mail: [EMAIL PROTECTED] Tel:I'm not telling --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Launching an application with the keyboard
On Tuesday 16 July 2002 16:05, Pat Colbeck wrote: Hi Is it possible to launch an application with a keboard shortcut in KDE 3.02 ? With WindowMaker or Sawfish which I can assign say Alt t to launch a terminal session. Can I assign a such a keyboard shortcut to Konsole using KDEs window manager, I cant seem to find such an option in control panel ? You can use kmenuedit for this. Regards Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Launching an application with the keyboard
Ahhh thanks, that works great. I knew there must be a way to do it. On Tuesday 16 July 2002 3:43 pm, Michael Schmitz wrote: You can use kmenuedit for this. -- --- Pat Colbeck E-mail: [EMAIL PROTECTED] Tel:I'm not telling --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: noatun crashes on startup
On Tuesday 16 July 2002 05:15, Michael Schmitz wrote: On Tuesday 16 July 2002 01:38, David Gibb wrote: system info: athlon 1.4GHz 256MB memory debian woody/sid stderr gives: mcop warning: user defined signal handler found for SIG_PIPE, overriding ASSERT: mPlaylist in ../../../noatun/library/pluginloader.cpp (259) KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = noatun path = unknown pid = 20174 ERROR: KUniqueApplication: DCOP communication error! Remove the $KDEHOME/share/config/noatunrc file. Then it will work. (a new one will be created at first start of noatun) Regards Michael Are you talking about /usr/share/config/noatunrc or ~/.kde/share/config/noatunrc? If you're talking about the former, it doesn't exist on my system. If your talking about the latter, I already tried it. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: audio io slave, ogg, and incorrect bitrates.
On Tuesday 16 July 2002 00:59, Chris Cheney wrote: This bug is fixed in KDE 3 though. Chris Not for me! I consistently get ~100kbps, no matter how high I put the setting. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
noatun
Hmm. Now noatun works. And I don't know why. I'm confused, but not complaining ;) Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: noatun crashes on startup
On Tuesday 16 July 2002 18:03, David Gibb wrote: Are you talking about /usr/share/config/noatunrc or ~/.kde/share/config/noatunrc? If you're talking about the former, it doesn't exist on my system. If your talking about the latter, I already tried it. I'm talking about the one in your home directory (the latter). For me it works like that way: dpkg --purge noatun rm ~/.kde/share/config/noatunrc apt-get install noatun I've got that hint from: http://mail.kde.org/pipermail/kde-multimedia/2002-April/000288.html Regards Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Just how long does it take to compile?
Well, it seems the consensus is about a week?!? Being out of work at the moment, I've got nothing but time. There have also been a few suggestions, which I'll give my answers to and maybe someone can enlighten me in the errors of my ways ;-) This machine takes old RAM's which should be easy and cheap to find. Unfortunately neither is the case. Shops don't carry them so second-hand is the only source. And second hand is rarer than hen's teeth since most home users have swapped these machines out ages ago. Like I said, my duaghter currently has 64M in her machine. I am hoping to prove to her that this new machine will be better then her current one, which doal-boots with Windows95 for her printer and scanner and a few games I never see her play anymore. The printer now seems to be supported, Xerox M750, but the scanner is Parallel, which might be a problem. As for compiling on my dual PII 350 and copying over. Yes, I've got a network connection so connectivity is not an issue. The two things I am worried about are: 1) How can I compile this on my current, working KDE2 system without screwing it up. Every time I've tried playing with such things, I've alway been bitten, 999 times bitten, once shy. 2) As my system is PII and the target is PentiumMMX I'm not sure exactly haw to cross-compile. If I ws willing to take the plunge and upgrade MY desktop, I could compile for my PII and hopefully get a bit of performance improvement, but I would need to compile for the PentiumMMX in the target box. It seems simpler, but slower, just to compile on the target in the first place. I know(think?) that it will optimise for the Pentium rather than the 386 compatible deb's for a bit of performance? If someone can answer the two points above to my satisfaction, and remember, I'm not really a programmer, I just play one in my dreams ;-), then I might take the chance with compiling on my faster box. The wife keeps complaining about the box being on all night, often thrashing, and just how much power is it using. Thanks for the answers and suggestions. I look forward to even more, but I'm having problems with my ISP's mail service. Seems I can send mails just fine, but can't fetch them reliably? Sometimes it helps if I fetch a few of them via the web site, but that removes them from my mail box, so I risk loosing many mails that way. Cheers, John Gay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Just how long does it take to compile?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 16 July 2002 06:15 am, John Gay wrote: Well, it seems the consensus is about a week?!? Being out of work at the moment, I've got nothing but time. There have also been a few suggestions, which I'll give my answers to and maybe someone can enlighten me in the errors of my ways ;-) As for compiling on my dual PII 350 and copying over. Yes, I've got a network connection so connectivity is not an issue. The two things I am worried about are: 1) How can I compile this on my current, working KDE2 system without screwing it up. Every time I've tried playing with such things, I've alway been bitten, 999 times bitten, once shy. One way is to add a new partition to your system and install a debian base, source, compiler and begin your task. A second way, and one that was fun to see on my own box, is using fakeroot, debootstrap, and chroot(?). Early versions of kde3 were compiled on this computer in this *new* environment. It actually installs a new version of Debian, in a protected environment. A user then can become a fakeroot user and apt-get all the stuff needed to build packages. I don't recall all the binaries that are needed, but I know that there is at least one hacker that does, and reads this list! 2) As my system is PII and the target is PentiumMMX I'm not sure exactly haw to cross-compile. If I ws willing to take the plunge and upgrade MY desktop, I could compile for my PII and hopefully get a bit of performance improvement, but I would need to compile for the PentiumMMX in the target box. It seems simpler, but slower, just to compile on the target in the first place. I know(think?) that it will optimise for the Pentium rather than the 386 compatible deb's for a bit of performance? This is a compiler option. As far as I know, all binary packages in debian are built for a 386 (for intels). When you are ready to build, add the appropriate string and press ENTER to build for your particular needs. John Gay I hope this helps. tatah and 73 - -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9NFkyZHBxKsta6kMRAnTWAKCUmgloY75nJ4We7yOAr6bxPB3JCwCgjdBD OgOobOK3ACy9zTMTSZ4j3A0= =5wsd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Just how long does it take to compile?
On Tue 16 Jul 2002 18:34, Jaye Inabnit ke6sls wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 16 July 2002 06:15 am, John Gay wrote: Well, it seems the consensus is about a week?!? Being out of work at the moment, I've got nothing but time. There have also been a few suggestions, which I'll give my answers to and maybe someone can enlighten me in the errors of my ways ;-) As for compiling on my dual PII 350 and copying over. Yes, I've got a network connection so connectivity is not an issue. The two things I am worried about are: 1) How can I compile this on my current, working KDE2 system without screwing it up. Every time I've tried playing with such things, I've alway been bitten, 999 times bitten, once shy. One way is to add a new partition to your system and install a debian base, source, compiler and begin your task. Since I've two hard drives, hda and hdb and a CD-RW and DVD in hdc and hdd, I'd have to go to SCSI drives to add any more. Also, my current disks are FULL! I really need to delete a few things ;-) A second way, and one that was fun to see on my own box, is using fakeroot, debootstrap, and chroot(?). Early versions of kde3 were compiled on this computer in this *new* environment. It actually installs a new version of Debian, in a protected environment. A user then can become a fakeroot user and apt-get all the stuff needed to build packages. I don't recall all the binaries that are needed, but I know that there is at least one hacker that does, and reads this list! This sounds more interesting, but again, I just want to build pure binaries, not deb's. I suppose I could still use the fakeroot route, but again, I'd need to free up some space. 2) As my system is PII and the target is PentiumMMX I'm not sure exactly haw to cross-compile. If I ws willing to take the plunge and upgrade MY desktop, I could compile for my PII and hopefully get a bit of performance improvement, but I would need to compile for the PentiumMMX in the target box. It seems simpler, but slower, just to compile on the target in the first place. I know(think?) that it will optimise for the Pentium rather than the 386 compatible deb's for a bit of performance? This is a compiler option. As far as I know, all binary packages in debian are built for a 386 (for intels). When you are ready to build, add the appropriate string and press ENTER to build for your particular needs. Yes, but it's also something that is checked during ./configure. So, if I'm not mistaken, when I ran ./configure, with the options I wanted, it noticed it was a PentiumMMX and set some variable in the Makefile's for this. Teh compiling seems to be set for 586 rather than 386. Of course if I had compiled this on my box, it would have been set to 686 instead. I think, for the time being, I'll just keep going on the Pentium box, since kdelibs is about 12 hours along and qtlibs took about 30 odd hours. I'll be building most of the modules, 1) because I'm a glutton for punishment. 2) I want to see them on my Daughters new box. John Gay I hope this helps. Thanks for the info. I'll probably try this out with something else in the future, like when Linux Format puts KDE3.1.0 on CD for me :-) tatah and 73 - -- Also, I've been invited to assist in testing some 3D acceleration stuff for XFree86, since one of the developers has a dodgy card. This could be great fun in itself! Cheers, John Gay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
KDE 3.0.2 packages for linux-alpha
Hi, I just finished compiling most of the unofficial kde3/koffice packages on debian/alpha (kdeaddons and kdeartwork still outstanding, will follow soon) If there are some other DEC(Compaq(HP)) Alpha users interested in trying them out: They are apt-getable at deb http://www-stat.uni-klu.ac.at/~agebhard/kde3-alpha/ ./ Please also look at the README: http://www-stat.uni-klu.ac.at/~agebhard/kde3-alpha/README which states, that these are UNOFFICAL rebuilds of UNOFFICIAL packages!! I did no very exhaustive testing, but it seems quite stable, no obviouos differences to the i386 kde3 packages. I simply used the debian source packages for kde3 (kde3.geniussystems.net ...). The only modification I had to make was to add --disable-final to each ./configure call in k*/debian/rules (it would otherwise trigger an alpha-specific size limitation for the .got section (global offset table?) in alpha object files). And of course I had to disable the kcmlilo package. Albrecht Please take into account that I'm quite new to debian linux (I have some years of experience with rpm based linux systems as well as with Tru64 on DEC alphas though), so if I missed something ... // Albrecht Gebhardt Tel.: (++43 463) 2700/3118 // Institut fuer Mathematik Fax : (++43 463) 2700/3198 // Universitaet Klagenfurtmailto:[EMAIL PROTECTED] // Universitaetsstr. 65 http://www-stat.uni-klu.ac.at/~agebhard // A-9020 Klagenfurt, Austria -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
