Este blog é alimentado pela comunidade aqui na rede SoftwareLivre.org e pelo feed do Planet Mageia English.
Season of KDE is an outreach program hosted by the KDE community. This year I am working as a mentor to a long time requested project related with Cantor – the development of Python 3 backend. You can read more about Cantor in my blog (texts in English and Portuguese). So, let’s say welcome and good luck to Minh Ngo, the student behind this project!
My name is Minh,Minh Ngo
I’m BSc graduated student. I’m Vietnamese, but unlike other Vietnamese students spent most of my life in Ukraine. Currently, I’m preparing myself to the Master degree that will start in the next semester.
Open source is my free time hobby, so I would like to make something that is useful for the community. Previously, I was participated in the GSoC 2013 program and in several open source projects. Some of my personal projects is available on my github page https://github.com/Ignotus, not so popular like other cool projects, but several are used by other people and this fact makes me very happy .
Cantor is one of opportunities to spend time to create an useful thing and win an exclusive KDE T-shirt :). I decided to start my contribution with the Python3 backend, because few months ago I studied several courses that are related with Machine Learning, so I was looking for a stable desktop backend for IPython. A notebook version IPython I do not entirely like and its qtconsole version doesn’t satisfy me in terms of functionality, therefore I decided to find some existent frontend for IPython that I can tune for myself. And the story with Cantor began after than
As you all know, we can’t maintain Mageia releases forever. And it’s time to say goodbye to Mageia 3. After Wednesday the 26th of November, this release won’t benefit from any more security or bugfix updates. This will allow QA team to give more time for polishing our coming Mageia 5.
So you have only one week left to upgrade to Mageia 4 if you want to keep an up-to-date system. Do not hesitate to use our mailing-lists, forums or IRC channel to speak about it and ask for help if needed.
See www.mageia.org/support for more details.
The various ways of upgrading from Mageia 3 to Mageia 4 are described in this page.
Well, HP is now promoting a new solution for webinars called HP MyRoom. And even if they provide rpm (and deb) packages, these are not working out of the box on my Mageia 64 bits distro, of course. That was already the case with HP Virtual Room previsouly.
But nothing you can’t make work, as long as you have the source don’t you ? So here is the receipe:
First install all the required dependencies that are not correctly mentioned in the rpm:
urpmi lib64xtst6 libxtst6 lib64xscrnsaver1 libxscrnsaver1 jpeg-devel lcms-devel
Then add an additional library which was not even part of Mageia when I started this post ;-)
Get it from Cauldron where I uploaded it:
urpmi libmng1-1.0.10-1.mga5.x86_64.rpm libmng1-1.0.10-1.mga5.i586.rpm
Then finally download HP MyRoom for a 64 bits RPM system and install it with:
rpm -ivh --nodeps hpmyroom-10.0.0.0210.amd64.rpm
and launch it !
And now enjoy exchanging from Linux as well as from Lynx but without the hassle to use Windows ;-)
Filed under: FLOSS Tagged: HP, HPLinux, Linux, Mageia, MyRoom
Well, it’s been a long road, longer than we anticipated, but we’re almost there! Mageia 5 Beta 1 is now validated!
What exactly does that mean? What took so long (a month and a half longer than originally planned)?
RPM 4.12 versus the Mageia buildsystem, a retrospective
The short explanation: Some stuff went wrong and other things got broken.
The long one: Back in September, we decided to update our package manager, RPM, to its latest upstream version 4.12. This was done shortly before our planned mass rebuild, a necessary step before the Beta where we rebuild all packages in the distribution to make sure that they are still compatible with the current state of our development stack. Usually, mass rebuilds show that a fair number of packages do not build anymore even if they did some months ago: the packagers’ task is then to patch them so that they can build against the new stack, or in some cases to patch the development tools to fix regressions.
But this time, the new RPM version introduced changes that were significant enough to break a lot of core packages during the mass rebuild, and lots of packages failed to build in a chain reaction. It took a couple of weeks to fix and we were already long past the planned deadline for Mageia 5 Beta 1 (originally scheduled for the end of September). So we decided to postpone it to mid October.
Still, while fixing our core tools during this first mass rebuild, some important changes were made to our RPM setup. As a consequence, half of the rebuilt packages (the ones built before our RPM setup changes) were lacking some important metadata. We then decided to do a second mass rebuild in October, which went quite fine apart from some issues with the Java stack. It was already late October when the first Beta 1 ISOs could be spun and delivered to the QA team for pre-release testing.
You may know that a Linux distribution release is basically an installer together with a set of packages. The latter were now starting to behave properly, but we were then faced with some issues in the installer regarding glibc (the GNU C library) and RPM. This delayed the beta for another week or so.
Then the QA team could finally get started with a fresh set of ISOs, and found the usual numbers of critical bugs (system doesn’t boot, stuff like that) that were fixed with the help of our developers. A big thanks to the QA team for their continued work on the ISOs while also testing update candidates for Mageia 3 and Mageia 4! This beta is far from perfect so don’t forget to check the errata, but you should be able to install it and to see the state of current cauldron. Please report any bugs, we will try to fix as many as we can for Mageia 5 Beta 2.
Consequence on the development roadmap
According to our original schedule, the second beta should have been released on October 31st… So we had to choose between skipping Beta 2 or postponing the Mageia 5 final release and the intermediate releases. Based on the input from the Beta 1 testing, we decided that we can’t afford to skip the second beta, since the current one still has some serious issues. As a consequence all planned dates for the future intermediate and finale releases have been postponed, and the new development roadmap reads as follows:
- Beta 2: December 16th, 2014
- Release Candidate: January 6th, 2015
- Internal release: January 23rd, 2015
- Final release: January 31st, 2015
Fine… Now, where is my Beta 1?
You all waited long enough for this release, so grab it with the first link, but don’t forget to check the following ones:
Test, enjoy, and report any bugs! Now is the time to polish this Mageia 5!
As explained in a previous post, lots of updates occured especially dealing with rpm. And here we go. We are facing at the moment some nasty issues in installer. The graphical part of the installer is just crashing due to a bug implying glibc and rpm. Both were recently updated.
Work is in progress and the issue was reported upstream. You can follow it here on the bug report. As soon as this bug is fixed, we will be able to release the Mageia 5 beta 1 isos. Stay tuned!