Time to go back to project-builder.org for its own next version !
Posts Tagged ‘Mandriva’
The MondoRescue project has made quite some progresses again recently. So it”s time to publish mondo 3.0.1 and mindi 2.1.1. Those are bug fix versions mainly. Especially there is a fix for bad LVM i-want-my-lvm setup file, where sometimes duplicated lines were generated which was annoying, as well as an error again in some cases to compute the multiplier factor used when disk size changed.
Among the major improvements, we are now supporting kernel 3.2 new usb_common module, btrfs, grub2 and the launch of rpcbind at restore time to improve NFS restore support for at least RHEL 6.2 (on which I made my tests) and hopefully Debian 6 as well (feedback welcome !). All details are available in trac.
I have had multiple reports that this version was indeed better than 3.0.0 with regards to the issues mentionned upper, so I think it’s time to make it official now, so a larger audience can test it. This is the version I’ll push to Mageia tomorrow, once the build is done, and to Mandriva when time permits. What I find nice, is that latest releases receive more feedback, and also more pathces from contributors and users. A good sign !
The next task on my TODO list is to publish a newer version of project-builder.org as well, that is still helping me dramatically in building the 100+ tuples as well as indices for urpmi/yum/apt/… in the public repository.
To be honest the first packages appeared before Christmas as I was hoping to have everything ready as a gift ! But I met a certain number of issues trying to build all packages for the 99 different distributions I’m trying to build for ! This is due to my upgrade to Mageia 1 where the QEMU/KVM version proposed work differently from the previous Mandriva 2010.2 I was using.
Some i386 VMs are now freezing, so I had to find new correct parameters for them. Then autoconf wasn’t generating a correct content for all Mandrake/Mandriva build for mondo, so I had to call for these distro now %configure2_5 as a macro, instead of %configure.
And I still have some issues remaining, with busybox on SLES 9, Mandriva 2009.1, and RHEL 3, with some old SuSE (10.1-11.0) and old Asianux 2, RH 7.3/9, RHAS 2.1 … So Project-Builder.org gained at this occasion a new feature which consists in enumerating on the remote repo which packages have been built correctly or not. And chain the result to a sbx2vm option through the new –rebuild option, which will trigger the rebuild of all not correctly built packages. Very handy ! And will be used to finish publishing what is missing and still useful.
And finally looking at all the modifications since latest stable, MondoRescue really deserve it’s 3.0.0 label ! I won’t be able to cope with the Linux kernel, now at 3.2, but hopefully you’ll find that new version usefull. It fixes a lot of issues brought recently on the mailing list. Remains to work on the Xen kernel support more precisely, but most of what I wanted to fix is in it, including OBDR fixes, RHEL 6.2 fixes, SSSTK ProLiant support improved, loop mount issues, bootable USB keys, mdadm support for metadata, a grub install fix among many others.
You’ll need to use mondo 3.0.0 with mindi 2.1.0 and mindi-busybox 1.18.5 to have a working environemnt as underlined on our Wiki.
And even if it’s a 3.0.0 number, I consider it stable and in the line of latest 2.2.9.x versions. I’d like to avoid copying my Red Hat friends with their .0 versions 😉
Happy New Year and Disaster Recovery with MondoRescue !
Time has come again to think to our friends down under ! Since I was there in 2007 for a MondoRescue conference I think this is really a place to be in the FLOSS ecosystem when possible; Too bad it’s so far away from France 😦 Travel costs are not light either.
But I thought I should propose the follwoing mini-conf, as the one I attended in Fosdem 2010 on the same topic worked very interesting, and allowed to start some joint collaboration that I think is fruitful and avoid/reduce fragmentation.
I hope it will be accepted to give me an opportunity to fly there and meet with the great community which gathers there each year.
So here it is (Thanks to the great example provided by Martin Michlmayr last year)
The “Cross-Distribution” mini-conf at LCA 2012 (Ballarat, Australia; January 16-20 2012) is for people interested in cooperation between Open Source distributions. Topics include contributors agreements, licensing policies, packaging best practices and tools, sharing patches to upstream projects, communications, working with upstream Open Source developers, translations, governance, workflow in place, version control systems, bug reporting management and sharing, vcs-pkg.org, funding, marketing, lessons from your experience, and whatever related topics people would like to bring up. Whether you are a single contributor working on a single package, or leading a full distribution, managing a full distribution infrastructure, or representing it in the press, whether it’s famous as Debian or less as AbulEdu this mini-conf hopes to bring different people together to exchange thoughts and facilitate discussion about these topics.
Presentation submitters should feel free to suggest their own topics. Here is a list of potentially interesting subjects (in no particular order):
* Building software packages on a large scale
* Choosing valid licenses and copyright policies
* Patch management
* Working with upstream
* Forking a distribution
* Experiences in distributed development
* Managing bug report and enhancement request
* Tools to support making a distribution
* Translation of a distribution
* Reuse between distributions
* Collaborationbetween distributions
* Distribution structures
* Distribution Development Management and Governance
* Distribution Corporate Governance
* Lessons learned in building up your distribution
* Applying your copyright and license choices
We hope to receive proposals for:
* 50 minute expert panel discussions
* 50 minute full presentations
* 25 minute half presentations
* 5-10 minute lightning talks (e.g. success stories, …)
To submit a proposal, please contact Bruno Cornec at email@example.com and include the following information:
* Your name
* Brief bio noting any previous speaking experience
* Talk title
* Brief outline of your proposed talk
* Notes of any special equipment / facilities you may require
There has been a recent discussion on the Mageia mailing list on the mondo package which is one of the last having a non-coherent version schema with the one in Mandriva, thus blocking the update.
I was annoyed by this, so took the opportunity I was at Solution Linux to discuss about it with Anne Nicolas and Erwan Velu to try to find the best solution. Well, in that case, it seems there is no 😦
Upstream has move 5 years ago to fix a discrepency: renaming versions that were 2.04,2.05 into 2.0.4, 2.0.5 especially in order to facilitate life of distributions. But Mandriva was already at that time with 2.05. And now, when upstream is at 2.2.9.x, Mandriva is still at 2.29.x. And nobody really understand today why there is a mismatch between Mandriva and upstream.
So I think that Mageia should not suffer from that, even if it means that upgrade from Mandriva to Mageia won’t work out of the box for mondo. Well, in fact, people will keep the mandriva package (2.29 being higher than 2.2.9). So the receipe is, when you’ll upgrade from Mandriva to Mageia around the 1st of June, you’ll have to remove manually the mondo package to reinstall it afterwards. Not too complicated, and will avoid packagers to maintain an Epoch for the rest of Mageia, when the distribution is just started. Note that it just affect the mondo package. All the others are already sane.
All other attempts we tried to evoke had other drawbacks, and as much as I hate having exceptions in process, for once, I think this will be much less painful afterwards. Also not everybody will upgrade. Some will directly install and won’t see anything. A small price to pay to be clean for the future (after all it’s what Mageia is all about no ?) !!
I took the opportunity of a Data Center planned shutdown to do a task a reported way too long: migrating my existing old TC4100 NetServer which was hosting the projects I’m working on in our Solution Center to a much less obsolete ProLiant system with much more capacities.
I also updated the underlying distribution to the latest Mandriva 2010.2 (Mageia is still not ready for production usage), and seeing that trac, my main tool of choice for helping e manage these projects, was still at version 0.11.x, I decided to look at cooker, take the latest 0.12.1 and backport it on to my system (python-genshi was also needed).
Was not too complicated, as long as you follow the upgrade guidelines for trac. In short do upgrade, wiki upgrade and repository resync ‘*’. I also took that opportunity to have a single instance of trac to manage the 3 projects in a consistent way, sharing at maximum what could be. Notice the new [inherit] possibility provided in the trac.ini file as an easy way to do it.
Lots of new features are provided now ! Inerface is still very nice and performant (well new HW helps as well 😉 Once the WebAdmin plugin has been installed and the trac.ini files cleaned up, I was at work again, with a much more maintainable environement. So kudis to the trac team here !
The Web sites and FTP services are working just fine, but I still need to work on re-enabling Sympa to be completely operational.
Last item I really need to look at is a way to reduce spam in tickets and wiki pages, so the captcha method seems to be the way to go. Other ideas welcome !!
So most of my Debian friends or Fedora friends would argue with me why I’m still choosing Mandriva for that ? Well the answer is for me simple: it provides all the tool I need to do what I have to do on that machine. Which means in addition to the services already mentioned, creating yum repo (createrepo is there), or for dpk (dpkg-scanpackage and apt-ftparchive are also there) or for urpmi (genhdlist is also there. And except Mageia, I don’t know of any distribution that would allo wme to do that.
And anyway, if it’s not in it, I just have to add it 😉 And the Mandriva/Mageia ecosystem is still IMHO the most friendly to receive contributions. So, even if the future may be seen as uncertain, it’s still fo me the way to go.
Services are nearly all back online, so thanks should go to my HP colleagues, the Solution Center for hosting, the trac, vsftpd, Apache, Sympa and Mandriva teams. Please use the projects, report bugs, write documentation, share and enjoy !
Just a small hint (this page serves as a reminder for me mainly) for using Thunderbird as default mail reader with KDE4. You may run the
systemsettings command (or click on it in the KDE panel), select the mail client entry and type the following line for thunderbird:
/usr/bin/thunderbird -compose "subject=%s,cc=%c,to=%t,attachment=%A"
Works like a charm here. Reference doc is at https://developer.mozilla.org/en/Command_Line_Options and also by letting the mouse over the text box where you have to pass that text.
Typically OpenOffice.org which uses on Mandriva 2010.1 by default the
xdg-menu entry for the default mail reader just does the right thing when ask to send by mail the current document.
Well, it wasn’t too long to wait 😉
At least the Mandriva community doesn’t seem to be in trouble anymore. Mageia, a Mandriva fork has been made by an impressive list of former Mandriva contributors and employees. So I’ve subscribed to the mailing lists, and will now contribute to this fork as well myself (don’t expect much that what I was doing before however ;-)). There I know the names of the people behind and appreciate them, so should give us an exit way by the top. The real question remaining there for me is how will some of the former employee be able to contibute, without a regular and fixed salary around. I guess the future will say how this evolves for them.
So to my previous blog message, the answer is even more clear that the Mandriva that is now in trouble is the Mandriva SA company. They didn’t generated the trust in their community. So it vanished. Remember XFree86 vs Xorg ? I’m pretty sure we are on a similar history now.
For those of you who would like to meet to discuss contibuous packaging and project-builder.org, disaster recovery and MondoRescue.org, deployment and LinuxCOE.org, Linux at HP, Mandriva community, HP.Intel/Red Hat partnership or what ever other topic, feel free to touch base with me during the Open Source Think Tank and Open World Forum between the 28th of September and 1st of October 2010 in Paris.
The cooker community is hot these days. A lot of Mandriva employees have announced their resignation from the Mandriva company. This is occuring as following to the death of Edge-IT (subsidary of the Mandriva firm) which was employing lots of employees working around the core of the Mandriva distribution.
It seems that Wallix is bringing financial support to Mandriva in order to save it. Well what does save mean here ? It seems the interest of Wallix is in Pulse and MDS. Well that’s not the real technical crown of Mandriva ! That plus Linux Rescue Server (competitor of MondoRescue) are more classical commercial products offering than Open Source projects.As well as Wallix products. As for the mentioned expertise in Linux, it’s probably too late as most of that is already gone, or will soon.
So it seems to me after looking at all these recent events that the orientation that will be taken is to favour the activity of software selling to the detriment of the Open Source activities. Anyway, without Olivier, Anne, Fred, Nicolas, our brasilian friends of cooker, and all the people who have recently left, I have no hope that the new Mandriva firm will be interested in maintaining a distribution anymore when so many people are leaving. Maybe some of their tools at the limit. But don’t hold your breathe here 😦
So the Mandriva firm will soon become much less interesting to me: no more friends working there, no Open Source dedication, Commercial SW dev centric. The company will probably survive, at least a bit. But what about the other Mandriva, the most interesting in fact, the distribution ?
Well, without all core contributors that were payed by the firm to develop it, it may well disappear. And that’s more of a concern to me as I have at least 10 computers, critical to both my personal and professional activity running it. It may well become an itch to scratch.
I think there are 2 scenarios there: the community is strong enough to reorganize itself, find new hosting for developing the distro, enough contributors to maintain packages, and continue to develop the real value add of Mandriva, the distro: urpmi, msec, auto-inst, draktools, KDE integration, PLF, … all what makes this distrubtion speial to its users. Is it really possible. Well I think I could give a bit more of my time to maintain some more packages and help at my level ontributing to improve it. It would also place it at a similar level to Debian, a pure open source distro, used and developed by its community. Why not, but again if ex-Mandriva firm employee do not have time to contribute anymore, big losses have to be expexted from their departure, and correct replacement will be long and hard to have. Also what about the innovation on the distro then.
The other and sader scenario is that the new mandriva doesn’t help the community to reform (they host everything today), thus discouraging the good willness of current contributors, making them move to another distro of choice for their activities. I for one, clearly will look at latest fedora and debian version to see which one is the most appealing to me, and which community I may join (my past experience with these 2 doesn’t make that move a very happy one to me, feedbacks welcome here).
Maybe there is also a mid solution: people interested by the above mentioned specific Mandriva tools adapt them to provide them on Fedora, OpenSuSE, … and thus make these distro lok more Mandriva friendly than today. I for sure will look closely at what happens in the coming days, and especialy around the 17th of September when the AG will be hold.
At least we have all these possibilities because the founders of Mandriva had the wisdom to put all their devs under the GPL. Thus ex-employees can continue to work on their tools if they want, if their new employer find it useful for their activity. Or others can take over. Without that, we would just cry and move right away.
I don’t worry too much about ex-Mandriva employees. Their talent and proof of experience around what they did for the Mandriva distro will serve as the best resume to find another place somewhere, and i’m ready to support them in their research where I can, if it’s useful.
Mistakes were made in the past around the Mandriva firm management. However its communiy and open source devs are just among the greatest I ever met in FLOSS. Let’s hope that this community (booth contributors and ex-employees) will find a way to persue its quest.