librsync 0.9.5 contains memory leaks which cause it to use an amount of RAM about equal to the size of the data being rsync'd. librsync-0.9.5.1 fixes this bug, and the existing ebuild need only be renamed for it to work properly with librsync-0.9.5.1. Recommend removing 0.9.5 from portage tree as unless you've got lots of ram or a big swap space, the leak will lockup your system. Reproducible: Always Steps to Reproduce:
sorry i dont see any 0.9.5.1 file on the homepage
Sorry, it is available at http://rdiff-backup.stanford.edu/librsync-0.9.5.1.tar.gz (you'll need to change SRC_URI in the ebuild). I got that link from rdiff-backup's website, http://rdiff-backup.stanford.edu/. I'm not sure why the librsync homepage doesn't list it, I could have sworn it did. I apologize for the confusion.
There seems to be some confusion with the various websites. The rproxy webpage, that is also referenced as HOMEPAGE in the librsync-0.9.5.ebuild (http://sourceforge.net/projects/rproxy/) denotes 0.9.5 as the newest version. But there is also a news item (dating from Feb, 27 2003, that says, that librsync has now its own webpage: http://librsync.sourceforge.net/ Also on this webpage 0.9.5 seems to be the newest version. But the webpage for rdiff-backup (http://rdiff-backup.stanford.edu) , a wonderfull backup utility, points to an updated librsync-0.9.5.1, that fixes a memory leak present in 0.9.5. According to the rdiff-backup webpage, rdiff-backup requires librsync-0.9.5.1. But librsync-0.9.5.1 is neither in the portage tree, nor does the rdiff-backup ebuild mention the correct dependency, which is librsync-0.9.5.1. Greping for librsync in /usr/portage revealed, that rdiff-backup is the _only_ ebuild that relies on librsync. So I would suggest, that we should include librsync-0.9.5.1 from the rdiff-backup website.
in cvs
