Bug#974947: dolfin: FTBFS against boost_1.74

[Drew Parsons]

Your 2019.2.0~git20200629.946dbd3-7 doesn't build either. I think the 
problem is the source upload, not the patch.

You've got
   boost::wrapexcept<boost::iostreams::gzip_error>

This happens when the test mesh files have not been pulled from git lfs.

You need to make sure it builds cleanly locally before uploading, you 
can't just upload a source.changes without that.

I don't know why the lfs files aren't being pulled automatically by git 
clone. git lfs sometimes seems to be more trouble than it's worth. And 
there's git trouble with demo/undocumented/elasticity/pulley.xdmf, which 
can't be registered in debian/source/include-binaries with the other lfs 
files.

Prepare source for build with

git clone <...source repo...>
git lfs pull
patch -p1 -R < debian/patches/git-lfs_fetch_demo_meshes


Drew



On 2020-11-18 18:01, Anton Gladky wrote:
> Hi Drew,
> 
> The patch works for both versions, so it
> shoe safely be applied by upstream.
> That is the reason why i decided to
> make this minimal team upload. But
> reverted it because of FTBFS.
> 
> Regards
> 
> Anton
> 
> Drew Parsons <dparsons at debian.org> schrieb am Mi., 18. Nov. 2020,
> 10:39:
> 
>> Source: dolfin
>> Followup-For: Bug #974947
>> 
>> Hi Anton, what would be helpful is if the patch can be configured to
>> build with either boost 1.71 or boost 1.74.
>> 
>> Upstream won't want to necessarily depend on boost 1.74, and a
>> common
>> multi-version patch will be helpful for them to manage with the
>> various boost versions. The patch can be pushed upstream if it does
>> that.
>> 
>> Drew
>> 
>> --
>> debian-science-maintainers mailing list
>> debian-science-maintainers at alioth-lists.debian.net
>> 
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers