Re: ok folks...let's talk freeze...
> It would be a good idea to provide the "C / C++ Reference Guide", instead > of the page telling how to install it (in kdevelop, in the "books" tab). AFAICT, Ivan is not the current maintainer of kdevelop; you're probably best sending your request to Norman Jordan (see below), or even better filing a wishlist bug in the BTS. Ben. [EMAIL PROTECTED]:~> dpkg --status kdevelop Package: kdevelop Status: install ok installed Priority: optional Section: devel Installed-Size: 3160 Maintainer: Norman Jordan <[EMAIL PROTECTED]> -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] http://baasil.humbug.org.au/bab/ Public Key: finger [EMAIL PROTECTED] You are very cleverly deceptive, Funkyspice. - Bernie to me on the theology boards
Re: ok folks...let's talk freeze...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On November 29, 2001 02:21 pm, Macolu wrote: > > is there any pressing things that needs to be done to the packages that > > are currently in sid? Patches, submissions, last minute simple changes? > > > > Speak now or forever hold your piece. In a few weeks it will be RC bug > > fixes only. > > > > Ivan > > It would be a good idea to provide the "C / C++ Reference Guide", instead > of the page telling how to install it (in kdevelop, in the "books" tab). Even better, if kdoc didn't try to put your projects .kdoc file in /usr/share/doc/kdelibs3-doc/html/kdoc-reference/ that would be great! Ivan, is this a kdoc bug? a new prefence in kdevelop that I'm unaware of? or compile time definition or config file issue? Sheldon. - -- == "... all thoughts of selfish desire, ill-will, hatred and violence are the result of a lack of wisdom ... " - Buddha For an awsome fantasy role playing game checkout: http://lycadican.sourceforge.net GPG KeyID=04B7F7F8 GPG Fingerprint=4B0F 7202 FAFF D146 5F56 9E83 BE7F D7F7 04B7 F7F8 == -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8B6XBvn/X9wS39/gRAq6BAJ4q+fFiqp9X1d+lR2jTMMR6JG8AbwCfc0Ee nvjvgha4mGSffUD3JD+FqQA= =WbU1 -END PGP SIGNATURE-
Re: ok folks...let's talk freeze...
On Fri, Nov 30, 2001 at 12:57:48PM +1000, Mark Constable wrote: > On Thu, 29 Nov 2001 20:06, Ivan E. Moore II wrote: > > We are very close to freeze. I'm very impatiently waiting for word on > > ... > > Speak now or forever hold your piece. In a few weeks it will be RC bug > > fixes only. > > Minor knit, I've notice that in the last week with > Konsole, that using any console apps that use the > whole Konsole screen (like nano for instance) now > leave the cursor at the top of the screen on exit. > > Maybe there is a setting somehere to alter this and > the default has simply changed but it's quite an > obnoxious and unexpected behaviour... ie; if the > console screen is already full of output then when > editing a file with nano, upon exit the cursor is > at the top of the screen with all manner of previous > screen gunk still on the screen. > > Seeing no else (that I've seen) has commented about > this then it might be a setable option somewhere ? this has already been fixed and uploaded. Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
Re: ok folks...let's talk freeze...
> Minor knit, I've notice that in the last week with > Konsole, that using any console apps that use the > whole Konsole screen (like nano for instance) now > leave the cursor at the top of the screen on exit. This appears to have been fixed in the latest upload to unstable (2.2.2-3). Ben. -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] http://baasil.humbug.org.au/bab/ Public Key: finger [EMAIL PROTECTED] You must immerse yourself, and be one hundred percent with something. I have yet even to get my feet wet. - Tori Amos
Re: ok folks...let's talk freeze...
On Thu, 29 Nov 2001 20:06, Ivan E. Moore II wrote: > We are very close to freeze. I'm very impatiently waiting for word on > ... > Speak now or forever hold your piece. In a few weeks it will be RC bug > fixes only. Minor knit, I've notice that in the last week with Konsole, that using any console apps that use the whole Konsole screen (like nano for instance) now leave the cursor at the top of the screen on exit. Maybe there is a setting somehere to alter this and the default has simply changed but it's quite an obnoxious and unexpected behaviour... ie; if the console screen is already full of output then when editing a file with nano, upon exit the cursor is at the top of the screen with all manner of previous screen gunk still on the screen. Seeing no else (that I've seen) has commented about this then it might be a setable option somewhere ? --markc
RE: ok folks...let's talk freeze...
"Ivan E. Moore II" <[EMAIL PROTECTED]> wrote: > > --snip-- < > is there any pressing things that needs to be done to the packages that > are currently in sid? Patches, submissions, last minute simple changes? > > Speak now or forever hold your piece. In a few weeks it will be RC bug > fixes only. > > Ivan Ivan, I am back with my list of "nits" for your consideration. Same old stuff...klisa doesnt work properly plus a suggestion on the initial (startup) wallpaper on the main kde screen. All of these suggestions & nits apply to both the ALPHA and i386 arches. All are confirmed on the most recent packages from SID updated as of yesterday, 28 Nov 01. Problem #1. Clicking on "Local Network" will only find the "localhost" and no other network hosts. This remains as such even after configuring klisa in Control Center--> Network --> Lan Browsing. Investigation reveals that when klisa is configured this way, it will ALWAYS save the lisarc file in /etc/lisarc. However, the klisa initscript in /etc/init.d/klisa is set to read its configuration info from /etc/kde2/lisarc. Therefore the updated local config information in /etc/lisarc is never read. This problem appeared in KDE 2.2.X, and was not present in KDE 2.1.2. FIX to #1. There are probably better ways to do this, but I moved the supplied /etc/kde2/lisarc file out of the way and created a symlink to the /etc/lisarc file and re-started klisa. It will now "see" the other computers on the LAN. I tried the symlink the other way (from /etc/lisarc --> /etc/kde2/lisarc) but when I configured the network "Lan Browsing" again, the symlink was removed and a new /etc/lisarc file was created. Problem #2. Clicking on the (+) sign beside the "Local Network" icon will produce this error: "Cannot find parent item lan://localhost/ in the tree. Internal Error". Blind investigation here have revealed the "URL" line in the /.kde/share/apps/konqueror/dirtree/remote/lan.desktop file is set to "URL=lan:/". Changing this to read "URL=lan://localhost/" will restore normal behavior and clicking on the (+) sign beside the "Local Network" icon will expand to a sub-tree of all the LAN comuters found. This problem appeared in KDE 2.2.X, and was not present in KDE 2.1.2. BTW, I have found similar bug reports on the KDE bug list from other distros (SuSE,Mandrake). This would indicate this may be more of a KDE "generic" problem than just a Debian version problem. FIX to #2. For all accounts that already have a /.kde/ directory, the local sysadmin will have to manually edit the /.kde/share/apps/konqueror/dirtree/remote/lan.desktop file and make this change to make the system work correctly. HOWEVER, for new accounts and/or new installs of KDE where there is NOT an existing .kde directory, if the /usr/share/apps/konqueror/dirtree/remote/lan.desktop file contains this edit, then it will be applied to each new KDE setup created. This change also will allow deletion of old ~/.kde directories and re-generation of a corrected lan.desktop file automatically. This is something to consider for the final package if a better solution is not found. PROBLEM #3. The initial background is set to display the "Debian.jpg" wallpaper, however this wallpaper is never shown when first starting up KDE and going through the new setup wizard. I can later get it to display by first turning off the wallpaper setting (none) in Control Center --> Look & Feel --> Background and applying that new config, THEN redoing the above and selecting the Debian.jpg wallpaper and applying it again. This same thing has shown up on 4 different computers here over multiple installs (> 6) of KDE 2.2.2 . FIX to #3. (Suggested). Since the wallpaper is not currently being shown anyway, why not just set the default wallpaper to "none". This will possibly save some memory for users will limited memory resources. Submitted for your consideration. Cheers, -Don Spoon-
Re: ok folks...let's talk freeze...
> is there any pressing things that needs to be done to the packages that > are currently in sid? Patches, submissions, last minute simple changes? > > Speak now or forever hold your piece. In a few weeks it will be RC bug > fixes only. > > Ivan It would be a good idea to provide the "C / C++ Reference Guide", instead of the page telling how to install it (in kdevelop, in the "books" tab).
Re: ok folks...let's talk freeze...
On Thursday 29 November 2001 08:05 am, Ben Burton wrote: > > Speak now or forever hold your piece. In a few weeks it will be RC bug > > fixes only. > > Can I just verify that I'm still the only person finding kmail has been > slow as all hell for the last few weeks? > > Maybe it's my own setup. I was wondering if it was due to one of the > recent CVS updates. > > Ben. Ben: I had a case locally during an ISP foobar that kmail was slow. Every day, it just seemed slower. I was positive it had to be a DNS lookup issue. Everyone else on the lan had instant downloads except me! Finally, looking over the 'network' tab, I found the oops! I hand unchecked the box "delete mail from server" since I was using two email programs at one point. I had several thousand emails that kmail would have to sift through each check. It crashed kmail the first time it deleted the old mails, but then it was fine :) hthtatah -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
Re: ok folks...let's talk freeze...
Le Jeudi 29 Novembre 2001 17:05, Ben Burton a écrit : > Can I just verify that I'm still the only person finding kmail has been > slow as all hell for the last few weeks? No speed problem for me (using kmail 2.2.2-1, PIII 550)
Re: ok folks...let's talk freeze...
> Speak now or forever hold your piece. In a few weeks it will be RC bug > fixes only. Can I just verify that I'm still the only person finding kmail has been slow as all hell for the last few weeks? Maybe it's my own setup. I was wondering if it was due to one of the recent CVS updates. Ben. -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] http://baasil.humbug.org.au/bab/ Public Key: finger [EMAIL PROTECTED] It's so difficult to be critical of children because they need to discover themselves. We're always telling them, "No, the tree has green leaves! - Tori Amos, Women, Sex and Rock'n'Roll:In Their Own Words
ok folks...let's talk freeze...
We are very close to freeze. I'm very impatiently waiting for word on crypto in main so that I can get rid of the -crypto packages. I have a slowly increasing list of fixes/changes which will be uploaded within the next week... here are some things that I'm doing... * lots of build cleanup * lots of dependency cleanup (Moving alot of the Recommends to Suggests) * crypto build in main packages (pending...) * Xinerama support for i386 only * final sync with upstream...tho there hasn't been any changes yet... is there any pressing things that needs to be done to the packages that are currently in sid? Patches, submissions, last minute simple changes? Speak now or forever hold your piece. In a few weeks it will be RC bug fixes only. Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
