> Maybe you didn't install the konqueror package on Ubuntu but did so on SID?
In all cases, konqueror and khelpcenter (the KDE 4 versions) were installed.
Ben.
--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
Hi again,
On further digging, it looks like the ubuntu people have fixed the
khelpcenter problem by patching kdelibs directly. The patch is quite
small (in KApplication::invokeHelp(), start khelpcenter directly instead
of using dcop).
I'll file a bug for this against debian's kdelibs shortly.
Hi,
I have a KDE3 app that I maintain, whose help menu has a couple of items
that rely on helper programs:
(i) the usual Help -> Handbook menu entry tries to open the handbook in
the standard way using khelpcenter;
(ii) there is an extra Help -> API Reference menu entry that opens some
pre-inst
> I remember him wanting to give kile to the team. I'm not 100% sure
> it's the package he talked about. maybe someone could step up and ask ?
Yep, that was the one. :)
TIA for looking after it,
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
> Do a
>
> find /usr/share/doc -name copyright -exec grep -l "YOUR NAME" {} \;
>
> to find those packages on your system. (This might cause a few false
> positives, figlet for example is not affected :)
Hmm, I suspect this will find a very large number of false positives
since "YOUR NAME" sh
Hi all,
> #327977 contains interesting information now.
Luk Claes is doing an NMU this week that will at least make the old
koffice 1.3.x installable.
As for KOffice 1.4.x, I'm afraid the last month has been an order of
magnitude crazier than expected, and each block of time that I had set
as
(Resent since I messed up the To: line in my previous mail. This was
also posted to debian-qt-kde, so please send follow-ups to both lists.)
Hi all,
I've orphaned two packages today.
1) konq-speaker (text-to-speech for konqueror and kate);
2) qbble (search support for xmms playlist).
Both are
> I guess we (qt-kde team) could do it. and anybody interested in doing
> it too could join us (only having an alioth account is required) and
> maintain those inside our svn.
Works for me, ta.
b.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
Hi all,
Since my spare time is not what it used to be, I have put a few KDE apps
up for adoption this morning:
kdbg (#315336) -- graphical debugger interface
kprof (#315337) -- visual tool to help analyse profiling results
kbear (#315340) -- graphical ftp client for KDE
If anyone is willi
> patches are very welcome. pick your favourite kde app and write a nice
> description for it. could even work, if each user here would prepare
> one.
Even without humans writing additional descriptions, a start would to be
to reverse the order so you have (app-description kde-ad) instead o
Hi.
> I really belief that it would be better to include a bug fixed kde 3.2 than
> a buggy kde 3.3.
FWIW, I'm also in favour of including 3.2.3 rather than 3.3.0. Each new
3.x release seems to (understandably) begin with a number of annoyances
that are ironed out over the BRANCH releases, and
> However, the KDE modules doesn't change very quickly, and probably (it's just
> my opinion) the only change that will affect the kde metapackage after 3.3,
> will be changing quanta for kwebdev, and maybe adding kdebindings.
FWIW there is already a kdewebdev metapackage, so you can install th
> Thank you! It really is much appreciated.
And my apologies for the unwarranted CC. :)
b.
> I naïvely thought that an invalid from-address and the fact that I do not ask
> to receive CCs would stop people from doing it accidentally or go through the
> effort to do it deliberately, especially considering what
> http://www.debian.org/MailingLists/#codeofconduct tells you. Silly me.
O
[ snipped 7 lines of anger ]
Well if you're going to be that touchy about it then you might at least
consider setting an appropriate Mail-Followup-To. But then it's always
more fun to complain than to try to prevent the problem, isn't it?
b.
> As much as I like vi, I might have to agree with that. The inclusion of kvim
> and vimpart in popular meta packages could be questioned, at least if it is
> greedy about file associations.
FWIW, I have kvim and vimpart installed and they have never offered
themselves as defaults for anything.
> I did an strace this weekend and managed to locate the probable cause [1].
Much appreciated btw. :)
b.
> I have to tell konqueror to re-read kioslaverc. For this, I wanted to
> use dcop, but I couldn't find the correct function to call in kdcop -
> if there is one.
dcop konqueror- KonquerorIface reparseConfiguration
Does this do what you want?
b.
Hi.
> {Using Xandros/Debian and KDE 3.1.4]
>
> I am at my wits' end. I've tried everything and nothing works.
Since you're compiling your own koffice from source and installing it in
a separate prefix, you're possibly best asking on the koffice lists
(e.g., [EMAIL PROTECTED]).
I personally don
> The files are there, but I can't figure out how to active it?
Have you got kate-plugins 3.2.1 (not 3.1.5)? If so, it shows up for me
in Kate/Settings/Application/Plugins (where you can activate it).
b.
> Is fsview (kde 3.2) availble from unstable?
I've uploaded kdeaddons 3.2.1 to sid today (including konq-plugins), and
the fsview included works for me.
b.
> Is fsview (kde 3.2) availble from unstable? It seems to be part of the
> konq-plugins woody package but it is not in the unstable konq-plugins
> package.
I can't upload kdeaddons (which includes konq-plugins) until kdegames is
available.
Ben.
> After upgrading to 3.2, it seems the "Archive web page" feature is gone. Has
> it really been removed or can't I just find it?
It's part of konq-plugins, which I can't upload until kdegames is ready.
Ben.
Quite convenient having a Turkish boyfriend. :)
The question seems to be:
"I downloaded 3.0r2 iso files, and wrote it to CDs. KDE doesn't work. When I
checked MC and /usr/lib icluding libkdeui.so most files are red. As far as
I understood there is a problem with (dunno how to translate
> Also, where's plastik?
kdeartwork-theme-style, which was uploaded last night.
b.
Hi.
> I am using sid.
> Updated today to official kde 3.2.1 peackages in sid.
> Then I want to install kword an got this error.
KOffice is trying to install some files that it needs for KDE 3.1 (for
KDE 3.2 they were put into kdelibs).
The KDE 3.2 build for koffice is being upload now.
Ben.
> Does quanta just need to be recompiled for 3.2.1 or will I have to wait
> for Quanta 3.2 (which isn't ready yet, AFAIK)?
In all likelihood, quanta 3.2.1 will be uploaded today.
Ben.
> does anyone know what has happened to various KDE screensavers, e.g.
> kslidescreen? This is my favourite one.
> They can be found in the KDE 3.1.5 packages, but I can't find them in the new
> 3.2 packages anymore, I can't even find them in the KDE CVS.
AIUI, a number of screensavers were re
Hi. :)
> There have been some setbacks since the last status update. kdetoys had
> an rc bug, so a new version was uploaded and still needs to build on 4
> archs.
FWIW, this wasn't an RC bug (in fact the bug wasn't even in the debian
BTS). It was however a bug that had been annoying me, and
> My system time and time zone is correct in kde 3.1-5 Control Center. running
> knoppix/debian 3.3 2.4.22-xfs kernel, but my kicker panel shows a time 10
> hours ahead of what it should be, any ideas?
>
> AFAIK all my apps show the correct time as well, this appears to just be
> confined to
> There's a conflict between kdelibs-data and today's version of
> openoffice.org-mimelnk (1.1.0-6), they both provide
> /usr/share/mimelnk/application/vnd*.desktop
As a follow-up to that: what kdelibs should do (IMHO) is not ship the
files and instead recommend OOo-mimelink. KOffice used to
> My system time and time zone is correct in kde 3.1-5 Control Center. running
> knoppix/debian 3.3 2.4.22-xfs kernel, but my kicker panel shows a time 10
> hours ahead of what it should be, any ideas?
I don't suppose you're running kworldclock are you? It seems to do
screwy things to my kick
> A number of applications which depend on libqt3c102-mt --- including
> all of KOffice 1.3, kvim, k3b, (and for those using Libranet)
> adminmenu --- were all uninstalled. I am certain that a resolution is
> in the works. Does anyone know the timing?
The debs on the KDE servers are for woody.
> I would like know if the package of koffice 1.3 is in construction ?
It was uploaded about 12 hours ago, should appear on your mirror soon.
Ben.
> When I finished using Konstruct to compile KDE 3.2RC1, it ended with an error
> saying that the automake on my machine was version 1.7.9. It evidently
> requires automake 1.7.6 to correctly function.
>
> Where can I acquire and downgrade my automake to version 1.7.6?
I suspect the build is
Hi.
> I downloded Kbear from:
>
> deb ftp://ftp.de.debian.org/debian/ sarge main
Which versions of kbear and kdelibs4 (precise package version numbers)
do you have installed?
Thanks - Ben (kbear maintainer).
Hi.
> I tried to install KDE 3.1.4 and ran into a bad dependency problem between
> the KDE 3.1.4 packages and the existing libsdl-arts/libsdl-all packages. Can
> anyone suggest to whom I should send this big report to?
Regardless of where else it goes, you'll want to send a copy of this
report t
Hi.
> The KDE desktop needs too much time to start
> ...
> also some programes, (its explorer in
> windows, how is it called under linux? i dont remember ...) have slow
> startup (1 min)
FWIW, I had something like this appear a couple of days ago (though not
as long a delay as this) - I fixed
Hi.
> when I try to install Koffice again I get this message from synaptic:
>
> "The selected package couldn't be installed/upgraded.
If you're running sarge (testing) then yes, this is a temporary problem.
KOffice is waiting for the new glibc to enter testing before it can
move in as well.
Be
> But that still doesn't really explain why Sarge still has 2.x, since
> there are 3.1.x version that are OK on all platforms.
That's not enough; it needs to be the latest 3.1.x version OK on all
platforms before it will migrate to testing.
b.
> what is the last item doing there?
Not sure, it doesn't show up on my machine.
b.
> > Somebody update kvim, TODAY!!!
>
> give chris a break
Well, FWIW Chris isn't responsible for kvim anyway:
[EMAIL PROTECTED]:~> apt-cache show kvim
Package: kvim
...
Maintainer: Mickael Marchand <[EMAIL PROTECTED]>
b.
> Ben Burton has packages of kdbg built against 3.0.3 on people.debian.org.
When KDE 3.1 was uploaded to sid, I took those 3.0.3 packages down since
they essentially because untested and unmaintained (IIRC this was also
in the middle of several transitions including gcc2 -> gcc3, and it
> Has anyone else noticed this and/or have any idea
> on what might be causing it?
I haven't noticed it, but there do seem to be other random quirks
appearing as a result of the Qt 3.1 -> 3.2 upgrade. If downgrading Qt
to 3.1 gets rid of this problem then it might be worth submitting a KDE
bug r
> i was looking quanta documentation, and i realized that most of it
> seems to be missing. So i thought of a quanta-doc package, but didn't
> see it. am i missing something?
English docs are in the quanta package. I had assumed that i18n docs
for quanta were in the kde-i18n-* packages since qu
> kdeartwork
> ==
> 3.1.3 not uploaded yet by Ben Burton
This is not entirely true - it's uploaded but sitting in incoming (new binary
package).
b.
> Er, wha'? As far as I can tell you both said libqt3-plugins-headers ...
Indeed you are correct (i.e., oops).
FWIW, I just came home from watching a piece of Japanese surrealist
cinema. This may or may not help explain things.
b. :)
> > main.cpp:8: qwindowsstyle.h: No such file or directory
>
> I think you need to install libqt3-plugins-headers.
That one I think is in libqt3-plugins-headers instead.
b.
> A workaround is documented on http://wiki.debian.net/index.cgi?DebianKDE
Sure, but there's no specific reason that people should know to look
here once it breaks, other than doing random web or mailing list
searches. Upgrades should Just Work.
Perhaps Ralf and Madkiss have a greater plan here
> Seems libqt3-mt-dev in sid is a lower version number than the woody
> version at kde.org.
Is it? This is a serious problem - upgrades from woody to sid should be
seamless. I recall having to epoch several of my KDE modules from 0: to
4: because the woody backports had incorrect version number
> Read Ben's entertaining rant about why it's needed:
*grin*.. always glad to keep people entertained.
I'd also try passing --with-qt-dir=/usr/share/qt3 to ./configure, since
it seems to be having trouble even finding standard headers such as
qglobal.h.
b. :)
> Verify that the kdelibs4/meinproc fix really works #196564
No fix for this bug has been uploaded AFAIK. The message I posted to
the end of this bug report was actually intended for other bug reports
(the meinproc requires libxml2-utils reports) and has nothing to do with
this specific bug.
> Apparently some KDE stuff is unnecessarily depending on the compat
> headers too, which could be fixed.
This is true. However, the use of legacy headers should never have
caused breakage (upstream Qt still fully supports legacy headers), and
the transition is a task that upstream developers an
> (v) Talk to the maintainer, see what he thinks.
[...]
> Hopefully Madkiss'll have an upload ready by tomorrow's dinstall (26 hours
> away or so).
Ah, wonderful. For me (v) over the last 4.5 months has occasionally led
to positive rumblings but these were never followed by an actual upload.
> I wouldn't do it. Suppose you were the Qt maintainer, and you made a
> technical choice that some people disagree with
You mean a technical choice with a significant negative impact on users that
breaks compatibility with upstream and every other linux distribution
and that most (not some) peo
appy to do the NMU myself and wear the consequences if necessary.
Though I would first like to elicit opinions from other developers on whether
they feel this is the correct action to take at this point.
So. Do people support this move or not?
Ben.
- --
Ben Burton
[EMAIL PROTECTED]
Public
> I understand. But in unstable the bug seems to be fixed and the
> package is called 3.1.2-1.
The 3.1.2 package in unstable was actually pulled from CVS
(KDE_3_1_BRANCH) shortly after KDE 3.1.2 was tagged. So it is possible
that the bug was fixed in the brief period after CVS was tagged but
be
> whether the 196222 suggested solution works,
This is not a complicated issue. libxml2 was split, meinproc requires
parts of it that were moved into libxml2-utils but kdelibs4-dev does not
yet depend on libxml2-utils.
It is also not complicated to fix.
Depends: ..., libxml2-utils
This bre
See #198499 for a full description of the problem with kstars; it
basically boils down to kstars using non-DFSG-free data.
> Please also notice that Debian currently provides, in the non-free section
> due to this same license issues, some star-data catalogues (Gliese and
> Yale). It might be use
> 2). I've build the koffice-i18n packages in the same way that the kde-i18n
> packages are. That avoids 37 source packages at least but only gives you the
> languages.
Sure, it was always going to come from one source package. It's the 37
*binary* packages I was worried about, which is what t
> So, if you put all kde translations in kde-i18n-**, you will have to do this
> with the others kde apps which have a different release cycle.
FWIW, I was proposing this just for koffice (which has an unusually large
amount of i18n data), not for all KDE apps.
Ben.
Ah, okay, I wasn't entirely clear on the kde-i18n-lang option. What I
meant by this is that kde-i18n-lang would be updated for both KDE and
KOffice releases, and would include code taken from both branches as
appropriate. e.g., when KOffice 1.3 is released, even though KDE 3.1.2
stays the same,
Hi. :)
> we already discussed this sometime ago
Though not with any resolution.
> and since then there are koffice-i18n-xx packages
Not on the debian servers.
> apt-cache show koffice-i18n-es
> Package: koffice-i18n-es
...
> Maintainer: Ralf Nolden <[EMAIL PROTECTED]>
...
> Version: 1.2.
Hi. I'd love some input here on the packaging of very large i18n
components of software. The specific case at hand is koffice, which
still doesn't ship with i18n files. I'd love to get this sorted out.
The problem is that there is a *lot* of i18n material provided with
koffice. There are tran
Sorry about the delay on this, my thesis kind of took up all my recent time.
> About those stupid headers - is Recommends enough to make everyone stop
> nagging ?
Makes me happy.
> In the meanwhile unstable is in a state where the maintainers know
> where to use compat-headers and where they
> How exactly does it break? It worked just fine for me ... :\
I think the problem is that it's a shell script, and that from many
(most?) kfoo/debian/rules files it is invoked as "perl -w admin/debianrules".
b. :)
> I will upload the rest of KDE 3.1.2 in the next few days
My parts of KDE may take one or two weeks to upload. There's some
non-trivial changes I want to make to the packaging but I'm submitting
my PhD thesis on May 30 and so it's entirely probable that things could
get a little hectic.
Ben.
> Has anyone else had these problems with the Sid KDE?
Yes. It's been fixed in KDE 3.1.2 so this problem will disappear from
sid when 3.1.2 is uploaded.
Ben.
So it seems we're giving up completely on the idea of some sane system
for having debian install the compatibility Qt headers by default just
like *every* other Qt installation?
I realise I brought this up several times some months ago, and it did
seem IIRC that it was generally agreed upon that
> Are you sure it's just konqueror, or could it be printing something with lots
> of images that causes your problem? Try some other apps and see.
FWIW, printing for me is also broken across all of KDE. Whenever I open
a print dialog the corresponding app crashes. I'm printing via cups.
A va
> I don't know about KOffice.
KOffice will be coming after I return from a particularly intensive
computer science school where I'm teaching for another week.
b. :)
> I've got problems compiling some KDE apps. It says there is no qlist.h
> in my include path, and indeed there it is not. There is qlistview.h and
> qlistbox.h.
apt-get install libqt3-compat-headers.
b. :)
mes and
ensure they stay good for the current KDE in sid.
Thanks - Ben. :)
--
Ben Burton
[EMAIL PROTECTED]
Public Key: finger [EMAIL PROTECTED]
A little sincerity is a dangerous thing, and a great deal of it is
absolutely fatal.
- Oscar Wilde
> After upgrading Quanta ( 3.1 to 3.1.1) in Sid is Quanta not longer useable.
> Quanta starts without Problems but then i can not do anything in Quanta.
I can't reproduce this here, but then I haven't upgraded for a week. So
if there's been a new libqt or kdelibs or something that's the cause of
> This is fixed in 3.1.1 according to the changelog, but kdetoys in sid is
> still 3.1.
Patience, KDE 3.1.1 was only released about a day ago. It'll be up
soon. :)
b.
> Correct me if I'm wrong, but isn't libqt3-mt-dev the correct dev pkg to use
> when using libqt3-mt? It works for me, if it wasn't for the symlinks in
> /usr/share/qt3/lib pointing to the wrong release.
No, you're correct. But if it's looking for libqt.so then you're not
using libqt3-mt, you'
> OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to
> /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all works!
The libqt.so link is provided by package libqt3-dev, which is different
from libqt3-mt-dev (which is the Qt development package dragged in with
kdelibs4-dev
> You'll get that with apt-get install kdebase anyway :-) That's why I proposed
> to make it a metapackage for kdebase and kdm.
Ah, okay. Though I'd argue in this case just to get rid of kde-core
completely. If you only want the bare bones of KDE support, it seems
unlikely to me that you'd cho
Hmm, on retrospect the kde-extras idea seems questionable to me - it will
take a lot of effort to keep it current and to ensure that all the apps
it depends on are in good working order.
Though I'd still like to see kdbg, kprof and kcachegrind in the -devel
metapackage if it will be made, for rea
I like the following combination of what's already been suggested:
kde-core (arts, libs, base - for people not needing a full-blown KDE
environment);
kde (all of the official release excluding -dev and kdesdk, i.e.,
the KDE for general users);
kde-devel (-dev, kdesdk, other devel stuff li
> Any comments? Why am I losing kdemultimedia and koffice? xawtv and motv?
A rebuilt koffice is already uploaded to sid, should come through today.
b.
> we'll get it fixed for 3.1.1 (hopefully). Until then use kdevelop-2.1.5.
I'll do an interim upload this evening so the problem is fixed in sid;
the KDE 3.1.1 upload (for kdesdk at least) will be done when 3.1.1 is
officially announced.
Ben.
> But I removed it and reinstalled my own version today, since the SID version
> just gave me too many problems. It was also noticable slower in addition to
> the problems.
What kinds of problems?
b.
> ... and the
> prospect of a simple kde metapackage for easy installation for newbies seems
> a farfetched dream.
I'll adopt meta-kde if Chris isn't taking it (it's currently orphaned,
though there's no wnpp bug AFAICT). If I don't hear otherwise in a few
days I'll fix it up and do a new uplo
> > anybody seen Krusader for KDE 3.1 as a Deb-Package somewhere
> > (preferred for woody)?
It's already in sid built for KDE 3.1.
Ben.
> How about using Recommends: on libqt3-headers for the compat-headers ? Then
> it
> should be obvious that you need to install these if you're not an expert, but
> you're not forced to (in case you're a programmer).
Even as a programmer I'd install all Recommends: to make sure apps work
prope
> If it doens't compile using just -dev then it is a
> app that needs to be fixed, and they can help the debian movement by sorting
> this out :)
Indeed, they *can* help. I don't believe it's debian's place to force
them to.
Ben. :)
> Ben, I always appreciate your work but I think from the developers
> perspective
> you just need to have a way to get the legacy headers out of the way.
We have that already. -DQT_NO_COMPAT.
> So if we revert this and put the legacy headers back, even change
> them, which I consider to be
> Almost all of KDE CVS should be working without the compat-headers ...
I'm not referring to KDE CVS specifically; I believe perfectly that
package maintainers are capable of sorting out this situation in time.
The thing is that most users *aren't* package maintainers, and most
people who build
lternatively if libqt3-dev and
libqt3-mt-dev can be made to depend on libqt3-compat-headers.
Do other people have thoughts on this?
Ben. :)
- --
Ben Burton
[EMAIL PROTECTED]
Public Key: finger [EMAIL PROTECTED]
I like to think of Linux development as sort of a modified IETF style:
rough consensu
> I've put some times ago an ITP on k3b. However someone notice me that is
> part of kde-extragear and so can not be packaged.
This is not true. The extragear modules should not be packaged as a
single unit anyway, since each app is on its own release cycle.
Please feel welcome to package k3b s
Well, FWIW I can now verify that there are problems with third-party
apps building out of the box since the Qt headers have moved from
/usr/include/qt to /usr/include/qt3.
>From the kile build:
checking for Qt... configure: error: Qt (>= Qt 3.0.3) (headers and
libraries) not found. Please ch
> I have found that while upgrading from KDE 2.2.2 to KDE 3.1 in a pure woody
> machine there is a problem when installing package kdeartwork-theme-desktop.
> It requires that package kdewallpapers be removed first.
Yep, this was reported as bug #180209 which I've fixed in kdeartwork
4:3.1.0-
> I'll try to explain my point of view on koffice-i18n. It's very simple: if we
> have kde and koffice (separate) packages, with different release cycles and
> so, why should we package koffice-i18n and kde-i18n together?
You're right, it's a bad solution. The problem is that the other
solutio
qlist.h has been moved to package libqt3-compat-headers. A request has
already been made for kdelibs4-dev to depend on libqt3-compat-headers
until #includes like qlist.h have been removed from the core KDE
headers.
Ben. :)
> I agree that this should be taken up-stream to ask KDE to keep the
> languages seperate and merge koffice and kde together.
I think it will be difficult to persuade upstream to supply KDE and
KOffice i18n stuff together, since KDE and KOffice are on different
release cycles. However, from the
> * Package name: koffice-i18n
Hi. The situation with koffice i18n stuff is a bit unclear; in
particular, it has been included in kde-i18n at various times in the
past, though it doesn't seem to be at the moment.
There was a short thread on debian-kde regarding koffice i18n stuff
(http://li
> OTOH Qt should be found fine through the search pathes
> admin uses for looking through configure for it automatically.
So you're saying that even if debianrules isn't updated, things should
still build? So this means that calc and I *don't* need to reupload our
modules, yes?
(Though of cour
ple go to roll their own packages
it will still break AIUI.
Ben.
--
Ben Burton
[EMAIL PROTECTED]
Public Key: finger [EMAIL PROTECTED]
The books that the world calls immoral are the books that show the world
its own shame.
- Oscar Wilde
> Most probably they will get removed, since the new libraries compiled
> with GCC 3.2 have different package names (libfoo102c) and conflict
> with the previous versions.
Be aware however that there are some arch-independent KDE packages that
*don't* depend on libqt3-mt (e.g., kdesdk-scripts,
kd
1 - 100 of 314 matches
Mail list logo
