http://www.davidpashley.com/debian-kde/faq.html
Just to give you some warning, I intend to remove this document at the end of this week. I'm not entirely sure why this link is still the top result in google for "debian kde" as the information is 3 years old. As I haven't been keeping up with developments, I don't know how relevant any of that information is. If there is anything worth keeping, you may want to add it to the wiki. I intend to redirect people from that page to http://www.davidpashley.com/debian/kde.html, so if you have any links you think might be worth including on that page, please let me know. (Please CC me as I'm not on either list.) -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: unsubscribe
On Mar 02, 2004 at 13:00, Olivier Levillain praised the llamas by saying: > > -- > Olivier Levillain > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] HTH HAND -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgph1613CLNkj.pgp Description: PGP signature
Re: KDE 3.2 Progress
On Feb 16, 2004 at 21:38, Josh Metzler praised the llamas by saying: > Now to your argument - I agree it doesn't make sense for KDE 3.2 packages to > be available for stable but not for unstable. A final reason for this is > that there are two KDE teams. The stable packages were not made by the > Debian KDE maintainers, but by the KDE project, and they were made using a > snapshot of the incomplete Debian packaging. If you browse the list > archives, you will see that people have had problems with these packages. It > is my understanding that when 3.2 is released to unstable, the stable > backports will be recreated using the updated packaging. In my opinion, it > was inappropriate for KDE to release Debian stable backports using incomplete > packaging, but that was their decision, and that is why 3.2 is available for > stable. > This isn't quite true. The packages available were done aiui, by Ralf Nolden, who is part of the Debian KDE packaging team. The packages are pretty much exactly the same as the final packages available for sid. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpGB1utBmtXs.pgp Description: PGP signature
Re: permissions of /tmp/.ICE-unix
On Jan 12, 2004 at 11:06, Mike Williams praised the llamas by saying: > This might be a FAQ, but I've just discovered that the following > init-script greatly improves my KDE start time: > > ,--- /etc/init.d/ICE-unix --- > | #!/bin/sh > | > | PATH=/sbin:/bin:/usr/sbin:/usr/bin > | > | case "$1" in > | start) > | mkdir -p /tmp/.ICE-unix > | chmod 1777 /tmp/.ICE-unix > | ;; > | *) > | ;; > | esac > ` > > Previously, KDE would often pause for 6-7 seconds at the "Initializing > peripherals" stage; now, it's noticebly faster. Seems faster when starting > konqueror, too (though I might just be imagining it). > > Might it be worth making this a standard part of /etc/init.d/kdm?? > This is certainly part of the Xfree86 4.3 packages. I'm not sure if it is in the 4.2 packages yet. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgprEbeA4oTti.pgp Description: PGP signature
Re: KDE status report (again)?
On Sep 28, 2003 at 23:45, Chris Cheney praised the llamas by saying: > On Sun, Sep 28, 2003 at 03:38:46AM -0400, Nathanael Nerode wrote: > > Hate to ask again, but what's currently holding up KDE? I don't > > know of any Qt/KDE-affecting bugs in gcc or binutils. > > My being sick. :\ > hope you are feeling better soon. > Maybe :\ I seem to have found a libtool bug on arm today. arts has > failed on 3 archs, arm, mips, mipsel. mips/el are due to the Qt bug. > However, from what pb has said arm appears to have a libtool bug of some > sort. > AIUI from discussions with Scott James Remnant that we really need to replace KDE's libtool.m4.in and ltmain.sh with our own. Scott as fixed several bugs in Debians libtool including various fixes for Arm. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgp32QxgalGvu.pgp Description: PGP signature
Re: KDE 3.2 CVS - problems
On May 26, 2003 at 20:53, Ing. Vladimir M. Kerka praised the llamas by saying: > Hi, James, > thank you for your great work at KDE 3.2 CVS deb. I installed them last > night, installation went very smoothly and almost all is very fine. > There are several problems I cannot handle myself, so can you give me a > clue? > From the most important to the lesst: > 1. Kgpg keeps crashing, I attached file from backtrace This is to be expected. It is a development version. Have you filed a bug with upstream? http://bugs.kde.org > 2. there was no konqueror icon on the kicker, there was written (in pop > up) /usr/share/applnk/Internet/konqbrowser.desktop is missing - I found > it in /usr/share/applications and copied to previous mentioned location, > it seems now is it OK Kicker needs to be changed. The desktop files sould be in /usr/share/applications and not in /usr/share/applnk. I should be able to look into this in the nexr couple of days when I get my development machine back up and running. > 3. when I tried to install kdevelop, installation keeps on uninstalling > gideon - both packages are listed in your repository This is also to be expected. They are 2 versions of the same software. They will conflict with each other. Use gideon over kdevelop and file bugs with upstream if you find any. > 4. I cannot install package qsa, which is also listed in your > repository. why is this? what was the problem? > Thank you once more for your packages, I am really happy with the new > KDE. Thank you for your bug reports. -- David Pashley [EMAIL PROTECTED] pgpTv4Exjp2Lh.pgp Description: PGP signature
Re: Diff against faq.xml
On May 01, 2003 at 04:24, Jeff Bonham praised the llamas by saying: > I just fixed up a bunch of typos and misspellings. > Applied and uploaded Many thanks -- David Pashley [EMAIL PROTECTED] pgpsRFY4Atzvq.pgp Description: PGP signature
Re: Making PDF via KWord
Aryan Ameri said, and I quote: > Hi There: > > When I want to make a PDF document with KWord (Using print menu), KWord is > able to make a pdf file, but the result is crappy, many words are not in > their original position, and all in all, it is unreadable. However, making > PostScript files works fine, but anyway, windoze users can't view PS files. > > Is there any reason why the resulted PDF files are like this? Any way I can > repair this? You could try using ps2pdf to convert it. I'm afraid I don't know why it is not working, but you may want to see if any other applications has problems printing to pdf and if so file a bug with kprinter or with koffice depending if the problem is global. > > BTW, I am using KOffice 1.2.1, on KDE 3.1.0 RC 5 > It may be worth trying the 3.1.1 debs in sid. > Cheers -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgprsrRBSkzuP.pgp Description: PGP signature
(forw) [Bug 51427] lisa should be silent when starting
This should make lisa a bit nicer during start up. - Forwarded message from Alexander Neundorf <[EMAIL PROTECTED]> - From: Alexander Neundorf <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Bug 51427] lisa should be silent when starting Date: 18 Mar 2003 20:54:18 - Message-ID: <[EMAIL PROTECTED]> --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. http://bugs.kde.org/show_bug.cgi?id=51427 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-18 21:54 --- Ok, I added the command line option -q / --quiet in HEAD branch. Until then you could try to redirect the standard output to /dev/null Alex - End forwarded message - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpkX0IuLD6Dm.pgp Description: PGP signature
Re: Menus & toolbars all screwed up.
Doug Holland said, and I quote: > Since I updated my system using dselect, menus & toolbars on many programs > are > seriously screwed up. I get doubled entries, doubled toolbars, menu items > saying "No text!" and so on. > > What happened to my menus and how do I fix it? > > Check that you have a /etc/kde3/ui/ui_standards.rc file. Re-install kdelibs-data. apt-get install --reinstall kdelibs-data -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgptctL4D8qmu.pgp Description: PGP signature
Re: Patch for the David Pashley FAQ
Chris Harris said, and I quote: > This patch updates a few incorrect URLs and cleans up > some wording ever so slightly. I have been careful not > to screw up the SGML, but I have not run it through a > parser to make sure it is correct. Sorry. > > -Chris > I've updated the faq and is now being uploaded. There was one small xml error, but it was easy to fix. Many many thanks. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpP9lfdeIhjF.pgp Description: PGP signature
Re: kwin development files
david david% dlocate kwin | grep include libqt3-dev: /usr/include/qt/qdockwindow.h kdelibs4-dev: /usr/include/kde/kwinmodule.h kdelibs4-dev: /usr/include/kde/kwin.h kdelibs4-dev: /usr/include/kde/kdockwindow.h kdelibs4-dev: /usr/include/kde/kwindowlistmenu.h kdelibs4-dev: /usr/include/kde/kwindowinfo.h kdebase-dev: /usr/include/kde/kwin kdebase-dev: /usr/include/kde/kwin/options.h kdebase-dev: /usr/include/kde/kwin/client.h kdebase-dev: /usr/include/kde/kwin/workspace.h kdebase-dev: /usr/include/kde/kwin/kwinbutton.h libgtk1.2-dev: /usr/include/gtk-1.2/gtk/gtkwindow.h /me would like to point out the pure funkyness of highlighting something in linux and pasting it on a windows machine using VNC. - Original Message - From: "Rene Horn" <[EMAIL PROTECTED]> To: Sent: Monday, February 03, 2003 10:16 AM Subject: Re: kwin development files > Sorry, I forgot to mention some other information. > > I am using 3.1, and I'm not on the list. Please CC me. > > RENE E HORN > Internet - [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: mp3 support for kio_audiocd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 12 January 2003 15:51, Ralf Nolden wrote: > On Sonntag, 12. Januar 2003 15:55, Sven Bergner wrote: > > Hi list, > > I have the kio_audiocd installed on my machine. I used the package from > > Ralf. It shows me the tracks and gets the title of the tracks from cddb. > > Thats ok. But I have only a ogg vorbis subdirectory and no mp3. What do I > > have to do, to get a mp3 directory? > > I hope someone can help me. > > The reason for that is that I don't have liblame installed in my build > environment because liblame is GPL but still, the encoding to mp3 is quite > problematic license-wise. This is the reason why SuSE doesn't compile > kdemulitmedia with liblame either. > > Now, what they do is if you install liblame afterwards, you can ripp to > mp3. I'll try to make this work the same way; if it doesn't work I'll > provide a separate package for kio-audiocd that works with liblame > installed. > > Ralf > AIUI you need liblame-dev installed during building. As this does not ship in Debian, the offical packages will not support ripping MP3. If kio_audiocd detects liblame existance at run time without needing liblame-dev during build then it may be supportable. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+IZU/YsCKa6wDNXYRAvGvAKCYhD3TnFopmU2uaUJnA2fhwacclwCeL+Hr KpSk8SX0TdS4inDrcw79vno= =PAFC -END PGP SIGNATURE-
Re: kio_audiocd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 12 January 2003 05:48, Anthraxz __ wrote: > If I try to convert audio cd to mp3, I type > audiocd:/ > in konqueror and I get these message : > > "can't find kio_audiocd" > > I use kde 3.1 rc6 from > > deb http://ktown.kde.org/~nolden/kde/woody/i386/ ./ > > installed today with the command ( I had removed previous installation) > > apt-get install arts kdelibs kdebase kdenetwork kdepim kdegraphics kdeadmin > kdemultimedia kdegames kdevelop kdm > Can you reply with the results of: dpkg -l kio-audiocd dpkg -L kio-audiocd apt-cache show kio-audiocd locate kio_audiocd - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+IWttYsCKa6wDNXYRAt5+AJ4ht8vTSnND4agt6wWn5za8bDG0hwCdGgBL wg2bkNXCj5+ofdWu2ZMFNq4= =C6dO -END PGP SIGNATURE-
Re: bug in cleaning cache
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 12 January 2003 05:52, Anthraxz __ wrote: > The first time I try to clean the cache from the control panel of kde 3.1 > rc6, the panel crash. > > I had never used konqueror before cleaning the cache, so the directory > ~/.kde/share/cache does not exist at this time. I suppose kde does not > check if the directory exist before trying to remove it's content. > Please submit this to bugs.kde.org. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+IWq9YsCKa6wDNXYRAgKiAJ9QTr4TLVnWUHXnstzZxxM4RlWgLgCfcQBX XUGd4Qr6rLbH0YS1juqjrNc= =wCXw -END PGP SIGNATURE-
Re: Kacpi error: Qt (>= Qt 3.0.3) (library qt-mt) not found
suresh Sharma said, and I quote: > hi, > I have a debian testing on my sony vaio laptop . > I have acpi support in my kernel verion 2.4.20 ( ACPI patch ) . > I was trying to install Kacpi from source but > when I do ./configure I keep getting error > this error . > "checking for Qt... configure: error: Qt (>= Qt 3.0.3) > (library qt-mt) not found. Please check your > installation!" > > I checked what version of libqt-mt-dev I have and it > is 3.0.5 > I did dpkg -l | grep libqt > ii libqt2 2.3.2-5Qt GUI Library > (runtime version) > ii libqt2-mt 2.3.2-5Qt GUI Library > (runtime threaded version) > ii libqt3 3.0.5-3Qt GUI Library > (runtime files) > ii libqt3-dev 3.0.5-3Qt GUI development > files > ii libqt3-mt 3.0.5-3Qt GUI Library > (Threaded runtime version) > ii libqt3-mt-dev 3.0.5-3Qt Threaded > development files > > so why is it still complaining > help !! > I relatively new to this linux world so pls bear with > me . > > thanks > suresh > Please run g++ --version and confirm that you are using gcc 3.2.2. If so then this will not work until Qt has been uploaded to sid and rebuilt using the new default compiler. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpKVEKuh9HFe.pgp Description: PGP signature
Re: more apps, and sources :-)
Ralf Nolden said, and I quote: > On Freitag, 10. Januar 2003 13:36, Karolina Lindqvist wrote: > > fredagen den 10 januari 2003 12.32 skrev David Pashley: > > > The most useful thing atm would be writing man pages. Check > > > http://webcvs.kde.org in the debian dir for binaries that do not have a > > > sgml document. You can use one of the existing sgml docs for a template. > > > > I have written man pages for almost all baseline KDE applications (259 so > > far). So there is no need to do that job again. Of course, it is always > > possible to dig deep down in the specific program, to find the very special > > information that should be in the manpage. But for that you have to > > understand C++ and KDE reasonable good. > > So it's just a matter of adding your manpages to CVS ? coolness. David, > Chris, > Daniel, anyone ? > If someone emails either one of the people Ralf listed or to the mailing list we will add them pretty much straight away. Are they in sgml/xml or roff? I have also added a question to the Debian-KDE faq at http://www.davidpashley.com/debian-kde/faq.html as to what people can do to help. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpk9dyiQaIHn.pgp Description: PGP signature
Re: more apps, and sources :-)
Sergio Rodriguez de Guzman Martinez said, and I quote: > [EMAIL PROTECTED] (2003-01-10 at 1152.02 +0100): > > > > Also, it would be nice if someone would care about a debian.kde.org (or a > > kde.debian.org respectively) webpage to collect all the info for KDE on > > debian and fill that with content about new apps, where to get KDE for > > woody/sid and how to install it, which features you could use, deblines etc. > > > > Ralf > > I could help maintaining this webpage. I think that idea would help a > lot of people as it may be a way of joining many information collected > from lists, news, etc.. > > Sergio. > > If I understand Ralf correctly, this will be a CVS module so anyone with a KDE CVS account will be able to change it. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgp2EInnRVGlU.pgp Description: PGP signature
Re: KDE development for debian (was: Re: Test request (was: Re: Small strange problem))
Ralf Nolden said, and I quote: > On Sonntag, 5. Januar 2003 14:13, tomas pospisek wrote: > > On Sun, 5 Jan 2003, Karolina Lindqvist wrote: > > > If we could coordinate our findings and efforts there would be much > > > better packages for sid, than if everyone have to find exactly the same > > > things separately again and again. My packages are not just CVS snapshots > > > and a clone of the CVS ones, but contain a lot of work that is not in the > > > CVS. Some of it can be discussed, some does not belong and some is > > > bugfixes or enhancements. > > > > Why don't you just get yourself a CVS account for KDE and do the work in > > the CVS repository? That's IMHO one of the easiest ways to communicate. > > That way everyone _has_ to make sure they're in sync with other people's > > reality and _have_ to make sure stuff works for everyone, work is not > > duplicated etc > > *t > > I requested a [EMAIL PROTECTED] mailinglist this morning after Karolina's > suggestion and will ask David to give her a CVS account. > Why do we need a [EMAIL PROTECTED] We have this mailing list and if needs be we can ask for a [EMAIL PROTECTED] -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgptup9VcAYOH.pgp Description: PGP signature
Re: more apps, and sources :-)
Graeme Merrall said, and I quote: > On Fri, Jan 10, 2003 at 11:52:02AM +0100, Ralf Nolden wrote: > > > Yes. What you could do is two, three things: > > Is there any help you need specifically for getting debian-kde besides > the web page? > > Cheers, > Graeme The most useful thing atm would be writing man pages. Check http://webcvs.kde.org in the debian dir for binaries that do not have a sgml document. You can use one of the existing sgml docs for a template. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpgK0wDjttOo.pgp Description: PGP signature
Re: Magiconf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 December 2002 13:11, Richard Ibbotson wrote: > Hi > > Those of you who have taken an interest in our Magiconf project might > like to know that the latest source code has been uploaded... > > http://magiconf.sheflug.co.uk/ > > Please feel free to browse the site. > > -- > Merry Christmas :) > You may want to mention this to [EMAIL PROTECTED] - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9/esWYsCKa6wDNXYRAv7bAJ91ReAL0FD3jWDDsekZoTCcZk112gCfdRsX 0LFc4iHiTA1OckiEQljDqkE= =1WP7 -END PGP SIGNATURE-
Re: Relation of debs and KDE CVS?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 26 November 2002 10:22 pm, Michael Schuerig wrote: > he debian-related changes flowing back into the main KDE CVS > so that it would be possible (with some work...) to build packages from > the latest CVS state? It should be possible to build debian packages straight out of CVS. You may have issues with some modules, but as we are currently in a feature freeze, there should be no problems with files being moved around, breaking the builds. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE95J46YsCKa6wDNXYRAg/iAJ42FMaPPzUxQRGNd/dvbneHz8VRGgCfVw/s xThdxTgNgBuCjrKQTwCSxng= =rFFA -END PGP SIGNATURE-
Re: Pencam2 KDE blues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 26 November 2002 4:56 pm, Laura Rudmin wrote: > Hi, > > I have a STV*** -style digital camera, an ARGUS DC1500. This is the > same camera > that works with the package "Pencam2". > > I'm running KDE 3.0.4 on unstable (SID) debian, 686 computer. > > I noticed that the images, when I download them to Linux (not Win98 -- > that's okay) look > dim and blue. Now, with Pencam, there is a setting or flag you can > adjust so that they will > download okay. But with KDE, I don't know of any such settings. > Indeed, when I click > setup in "Control Center/Peripherals/Digital Camera", I see "no settings > necessary". > > If I remember, the explanation is that there are 4 bits, and sometimes > the bits are > set one way, and sometimes they are set the other -- you have to pack > them into the image correctly > to get the correct results. > > Does anyone know how to fix this? > > QUESTION 2 >I notice that there are no previews for .pnm files on my pencam. It > might be nice to get them. > If anyone knows how to get previews there, please say. Otherwise, it > might make a good additional > development. I know that if I double-click the image, I can view it. I have a l'espion with is much the same thing. KDE 3.1 does have previews for .pnm files. I don't know about any earlier versions. As for being blue, I don't seem to have this problem, but I do when running it as a webcam. I know there is a switch for the kernel module to fix this. As KDE just used gphoto2, I suggest you email them wrt to the blue images. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD4DBQE95J05YsCKa6wDNXYRAsjHAKCVPeJIwlmC+bVq3q7ddDHga2QigQCYpbD6 DeEbEUXWxMCfEmg2pqAEuw== =gXvj -END PGP SIGNATURE-
Re: Backtrace mentions "__check_rhosts_file" !?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 20 November 2002 1:58 am, Nick Boyce wrote: > On Tue, 19 Nov 2002 11:53:45 +0000, David Pashley wrote: > >On Tuesday 19 November 2002 2:28 am, Nick Boyce wrote: > >> ... why does every KDE crash dump (= backtrace) I > >> see include the line > >> > >> #1 0x40dcae48 in __check_rhosts_file () from /lib/libc.so.6 > > [...] > > >You are better off asking the kde mailing list. Look at http://www.kde.org > > for mailing list information. Alternatively, grep the sources. > > Yeah - I guess you're right - sorry, wrong list ... > > > ... It would be helpful if you posted the entire backtrace (or at > >least the few lines around that), so we can see the context. > > FWIW, here's a bit more : > (the crash was the klisa ioslave in konqueror, KDE 2.2.2) > ==< cut >=== > (no debugging symbols found)...(no debugging symbols found)... >[lots more lines just the same snipped] > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...0x40d53a59 in wait4 () from > /lib/libc.so.6 > #0 0x40d53a59 in wait4 () from /lib/libc.so.6 > #1 0x40dcae48 in __check_rhosts_file () from /lib/libc.so.6 > #2 0x405944d8 in KCrash::defaultCrashHandler () from > /usr/lib/libkdecore.so.3 > [snip] > ==< cut >=== > > I'm not going to dwell on it though - klisa having an imminent > security fix and all .. but I will repost my general query to > kde-linux. > As you can see this is being called from KCrash, so every time the program crashes, it calls this function. not too sure why. > BTW I just did some Googling on this, and the __check_rhosts_file call > seems to appear in every bugzilla-reported backtrace there is ! That > seems to include Gnome app crashes as well, so maybe it's not a > KDE-related thing. > - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE92w4IYsCKa6wDNXYRAi/AAJ9THaBZWLBHvah1OwXP5ghwMWnvRACfeujD hU61SruwVgnsCjo4jX9kJpY= =wCV8 -END PGP SIGNATURE-
Re: Stuck trying to build kdepim
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 18 November 2002 6:23 pm, Alan Chandler wrote: > Help > > I have slowly managed to build .debs of all of kde except kdebindings and > kdepim. kdebindings I can live with, but kdepim is particularly an area I > want to test. > > I am pretty up to date with the CVS version, and I am using the debian way > (ie using dpkg-buildpackage -b -uc -us to build the debs (using g++-3.2 and > I have build and then installed debs back to qt-copy) > > It gets to the point of building kalarm and it fails with the messages > below > > It looks to be going wrong in editdlg.cpp which includes someway > down its list of includes. I can't find anything obviously wrong with the > code and it doesn't look like the kde cvs has had any recent changes. > > The initial lines it is reporting as wrong in qdir.h are just blank lines. > > Since when does the compiler take blank lines as the end of a statement? > [snip compiler output] > and a lot more errors before eventually giving up > This looks like an enable-final issue. Try using DEB_BUILD_OPTIONS=debug dpkg-buildpackage While enabling debuging output, it will disable --enable-final. Don't worry about increasing the size of the binaries as they are still stripped. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE92ilNYsCKa6wDNXYRApZyAJoDfEl+a4ji+VlGeHrEH4Z35TDWwACdHMuY gsk5qkV38KsDqEnW8Vfy3UY= =lBq9 -END PGP SIGNATURE-
Re: question about locally compiled software
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 19 November 2002 11:00 am, Warren Turkal wrote: > Is there any way to make kde realize the location of things like icons and > the like for application that are "make installed" into /usr/local/? Could > the default KDE paths be changed to include the /usr/local/ as well as the > /usr/ hierarchies so that I could just plug a locally compiled app in > instead of having to specially configure? > Thanks, Warren > > BTW, I am not subscribed. Please CC: any replies. > -- > Treasurer, GOLUM, Inc. > http://www.golum.org This was mentioned recently on the list. It is noted and will be looked at. If kde3.1 still doesn't support this *WHEN IT IS IN SID*, then file a bug. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE92ihiYsCKa6wDNXYRAhpPAKCmYmEi5dRJGep1Z9PfBq8sBTby4gCfRFcd ydspbHqk4UFxA0y9DuTW4SA= =bKWR -END PGP SIGNATURE-
Re: Backtrace mentions "__check_rhosts_file" !?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 19 November 2002 2:28 am, Nick Boyce wrote: > Since we seem to be quiet at the moment, I thought I'd ask something > that's been bugging me : why does every KDE crash dump (= backtrace) I > see include the line > > #1 0x40dcae48 in __check_rhosts_file () from /lib/libc.so.6 > > (where the virtual address may vary) ? > > The presence of that "__check_rhosts_file" string always worries me - > surely nothing should be looking for an rhosts file unless I'm using > one of the hideous "r" commands (which I never am) ? > > (Sorry if this is a dumb question - I'm not a KDE programmer.) You are better off asking the kde mailing list. Look at http://www.kde.org for mailing list information. Alternatively, grep the sources. Sorry, but most people here are users and the packagers don't tend to do that much with the actual source code. I would imagine that it will be in kdelibs or qt. It would be helpful if you posted the entire backtrace (or at least the few lines around that), so we can see the context. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE92iZJYsCKa6wDNXYRAhvfAJ9K0UKSa2VHYJb5c0HTn4G67mXrEQCcDH56 /ztXikwCdqvUTn/tbMSICkQ= =FsG/ -END PGP SIGNATURE-
Re: Issues with Debian packages of KDE3 and locally installed software
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 11 November 2002 1:54 pm, Daniel Burrows wrote: > (aside: please Cc me on replies, I'm not subscribed) > > Michael Schuerig <[EMAIL PROTECTED]> writes: > > On Monday 11 November 2002 02:03, Daniel Burrows wrote: > > > This appears to be some sort of problem with the KDE settings: the > > > search is performed from what appears to be a library function, > > > "locate", and this function doesn't search in /usr/local for data > > > files. > > > > It searches in KDEDIRS (plural, see below) and ~/.kde > > > > > Presumably there's a setting in the KDE libraries that could get it > > > to behave properly. I tried modifying /etc/kderc, but it seems to be > > > ignored, or maybe my guess at what should be in this (entirely > > > undocumented) file was wrong. After poking around a bit more, I > > > tried setting KDEDIRS to /usr/local, and the program ran. > > > > > > This probably should be fixed in the packages (preferably before > > > you release them to unstable, or at least a bit afterwards) > > > > No, the packages are fine, as far as I can tell. Just set KDEDIRS > > appropriately. I have the following line in /etc/environment > > > > KDEDIRS=/usr:/usr/local/kde:/usr/local > > Hi, > > I think you misunderstood me -- a default installation of Debian KDE3 > does not allow programs to be installed in /usr/local. This is Not Right. > I don't care if I can work around it by setting an environment variable, > changing a config file, or standing on my head and reciting the alphabet > backwards, it should work properly in the first place. > Calc, I had a quick look in kstandarddirs.cpp. I think we need to add "prefixes=/usr/local" to /etc/kderc. I haven't tested this yet, but I will try later. I don't know if we need to include /usr in there too. I doubt that we do. I don't think that we should support any more locations as standard. Maybe a note in README.Debian about $KDEDIRS. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9z8IxYsCKa6wDNXYRAg16AKCRJxX0KyKk08fIlfVZzXM4dkydfACgiFmF TjNp/OxDEXACuPLP/MkkrMw= =p92c -END PGP SIGNATURE-
Re: KDE3.1, qt3.0.5 and GCC3.2???
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 11 November 2002 2:00 pm, Giles Constant wrote: > On Sun, 10 Nov 2002, John Gay wrote: > > I am getting ready to wipe my Debian Woody system and replace it with a > > self-compiled Linux including the latest bells-N-whistles I could find. > > If you want to compile your entire system up yourself, you might want to > look at gentoo (www.gentoo.org). It's based on the BSD portage system, so > it compiles absolutely everything when you install it. > > It took me from 10am until about 2am to get my Athlon-XP 1.8 running KDE > from scratch, and it's still not quite how I want things, but it was worth > it :-) Everything was compiled with gcc-3.2 and -mcpu=athlon-xp, etc. apt-get install apt-src or apt-get install apt-build - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9z71mYsCKa6wDNXYRAkaKAJ49ctobhoDriXR5tHXSgXP3hGWlpgCgoJEo 4q9W8TJtuGs1r+FTeujM3LE= =B7pq -END PGP SIGNATURE-
Re: Release date for KDE package??
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 08 November 2002 10:33 pm, Michael Peddemors wrote: > Chris looks a tad busy, anyone have anyfurther info on releasing a 3.1RC > package? Anyone have a development package source to use/tryout? > -- If you want to build the current packages then you can check them out of CVS and run debuild -us -uc in each of the directories. Check www.kde.org for details on checking out CVS. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9z3kLYsCKa6wDNXYRAkFsAJ490S4fdmy58BULOLc7MyODs4mN3gCfYFoT sSfyIwEjCwUxvKIUA36qZ6I= =gvL6 -END PGP SIGNATURE-
Re: licq
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 05 November 2002 9:33 am, Nikita V. Youshchenko wrote: > New licq in unstable has no kde plugin. > Bad. Not knowing anything about licq, I assume this is due to the lack of KDE3 in sid. Presumably when KDE 3 is in sid, the kde plugin will be rebuilt. I suggest checking the bug list for licq and file a wishlist bug for it if one has not already been filed. Please point out that KDE3.1 will hopefully be in sid soon. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9x5cxYsCKa6wDNXYRAis9AKCJkH8PEKxsdGIjo7HK/XDd2ajZMwCgnOyy Amt5kqm/3vAEuIFIhypwCbA= =zDBJ -END PGP SIGNATURE-
Re: KDE debian-related CVS commits
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 29 October 2002 12:15 pm, Ben Burton wrote: > So here's a thought. Would anyone be interested in setting up > [EMAIL PROTECTED] (or something similar) for distributing > notifications of commits beneath KDE debian directories? > > We could either do this by putting a rule in KDE's CVSROOT/loginfo with the > regex "/debian" (or whatever) to forward all such commit notifications to > this list, or we could have some account somewhere or other subscribed to > [EMAIL PROTECTED] with a procmail rule to forward all debian commits and dump > all others. > > This way it could be easier for packagers and other interested parties to > keep track of what's happening with packaging in CVS without getting commit > notifications for all of KDE. > > Anyway, just an idea. > I have spoken to KDE about this, and they will not do it for us. I am subscribed to kde-cvs and can set up a very dumb forwarding for debian commits. emai me if you would like to be added to the list. I can only take a few, so first come, first served. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9wB9uYsCKa6wDNXYRAi4uAJsGJZ5/j4pXbfqAGAO4QTIl1g4NfgCeJZlK N+KhPE43GRzWI7CSFmdod14= =+fvX -END PGP SIGNATURE-
Re: OpenPGP Plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 23 October 2002 12:28 am, Hasso Tepper wrote: > David Pashley wrote: > > It is a bit easier than ralf thinks, but still not particularly > > easy. > > > > run: > > apt-get install libgpgme-dev > > apt-get source libgpgme6 > > > > cd in to gpgme source dir > > edit debian/rules and add --enable-gpgmeplugin to the configure > > line [0] run debuild -us -uc > > then copy the debian/tmp/usr/lib/gpgme dir to /usr/lib > > > > In kmail, load both of the .so files in /usr/lib/gpgme. You should > > fine that they now work. > > > > NOTE: THIS IS NOT SUPPORTED AND THE FILES WILL NOT BE DEALT WITH BY > > THE PACKAGING SYSTEM > > > > [0] You will need to check the correct name for this option. use > > "./configure --help" > > But it is not enough to _use_ plugin. You will need gpg-agent and > pinentry as well. > It will allow you to read PGP/MIME emails, but not send them. > -- > Hasso - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tmQ0YsCKa6wDNXYRAsdfAJ9gtOL2gzUP5W/pL2xlXoI1k2TbkQCgpJzC x7r2/cnO5oXGSTn5j/6GYHU= =yFOB -END PGP SIGNATURE-
Re: cpu optimisation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 21 October 2002 7:38 pm, Frank Van Damme wrote: > Hello, > > Every now and then I compile kde packages which didn't make it in the kde3 > distribution (yet). I usually make debian packages out of them, which > involves nothing more then configuring the thing and running dh_make and > dpkg-buildpackage in the source dir; then installing the .deb package . > > But debian has a habit of compiling everything so that it still runs on a > 386. Since I am only installing those packages on my own machine, I would > like to know what to manipulate to make these packages optimised for my cpu > (athlon). > > Thx! > david david% apt-cache show pentium-builder Package: pentium-builder Priority: extra Section: devel Installed-Size: 44 Maintainer: Alex Pennace <[EMAIL PROTECTED]> Architecture: all Version: 0.18 Depends: gcc | g++, perl Filename: pool/main/p/pentium-builder/pentium-builder_0.18_all.deb Size: 6894 MD5sum: df2e717efdf6c599929f1e0bb5dc511d Description: force pentium optimized compilation Replaces gcc, cc, and g++ with scripts that build pentium optimized code. (Other processors can be optimized for as well.) . By default, after installing this package, the compilers will behave normally. However, if the environment variable DEBIAN_BUILDARCH=pentium is set, they will enter pentium optimized compile mode. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tXwrYsCKa6wDNXYRAny0AKCE3eYew8XWLtfcahJtC5sAVwe+RQCfTID+ +LPfu2OBAeCRklnwbNLOdZc= =mMNt -END PGP SIGNATURE-
Re: OpenPGP Plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 22 October 2002 4:55 am, Ralf Nolden wrote: > On Monday 21 October 2002 23:34, Oracle Administrator wrote: > > KMail complains when I click on certain messages with the dialog that the > > openpgp plugin is not installed. > > > > I am running Debian unstable and apt-get update nightly. > > > > How can I install this plugin? > > That's quite complicated and is not yet available as a deb package. It is > included in the Ägypten project that is connected to the S/MIME stuff. > > http://www.gnupg.org/aegypten/ > It is a bit easier than ralf thinks, but still not particularly easy. run: apt-get install libgpgme-dev apt-get source libgpgme6 cd in to gpgme source dir edit debian/rules and add --enable-gpgmeplugin to the configure line [0] run debuild -us -uc then copy the debian/tmp/usr/lib/gpgme dir to /usr/lib In kmail, load both of the .so files in /usr/lib/gpgme. You should fine that they now work. NOTE: THIS IS NOT SUPPORTED AND THE FILES WILL NOT BE DEALT WITH BY THE PACKAGING SYSTEM [0] You will need to check the correct name for this option. use "./configure - --help" - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tXmwYsCKa6wDNXYRAsORAKCHpmVEOdSA7pDV29gui4N8sPgFXgCfVlAf IjE1eKlf0FW+8tEb91iKiLA= =uMeX -END PGP SIGNATURE-
Re: How I get KDE 3 on Woody?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 18 October 2002 2:40 pm, Fran Ramírez Guerrero wrote: > Hi all :) > Anybody knows how can I update KDE 2.2 to KDE 3.3 on woody i386? Or I have > to download all the packages in the KDE ftp and install all them? Thx > > ___ >_ Para recibir mejor tus mensajes, utiliza un PC más puntero! Aprovéchate de > las mejores ofertas que Dell te propone en exclusiva en i (españa) > http://www.iespana.es/_reloc/email.dell A search of the archives to this mailing list would show you that http://www.davidpashley.com/debian-kde/faq.html would have been a good starting point. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9sCXNYsCKa6wDNXYRAgAUAJwIOsPpoysMOzrGf3KNG5LFK045fgCgladF WS9h2FfEMs2FlWaPTFMrwhU= =efaR -END PGP SIGNATURE-
Re: [debian-kde] List configuration & usability
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 10 October 2002 1:19 am, Nigel A. Chapman wrote: > It has occurred to me that I could probably set up filtering in Mozilla > to use the X-Loop (or some other) header as a send-to-a-folder criterion > to get around this, but (1) there will be lots and lots of potential > users who wouldn't think of that, (2) no other list I subscribe to > requires this and (3) I'm not yet sure of the value of belonging to this > list, due to this problem, so I'm not too inclined to spend a much time. > looking into that. Maybe that's lazy, yes. :) X-Mailing-List is probably your best bet. easily doable in kmail, exim, procmail or others. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qoE6YsCKa6wDNXYRAsYAAJ92r48iXS4kDeTjUmrxanUvQQuaWACgiG8n wHYS+pLRHOpsaom2Wz5vYnw= =8+tO -END PGP SIGNATURE-
Re: Konqueror + Debian + IPv6?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 12 October 2002 6:56 pm, Felix Homann wrote: > Hi, > > some webpages take extraordinary long time to load in Konqueror (all the > 3.0.x versions) on Debian (e.g. www.golem.de) while they load fast in > Mozilla or Konqueror on SuSE. > > I remember someone posting this had something to do with IPv6 being > compiled as default into KDE (something like: konqueror tries to establish > a IPv6 connection to the server say 20 times until it falls back to > IPv4??). I don't know if this is true, but it's really annoying. > > Does anybody know what's exactly happening? > Can I do something about it without recompiling KDE? > Should/could the Debian packages be build with more comforting options? > > Regards, > > Felix using 3.0.8, taken from CVS on monday, the address you gave loaded konqueror and displayed in about 5 seconds. Didn't notice any difference to other sites. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qGSOYsCKa6wDNXYRAiGVAKCBSUYeD7mznwHBEcnMqxncwV/U0wCeKKpC jAalsFHRu/j9b04dsm9OqVk= =OGY9 -END PGP SIGNATURE-
Re: Question about upgrade KDE 3.0.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 12 October 2002 6:12 pm, Charles de Miramon wrote: > > First Question: Does KDE 3.0 really work with Debian (I rather suspect > > something that hasn't made it into Debian's STABLE source yet). > > KDE 3.0.4 works well on Debian and is in my opinion more stable than KDE > 2.2. I think you should upgrade if you use your computer mainly as a > Desktop. If you use it as a server and use KDE only to fire some xterms. > Maybe, you can wait. > > > Second Question: Can anyone tell me how to properly set DSELECT to a > > valid source? Alternatively, if I have to download and compile myself > > (usually through the make series or whatever), do I have to do anything > > else to properly register KDE 3.0 with APT/APT-GET/DSELECT so that I > > don't find KDE downgraded sometime later? > > > >- Mike > > The easiest way is to dist-upgrade to sid and follow the instructions on > http://www.davidpashley.com/debian-kde/faq.html and related links. > Remember that you must first remove completely KDE 2 before installing KDE > 3. These faqs have not been updated for the new apt line for KDE 3.0.4. > which is for sid : Now Updated. Any furthur changes that need to be made, please feel free to send patches. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qGCHYsCKa6wDNXYRAg1TAJ0cJKYcBlMsg05o+ZYXrBYEFts/rwCeOkGc d+dFtO2hquZh84OnWRVUBH4= =A8qs -END PGP SIGNATURE-
Re: KMail, pgp5 and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 October 2002 10:49 am, Pablo de Vicente wrote: > Hello, > > I have run into some trouble with KMail, gpg and pgp5i. I will expose the > case: > > I usually use pgp5i and have exported my public key to a keyserver. Before > doing that I checked that using PGP5i in different machines and with > different identities KMail worked fine, detecting the validity of > signatures. > > The problem arises when people who only use GnuPG import my public key > from the keyserver. All emails from my address appear in Red in their Mail > folders and with a "Warning: The signature is bad" message. These people > use, under KMail -> Settings -> Security -> OpenPGP option "Select > encryption tool to use: GnuPG". > I can confirm that this does happen in KDE 3.1beta2. > If the previous option is set to: "Autodetect", then the email will appear > in yellow with a "The validity of the signature can't be verified" message. > > However if one only uses KMail with PGP5 (for which one imports my public > key from the keyserver) the emails appear in green and with a "The > signature is valid and the key is fully trusted" message. > > Is there some kind of incompatibilty between GnuPG and PGP5i?. Is this a > KMail problem which, when using GnuPG does not recognize the validity of > messages signed with PGP5i?. > > On the other hand Kmail works fine the other way round, that is messages > signed with GnuPG are correctly verified. > > Any ideas? Have you emailed [EMAIL PROTECTED] They are the KMail developers. they should be able to help you more. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oq04YsCKa6wDNXYRArgBAKCdlMcgZ8PJ8z561azf9qnnTWWAzQCgmRE2 jQzZFDZxVBNjWMH1jg3Tb+8= =Lbsk -END PGP SIGNATURE-
Re: Problem with konqueror 3.1beta2 and a website
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 07 October 2002 10:48 am, Rob Lensen wrote: > Hello, > > I just installed the kde3.1beta2 packages and they are working fine. > But this http://forum.bsdfreaks.nl forum ain't working well. > It worked in kde3.0. I made a screenshot what it is look like > http://www.bsdfreaks.nl/files/forum.png > The problem is that the text is displayed outside the forum (as you see > on the screenshot) > Is this a bug in konqueror or is it a bug in the website? Galeon and > mozilla have no problems with this. > I would check the page with the validator at www.w3c.org first. If you have kdeaddons installed then konq should have a menu option in the tools menu. If it doesn't validate then there isn't much point in filing a bug with KDE. I would complain to the website though with a link to the validator test. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oVvzYsCKa6wDNXYRAt8hAJ9MxXhwUdqwAhS4aXujY7Dj7KSBQgCfU5x0 I7W76Qx6YqcOzsNectbPP1o= =md7k -END PGP SIGNATURE-
Re: kde3, xinerama, and xfs (x font server)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 06 October 2002 5:53 am, Rob Weir wrote: > On Fri, Oct 04, 2002 at 10:06:39AM +0100, David Pashley wrote: > > don't use xfs. seriously. There is no reason these days to run a font > > server if you just have a single machine. AIUI, you can't use XRENDER > > with font servers, so you will be able to get anti-aliased text if you > > use one of the local font renderers. > > > > /me awaits the "you should always use font servers" replies > > Not having to fiddle around with font servers (at least with TT fonts) > was one of the coolest things about X4. The downside (as far as I have > been able to figure) is that you have restart X to take advantage of any > new fonts you might install. > "xset fp rehash" should work. AIUI, it reloads the font path info. I would be surprised if it didn't take new fonts into account. > Aside from that, yeah, avoid font servers unless you know why you want > it (sharing fonts over a network). > > -rob - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oBrQYsCKa6wDNXYRAitVAJ9pG3+o64P01MSKGEGzggmitrMtewCfZeqY KraKz1dGMm9OFEtqL9iqktg= =yEvz -END PGP SIGNATURE-
Re: problems with dist-upgrade (libarts)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 05 October 2002 6:54 pm, Fred K Ollinger wrote: > > /home/mschz/ROOT> apt-get dist-upgrade > > [SNIP] > > > (Reading database ... 55855 files and directories currently installed.) > > Unpacking libartsflow-data (from .../libartsflow-data_1.1.0-1_all.deb) > > ... dpkg: error processing > > /var/cache/apt/archives/libartsflow-data_1.1.0-1_all.deb (--unpack): > > trying to overwrite `/usr/lib/mcop/Arts/Synth_ADD.mcopclass', which is > > also in package libarts1 > > Looks like you have two versions of libarts, one of which is being > replaced. > > To me, I think you should have purged kde before you did the dist-upgrade: > > apt-get remove --purge `dpkg -l | grep kde` > This sadly will not work. you need to do: apt-get --purge remove kdelibs4 libarts1 you can then just install kde again. > After you dist-upgrade do: > > apt-get -f install > > if you need to clear things up. > > Good luck, > > Fred Ollinger - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oBQRYsCKa6wDNXYRAoUtAJ4t7qK4xwRnsXiasExiBBodSR9iXgCeN3Ee jN9S9fZti036WmBTrcqR+mA= =k7bx -END PGP SIGNATURE-
Re: kde3, xinerama, and xfs (x font server)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 04 October 2002 3:57 am, Rupa Schomaker wrote: > Problem: Dual Head setup using Xinerama. > > Additional system specs: > > Dell Precision 420 > Dual P3 1Ghz > 1G Ram > ATI Radeon 7500 (2x 1600x1200) > > So, I upgrade to kde3.0.3 using the kd3.org link and restart kdm. > When I login, things seem to start up but the kicker quickly stops > responding (locks up). > > If I remove my .kde dir the preferences window that starts the first > time exhibits the same behavior. > > Some searching on google found a message about disabling xfs to work > around it. Sure enough, commenting out the option in the X config > file allows me to use kde but now my fonts are not what they were > (Emacs uses a wider font, Mozilla doens't "feel right"). > > Thoughts? > don't use xfs. seriously. There is no reason these days to run a font server if you just have a single machine. AIUI, you can't use XRENDER with font servers, so you will be able to get anti-aliased text if you use one of the local font renderers. /me awaits the "you should always use font servers" replies - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9nVohYsCKa6wDNXYRAkH4AJ92LwdHscJ37zTdquXB7kEux6M3HQCgpSnz lNuHvtiLn1Q9IdR+05SRBrs= =fTt2 -END PGP SIGNATURE-
Re: Kmail and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 04 October 2002 2:33 am, bruno randolf wrote: > ok. sorry for my wrong post. i eventually took the time to read the gnu > privacy handbook. what i suggested was nonsense and dangerous. and i'll > never do something like that again, promised... > > what lead me to this stupid workaround was the fact, that kmail 1.4.3 (kde > 3.0.3) refuses to encrypt to keys which are not signed (the old version > allowed this). this behaviour might be right and conforming to the rfcs, > but for casual, uneducated gpg users this is annoying and can lead to such > stupid workarounds. of course it would be best if everybody just read the > manual, but in my case, wouldn't it have been better if i just continued > using the unsigned keys privately? > > anyway, thanks for pointing me to the infos, reading the gpg handbook was > something i always had on my todo list... i'm glad that i've done it now... > > br1 If you really want to be able to encrypt emails to untrusted keys, then you can use --lsign to locally sign the key. You need to check the docs but I beleive that is the correct thing to do. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9nVkYYsCKa6wDNXYRAtEGAKCGce88IMAz4Q0ofuZGyCiK4jP++wCeIozC 2iDdB2IoOKLxUSC7lMY8esA= =olBw -END PGP SIGNATURE-
Re: Kmail and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 03 October 2002 2:50 pm, David Pashley wrote: > On Thursday 03 October 2002 1:19 pm, bruno randolf wrote: > > i'm not sure if this is the problem in your case, but kmail only encrypts > > to keys which are signed and trusted. > > > > so you have to do > > gpg --edit-key > > > > and then: > > Command> sign > > ... > > Command> trust > > ... > > Command> save > > > > after that you are able to select the key when you encrypt a message. > > [snip] > > /me has found another person to not trust > david david% gpg --edit-key E5FA70BF pub 1024D/E5FA70BF created: 2002-06-14 expires: never trust: -/- sub 2048g/6C0F3248 created: 2002-06-14 expires: never (1). Bruno Randolf <[EMAIL PROTECTED]> Command> trust pub 1024D/E5FA70BF created: 2002-06-14 expires: never trust: -/- sub 2048g/6C0F3248 created: 2002-06-14 expires: never (1). Bruno Randolf <[EMAIL PROTECTED]> Please decide how far you trust this user to correctly verify other users' keys (by looking at passports, checking fingerprints from different sources...)? 1 = Don't know 2 = I do NOT trust 3 = I trust marginally 4 = I trust fully 5 = I trust ultimately m = back to the main menu Your decision? 2 pub 1024D/E5FA70BF created: 2002-06-14 expires: never trust: n/- sub 2048g/6C0F3248 created: 2002-06-14 expires: never (1). Bruno Randolf <[EMAIL PROTECTED]> Please note that the shown key validity is not necessarily correct unless you restart the program. Command> quit - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9nFq5YsCKa6wDNXYRAjwNAKCQ8dg2pNmdRIRCJA9avGJmbMx09gCdFUg/ OqKchnjQ7OlybC02Q0h2Cig= =jATY -END PGP SIGNATURE-
Re: Kmail and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 03 October 2002 2:40 pm, Russell Coker wrote: > On Thu, 3 Oct 2002 15:17, Ben Burton wrote: > > > so you have to do > > > gpg --edit-key > > > Command> sign > > > Command> trust > > > Command> save > > > > No! You should only ever sign a key if you can be sure the key belongs > > to the person who claims to own it. This generally means you have > > received the key (or its fingerprint) through a non-electronic medium - > > such as in person on a slip of paper - and you have verified the identify > > of its owner, such as by checking a drivers' license or passport. > > I was under the impression that the original message was about your own > key, which you should sign (keys that aren't self-signed are worthless). > Presumably you don't need to look at your own drivers' license. > GPG changed recently in that it stopped ultimately trusting any key for which you have a private key. This means you have to edit your key and trust yourself. I would be surpised if someone had managed to create a key which hadn't been self-signed. However, that said, I was under the impression that the email bab followed up to was advocating signing keys willy nilly. Certianly how I read it. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9nFEGYsCKa6wDNXYRAqS9AJ0Rtt8yB0DjOYcbDI9z15SKx3/KMACghKB3 K8jCX+bg0vpgVbh3wxU15X0= =uFuM -END PGP SIGNATURE-
Re: Kmail and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 03 October 2002 1:19 pm, bruno randolf wrote: > i'm not sure if this is the problem in your case, but kmail only encrypts > to keys which are signed and trusted. > > so you have to do > gpg --edit-key > > and then: > Command> sign > ... > Command> trust > ... > Command> save > > after that you are able to select the key when you encrypt a message. > > br1 > > On Thursday 03 October 2002 11:30, José Manuel Pérez wrote: > > Hi all. > > > > I've got KDE 3.0.3 and gnupg 0.13-3 from Debian unstable. I've generated > > my keys and configure kmail (1.4.3) in order to use gpg, but it never > > signs nor encripts my messages. > > > > Someone knows what can I do? I don't get any error/warning message about > > it, and I know gpg works ok. > > > > Thanks in advance, /me has found another person to not trust - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9nEskYsCKa6wDNXYRAsHxAJ9g/WNYxrcgEjRwlcpyGFp0CMPPkACfTj/8 Qgc7pPqHhIL1xd2aiPXzoyc= =EPW6 -END PGP SIGNATURE-
Re: KDE 3.1b2 Dependency Problems!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 02 October 2002 11:57 pm, Richard Shaw wrote: > Look for sections like the following: > > Preparing to replace kaddressbook 4:3.0.7.cvs20020824-1 (using > > .../kaddressbook_4%3a3.0.8.cvs20020930-1.2_i386.deb) ... > > Unpacking replacement kaddressbook ... > > dpkg: error processing > > /var/cache/apt/archives/kaddressbook_4%3a3.0.8.cvs20020930-1.2_i386.deb > > (--unpack): > > trying to overwrite `/usr/lib/kde3/libkaddressbookpart.la', which is > > also in package kpilot > > dpkg-deb: subprocess paste killed by signal (Broken pipe) > > Then 'cd /var/cache/apt/archives/' and 'dpkg --force-all -i > ' Do that for each package that has problems like the one > above. Then 'apt-get -f install', to fix everything up and continue > again with the upgrade. It will necessary to do this for every upgrade > until the packages are all perfectly sorted in this respect. > > Richard ** WARNING *** *NEVER USE --force-all WITH EXPERIMENTAL DEBS* Some of you may remember some 3.0.0 betas which had /usr/sbin as a file. The correct fix is: apt-get --purge remove kdelibs4 apt-get --purge remove libarts1 apt-get install arts kdelibs kdebase kdenetwork - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9nAH0YsCKa6wDNXYRAh56AKCCQFGajIYPToaKdaoDFIUE8wq69ACgoAuw 8l0tKEBEWFjMbzM0+JDfad4= =tGzE -END PGP SIGNATURE-
Re: libarts1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 02 October 2002 8:34 pm, Jarno Elonen wrote: > > btw your key doesn't seem to be on the keyservers, which makes signing > > messages a lot less useful. You may want to do: > > gpg --keyserver the.earth.li --send-key E5FA70BF > > btw2: is there some way to configure KDE/Kmail to automatically look-up > keys of signed messages? > > - Jarno Yes. Add the folling line to ~/.gnupg/options: keyserver-options auto-key-retrieve You may not want to until KDE3.1 due to a bug in kmail which means that gpg recalculates the trustdb every time you import a new key into your keyring, and kmail takes 50% of the processor time polling the gpg process. This has been fixed in KDE3.1 aiui. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9nAD5YsCKa6wDNXYRAoUWAJ9Hg1MZXLEgTZW50sw8fUbkQ/17QACeOxJF ZYd0UBk7qRp1S1jNDC9NIHI= =MAGw -END PGP SIGNATURE-
Re: 178 days and counting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 30 September 2002 8:00 pm, Fred K Ollinger wrote: [snip] I would like to point out we use a mailing list for a reason. Please stop CCing everyone who so much as touchs a thread. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9mMY5YsCKa6wDNXYRAk3WAJ0Yw2RU5jbuhDxajDYMSBKJFc4OzwCdFXP9 OOI+YZNHvl/hTyRcUociQi0= =UsQc -END PGP SIGNATURE-
Re: Removal of KDE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 30 September 2002 4:54 am, Karolina Lindqvist wrote: > måndagen den 30 september 2002 04.05 skrev Thomas Ritter: > > But removing > > those packages was really a pain... > > Ok, I i'll see what I can do. I have another machine where I can install > KDE 3.0.3 on and install KDE 3.1 over it, to see what happens. I want such > a transition to be smoothly. I guess I should do the same thing for KDE > 2.2, right? > > > Reading apt-get's manpage I found no option to remove the given package > > and all packages depending on that. Does such a thing exist? > > > > Something like "apt-get --with-all-depending-packages kdelibs" would be a > > great help. > > Just removing apt-get remove kdelibs (with optional --purge) should remove > everything that depends in kdelibs. > > -- Karolina That will not work as kdelibs is a meta package which just depends on things in kdelibs. Nothing should depend on kdelibs. I would consider it a bug if it did. You can find the information about what to remove at http://www.davidpashley.com/debian-kde/faq.html - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9mA/NYsCKa6wDNXYRAgzhAJsHmY7WAjqDswrAmBmWwuypKN7ZKwCfZgQM q2Z0zp9JOAj8/Br9Xc9b9+M= =ZBpy -END PGP SIGNATURE-
Re: 178 days and counting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 29 September 2002 12:40 pm, Karolina Lindqvist wrote: > söndagen den 29 september 2002 11.59 skrev David Pashley: > > The current plan intents to append a c to the package name for 3.2 > > compiled packages. This can then go when the soname is upped. So if we > > put KDE in now, we are stuck with kdelibs4c until kde4 is released. > > How will you do with incompatible libraries with the same name, like > /usr/lib/libkdecore.so.4.1.0? Will you give the gcc3 compiled version the > same name and place as now, or will you change the name or path for the > gcc3 version? > > -- Karolina I don't know all of the plans. This is the closest we have to a plan atm. http://people.debian.org/~willy/c++transition.html - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9mA4vYsCKa6wDNXYRAmdPAJ0dSOYLHW8CuKd3O/zlYzOwuqTShwCcDoHo kiC98F3Ks2f0rwirZutSEQ4= =cOnQ -END PGP SIGNATURE-
Re: 178 days and counting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 27 September 2002 7:01 pm, Hendrik Sattler wrote: > Am Freitag, 27. September 2002 19:36 schrieb > > [EMAIL PROTECTED]: > > woody/unstable (libc3.x maybe? I don't remember.) that were > > dependencies. > > Because you wrote that often enought now: > "woody" is not "unstable" or "testing" but the current "stable", maybe you > should take a look at http://www.debian.org to get this right: > "woody" == current "stable" > "sarge" == current "testing" > "sid" == always "unstable" > It is annoying and hard to track what you mean when you mix this up > completely. > > BTW: I don't understand why most unstable packages are not in unstable > anymore. KDE3.x ist left out because of gcc3.2, although it does not make > much sense: if it breaks on transistion to gcc3.2- well, it's unstable. > Same with XFree4.2. What's the difference to make the gcc change with or > without KDE3 in unstable? It compiles with gcc2.95 and troubles with gcc3.2 > are expected anyway. > Sorry, but it does not make much sense to me at all. This is no matter to > me though because I track testing and not unstable. But current behaviour > makes unstable rather pointless. > The current plan intents to append a c to the package name for 3.2 compiled packages. This can then go when the soname is upped. So if we put KDE in now, we are stuck with kdelibs4c until kde4 is released. Plus it means that we can compile KDE3 outside of the transition so we reduce the workload on the other Debian Developers - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9ls8aYsCKa6wDNXYRAt+VAJ9blzY6DQkn2G7BAvcCnDONS7S3QQCgoh99 qB1740oMIMKtbMXMYEK2U0w= =qhgv -END PGP SIGNATURE-
Re: 178 days and counting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 27 September 2002 2:48 pm, Brad Felmey wrote: > Since KDE 3.0 was released, and still nothing in sid. > -- > Brad Felmey Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody, or you could just bitch about it. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9lIPWYsCKa6wDNXYRAoFtAJ4mZb5noFhCkUFRCTqe1h/ablQrnACgiYz3 k7Ig8eY97dWx7gRUN1T6zr0= =OcOa -END PGP SIGNATURE-
Re: What's going on with KDE 3 and XFree86's libxkbfile?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 27 September 2002 2:17 am, Branden Robinson wrote: > [Please reply to both debian-kde and debian -x.] > > I recently got a mail that said something like this: > > Why isn't there a -fPIC compiled version of /usr/X11R6/lib/libxkbfile.a > available? (e.g. /usr/X11R6/lib/libxkbfile_pic.a) > > Background: I'm regulary compiling KDE3 CVS head on hppa and I'm getting > a failure in the link stage: > > /usr/local/bin/ld: /usr/X11R6/lib/libxkbfile.a(maprules.o): relocation > R_PARISC_DPREL21L can not be used when making a shared object; recompile > with -fPIC /usr/X11R6/lib/libxkbfile.a: could not read symbols: Bad value > > This error is caused because the libxbbfile isn't compiled with -fPIC and > so it's not usable to build a shared lib. But both libXxf86dga_pic.a > libXxf86vm_pic.a are available as pic versions. > > I already answered this person privately, and I trust I don't need to > remind this list of why it's a stupid idea to treat an unversioned static > object like a shared library[1]. > > Can someone tell me what part of KDE is trying to sneak things in the back > door? Can someone get in touch with upstream quickly and warn them of the > hazards of doing so? The right thing to do is to statically link > libxkbfile into the object being created. > > [1] > http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00028.html > http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00063.html > http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00087.html > http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00085.html Branden, can you get deepthroat to send a build log so we can see there this error is occuring in the build. Can you ask them how recently this has happened? Has anyone else had this problem on HPPA? - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9lCsqYsCKa6wDNXYRAuCsAJ0eT9Gj4HoXq83zQfc1yP5WfHNaLgCeLP3J 1kAF7Jnh/DxSlupG6lzrJb8= =zyI3 -END PGP SIGNATURE-
Re: ugly x background when starting kdm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 26 September 2002 10:57 am, Bastiaan Naber wrote: > Every time I start my computer I am anoyed with this problem but > have not been able to get rid of it. So please help me. > > When kdm starts I first get this very ugle black and white dots as > a background after which the login box comes up and after that > the debian background appears. I would like to get rid of the > black and white dots, how do I do this ? I have looked in > /etc/kde3/kdm but could not find anything. > > What I like is to replace the dots with just a plain collor, like black > or white or blue. Does anyone know how to do this ? > > Thanks, > Bastiaan Basically, this is compiled into the Xserver. If you want to change it then start learning the Xfree86 sources. I doubt very much if Xfree86 will accept any patches to change it. Think of it as a tradition. There was an interview with Jim Gettys and one of the questions touched on this very subject. I could try to dig it up if anyone really wants me to try. As people have mentioned kdm does replace the background after a few seconds. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9kyc6YsCKa6wDNXYRArXuAJsEkirMtNrrClPbuhzFr/adLRpHogCgq7L+ GFaxtKn4LDcJlP1dUUC/9MM= =HK95 -END PGP SIGNATURE-
Re: Home and end will work?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 25 September 2002 10:08 pm, Paul Cupis wrote: > On Wednesday 25 September 2002 23:42, Carlos Acedo wrote: > > I am still wondering when will be fixed the home and end keys in konsole > > that doesn't work for me since begginig :( > > Any one has found a solution? > > I believe that this was fixed in bash package 2.05b-1, available from > testing/sarge and unstable/sid. > > Paul Cupis > -- > [EMAIL PROTECTED] This is now in the FAQ at http://www.davidpashley.com/debian-kde/faq.html - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9ksCVYsCKa6wDNXYRAqu1AJ0VXV0AoEyonhgEvb0ECvZnaX9GPACfUHsE r1lNgB2DlwMKwCVOIAe1gMI= =c3GU -END PGP SIGNATURE-
Re: KDE2.2.2: Ctrl-S kills konsole input
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 23 September 2002 3:49 am, Hendrik Sattler wrote: > Am Montag, 23. September 2002 03:40 schrieb Donald R. Spoon: > > Hendrik Sattler wrote: > > > sometimes I accidently hit Ctrl-S instead of Shift-S. This seems to > > > disable the ability to do any keyboard input to that session. So what's > > > wrong? How can I reenable input without closing the window and opening > > > a new one? > > > > Try hitting Ctrl-Q and see what happens > > > > This used to be an old key sequence to stop / start screen scrolling. > > Thanks, that really did it. Is there a way to disable this behaviour? I use > my own keytab file with .kde/share/apps/konsole/default.keytab, so there is > no problem adding additional entries. I don't need Ctrl-S/Ctrl-Q but would > rather use the "Rollen" button (german, between Print and Pause buttons) > for this (this is what the button is for and it would make much more sense > to use that one). Is there any known solution? (Does KDE 3.0.x have this?) > > HS > This is dealt with by the same thing that deals with ctrl-C and ctrl-\. AIUI that is the kernel. They are signals SIGSTOP and SIGCONT iirc. So basically you don't have much chance of stopping it. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9jt5pYsCKa6wDNXYRAqPgAJ9DGY0Xdg05QpZrGKuFefX5onM1zwCfStE4 pCbn3DxDHGEzEqjBMRSgUSg= =VX54 -END PGP SIGNATURE-
Re: KDM patch in kdebase
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 19 September 2002 10:38 pm, Ralf Nolden wrote: > Hi Chris and others, > > could someone have a look at the kdm patch that gets applied to kdebase/kdm > during debuild ? The patch file fails in one patch; I didn't have the time > yet to have a look. Also, I'll be busy learning for an exam on next > tuesday, so please don't expect any checkins from me until next wednesday. > Sorry. > fixed - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9i1UEYsCKa6wDNXYRArQoAJ9Qv0oBYO+jQcNvOB/1AAUS26ts2ACfQJ0J OIb5xyRV9RFifLPRcqfZ7EE= =PlW5 -END PGP SIGNATURE-
Re: Building KDE and debhelper problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 19 September 2002 1:39 pm, Vyacheslav E. Sidin wrote: > HI All. > I'm make decision to build KDE debs from CVS myself and at this moment have > a problems. > > The first package need to be compiled/installed is arts. > I'm do next: > > cd arts > make -f admin/Makefile.common cvs-clean > make -f admin/Makefile.common cvs > cvs update > dpkg-buildpackage > > And start compile/build arts package. > The compiling process seems to me ok and w/o errors. > In the end of compile/build process I got next error (here is last few > lines): > --- >- make[3]: Leaving directory > `/usr/local/src/system/kde/kde3/arts/obj-i386-linux' make[2]: Leaving > directory `/usr/local/src/system/kde/kde3/arts/obj-i386-linux' make[1]: > Leaving directory `/usr/local/src/system/kde/kde3/arts/obj-i386-linux' > dh_install --list-missing > Unknown option: list-missing > dh_install: unknown option; aborting > make: *** [install] Error 1 > wave:/usr/local/src/system/kde/kde3/arts# > --- >- So, the problem seems to me with dh_install binary > (debhelper package) I tried to run dh_install manually and --list-missing > option is really unsupported. > > Can someone suggest to me what to do in this situation ? > Where is problem ? In kde build scripts ? In debhelper package (may be > update this from unstable repository) ? > > Please help me. > > P.S. I'm almost new in Debian, I was used RedHat about 6 years and most of > application compiled via rpm --rebuild file.rpm or configure && make > install . > I'm really like Debian package management system and would like to > compile/install applications only using this one. > You need a later version of debhelper. The version in sid works fine. I don't know about sarge. If you are using woody, you can just remove that option. It isn't really needed for building the packages. It is more of a debugging aid. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9ic8BYsCKa6wDNXYRAuybAJ9w0DpsiHiyhGemBarQPtZK6fkaegCePUoX f7ptZ7VUWTS+YKgOnzEdE4o= =eIey -END PGP SIGNATURE-
Re: kdebase deb questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 9:42 pm, David Pashley wrote: > On Monday 16 September 2002 9:24 pm, Ralf Nolden wrote: ah crap. wrong attachment - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9hv8XYsCKa6wDNXYRAvKIAJ9+5AIezdLXZhNx/M5xpuvplR25YwCfZ0A/ uEyEEr1uCKA0MoEa2YL84nY= =KYc8 -END PGP SIGNATURE- dh_missing Description: application/shellscript
Re: kdebase deb questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 9:24 pm, Ralf Nolden wrote: > Hi, > > anyone who can tell me something about these files ? (--list-missing) > > Thanks, > > Ralf > interestingly here is the difference between dh_install and dh_missing dh_install --list-missing dh_install: ./debian/tmp/etc/kde3/kdm/Xservers not installed dh_install: ./debian/tmp/etc/kde3/kdm/Xaccess not installed dh_install: ./debian/tmp/etc/kde3/kdm/Xwilling not installed dh_install: ./debian/tmp/etc/kde3/kdm/Xsetup not installed dh_install: ./debian/tmp/etc/kde3/kdm/Xstartup not installed dh_install: ./debian/tmp/etc/kde3/kdm/Xreset not installed dh_install: ./debian/tmp/etc/kde3/kdm/Xsession not installed dh_install: ./debian/tmp/etc/kde3/kdm/README not installed dh_install: ./debian/tmp/usr/share/fonts/fonts.dir not installed dh_install: ./debian/tmp/usr/share/fonts/override/fonts.dir not installed dh_install: ./debian/tmp/usr/share/doc/kde/HTML/en/kdebase-apidocs/common not installed david david% dh_missing - -- /dev/fd/63 2002-09-17 09:41:49.0 +0100 debian/tmp/etc/kde3/kdm/README debian/tmp/usr/share/doc/kde/HTML/en/kdebase-apidocs/common debian/tmp/usr/share/fonts/fonts.dir debian/tmp/usr/share/fonts/override/fonts.dir - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9huyzYsCKa6wDNXYRAsEJAKChczC4FjAXc8CozQYsAp/vI//JNgCgn3D2 +lx+yHnNY9x3j4pFBbxyJp8= =F6Zw -END PGP SIGNATURE-
Re: kdebase deb questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 17 September 2002 3:33 am, Karolina Lindqvist wrote: > måndagen den 16 september 2002 22.42 skrev David Pashley: > > iirc they are actually installed, but --list-missing is not the best in > > the world. it doesn't seem to take into account files that have been > > moved. try the following script. Be wanted. it is "The Worst Bash Script > > In The World" TM > > It looks like line noise, so it must be perl er no it's bash. > > I use a different method. I started packing when dh_movefiles was used and > used the following binary target in the rules file: > > binary: binary-indep binary-arch > find $(tmp) -type f -o -type l | sed -e "s_^$(tmp)/__" | tee doit > > It always lists missing files, and also puts them in the file "doit", from > where in a format that can be easily pasted into ".files" files. > To categorise a couple of new files, after a new cvs update and rebuild is > quite easy. > except dh_install copies files, not moved so you can't tell what files haven't been put in a package. you need to do a bit more to get the same information > Another problem is disappearing files. That has bitten me one or two times > now. dh_install and dh_movefiles just don't do what I want them to do. > And then we have at least one empty directory in KDE, that need to be > copied. At least dh_movefiles just omits empty directories. > > -- Karolina - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9huxsYsCKa6wDNXYRAgvLAJ0U+TULGSUptRgv0OtxtnNWYuIW4ACfaS3/ zF15RLtrsjinsFXguOFf7So= =aiv8 -END PGP SIGNATURE-
Re: kdebase deb questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 9:24 pm, Ralf Nolden wrote: > Hi, > > anyone who can tell me something about these files ? (--list-missing) > > Thanks, > > Ralf > > dh_install: ./debian/tmp/usr/share/fonts/fonts.dir not installed > dh_install: ./debian/tmp/usr/share/fonts/override/fonts.dir not installed Can't package. against policy or maybe just that they get generated on install > dh_install: ./debian/tmp/usr/share/doc/kde/HTML/en/kdebase-apidocs/common > not installed > dh_install: ./debian/tmp/etc/kde3/kdm/Xresources not installed > dh_install: ./debian/tmp/etc/kde3/kdm/README not installed > dh_install: ./debian/tmp/etc/kde3/kdm/Xaccess not installed > dh_install: ./debian/tmp/etc/kde3/kdm/Xservers not installed > dh_install: ./debian/tmp/etc/kde3/kdm/Xsession not installed > dh_install: ./debian/tmp/etc/kde3/kdm/Xreset not installed > dh_install: ./debian/tmp/etc/kde3/kdm/Xsetup not installed > dh_install: ./debian/tmp/etc/kde3/kdm/Xstartup not installed > dh_install: ./debian/tmp/etc/kde3/kdm/Xwilling not installed > iirc they are actually installed, but --list-missing is not the best in the world. it doesn't seem to take into account files that have been moved. try the following script. Be wanted. it is "The Worst Bash Script In The World" TM > -- > We're not a company, we just produce better code at less costs. > > Ralf Nolden > [EMAIL PROTECTED] > > The K Desktop Environment The KDevelop Project > http://www.kde.org http://www.kdevelop.org - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9hkIjYsCKa6wDNXYRAquWAJ0WjnFra/lje0LSY40fdWqlvJk6ZgCfbeHV m3wEjuwp0t+v3sj6Wy/YDno= =2XKD -END PGP SIGNATURE- dh_install Description: Perl program
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 16 September 2002 6:46 pm, Ralf Nolden wrote:
> On Monday 16 September 2002 18:08, Tomas Pospisek's Mailing Lists wrote:
>
> Is the below rules file something we can reuse for that ? or are there
> other options ? Then, why not importing it as rules.cvs into every module
> so we can all reuse it for daily builds ?
>
> Ralf
>
There is a perl script (admin/debianrules) which generates the
debian/debiandirs makefile fragment.
> > On Mon, 16 Sep 2002, Yenar Calentaure wrote:
> > > Another thing with debs I dislike atm: The package versions are the
> > > same all the time. Sure, apt-get is smart enough to figure out what
> > > changed, but you lose overview soon which build you run. I'll bump up
> > > version (probably best scheme is 3.0.7-cvsMMDD) at each rebuild,
> > > and probably push the patch upstream :). Likewise all changes to
> > > packaging should bump package version (they should be mentioned in
> > > debian/changelog).
> >
> > I'm using:
> >
> > $ cat debian/rules
> > #!/usr/bin/make -f
> > #
> > # Based on Sample debian/rules file - for GNU Hello (1.3) by Ian Jackson.
> > #
> > # See realsync-files/debian/rules for details!
> >
> > VERSION=${shell date +'%y%m%d%H%M%S'}
> > package=escher-cvs
> >
> > [...]
> >
> > binary-indep: build
> > [...usual stuff...]
> > dpkg-gencontrol -isp -v${VERSION}
> > -DPackage=${package}-${VIDEO_DSCR} dpkg --build debian/tmp ..
> > [...]
> >
> > I suggest a note in README.Debian:
> >
> > This package represents a daily build from CVS. Upstream changes are not
> > noted in the changelog
> >
> > And I'd only mention stuff in the changelog if you really tighten some
> > Debian specific screw.
> > *t
> >
> > --
> > ---
> > Tomas Pospisek
> > SourcePole - Linux & Open Source Solutions
> > http://sourcepole.ch
> > Elestastrasse 18, 7310 Bad Ragaz, Switzerland
> > Tel: +41 (81) 330 77 11
> > -------
>
> --
> We're not a company, we just produce better code at less costs.
>
> Ralf Nolden
> [EMAIL PROTECTED]
>
> The K Desktop Environment The KDevelop Project
> http://www.kde.org http://www.kdevelop.org
- --
David Pashley
[EMAIL PROTECTED]
Nihil curo de ista tua stulta superstitione.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9hjGWYsCKa6wDNXYRAkh4AJ9BITVs3ZJaD7Fg+7lEbmLIp0qiQQCgmdf5
909vxF8AS+qM8mPIzlofWZU=
=EmOb
-END PGP SIGNATURE-
Re: ALSA and KDE in debian
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 1:41 pm, Karolina Lindqvist wrote: > I think ALSA is a small problem with KDE on debian. > > In KDE 2.2 it was possible to choose different packages for ALSA support > or not ALSA support, but that was removed in KDE 3 packaging. ARTS can be > built without ALSA support, with ALSA 0.5 support or with ALSA 0.9 support. > kdemultimedia does not build cleanly with ALSA 0.9, since support for it is > simply missing. It only works with ALSA 0.5. > > Some newer interesting audio applications require ALSA 0.9. But > unfortunately, ALSA is not backward compatible, so if there is ALSA 0.9 in > the kernel, ALSA 0.5 applications won't work. (Maybe some will) > > So what should KDE be built with? > > One version for all, with two versions ALSA and not ALSA, or with three > versions, not ALSA, ALSA 0.5 and ALSA 0.9? > > I built KDE 3.1 beta with ALSA 0.9 support, but I am not sure that is good > for everyone. You can also not cleanly rebuild kdemultimedia with ALSA 0.9 > > Is there maybe some policy, like "debian version XXX has ALSA X.Y as > standard" or something like that? > > -- Karolina Never seen any problems here. I use alsa 0.9. What sort of problems do you see with kdemultimedia? - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9hdmSYsCKa6wDNXYRApK4AJ0ao+ZWDCZVjefAca4BXhs0vUGYywCfdzBN iS6V0bpnkuXI0V2WJyfInG4= =tg9o -END PGP SIGNATURE-
Re: A suggestion: i18n for KOffice
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 11:13 am, Pablo de Vicente wrote: > Hello, > > I would like to propose a change to the KOffice packagers to include an > independent i18n package for KOffice. > > At the moment translations for the different languages are provided in > kde-i18n-xx packages, according to the main KDE releases. However KDE > releases are not in sync with KOffice releases, because they are > independent. This leads to having the latest KOffice packages for the > latest stable branch but not its corresponding updated translations. > > I can show this with an example; now Ben Burton has released KOffice 1.2, > but the translations for this version are in the HEAD branch and are tagged > as KOFFICE_1_2_RELEASE. However the KOffice 1.2 packages are built for KDE > 3.0.3, which I think is __totally__ correct. On the other hand the > translations applied to KOffice come from the KDE_3_0_BRANCH, so that some > applications appear partially translated and others not translated at all, > while the translations are completed in the CVS. > > I propose a solution for this, but I am sorry because it means more work > for the KOffice packager (Ben Burton in this case), it would be to release > koffice-i18n-xx packages, which would be created extracting from the CVS > all messages and documents tagged as KOFFICE_X_Y_RELEASE. And to prevent > that the files with messages and documentation are not overwritten by the > kde-i18n-xx packages, the koffice part of this package should be removed > from the kde-i18n-xx packages. > > regards, and many thanks to all Debian packagers for KDE for their work. > > Pablo de Vicente > KDE-es translation team. This is really an upstream problem. They probably should not have seperate releases for koffice and KDE, but have all the translations in one place maybe you could suggest that they split up the koffice and kde translations. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQE9hcbVYsCKa6wDNXYRAskGAJib8No9ojOuOWk/WYusEW5cCoYMAJ9G14jU N/iDtbmTfZNwN8ZB0VajzA== =nCbI -END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 12:09 pm, Karolina Lindqvist wrote: > måndagen den 16 september 2002 11.20 skrev David Pashley: > > I'm sorry that just isn't true. KDE HEAD has been kept up to date as much > > as possible. People have been able to build packages for 3.1 for the last > > few months. I could check the dates if you are interested. We haven't > > provided binary packages because a) they take up a lot of room and b) > > calc has been busy making sure that 3.0.x is working, bab has been > > working on koffice 1.2 and everyone else has been making sure that HEAD > > works. We have never said that we will start for on 3.1 debs once 3.1 has > > been released. > > Good you say it, since then I don't have to bother with building KDE 3.1 > packages for others. Actually I never intended to and just made my own > packages available, and was surprised by the demand. I am happy for the > feedback I got on this list, and will improve my own packages and packaging > technique. I have some plans and make small experiements on improvements, > based on problems I have heard on this list, from all kind of KDE versions. > If you want to provide patches, we will gladly look at them. Just send them to the list. > If someone want my new packages for KDE 3.1 beta 2, when they come, I will > make them available. But as you say, it is probably not needed since you > already have done the work and hopefully will also provide binary packages. > I can't provide binaries, but I'm sure someone will. Hopefully it will start to get a bit less bumpy so when beta 2 is tagged, files won't be moved around so much. > -- Karolina - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9hcYaYsCKa6wDNXYRAhX0AJ4rOZfRD5CxuM7bkKitH0jBPwMuzwCdGse1 CoPDUxjK75TDfUfVpLWOEgM= =Pw49 -END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 12:33 am, Ralf Nolden wrote: > On Sunday 15 September 2002 20:08, Yenar Calentaure wrote: > > Hi Yenar, > > thanks for your kind and quick answer - I've got CVS write access, so does > Chris. We'll be glad to take any patches and put them into CVS that would > help automate the build process. I myself have a DSL line so up/download is > not an issue for me; I could also use the 2mbit line in the company I work > for now. > Ben Burton and myself also have write access. > Also, like Charles de Miramon pointed out, we should take care of daily or > at least weekly builds from CVS that can be installed side by side of a > stable environment for the translators and doc writers who need a recent > KDE from CVS but can't/won't want to go through the development process. > Do we have anyone willing to build them and host them? - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9haL+YsCKa6wDNXYRAuasAJ9jnxHJDeQVGlx+xYAS0GGVhisCvwCglbs7 /c6iwhEx+zL1ikAbv5U6ufQ= =ox/o -END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 5:53 am, Karolina Lindqvist wrote: > söndagen den 15 september 2002 17.35 skrev Ralf Nolden: > > as some of you got to know until now, I switched from SuSE to Debian this > > week - - and directly hit the fact that building debs from CVS would work > > best for me to have it working the right way (tm). Now, I got into > > working with Chris lately and we try to fix the issues one by one soon > > now so that everyone can build debs himself but more important, provide > > debs for KDE constantly that work, where also most importantly betas, > > RC's and finals are provided by the day that the packages are build and > > work optimal on Debian. > > I have some experience of packaging KDE into debs, and I think it would be > great if we could combine our efforts. > > My KDE3.1-beta packaging was not originally meant for distribution to > others, but it appears to be quite popular judging on the number of > downloads I got (I have 123 downloads of kdelibs from my machine, and there > are a > mirrors), so I am thinking of making the packaging both better, more > versatile and more fine-grained. > > My main interest is just something that works, and since the debian KDE > packagers have announced that they are not interested in packaging KDE > beta, and have said that they are starting their packaging efforts first > when the final version is out, I aimed at packaging just beta versions and > early releases. I don't think it is such a bad idea that the main packagers > work on refining the final product, and are not bothered with beta versions > when they come. > I'm sorry that just isn't true. KDE HEAD has been kept up to date as much as possible. People have been able to build packages for 3.1 for the last few months. I could check the dates if you are interested. We haven't provided binary packages because a) they take up a lot of room and b) calc has been busy making sure that 3.0.x is working, bab has been working on koffice 1.2 and everyone else has been making sure that HEAD works. We have never said that we will start for on 3.1 debs once 3.1 has been released. > Actually, what I really think is that by providing packaging of KDE betas, > the packaging problems can be found at an early stage, making it much > easier and less troublesome to fast provide a good final version for those > who don't want surprises (like with libpng this spring). > > -- Karolina - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9haJkYsCKa6wDNXYRAjpwAJ0V3DU+iLiUJwbm8pTiCdAZojSmQQCeI6i8 wjVyXZKAS5Jj5Cb49V9ejdY= =UVqw -END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 September 2002 7:35 pm, Alan Chandler wrote: > On Sunday 15 September 2002 4:35 pm, Ralf Nolden wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hi, > > > > as some of you got to know until now, I switched from SuSE to Debian this > > week - - and directly hit the fact that building debs from CVS would work > > best for me to have it working the right way (tm). Now, I got into > > working with Chris lately and we try to fix the issues one by one soon > > now so that everyone can build debs himself but more important, provide > > debs for KDE constantly that work, where also most importantly betas, > > RC's and finals are provided by the day that the packages are build and > > work optimal on Debian. > > Fantastic > > > The other thing is that third party apps need to be compiled if you like > > to use them. Until now several people do that for the apps they like to > > run or that they are developing using debian as their development > > platform. The problem for the users is that the deb lines for > > sources.list are spread all over and there is no central way of getting > > the newest apps through debs for people that are not necessarily > > developers like we are. The other thing is that as developers, just doing > > a make install would work but that usually messes up our systems, > > especially as KDE has /usr as its prefix on debian. So it would be the > > best if we could somehow collect our resources and schedule building debs > > and providing them in a central place. > > Still not sure why KDE and these apps can't seem to make it into the formal > debian unstable (and then the more stable) archive and mirrors, but > apparently not - so ... > Read the FAQ at http://www.davidpashley.com/debian-kde/faq.html > > I talked with Dirk Müller already and some other guys that I use to work > > with at KDE and we should provide that possibility through KDE on > > ftp.kde.org. Wether that will work out just depends on how many people > > would volunteer to participate. > > A good alternative - especially if you could set it up so that it had > different sections for stable, unstable and development (or something) so > that we could chose what. > > I am not sure how I could participate - I do have an always on, lightly > used server supporting my family at home at the end of a cable modem, but > my acceptable use conditions require that it is not used as a public server > other than for a limited (<10) password controlled connections. I could > perhaps do some regular builds (Its only a p2 400 with 128MB Ram, but it > has loads of disk space). > > As for my time, I am travelling abroad (from the UK) between 3 and 4 days a > week, so that pretty much limits what I could do. I am trying to do some > light coding or bug fixing offline in the evenings when I am away - but > last weeks attempt was feeble, I managed only an hour (working late and > then eating seems to grab most of the time). I could devote a bit more > when I am at home. > > > > > > -- > Alan Chandler > [EMAIL PROTECTED] - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9haEZYsCKa6wDNXYRAh3+AJwIU5spgBSgKEUSYKp4t9pwJnaQ2ACfYq/n U+681Wq5w7iw11lw77GzmwE= =9FIJ -END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 September 2002 6:53 pm, Tamas Nagy wrote: > Glad to hear the initiative. First of all, credit to all packagers, it > was a good work... > > IMHO, the current practice (everybody creates own packaging for KDE) > needs to be changed. The debian directories in CVS used to be outdated, > and this leads to duplicated (and wasted) packaging efforts. KDE package > building should be repeatable from the CVS by anyone. > and they are for 3.0.x, see below for info. > However there are some site, including mine > (http://mypage.bluewin.ch/kde3-debian, for gathering all the (often > incompatible) packages and sources ), the best would be to have a single > repository for all the KDE Debian packages at ftp.kde.org. > The problem is that several people are maintainers for several packages. Chris Cheney is maintainer for kdelibs, kdebase and others, while Ben Burton is maintainer for kdeartwork, kdeaddons, koffice and a few others. Someone else is maintainer for kdevelop. > Finally, individual heroes, please try to use the KDE CVS (more > frequently) and let everybody will benefit from your work. > AFAIK, most people do use CVS and try to keep HEAD up to date. The problem there is that HEAD is a moving target. KDE developers add files, move files and remove files which means that the file lists in CVS are not up to date. Several people, including myself, build KDE HEAD as and when we can and update CVS so they are buildable, but we can't do all of the modules all of the time, so they won't always be buildable. BRANCH has pretty much been up to date since before 3.0.0 so people could build packages from CVS for the 3.0.x series. IMHO, the situation with KDE is significantly better than for most other Debian packages which do not have debian dirs available for development versions. > Tamas > > -Original Message- > From: Ralf Nolden [mailto:[EMAIL PROTECTED] > Sent: Sunday, September 15, 2002 5:36 PM > To: debian-kde@lists.debian.org > Subject: KDE debs building > > > Hi, > > as some of you got to know until now, I switched from SuSE to Debian > this week > - and directly hit the fact that building debs from CVS would work > best for > me to have it working the right way (tm). Now, I got into working with > Chris > lately and we try to fix the issues one by one soon now so that everyone > can > build debs himself but more important, provide debs for KDE constantly > that > work, where also most importantly betas, RC's and finals are provided by > the > day that the packages are build and work optimal on Debian. > > The other thing is that third party apps need to be compiled if you like > to > use them. Until now several people do that for the apps they like to run > or > that they are developing using debian as their development platform. The > > problem for the users is that the deb lines for sources.list are spread > all > over and there is no central way of getting the newest apps through debs > for > people that are not necessarily developers like we are. The other thing > is > that as developers, just doing a make install would work but that > usually > messes up our systems, especially as KDE has /usr as its prefix on > debian. So > it would be the best if we could somehow collect our resources and > schedule > building debs and providing them in a central place. > > I talked with Dirk Müller already and some other guys that I use to work > with > at KDE and we should provide that possibility through KDE on > ftp.kde.org. > Wether that will work out just depends on how many people would > volunteer to > participate. > > If you're interested, let's come together to finally end this messy > system > where there's certain problems with building debs for us and the KDE > users > using debian, it would surely make things a *lot* easier if we organize > ourselves and coordinate doing things efficiently. > > Thanks for your attention and for volunteering :-) > > Ralf > -- > We're not a company, we just produce better code at less costs. > > Ralf Nolden > [EMAIL PROTECTED] > > The K Desktop Environment The KDevelop Project > http://www.kde.org http://www.kdevelop.org > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9haDEYsCKa6wDNXYRAv3qAKCDLJFgZKFsfCFx00agVsZvchuUCQCdFyh8 OAl8hAvTFGBub6MSeJxbtgM= =Q9T1 -END PGP SIGNATURE-
Re: Where can I get 3.0.3?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 14 September 2002 4:56 pm, Richard Beri wrote: > I have been searching through the list but I can't find an apt-gettable > place to get KDE 3.0.3 for testing/unstable. I have a mostly sid > system but in the last week have decided to track testing and wait for > it to catch up. I see that there is a 3.0.3 for woody, but I am unsure > about installing this. http://www.davidpashley.com/debian-kde/ - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9g2M5YsCKa6wDNXYRAkqYAKClHeafLxtx5b++CLqWHAjOekAEFwCfX81j O5+GBagmdAGvzZDcgMvdqqw= =asGR -END PGP SIGNATURE-
Re: kde 3.* in sid will it ever happen?
Paul Cupis said, and I quote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Friday 13 September 2002 15:58, Matt Reynolds wrote: > > On Fri, 2002-09-13 at 08:32, Paul Cupis wrote: > > > kde3 will go into sid when the gcc3.2 transiton is over/complete. KDE is > > > very much a C++-based system and there is little point uploading it using > > > gcc3.1 and then reuploading/compiling it in X days/weeks when the gcc3.2 > > > transition happens. And it cannot be uploaded now as gcc3.2 becuase the > > > ftp-masters will not allow gcc3.2 libraries in until the DD's have worked > > > out how to best deal with gcc3.2. > > > > > > I think it is just a matter of being patient, or helping the developers > > > decide how the gcc3.2 transition is going to happen, so that it can > > > happen and kde3 can go in. > > > > > > I notice that people have stopped asking when X4.2 will be in sid, and > > > when openoffice.org will be in sid... [and no, I'm not asking now, > > > either] > > > > One of the reasons I haven't complained or queried about X4.2 is that > > Branden is very good about replying to list complaints, releasing, and > > publicizing his releases. > > > > Visibility and transparency in the packaging process seems to keep the > > wolves at bay. While I'm happier with 4.2's packaging, I would still > > *love* to see dates associated with the actions taken on list(s). Not a > > schedule, but just a "here's what we've done so far" timeline. This > > keeps everyone on the same page, and could even help remove duplicated > > effort, IMNSHO. KDE 3.0.3 is packaged and apart from a KDE 3.0.4 release, the KDE 3.0.x branch is pretty much finished packaging wise. calc and others are now working on KDE 3.1 packaging. KDE 3.x will be in sid once the GCC transition plan has been worked out and started. This is kind of out of our hands. > > You do, of course have a good point and I thank you for your feedback. There > is already an (under-publicised) kde faq, at > http://www.davidpashley.com/debian-kde though I'm not certain from memory > that it has this type of information. > > It is obvious now that it should, and I will work with the maintainer and the > debian-kde folk to get that information into the faq. I will probably also > see about getting the faq a bit more publicity than the occasional mention > here and the references to it on #debian-kde/#debian. > > Thank you, > > Paul Cupis > - -- > [EMAIL PROTECTED] > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQE9gir3IzuKV+SHX/kRAuRaAJ9wQWD44J9GeQEz/x14HzDaXr3j4gCfaUJG > 8ABK7JdWNgIqMHy0SY9OmTk= > =VEu5 > -END PGP SIGNATURE- > > -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpXgdzPddMUe.pgp Description: PGP signature
Re: KDevelop and documentation for KDE and QT, How?
Pablo de Vicente said, and I quote: > Hello, > > I am running KDevelop 2.1.3, and I miss the KDE library documentation at the > left navigation panel. In former versions, I could unfold a tree with the > list of classes for QT and KDE. Now I can only browse the QT documentation > form the centralpanel. > > I have also installed htdig, and doxygen. For the first one I have followed > the instructions in /usr/share/doc/kdevelop/README-htdig.Debian and the > search engine works fine. I have read in this list that doxygen is necessary > for the documentation, but I am unsuccesfull browsing the documentatino form > KDevelop. I even select the path where the documentation for KDE is, but > KDevelop does not recongnize the directory as valid. > About 3 weeks before KDE 3.0.0 was released, KDE developers changed the program used to generate the documentation. Previously they used kdoc. They have since moved to doxygen, which produces different documentation Kdevelop for KDE3 did not have time to change to the new docs format. I think you will have to wait for an updated kdevelop 2.x or wait for Gideon. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpmx8M1ZVtGQ.pgp Description: PGP signature
Re: kde 3.* in sid will it ever happen?
Frank Van Damme said, and I quote: > On Friday 13 September 2002 18:58, Nathan Waddell wrote: > > IMNSHO, the RedHat Package Manager is far less powerful and flexible than > > Debian's dpkg. Forcing users to go searching for RPM's that may or may not > > have that dependency you need to compile/run an important program is > > idiocy. > > IMELHO (In My Even Less Humble Opinion) this has nothing to do with dpkg vs. > rpm but rather with apt vs. non-apt. Redhat doesn't support Apt (because they > sell a service that does the same?). Debian does (duh). There is apt for rpm > too, see Connectiva (and it also works with Mandrake afaik). > I think you too are mistaken. What makes Debian better than most distributions is policy (and lintian/linda) and the fact that most software has already been packaged so you don;t need to search for packages which may or may not work with your version of linux. Policy has the nice effect of making sure that debian packages work well together. The other nice advantage is that debian packages don't have to try and work on 50 different distributions. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgplgxpDbKlt5.pgp Description: PGP signature
Re: kde 3.* in sid will it ever happen?
Brian Nelson said, and I quote: > > But isn't the point of the gcc transition to decide how to cleanly > migrate C++ stuff like KDE to the new ABI? If KDE3 were uploaded, it > would just end up transitioning just like every other C++ library, like > Qt. > If I understand the current draft transistion plan, every C++ package will need a c added to the package name a la the libc5 -> libc6 transition. This can be dropped when the sonames is updated AIUI, most(all?) of the KDE libs have had their sonames bumped so we do not need to do this if we put KDE 3 in to a post transition sid, but we will have to wait until KDE4 before we can drop the c from the package names if we put it in a pre-transition sid. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpNP5xVThuwc.pgp Description: PGP signature
Re: Logout, Shutdown, Reboot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 13 September 2002 1:52 pm, Tamas Greguss wrote: > Hi! > > I use KDE 2.2.2 and when I choose Logout, it asks if I really want to > logout but there is no options to choose shutdown or reboot, too. > I can do shutdown or reboot only from KDM. > How can I configure KDE to ask me at logout if I want logout, shutdown, > or reboot? I couldn't find such a setting in KDE Control Center, but I > do know that it is possible because I saw it in another distribution > (Mandrake Linux). > > Thanks, > GregTom I think this is only available using KDE3, and then only by using KDM as login manager. I'm sure someone will correct me. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9gei/YsCKa6wDNXYRAmedAKCldBOqU2stWMs7USb3+LFtpB5bKgCfVw46 goMHRpunuo9ja+xXQvHAA6Q= =mYaH -END PGP SIGNATURE-
Re: kmail and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 01 September 2002 9:25 pm, Russell Coker wrote: > A problem that I have had with kmail in kde 2.0 and am now having with > kmail in kde 3.0.3 is that it takes up lots of CPU time when launching gpg. > > When I do an operation that causes GPG to take some time (IE re-calculating > the trust db because new signatures have been received for some keys) then > kmail apparently goes into a spin loop waiting for a response from gpg. > The result is that for some minutes kmail gets 50% CPU time and gpg gets > the other 50%. > > I then tried kill -stop on the kmail process, gpg then used >90% CPU time > until it finished it's work and I then did kill -cont on kmail and > everything was fine. > > Is there some way to reconfigure kmail to make it behave better? Or is it > just buggy? > Just buggy. There was a thread about this very issue very recently on the kmail mailing list. you can find archives at www.kde.org. It is "Bug#46406: Resolving GPG key owner is slow with large keyring" on 2002-08-12. You can also find it on bugs.kde.org. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9cqA1YsCKa6wDNXYRAtuNAJ9wuHw+pf31mhtO0ps3x4IsO8qXmACfW+sZ sHWNczpiewF9doIKjCL7fR4= =+nha -END PGP SIGNATURE-
Re: [PATCH] kdeutils (cvs head), debian
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 28 August 2002 3:18 pm, Yenar Calentaure wrote: > Hi! > > I needed this patch to build kdeutils debs from cvs head. Can i ask > debian kde maintainer to commit this? Dunno if this is right place for > this post. Please redirect me to right place if it isn't :). > > Thanks in advance. > > cheers > yenar This is as go a place as any. I will attempt to commit it later tonight, after I have rebuild all of arts, kdelibs and kdebase. The patch looks sane. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9bQ6RYsCKa6wDNXYRAiS/AKCavWqIjYDengastYh8loR8ND3ijgCcCf2a 1U4YSglxU1O8cQ5iRM12zm8= =BMv4 -END PGP SIGNATURE-
Re: Donations for KDE on debian.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 27 August 2002 10:12 am, Lars Roland Kristiansen wrote: > Hi i have 2 Mylex scsi raid controllers that can do 160mb/s. In the past > the debian-kde sites have been up an d down and if there is any idea in it > i would like to donate these(or just one of them) so we can get an > permanent side. > Mirror the debs on your machice, provide the url and we will put it in kde.txt. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9a0alYsCKa6wDNXYRAgdrAJ96VHAWpCbEnCo8aiMApe1MK3nspQCgnQFF rTx7ln7JPqHJLtXj4W8FvMQ= =oR7S -END PGP SIGNATURE-
Re: building qtlib fails?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 25 August 2002 10:49 pm, John Gay wrote: > I am still working on my Linux From Scratch box and have run into another > problem. > > To build qt and kde3 in system standard locations, I've selected /usr/qt > and /usr/kde for the build locations. I've un-tarred qt-3.0.2 into /usr and > created a sym-link of /usr/qt, since qt says it should be built in place. > I've set the environment for the /usr/qt location, but when I try to build, > I get a segmentation fault. Since the box is next to me, I'll copy the > error message portion. > > make[2]: Entering directory '/usr/qt-3.0.2/src' > /usr/qt/bin/moc kernel/qapplication_x11.cpp -o > .moc/release-mt/qapplication_x11.moc > make[2]: *** [.moc/release-mt/qapplication_x11.moc] Segmentation fault > make[2]: Leaving directory '/usr/qt-3.0.2/src' > make[1]: *** [sub-src] Error 2 > make[1]: Leaving directory '/usr/qt-3.0.2' > make: *** [init] Error 2 > > I've tried the usual make clean, make distclean and even removing the > entire directory and starting again. The reason I'm using this particular > version is I got it on a cover DVD with KDE3Beta2 from a local Linux > magazine and it saves me hours of down-load time this way. > > Since I know that quite a few people here are building different versions > of kde, I was hoping someone might know why I'm getting this error? > > At the moment, I've got a rather sparce Linux installed on this box and > I've added xfce for a standard Desktop/Window manager but I'd really like > to see KDE3 on it. And since I pay per minute for my Internet connection, > I'd really like to avoid having to fetch the full sources if I can get by > with the ones I have. > > Does anyone know if there is a known problem with this version of qt? It > seems strange that everything else I've compiled on this box works bar > this. > don't compile Qt with objprelink - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9a0LWYsCKa6wDNXYRAvAmAJ4hTZiVAqade8gQf7xGXIex0VqKFQCfTg2E EYFG7IZUwt74zlvWMnfRowI= =6OuY -END PGP SIGNATURE-
Re: Can Konqueror 2.2.2 support the protocol https
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 10 August 2002 1:28 pm, Roland Wegmann wrote: > Hello > > I have the problem that Konqueror 2.2.2 can't open pages using the protocol > https. For example, when I try to login in some online shops Konqueror > tells me that the protocol https isn't supported. > > Exist there a way that Konqureor 2.2.2 can handle this protocol ? > > By the way, I am using a iMac-Woody-Box > > Tanks for your hints in advance!! > > Roland Wegmann > [EMAIL PROTECTED] install kdelibs3-crypto package - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9VPQCYsCKa6wDNXYRAnNeAJ0SEYm2uAYKwCFd/LL+f0+bTTtOwACgofFl zrb65EQD0Bwn3o5US1z9waU= =oHTF -END PGP SIGNATURE-
Re: kdelibs4-doc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 06 August 2002 7:45 am, Nikolaus Regnat wrote: > I have installed kdevelop (2.1.2 also tested 2.1.3) and kdelibs4-doc and > was wondering why kdevelop does not recognise the KDE-library documentation > from kdelibs4-doc. Even pointing kdevelop at the proper location does not > work. The downloaded KDE API Reference works. So can anyone tell me if I'm > doing anything wrong (or am I missing something) or is the kdelibs4-doc > package not intended for this purpose? > > Nik > 3 or 4 weeks before KDE 3.0.0 was released, kde changed from using kdoc(?) to doxygen. This meant that kdevelop did not have chance to respond to the change in format, and so kdevelop doesn't detect the docs. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9T5VAYsCKa6wDNXYRAmO4AKCQ8mLDUTFNPqlK5QuZgWgvdzx3/QCfXfSi fs1u7NULsArBr8gMfPhguhk= =TTec -END PGP SIGNATURE-
Re: KDE3 -- Where did kuickshow go?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 20 July 2002 11:34 am, Felix Homann wrote: > I can't find kuickshow in the debs provided at geniussystems. Is it just > not packaged or where can I find it? > > Thanks, > Felix IIRC kuickshow is linked against imlib and as imlib is one of the biggest causes of libpng problems, calc decided to not ship kuickshow until the whole libpng2/libpng3 thing is sorted. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9OUuWYsCKa6wDNXYRAi1dAJ0aWt/CyVEk+dl9IrZ/yW/zhHT40QCbBxzV ZtrGCy+Gwb8niQJJftGyIf8= =yAct -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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
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: 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: KDE 3.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 15 July 2002 11:09 am, Karolina Lindqvist wrote: > måndagen den 15 juli 2002 10.49 skrev David Pashley: > > Bit of a waste of effort there as the packages are being kept up to date > > in CVS. The builds may break, but I know that arts, kdelibs and kdebase > > did work last week. > > Let's have a look in the CVS updated today: > > for f in /q/cvs/kde3/*/debian/changelog; do head -1 $f; done > arts (1.1.0-1) unstable; urgency=low > kde3-i18n (3.0-0.alpha1-1) unstable; urgency=low > kdeaddons (3.0.9-1) unstable; urgency=low > kdeadmin (4:3.0.5-1) unstable; urgency=low > kdeartwork (3.0.2-1) unstable; urgency=low > kdebase (4:3.0.6-1) unstable; urgency=low > kdebindings (2.1-final-1) unstable; urgency=low > kdeedu (3.0.2-1) unstable; urgency=low > kdegames (4:3.0.0-0rc4-1) experimental; urgency=low > kdegraphics (4:3.0.5-1) unstable; urgency=low > kdelibs (4:3.0.6-1) unstable; urgency=low > kdemultimedia (4:3.0.6-1) unstable; urgency=low > kdenetwork (4:3.0.9-0) unstable; urgency=low > kdepim (4:2.9.9+cvs.20020110-1) unstable; urgency=low > kdesdk (3.0.2-2) unstable; urgency=low > kdetoys (4:3.0.2-1) unstable; urgency=low > kdeutils (4:3.0.9-1) unstable; urgency=low > koffice (1:1.2-beta2-1) unstable; urgency=low > qt-copy (2:3.0.3-20020329-5) unstable; urgency=low > > It does not look very updated to me: > kdelibs, kdebase, kdemultimedia are at version 3.0.6 Up to date. In fact kdelibs has just been updated by me and kdebase will follow shortly. > kdeaddons, kdenetwork, kdeutils are at version 3.0.9 I think these are a couple of weeks old. > kdeadmin is at version 3.0.5 This is probably a week or 2 old > kdeartwork, kdeedu, kdesdk, kdetoys are at version 3.0.2 These are Ben Burtons packages > kde-i18n is at version 3.0.0.alpha1 i18n is a law unto itself > kdegames is at version 3.0.0 rc4 I think that is also one of Bens. I'd need to check > kdepim is at version 2.9.9 > koffice is actually at current level, 1.2 beta 2 > This should be reasonalby current. > -- Karolina - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9Msr7YsCKa6wDNXYRAt2kAJ9gxXzwqqbMyPKA2LhHd8WsO1v5gwCeMRjh zG1RibBZuUItFLcG2m5FDag= =skE4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 13 July 2002 5:51 am, Karolina Lindqvist wrote: > lördagen den 13 juli 2002 00.54 skrev David Bishop: > > Well (and maybe this is what Jon meant) is anyone planning on packaging > > up the beta releases? I don't think anyone should bother with the alphas > > (too much of a moving target), but at least with Ivan, there was a > > tradition of putting the last few betas and release canidates through > > sid, or up on people.debian.org. Obviously, as I'm not volunteering to > > do the packaging and maintainence myself, this is a simple query, not a > > demand :-) > > After the long wait and all the trouble, instead of wining I keep my own > packaging for debian and have everything for 3.1 alpha packaged. Not to the > same high standard as the real packaging, but in a working condition. I am > running 3.1 alpha since about a week, and it appears to work pretty good > now. > > I try to keep the same packaging as the real stuff, even if that is a > moving target, but have a sligthly different way of doing it, since I often > incrementally rebuild from new cvs updates, and I also have a system that > catch changes > > And then I also found in the past that building kde on my own system is so > much more stable than the general builds. Particularly after all the > problems this spring. I also get the latest KDE patches incorporated when > they come. > > -- Karolina Bit of a waste of effort there as the packages are being kept up to date in CVS. The builds may break, but I know that arts, kdelibs and kdebase did work last week. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9MoyzYsCKa6wDNXYRAqyOAKCS3kZTqkqOjV67wKa/mlNWg5wpdQCfZITw QxSLUMafqKJnhUMGpOXJ/5Q= =3JbT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debianrules
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 10 July 2002 10:06 am, Achim Bohnet wrote: > On Wednesday 10 July 2002 07:49, David Gibb wrote: > > Hi! > > > > I'm trying to start learning how to package kde programs, and I came > > across admin/debianrules files. I've figured out they relate to > > packaging, but I'm not sure how. Can anyone explain how the debianrules > > file is used, or point me somewhere it is explained? > > AFAIK it's special for the debian kde pkgs. If you check the debian subdir you'll find: > > grep -d skip admin/debianrules debian/* > > debian/rules:debian/debiandirs: admin/debianrules > debian/rules: perl -w admin/debianrules echodirs > debian/debiandirs > debian/rules: perl -w admin/debianrules echoglobals > > debian/system.kdeglobals > > Run those command without the redirection and you 'see' what they do ;) > The rules file is the Makefile that is used to build the package > (see http://www.de.debian.org/doc/maint-guide/ch-dreq.en.html#s-rules) > > Short story: debiandirs defines the environment and options for configure. > system.kdeglobals is later installed in /etc/kde3 As Achim explained it provides a list of configure options to use. As the admin dir is shared by all kde modules it means that all debian KDE packages have the options for file locations. systems.kdeglobals needs the same information so it makes sense to use the same program to generate it. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9LFsBYsCKa6wDNXYRApAzAJ0UqwgKW5ndhyEi0OqsJvUUT3AVsACdEh9O MkFLlwBvtqdqt3H2FvnI+Js= =a4Bu -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Tips for Debianizing KDE3 apps?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 24 June 2002 10:07 pm, Jarno Elonen wrote: > Hi, > > Could someone (Chris?) spare a moment and share with us some secrets of > Debianizing KDE3 packages? > > What to look out for (e.g. objdir!=srcdir problems and how to solve them), > have you made your own dh_make templates or other tools for KDE 3 etc? > If the program uses autoconf/automake, this should work, but as kde-i18n doesn't don't hold your breath. > (The inspiration for this request comes from having been trying to get > Kwave and Pixie plus working on Debian with KDE 3. Neither works fine if I > just "make install" but complain about missing plugins - and besides, > trying to Debianize them is a great exercise.) > > - Jarno Probably the best thing to do is to copy the debian/rules and admin/debianrules files for kdelibs and then modify them as required. This is what I did for a quick koffice package. There was a text file in kdelibs which explained how to package kde apps. I don't know if calc has updated it for the new packaging. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9GCZMYsCKa6wDNXYRAnAJAJ4z/1gB18p+cGHCwgVQT2a24HbAVgCgmmWh SJ9cEzSwRk1VRg5fhoqxHrw= =2LlV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3 packaging - bug thread
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 11 June 2002 6:40 am, Jarno Elonen wrote: > > into sid so can everyone please post outstanding bugs against current > > kde 3 packaging as a reply to this message (so it will thread properly). > > Apply this patch in /kdelibs/khtml/, if it's not already in CVS, so that > plugins (e.g. Flash) work correctly. At least the deb for 3.0.1-0.1 doesn't > contain it yet and thus refuses to show Flash on web pages. > > The patch was sent to me earlier by Stephan Jaensch on this list during > thread "KDE3, Konq & Flash". > > - Jarno - From what I remember, this has been back ported into KDE_3_0_BRANCH, but you may want to check. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9BbatYsCKa6wDNXYRAjt6AKCjDQt7mkKKC1xTU3SJK2WkcWxe8ACfSH0s NjjwBGZz5SmZtz/7YBKP5QE= =cAv2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3 packaging - bug thread
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 11 June 2002 12:01 am, Chris Cheney wrote: > On Tue, Jun 11, 2002 at 12:28:37AM +0200, Reinhold Kainhofer wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On Tuesday 11 June 2002 00:05, Chris Cheney wrote: > > > time). I need to know all current outstanding bugs that I still have > > > not taken care of however, so people won't be screaming when it goes > > > into sid so can everyone please post outstanding bugs against current > > > kde 3 packaging as a reply to this message (so it will thread > > > properly). > > > > Hmm, not really a bug, but a wish (and a very annoying thing to me): Is > > it possible to have libarts and libarts1 coexist? The same for kdelibs3 > > and kdelibs4. Currently, updating to kde 3 will deselect the old ones, > > and with it important things like all additional apps for kde2 (of > > course), but also wine!!! So users have to decide whether they want wine > > or kde 3 :-( And the other thing with these dependencies is that whenever > > you incidentally select a kde 2 app (e.g. kwintv, koffice etc.) in > > dselect, all kde3 packages are deselected in the dependencies conflict > > page, and I have to select them manually again to prevent them from being > > removed. > > I will look into libarts/libarts1 issue, but I know for certain the > kdelibs issue is not resolvable, I have looked at it along with Kurt > Granoth. If I remember correctly, it is almost possible to do but > leaves the programs that do work limping along, certainly not in state > most users would want. > > Once KDE 3 goes in though a lot of the KDE 2 apps will be updated. So it > won't be nearly as big a problem as it is with KDE 3 outside the archive. Could libarts1 provide libarts? are they compatible. Has anyone found anything that does not work with libarts1 that did with libarts? - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQE9BbZpYsCKa6wDNXYRApXEAJjdh2RTaStvszxXLLGkLK1WYTmSAJ437Wdb wBfclin+s/hBqPjq6e8fng== =Ef/5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Xinerama not recognized by KDE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 17 May 2002 12:31 pm, Marcel Kossin wrote: > with two Graphiccards in "Xinerama-Mode". After > installing the latest kdelibs3 with apt-get I tried to use it with KDE > but unfortunately it didn't Work. > After starting kdm I have the login Window on one Monitor and the other > Monitor only shows a naked X. After logging in KDE is started on the one > screen. On the other screen appears a second KDE window. I can use the > mice and the keyboard on both Monitors but each Monitor seems to show a > single Session. It is not possible to Move Windows from one Monitor to > the other. I can configure each Monitor (kicker, background, wallpaper, > etc.) But I am logged in as the same user. I didn't see or use Xinerama > on KDE before but I think that's not the right behaviour?! > > > The other problem is that I can't use the Option "activate Xinerama" in > "Window Behaviour". That means I can see the Options, but I can't use > them. > > > Are there some other Options that have to be activated? > > > Are there some Hardwarelimitations? the second Graphiccard is running > with a "vesa" Driver 'cause I didn't find a s3-Driver in XFree86 > 4.1.0.1. You will probably find that this is due to the QT 2 libraries are not compiled with Xinerama support. This probably will not be changed in woody. As for sid, QT3 (and KDE3) is currently compiled with Xinerama on i386. When KDE3 enters sid, the optio should work. You may be able to get Ivan to enable Xinerama in Qt 2 for sid, but it may not be worth the hassle when KDE is just around the corner. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE85QnzYsCKa6wDNXYRAqfKAKCN6/mFMu3a8Bm9d1OSRttvIIjIMQCcDYtE uqbdlQ6CV2IfJ9hoGyaRtI4= =AUxN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Out of Office AutoReply: [KDE3] KPager/workspace weirdness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 02 May 2002 2:58 am, Chris Cheney wrote: > On Thu, May 02, 2002 at 02:26:15AM +0200, Mayer, Christian (Dregis) wrote: > > Bin erst am 6.5.02 wieder im Hause. Bitte wenden Sie sich in dringenden > > F?llen an "team-adsm" > > Fix your damn autoreply program not to reply to list traffic. > I thought that too, but you'll notice they are using Outlook Express, which I believe is incabable of being nice to mailing lists, and even though I can't read much german (beyond having a strange maternal relationship) it looks like they will not be back until Monday. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE80PvZYsCKa6wDNXYRAoOeAJ4j05A9hkJ9Rmt2JbjNsKc2H9QBfgCaA7DO wmOLX3ojJhQeSikNjo5YfIc= =4t/C -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 Logout
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 01 May 2002 10:24 pm, Carlos Acedo wrote: > Hi! > > I have seen in other distros such as mdk or gentoo that, when logout you > get a menu: Logout, Reboot, Shutdown. With Debian I only get the logout > option, I have compiled my own KDE3, and I haven't seen any option for > this. > > I am unable to run KDM, when running simply as root with kdm takes no > effect, this is since I remove kdm form 2.2.2 > You only get the menu when you started KDE from kdm. if you use any other method of starting kde, you only get the logout confirmation. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE80PqnYsCKa6wDNXYRAm0fAJ0R8YXWjR0qC5+ULLp2OVzUjxAfDQCglC2A OKcte/AAtZKePZAQgc6mTYU= =13Ud -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE freezes on "initializing peripherals"
On Wednesday 01 May 2002 5:03 am, Phil Dibowitz wrote: > Greg C. Madden wrote: > > afaik, xserver-xfree86 is for Xfree86 ver. 4.x & xserver-svga is for > > Xfree86 ver. 3.x so I don't know if I am much help. > > I found that out later tonight - and switched backed to xfree4 and had some > help making some configuration changes and now all is working perfectly! > Thanks for everyone's help. > > > Phil For what it is worth, you will find more information about wht is going on after you have logged in in the ~/.xsession-errors file. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: When will it be ready?
Michael Stucki said, and I quote: > Hi Chris, > > > > So is it just me or was not everyone aware that Debian takes long with > > > packages > > > and you are not going to get them righ away. If you want that then you > > > should > > > try Redhat. I installed KDE3 on a RedHat box and its not all that > > > diffrent or > > > great, its a little bit fast and has a few new nice tools and it looks > > > even more > > > like Windows then it did before. I personally prefered 2.2.1 to 3.0 > > > from what I > > > saw at it at first glance. So I don't understand the huge hurry of > > > every one > > > wanting to get it. There are those who like to be running the latestst > > > greatest > > > and there are those who would like it stable first. Rule of thumb never > > > install > > > something that is brand new right away because there are going to still > > > be bugs > > > in it, I have hosed my box a few times doing this. > > > Yep, KDE 3.0.0 had quite a few bugs and they even still existed in 3.0.1 > > but puetzk is squashing them as quickly as I can find them. Hopefully > > 3.0.1 will be mostly bug free. I will most likely have debs finished by > > the time 3.0.1 is made available to packagers (May 8). I already have > > test debs available now but they still have a few debian specific bugs > > in them. > > But couldn't you at least update your "debian" control subdirectories on KDE > cvs? This would give anyone the possibility to play around with a running > base... > Under KDE_3_0_BRANCH, you should find reasonably up to date kdelibs, kdebase, kdeadmin, kdenetwork and probably more (I just can't be bothered to check). arts debian is currently in HEAD. I will backport it into ARTS_1_0_BRANCH hopefully later today. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpOTIrVhfaxk.pgp Description: PGP signature
