Beagle support in Ubuntu has been less than stellar up until this point (across all releases), and unfortunately, the best that we can really hope for in the immediate future is acceptable. This is mostly because only a few of Beagle’s developers are running Ubuntu, and accurately reproducing common errors is difficult. To top this all off, the defacto Ubuntu contact at this point is me, and I haven’t had the available time to really track down some of the more difficult bugs.
However, this problem reached an all time low when the beagle source package stopped building in Gutsy. This spurred us into action (our urgency increasing as we realized how close Gutsy was to shipping) and as a result there exist updated Ubuntu Gutsy packages (based upon the new 0.2.18 bugfix release of Beagle) available for testing. Thanks to Launchpads new super-awesome Personal Package Archive system, you only need to add the following sources, or download from the corresponding link. (NOTE! the versioning of these debs will not force an update if they are accepted into main, you will need to reinstall should they be accepted at their current version number!)
deb http://ppa.launchpad.net/kkubasik/ubuntu gutsy maindeb-src http://ppa.launchpad.net/kkubasik/ubuntu gutsy main
Please report bugs with these packages either to Beagle in launchpad or the dashboard-hackers mailing list. The more feedback we get in the next few days the better the chance that Ubuntu Gutsy will ship a solid Beagle.
Hello,
Will you be making Beagle 0.30 debs available for testing on Ubuntu? I’ve just built it from SVN but some regularly built packages would be nice
Thanks
I hope to have some test packages rolled soon. Beagle 0.3 represents some major structural changes to the beagle codebase as well as a plethora of new features, so the new package will be a little tricky, but I’ll post soon!
Great. I’ve been running 0.3 from SVN and it seems to be stable (i.e. not crashing). There’s a few things I’ve noticed that might be bugs but I’ll wait for your debs before I start reporting anything. Cheers.
Ahem! Kevin, you lost the race – you gotta start afresh now
. 0.3.1 was just released (it contains fixes for two major problems upgraders might face).
Since I am commenting anyway, if you are the moderator for gnome-announce, could you see that the announcement email for 0.3.1 is approved ? It was sent from an unregistered email address. TIA.
Thats fine =/ I’ll keep on workin. Its just exam and final project time at school. =/ Anyways, I approved the announcement, which came at the same time as a tracker one, so that’s kinda fun
With a lot of help from the Ubuntu community I have installed Beagle 0.3.4. I am experiencing some problems and I do not know how to make them go away:
I found a thunderbird xpi file in the beagle package and without adjustment or recompiling added it into Thunderbird as an addon. It now appears in the Thunderbird addons as a beagle indexer. I am using Pop3 not imap.
There are no instructions as to how to install the Thunderbird extension so I have had to guess that there is no need to make, and make install, although those files are in the TB extension folder within the beagle package.
It seems to be working with Thunderbird files showing in the index information. I had left the machine on overnight and although when the index started on TB there was a window that kept saying it was attempting to contact the host with login info I ignored it. I assume that the addon also tries to index online emails. The result appears to be my emails have been indexed, but the Beagle icon in Thunderbird is showing a large number of errors stating:
An error occurred while indexing. Error description:
TypeError: account.incomingServer has no properties
As I am using Pop3 I am surprised at the reference to incoming server.
I am not seeing any extract of the emails within the search result. I only see the subject of the email. I am used to seeing the first say 200 characters being returned as part of a search. Do you know if Beagle does this as well?
Robin
Is anyone able to reply to this email by me?