I've uploaded Xapian 1.2.4 (including Search::Xapian 1.2.4.0). As usual you can download from: http://xapian.org/download You can read an overview of the release here: http://trac.xapian.org/wiki/ReleaseOverview/1.2.4 The full lists of user-visible changes are linked to from there, and also from the "[news]" links on the download page. As always, if you encounter problems, please report them here, or to the bug-tracker: http://xapian.org/bugs Here are the SHA1 checksums of the released files: 4c2184d981bd60342c615d816ce414f223cc16fb Search-Xapian-1.2.4.0.tar.gz 13611f09cdbca8424c871c79d14c8e75b6547a9c xapian-bindings-1.2.4.tar.gz c269e0f711ff4c9423d6301c3f7b949cc85a01b4 xapian-core-1.2.4.tar.gz 9df4f10221c4e02747182cd87fd22321b16287a5 xapian-omega-1.2.4.tar.gz And SHA256 checksums (more secure, but sha256sum is less widely installed): a1cc1f394c5f62d4e1c9df3e7f77287f6ca6aae2b0f9a52c45b846ebaa4c8394 Search-Xapian-1.2.4.0.tar.gz d41ebd46aa5070782b8294caea6bc02ef96f8506081e52cf8970056bc9a08f0c xapian-bindings-1.2.4.tar.gz 0665c02aa1a6cccc071d4f2b426ac0feb6f4f8f0e50da720ce375ae6d3d6f348 xapian-core-1.2.4.tar.gz 492e30b89ac74bad1cf1952f2fed6124fdb4890ca585cfc4c98e3ea7eb280b2d xapian-omega-1.2.4.tar.gz Cheers, Olly -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: Digital signature URL: <http://lists.xapian.org/pipermail/xapian-discuss/attachments/20101221/dd57721c/attachment.pgp>
On 20/12/2010 12:40, Olly Betts wrote:> I've uploaded Xapian 1.2.4 (including Search::Xapian 1.2.4.0). >Windows binaries and build files are available from the usual place: http://www.flax.co.uk/xapian_binaries If you're building from source, please read the README file first - there's a few patches you'll need to make. Charlie
On Tue, 2010-12-21 at 01:40 +1300, Olly Betts wrote:> I've uploaded Xapian 1.2.4 (including Search::Xapian 1.2.4.0).I've tried compiling this on RHEL5 and get this for xapian-omega: diritor.cc: In member function 'std::string DirectoryIterator::get_magic_mimetype()': diritor.cc:104: error: 'MAGIC_MIME_TYPE' was not declared in this scope make[2]: *** [diritor.o] Error 1 rpm -qf /usr/include/magic.h file-4.17-15.el5_3.1 /usr/include/magic.h: #define MAGIC_NONE 0x000 /* No flags */ #define MAGIC_DEBUG 0x001 /* Turn on debugging */ #define MAGIC_SYMLINK 0x002 /* Follow symlinks */ #define MAGIC_COMPRESS 0x004 /* Check inside compressed files */ #define MAGIC_DEVICES 0x008 /* Look at the contents of devices */ #define MAGIC_MIME 0x010 /* Return a mime string */ #define MAGIC_CONTINUE 0x020 /* Return all matches */ #define MAGIC_CHECK 0x040 /* Print warnings to stderr */ #define MAGIC_PRESERVE_ATIME 0x080 /* Restore access time on exit */ #define MAGIC_RAW 0x100 /* Don't translate unprintable chars */ #define MAGIC_ERROR 0x200 /* Handle ENOENT etc as real errors */ /Tim.
On Tue, 2011-01-18 at 14:52 +0000, Olly Betts wrote:> On Tue, Jan 18, 2011 at 02:47:38PM +0000, Tim Brody wrote: > > diritor.cc:104: error: 'MAGIC_MIME_TYPE' was not declared in this scope > > make[2]: *** [diritor.o] Error 1 > > This is fixed in trunk already - here's the patch ("Unified Diff" link > at the bottom is the actual patch file): > > http://trac.xapian.org/changeset/15281Next ... It looks like outlookmsg2html is going to the wrong place on install: /usr/lib64/xapian-omega/outlookmsg2html It's turning up as an unknown file in the rpm spec. 'omega' is also being installed there, which doesn't seem right for /lib64? /Tim.
On Wed, 2011-01-19 at 03:37 +0000, Olly Betts wrote:> On Tue, Jan 18, 2011 at 03:23:14PM +0000, Tim Brody wrote: > > It looks like outlookmsg2html is going to the wrong place on install: > > /usr/lib64/xapian-omega/outlookmsg2html > > Hmm, did you miss out a "bin" directory there? > > > It's turning up as an unknown file in the rpm spec. 'omega' is also > > being installed there, which doesn't seem right for /lib64? > > Well, the lib64 is thanks to RPM - by default this is under > <prefix>/lib. > > Arguably libexecdir would be a more appropriate location, though > outlookmsg2html is actually an arch-independent script so probably > should be under /usr/share. > > To be useful, the omega CGI actually needs to go wherever CGI scripts go > for the distro, or else to be copied/linked/symlinked by the user to > where it is wanted, but the former isn't possible to automatically > determine AFAIK, and the latter certainly isn't. I don't know what RHEL > or Fedora does, but for Debian and Ubuntu the CGI is packaged as: > > /usr/lib/cgi-bin/omega/omega > > Anyway, for now I would just move them somewhere suitable in the spec > file after "make install".I've modified the .spec like so: # Move the scripts to the right place mv %{buildroot}%{_libdir}/xapian-omega/bin/outlookmsg2html %{buildroot}/usr/share/omega mv %{buildroot}/usr/share/omega %{buildroot}%{_datadir}/%{name} And updated rpm.eprints.org/xapian to 1.2.4. All the best, Tim.