knode
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am using Knode from Sid ( actually all of KDE) on a Woody box. What I like to do is start an instance of knode as a differnt user, using the 'run as a different user' option by right clicking on the icon on my panel > preferences>execute. This works for Kmail but Knode fails to start. I don't know where to look for error messages or a possible difference in the config between these two apps. Help appreciated. - -- Greg Madden -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjw5GIYACgkQaefA3q8KcpDHjgCdFc4p17Yctc/4zyB8C+qKO/0h 4CgAoISPoiTqMA7KcOVyWiH7livOZppo =nhUc -END PGP SIGNATURE-
Re: KDE apps cannot display Chinese fonts
Anthony Fok wrote:
> On Fri, Jan 04, 2002 at 01:52:33PM +0800, scheme wrote:
>
>>I'm using unstable and found KDE 2.2.2 cannot display Chinese fonts if
>>anti-aliasing enabled.
>>
>
> Check your /etc/X11/XftConfig settings. Remove these:
>
> dir "/usr/X11R6/lib/X11/fonts/defoma/TrueType"
> dir "/usr/X11R6/lib/X11/fonts/defoma/CID"
Actually, in the file it's ".../fonts/{TrueType|CID}". I'd checked the settings
and thought OK. I was wrong.
>
> Add these:
>
> dir "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
> dir "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
Thanks, it works now. Probably this change should be done automatically in the
x-ttcidfond-conf package.
Re: The png fiasco, libqt2, and GNOME
On Mon, Jan 07, 2002 at 11:54:30AM +1100, Daniel Stone wrote:
> > I don't understand why you say that.
> Let me clarify. This is not something that can be done *cleanly* with
> bugs, nor something that I have any desire to do with bugs.
Bugs aren't a mechanism, they're a communications tool. If something's
not working correctly (and right now things *aren't* working correctly),
there's a bug, and it should be documented. That's all there is to it.
Generally, you can rely on testing to just get this right if you follow
that rule, and you're better off not trying to second guess it.
> > > Bug AJ to do it. It is not a bug in libqt2, and it is most certainly not
> > > critical.
> > I would suggest that the consensus opinion of the last week is that
> > the partial upgrade breakage for the libqt & KDE packages was a problem.
> > I am only concerned about avoiding the same problem occurring when
> > the packages trickle into TESTING, one by one.
The real problem is that partial upgrades are a supported feature of
Debian: if you update libqt but don't update some old .debs (from a few
months ago in testing, from RevKrusty's external potato KDE archives,
whatever) and stuff doesn't work, that's a serious bug. These things
have to be fully expressed with dependencies.
> So let them trickle in over a couple of days; what's the harm? There's
> no bug in any of the packages;
You may not think it's your fault, but if the packages don't work there's
definitely a bug. From what I've seen described there are only three ways of
fixing it:
* revert qt and everything that's rebuilt to libpng2, and worry
about it later
* change libpng3 so that it works with libpng2
[providing a libpng2 compatability lib may work, here]
* acknowledge that qt-based-on-png2 and qt-based-on-png3 aren't
fully compatible and change qt's .so-name, and change the name of
the package it's in
Ignoring the problem ("Oh, everyone just recompile, and we'll pretend
nothing happened, and not worry about users whose systems break when they
`apt-get install' something") is an option, but it's not a good one.
> at most an important-severity to rebuild
> with libpng3 (all of mine are currently being rebuilt and uploaded), so
> I don't see why you want to inflate severities.
Policy requires packages to accurately specify their dependencies with
a Depends: line; packages that used to Depend: on libqt, libpng2 are now
broken because libqt's interface changed. That's a bunch of serious bugs,
one way or another. It's not inflated at all.
Cheers,
aj
--
Anthony Towns <[EMAIL PROTECTED]>
Re: The png fiasco, libqt2, and GNOME
On Sun, Jan 06, 2002 at 12:43:05PM -0500, Steve M. Robbins wrote: > On Sun, Jan 06, 2002 at 10:46:52PM +1100, Daniel Stone wrote: > > > This is not something that can be done with bugs, > > I don't understand why you say that. Let me clarify. This is not something that can be done *cleanly* with bugs, nor something that I have any desire to do with bugs. > > Bug AJ to do it. It is not a bug in libqt2, and it is most certainly not > > critical. > > I would suggest that the consensus opinion of the last week is that > the partial upgrade breakage for the libqt & KDE packages was a problem. > I am only concerned about avoiding the same problem occurring when > the packages trickle into TESTING, one by one. > > If we let the updated libqt2 into TESTING without simultaneously > updating *all* the packages that use it and libpng, then TESTING > becomes unreleasable. That is a problem, no? > > I don't care how this problem is avoided. I am only concerned that > if nothing is done within a day or two, then libqt2 *will* go into > testing. To my mind, putting an RC bug on libqt2 is the easiest option. > If you feel otherwise, I'll leave you to fight it out with AJT. So let them trickle in over a couple of days; what's the harm? There's no bug in any of the packages; at most an important-severity to rebuild with libpng3 (all of mine are currently being rebuilt and uploaded), so I don't see why you want to inflate severities. -- Daniel Stone<[EMAIL PROTECTED]> i am going to start kernel hacking tonight * XFire gets out his peril sensitive sunglasses * XFire sets them to "Extra-Dark" XFire: peril sensitive sunglasses = /ignore dopey: that, and turning off my mobile phone.
Re: subject? no subject
On Sunday 06 January 2002 12:09 pm, Florian Struck wrote: > On Sunday 06 January 2002 20:19, you wrote: > > Messag > > e-Id: <[EMAIL PROTECTED]> > > Content-Transfer-Encoding: 8bit > > Resent-Message-ID: <[EMAIL PROTECTED]> > > Resent-From: debian-kde@lists.debian.org > > X-Mailing-List: archive/latest/6205 > > X-Loop: debian- > > [EMAIL PROTECTED] > > > Precedence: list > > Resent-Sender: [EMAIL PROTECTED] > > > > On Sunday 06 January 2002 09:01 am, Florian Struck wrote: > > > Re > > > sent-From: debian-kde@lists.debian.org > > > X-Mailing-List: archive/latest/6200 > > > X-Loop: debian-kde@lists.debian.org > > > Precedence: list > > > Resent-Sender: [EMAIL PROTECTED] > > > > > > Hi its weird on most messages i see the subject using kmail but in some > > > mails it says "no subject" even though i can see the subject in the > > > header does anyone experience this too? > > > > Greeting Florian: > > > > Yes. I am running pure Woody here and there was breakage I think in late > > November. Some of it was resolved, and some wasn't, like the kmail > > issues. If you run pure Woody too, you will also note that you can't > > attach messages without segfaulting kmail.. > > Howdy > True that attach thing is funny =/ running pure woody here too. > strange is that the broken subjects come only into my mandrake mailing > lists folder shhh dont tell anyone lol. > But whats a klient that i can use in the meantime ? Something that is > similar to kmail? > > > Hang in there, new code is always coming one bit at a time :) > > > > tatah Florian: I read kde-user, so it's not necessary to CC me. I don't use any of the other mailers like netscape, opera, or console like mutt etc. I have used linuxfreemail.com for any attachments. I like it since I can telnet into them and use pine :) Go figure. I can also access them via http with linuxfreemail.com webmail gui. Works nicely. I can also pop3 them, and they claim they will support imap soon. In fact, I have considered setting pine up here, it's very easy to use and so far, I have not used a man page once on it :) good luck -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
Re: subject? no subject
On Sunday 06 January 2002 20:19, you wrote: > Messag > e-Id: <[EMAIL PROTECTED]> > Content-Transfer-Encoding: 8bit > Resent-Message-ID: <[EMAIL PROTECTED]> > Resent-From: debian-kde@lists.debian.org > X-Mailing-List: archive/latest/6205 > X-Loop: debian-kde@lists.debian.org > Precedence: list > Resent-Sender: [EMAIL PROTECTED] > > On Sunday 06 January 2002 09:01 am, Florian Struck wrote: > > Re > > sent-From: debian-kde@lists.debian.org > > X-Mailing-List: archive/latest/6200 > > X-Loop: debian-kde@lists.debian.org > > Precedence: list > > Resent-Sender: [EMAIL PROTECTED] > > > > Hi its weird on most messages i see the subject using kmail but in some > > mails it says "no subject" even though i can see the subject in the > > header does anyone experience this too? > > Greeting Florian: > > Yes. I am running pure Woody here and there was breakage I think in late > November. Some of it was resolved, and some wasn't, like the kmail issues. > If you run pure Woody too, you will also note that you can't attach > messages without segfaulting kmail.. Howdy True that attach thing is funny =/ running pure woody here too. strange is that the broken subjects come only into my mandrake mailing lists folder shhh dont tell anyone lol. But whats a klient that i can use in the meantime ? Something that is similar to kmail? > > Hang in there, new code is always coming one bit at a time :) > > tatah
Re: The png fiasco, libqt2, and GNOME
On Sun, Jan 06, 2002 at 12:43:05PM -0500, steve wrote: > On Sun, Jan 06, 2002 at 10:46:52PM +1100, Daniel Stone wrote: > > > However, if the rebuilt libqt2 gets into testing before the rebuilt > > > KDE apps, then the latter will suddenly break for everyone using the > > > "testing" distribution. It seems prudent to hold up the migration to > > > testing until all the packages are ready to go. > > > > This is not something that can be done with bugs, > > I don't understand why you say that. It occurs to me now that you are probably thinking of moving the set of packages *into* testing once they are all rebuilt, whereas I was concentrating on keeping them *out* of testing. I think one can easily keep them out of testing with an RC bug. Initially, I thought it would suffice to wait ten days, then close the bug to get everything moved into testing: > > > Therefore, I'd like to reopen Bug #126808 on libqt2 and set its > > > severity to "critical". I believe that would keep the new libqt2 > > > (and everything that depends on it) out of testing. When all the > > > packages are ready, we would wait ten days (so that all the packages > > > become candidates for "testing"), then close the bug. Upon reflection, I see the flaw in this strategy: if one of the applications using libqt2 has its own RC bug, that application will not migrate, and will get broken when the updated libqt2 gets put into testing. Tough problem. I guess forcing things manually is one way around it, but it sounds more and more like AJ was right in suggesting that libqt2 ought to change SONAME. Still, I think it would be wise to keep libqt2 out of testing until this all gets worked out, one way or the other. -Steve -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants
Re: subject? no subject
>Hang in there, new code is always coming one bit at a time :) > That's why it costs me so much every time I do an apt-get dist-upgrade :) One bit at a time, over a 56K modem, with pay-per-minute phone charges, and the wife asking why I keep upgrading! I can't wait until ADSL finally arrives in Ireland Cheers, John Gay
Re: subject? no subject
On Sunday 06 January 2002 19:56, you wrote: > Op zondag 6 januari 2002 18:01, schreef Florian Struck: > > Hi its weird on most messages i see the subject using kmail but in some > > mails > > it says "no subject" even though i can see the subject in the header > > > does anyone experience this too? > > most likely corrupted index files. try to remove .*.index in your Mail/ > directory (while kmail ain't running, and then restart kmail, click on a > folder and on a mail), it worked for me. Not for me still the same =( > before you remove the indexes you also might want to pack all folders, > otherswise deleted mails show up again. I tried with a complete new kmail install after removing all files (kmailrc, Mail ...) after that i installed kmail again and hop still no subjects. Also i have a problem installing kdelibs-crypto it gives error when installing. > > greetings, > frank
Re: subject? no subject
On Sunday 06 January 2002 09:01 am, Florian Struck wrote: > Re > sent-From: debian-kde@lists.debian.org > X-Mailing-List: archive/latest/6200 > X-Loop: debian-kde@lists.debian.org > Precedence: list > Resent-Sender: [EMAIL PROTECTED] > > Hi its weird on most messages i see the subject using kmail but in some > mails it says "no subject" even though i can see the subject in the header > does anyone experience this too? Greeting Florian: Yes. I am running pure Woody here and there was breakage I think in late November. Some of it was resolved, and some wasn't, like the kmail issues. If you run pure Woody too, you will also note that you can't attach messages without segfaulting kmail.. Hang in there, new code is always coming one bit at a time :) tatah -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
Re: Work-needing packages report for Jan 4, 2002
On Fri, 4 Jan 2002 21:26, Ivan E. Moore II wrote: > I'd just like to say that the reason for my doing this has little to do > with any dd's or the arguments that went on on the debian-devel mailing > list. While that did have some part in my decision I did not let that make > my decision as that would just be a stupid thing to do (IMO). Things like > that are part of the job which is being a Debian Developer. I however just > don't have the time to do my job properly anymore. This has been a growing > trend for some time as those of you who have been following since the > beginning. Originally...crap almost 3 years ago...I was maintaining over > 100 KDE specific packages + QT on the side. And that was for multiple It should be noted here that KDE packages are more difficult to maintain than your average Debian package. KDE has huge amounts of dependencies, is complex enough that it's simply impossible to test any fraction of the functionality before a release, and takes hours to compile. You did a better job at this than I did... > So with all of that said after my blood pressure went through the roof the > other day I decided it was time that I just walk away. I'm not sure if > I'll volunteer for Debian as a Developer again. I'll probably still help There's always lots of small stuff you could do... -- 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/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
Re: subject? no subject
Op zondag 6 januari 2002 18:01, schreef Florian Struck: > Hi its weird on most messages i see the subject using kmail but in some > mails it says "no subject" even though i can see the subject in the header > does anyone experience this too? most likely corrupted index files. try to remove .*.index in your Mail/ directory (while kmail ain't running, and then restart kmail, click on a folder and on a mail), it worked for me. before you remove the indexes you also might want to pack all folders, otherswise deleted mails show up again. greetings, frank
Re: The png fiasco, libqt2, and GNOME
On Sun, Jan 06, 2002 at 10:46:52PM +1100, Daniel Stone wrote: > - Original Message - > From: "Steve M. Robbins" <[EMAIL PROTECTED]> > > The reason I'm writing here is that I would like to see the problem > > packages (libqt2 and related kde apps) stay out of TESTING until > > this issue is resolved. > > > > I gather that the way forward chosen for QT2/KDE is to recompile > > everything against libpng3. Chris Cheney and Daniel Stone: > > please confirm or correct this! > > Yes. Since we're already halfway there, going back would only cause more > confusion. > > However, if the rebuilt libqt2 gets into testing before the rebuilt > > KDE apps, then the latter will suddenly break for everyone using the > > "testing" distribution. It seems prudent to hold up the migration to > > testing until all the packages are ready to go. > > This is not something that can be done with bugs, I don't understand why you say that. The TESTING FAQ (http://people.debian.org/~jules/testingfaq.html) describes the rules for moving from UNSTABLE->TESTING: 3.What determines when a package moves into testing? A (particular version of a) package will move into testing when it satisfies all of the following criteria: 1.It must have been in unstable for 10, 5 or 2 days, depending on the urgency of the upload; 2.It must be compiled on (at least) every architecture which the corresponding version in testing was compiled on; 3.It must have fewer release-critical bugs than, or the same number as, the version currently in testing; 4.All of its dependencies must either be satisfiable by packages already in testing, or be satisfiable by the group of packages which are going to be installed at the same time; 5.The operation of installing the package into testing must not break any packages currently in testing. (See below for more information) Rule #3 implies that opening RC bugs on the package will keep it out. I can't find any trace of an RC bug being open for version -17 (the version in testing), so I presume that opening one single RC bug for -18 will keep it out of testing. > it's something that needs to manually be done by AJ. I suppose that AJ could do it manually. But I don't see why we ought to load him with even more busy work. Using the BTS appears to me to be the easier option. Moreover, it keeps the control with you, the maintainer, where it ought to be. > > Therefore, I'd like to reopen Bug #126808 on libqt2 and set its > > severity to "critical". I believe that would keep the new libqt2 > > (and everything that depends on it) out of testing. When all the > > packages are ready, we would wait ten days (so that all the packages > > become candidates for "testing"), then close the bug. > > Bug AJ to do it. It is not a bug in libqt2, and it is most certainly not > critical. I would suggest that the consensus opinion of the last week is that the partial upgrade breakage for the libqt & KDE packages was a problem. I am only concerned about avoiding the same problem occurring when the packages trickle into TESTING, one by one. If we let the updated libqt2 into TESTING without simultaneously updating *all* the packages that use it and libpng, then TESTING becomes unreleasable. That is a problem, no? I don't care how this problem is avoided. I am only concerned that if nothing is done within a day or two, then libqt2 *will* go into testing. To my mind, putting an RC bug on libqt2 is the easiest option. If you feel otherwise, I'll leave you to fight it out with AJT. Regards, -Steve -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants
test
test do not reply
subject? no subject
Hi its weird on most messages i see the subject using kmail but in some mails it says "no subject" even though i can see the subject in the header does anyone experience this too?
Re: Minimum-impact disabling of libpng2
On Fri, Jan 04, 2002 at 12:20:33PM -0800, Oliver Johns wrote: > But, if you do remove the package libpng2, then apt-get won't do > any further upgrades, due to the many packages depending on > libpng2. Correct, as i said i hoped this problem was solved much faster. > So, maybe a minimum-impact, short-term solution is to INSTALL > libpng2, and then rm or mv the file /usr/lib/libpng.so.2.1.0.12 > Then make the symlink as above > ln -sf /usr/lib/libpng.so.3.1.2.1 /usr/lib/libpng.so.2 Both kludges are very BAD [TM]. Most KDE stuff seems to work fine now except some software like quanta. To get 'em working correctly until everything libpng related is fixed start the programs from commandline like f.e. LD_PRELOAD=/usr/lib/libpng.so.3.1.2.1 quanta Bjoern
Re: Adopting these packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 04 January 2002 17:03, Daniel Stone wrote: > (BCC'ed to [EMAIL PROTECTED]). > > I will adopt the KDE packages, while Chris "calc" Cheney will take Qt, and > will also be the KDE3 maintainer when it comes around to it; by the time > KDE2.2 is phased out in favour of KDE3, I won't have the time to maintain > KDE, so it works out nicely. > > :) d > > Please CC all replies to me; the MX for the domain I get all list mail on > is down, so I'm reduced to reading lists through the archives. If you > don't, I reserve the right to have a long, flaming, thread about the fact. > Oh, and sorry about the line wrapping - LookOut! Express doesn't have it. > :\ Hi Daniel, I'm a KDE hacker. I would like to eventually adopt KDE3 packages. Could Chris please contact me? Unfortunately I'm not available until February, but if you have any problems I'd try to help. Thanks, - -- Eray Ozkural (exa) <[EMAIL PROTECTED]> Comp. Sci. Dept., Bilkent University, Ankara www: http://www.cs.bilkent.edu.tr/~erayo GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8NymzfAeuFodNU5wRArY1AJ99z5fT3cSDSg/+ONmtYqj6JnzDIQCdFrQX ws32zGnOqw/ynCBZwPYvoXQ= =yKYi -END PGP SIGNATURE-
Re: Work-needing packages report for Jan 4, 2002
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 04 January 2002 22:50, Kamil Kisiel wrote: > After reading this thread in full, I too understand Ivan's frustration with > the situation that has arisen.. > > Ivan has put a lot of effort n to packaging KDE on Debian, and I think that > many people (including myself) don't fully understand and respect the scope > of his work. Judging from the number of packages orphaned yesterday, it was > definitely no small task. > > While I have not talked to Ivan very much, the few conversations we had in > #debian-kde and on this mailing list were very friendly, and he was always > helpful. Myself and many others have really enjoyed the frequent updates to > the KDE packages in Sid and our sincerest thanks goes out to Ivan. I know > that I am not just speaking for myself when I say that we will be sorry to > see you go. Thank you for your hard work. > I think Kamil put this quite well. Ivan's contributed a lot of volunteer time for this task and it's not nice to see it turn this way. For one thing however, KDE developers are a bunch of very friendly coders (yes, we are, eheh) and I'll make sure we continue debian package maintenance within the KDE community. I fix build problems and contribute to debian packaging of a few proggies (kdevelop and I did the gideon packaging) occasionally besides coding. There are also several other KDE developers who are using debian systems for coding. If Ivan is still using KDE we could continue working on KDE CVS together. So that whoever the build guy is in debian, he can just wrap and go. What matters is that the stuff works for you people. Thanks, - -- Eray Ozkural (exa) <[EMAIL PROTECTED]> Comp. Sci. Dept., Bilkent University, Ankara www: http://www.cs.bilkent.edu.tr/~erayo GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8N5UkfAeuFodNU5wRAmaZAKCTB4I7Ky3kTOxL34pKpCswkHZ+VgCeJgi2 sdFH+R2Sra3akoJsjvUy65E= =0GsQ -END PGP SIGNATURE-
The png fiasco, libqt2, and GNOME
Hi, I was just perusing this list archive (I don't subscribe, so CC me if you want me to see any followup) and noticed a message from John Gay quoting me. I had said: By the way, "imlib1" is in the same boat as libqt2: I recompiled imlib using libpng3 and loads of GNOME binaries started failing to load icons. So this issue affects all of GNOME as well as KDE. >From this John concluded, "therefore, this is not Ivan's fault, as some debian maintainers seem to be saying." This latter comment belies misunderstanding of the issue and of the discussion on debian-devel. I don't think it is helpful to assign blame. I don't think anyone can question that Ivan generally did a great job with the KDE packages. You can read my take on the situation in this message: http://lists.debian.org/debian-devel/2002/debian-devel-200201/msg00243.html In that thread, three or four approaches have been mooted as a possible solution to the upgrade problem, but little discussion has emerged as yet. The reason I'm writing here is that I would like to see the problem packages (libqt2 and related kde apps) stay out of TESTING until this issue is resolved. I gather that the way forward chosen for QT2/KDE is to recompile everything against libpng3. Chris Cheney and Daniel Stone: please confirm or correct this! That is fine, although one should note Anthony Towns' remarks in http://lists.debian.org/debian-devel/2002/debian-devel-200201/msg00254.html http://lists.debian.org/debian-devel/2002/debian-devel-200201/msg00263.html However, if the rebuilt libqt2 gets into testing before the rebuilt KDE apps, then the latter will suddenly break for everyone using the "testing" distribution. It seems prudent to hold up the migration to testing until all the packages are ready to go. Therefore, I'd like to reopen Bug #126808 on libqt2 and set its severity to "critical". I believe that would keep the new libqt2 (and everything that depends on it) out of testing. When all the packages are ready, we would wait ten days (so that all the packages become candidates for "testing"), then close the bug. Comments? [Remember to CC me, please.] Regards, -Steve -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants
Re: Work-needing packages report for Jan 4, 2002
On Friday 04 January 2002 12:50, Kamil Kisiel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Friday 04 January 2002 02:27, Mariusz Przygodzki wrote: > > [- snip -] > > > Because some arrogant assholes (called debian maintaners officially) > > have flamed Ivan on debian-devel for his very hard volunteer work. The > > most interesting is that they think they did it on behalf of Debian > > KDE Users. > > > > I can only add I fully understand Ivan's decision after reading the > > whole thread about libpng package on debian-devel. > > After reading this thread in full, I too understand Ivan's frustration with > the situation that has arisen.. > > Ivan has put a lot of effort n to packaging KDE on Debian, and I think that > many people (including myself) don't fully understand and respect the scope > of his work. Judging from the number of packages orphaned yesterday, it was > definitely no small task. > > While I have not talked to Ivan very much, the few conversations we had in > #debian-kde and on this mailing list were very friendly, and he was always > helpful. Myself and many others have really enjoyed the frequent updates to > the KDE packages in Sid and our sincerest thanks goes out to Ivan. I know > that I am not just speaking for myself when I say that we will be sorry to > see you go. Thank you for your hard work. > 2nded except the conversations in #debian-kde. Thanks Ivan
Re: Work-needing packages report for Jan 4, 2002
El Vie 04 Ene 2002 21:26, Ivan E. Moore II escribió: > > > >Because some arrogant assholes (called debian maintaners officially) > >have flamed Ivan on debian-devel for his very hard volunteer work. The > >most interesting is that they think they did it on behalf of Debian > >KDE Users. > > > >I can only add I fully understand Ivan's decision after reading the > >whole thread about libpng package on debian-devel. > > I'd just like to say that the reason for my doing this has little to do > with any dd's or the arguments that went on on the debian-devel mailing > list. While that did have some part in my decision I did not let that make > my decision as that would just be a stupid thing to do (IMO). Things like > that are part of the job which is being a Debian Developer. I however just > don't have the time to do my job properly anymore. This has been a growing > trend for some time as those of you who have been following since the > beginning. Originally...crap almost 3 years ago...I was maintaining over > 100 KDE specific packages + QT on the side. And that was for multiple > arch's. One could say that I definatly had alot of free time back then. > Over the past few years I have found less and less free time. My job and > personal life has taken it's tole and of late I've had to make decisions > that would make sure that I could keep my job and be happy doing it as well > as be happy in my personal life. Spending all my weekend and evenings > doing Debian stuff just doesn't cut it and my stress level has gone through > the roof. I find myself getting angry easier and easier as the argument on > d-devel shows. It also doesn't help that I care about the work I do and > when I always see comments about how I don't fix problems fast enough, am > not doing a good job at all, am always an asshole, etc... it just grates > on my nerves. It doesn't matter how much praise one get's. I definatly > never deserved as much as I received as I constantly see other people who > do far more than I have ever done. > > So with all of that said after my blood pressure went through the roof the > other day I decided it was time that I just walk away. I'm not sure if > I'll volunteer for Debian as a Developer again. I'll probably still help > out from time to time in other capacities and may do some non-official > stuff on the side. But at this time I plan on removing (or rather already > have) myself from all mailing lists and removing all -dev crap off my > machine so I won't even be tempted. > > > and finally to help qwell some disputes I've read and some other crap I've > read: > > The PNG fiasco. It could partially and quickly be fixed by reverting > everything back to using libpng2 specifically. However by the time we > found the problem several large chunks of affected packages were aready > built with libpng3 and uploaded (qt/kdebase/kdelibs/kdemult/+others) and so > several felt it would be just better to move forward and just migrate to > libpng3. > > this brings up 1 other problem that was pointed out just recently. Any > packages built against libqt2 that is in stable may break if they also link > to libpng2. While the breakage is usually minor (depending on the app) it > is still a problem. > > there is 2 solutions to this problem...one is to revert back to libpng2 and > basically stick with libpng2 and just migrate to libpng3 for qt3/kde3. The > other solution is to see if something can be done to libpng3 for backwards > compatability. The maintainer of libpng3 is out until something like the > 10th so we won't know until sometime after then if this is possible unless > someone else jumps in and does the footwork. > > > The imlib bit will only be an issue is a new imlib is uploaded linked to > the new libpng3. > > AFAIK all of the QT/KDE packages have been adopted. Don't worry about KDE > not being in woody. Others have taken the packages and will do an > excellent job. > > Ivan hello Ivan Your attitude honours you and I think you deserve our gratitude. Serious work on free software (like yours) in most of the cases is done because of its own pleasure but one has to pay for it. And one pays with his job, his family, his friends and at the end his health. Many times it does not pay off. I want to thank you for providing us the possibilty to use KDE without abandoning Debian and for providing so many packages of the best quality for such a long period of time. I wish you the best, Pablo de Vicente.
Package dependency loop in unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just hit the following after an dselect update kpackage depends on rpm and librpm0 rpm depends on librpm4 librpm0 conflicts with librpm4 eek - -- Alan - [EMAIL PROTECTED] http://www.chandlerfamily.org.uk -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8ODxn1mf3M5ZDr2kRAgXyAJ9npt0Wk+SHxKsSEqIafSVozf5y3wCgmvM1 ZBsEw/xkbC340abIjmiIAxk= =V+IK -END PGP SIGNATURE-
Re: The png fiasco, libqt2, and GNOME
Excuse the LookOut! Express's crapping up of the message. Real mail client tomorrow, yeah! - Original Message - From: "Steve M. Robbins" <[EMAIL PROTECTED]> To: Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, January 06, 2002 11:38 AM Subject: The png fiasco, libqt2, and GNOME > In that thread, three or four approaches have been mooted as a possible > solution to the upgrade problem, but little discussion has emerged as > yet. > > > The reason I'm writing here is that I would like to see the problem > packages (libqt2 and related kde apps) stay out of TESTING until > this issue is resolved. > > I gather that the way forward chosen for QT2/KDE is to recompile > everything against libpng3. Chris Cheney and Daniel Stone: > please confirm or correct this! Yes. Since we're already halfway there, going back would only cause more confusion. Build-Dep on "libpng3, libpng3-dev || libpng-dev", and you're set. > That is fine, although one should note Anthony Towns' remarks in > > http://lists.debian.org/debian-devel/2002/debian-devel-200201/msg00254.html > http://lists.debian.org/debian-devel/2002/debian-devel-200201/msg00263.html > > However, if the rebuilt libqt2 gets into testing before the rebuilt > KDE apps, then the latter will suddenly break for everyone using the > "testing" distribution. It seems prudent to hold up the migration to > testing until all the packages are ready to go. This is not something that can be done with bugs, it's something that needs to manually be done by AJ. > Therefore, I'd like to reopen Bug #126808 on libqt2 and set its > severity to "critical". I believe that would keep the new libqt2 > (and everything that depends on it) out of testing. When all the > packages are ready, we would wait ten days (so that all the packages > become candidates for "testing"), then close the bug. Bug AJ to do it. It is not a bug in libqt2, and it is most certainly not critical. Users will live for the next couple of days. Unexpected shit can crop up and keep packages out of testing, you cannot rely on bugs to work testing. AJ, I'm also going to ask you to force newer KDE packages (calc has them to build and upload) into testing, as Ivan isn't going to maintain them at all, and I don't want to maintain the old ones. -d
kpackage and rpm
yeah, I've been aware of this for a couple of days; joeyh was kind enough to give me a heads-up. unfortunately i've been on holiday-ish for some time, so i haven't been able to dedicate as much attention as i would've liked to kde. oh well, a new kdeadmin should go up soon, with the new kpackage and shiny new deps. :) d
Re: KDE apps cannot display Chinese fonts
On Fri, Jan 04, 2002 at 01:52:33PM +0800, scheme wrote: > I'm using unstable and found KDE 2.2.2 cannot display Chinese fonts if > anti-aliasing enabled. Check your /etc/X11/XftConfig settings. Remove these: dir "/usr/X11R6/lib/X11/fonts/defoma/TrueType" dir "/usr/X11R6/lib/X11/fonts/defoma/CID" Add these: dir "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" dir "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID" The font paths used by defoma/x-ttcidfont-conf have changed. > That's not the case sometimes ago. Since I'm constantly dist-upgrade-ing > my system, I cannot remember exactly when that's broken. I just > uninstalled kde-i18n-zhcngb2312 and used English only. > > I searched the kde bug reports and learned that one can disable > anti-aliasing, but it's aweful to use KDE without anti-aliasing. > > I followed debian-chinese-faq closely, and it once worked. So the > problem cannot be solved by referring to the faq. > > Any helps are welcome! I guess one of us Debian developers should update the FAQ soon. I guess most of us are too busy to do so right now, but we will get to it before the official woody is released. -- Anthony Fok Tung-Ling ThizLinux Laboratory <[EMAIL PROTECTED]> http://www.thizlinux.com/ Debian Chinese Project <[EMAIL PROTECTED]> http://www.debian.org/intl/zh/ Come visit Our Lady of Victory Camp! http://www.olvc.ab.ca/
test - plz ignor
eof
libpng? What is the current status?
I haven't updated my system since this whole problem with libpng happened, so I'm still waiting to hear the current status. I must have picked up a bit of the problem, because kmail no longer has icons, but konq still works, unless I start it from the command line. So, my question is: If I do an apt-get dist-upgrade now, will I get the rest of my icons back? On the other hand, I'd like to know how debian-devel can say this is a kde-specific problem when Debian's beloved Gnome suffers identical problems without a complete re-compile and several dependancy changes as well? Cheers, John Gay
Minimum-impact disabling of libpng2
On Thursday 03 January 2002 06:40 am, Bjoern Krombholz wrote: >On Thu, Jan 03, 2002 at 01:50:03AM +0100, Laurent Rathle wrote: > > So I didn't remove libpng2 but I simply renamed > > the symlink libpng.so.2 in libpng.so.2.old and I made the > > symlink you mentionned (ln -s /usr/lib/libpng.so.3.1.2.1 > > /usr/lib/libpng.so.2). It works. > > Really? Run ldconfig, this should change the so.2 symlink back > to the real 2.1.0.12 library when libpng.so.2.x.x.x is found. > > > Bjoern But, if you do remove the package libpng2, then apt-get won't do any further upgrades, due to the many packages depending on libpng2. So, maybe a minimum-impact, short-term solution is to INSTALL libpng2, and then rm or mv the file /usr/lib/libpng.so.2.1.0.12 Then make the symlink as above ln -sf /usr/lib/libpng.so.3.1.2.1 /usr/lib/libpng.so.2 Now, I believe since it worked that way here, running ldconfig (as is done by many upgrade setups) will not mess things up. The downside, of course, is that anything linked against the removed library won't work, including quite a bit of gnome stuff. But that downside was already there with the changed symlink. This may work for those, like me, who use kde almost entirely. Maybe this mess will be cleaned up soon, but maybe not. It has seemingly provoked flames and the resignation of Ivan, our stellar maintainer. -- Oliver Johns <[EMAIL PROTECTED]> San Francisco, California USA GPG KeyID=A2ACE692 GPG Fingerprint=BE4A C1B8 EB0D 8FD9 737D CE4A 1E56 BF9B A2AC E692
