Hi, the author has released version 2.0 and 2.1 some time ago, while 2.0 is considered stable. As far as I can tell, there's not much to do to upgrade the ebuild, I think the USE-flags "afs" and "tcpd" aren't needed anymore. I also think it would be worth having both 2.0.54 (latest stable) as well as 2.1.6 in Gentoo. One thing that might be good to point out at the end of the install process would be that the protocol 2 is not considered stable yet and may cause dataloss, so users should make sure to have "protocol = 1" in their server config. While burp currently only runs on little endian CPUs (x86, ARMs in LE mode like on the raspi), there's activity on the github tracker to have it work on big endian CPUs like PPC64 and SPARC in future versions. Thanks! Reproducible: Always
As luck would have it I wrote a working ebuild for 2.1.6 (which at a glance ought to work fine for 2.0.54 as well) just a week ago! I'll have to sit on it for bit longer though, until a related news item gets approved and submitted. The problem is, the patch we apply in existing ebuilds which changes the default config file used by bedup from burp.conf to burp-server.conf would be a pain to port to burp2, and simply dropping that patch could cause problems for anyone currently using bedup. In the meantime, I'll update the ebuild so that in addition to the warning you have suggested, the server config file defaults to protocol = 1.
commit 8262cee470aafbef23da9a6c618d5c4c45b7e8e6 Author: Marek Szuba Date: Thu Apr 20 09:33:27 2017 +0000 app-backup/burp: bump to 2.0.54 * * * As for the 2.1 line, in light of the fact it is considered unstable I'll hold it off for a while. Please open a separate version-bump bug for it if you think it should already be added, I reckon we will slot it then.
