From: David Bremner <david@tethera.net>
To: <notmuch@notmuchmail.org>, Felipe Contreras <felipe.contreras@gmail.com>
Subject: [Christian Hofstaedtler] Bug#739120: ruby-notmuch: Please update ruby binary extension install path
Date: Sat, 15 Feb 2014 23:18:26 -0400 [thread overview]
Message-ID: <87vbwfzqwt.fsf@zancas.localnet> (raw)
[-- Attachment #1: Type: text/plain, Size: 125 bytes --]
Any comments Felipe? It's debian specific, and I assume if notmuch vim
still runs with that change, it didn't do any harm.
[-- Attachment #2: Type: message/rfc822, Size: 4672 bytes --]
From: Christian Hofstaedtler <zeha@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#739120: ruby-notmuch: Please update ruby binary extension install path
Date: Sat, 15 Feb 2014 23:40:32 +0100
Message-ID: <20140215224032.30302.34424.reportbug@nq.home.zeha.at>
Package: ruby-notmuch
Version: 0.17-3
Severity: normal
Tags: patch
Dear Maintainer,
When ruby-defaults > 1:2.0 will be uploaded to sid, the version of Ruby
provided by the 'ruby' and 'ruby-dev' packages will change to version 2.0.
This version change includes a change to the path for binary extensions.
Below you'll find a patch that works for Ruby 1.9.1 as well as Ruby 2.0,
so it's safe to apply now.
Thank you,
Christian
diff -Nru notmuch-0.17/debian/ruby-notmuch.install notmuch-0.17/debian/ruby-notmuch.install
--- notmuch-0.17/debian/ruby-notmuch.install 2014-01-12 22:10:04.000000000 +0100
+++ notmuch-0.17/debian/ruby-notmuch.install 2014-02-15 23:28:32.000000000 +0100
@@ -1 +1 @@
-usr/lib/ruby/vendor_ruby/*/*/notmuch.so
+usr/lib/*/*ruby/*/*/notmuch.so
next reply other threads:[~2014-02-16 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 3:18 David Bremner [this message]
2014-02-22 1:07 ` [Christian Hofstaedtler] Bug#739120: ruby-notmuch: Please update ruby binary extension install path David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbwfzqwt.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=felipe.contreras@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).