^~ insertionops.cc: In function ‘std::ostream& operator<<(std::ostream&, const ext2_inode&)’: insertionops.cc:36:36: error: ‘const struct ext2_inode’ has no member named ‘i_dir_acl’; did you mean ‘i_file_acl’? os << "Directory ACL: " << inode.i_dir_acl << std::endl; ^~~~~~~~~ i_file_acl ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-hardened_libressl_20180402-100611 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) [2] ruby23 (with Rubygems) * emerge -qpv sys-fs/extundelete [ebuild N ] sys-fs/extundelete-0.2.4
Created attachment 526698 [details] emerge-info.txt
Created attachment 526700 [details] emerge-history.txt
Created attachment 526702 [details] environment
Created attachment 526704 [details] etc.portage.tbz2
Created attachment 526706 [details] logs.tbz2
Created attachment 526708 [details] sys-fs:extundelete-0.2.4:20180405-215342.log
Created attachment 526710 [details] temp.tbz2
Based on this, I created an patch and PR: https://github.com/tytso/e2fsprogs/commit/578fcbfd2e61e0b13ce8c7b62804c941d6c1eb8e
It appears that "The "#define i_dir_acl i_size_high" was removed"[1]. The file compiles fine once de preprocessor definition is added. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894645
(In reply to Conrad Kostecki from comment #8) > Based on this, I created an patch and PR: > https://github.com/tytso/e2fsprogs/commit/ > 578fcbfd2e61e0b13ce8c7b62804c941d6c1eb8e Wrong link? I see your ticket here (the date seems to fit): https://sourceforge.net/p/extundelete/tickets/5/
(In reply to Ulrich Müller from comment #10) > (In reply to Conrad Kostecki from comment #8) > > Based on this, I created an patch and PR: > > https://github.com/tytso/e2fsprogs/commit/ > > 578fcbfd2e61e0b13ce8c7b62804c941d6c1eb8e > > Wrong link? I see your ticket here (the date seems to fit): > https://sourceforge.net/p/extundelete/tickets/5/ Sorry, didn't saw your comment :/ Pushed now a new PR.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=75bb550eb671ab4ef8479b8106c2d9e173da0b2d commit 75bb550eb671ab4ef8479b8106c2d9e173da0b2d Author: Conrad Kostecki <conrad@kostecki.com> AuthorDate: 2018-07-07 21:52:01 +0000 Commit: Tony Vroon <chainsaw@gentoo.org> CommitDate: 2018-07-11 10:53:21 +0000 sys-fs/extundelete: fix build with newer e2fsprogs version Closes: https://bugs.gentoo.org/652688 Package-Manager: Portage-2.3.41, Repoman-2.3.9 Closes: https://github.com/gentoo/gentoo/pull/9094 Closes: https://bugs.gentoo.org/652688 sys-fs/extundelete/extundelete-0.2.4.ebuild | 15 ++++++++------- .../extundelete/files/extundelete-0.2.4-e2fsprogs.patch | 11 +++++++++++ sys-fs/extundelete/metadata.xml | 15 ++++++++------- 3 files changed, 27 insertions(+), 14 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=75bb550eb671ab4ef8479b8106c2d9e173da0b2d commit 75bb550eb671ab4ef8479b8106c2d9e173da0b2d Author: Conrad Kostecki <conrad@kostecki.com> AuthorDate: 2018-07-07 21:52:01 +0000 Commit: Tony Vroon <chainsaw@gentoo.org> CommitDate: 2018-07-11 10:53:21 +0000 sys-fs/extundelete: fix build with newer e2fsprogs version Closes: https://bugs.gentoo.org/652688 Package-Manager: Portage-2.3.41, Repoman-2.3.9 Closes: https://github.com/gentoo/gentoo/pull/9094 Closes: https://bugs.gentoo.org/652688 sys-fs/extundelete/extundelete-0.2.4.ebuild | 15 ++++++++------- .../extundelete/files/extundelete-0.2.4-e2fsprogs.patch | 11 +++++++++++ sys-fs/extundelete/metadata.xml | 15 ++++++++------- 3 files changed, 27 insertions(+), 14 deletions(-)
