$summary
Created attachment 526218 [details] build.log build.log
Created attachment 526220 [details] emerge.info emerge.info
builds fails. please cc arches when fixed.
(In reply to Aaron Bauman from comment #3) > builds fails. please cc arches when fixed. Please, do not act this way. -when something fails please open a new bug and make the bug block the bug you found problem in. -please use safe cflags for testing, these ones do not look sufficient -please test your package and re-test it again to make sure your input is valid, do not take any action on CC until you are totally sure that the bug is valid -please check packages for regressions
(In reply to Mikle Kolyada from comment #4) > (In reply to Aaron Bauman from comment #3) > > builds fails. please cc arches when fixed. > > Please, do not act this way. > > -when something fails please open a new bug and make the bug block the bug > you found problem in. > I could understand this if it were a minor test failure or something non-fatal. > -please use safe cflags for testing, these ones do not look sufficient > Ugh, what? Did you look at them? > -please test your package and re-test it again to make sure your input is > valid, do not take any action on CC until you are totally sure that the bug > is valid > What makes you think I didn't? > -please check packages for regressions It's obviously a regression as older versions are marked stable. I wasn't rude, condescending, or negative. It fails to build. Simple as that.
(In reply to Aaron Bauman from comment #5) > (In reply to Mikle Kolyada from comment #4) > > (In reply to Aaron Bauman from comment #3) > > > builds fails. please cc arches when fixed. > > > > Please, do not act this way. > > > > -when something fails please open a new bug and make the bug block the bug > > you found problem in. > > > > I could understand this if it were a minor test failure or something > non-fatal. No, a STABLEREQ bug remains STABLEREQ, the rest of the party goes to the depending bugs, STABLEREQ keeps as least additional info as possible. > > > -please use safe cflags for testing, these ones do not look sufficient > > > > Ugh, what? Did you look at them? Yes, and still likely to add say -frecord-gcc-switches as mandatory. > > > -please test your package and re-test it again to make sure your input is > > valid, do not take any action on CC until you are totally sure that the bug > > is valid > > > > What makes you think I didn't? just general recommendation, no more. > > > -please check packages for regressions > > It's obviously a regression as older versions are marked stable. It works for me pretty well, in the safe stable env, so let me politely doubt it. > > I wasn't rude, condescending, or negative. Me either :) > It fails to build. Simple as > that.
After further review, I forgot to attach the use flag combinations. It looks like the build is only failing when USE='-ssl' or tests are run (which depend on OpenSSL). Hope that helps.
x86 stable
Contacted upstream regarding build issue with -ssl (aka "--disable-md5").
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3dfe4046dcdb2b26540d737f5bf1405d0e097cef commit 3dfe4046dcdb2b26540d737f5bf1405d0e097cef Author: Aaron Bauman <bman@gentoo.org> AuthorDate: 2018-04-14 19:07:17 +0000 Commit: Aaron Bauman <bman@gentoo.org> CommitDate: 2018-04-14 19:07:59 +0000 sys-block/mbuffer: amd64 stable Bug: https://bugs.gentoo.org/651680 Package-Manager: Portage-2.3.28, Repoman-2.3.9 sys-block/mbuffer/mbuffer-20171011.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)}
ppc Unable to build with USE="-ssl" (bug #653680) and fails tests (bug #653682).
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7c5ea7a9d9e70960e2356d976f644b367e50a055 commit 7c5ea7a9d9e70960e2356d976f644b367e50a055 Author: Sergei Trofimovich <slyfox@gentoo.org> AuthorDate: 2018-06-24 17:28:41 +0000 Commit: Sergei Trofimovich <slyfox@gentoo.org> CommitDate: 2018-06-24 19:35:11 +0000 sys-block/mbuffer: stable 20171011 for ppc, bug #651680 Bug: https://bugs.gentoo.org/651680 Package-Manager: Portage-2.3.40, Repoman-2.3.9 RepoMan-Options: --include-arches="ppc" sys-block/mbuffer/mbuffer-20171011.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Last arch is done. Closing.
