October 2009

Services recovered

Our services (primarily our web services and puppetmaster services) have recovered from unexpected interruption.

Join the Ruby SIG (mailing list)

Are you a Ruby enthusiast or maybe a Ruby on Rails web application developer? Did you know Fedora has a Special Interest Group (SIG) for Ruby related development and issues?

If you are a Ruby dev, but you didn't know about the SIG, here's our Wiki page (lists SIG members, things to do, and needs a little work), and we now have a mailing list. Whether you are with Fedora already, or just use Fedora, Extra Packages for Enterprise Linux (EPEL) or Enterprise Linux itself (Red Hat, CentOS), this mailing list is your chance to get in touch with the developers and packagers that work on your platform.

RE: Ruby-1.9.1 in Fedora?

I've posted a few things on Ruby before, I know, but this is one thing I really wanted to share with you. I'm thinking of making the search path look like this:

[jmeeuwen@ghandalf ruby-1.9.1-p243]$ ruby-1.9.1 -e 'puts $:'
/usr/local/lib64/ruby/1.9.1
/usr/local/lib64/ruby
/usr/local/share/ruby/1.9.1
/usr/local/share/ruby
/usr/lib64/ruby-1.9.1/site/1.9.1
/usr/lib64/ruby-1.9.1/site/
/usr/share/ruby/site/1.9.1
/usr/share/ruby/site/
/usr/lib64/ruby-1.9.1/vendor/1.9.1
/usr/lib64/ruby-1.9.1/vendor/
/usr/share/ruby/vendor/1.9.1
/usr/share/ruby/vendor/

Ergo;

  1. Your local, architecture specific, ruby version specific stuff
  2. Your local, architecture specific stuff
  3. Your local, architecture independent, ruby version specific stuff
  4. Your local, architecture independent stuff

    ^^ This would include results from "gem install"

  5. Packaged, architecture dependent, ruby version specific stuff, such as ruby gems from RPM, or ruby libs
  6. Packaged, architecture dependent stuff
  7. Packaged, architecture independent, ruby version specific stuff
  8. Packaged, architecture independent stuff

    ^^ This is where "yum install rubygem-*" would put it's files

  9. Architecture dependent ruby vendor, ruby version specific stuff
  10. Architecture dependent ruby vendor stuff
  11. Architecture independent, ruby version specific, ruby vendor stuff
  12. Architecture independent ruby vendor stuff

Did I forget anything? Comments?

RE: rubygem-passenger-2.2.5-2 available now

I recently blogged about rubygem-passenger-2.2.5-2 being available from my repositories, and there's a few side-notes on this:

  1. rubygem-passenger now requires rubygem-hawler, which was not (but is now) available from those same repositories
    rubygem-hawler enables one to perform /usr/bin/passenger-stress-test, which would have failed prior to including rubygem-hawler. I realize this would have better been split to a separate package, which is on my TODO list for the next version of rubygem-passenger
  2. The Apache2 module is readily available through the mod_passenger package, a subpackage of rubygem-passenger. There's no need to run passenger-install-apache2-module and in fact that command will fail. I've added to my TODO list to remove that command from the package entirely, or replace it with my own script that lets you know to install the mod_passenger package.

Fedora 12 Release Party in NL?

A Fedora 12 Release Party in the Netherlands, how does that sound?

I'm asking, just to see how many people would be interested. Since there's more then just Dutch speaking Fedora enthusiasts in the Netherlands, part of this blog post is in English, and for those of you that don't speak Dutch; drop me a line on whether you'd like a Fedora 12 Release party in NL (or not), at kanarip@kanarip.com.

In het Nederlands dan;

Wat zou je denken van een Fedora 12 Release feestje? Een paar highlights van de nieuwe features, een paar PCs met de nieuwste versie erop zodat je deze kunt uitproberen, een aantal CDs en DVDs, en een lokale mirror voor als je je laptop wilt upgraden (met opstarten van netwerk, preupgrade, yum update/upgrade, jij kiest).

Daarbij natuurlijk de gelegenheid voor een hapje en een drankje en een gesprek met andere Fedora enthousiastelingen...

Hoe klinkt dat? Laat het me weten via kanarip@kanarip.com -we kunnen dan een beetje inschatten over welke orde van grootte we het zouden kunnen gaan hebben.

rubygem-passenger-2.2.5-2 available now

I've made rubygem-passenger-2.2.5-2 packages available for Fedora 10, Fedora 11, Rawhide and EPEL-5 for those interested. You can find them at http://www.kanarip.com/custom/ if you're interested.

PS> Rubygem-passenger (a.k.a. mod_rails/mod_rack) will not be in Fedora until someone fixes the package shipping its own version of Boost

PS^2> Rubygem-passenger's %{_bindir} files have now been fixed, but for passenger-stress-testing you'll need rubygem-hawler (which is in the repositories as well)

Upgrading rubygem-git to 1.2.4 instead of 0.7.0 in Fedora 11

If there is no objections within the next few days, I would like to upgrade rubygem-git to version 1.2.4 (instead of 0.7.0 which is now in Fedora 11). It is a requirement for one of the projects still in development over at my company. I'm not sure how many people use it, so I wanted to let you know ahead of time I'm going to upgrade it (unless there's significant objections).

Drop me a line if you have objections ;-)

Default desktop, what is Fedora, yada yada

All that I can think of given recent discussions on list fedora-advisory-board list, concerning "What is Fedora?" and "What is Fedora Project?", as well as the topic on "Fedora 14 (two releases away folks) Feature Proposal", is this:

Maybe we focus too much on what the users want to consume from us -as we perceive it, while it is all there-, rather then focussing on what we want the user to consume, while we have a chance.

We oughtta be leading, not following. Should we be following <random-user>'s opinion on GNOME vs. KDE? Should we define the Fedora Project to be whatever is in anyone's mind? Should we attach a slogan to anyone's gut feeling or should we just continue to do what we do so well? Should we not be leading by example, including giving GNOME and KDE and XFCE an equal chance at being positioned as the most excellent desktop? Isn't that part of what Fedora is about?

gdk, got a ten with your name on it!

Hey gdk,

Last time we played poker has been a long time ago! Time's fun when you're having flies, no? I could have sworn I was down a few bucks, but when I met Max in Rheinfelden, he gave me a ten on your behalf saying you would play me for it.

So, long story short, I have a ten with your name on it:

Cya in Toronto! (You bring the chips)


Upgrade to Rawhide; some initial thoughts

A micro blogpost ago, I said I was going to upgrade to Rawhide. And I did. Some of you asked "How?", and so let me start by telling you exactly that; Remember I was running Fedora 11 x86_64, fully up-to-date before I started the following procedure, which I've been repeatedly executing between Alpha and Beta releases ever since Red Hat Linux 9 -and yes sometimes it fails and nukes your machine, be very, very careful.

  1. In a terminal, type:
    # yum upgrade
  2. See dependencies resolve, and fail resolving. For the part they fail resolving, determine whether you are going to need these packages after you upgraded. In my case, there is too much useless crap installed I can remove (netcdf-devel, other *-devel, packages I use once or show off to somebody but never use again, etc.), and there's things I don't really need for the work that I do on my laptop (codecs anyone?). So, in my case;
    # yum -y remove <all-packages-with-failed-dependencies>
  3. Again, attempt to upgrade and type:
    # yum -y upgrade
  4. Give it some time, if you have as many packages installed as I do. Around 2300 packages in my case, that is.
  5. First thing you do after success, is reboot.
  6. Enjoy Rawhide!

Now, for the part where have some initial thoughts on Rawhide as it currently is;

  • Apparently, my mirror isn't fully up to date. I have no gnome-shell package but that was the reason I wanted to try out Rawhide earlier then normal; I normally yum upgrade my way through to Rawhide during the same time a Beta release is pending or readily available.
  • Hence, I have yet to enjoy the nastyness that comes with running a desktop environment that is still being developed, while trying to do some actual work.
  • The GTK(+? 2? Dunno, don't care) theme thing (engine?) has slightly changed. For one, the standard buttons that say "Quit", "Save", "Close", etc. are not as huge anymore, and so now they seem to me like actual buttons (rather then empty spaces I can click on). However seamingly insignificant, its an improvement!
  • The most yum upgrade trouble I had was about this packaging effort I had once done for a customer; practically, there was no Fedora* trouble in yum upgrading. There was some RPMFusion package that wouldn't upgrade, but so be it (gstreamer-plugins-bad).
  • There is some packages in Rawhide that, I assume, have to be rebuilt (or otherwise updated). Amongst these:
    $ package-cleanup --problems
    Setting up yum
    Loaded plugins: dellsysidplugin2, fastestmirror, refresh-packagekit
    Reading local RPM database
    Processing all local requires
    Missing dependencies:
    Package NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64 requires NetworkManager = 1:0.7.1-8.git20090708.fc11
    Package NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64 requires NetworkManager-glib = 1:0.7.1-8.git20090708.fc11
    Package NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64 requires libnm_glib.so.0()(64bit)
    Package NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64 requires libnm_glib_vpn.so.0()(64bit)
    Package NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64 requires libpolkit-dbus.so.2()(64bit)
    Package NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64 requires libpolkit-gnome.so.0()(64bit)
    Package NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64 requires libpolkit-grant.so.2()(64bit)
    Package NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64 requires libpolkit.so.2()(64bit)
  • For the rest of it, everything works!

More thoughts and feedback and stuff after I've installed the new gnome-shell!