Re: [SOLVED] Re: State of KDE in testing?
Le 23 avril 2022 22:15:05 GMT+02:00, local10 a écrit : > >So I have upgraded from Bullseye to Bookworm. The upgraded wasn't completely >smooth, there were some errors and some packages "dist-upgrade" failed to >upgrade. But running "safe-upgrade" and then "full-upgrade" afterwards has >upgraded them. That's the recommended / supported way to upgrade between major Debian releases, so nothing too surprising here. See Debian 11's release doc §4.4.4 and 4.4.5 for example : https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade Welcome to bookworm. :-) Happy hacking, -- Aurélien
[SOLVED] Re: State of KDE in testing?
Apr 20, 2022, 18:56 by li...@coucouf.fr: > It's all fine and ready and fine as a daily driver on both AMD and Intel > graphics for what I use. > Even Wayland in Intel is mostly stable (like < 1 crash a week) in my > experience and setup. > > Possible breakages would happen around when a new major version of Plasma > gets released so the next would be mid-June with Plasma 5.25. > So I have upgraded from Bullseye to Bookworm. The upgraded wasn't completely smooth, there were some errors and some packages "dist-upgrade" failed to upgrade. But running "safe-upgrade" and then "full-upgrade" afterwards has upgraded them. The upgrade has solved some issues I had with Bullseye, added a couple of minor new issues but overall I'm happy with the upgrade: nothing is really broken, everything seems to work fine. Also, Bookworm seems to be a bit more responsive (the apps open and close a bit quicker) and it seems like it's using less RAM too. Comparing Bullseye and Bookworm, Bookworm seems to be a better release to me. Thanks to everyone who responded.
Re: State of KDE in testing?
Le 20 avril 2022 17:24:23 GMT+02:00, local10 a écrit : >Apr 20, 2022, 11:08 by li...@coucouf.fr: > >> One thing to be aware of is to be more careful when upgrading major versions >> of Plasma. We currently don't have a safe way to ensure that all Plasma >> packages transition form unstable (where we upload them) to testing at once. >> So be sure you know what you're doing when doing upgrades to ensure you >> don't end up with mixed versions of Plasma packages. >> > >That's what I was concerned about. I usually use "aptitude dist-upgrade" to >upgrade between releases, so will it catch a situation like that or will I >have to manually ensure that all KDE packages are of the same version? > >Also, what is the current state of KDE/X in testing, are all packages of the >same Plasma/KDE version? It's all fine and ready and fine as a daily driver on both AMD and Intel graphics for what I use. Even Wayland in Intel is mostly stable (like < 1 crash a week) in my experience and setup. Possible breakages would happen around when a new major version of Plasma gets released so the next would be mid-June with Plasma 5.25. Happy testing ! -- Aurélien
Re: State of KDE in testing?
Apr 20, 2022, 11:08 by li...@coucouf.fr: > One thing to be aware of is to be more careful when upgrading major versions > of Plasma. We currently don't have a safe way to ensure that all Plasma > packages transition form unstable (where we upload them) to testing at once. > So be sure you know what you're doing when doing upgrades to ensure you don't > end up with mixed versions of Plasma packages. > That's what I was concerned about. I usually use "aptitude dist-upgrade" to upgrade between releases, so will it catch a situation like that or will I have to manually ensure that all KDE packages are of the same version? Also, what is the current state of KDE/X in testing, are all packages of the same Plasma/KDE version? Thanks,
Re: State of KDE in testing?
Apr 20, 2022, 09:08 by s...@platonix.com: > I've been using KDE/X from testing for a few years, which implies I'm > generally pleased enough. As others pointed out, there are problems; > the one I've experienced most, in the last few weeks, is kwin crashing > (it restarts automatically and windows seem to all stay where they > were, so it's not terrible). > Thanks for your feedback. I'll have to think about it as my annoyances with KDE in Bullseye are minor as well, for example: https://bugs.kde.org/show_bug.cgi?id=445974
Re: State of KDE in testing?
Le 20 avril 2022 02:43:50 GMT+02:00, local10 a écrit : >Hi, Hi local10, >Am thinking about upgrading from Bullseye to Bookworm as there are some minor >bugs in Bullseye that annoy me and I hope they are resolved in Bullseye. >What's the current state of KDE in testing and testing in general? Any issues >I need to be aware of? I use KDE with X. Testing is in a generally usable state and many are using it as a daily driver. Obviously if you're running mission critical machines and cannot afford hicups you should be running stable. We try to follow upstream releases closely in testing with the latest upstream versions of Plasma and Gear (applications) currently available and the KDE frameworks libraries being slightly older. One thing to be aware of is to be more careful when upgrading major versions of Plasma. We currently don't have a safe way to ensure that all Plasma packages transition form unstable (where we upload them) to testing at once. So be sure you know what you're doing when doing upgrades to ensure you don't end up with mixed versions of Plasma packages. Or/and continue reading this list where transitions are announced and you get warned during transitions. Regarding the bugs we're following upstream closely, so as others have said we tend to have mostly upstream bugs. It's a bit easier to report these to upstream than if you're using stable though, because upstream focus is really on the latest versions and not on our stable ones. Happy testing ! -- Aurélien
Re: State of KDE in testing?
Hi, I've been using KDE/X from testing for a few years, which implies I'm generally pleased enough. As others pointed out, there are problems; the one I've experienced most, in the last few weeks, is kwin crashing (it restarts automatically and windows seem to all stay where they were, so it's not terrible). I should point out that I'm not a very sophisticated user, my common mode of operation is one window maximized on one screen, while ignoring the other screen; but I do mix windows from different users in one X-session. In fact, the thing that's been broken for me so long that I've learned how to deal with it, is sound only being available to one user at a time. Your mileage may vary, Shai.
Re: State of KDE in testing?
Hi,
All KDE has bugs, not just from Debian but also up-stream. I'd say "of
course".
I use to my satisfaction a close to up-stream, w.r.t. time, KDE packages
provided by Norbert:
https://www.preining.info/blog/2022/02/kde-plasma-5-24-for-debian/
Regards,
Luc
Op wo 20 apr. 2022 om 07:55 schreef Brad Rogers :
> On Wed, 20 Apr 2022 02:43:50 +0200 (CEST)
> local10 wrote:
>
> Hello local10,
>
> >as there are some minor bugs in Bullseye that annoy me
>
> {sigh} I'll reply in kind.
>
> >What's the current state of KDE in testing and testing in general?
>
> It's got bugs.
>
> > Any issues I need to be aware of?
>
> All of them.
>
> --
> Regards _
> / ) "The blindingly obvious is never immediately apparent"
> / _)rad "Is it only me that has a working delete key?"
> If you ain't sticking your knives in me, you will be eventually
> Monsoon - Robbie Williams
>
--
Luc Castermans
mailto:luc.casterm...@gmail.com
Re: State of KDE in testing?
On Wed, 20 Apr 2022 02:43:50 +0200 (CEST)
local10 wrote:
Hello local10,
>as there are some minor bugs in Bullseye that annoy me
{sigh} I'll reply in kind.
>What's the current state of KDE in testing and testing in general?
It's got bugs.
> Any issues I need to be aware of?
All of them.
--
Regards _
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
If you ain't sticking your knives in me, you will be eventually
Monsoon - Robbie Williams
pgpUxuPvxPcP_.pgp
Description: OpenPGP digital signature
State of KDE in testing?
Hi, Am thinking about upgrading from Bullseye to Bookworm as there are some minor bugs in Bullseye that annoy me and I hope they are resolved in Bullseye. What's the current state of KDE in testing and testing in general? Any issues I need to be aware of? I use KDE with X. Thanks,
KDE on Testing after last apt security update
I run testing etch on a different machine. Following latest download Monday 7 November, KDE is broken. Windows can no be slid around. Any and all application window headers and buttons are not present. Konqueror is not present. Window shading not possible. Configuration tools for KDE do not fix these problem. Gnome works OK. I am more used to KDE. The bug forms do not fit this problem. I will cooperate to answer any specific questions put to me. Thanks for all you do. [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SOLVED Re: kmail 1.5.4 / KDE 3.1.5 (testing/unstable) crashes
It turns out that the versions of kmail and kde I had after the upgrade don't match any of the versions in stable, testing, or unstable. This is because I did an 'apt-get upgrade' rather than an 'apt-get dist-upgrade', so kmail (and many other packages) were 'held back'. After an 'apt-get dist-upgrade', kmail works again (though other things are somewhat broken). Thanks, -- Robert
kmail 1.5.4 / KDE 3.1.5 (testing/unstable) crashes
I just did an apt-get upgrade, upgrading a few hundred packages. I now have kmail 1.5.4 and KDE 3.1.5. I'm not sure what I had before (how can I tell?). I can launch kmail, but selecting a message or selecting a folder causes kmail to pause, then exit silently. I've tried hiding all of the index files, so kmail would rebuild them (which it does), but it still crashes. Any hints? -- Robert
Re: kmail 1.5.4 / KDE 3.1.5 (testing/unstable) crashes
Robert Merithew [EMAIL PROTECTED] writes: I just did an apt-get upgrade, upgrading a few hundred packages. I now have kmail 1.5.4 and KDE 3.1.5. I'm not sure what I had before (how can I tell?). I'm not sure the packaging system keeps track of what version you *used* to run... I can launch kmail, but selecting a message or selecting a folder causes kmail to pause, then exit silently. I've tried hiding all of the index files, so kmail would rebuild them (which it does), but it still crashes. Do you still have that problem if you get the next older version? I generally keep the last month's worth of archives in my sources.list so I can rollback if I have to easily, even if I clear my package cache. # Prior few unstables including non-us deb http://snapshot.debian.net/archive/date/yesterday/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/yesterday/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/2-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/2-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/3-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/3-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/4-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/4-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/5-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/5-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/6-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/6-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/7-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/7-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/8-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/8-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/9-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/9-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/10-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/10-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/11-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/11-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/12-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/12-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/13-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/13-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/14-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/14-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/15-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/15-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/16-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/16-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/17-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/17-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/18-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/18-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/19-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/19-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/20-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/20-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/21-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/21-days-ago/debian unstable main contrib non-free deb http://snapshot.debian.net/archive/date/22-days-ago/debian unstable main contrib non-free deb-src http://snapshot.debian.net/archive/date/22-days-ago/debian
no text in menus KDE Debian testing/unstable
Hi all, I've installed debian via debian-installer (http://www.debian.org/devel/debian-installer/) in a vmware environment. All went well, configured and so; however, when I enter X, I can't read anything on the menus. The text simply doesn't appear. Sometimes it appears for a brief period of time (split-seccond), but never stays. This happens when I go to menu button, as well as dialog boxes (for example in Control Panel). I forgot, we're talking about kde of course ;-) Any of you experienced the same problem? How did you solved it? I plan to deploy debian on a toshiba a25-s207 laptop using debian-installer. Anyone did the same? Thank you. s --- Martisoare virtuale prin http://felicitari.acasa.ro
Re: no text in menus KDE Debian testing/unstable
Are you running Debian as a vmware virtual machine ? if so, you will need the vmware x-server module for X to work properly: http://www.vmware.com/download/downloadxserver.html On Sun, 2004-02-29 at 10:38, Sneferu wrote: Hi all, I've installed debian via debian-installer (http://www.debian.org/devel/debian-installer/) in a vmware environment. All went well, configured and so; however, when I enter X, I can't read anything on the menus. The text simply doesn't appear. Sometimes it appears for a brief period of time (split-seccond), but never stays. This happens when I go to menu button, as well as dialog boxes (for example in Control Panel). I forgot, we're talking about kde of course ;-) Any of you experienced the same problem? How did you solved it? I plan to deploy debian on a toshiba a25-s207 laptop using debian-installer. Anyone did the same? Thank you. s --- Martisoare virtuale prin http://felicitari.acasa.ro -- James D. Freels, Ph.D. [EMAIL PROTECTED] [EMAIL PROTECTED]
KDE for testing
Hello all, Where is the best place to download debs from for testing now? I am using the kde site set but it doesn't seem to have several things. eg kpgp. Regards, Stephen.
Tips on CUPS + KDE + Debian Testing NOTE: long msg!
I recently decided to install CUPS on my main linux box with the eventual goal of making it a print-server for the rest of my home LAN. I was sucessful in getting it going on the single machine because of questions asked by others on the Debian-KDE and Debian-Users mailing lists. Getting it going on a single machine has been discussed in previous messages, so I won't dwell on that aspect of it except to make a few notes: 1. The cupsys-driver-gimpprint package is EXCELLENT. It supports a wide variety of printers, and of all the printer drivers I have tried, it far excels in the quality of printing on my HP 960c inkjet. Highly recommeded! BEWARE! This package comes in several languages ALL are installed. The en is the second selection from the top, and is NOT diferentiated as such during the KDE printer config. You can only see the differences if you use the localhost:631 method to configure your printer. 2. If you are going to be in a mixed system that involves some lpr systems, you might want to pay close attention during the install to the question about setting cupsysd suid root. My LAN is/will be straight CUPS, so it didn't make much difference. You also want to install the cupsys-bsd package. 3. A fully-functional CUPS + KDE install in Debian Testing will require the following packages: cupsys, cupsys-client, cupsys-pstorastor, libcupsys2, and kdelibs3-cups. If you want lpr/bsd compatability with other printing systems, you should add cupsys-bsd. 4. The KDE Control Center - System - Printing Manager tool is EXCELLENT. About all you have to do to get a running system is select CUPS as your printing system at the bottom, and add your printer. This will bring up a wizard that will lead you through all the steps. This is the series of screens that will show you about 4 available gimpprint drivers that all look the same. They are not... select the second one from the top if you want English or check it with the http screens available at localhost:631. After I got CUPS running on a single machine, I turned my attention to getting it on my LAN as the LAN printer. I wandered around in the desolate wilderness of the documentation for about a week without any progress. I finally yelled for help on the Debian-Users mailing list, and a kind soul guided me through a MANUAL config for the network. After I got it going, I re-traced my steps, and again, the KDE Printing Manager proved to be the BEST tool to set it up. Here are the steps: 1. Pull up the Printing Manager and click on the Configure Server Icon. 2 Accept the default settings EXCEPT for the below steps: 3. Check the Enable Browsing on the Browsing screen. 4. Go to the Security screen. In the Resources box, you should find two entries already there.. one for Root and another for Administration. Click on add and select your printer's name (lp?) from the pull-down resource menu. Click on the Access tab and put your LAN IP number in the Allow box (i.e. 192.168.10.*) and ALL in the Deny box The order should be Deny, Allow. Click OK to save the changes. 5. Restart the server... there is a button for it to the left of the Configure Server icon. At this point remote computers running CUPS will list your printer and you can set it to be the default on the remote systems. Check out everything by printing test pages. I hope these ruminations will prevent others from the aimless wandering and editing of various conf files that I did. I appologize to those who think I have wasted their time. Cheers, -Don Spoon-
Re: unstable KDE situation? TESTING
Magnus von Koeller Spoke Thusly: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 19 November 2001 22:52, James Lindenschmidt wrote: I am running pure unstable, with KDE 2.1. I know that KDE 2.2 is currently making its way into unstable. I'm looking forward to upgrading, but I can't afford a complete KDE crash and burn at the moment. Is it safe to upgrade? I know it takes 10 days for the packages to clear. Are you talking about testing? Because KDE 2.2 is already in unstable (packages get there immediately ...). Did you mean you're running testing? Yes. Sorry. Brain cramp. I meant testing not unstable. -- Jim -- [EMAIL PROTECTED] --
Re: unstable KDE situation? TESTING
On Monday 19 November 2001 02:14 pm, James Lindenschmidt wrote: Magnus von Koeller Spoke Thusly: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 19 November 2001 22:52, James Lindenschmidt wrote: I am running pure unstable, with KDE 2.1. I know that KDE 2.2 is currently making its way into unstable. I'm looking forward to upgrading, but I can't afford a complete KDE crash and burn at the moment. Is it safe to upgrade? I know it takes 10 days for the packages to clear. Are you talking about testing? Because KDE 2.2 is already in unstable (packages get there immediately ...). Did you mean you're running testing? Yes. Sorry. Brain cramp. I meant testing not unstable. I moved over to the 2.2 version in testing and had two problems: - kmail was broken (see earlier mail) - the qt libs made konqueror a bit wobbly Both of these (with some help from this list) turned out to be easy to fix with a bit of package fiddling, but it's not yet a completely no-stress transition. - Derek
Re: task-kde* for testing/unstable
On Thu, Jul 05, 2001 at 08:47:38PM -0500, Stephen Uhlhorn wrote: Okay guys, now I'm confused...and reading thru the archives has not helped. I just gave my potato box a woody, i.e.- stable-testing. I'm reading through the archives about all these great new AA features, and where the docs are, etc. But the thing I find most puzzling iswhere are the task-kde* debs? I really liked my potato box, and I'm new to the testing/unstable thing, so don't be too harsh...I'm a very sensitve person. Are there any task packages in testing/unstable? ...and where is that task-anti-aliasing package I read so much about? Thanks. there is not task-anti-aliasing anymore..it's just anti-aliasing-howto as that's mostly what it is. as for the tasks... there is a task-kde, task-kde-devel, task-kde-extras, task-kde-games. they may not be in testing and I've heard they are not. These tasks depend on a lot of packages and in order to get into testing each and every one of those packages must conform to the guidelines for entrance into testing. 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: task-kde* for testing/unstable
On Jul 05 2001, Ivan E. Moore II wrote: they may not be in testing and I've heard they are not. These tasks depend on a lot of packages and in order to get into testing each and every one of those packages must conform to the guidelines for entrance into testing. That's right: task-kde (at least) is still not in testing, unfortunately. BTW, I just installed the base system of a Debian 2.2 and made an upgrade *directly* (via a hand installed apt) to testing. This is one of the reasons Debian rocks. []s, Roger... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogério Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
task-kde* for testing/unstable
Okay guys, now I'm confused...and reading thru the archives has not helped. I just gave my potato box a woody, i.e.- stable-testing. I'm reading through the archives about all these great new AA features, and where the docs are, etc. But the thing I find most puzzling iswhere are the task-kde* debs? I really liked my potato box, and I'm new to the testing/unstable thing, so don't be too harsh...I'm a very sensitve person. Are there any task packages in testing/unstable? ...and where is that task-anti-aliasing package I read so much about? Thanks. Sheepishly, Stephen
Re: KDE and testing
(1) Are the kde.tdyc debs. pure potato? no. but what isn't is there. (2) If I download the unstable .debs (wherever they may be) into my local .deb repository (applying dpkg-scanpackages on them and thereby making them locally apt-gettable for my testing system): Would the dependencies for non-KDE/qt apps come from unstable? Or are the kde .debs so packaged that they would pull from whatever source (either stable/testing/unstable) available regardless of version number. huh? I don't follow...the qt that's in unstable will work fine in testing... or should. 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: KDE and testing
Two questions: (1) Are the kde.tdyc debs. pure potato? (2) If I download the unstable .debs (wherever they may be) into my local .deb repository (applying dpkg-scanpackages on them and thereby making them locally apt-gettable for my testing system): Would the dependencies for non-KDE/qt apps come from unstable? Or are the kde .debs so packaged that they would pull from whatever source (either stable/testing/unstable) available regardless of version number. On Friday 09 March 2001 03:20, Ivan E. Moore II wrote: On Thu, Mar 08, 2001 at 05:54:16PM +0100, Thibaut Cousin wrote: Ivan, you told us one or two days ago that those using testing should take the KDE packages for woody, not those for potato. You mean, take them from the package pool ? The problem if I do that is that I have to point to unstable instead of testing... is there another place I can make apt-get point to ? Testing is OK for me, but I don't want unstable. I mean take them however you feel comfortable taking them. The latest version of apt allows one to have multiple apt lines and pull from specific pools... aptget install kdebase/unstable for example...(not sure if that's the exact command line...) so that's one option,the other is to go and download the packages directly out of the pool...my personal favorite is to run unstable..as it's far better than testing. Ivan
KDE and testing
Hi, I'm considering moving from 'potato' to 'testing' but I thought I should see if anyone would like to share their experiences with KDE and 'testing' (or even just 'testing'). Also, what are the appropriate sources.list lines that one should use for the KDE packages that go with 'testing'? (I know KDE is to be a part of woody, and hence testing, but I didn't know if that was in place yet.) Thanks - pat
Re: KDE and testing
Patrick, I just did it today. It is very easy to add the single word to your sources 'beta'. I used apt-get and was a little mystified to see that EVERYTHING kde was removed and nothing was added :) So, off to dselect land and reselected the 2.1 packages and it did it's trick. I Missed some stuff the first pass and when back to it again. I really like it though! The look and feel works WAY WAY better and I finally have an appropriate startup sound file :) Games didn't come back and I'm gonna post a message about that next. my pain rating for this is .1 out of a possible 5 :) tatah On Tuesday 09 January 2001 13:03, Patrick K Notz wrote: Hi, I'm considering moving from 'potato' to 'testing' but I thought I should see if anyone would like to share their experiences with KDE and 'testing' (or even just 'testing'). Also, what are the appropriate sources.list lines that one should use for the KDE packages that go with 'testing'? (I know KDE is to be a part of woody, and hence testing, but I didn't know if that was in place yet.) Thanks - pat -- Jaye Inabnit, ARS ke6sls e-mail: [EMAIL PROTECTED] 707-442-6579 h/m 707-268-4074268-4074//www.qsl.net/ke6sls ICQ# 12741145 This mail composed with kmail on kde on X on linux warped by debian If it's stupid, but works, it ain't stupid.
