<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>198544</bug_id>
          
          <creation_ts>2007-11-09 10:27 0000</creation_ts>
          <short_desc>stabilize sys-fs/inotify-tools</short_desc>
          <delta_ts>2007-11-25 03:22:53 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>2006.1</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <keywords>STABLEREQ</keywords>
          <priority>P2</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>bugzilla-gentoo@bwurst.org</reporter>
          <assigned_to>wschlich@gentoo.org</assigned_to>
          <cc>hanno@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>bugzilla-gentoo@bwurst.org</who>
            <bug_when>2007-11-09 10:27:43 0000</bug_when>
            <thetext>No stable version available at the moment on amd64.

I installed sys-fs/inotify-tools-3.11 and have no problems.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>hanno@gentoo.org</who>
            <bug_when>2007-11-11 14:31:44 0000</bug_when>
            <thetext>cc-ing archs</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cla@gentoo.org</who>
            <bug_when>2007-11-11 16:18:56 0000</bug_when>
            <thetext>On x86 it fails on make check

make[5]: Entering directory `/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11&apos;
make[5]: Leaving directory `/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11&apos;
event_to_str: test begin
event_to_str: test end
event_to_str_sep: test begin
event_to_str_sep: test end
str_to_event: test begin
str_to_event: test end
str_to_event_sep: test begin
str_to_event_sep: test end
basic_watch_info: test begin
basic_watch_info: test end
watch_limit: test begin
watch_limit: Warning, this test may take a while
test.c:271 Test &apos;watch_limit&apos; failed: Actual (sbrk(0)): 136425472, Expected (sbrk_ptr): 136384512
tst_inotifytools_snprintf: test begin
tst_inotifytools_snprintf: test end
Out of 145208 tests, 145207 succeeded and 1 failed.
FAIL: test
=====================================
1 of 1 tests failed
Please report to rohan@mcgovern.id.au
=====================================
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11/libinotifytools/src&apos;
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11/libinotifytools/src&apos;
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11/libinotifytools/src&apos;
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11/libinotifytools&apos;
make: *** [check-recursive] Error 1

!!! ERROR in sys-fs/inotify-tools-3.11:
!!! In src_test at line 29
!!! make check failed


Paludis build information:
    Compiler:
        CXX:                   i686-pc-linux-gnu-g++ 4.1.2 (Gentoo 4.1.2)
        CXXFLAGS:              -O2 -march=pentium-m -fomit-frame-pointer -pipe
        LDFLAGS:               
        DATE:                  2007-11-06T15:48:32+0100

Package information:
        app-admin/eselect-compiler: (none)
        app-shells/bash:       3.2_p17
        dev-java/java-config:  1.3.7, 2.0.33-r1
        dev-lang/python:       2.4.4-r6
        dev-python/pycrypto:   2.0.1-r6
        dev-util/ccache:       (none)
        dev-util/confcache:    (none)
        sys-apps/baselayout:   1.12.9-r2
        sys-apps/sandbox:      1.2.18.1-r2
        sys-devel/autoconf:    2.13, 2.61-r1
        sys-devel/automake:    1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
        sys-devel/binutils:    2.18-r1
        sys-devel/gcc-config:  1.3.16
        sys-devel/libtool:     1.5.24
        virtual/os-headers:    2.6.22-r2</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ssuominen@gentoo.org</who>
            <bug_when>2007-11-11 17:43:26 0000</bug_when>
            <thetext>same for amd64, fails at make check,

test.c:271 Test &apos;watch_limit&apos; failed: Actual (sbrk(0)): 8781824, Expected (sbrk_ptr): 8757248</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ssuominen@gentoo.org</who>
            <bug_when>2007-11-12 23:17:18 0000</bug_when>
            <thetext>(In reply to comment #1)
&gt; cc-ing archs
&gt; 

un-cc-ing amd64, add us back when it&apos;s fixed</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>fauli@gentoo.org</who>
            <bug_when>2007-11-18 11:02:09 0000</bug_when>
            <thetext>Wolfram, could you please look into the failures?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wschlich@gentoo.org</who>
            <bug_when>2007-11-18 22:57:26 0000</bug_when>
            <thetext>I have tried to contact Rohan, will let you know when I got his attention ;)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wschlich@gentoo.org</who>
            <bug_when>2007-11-18 23:22:33 0000</bug_when>
            <thetext>Wow, that was quicker than I hoped ;)
He will take care about it next weekend (maybe earlier).
Will keep you up2date.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wschlich@gentoo.org</who>
            <bug_when>2007-11-24 01:58:29 0000</bug_when>
            <thetext>--8&lt;--
24 November 2007: inotify-tools 3.12 released. Changes:
* Fix: inability to free memory allocated by inotifytools, and bogus memory
  leak check (causing `make check&apos; to fail on some systems).
* Fix: spurious warning when the `--format&apos; option is given to inotifywait.
* Fix: inotifywait fails to watch newly created directories when recursively
  watching a symlink to a directory.
--8&lt;--

3.12 is in CVS.

So, either you ignore the &quot;make check&quot; results, or you wait until you can
consider 3.12 for stable marking :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ssuominen@gentoo.org</who>
            <bug_when>2007-11-24 09:25:52 0000</bug_when>
            <thetext>amd64 stable

But.. entire src_compile() should be removed since it only does econf, emake without arguments?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wschlich@gentoo.org</who>
            <bug_when>2007-11-24 12:16:17 0000</bug_when>
            <thetext>(In reply to comment #9)
&gt; amd64 stable
&gt; 
&gt; But.. entire src_compile() should be removed since it only does econf, emake
&gt; without arguments?

Yep, you&apos;re right.
Either I can do it, or x86 can do it when they touch the ebuild anyway ;)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cla@gentoo.org</who>
            <bug_when>2007-11-25 03:22:53 0000</bug_when>
            <thetext>x86 stable, so closing</thetext>
          </long_desc>
      
    </bug>

</bugzilla>