=app-backup/btrbk-0.23.3 works fine on ARMv7a (Odroid-U2). Please keyword it. Reproducible: Always
https://github.com/gentoo/gentoo/pull/1915
(In reply to Andrius Štikonas from comment #0) > =app-backup/btrbk-0.23.3 works fine on ARMv7a (Odroid-U2). Please keyword it. > > Reproducible: Always Hi. Please provide a build log and CC me in to your response. (In reply to candrews from comment #1) > https://github.com/gentoo/gentoo/pull/1915 Thanks for the PR. You wrote: "I have not personally tested on these arches (is that okay? I'm not sure what the process is, so I'm making a best guess assumption here). I'm going by what the dependencies permit and upstream's claim." We have our own testing process for new arches. If you don't actually know the package in question does work on a given arch, don't add the keyword. I'm going to close your PR.
> I'm going by what the dependencies permit and upstream's claim. btrbk is designed to require as less dependencies as possible, and is supposed to work on every platform running a decent perl version, as well as >=sys-fs/btrfs-progs-3.18.2 (and of course openssh calls if remote backups are configured). I can only confirm it running on amd64 and x86 gentoo boxes. I know of people having it running on ARM, not sure if they use gentoo though.
Created attachment 441348 [details] build.log I'm attaching build log but clearly btrbk is ebuild satisfying property that if it builds on one arch it will build on all others provided perl builds and runs on those arches. (sometimes ALLARCHES keyword is used on Gentoo)
(In reply to Andrius Štikonas from comment #4) > Created attachment 441348 [details] > build.log > > I'm attaching build log but clearly btrbk is ebuild satisfying property that > if it builds on one arch it will build on all others provided perl builds > and runs on those arches. > > (sometimes ALLARCHES keyword is used on Gentoo) I agree. If the Perl interpreter work on these arches, the package in question should in theory work.. but you never know. ALLARCHES is a different keyword and is used in conjunction with stabilisation requests: a developer can stabilise a package on a single architecture and retroactively mark the ebuild stable for the remaining arches. For instance, I stabilise foo-1.0 for ~amd64 and if other arches are listed in KEYWORDS (~arm, ~x86, ~ppc, what have you), I can stabilise the package for those arches as well. ALLARCHES cannot be used for keyword requests (you never know until you try). Alright. So since you've built and installed btrbk on arm, I'm going to keyword this package for ~arm. If you wish to keyword it for other arches, reopen this bug and CC in the target arches. Cheers.
commit 8e8f3c3387401031836136bd9b20271d2dd75b73 (HEAD -> master, origin/master, origin/HEAD) Author: Patrice Clement <monsieurp@gentoo.org> AuthorDate: Fri Jul 22 17:16:03 2016 +0200 Commit: Patrice Clement <monsieurp@gentoo.org> CommitDate: Fri Jul 22 19:38:34 2016 +0200 app-backup/btrbk: Keyword for the arm platform. Courtesy of Andrius Štikonas <andrius@stikonas.eu>. Gentoo-Bug: https://bugs.gentoo.org/588854 Package-Manager: portage-2.2.28 app-backup/btrbk/btrbk-0.23.3.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Keyworded, thanks!
