I have installed app-backup/bareos and app-arch/lz4. Configure bareos to use LZ4 in file set options. When i try to start job, i get this: 11-Sep 23:10 newweb2-fd JobId 5: Fatal error: LZ4 compression not supported on this platform 11-Sep 23:10 backup-sd JobId 5: Fatal error: append.c:156 Error reading data header from FD. ERR=No data available
I will need to package https://github.com/bareos/fastlzlib for LZ4 support, which currently has not releases. I will see what I can do. Thanks for reporting!
We just need ebuild from specific revision of FastLZ as it do with app-arch/lz4. If you don`t want to waste time for write ebuild, i can do bug report for request ebuild for FastLZ. LZ4 support in bareos is would be killer feature. Also, may be you will add ebuld for bareos-14.2 and mask it for testing purposes?
fastlzlib is already in my queue. No ETA yet, but should be added shortly. Stay tuned! (I and i will propably bump bareos as well then)
Please test bareos-13.2.3-r1 with USE=fastlz and repoen if not working for you. And thanks for reporting!
I think you did it wrong way. I get this error: backup fvl # emerge -pv bareos These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild N ] dev-libs/bareos-fastlzlib-0_pre20140912 371 KiB [ebuild U ] app-backup/bareos-13.2.3-r1 [13.2.3] USE="acl director fastlz%* ipv6 logwatch mysql ndmp postgres readline sql-pooling ssl storage-daemon tcpd vim-syntax -X -clientonly -python -qt4 -scsi-crypto -sqlite3 -static" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 0 KiB [blocks B ] app-arch/lz4 ("app-arch/lz4" is blocking dev-libs/bareos-fastlzlib-0_pre20140912) Total: 2 packages (1 upgrade, 1 new), Size of downloads: 371 KiB Conflict: 1 block (1 unsatisfied) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (dev-libs/bareos-fastlzlib-0_pre20140912:0/0::gentoo, ebuild scheduled for merge) pulled in by dev-libs/bareos-fastlzlib required by (app-backup/bareos-13.2.3-r1:0/0::gentoo, ebuild scheduled for merge) (app-arch/lz4-0_p120:0/0::gentoo, installed) pulled in by app-arch/lz4 required by @selected For more information about Blocked Packages, please refer to the following section of the Gentoo Linux x86 Handbook (architecture is irrelevant): http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked As i see dev-libs/bareos-fastlzlib ebuild, you create it from https://github.com/bareos/fastlzlib. But if look deeply, you can see that bareos fastzlib is from two component merged into bareos/fastlzlib branch: 1. http://code.google.com/p/fastlz/ 2. https://code.google.com/p/lz4/ lz4 already in portage(but not latest available version). So i think, we just need to write ebuild app-arch/fastlz that would depend on app-arch/lz4 I want to discuss about my opinion =)
I forget to write about https://github.com/exalead/fastlzlib This is original source used by bareos
I asked bareos upstream and they told that they patched those sources to work fine with bareos so I did not want to use the original source on purpose. Hence the name "bareos-fastlzlib". I think ideal solution would be if bareos upstream could use upstream sources as they are but this is not the case right now. So it should work for you if you unmerge app-arch/lz4. I agree that it would be better to use external app-arch/lz4, but then we would have to remove it from bareos-fastlzlib package after app-arch/lz4 has been bumped to the required version.
What parts they are modified? Fastlz and/or lz4? Could you post a link to the thread where did you asks?
Please see: https://groups.google.com/forum/#!topic/bareos-devel/dwoaueP_LxQ
I think we can close thi, right?
