Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#18470 - [encfs] Failures with latest boost

Attached to Project: Community Packages
Opened by Matthew Gyurgyik (pyther) - Friday, 26 February 2010, 03:39 GMT
Last edited by Allan McRae (Allan) - Saturday, 20 March 2010, 12:18 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dan Griffiths (Ghost1227)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 16
Private No


[somebody@tux ~]$ encfsctl export ~/.abc/ abc/
22:34:31 (FileUtils.cpp:375) Archive exception: stream error
22:34:31 (FileUtils.cpp:326) Found config file /home/somebody/.abc/.encfs6.xml, but failed to load
Unable to initialize encrypted filesystem - check path.

Additional info:"> - Seems to be related to boost

Pacman Log:
[2010-02-23 09:55] upgraded boost (1.41.0-2 -> 1.42.0-1)

This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 20 March 2010, 12:18 GMT
Reason for closing:  Fixed
Comment by Matthew Gyurgyik (pyther) - Friday, 26 February 2010, 03:46 GMT
Same happens with encfs ~/.abc ~/abc
Comment by Matthew Gyurgyik (pyther) - Friday, 26 February 2010, 03:47 GMT Comment by Christer Sjöholm (hcs) - Tuesday, 09 March 2010, 09:40 GMT
According to upstream: encfs requires boost <= 1.41,
see comment 24 in upstreams issue.
Comment by David Rosenstrauch (darose) - Tuesday, 09 March 2010, 18:03 GMT
Downgrading to boost 1.41, and then recompiling encfs against it, seems to fix this.
Comment by Petar Bogdanovic (pebo) - Wednesday, 17 March 2010, 15:07 GMT
> What distribution are you using? A ticket needs to be filed with that distribution
> that they should *not* upgrade to boost-1.42, as it can cause silent data lose for
> programs using boost serialization.

Any thoughts on reviving boost 1.41 and skipping 1.42? Seems reasonable to me..
Comment by Ionut Biru (wonder) - Thursday, 18 March 2010, 09:24 GMT
@pebo i think that will be to last resort and i won't happen. we can backport from svn the fix and add to our current package when is fixed upstream.
Comment by Petar Bogdanovic (pebo) - Thursday, 18 March 2010, 09:32 GMT
As you said, there is no fix yet and the longer you keep 1.42 in the
repo the longer you're accepting the risk of other users being burned
by the very probable data loss described in the mentioned bug report.
Comment by Matthew Gyurgyik (pyther) - Thursday, 18 March 2010, 12:40 GMT
Downgrading to boost 1.41 because of 1 package is plain nuts! Although it does stink that encfs doesn't work with the new version of boost, we shouldn't hold boost back becasue of one package.
Comment by Petar Bogdanovic (pebo) - Thursday, 18 March 2010, 13:01 GMT
Read the boost bug report and then read it again. It has nothing to do
with encfs, it affects every package that uses boost for serialization.

encfs just happened to be first and in my case the circumstances nearly
turned the content of my whole home directory into a big pile of
encrypted garbage. Which makes it pretty clear that the implications of
that particular bug are unclear at best.
Comment by Ionut Biru (wonder) - Friday, 19 March 2010, 13:56 GMT
whats the status on this? now can be closed as we downgraded boost to 1.41?
Comment by Petar Bogdanovic (pebo) - Friday, 19 March 2010, 15:06 GMT
I'll check both packages as soon as I come back
home which will be rather tomorrow than today.

Thanks for your work.
Comment by Petar Bogdanovic (pebo) - Saturday, 20 March 2010, 11:35 GMT
It's all good again, please close.