Happy New Year everybody!
I have a little New Year’s proposal for you all, users and developers.
Take a look to the bugs you have reported in Debian, this can be very easily done by browsing:
where USER@DOMAIN.NET is the email address you used for reporting. Then update the bug reports information in the following way:
- If the bug is already fixed, send an email to BUGNUMBERfirstname.lastname@example.org with a quick explanation like “it is not reproducible anymore” and the bug will be closed.
- If the bug is still there, send a email to BUGNUMBER@bugs.debian.org and specify all the new information you are able to add: newer software version where it still applies, way of reproducing the bug.
Alternatively, you can look at the bugs of your favorite package and help the maintainer. Go to http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=PACKAGE replacing PACKAGE with the application name, look at the bugs and send a email to BUGNUMBER@bugs.debian.org with all the information you can gather about the bug: if you can reproduce it (and if yes, how), versions affected, also you can make a patch…:) etc.
Above, I only gave basic hints of how to interact with the Debian BTS, if you want to know more, read the documentation at http://www.debian.org/Bugs/.
David Palacio has made a live CD with the current snapshot packaging of KDE 4.2. The distribution is being made only using the BitTorrent protocol, using the tracker services of LinuxTracker. And do not worry, it is being well seeded!
And remember this is only made with the purpose of take a look to current status of upcoming KDE 4.2. Enjoy!
Good news for those wanting to test KDE 4.2. Finally, we have decided to do a little experiment and provide snapshot packages of current KDE trunk (future KDE 4.2).
First of all, I would like to say that even if I am the one blogging, the most part of the job was done by Modestas Vainius.
I am calling this an experiment because we are not sure yet whether this is a good idea, there are several reasons:
- packaging can suffer big changes before the final release
- this is still code in development with some important bugs
- some upstream changes (like ABI bump) can make huge dependencies problems
All the above reasons are likely to generate a lot of demands from users asking for support that are surely too many for our time and, I am afraid, patience.
So, in short, these packages are being provided without any support from your packagers even if they are done by the people who usually package KDE.
You have the repository and all the information at:
The current snapshot is post-beta2 and again, before installing the packages, please read all the information. I am sorry if the wording is read as a bit harsh, but we really wanted make clear the message.
Update (25 January 2008): KDE 4.2.0 will be available soon in experimental, if you are a new user, we recommend you to wait until it is fully updated in the Debian repositories and install it from there.
I got a bunch of emails in the last weeks with one or more of the following questions. Here it is for general knowledge :)
Will be KDE 4.2 beta 1 uploaded to experimental? Or to another public repository?
And KDE 4.2 beta 2?
Maybe. But notice if it is uploaded it will be replacing current KDE 4.1 in experimental, so we will upload it only if we are sure it is stable and mature enough to replace 4.1
Will be KDE 4.2 backports in http://kde4.debian.net ?
No, backports were planned only for the KDE 4.1 series.
If experimental starts shipping KDE 4.2 (beta or RC), will be updates in http://kde4.debian.net for 4.1.4 (and if released 4.1.5)?
Yes, there will be backports for all the releases of 4.1.x.
When will be KDE 4 uploaded to unstable? And to testing?
KDE 4 will replace KDE 3 in unstable when Lenny is released. After some time, it will migrate from unstable to testing.
Bonus question: When will be Lenny released?
When it is ready.
As in every (free software) project, Debian has problems. Specially, there were 2 big problems:
- A: We are not good acknowledging, accepting and integrating new members in a good way.
- B: We have some people accumulating too much power.
In case this was not enough, the people creating the problem B) decided to fix the problem A) totally on their own in a way that makes both A and B worse.
People with too much power are winning. A lot of of the average contributors have good points about all this, but they already gave up (this is a hobby for most of all!) and do nothing because they are already too frustrated. Some try arguing and discussing, but it is not going anywhere because people of the problem B are playing to ignore everything, so you can not argue with silence.
Some people is eating this poisoned cookie, they accept these changes because finally we will be able to integrate (someway) in the project translators, artists, etc, with the cost of change badly another stuff like DM, in the way the people of the group B like.
The proposal or policy is presented as a whole, take it all or leave it.
This proposal or policy will be implemented with some minor changes resulting of “listening” people, then this people causing the problem B, will say this proposal was widely discussed since it was changed because all the discussion.
Ah, and release Lenny sometime too.
It was complicated getting this done, but finally backports for 4.1.2 are available at kde4.debian.net. Thanks to the help of Aleix Pol and his Mac Mini, there are available packages for PowerPC now.
As well, I have uploaded a backport of Qt 4.4.3 (*), for AMD64, i386 and PowerPC. If you are using KDE 4.1.x, you definitively want to use this Qt 4 version with a bunch of bugfixes.
A lot of people mailed me in the last week asking about problems with the mirror, this was caused by kde4.debian.net being actually 2 mirrors in round robin and the secondary (and faster) one having some problems syncing.
(*) Yes, I know Qt 4.4.2 and 4.4.3 are equal just with copyright changes, but it was easier backport latest version from unstable, right? :)
I have just finished uploading the Lenny backports for KDE 4.1.1 to http://kde4.debian.net/. I have improved slightly the website and added some information as well.
If you followed the instructions in the website and you are already using the KDE 4.1.0 backports, you only have to update your system and you will get automagically the KDE 4.1.1 packages.
Now Lenny has been frozen for some time and the necessary packages have migrated to Lenny (that remember is still testing); I have finally made the backports of KDE 4.1.0. You can find the repository and the instructions at:
And remember, KDE 4.1 is pretty good but it still has some issues that are little to little being fixed. Do no expect something so rock solid as KDE 3.5.x yet :)
In the beginning of this week, KDE 4.1 RC 1 was released and, of course, there are Debian packages since the release day. The instructions I blogged about how to install the beta1 (and downgrade) still mostly apply, although the version of the KDE 4 RC1 is 4.0.98.
The Debian KDE Team website has finally been updated, so you have even more useful information about how to install KDE 4.1 packages from experimental, specially the bits about Apt Pinning.
kdeplasmoids has been renamed, again, and it is now named kdeplasma-addons, this means it is currently stuck at the NEW queue in Debian. I do not know when it will be available in the archive, but luckily current version of kdeplasmoids (post beta 2), works well with the RC 1 packages, you can use it until kdeplasmoids is accepted.
The important part about RC 1 in Debian is we finally have kde4libs, kdepimlibs and kdebase-runtime in unstable, and they are meant to be released in Lenny.
Together with those packages, some KDE 4 applications have been uploaded to unstable:
- okular, the KDE 4 document viewer, has been packaged separately, and if you try it, I am sure you will love it ;)
- ktorrent 3.1.1 is now the default ktorrent version (you still can install KDE 3’s version that has been renamed to ktorrent2.2)
- and systemsettings, split from kdebase-workspace with less modules have been package separately, so you can configure the settings of KDE 4 packages.
Continuing with experimental, there are some standalone KDE 4 applications in experimental you might be interested in installing: yakuake, adept-manager, gtk-qt-engine-kde4, konq-plugins, rsibreak and digikam.
You can find as well, the 9th alpha of KOffice that was released a couple of days ago. If you need an excuse to try it out, take a look to the visual changelog.
If you are a Debian user and you have not tried KDE 4 yet but you are curious, I think you finally should give it a try, that some packages are in experimental it is not because it is experimental software (well, once KDE 4.1 is out!), it is because full KDE 4.1 is not meant to the be released in the Debian stable release that will be shipping KDE 3.5.9 and they both are not co-installable. There will be backports of KDE 4.1 for Lenny, but that is a topic for a next post.
There will not be Debian packages for KDE 4.1 beta 2. Last week, beta 1 was replaced in experimental by a snapshot of the revision 819867, and beta 2 was tagged at revision 821791, so it is not a huge difference.
I have no idea when we will do the next update for the KDE 4.1 packages, I guess with the RC 1. My personal plans for the next 2 weeks are polishing all the possible KDE 3.5.9 for Lenny.
The instructions I blogged about how to install KDE 4.1 beta 1 still apply, the only changes are: extragears-plasma package is now called kdeplasmoids and the version is 4.0.82+svn819867 instead of 4.0.80.
In the case you are installing in a clean environment, you can use directly the metapackages: kde4-minimal for a minimal KDE 4 environment: kdelibs, kdepimlibs and all the kdebase packages; or kde4 that will install everything.
As important note, if you are using these packages, remember before reporting a bug that the issue could be already fixed in the beta 2 or later.
And, by the way, hi planet KDE!