Re: 178 days and counting
On Sun, 29 Sep 2002 01:34, David Pastern wrote: eh? Thanks, but no thanks. I'm running on a Class C internal network where I live, with a direct backend into the ms exchange server (yes the gentleman where I live runs his own ISP, Microsoft based without a single touch of linux as he thinks it's a pile of shit and a fad - oh and he does have 20 years or so of experience in the IT industry). Therefore I do not Many people have 10 or more years IT experience where it's just the same year repeated many times, I fear that your husband(*) might be one of them. have a pop3 or imap account to set up mutt, evolution etc. At the moment Apparently Exchange does support POP and IMAP, but the administrator has to install it (it's not usually part of the default install). Unfortunately most Exchange admins aren't capable of anything other than a default install... (*) I use the term husband in a colloquial form, gay marriages aren't legal in Australia. You and the gentleman you live with would have to visit Europe to actually get married. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
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-
KDE 3.2-beta2
KDE 3.2-beta2 appears to never get announced. I guess it is delayed. (or have I missed the announcement somehow). When I packed the KDE 3.1 beta1, I more or less took the version from CVS and compiled it. But now for KDE 3.2-beta2 I have put down much more work on packaging and it is branched off from the CVS version in a direction of its own. One thing I have done is to break out many libraries from kdelibs so that there is no monolithic kdelibs4 anymore, but instead a group of smaller packages containing one separate library or a group of related libraries. The reason for this is not package bloat, but to make it possible to install a KDE application and just need to install just those libraries that are needed, and not all kdelibs libraries. It is also so that applications from different versions of KDE possibly can coexist. One typical example was the libkjava library, that does not exist anymore in kdelibs, but since it was not separately broken out, old kde applications can't run anymore. I am still working on everything, now more on the level of filling in holes, fixing things to adhere better to debian policy, fixing installation clashes, requirements, etc., writing manual pages and things like that. As things sounds, this might be the only debian packed version of kde 3.1 compiled with the old gcc compiler. Testing of everything might take forever, since I am only one person, so whoever want to try, the whole thing is available. I will fix problems when they are reported, if it is something within my powers and I can figure out how to fix it. Someone that want something stable - don't bother. Someone who want to test (and hopefully report problems), the whole thing is available with http: protocol on http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-beta2 and with ftp on http://cgi.algonet.se/htbin/cgiwrap/pgd/ftp/debian/kde3.1-beta2. (Yes, http:, not ftp, since a cgi script is supplying the ip address) This time it is apt-aware, and is in subdirectories. Also in the directories is a file on the form kde-debian-src.tar.gz, which contains the debian files that differ from them in those in the cvs. (Not exactly, since I have a build script that might do some extra things, but the files are there for reference) Just note that this is still a cvs snapshot, and there are problems from KDE. The KDE cvs is still in quite a flux, which might be why the beta2 freeze is not done yet. I have not had time to try installing just one applicatation without KDE, to see what happens. I want to fix so that works. But it is not tested. Some package might require some rare library. I am trying to eliminate that in some instances, and break out a separate package for that rare library. But actually, I don't even know which libraries are rare, so if someone finds something, and reports it, I might fix it. As usual, my machine has a dynamic IP-address (don't save the numeric address), and has a slow ADSL connection that appears to be able to deliver only something like 800kbps, so it can be slow. -- Karolina
KDE troll (was: Re: 178 days and counting)
Many people have 10 or more years IT experience where it's just the same year repeated many times, I fear that your husband(*) might be one of them. Please don't insult any sexual minorities by comparing them to mr. Troll. There are quite a few non-hetero Linux and KDE hackers, FYI. - Jarno
Re: 178 days and counting
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
Re: KDE 3.2-beta2
Am Sonntag, 29. September 2002 13:03 schrieb Karolina Lindqvist: As usual, my machine has a dynamic IP-address (don't save the numeric address), and has a slow ADSL connection that appears to be able to deliver only something like 800kbps, so it can be slow. I mirrored your site to our server... it has a 100mbit connection :) but in exchange i removed the previous 3.0.1 mirror from geniussystems.net, that was there... the debline is: deb ftp://wh9.tu-dresden.de/kde3 ./ -- Karolina -- MfG, Christian Welzel (Sektionsvorsitzender und Admin AG DSN Gerokstrasse) GPG-Key: http://www.wh9.tu-dresden.de/~gawain/key.asc Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15
Re: KDE 3.2-beta2
söndagen den 29 september 2002 13.38 skrev Richard Ibbotson: Put this line into sources.list.. deb http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-beta2 ./ and I'm getting an error message which says.. Failed to fetch http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-beta2/ ./Packages Sub-process gzip returned an error code (1) How do I fix this so that I can download KDE3.1 beta 2 ? Ok, I have figured out why it does not work. The cgi-script is sending the correct IP-address with a meta http-equiv=refresh content=0; url=x.y.z.. and APT-HTTP and wget and things like that just don't understand that. Sorry, then I just don't know how to make apt-get translate the ip address, so I don't know how to make a working sources.list string. -- Karolina
Re: KDE 3.2-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 29 September 2002 13:38, Karolina Lindqvist wrote: Ok, I have figured out why it does not work. The cgi-script is sending the correct IP-address with a meta http-equiv=refresh content=0; url=x.y.z.. and APT-HTTP and wget and things like that just don't understand that. Sorry, then I just don't know how to make apt-get translate the ip address, so I don't know how to make a working sources.list string. I don't know if apt will respect it, but the correct way of doing what you want would be for your cgi program to return a HTTP 302 code, telling the agent/client (apt in this case) to use a different IP/location/URI. If you use 302 as oppsed to 301, then the client (apt) will still go to the cgi program each time it is run, and not cache the new location/URI. The HTTP header should contain something similar to: HTTP/1.0 302 Found Location: http://a.b.c.d/~path/to/files If you post your code, I'm sure someone will help you modify it. Paul Cupis - -- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9lvd5IzuKV+SHX/kRAkITAJ4lLRRUfRtp4SccoHAtxaojyGvwlACaAkoq 6Stj9sYyQgeNR74KgPnpPC0= =nCYt -END PGP SIGNATURE-
Re: KDE 3.2-beta2
söndagen den 29 september 2002 14.03 skrev Christian Welzel: I mirrored your site to our server... it has a 100mbit connection :) but in exchange i removed the previous 3.0.1 mirror from geniussystems.net, that was there... the debline is: deb ftp://wh9.tu-dresden.de/kde3 ./ That's good. People just have to get it from there then. I guess I need a mirror that either is doing updates automatically somehow (which can be hard if I have a changing ip address), or to where I can upload the files when they change. -- Karolina
AW: KDE 3.2-beta2
Hi! I guess I need a mirror that either is doing updates automatically somehow (which can be hard if I have a changing ip address), or to where I can upload the files when they change. If your dynamic IP ist the problem, why don't you just use one of the free dns services? I'm using dyndns.org for years now, and it works wonderful. (they have tons of different clients/scripts to automatically update your ip). Once you have a dns with your current ip, it shouldn't be a big problem to set up an automatical mirror. Flavio
Re: KDE 3.2-beta2
On Sun, 29 Sep 2002 14:53, Karolina Lindqvist wrote: söndagen den 29 september 2002 14.03 skrev Christian Welzel: I mirrored your site to our server... it has a 100mbit connection :) but in exchange i removed the previous 3.0.1 mirror from geniussystems.net, that was there... the debline is: deb ftp://wh9.tu-dresden.de/kde3 ./ That's good. People just have to get it from there then. I guess I need a mirror that either is doing updates automatically somehow (which can be hard if I have a changing ip address), or to where I can upload the files when they change. I've just tried checking it out and got the following error: Err ftp://wh9.tu-dresden.de ./ libarts1 1.1.0.cvs20020926-1.2 403 Forbidden Also it seems really slow, are hundreds of people downloading at the same time or is the link between Dresden and Amsterdam slow? -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
Re: KDE 3.2-beta2
söndagen den 29 september 2002 14.51 skrev Paul Cupis: I don't know if apt will respect it, but the correct way of doing what you want would be for your cgi program to return a HTTP 302 code, telling the agent/client (apt in this case) to use a different IP/location/URI. If you use 302 as oppsed to 301, then the client (apt) will still go to the cgi program each time it is run, and not cache the new location/URI. The HTTP header should contain something similar to: HTTP/1.0 302 Found Location: http://a.b.c.d/~path/to/files If you post your code, I'm sure someone will help you modify it. That sounds like a much better way of doing that what I am doing. Should I just send that stuff back? This is my small cgi script with the name debian: #! /usr/local/bin/python import os, string, ip print Content-type: text/html print QUERY_STRING = os.environ[QUERY_STRING] PATH_INFO = os.environ[PATH_INFO] request_uri = os.environ[REQUEST_URI] where = string.index(request_uri, htbin/cgiwrap/pgd/) newurl = http://; + ip.ip + request_uri[where+17:] print htmlhead print 'meta http-equiv=refresh content=0; url=', newurl, '' print /html The file ip.py just contains whatever is my current ip at the moment: ip=217.208.212.10
Re: KDE 3.2-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 29 September 2002 14:10, Karolina Lindqvist wrote: That sounds like a much better way of doing that what I am doing. Should I just send that stuff back? Basically, yes. This is my small cgi script with the name debian: #! /usr/local/bin/python import os, string, ip print Content-type: text/html print QUERY_STRING = os.environ[QUERY_STRING] PATH_INFO = os.environ[PATH_INFO] request_uri = os.environ[REQUEST_URI] where = string.index(request_uri, htbin/cgiwrap/pgd/) newurl = http://; + ip.ip + request_uri[where+17:] print htmlhead print 'meta http-equiv=refresh content=0; url=', newurl, '' print /html The file ip.py just contains whatever is my current ip at the moment: ip=217.208.212.10 I don't know python, but the following should be what you want: #! /usr/local/bin/python import os, string, ip QUERY_STRING = os.environ[QUERY_STRING] PATH_INFO = os.environ[PATH_INFO] request_uri = os.environ[REQUEST_URI] where = string.index(request_uri, htbin/cgiwrap/pgd/) newuri = http://; + ip.ip + request_uri[where+17:] print 'HTTP/`1.0 302 Found' print 'Location: ', newuri' print Please exuse any errors in the code/syntax - I don't know python. Also, you will need to configure your webserver so that it does not create it's own HTTP header for this cgi program. Search the config file for nph, non-parsed-head, parse or similar and check the documentation. Basically, if your webserver manages to run the program okay, it will put a HTTP header on the output, but you want your program to give the HTTP header, not your server. Again, let us know what server you are running (and maybe post an except from it's config) and someone will try and help, I'm sure. Paul Cupis - -- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9lv+aIzuKV+SHX/kRArcWAJ40zPsamn73gJngjP1KDtqKBWACxwCfeAKn b8/ypeUWWWAgXddKUjYmP7I= =s2hw -END PGP SIGNATURE-
Re: AW: KDE 3.2-beta2
söndagen den 29 september 2002 15.01 skrev Flavio Tischhauser: If your dynamic IP ist the problem, why don't you just use one of the free dns services? I'm using dyndns.org for years now, and it works wonderful. (they have tons of different clients/scripts to automatically update your ip). Once you have a dns with your current ip, it shouldn't be a big problem to set up an automatical mirror. Thank you very much for that hint. I didn't know there was such fantastic free services. So my new home address is: http://shakti.ath.cx I just tried it, and it works like a charm with deb http://shakti.ath.cx/debian/kde3.1-beta2 ./ -- Karolina
Re: KDE 3.2-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 29 September 2002 14:26, Paul Cupis wrote: Second attempt: #! /usr/local/bin/python import os, string, ip QUERY_STRING = os.environ[QUERY_STRING] PATH_INFO = os.environ[PATH_INFO] protocol = os.environ[SERVER_PROTOCOL] request_uri = os.environ[REQUEST_URI] where = string.index(request_uri, htbin/cgiwrap/pgd/) newuri = http://; + ip.ip + request_uri[where+17:] print protocol, ' 302 Found' print 'Location: ', newuri' print And just make sure the file is called nph-foo.cgi (it should start with nph- for most servers to automatically set non-parsed-headers - no server config necessary?) Paul Cupis - -- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9lwQ0IzuKV+SHX/kRAksNAJ48blfB42o2TvLxYE/nnyBu3URarwCeLudy +sDYv/8gEvEXQfz5mJuYMNc= =mNi5 -END PGP SIGNATURE-
Re: KDE 3.2-beta2
Am Sonntag, 29. September 2002 15:10 schrieb Russell Coker: I've just tried checking it out and got the following error: Err ftp://wh9.tu-dresden.de ./ libarts1 1.1.0.cvs20020926-1.2 403 Forbidden Also it seems really slow, are hundreds of people downloading at the same time or is the link between Dresden and Amsterdam slow? These problems seem to be solved now... -- MfG, Christian Welzel (Sektionsvorsitzender und Admin AG DSN Gerokstrasse) GPG-Key: http://www.wh9.tu-dresden.de/~gawain/key.asc Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15
Re: KDE 3.2-beta2
On Sun, 29 Sep 2002 21:03, Karolina Lindqvist wrote: KDE 3.2-beta2 appears to never get announced. I guess it is delayed. (or have I missed the announcement somehow). Karolina, Thanks for the quick work. Your efforts are very much appreciated.. Mark
Re: AW: KDE 3.2-beta2
Karolina So my new home address is: http://shakti.ath.cx I just tried it, and it works like a charm with deb http://shakti.ath.cx/debian/kde3.1-beta2 ./ Thanks for all the efforts... I've just logged in to try this out and found the site with 'apt-get update'. Then I find that apt-get tells me that it needs to get 1 package after which 1819kb of archives. After unpacking 8129B will be freed. When I say Y to this a package called kdecarddecks 4:3.0.8.cvs20020927-1.1 is downloaded. I've stopped it at this point because I'm a bit worried that there may be something wrong with the upgrade. Anyone like to make any comments ? I'm a bit worried I might destroy my present KDE 3.0.3 installation which took a very long time to install. -- Thanks Richard
Re: KDE 3.2-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When I packed the KDE 3.1 beta1, I more or less took the version from CVS and compiled it. But now for KDE 3.2-beta2 I have put down much more work on packaging and it is branched off from the CVS version in a direction of its own. Hmm, just out of interest, what's the specific reason for having two separate branches of KDE 3.1 packaging? I just took a look at the sources and there do seem to be some non-trivial splits between your versions and the CVS versions that the maintainers are updating. I'm not hassling you here, I'm just curious. :) Ben. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] I've never felt anything that moves me as much as my piano. I'm an emotional player. I don't really like people. I prefer my piano to people. It's totally reliable and it's alive. I can hear what it's saying. For the most part, piano are female to me. Sometimes they're dykes, and they're always good fun. - Tori Amos, Mick St. Michael CD Booklet -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9l5soMQNuxza4YcERAr9eAKCOn2vMre1dflfII2AF1Sin31HyagCdEESY Xk/QfCylvj2hwvuUi7O7V5w= =3S7t -END PGP SIGNATURE-
Re: KDE 3.2-beta2
söndagen den 29 september 2002 15.46 skrev Paul Cupis: And just make sure the file is called nph-foo.cgi (it should start with nph- for most servers to automatically set non-parsed-headers - no server config necessary?) I tried it, and it appears that the nph- suffix is not enabled on that server. In any case, it works now with dyndns.org, so the problem of today is solved. -- Karolina
Re: KDE 3.2-beta2
Ben Burton wrote: When I packed the KDE 3.1 beta1, I more or less took the version from CVS and compiled it. But now for KDE 3.2-beta2 I have put down much more work on packaging and it is branched off from the CVS version in a direction of its own. Hmm, just out of interest, what's the specific reason for having two separate branches of KDE 3.1 packaging? I just took a look at the sources and there do seem to be some non-trivial splits between your versions and the CVS versions that the maintainers are updating. I second this. Karolina, could you make patches from your changes and send them to the list? Or if they are large (40KB gzipped), upload them somewhere and post address? Thanks. I build packages for Woody from cvs (they will hopefully end up on ftp.kde.org). It would be nice to combine our efforts. I am developing script to make *.install files more flexible (with respect to ever-changing file-lists in cvs). If you think you could make use of it (i mean adapt packaging to this), i'd be happy to help you (i don't have enough time to do it myself properly, so the script is rotting on my hard-drive atm). Thank you in advance. I'm not hassling you here, I'm just curious. :) Ben. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] I've never felt anything that moves me as much as my piano. I'm an emotional player. I don't really like people. I prefer my piano to people. It's totally reliable and it's alive. I can hear what it's saying. For the most part, piano are female to me. Sometimes they're dykes, and they're always good fun. - Tori Amos, Mick St. Michael CD Booklet -- --- inetname: Yenar Calentaure realname: Peter Rockai mail: yenar(at)host.sk homepage: http://yenar.host.sk --- The universe is entering maintenance mode in 2 minutes. Please logout. -- Your administrator ---
Re: KDE 3.2-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I build packages for Woody from cvs (they will hopefully end up on ftp.kde.org). It would be nice to combine our efforts. I am developing script to make *.install files more flexible (with respect to ever-changing file-lists in cvs). If you think you could make use of it (i mean adapt packaging to this), i'd be happy to help you (i don't have enough time to do it myself properly, so the script is rotting on my hard-drive atm). Hmm, so I'm a little worried about the scenario where we have the CVS debs using the maintainers' packaging (which for KDE 3.1 is not apt-gettable AFAIK but is presumably the branch that's headed for sid), Karolina's debs using her (somewhat different) packaging and then Yenar's woody debs using a hybrid of the two plus his own scripts... I guess I'm starting to get a little nervous about upgrade paths, propagation of packaging bugfixes (as opposed to differences in taste), that sort of thing. Anyway, FWIW. Maybe I just get nervous easily. :) b. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] The Honorable Member has been in so many parties he is a complete political harlot. - Paul Keating, on Independant Steele Hall -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9l6hJMQNuxza4YcERArk6AJ44nT7abggOUU549DUDycHDWzJVDwCcCMzt 9AYGy/LlilzQfynZB6em+/8= =SLol -END PGP SIGNATURE-
Re: KDE 3.2-beta2
Ben Burton wrote: I build packages for Woody from cvs (they will hopefully end up on ftp.kde.org). It would be nice to combine our efforts. I am developing script to make *.install files more flexible (with respect to ever-changing file-lists in cvs). If you think you could make use of it (i mean adapt packaging to this), i'd be happy to help you (i don't have enough time to do it myself properly, so the script is rotting on my hard-drive atm). Hmm, so I'm a little worried about the scenario where we have the CVS debs using the maintainers' packaging (which for KDE 3.1 is not apt-gettable AFAIK but is presumably the branch that's headed for sid), Karolina's debs using her (somewhat different) packaging and then Yenar's woody debs using a hybrid of the two plus his own scripts... Eee, no. If i do something to packaging, i send patches so they can be integrated to cvs. I only change build-depends from my build-scripts to automake1.5 and libpng2-dev (no automake1.6 in woody and imlib-dev conflicts with libpng3-dev...). If the perl hack i wrote is going to be used, it will be all-or-nothing. I mean it will be used in cvs or not at all. Is it better this way? The purpose of the hack is to ease building of snapshot packages, as the file-lists are aging too fast to be comfortable. Let me reiterate: if someone is going to make use of it, i'm fine with it. I won't build modified debs with them and pollute already-problematic debian/kde packaging space :). I guess I'm starting to get a little nervous about upgrade paths, propagation of packaging bugfixes (as opposed to differences in taste), that sort of thing Anyway, FWIW. Maybe I just get nervous easily. :) Take it easy :). b. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] The Honorable Member has been in so many parties he is a complete political harlot. - Paul Keating, on Independant Steele Hall -- --- inetname: Yenar Calentaure realname: Peter Rockai mail: yenar(at)host.sk homepage: http://yenar.host.sk --- The universe is entering maintenance mode in 2 minutes. Please logout. -- Your administrator ---
Re: KDE 3.2-beta2
Hi, I just used Chrisitian's URI to upgrade from kde2.2 to the 3.1-b2 packages. Absolutely fabulous work! thanks a lot.. I had been trying to compile it from source earlier, but this is definitely faster :) Though, I had to chmod +x /etc/kde3/debian/startkde script to make the kdm launch kde3, otherwise it was leaving a single ffailsafe session window... Is that expected? Once again, thanks for sharing ur packages.. -nikhil. Christian Welzel wrote: Am Sonntag, 29. September 2002 13:03 schrieb Karolina Lindqvist: As usual, my machine has a dynamic IP-address (don't save the numeric address), and has a slow ADSL connection that appears to be able to deliver only something like 800kbps, so it can be slow. I mirrored your site to our server... it has a 100mbit connection :) but in exchange i removed the previous 3.0.1 mirror from geniussystems.net, that was there... the debline is: deb ftp://wh9.tu-dresden.de/kde3 ./ -- Karolina -- -- Nikhil Goel [EMAIL PROTECTED] http://grok.hn.org/ -- A holding company is a thing where you hand an accomplice the goods while the policeman searches you. --
Re: KDE 3.2-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hmm, so I'm a little worried about the scenario where... Okay, so I should have made this clearer - I'm referring to a hypothetical scenario that I wish to avoid, not necessarily the scenario as it is now. :) Eee, no. If i do something to packaging, i send patches so they can be integrated to cvs. Okay, cool. The purpose of the hack is to ease building of snapshot packages, as the file-lists are aging too fast to be comfortable. Let me reiterate: if someone is going to make use of it, i'm fine with it. I won't build modified debs with them and pollute already-problematic debian/kde packaging space :). Yep, cool again. What I'm particularly worried about is distributed debs that lots of users are downloading. Take it easy :). *grin*.. part of my worry is what I suspect will happen when KDE3 enters sid, which is that bug reports will start coming in that we'll have to deal with due to broken upgrade paths resulting from various unusual combinations of the ever-proliferating repositories of kde3 debs. :) Ben. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] When you come to my shows, you think you're walking into this really yummy lunch, and little do you know you ARE lunch. - Tori Amos -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9l7ExMQNuxza4YcERAjADAJ4znA45PVivi4vA41Xdtn7QzUAAPQCeJnl1 B17MmcheEHzC9px8nP0mziI= =wMYg -END PGP SIGNATURE-
Re: KDE 3.2-beta2
On Sunday 29 September 2002 09:26 pm, Ben Burton wrote: Hmm, so I'm a little worried about the scenario where we have the CVS debs using the maintainers' packaging (which for KDE 3.1 is not apt-gettable AFAIK but is presumably the branch that's headed for sid), Karolina's debs using her (somewhat different) packaging and then Yenar's woody debs using a hybrid of the two plus his own scripts... I guess I'm starting to get a little nervous about upgrade paths, propagation of packaging bugfixes (as opposed to differences in taste), that sort of thing. Anyway, FWIW. Maybe I just get nervous easily. :) b. No you are nervous for very good reason. What is the point of providing packages to end users (that's the goal right? i mean the people making the packages are all happy compiling from cvs so...) if the end users are so confused by the multitude of incompatible debian kde 3.x packages. The situation as it stands is very nearly FUBAR. I mean we almost have every combination of possible packaging scheme with everyone going there own direction. I mean choice is good and all, but this is ridiculous. Look at what the end users have to deal with: ( ( ( unstable -- testing -- stable ) || ( gcc 2.95 -- gcc 3.2 ) || ( KDE 3.0.X -- KDE 3.1* ) ) third party packages of everything else ) so that's 12 different incompatible packaging schemes with only one having a long term upgrade future. Add the third party packages into the mix and you have an end user nightmare! So, now that I've described the problem I'll try and offer a solution ;) Why don't we secure a common web space (surely kde or debian has some space for us) and package kde3.1beta2 (the latest release) with gcc 3.2 (the latest compiler) and target sid (the unstable branch where all KDE 3.X should go.) AFAIK, this is precisely what Calc et al are doing. Perhaps some transparency and better communication would be in order. I am glad Karolina has the time and talent to package KDE 3.1. It would appear that we are not suffering from a lack of volunteers on this, rather we are suffering from a lack of clear leadership and communication. So the clear steps would be: 1. Everyone agrees to the plan 2. An eager volunteer secures web/ftp space (maybe we already have it and I don't know) 3. The leader of kde packaging either delegates or sets up the kde3.1beta source on the space secured. 4. The leader of kde packaging coordinates the efforts of all packagers into packaging kde3.1beta2 with gcc3.2 for sid and when a new release is made we should focus on that. In this way the unstable would always remain just that: unstable Anyhow, that's my opinion :) Adam
Re: KDE 3.2-beta2
Well, I am writing now from Gnome, because of: 1. installing was little buggy, but I came through it 2. after logging into kde3.1 there were several error messages like: Cannot find application/octet stream and MIME types are not installed and there is nothing in my menu and on the desktop. Can you give me an advice what to do? Thanks Vlada On Sun, 2002-09-29 at 16:39, Karolina Lindqvist wrote: sndagen den 29 september 2002 15.46 skrev Paul Cupis: And just make sure the file is called nph-foo.cgi (it should start with nph- for most servers to automatically set non-parsed-headers - no server config necessary?) I tried it, and it appears that the nph- suffix is not enabled on that server. In any case, it works now with dyndns.org, so the problem of today is solved. -- Karolina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Ing. Vladimir M. Kerka Klukovicka 1530 155 00 Praha 5 - Stodulky Czech Republic e-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] web:www.dinmont.cz NOTE: rm -rf /bin/ladin Nedostavam a nerozesilam viry, protoze nepouzivam M$ Windows
Re: KDE 3.2-beta2
On Sun, Sep 29, 2002 at 01:03:41PM +0200, Karolina Lindqvist wrote: Testing of everything might take forever, since I am only one person, so whoever want to try, the whole thing is available. I will fix problems when they are reported, if it is something within my powers and I can figure out how to fix it. Hi Karolina, I've tried your debs. Great work! Some issues: * if you have an old .kde/ lying around, some apps crash. Is this supposed to work or should users start again with a new .kde/ dir? * some needed libs (libkhtml.la, libartsbuilder.la, ...) which are needed for konqueror/arts are in the -dev packages only. If they are needed at runtime, why are they in -dev? * kcontrol does not work at all - DCOP communication error. kcmshell some_module works fine. How to debug? * startup splash screen: is there supposed to be some text below the image? if so, it is unreadable (everything is white). * kdm has a Swedish welcome message (well had one in your previous debs, didnt recheck) and always reverts back to auto-focus the pgd user. might be fixed already. That's it for now. -Malte #8-)
Re: KDE 3.2-beta2
On Sun, 29 Sep 2002 18:59, Malte Cornils wrote: * if you have an old .kde/ lying around, some apps crash. Is this supposed to work or should users start again with a new .kde/ dir? This is an ongoing issue with KDE. I've had similar problems on many occasions over the years. Error handling for config files really needs to be improved. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
Re: KDE 3.2-beta2
söndagen den 29 september 2002 18.59 skrev Malte Cornils: * if you have an old .kde/ lying around, some apps crash. Is this supposed to work or should users start again with a new .kde/ dir? Thats with KDE. I think it is a bad thing, but * some needed libs (libkhtml.la, libartsbuilder.la, ...) which are needed for konqueror/arts are in the -dev packages only. If they are needed at runtime, why are they in -dev? I don't know how to figure out exactly which libraries need the .la files present and which need not. It is a little bit trial and error for me right now. Some libraries that have a numeric .so-version are also loaded separately. Those are the ones I have a hard time to catch. * kcontrol does not work at all - DCOP communication error. kcmshell some_module works fine. How to debug? This might also be that some essential file by mistake is in a package that you have not installed. Whenever I figure out which file, I put it right. In general I find missing files very hard to debug with KDE, since it often does not give any intelligable error message. * startup splash screen: is there supposed to be some text below the image? if so, it is unreadable (everything is white). Probably the same thing. * kdm has a Swedish welcome message (well had one in your previous debs, didnt recheck) and always reverts back to auto-focus the pgd user. might be fixed already. This is really strange, since I have not entered anything Swedish into the build directories. I don't even use kdm. I have to check it out nearer. Anything is possible. -- Karolina
CVS: KDE 3.2-beta2
Hello, i installed cvs dep package :-) How can i download now KDE from CVS-Server. What must i do ? I compiled 3.07 from ftp-download :-) Thanks DAniel
obsolete: Re: CVS: KDE 3.2-beta2
On Sunday 29 September 2002 21:30, Daniel Mehrmann wrote: Hello, i installed cvs dep package :-) How can i download now KDE from CVS-Server. What must i do ? I compiled 3.07 from ftp-download :-) Thanks DAniel Hi :-) I found the KDE webpage :-) I`m downloading :-) bye DAniel
Re: KDE 3.2-beta2
On Sun, Sep 29, 2002 at 07:32:45PM +0200, Karolina Lindqvist wrote: söndagen den 29 september 2002 18.59 skrev Malte Cornils: * if you have an old .kde/ lying around, some apps crash. Is this supposed to work or should users start again with a new .kde/ dir? Thats with KDE. I think it is a bad thing, but The question is whether one should report those bugs in detail or not. Though I dont have too much time for those little details ATM anyway :-) * some needed libs (libkhtml.la, libartsbuilder.la, ...) which are needed for konqueror/arts are in the -dev packages only. If they are needed at runtime, why are they in -dev? I don't know how to figure out exactly which libraries need the .la files present and which need not. It is a little bit trial and error for me right now. Some libraries that have a numeric .so-version are also loaded separately. Those are the ones I have a hard time to catch. Another one is libartsmidi.la. I have now installed all the -dev packages though, so I probably wont find any more of those :-) * kcontrol does not work at all - DCOP communication error. kcmshell some_module works fine. How to debug? This might also be that some essential file by mistake is in a package that you have not installed. Whenever I figure out which file, I put it right. In general I find missing files very hard to debug with KDE, since it often does not give any intelligable error message. no, it rather seems to be bug no 46783 (upstream). However, I do have the latest Qt from unstable, so this bug would bite all Debian users. Does anyone have Qt3.1beta packages or more details on what would be required to fix this? * startup splash screen: is there supposed to be some text below the image? if so, it is unreadable (everything is white). Probably the same thing. well. Is there text on yours then? I could not find any ksplash bug for this though :-) This is really strange, since I have not entered anything Swedish into the build directories. I don't even use kdm. I have to check it out nearer. Anything is possible. mmh, if nobody else reports this, it was probably the old kdmrc I kept from your first packages (beta1) - this means the problem is fixed now. -Malte #8-)
Re: KDE 3.2-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 BEGIN FORM LETTER Yes, yes, I *know* we don't support these packages, etc etc etc, but that doesn't mean it's not worth coordinating to avoid these problems where possible. There's also the selfish motivation that whilst at the moment we get posts to the list which anyone can deal with or ignore as they please, when it starts going through the BTS it becomes my personal responsibility (for the modules I maintain), and though I agree we don't support this that whatever, I don't particularly like just slamming the door on people. So I'm keen to see as few problems as possible arise in the first place. :) And when you reiterate that it's fine to politely redirect them to debian-kde or whatever and close the bugs, I'll reiterate the first paragraph above. :) b. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] The man who sees both sides of a question is a man who sees absolutely nothing at all. - Oscar Wilde -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9mBQGMQNuxza4YcERAgOTAJ9bVbdE90zMZHftHQuZBpKCO9GjfQCeIqTw zZrDShvEv/0RewS0cvDQ2sU= =ZCIQ -END PGP SIGNATURE-
RE: 178 days and counting
ooo nasty - go fuck yourself -Original Message- From: Russell Coker To: David Pastern Cc: debian-kde@lists.debian.org Sent: 29/09/2002 19:18 Subject: Re: 178 days and counting On Sun, 29 Sep 2002 01:34, David Pastern wrote: eh? Thanks, but no thanks. I'm running on a Class C internal network where I live, with a direct backend into the ms exchange server (yes the gentleman where I live runs his own ISP, Microsoft based without a single touch of linux as he thinks it's a pile of shit and a fad - oh and he does have 20 years or so of experience in the IT industry). Therefore I do not Many people have 10 or more years IT experience where it's just the same year repeated many times, I fear that your husband(*) might be one of them. have a pop3 or imap account to set up mutt, evolution etc. At the moment Apparently Exchange does support POP and IMAP, but the administrator has to install it (it's not usually part of the default install). Unfortunately most Exchange admins aren't capable of anything other than a default install... (*) I use the term husband in a colloquial form, gay marriages aren't legal in Australia. You and the gentleman you live with would have to visit Europe to actually get married. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.1-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Again I should add that I'm not trying to hassle you; you've done some wonderful work. My opinion is quite clear. Get it out in coordination with KDE 3.1 releases. Get it into unstable (or whatever), already beta-tested, when KDE 3.1 final is getting released. Though if your packages are significantly different from the packages that will move into sid, this beta-testing might or might not be of use; it'll be a good beta test of KDE but a less useful beta test of the debian packaging (which is what in particular this group should be trying to get right). I don't know. We can cooperate and make one branch. Well clearly the more critical places where the packages differ is with kdelibs/etc; these core packages are not my responsibility and I guess if there's coordination involved it'll need to be between you and calc. As for the modules I maintain that you've provided your debian/ for, there seem to be some good ideas, some design decisions that I disagree with, some removal of components to support non-KDE users (eg., xpms, HTML docs), some issues of purely personal taste and some changes that I already have in CVS in different forms (presumably made after you branched from CVS). If you mail me with a list of which of your changes you think are important to have in the final packages, we can see what we agree on. :) Though please take a look in CVS first as opposed to listing changes from the point at which you branched, since there have been some significant updates in CVS since then. Thanks - Ben. :) - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] Just because people don't know their myths and hardly read anymore, does it mean I'm cryptic or does it mean we're just very uneducated as far as our word paints. Our pallets are like four colors now. We're back to red, blue and what's the other one? See what I'm saying. I do feel sometimes that if it's not three-dimensional and so tangible that it can work back-to-back with Riki Lake and Jerry Springer then people think the writers aren't making sense. To me, the audience isn't making sense. I feel half the audience is working on a McDonald's mentality-and I have no problem with the french fries. They're all over my thighs. Left, right and center, they're there-you'll find them if we ever wind up in a coffin together. But I do feel like I'm encouraging college students to stretch. You all have a responsibility to understand your writers rather then rolling your eyes and concluding they're not making sense. Or maybe you're just a dingbat. - Tori Amos -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9mBlZMQNuxza4YcERAgWBAJwNnjxEsFULB7nLfa3Cc5G/WpkqUQCdEk3h VXRHMXUf1EbQlpcNExc6K9c= =nxS1 -END PGP SIGNATURE-
RE: 178 days and counting
Russell : further - this just proves that *some* debian users simply cannot read and comprehend. Read my *ucking posts idiot - you'll see I reference the guy and his wife and daughter. duh! Personally, i'm straight, but that shouldn't be any of your business. Your post was both offensive and discriminatory (yes I know some gay people, and I find anti gay comments vulgar and unneccessary). For those that will criticise me (note no z in criticise) for some of my previous posts as being offensive, fair enough - I wasn't discriminatory though. I lost my cool and vented my anger and frustration on you, and I shouldn't have. My apologies to those that I did offend (yes i've cooled down now). Dave -Original Message- From: David Pastern To: Russell Coker; David Pastern Cc: debian-kde@lists.debian.org Sent: 30/09/2002 9:21 Subject: RE: 178 days and counting ooo nasty - go fuck yourself -Original Message- From: Russell Coker To: David Pastern Cc: debian-kde@lists.debian.org Sent: 29/09/2002 19:18 Subject: Re: 178 days and counting On Sun, 29 Sep 2002 01:34, David Pastern wrote: eh? Thanks, but no thanks. I'm running on a Class C internal network where I live, with a direct backend into the ms exchange server (yes the gentleman where I live runs his own ISP, Microsoft based without a single touch of linux as he thinks it's a pile of shit and a fad - oh and he does have 20 years or so of experience in the IT industry). Therefore I do not Many people have 10 or more years IT experience where it's just the same year repeated many times, I fear that your husband(*) might be one of them. have a pop3 or imap account to set up mutt, evolution etc. At the moment Apparently Exchange does support POP and IMAP, but the administrator has to install it (it's not usually part of the default install). Unfortunately most Exchange admins aren't capable of anything other than a default install... (*) I use the term husband in a colloquial form, gay marriages aren't legal in Australia. You and the gentleman you live with would have to visit Europe to actually get married. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: 178 days and counting
mm well as I am stubborn [I hate losing, especially to a goddamn stupid machine] - i've reinstalled debian (to ensure that anything that *may* have been inadvertently broken was fixed) and i'm going to give kde another try. I've edited my sources.list file to show: deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-7 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-6 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-5 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-4 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-3 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-2 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-1 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb http://people.debian.org/~schoepf/kde3/woody ./ stable main deb http://ftp.au.debian.org/debian/ stable main deb-src http://ftp.au.debian.org/debian/ stable main deb http://non-us.debian.org/debian-non-US stable/non-US main deb-src http://non-us.debian.org/debian-non-US stable/non-US main deb http://security.debian.org/ stable/updates main I have no idea why the cd stuff is showing as unstable - I *did* download stable. I am 100% positive on this. Is this how it should be?? Anyways...after updating sources.list I run: apt-get update And it errors out, with this following error message: maxus:/etc/apt# apt-get update E: Malformed line 15 in source list /etc/apt/sources.list (Absolute dist) What have I done wrong? It looks fine to my eye (and reading a previous post from (I think it was) Thomas indicates that it just needs to be main. Dave PS I also tried: deb http://people.debian.org/~schoepf/kde3/woody ./ main and that didn't work either. -Original Message- From: Thomas Schoepf To: [EMAIL PROTECTED]; David Pastern Cc: debian-kde@lists.debian.org Sent: 27/09/2002 5:38 Subject: Re: 178 days and counting On Fri, Sep 27, 2002 at 01:36:16PM -0400, [EMAIL PROTECTED] wrote: deb http://people.debian.org/~schoepf/kde3/woody ./ It appears to be what I want. That looks like what I did, though, and there were still libraries that were required and only available from woody/unstable Use the deb source written above. The packages there will work with woody (=stable) without requiring any libs from testing or unstable. Bye Thomas -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: 178 days and counting
Ignore post - I just tried removing the stable main and it's working now. Dave -Original Message- From: David Pastern To: Thomas Schoepf; [EMAIL PROTECTED]; David Pastern Cc: debian-kde@lists.debian.org Sent: 30/09/2002 11:14 Subject: RE: 178 days and counting mm well as I am stubborn [I hate losing, especially to a goddamn stupid machine] - i've reinstalled debian (to ensure that anything that *may* have been inadvertently broken was fixed) and i'm going to give kde another try. I've edited my sources.list file to show: deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-7 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-6 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-5 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-4 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-3 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-2 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-1 (20020718)]/ unstable contrib main non-US/contrib non-US/main deb http://people.debian.org/~schoepf/kde3/woody ./ stable main deb http://ftp.au.debian.org/debian/ stable main deb-src http://ftp.au.debian.org/debian/ stable main deb http://non-us.debian.org/debian-non-US stable/non-US main deb-src http://non-us.debian.org/debian-non-US stable/non-US main deb http://security.debian.org/ stable/updates main I have no idea why the cd stuff is showing as unstable - I *did* download stable. I am 100% positive on this. Is this how it should be?? Anyways...after updating sources.list I run: apt-get update And it errors out, with this following error message: maxus:/etc/apt# apt-get update E: Malformed line 15 in source list /etc/apt/sources.list (Absolute dist) What have I done wrong? It looks fine to my eye (and reading a previous post from (I think it was) Thomas indicates that it just needs to be main. Dave PS I also tried: deb http://people.debian.org/~schoepf/kde3/woody ./ main and that didn't work either. -Original Message- From: Thomas Schoepf To: [EMAIL PROTECTED]; David Pastern Cc: debian-kde@lists.debian.org Sent: 27/09/2002 5:38 Subject: Re: 178 days and counting On Fri, Sep 27, 2002 at 01:36:16PM -0400, [EMAIL PROTECTED] wrote: deb http://people.debian.org/~schoepf/kde3/woody ./ It appears to be what I want. That looks like what I did, though, and there were still libraries that were required and only available from woody/unstable Use the deb source written above. The packages there will work with woody (=stable) without requiring any libs from testing or unstable. Bye Thomas -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: 178 days and counting
Well that was shortlived...this is the result of apt-get update: maxus:/home/maxus# apt-get update Hit http://people.debian.org ./ Packages Hit http://non-us.debian.org stable/non-US/main Packages Hit http://people.debian.org ./ Release Hit http://security.debian.org stable/updates/main Packages Hit http://non-us.debian.org stable/non-US/main Release Hit http://security.debian.org stable/updates/main Release Hit http://non-us.debian.org stable/non-US/main Sources Hit http://non-us.debian.org stable/non-US/main Release Hit http://ftp.au.debian.org stable/main Packages Hit http://ftp.au.debian.org stable/main Release Hit http://ftp.au.debian.org stable/main Sources Hit http://ftp.au.debian.org stable/main Release Reading Package Lists... Done Building Dependency Tree... Done maxus:/home/maxus# apt-get upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back ark karm kate kcalc kcharselect kchart kcoloredit kcron kdebase kdepasswd kdf kdict kdm kedit kfind kformula kfract kghostview khexedit kiconedit kit kivio kjots kmail knewsticker knode knotes koffice koffice-libs konqueror konsole kontour korganizer korn koshell kpackage kpaint kpresenter kruler kscreensaver ksirc ksnapshot kspread ksysv ktimer kugar kuser kview kword secpolicy 0 packages upgraded, 0 newly installed, 0 to remove and 50 not upgraded. SoI ran apt-get upgrade with the following messages: maxus:/home/maxus# apt-get upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back ark karm kate kcalc kcharselect kchart kcoloredit kcron kdebase kdepasswd kdf kdict kdm kedit kfind kformula kfract kghostview khexedit kiconedit kit kivio kjots kmail knewsticker knode knotes koffice koffice-libs konqueror konsole kontour korganizer korn koshell kpackage kpaint kpresenter kruler kscreensaver ksirc ksnapshot kspread ksysv ktimer kugar kuser kview kword secpolicy 0 packages upgraded, 0 newly installed, 0 to remove and 50 not upgraded. So I then tried apt-get dist-upgrade, which reading the man page for apt-get states: dist-upgrade dist-upgrade, in addition to performing the func#65533; tion of upgrade, also intelligently handles chang#65533; ing dependencies with new versions of packages; apt-get has a smart conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones if necessary. The /etc/apt/sources.list file contains a list of locations from which to retrieve desired package files. Now this is what is said by my Debian system when I run the apt-get dist-upgrade command: maxus:/home/maxus# apt-get dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages will be REMOVED: kab kde kdebase kdebase-audiolibs kdebase-doc kdebase-libs kdelibs3 kdelibs3-bin kdepim-libs kpm libarts libkdenetwork1 libkmid libkonq3 The following NEW packages will be installed: kaddressbook kalarmd kappfinder karbon kcontrol kdcop kdebase-bin kdebugdialog kdelibs-bin kdelibs-data kdelibs4 kdeprint kdesktop khelpcenter khotkeys kicker kioslave klipper kmenuedit konqueror-nsplugins kpager kpersonalizer ksmserver ksplash ksysguard ktip kwin kxkb libart-2.0-2 libarts1 libarts1-qt libasound2 libcupsys2 libkcal2 libkdenetwork2 libkgantt0 libkonq4 libqt3 libqt3-mt libsensors1 python2.2 49 packages upgraded, 41 newly installed, 14 to remove and 0 not upgraded. Need to get 45.6MB/51.5MB of archives. After unpacking 40.6MB will be used. Do you want to continue? [Y/n] I answered yes to this, and it asked me to provide cdrom disk 1, and at this point I got nervous. Why? Note that where it says the following packages will be REMOVED it says kdelibs3. Is that not for kde 3? Or is that also present for kde 2.2. Looking at the package lists on the Debian site, it does have a kdelibs3 for stable, so i'm wondering if all is ok, and I can provide the said cdrom and let it read it and do its work. After my previous troubles i'm just very nervous and hesitant and untrusting of it all. Dave -Original Message- From: David Pastern To: Thomas Schoepf; [EMAIL PROTECTED]; David Pastern Cc: debian-kde@lists.debian.org Sent: 30/09/2002 11:17 Subject: RE: 178 days and counting Ignore post - I just tried removing the stable main and it's working now. Dave -Original Message- From: David Pastern To: Thomas Schoepf; [EMAIL PROTECTED]; David Pastern Cc: debian-kde@lists.debian.org Sent: 30/09/2002 11:14 Subject: RE: 178 days and counting mm well as I am stubborn [I hate losing, especially to a goddamn stupid machine] - i've reinstalled debian (to ensure that anything that *may* have been
Re: 178 days and counting
David, Install Red Hat, Mandrake or SuSE - it's a lot less complicated and they properly support KDE 3. On Monday 30 September 2002 02:32, David Pastern wrote: Well that was shortlived...this is the result of apt-get update: maxus:/home/maxus# apt-get update Hit http://people.debian.org ./ Packages Hit http://non-us.debian.org stable/non-US/main Packages Hit http://people.debian.org ./ Release Hit http://security.debian.org stable/updates/main Packages Hit http://non-us.debian.org stable/non-US/main Release Hit http://security.debian.org stable/updates/main Release Hit http://non-us.debian.org stable/non-US/main Sources Hit http://non-us.debian.org stable/non-US/main Release Hit http://ftp.au.debian.org stable/main Packages Hit http://ftp.au.debian.org stable/main Release Hit http://ftp.au.debian.org stable/main Sources Hit http://ftp.au.debian.org stable/main Release Reading Package Lists... Done Building Dependency Tree... Done maxus:/home/maxus# apt-get upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back ark karm kate kcalc kcharselect kchart kcoloredit kcron kdebase kdepasswd kdf kdict kdm kedit kfind kformula kfract kghostview khexedit kiconedit kit kivio kjots kmail knewsticker knode knotes koffice koffice-libs konqueror konsole kontour korganizer korn koshell kpackage kpaint kpresenter kruler kscreensaver ksirc ksnapshot kspread ksysv ktimer kugar kuser kview kword secpolicy 0 packages upgraded, 0 newly installed, 0 to remove and 50 not upgraded. SoI ran apt-get upgrade with the following messages: maxus:/home/maxus# apt-get upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back ark karm kate kcalc kcharselect kchart kcoloredit kcron kdebase kdepasswd kdf kdict kdm kedit kfind kformula kfract kghostview khexedit kiconedit kit kivio kjots kmail knewsticker knode knotes koffice koffice-libs konqueror konsole kontour korganizer korn koshell kpackage kpaint kpresenter kruler kscreensaver ksirc ksnapshot kspread ksysv ktimer kugar kuser kview kword secpolicy 0 packages upgraded, 0 newly installed, 0 to remove and 50 not upgraded. So I then tried apt-get dist-upgrade, which reading the man page for apt-get states: dist-upgrade dist-upgrade, in addition to performing the func#65533; tion of upgrade, also intelligently handles chang#65533; ing dependencies with new versions of packages; apt-get has a smart conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones if necessary. The /etc/apt/sources.list file contains a list of locations from which to retrieve desired package files. Now this is what is said by my Debian system when I run the apt-get dist-upgrade command: maxus:/home/maxus# apt-get dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages will be REMOVED: kab kde kdebase kdebase-audiolibs kdebase-doc kdebase-libs kdelibs3 kdelibs3-bin kdepim-libs kpm libarts libkdenetwork1 libkmid libkonq3 The following NEW packages will be installed: kaddressbook kalarmd kappfinder karbon kcontrol kdcop kdebase-bin kdebugdialog kdelibs-bin kdelibs-data kdelibs4 kdeprint kdesktop khelpcenter khotkeys kicker kioslave klipper kmenuedit konqueror-nsplugins kpager kpersonalizer ksmserver ksplash ksysguard ktip kwin kxkb libart-2.0-2 libarts1 libarts1-qt libasound2 libcupsys2 libkcal2 libkdenetwork2 libkgantt0 libkonq4 libqt3 libqt3-mt libsensors1 python2.2 49 packages upgraded, 41 newly installed, 14 to remove and 0 not upgraded. Need to get 45.6MB/51.5MB of archives. After unpacking 40.6MB will be used. Do you want to continue? [Y/n] I answered yes to this, and it asked me to provide cdrom disk 1, and at this point I got nervous. Why? Note that where it says the following packages will be REMOVED it says kdelibs3. Is that not for kde 3? Or is that also present for kde 2.2. Looking at the package lists on the Debian site, it does have a kdelibs3 for stable, so i'm wondering if all is ok, and I can provide the said cdrom and let it read it and do its work. After my previous troubles i'm just very nervous and hesitant and untrusting of it all. Dave -Original Message- From: David Pastern To: Thomas Schoepf; [EMAIL PROTECTED]; David Pastern Cc: debian-kde@lists.debian.org Sent: 30/09/2002 11:17 Subject: RE: 178 days and counting Ignore post - I just tried removing the stable main and it's working now. Dave -Original Message- From: David Pastern To: Thomas Schoepf; [EMAIL PROTECTED]; David Pastern Cc: debian-kde@lists.debian.org
Re: KDE 3.2-beta2
BEGIN FORM LETTER Yes, yes, I *know* we don't support these packages, etc etc etc, but that doesn't mean it's not worth coordinating to avoid these problems where possible. Absolutely! As someone who is using outside debs, I have a vested interest in there being a clearly defined upgrade path. There's also the selfish motivation that whilst at the moment we get posts to the list which anyone can deal with or ignore as they please, when it starts going through the BTS it becomes my personal responsibility (for the modules I maintain), and though I agree we don't support this that whatever, I don't particularly like just slamming the door on people. So I'm keen to see as few problems as possible arise in the first place. :) See above! *However*, and this was the point of the form letter, the *vast* majority of upgrade bugs would be mitigated completely by following the instructions. Can you think of something* that *wouldn't* be fixed by removing all relevant KDE packages, installing from the One True Apt-Source, and (possibly) mv'ing your .kde? I can't. And when you reiterate that it's fine to politely redirect them to debian-kde or whatever and close the bugs, I'll reiterate the first paragraph above. :) I won't reiterate that, as it wasn't my suggestion B-) My suggestion is: coordinate on packaging as much as possible but don't sweat the small stuff. Or even the mildly large stuff. Between your efforts and my proposed form letter, most everybody should be well taken care of. I agree that having to come to debian-kde or #debian-kde shouldn't be necessary. I just don't think it would be, assuming people can read ;-) D.A.Bishop
Removal of KDE
Hi, I just stumbled with installing KDE 3.1. Just inserting the apt.sources line and running apt-get dist-upgrade was way too brutal for apt to handle. While clearing up all the mess (I hadn't done a dist-upgrade for some time and apt downloaded more than 300 packages, also trying to upgrade my KDE 3.0.3 version.) I deinstalled all my KDE packages by typing apt-get remove kdelibs, getting a looong list of unmet dependancies and building a long apt-get remove line. Then I installed kde-3.1 and it worked. But removing those packages was really a pain... 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. (This should be at least loosely related to debian-kde as it is for removing KDE.) -- - Thomas Ritter
RE: 178 days and counting
Malcolm, I would prefer not to. Others are shoving it down my throat that i'm a dumbass microsoft user who'd be better off with Redhat et al. Others are also shoving it down my throat that it's me that's stuffing it up at my end, and that that is why it is not working. Others are saying that they all got it to work without any issues, so therefore it must be me that's at fault. And i'm sick of those implications. If others can get it to work, then why can I not also do the same? As far as I can see, i'm not doing anything wrong with the way I have things setup. OK I admit that i'm new to Debian linux. But I'm not totally new to Linux in general. Anyways, I went ahead and accepted it as y and it did some stuff. It then connect to the http://people.debian.org/~schoepf/kde3/woody ./ site. It started d/l packages and it was like yay, finally. I went and made a cuppa and came back to find this: 0.3-1woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kugar_1.2.0-1woody1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kspread_1.2.0-1woody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kpresenter_1.2.0-1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/koshell_1.2.0-1woody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kivio_1.2.0-1woody1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kontour_1.2.0-1woody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kformula_1.2.0-1woody 1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kchart_1.2.0-1woody1_ i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/koffice-libs_1.2.0-1w oody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kword_1.2.0-1woody1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/ktimer_3.0.3-1woody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdepim/knotes_3.0.3-1woody1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kjots_3.0.3-1woody1_ i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/khexedit_3.0.3-1wood y1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdebase/kfind_3.0.3-1woody1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kdf_3.0.3-1woody1_i3 86.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kdepasswd_3.0.3-1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kcharselect_3.0.3-1w oody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kcalc_3.0.3-1woody1_ i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdepim/karm_3.0.3-1woody1_i38 6.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/ark_3.0.3-1woody1_i3 86.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kedit_3. 0.3-1woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kruler_3.0.3-1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/ksnapshot_3.0.3-1 woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kfract_3.0.3-1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kiconedit_3.0.3-1 woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kpaint_3.0.3-1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kghostview_3.0.3- 1woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kcoloredit_3.0.3- 1woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kview_3.0.3-1wood y1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdebase/kdm_3.0.3-1woody1_i38 6.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdebase/kscreensaver_3.0.3-1w oody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdebase/konsole_3.0.3-1woody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdebase/kate_3.0.3-1woody1_i3 86.deb Size mismatch
Re: 178 days and counting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Your post was both offensive and discriminatory (yes I know some gay people, and I find anti gay comments vulgar and unneccessary). Hmm? How was Russell's post offensive, discriminatory or anti-gay? He was mistaken about your sexual orientation but that's about all I can see. Hell, that happens to me every day. On the other hand, as a gay person myself I must say I'm offended that you took offense to being mistaken for gay. :) *huggles* Ben, who finally caved in and joined the thread. :) - -- Ben Burton Debian Developer [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] The only thing to do with good advice is pass it on; it is never of any use to oneself. - Oscar Wilde -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9mEBgMQNuxza4YcERAkVBAKCeLI2gPj6IUK+ZI3f/dDgJWxTmaACfRdae 8BWYZ5KUWPahy9rEeJEqaEU= =JNMA -END PGP SIGNATURE-
RE: 178 days and counting
Interestingly reading this post on this online forum: http://www.linuxquestions.org/questions/history/27477 The first persons response to the post in question is named Mara. He/she says; Try to choose a different server for downloads. It seems the files on server are broken. I'm not sure if this is the case or not in my situation. Any light? Dave -Original Message- From: David Pastern To: Malcolm Hunter; [EMAIL PROTECTED]; David Pastern Cc: debian-kde@lists.debian.org Sent: 30/09/2002 12:05 Subject: RE: 178 days and counting Malcolm, I would prefer not to. Others are shoving it down my throat that i'm a dumbass microsoft user who'd be better off with Redhat et al. Others are also shoving it down my throat that it's me that's stuffing it up at my end, and that that is why it is not working. Others are saying that they all got it to work without any issues, so therefore it must be me that's at fault. And i'm sick of those implications. If others can get it to work, then why can I not also do the same? As far as I can see, i'm not doing anything wrong with the way I have things setup. OK I admit that i'm new to Debian linux. But I'm not totally new to Linux in general. Anyways, I went ahead and accepted it as y and it did some stuff. It then connect to the http://people.debian.org/~schoepf/kde3/woody ./ site. It started d/l packages and it was like yay, finally. I went and made a cuppa and came back to find this: 0.3-1woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kugar_1.2.0-1wood y1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kspread_1.2.0-1wo ody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kpresenter_1.2.0- 1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/koshell_1.2.0-1wo ody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kivio_1.2.0-1wood y1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kontour_1.2.0-1wo ody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kformula_1.2.0-1w oody 1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kchart_1.2.0-1woo dy1_ i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/koffice-libs_1.2. 0-1w oody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./koffice/kword_1.2.0-1wood y1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/ktimer_3.0.3-1wo ody1 _i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdepim/knotes_3.0.3-1wood y1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kjots_3.0.3-1woo dy1_ i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/khexedit_3.0.3-1 wood y1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdebase/kfind_3.0.3-1wood y1_i 386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kdf_3.0.3-1woody 1_i3 86.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kdepasswd_3.0.3- 1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kcharselect_3.0. 3-1w oody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kcalc_3.0.3-1woo dy1_ i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdepim/karm_3.0.3-1woody1 _i38 6.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/ark_3.0.3-1woody 1_i3 86.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdeutils/kedit_3. 0.3-1woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kruler_3.0.3- 1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/ksnapshot_3.0 .3-1 woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kfract_3.0.3- 1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kiconedit_3.0 .3-1 woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kpaint_3.0.3- 1woo dy1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kghostview_3. 0.3- 1woody1_i386.deb Size mismatch Failed to fetch http://people.debian.org/~schoepf/kde3/woody/./kdegraphics/kcoloredit_3. 0.3- 1woody1_i386.deb Size mismatch Failed to
Re: KDE 3.2-beta2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 See above! *However*, and this was the point of the form letter, the *vast* majority of upgrade bugs would be mitigated completely by following the instructions. Can you think of something* that *wouldn't* be fixed by removing all relevant KDE packages, installing from the One True Apt-Source, and (possibly) mv'ing your .kde? I can't. Sure, this is true but experience shows that not all people find these three steps easy to follow. :) I've had to hold bug submitters' hands through fairly routine procedures before. Anyway, your point is taken. I'll quite possibly forego the Personal Treatment for these cases and send them across to you^H^H^Hdebian-kde. ;-) b. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] A cynic is a man who knows the price of everything, and the value of nothing. - Oscar Wilde -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9mEHSMQNuxza4YcERAvNUAJ42TMYFboWcWwPpx8Fe257yghAZfwCgiTL5 wJBjkPzRfPha5PEo0jPWGxk= =i0ud -END PGP SIGNATURE-
Re: 178 days and counting
On Sunday 29 September 2002 07:17 pm, David Pastern wrote: Interestingly reading this post on this online forum: http://www.linuxquestions.org/questions/history/27477 The first persons response to the post in question is named Mara. He/she says; Try to choose a different server for downloads. It seems the files on server are broken. I'm not sure if this is the case or not in my situation. Any light? Dave *unplonk* Hi David Here are my current sources.list and preferences files. I just checked them before writing this mail, so they should work for you (fingers crossed...) /etc/apt/sources.list: deb http://http.us.debian.org/debian testing main contrib non-free deb http://non-us.debian.org/debian-non-US testing/non-US main contrib non-free deb http://http.us.debian.org/debian unstable main contrib non-free deb http://non-us.debian.org/debian-non-US unstable/non-US main contrib non-free deb http://ftp.du.se/pub/mirrors/kde/stable/3.0.3/Debian/ / /etc/apt/preferences: Package: * Pin: release a = testing Pin-Priority: 777 Package: * Pin: release a = unstable Pin-Priority: 333 Hope this gets you up and running. - Derek
Re: KDE 3.2-beta2
On Mon, 30 Sep 2002 03:50, [EMAIL PROTECTED] wrote: BEGIN FORM LETTER Yes, yes, I *know* we don't support these packages, etc etc etc, but that doesn't mean it's not worth coordinating to avoid these problems where possible. Absolutely! As someone who is using outside debs, I have a vested interest in there being a clearly defined upgrade path. Actually I think that Ben and the other people working on Debian KDE packages are the ones who have the greatest interest in a clearly defined upgrade path. If you use an outside deb and it breaks your system a bit on upgrade then you can just purge a few packages, rm a few configuration files, run dpkg --force-whatever on some installations and it'll work again. If you have only one machine to maintain (I suspect that most KDE administrators only manage a single work-station) and you are up with KDE (know how it works and don't mind getting into it) then this probably isn't a great hassle for you. I haven't reinstalled my Debian system since 1996 and it's been through much worse. ;) But the people who maintain the official debs will end up getting bug reports for packages they didn't create, and for bugs related to a broken upgrade (which can sometimes surface many months after the upgrade). Some of this KDE stuff makes me glad I'm packaging easy things instead. :-# -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
Re: Removal of KDE
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
