I wanted to renew my GPG key for some time and after reading the latest news, I finally have generated a new key today.
pub 4096R/6AA15948 2009-05-10
Key fingerprint = 7A33 ECAA 188B 96F2 7C91 7288 B346 4F89 6AA1 5948
uid Ana Beatriz Guerrero López <firstname.lastname@example.org>
uid Ana Beatriz Guerrero López <email@example.com>
sub 4096R/2497B8B2 2009-05-10
Since I tend to forget this stuff, I am blogging all the steps I have followed.
Long and verbose post follows…
It was 2 years ago when we started working in KDE 4 packages, and exactly 20 months ago when we started uploading KDE 4.0.0 beta 1 to experimental. Finally, we are working in packages that are targeted to unstable \o/.
As announced in the users mailing list, we will be uploading KDE 4.2.2 to unstable in the next days, so look carefully at what you update :)
We have worked very hard in providing a smooth upgrade, but given the change is so big, some new (little!) problems will be discovered. One of the most problematic points is we were using .kde4 to store user data and settings of KDE 4 and now it is time to switch back to the default .kde. There are several possible migration cases here and for allow users select the case they prefer, a migration wizard tool named Kaboom has been created inside the Debian KDE team.
Be aware that there will be some inconsistencies in unstable the following days after KDE 4.2.2 reaches the archive. So please, be patient.
We are still testing and we are not uploading until we think it is good to go, so next days could become 2 weeks. Again, be patient :)
If you want to keep using KDE 3.5.10 for a few weeks more, just do not upgrade yet. But if you want to keep using KDE 3.5.10 for months, maybe you should consider become a Lenny user.
If you have questions, doubts and/or suggestions, you can check our Debian KDE Team website where we try to add information and the archive of the Debian KDE users mailing list.
Time for a personal note. KDE 4.2 is a huge change from KDE 3.5, and it is normal if you do not fully like it in the beginning. But I do think most of users of KDE 3 will feel very comfortable in KDE 4 after some days using it. You just need to discover the new ways of doing some tasks. Also, once KDE 4.2 is sitting in unstable, a lot of third party applications (specially plasma widgets) for KDE 4 will be finally uploaded to the Debian archive, making KDE 4 even better.
I have found today someone who spents an average of 12 hours every day working with the computer, and who has never heard about twitter. He keeps insisting he comes from the future.
Some stuff I want to reminder for next year’s FOSDEM:
- Carry a power bar with at least 3 outlets. Power plugs are a limited resource. With a power bar at FOSDEM you always will be able to get power for your laptop/gadgets and make new friends. All at the same time!
Make a backup schedule, in case the talk you wanted to attend run out of space.
Häagen-Dazs next to LUIZA/LOUISE metro station is good for breakfast and dessert. And there is wifi!
About a week ago I updated the KDE 4.1 backports for Lenny with the fourth and last revision of KDE 4.1.
As previously announced, this will be the last update available at http://kde4.debian.net
What is next?
The repository will continue there, so Lenny users can choose between KDE 3.5.9+ and KDE 4.1.4. But since 4.1.4 packages are not official, they do not have support: no bugs in the BTS or security updates.
If you are using Debian Lenny for stability and security purposes, you should use KDE 3.5.
Testing users (future squeeze, current Lenny) can continue using them until KDE 4.2 reaches testing. Again, remember, no bugs in the BTS or security updates, but they will get a clean upgrade to KDE 4.2 in the near future.
Unstable users. I have found that there are people using unstable with the backports, when they should be using experimental KDE 4.1. If this is your case, you can stick with 4.1.4 until KDE 4.2 reaches unstable or switch to experimental in a few days and get KDE 4.2 (no yet! it needs to be released first :) ).
Last, but not less important, thanks to all the people helping with the backports: MoDaX for helping as backup and the rest of the Qt/KDE team who worked in the experimental packages. HE, zobel and aba for his sysadmin tasks. apol for allowing me torture his PowerPC machine. All those who translated the instructions into their languages and
helped to others users in mailing lists and forums.
A quick note about KDE 3.5 to be released in Lenny
As most of you have realized, the packages of KDE 3.5 in Lenny and unstable are a mixture of KDE 3.5.9 and 3.5.10. Given that KDE 3.5.10 was released after Lenny was frozen, we could not push this new version into Lenny, however the KDE 3.5 packages were patched about June last year with the latest changes in KDE 3.5 from the KDE subversion. This means some of the modules with the version 3.5.9 are exactly the same that is shipped as 3.5.10.
The only “big” stuff missing are the kicker improvements shipped in kdebase and some bug fixes in kdepim. But in global, it is closer to KDE 3.5.10 that to KDE 3.5.9. If you want to see what changes are you missing, check the KDE 3.5.10 changelog.
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.