Bug#890721: flatpak: FTBFS with glibc 2.27: error: static declaration of 'copy_file_range' follows non-static declaration

2018-02-19 Thread Simon McVittie
Version: 0.11.3-1 On Mon, 19 Feb 2018 at 09:53:14 +, Simon McVittie wrote: > flatpak 0.11.0 has the upstream fix that you described, so this is > certainly fixed in experimental. Just to make sure, I built the version I'm about to upload against glibc 2.27 and it seems fine. I'll do the same

Bug#890721: flatpak: FTBFS with glibc 2.27: error: static declaration of 'copy_file_range' follows non-static declaration

2018-02-19 Thread Simon McVittie
Control: tags -1 + confirmed moreinfo On Sat, 17 Feb 2018 at 23:57:48 +0100, Aurelien Jarno wrote: > flatpak 0.10.3-1 (and version 0.10.4-1 currently in sid) fails to build > with glibc 2.27 (2.27-0experimental0 from experimental) Did you test 0.10.4-1 unsuccessfully, or is that based on extrapol

Bug#890721: flatpak: FTBFS with glibc 2.27: error: static declaration of 'copy_file_range' follows non-static declaration

2018-02-17 Thread Simon McVittie
Control: tags -1 + fixed-upstream On Sat, 17 Feb 2018 at 23:57:48 +0100, Aurelien Jarno wrote: > flatpak 0.10.3-1 (and version 0.10.4-1 currently in sid) fails to build > with glibc 2.27 (2.27-0experimental0 from experimental) ... > The issue has already been fixed upstream in commit 3e16d4ef with

Bug#890721: flatpak: FTBFS with glibc 2.27: error: static declaration of 'copy_file_range' follows non-static declaration

2018-02-17 Thread Aurelien Jarno
Package: flatpak Version: 0.10.3-1 Severity: important Tags: upstream User: debian-gl...@lists.debian.org Usertags: 2.27 flatpak 0.10.3-1 (and version 0.10.4-1 currently in sid) fails to build with glibc 2.27 (2.27-0experimental0 from experimental): | libtool: compile: gcc -DHAVE_CONFIG_H -I. -D