Summary: | app-arch/xar-1.5.2-r2 : lib/ext2.c:142:17: error: ‘EXT2_ECOMPR_FL’ undeclared (first use in this function) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bircoph, chain, EoD, kkrizka, kripton, lssndrbarbieri, Martin.vGagern, proteuss, wfdawson |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/mackyle/xar/issues/10 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
app-arch:xar-1.5.2-r2:20160521-131827.log
emerge-history.txt environment ebuild with patch patch file to fix compile problem |
Description
Toralf Förster
2016-05-21 15:04:14 UTC
Created attachment 434864 [details]
app-arch:xar-1.5.2-r2:20160521-131827.log
Created attachment 434866 [details]
emerge-history.txt
Created attachment 434868 [details]
environment
Same problem with xar-1.6.1 Filed https://github.com/mackyle/xar/issues/10 after some investigation. patch from Void linux package as temporary workaround: https://github.com/voidlinux/void-packages/blob/master/srcpkgs/xar/patches/ext2.patch Created attachment 457424 [details]
ebuild with patch
Created attachment 457426 [details, diff] patch file to fix compile problem From https://github.com/voidlinux/void-packages/blob/master/srcpkgs/xar/patches/ext2.patch (In reply to romockee from comment #6) > patch from Void linux package as temporary workaround: > https://github.com/voidlinux/void-packages/blob/master/srcpkgs/xar/patches/ > ext2.patch Can compile and run with provided patch, thanks! do you want to proxy maintain this package? https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers @pacho, whom are you addressing? I just notcied that https://github.com/KubaKaszycki/xar has more recent activity than https://github.com/mackyle/xar, including a fix for the issue discussed here in https://github.com/KubaKaszycki/xar/commit/69cd5f215a. As both of these GitHub project describe themselves as clones or forks of some subversion ancestor, I'm not sure there is a reason to see one of them as more official than the other. Well... anybody willing to maintain the ebuild is welcome of course :) Personally, as I am not familiar with this package, I would opt for simply applying the patch and keeping the current "fork" we are using... but, if finally this is maintained by someone, he is free to decide on that sure :/ (In reply to Pacho Ramos from comment #12) > Well... anybody willing to maintain the ebuild is welcome of course :) > > Personally, as I am not familiar with this package, I would opt for simply > applying the patch and keeping the current "fork" we are using... but, if > finally this is maintained by someone, he is free to decide on that sure :/ Is there any reason for not having this patch in the Gentoo tree yet? It is kind of annoying to have a stable package which fails building. (In reply to EoD from comment #13) > (In reply to Pacho Ramos from comment #12) > > Well... anybody willing to maintain the ebuild is welcome of course :) > > > > Personally, as I am not familiar with this package, I would opt for simply > > applying the patch and keeping the current "fork" we are using... but, if > > finally this is maintained by someone, he is free to decide on that sure :/ > > Is there any reason for not having this patch in the Gentoo tree yet? It is > kind of annoying to have a stable package which fails building. +1 +one more... [master 711dd791a44] app-arch/xar: Fix building (#583668) 2 files changed, 64 insertions(+) create mode 100644 app-arch/xar/files/xar-1.6.1-ext2.patch create mode 100644 app-arch/xar/xar-1.6.1-r1.ebuild |