Smile

Even though I’ll be stating the obvious for so many ubuntu users/developers reading this post, I’d like to post a quick recipe for those who don’t know how to easily install the latest version of epiphany with the WebKit backend, as well as all the needed dependencies, without having to mess with compiling the source code (which is not always an easy nor a quick task, by the way).

So here we go

1. First of all, this only works for Ubuntu Jaunty or Karmic, since there are no PPAs available for previous distros to install Epiphany (WebKit PPAs provided since Hardy).
2. Add the PPA’s from the WebKit Team both for installing latest version of WebKit and Epiphany. So, that is, add the following lines to your /etc/apt/sources.list file (replace ‘karmic’ with ‘jaunty’ if needed):

   deb http://ppa.launchpad.net/webkit-team/ppa/ubuntu karmic main
   deb-src http://ppa.launchpad.net/webkit-team/ppa/ubuntu karmic main 
   
   deb http://ppa.launchpad.net/webkit-team/epiphany/ubuntu karmic main
   deb-src http://ppa.launchpad.net/webkit-team/epiphany/ubuntu karmic main

3. Import the GPG key of the repo in APT:

   sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 2D9A3C5B

4. Update APT packages cache:

   sudo apt-get update

5. Install the needed packages:

   sudo apt-get install epiphany-browser epiphany-browser-dataepiphany-extensions

6. Just wait and let APT to do its magic

And that’s all. After those simple steps you should be enjoying the last version of  this great and amazingly fast browser (2.29.6 at the time of writing this post), which is nowadays under heavy development, continuously getting better, better and even better on its roadmap towards GNOME 2.30.

So, what are you waiting for? Just go ahead and give it a try if you haven’t done it yet and make it your default browser . Now you don’t have to manually compile all the needed stuff you just don’t have any good excuse not to do it.

And don’t forget to report any issue you find in the bugzilla. Remember feedback (and patches, of course) is the best way to help with improving it even more!

Ah! by the way, almost forgot to say that…

…as another member of the Igalia gang hanging around there this weekend.

See you there guys!

[Update 2010/01/04] As commented by zerwas, there’s an even easier way from Karmic on:

1. Add the PPA’s from the WebKit Team both for installing latest version of WebKit and Epiphany:

   sudo add-apt-repository ppa:webkit-team/ppa
   sudo add-apt-repository ppa:webkit-team/epiphany

2. Update APT packages cache:

   sudo apt-get update

3. Install the needed packages:

   sudo apt-get install epiphany-browser epiphany-browser-dataepiphany-extensions

After coming back from an awesome week of holidays in Paris (lovely city, btw!), today I finally managed to get some time for making up what it became the second upstream release of frogr: frogr 0.2

Just trying to give a brief update on “what is new”, here you have an excerpt from the NEWS file:

• Generate ChangeLog from git log with ‘make dist’
• Added .spec file for fedora 11 packaging system (thanks Adrián Pérez)
• Added drag’n'drop support for loading pictures in frogr
• Added support to add tags to pictures (instead of just replacing)
• Fixed (legacy) support for libgnome2 to compile in debian lenny
• Use accesor functions instead direct access and removed some deprecated GTK+ symbols (thanks Javier Jardón)
• Added i18n support and a es_ES lang file (thanks Alejandro Piñeiro, aka API)
• Support silent build rules with automake 1.11 (thanks Javier Jardón)
• Bugfixes and several minor improvements

Entering in more detail, and as you can easily extract from the list above, the main improvements from the user’s point of view are:

• Drag’n'drop now supported, so having to add pictures through the filechooser is no longer the only method to load pictures in frogr.
• New “add tags” dialog, very handy to add tags to some specific pictures before uploading them.
• i18n support, which should make easier to get more contributions for frogr in further releases, in the form of new translations to make it even more accessible for people all over the world (did I say we’re eager for new language files?)

At last, just to mention that you already can find pre-compiled packages for some distros at the web of the project, as well as the source code tarballs in gzip and bzip2 formats. And of course, get the source code from the git repository at gitorius, in case you prefer to directly clone the source tree to make up wonderful and nice patches to contribute with, or just to provide new pre-compiled packages for your favourite distro

So… what else could I say? Just go and get it… Hope you enjoy it as much as I do

Update [2009/10/14]: It seems the other day my mind was still a bit “on holidays” and I screwed it up when creating both the pre-compiled packages and the source tarballs uploaded to the web of the project, so they would just not  work as they should when installing frogr (basically, they would not install files under the proper path so frogr just would not work).

I realized of this yesterday and now everything should be fixed in packages (and tarballs) uploaded in the “Downloads” section of such a web, so if you experienced any problems two days ago just try now again and everything should be fine.

After perhaps quite a long time since I announced the “pre-release” of frogr, back in June, I’m now happy to tell the world that the 0.1 release is finally here, providing the user a very basic but still useful set of features to upload his/her pictures to flickr. Basically, as it’s told in the NEWS file, most important changes in this first release regarding to the code from almost 2 montsh ago are:

• A better UI. Faster and better user experience.
• Basic configuration management to store account details (auth token).
• Support for editing details of multiple pictures at the same time.
• Added status and improved the progress bar usage to show the status of async operations, giving a much better feedback to the end user.
• A better (and more easily hackable) code and design.
• No more .glade files, no more gtk-builder-convert.
• Avoid libgnome dependency if gtk+ >= 2.14 is present
• Still implemented some parts of the UI (menubar) without GtkBuilder to keep compatibility with Gtk+ 2.12 (least version supported)
• Bugfixes and several (minor and major) improvements

As usual you can get the source code at http://gitorious.org/frogr, where development for version 0.2 has already started, btw. And if you visit the project’s web at http://code.google.com/p/frogr you could even find some packages for you favourite distro there as well (currently only i386 packages for Ubuntu hardy, intrepid and jaunty are available, but more flavours and platforms are coming soon: debian, fedora, x86_64…).

For the special case of hardy you’ll need to install a newer version of libflickcurl0 than the bundled in hardy repositories (0.12), which you can get from here: http://packages.ubuntu.com/intrepid/libflickcurl0 (yes, intrepid package will work fine on hardy).

At last, knowing that people use to love screenshots, here you have three of them showing the current status and UI for frogr 0.1. Yes I know, still not too ‘eye-candy’ but hey!… it’s the 0.1 release! what did you expect? We’ll have time enough to improve the UI in the future as long as frogr gets more mature and complete. And in the meanwhile I honestly think current UI is not a complete disaster either

Hope you find this interesting.

Have fun!

As Juan, I’m one of the proud owners of a Linksys NSLU2 (aka Slug) perfectly (and continuously) running the Debian/NSLU2 distribution for more than 6 months, currently featuring the following configuration (both sw and hw), after some slightly changes:

1. Attached 500Gb 2,5″ HD (powered through its USB2.0 connector).
2. MediaTomb uPnP media server, to keep a nice “media center” running always available.
3. Samba filesharing server (to easily share files with any device connected to the LAN)
4. rtorrent bitTorrent client, to use the Slug as a dedicated machine always up and ready to download whatever you want.
5. The ’screen’ command line utility (useful to easily keep the rtorrent app always running and “detachable” ).
6. OpenSSH server (ssh port forwarded in the router to access the Slug from the Internet), to easily manage my Slug from anywhere in the world.

With the exception of the HD (which used to be a 3,5″ 120Gb HD since June to December, when I replaced with the 500Gb one), the rest of the configuration was amazingly working with no problems at all for more than 6 months, as I previously stated. This, along with the fact that this  device is quite small, noise-and-heat-free (no fans) and only needs 8W (it’s the 266Mhz, ‘underclocked’ version) to work, makes it one of my favourite devices I ever had .

But all this was kind of “incomplete” stuff until I got a PS3, as a present from my girlfriend during last Christmas holidays, which gave it a new dimension to the Slug, since the PS3 bundles a nice uPnP client for pictures, audio and video which works perfectly with the MediaTomb server installed in this cute device.

The point now is that I no more need to copy the video files I download with my Slug to another device (a desktop PC, a laptop…) to watch them, either in such a device or in the TV (with the help of a multimedia HD)… all I need to do is just:

1. Have the MediaTomb server continuously running in the Slug, watching (through its inotify feature) to the /storage/videos directory for new videos (I want it to index them whenever I copy new downloaded videos under that path).
2. Have the PS3 connected to the local network, either through it’s wired or wireless interface.
3. Move the video files, as soon as they get fully downloaded, from my /storage/downloads path into /storage/videos

This way, just by the moving the downloaded media files as explained in (3), and waiting a couple of minutes for the MediaTomb to index them, I have that media content available to be directly watched in the TV, which is really cool and very handy, by the way

Of course, you can also do the same with regular pictures or audio files (which is very nice also if you have, like me, the PS3 audio output also plugged into a Hi-Fi), but I think you’ll agree with me that watching video files seems to be the best way to make the most of the Slug+Ps3+TV combo .

And that’s all, I think… just to mention I’ve written this post while I was listening to a nice Thin Lizzy album (“Dedication“) stored in the Slug, through the PS3 and my Hi-Fi equipment. It sounds good, doesn’t it?

PS: One of these days I’ll post more in detail how to set up the configuration for all the components I’m currently using in my Slug (rtorrent, Samba, MediaTomb…), just in case someone found it useful.

Today was a nice day here in the DudesConf 07, full of interesting talks about debian and meeting new (and not so new) people from differents parts of the world who came just because one main reason: talk about the debian distro, its current state and about several related things, in general terms. (more info at http://www.dudesconf.org).

At first I thought I couldn’t attend this interesting event, but at last I could and I’m happy to do so, because it was an interesting day in which, even though I wasn’t able to pay as much attention as I wished, I learned several new things and met new people that could be difficult in other way apart from this one. And we even had a GPG signing party in which we shared our fingerprints and get our gpg keys signed by each other.

But, apart from the main reason of this conference, we had some interesting experiences after dinner, leaded by a “queimada”, and a session of playing “Frets On Fire” videogame which was a really fun and funny situation: everyone staring at someone who played an “electric guitar” with a keyboard while something like a guitar-karaoke was reproduced in the projector used for the talks.

Here you are some photos of this last “experience”:

Update [21:32]: I’ve added another photo of some igalians (Chema, Calvaris, Berto, Javi and me) with Steve Langasek, one of the Debian etch release managers:

See you next time guys!