Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 67940
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Andrej Kacian (RETIRED) <ticho@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Dave S <jk@pusspaws.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 67940 depends on: Show dependency tree
Bug 67940 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-10-17 14:49 0000 
Cant emerge duplicity, screens of errors centering around _librsyncmodule.c
copying src/tarfile.py -> build/lib.linux-i686-2.3/duplicity
_librsyncmodule.c: In function `_librsync_new_patchmaker':
_librsyncmodule.c:322: error: `pm' undeclared (first use in this function)
_librsyncmodule.c:334: error: syntax error before ')' token
'''until ...
_librsyncmodule.c: In function `init_librsync':
_librsyncmodule.c:467: error: `RS_DEFAULT_BLOCK_LEN' undeclared (first use in this function)
error: command 'gcc' failed with exit status 1
man:
there is no executable 'duplicity'

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

------- Comment #1 From rob holland (RETIRED) 2004-10-23 12:32:14 0000 ------- 
I'm afraid I don't wish to maintain this. Ticho seemed interested, throwing it
to him...

------- Comment #2 From Andrej Kacian (RETIRED) 2004-10-23 16:51:37 0000 ------- 
I'll gladly take up maintainership for this package, it sure is useful.

Could you please post output of your `emerge --info` ?

------- Comment #3 From Andrej Kacian (RETIRED) 2004-10-23 16:52:40 0000 ------- 
Also, what version of duplicity are you trying to install?

------- Comment #4 From Andrej Kacian (RETIRED) 2004-10-23 17:00:09 0000 ------- 
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'll mark 0.4.1 as stable and remove 0.4.0 from portage tree.

------- Comment #5 From Andrej Kacian (RETIRED) 2004-10-23 17:24:26 0000 ------- 
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.

------- Comment #6 From Andrej Kacian (RETIRED) 2004-11-01 12:54:49 0000 ------- 
Closing this, feel free to reopen if any problems spring up regarding this bug.
Thanks for reporting.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug