<?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>67940</bug_id>
          
          <creation_ts>2004-10-17 14:49 0000</creation_ts>
          <short_desc>when emerging duplicity  &apos;gcc&apos; failed with exit status 1</short_desc>
          <delta_ts>2004-11-01 12:54:49 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>Applications</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>jk@pusspaws.net</reporter>
          <assigned_to>ticho@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>jk@pusspaws.net</who>
            <bug_when>2004-10-17 14:49:43 0000</bug_when>
            <thetext>Cant emerge duplicity, screens of errors centering around _librsyncmodule.c
copying src/tarfile.py -&gt; build/lib.linux-i686-2.3/duplicity
_librsyncmodule.c: In function `_librsync_new_patchmaker&apos;:
_librsyncmodule.c:322: error: `pm&apos; undeclared (first use in this function)
_librsyncmodule.c:334: error: syntax error before &apos;)&apos; token
&apos;&apos;&apos;until ...
_librsyncmodule.c: In function `init_librsync&apos;:
_librsyncmodule.c:467: error: `RS_DEFAULT_BLOCK_LEN&apos; undeclared (first use in this function)
error: command &apos;gcc&apos; failed with exit status 1
man:
there is no executable &apos;duplicity&apos;

Reproducible: Always
Steps to Reproduce:
1.emerge duplicity
2.
3.

Actual Results:  
failed to emerge as above

Expected Results:  
emerge duplicity

fresh emerge sync
everything normal</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>tigger@gentoo.org</who>
            <bug_when>2004-10-23 12:32:14 0000</bug_when>
            <thetext>I&apos;m afraid I don&apos;t wish to maintain this. Ticho seemed interested, throwing it to him...</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ticho@gentoo.org</who>
            <bug_when>2004-10-23 16:51:37 0000</bug_when>
            <thetext>I&apos;ll gladly take up maintainership for this package, it sure is useful.

Could you please post output of your `emerge --info` ?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ticho@gentoo.org</who>
            <bug_when>2004-10-23 16:52:40 0000</bug_when>
            <thetext>Also, what version of duplicity are you trying to install?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ticho@gentoo.org</who>
            <bug_when>2004-10-23 17:00:09 0000</bug_when>
            <thetext>Nevermind the version, I found out that it was duplicity-0.4.0 causing this. Can you try emerging duplicity-0.4.1 (~x86)? If you confirm it merges and works, I&apos;ll mark 0.4.1 as stable and remove 0.4.0 from portage tree.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ticho@gentoo.org</who>
            <bug_when>2004-10-23 17:24:26 0000</bug_when>
            <thetext>Looks like I need to hold back my mouse from the Submit button. I did some testing and found out that duplicity-0.4.0 only works with librsync-0.9.5.1 only, while 0.4.1 introduces fix that makes it work with librsync-0.9.5.1 and higher (including 0.9.6).

I have fixed both duplicity ebuilds accordingly, please let me know if this fixes the problem for you.

Also, I would like to know if duplicity-0.4.1 installs and works for you, so I can mark it stable.

Thanks for your time.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ticho@gentoo.org</who>
            <bug_when>2004-11-01 12:54:49 0000</bug_when>
            <thetext>Closing this, feel free to reopen if any problems spring up regarding this bug.
Thanks for reporting.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>