Your message dated Mon, 04 Jun 2007 18:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427481: fixed in libinotify-ruby 0.0.0-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libinotify-ruby
Version: 0.0.0-2
Severity: serious
Tags: patch
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs
hi,
while doing an archive wide package rebuild your package failed to build from
source for the following reason:
> cd .
> /usr/bin/make distclean
> make[1]: Entering directory `/build/user/libinotify-ruby-0.0.0'
> make[1]: Leaving directory `/build/user/libinotify-ruby-0.0.0'
> /usr/bin/ruby1.9 extconf.rb
> checking for linux/inotify.h... yes
> creating Makefile
> /usr/bin/make
> make[1]: Entering directory `/build/user/libinotify-ruby-0.0.0'
> cc -I. -I/usr/lib/ruby/1.9/i486-linux -I/usr/lib/ruby/1.9/i486-linux -Iext
> -DHAVE_LINUX_INOTIFY_H -fPIC -fno-strict-aliasing -fPIC -c ext/inotify.c
> ext/inotify.c: In function 'rb_inotify_add_watch':
> ext/inotify.c:79: error: 'OpenFile' undeclared (first use in this function)
> ext/inotify.c:79: error: (Each undeclared identifier is reported only once
> ext/inotify.c:79: error: for each function it appears in.)
> ext/inotify.c:79: error: 'fptr' undeclared (first use in this function)
> ext/inotify.c:82: error: 'struct RString' has no member named 'ptr'
> ext/inotify.c:83: error: 'struct RString' has no member named 'ptr'
> ext/inotify.c: In function 'rb_inotify_each_event':
> ext/inotify.c:110: error: 'OpenFile' undeclared (first use in this function)
> ext/inotify.c:110: error: 'fptr' undeclared (first use in this function)
> make[1]: *** [inotify.o] Error 1
> make[1]: Leaving directory `/build/user/libinotify-ruby-0.0.0'
> make: *** [install/libinotify-ruby1.9] Error 2
The Full Build log is available and can be viewed at:
http://people.debian.org/~lucas/logs/2007/06/01/
i think attached patch should fix this issue.
bye,
- michael
diff -ruN orig/libinotify-ruby-0.0.0/ext/inotify.c patch/libinotify-ruby-0.0.0/ext/inotify.c
--- orig/libinotify-ruby-0.0.0/ext/inotify.c 2007-06-04 13:31:42.000000000 +0200
+++ patch/libinotify-ruby-0.0.0/ext/inotify.c 2007-06-04 13:44:25.000000000 +0200
@@ -1,5 +1,6 @@
#include <ruby.h>
#include <rubyio.h>
+#include <version.h>
#ifdef HAVE_LINUX_INOTIFY_H
#include <asm/unistd.h>
@@ -76,11 +77,15 @@
*/
static VALUE rb_inotify_add_watch(VALUE self, VALUE filename, VALUE mask) {
- OpenFile *fptr;
+#if RUBY_VERSION_CODE >= 190
+ rb_io_t *fptr;
+#else
+ OpenFile *fptr;
+#endif
int *fd, wd;
Data_Get_Struct(self, int, fd);
- if(wd = inotify_add_watch(*fd, RSTRING(filename)->ptr, NUM2INT(mask)) < 0) {
- rb_sys_fail(RSTRING(filename)->ptr);
+ if(wd = inotify_add_watch(*fd, RSTRING_PTR(filename), NUM2INT(mask)) < 0) {
+ rb_sys_fail(RSTRING_PTR(filename));
}
return INT2NUM(wd);
}
@@ -107,7 +112,11 @@
*/
static VALUE rb_inotify_each_event(VALUE self) {
- OpenFile *fptr;
+#if RUBY_VERSION_CODE >= 190
+ rb_io_t *fptr;
+#else
+ OpenFile *fptr;
+#endif
int *fd, r;
struct inotify_event *event, *pevent;
char buffer[16384];
--- End Message ---
--- Begin Message ---
Source: libinotify-ruby
Source-Version: 0.0.0-3
We believe that the bug you reported is fixed in the latest version of
libinotify-ruby, which is due to be installed in the Debian FTP archive:
libinotify-ruby1.8_0.0.0-3_i386.deb
to pool/main/libi/libinotify-ruby/libinotify-ruby1.8_0.0.0-3_i386.deb
libinotify-ruby1.9_0.0.0-3_i386.deb
to pool/main/libi/libinotify-ruby/libinotify-ruby1.9_0.0.0-3_i386.deb
libinotify-ruby_0.0.0-3.diff.gz
to pool/main/libi/libinotify-ruby/libinotify-ruby_0.0.0-3.diff.gz
libinotify-ruby_0.0.0-3.dsc
to pool/main/libi/libinotify-ruby/libinotify-ruby_0.0.0-3.dsc
libinotify-ruby_0.0.0-3_all.deb
to pool/main/libi/libinotify-ruby/libinotify-ruby_0.0.0-3_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Torsten Werner <[EMAIL PROTECTED]> (supplier of updated libinotify-ruby package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 4 Jun 2007 20:37:53 +0200
Source: libinotify-ruby
Binary: libinotify-ruby1.8 libinotify-ruby1.9 libinotify-ruby
Architecture: source all i386
Version: 0.0.0-3
Distribution: unstable
Urgency: low
Maintainer: Torsten Werner <[EMAIL PROTECTED]>
Changed-By: Torsten Werner <[EMAIL PROTECTED]>
Description:
libinotify-ruby - Ruby interface to Linux's inotify system
libinotify-ruby1.8 - Ruby interface to Linux's inotify system
libinotify-ruby1.9 - Ruby interface to Linux's inotify system
Closes: 427481
Changes:
libinotify-ruby (0.0.0-3) unstable; urgency=low
.
* Add patch ruby19.diff from Michael Ablassmeier. (Closes: #427481)
Files:
920a075be701c6e77215b4c8f0e0133c 863 libs optional libinotify-ruby_0.0.0-3.dsc
e7ed5f6da92db01d8dfb1daa5e5c96fa 3325 libs optional
libinotify-ruby_0.0.0-3.diff.gz
ade14b3a492d750d9548d36840bea4fe 2732 libs optional
libinotify-ruby_0.0.0-3_all.deb
115845468173f2da66314f149ca81503 6584 libs optional
libinotify-ruby1.8_0.0.0-3_i386.deb
8ee287176dd074883a684dfa07e4e09c 6638 libs optional
libinotify-ruby1.9_0.0.0-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGZF07fY3dicTPjsMRAsDiAKCCguDpl58FndW+CUJ4iL447fgdrwCfdIys
ZtID5EifAT1RGBcBQ4bOGQM=
=W76M
-----END PGP SIGNATURE-----
--- End Message ---
