Re: [gentoo-user] Several packages failing to build

[Elijah Mark Anderson]

On Monday, May 14, 2018 4:53:09 PM CDT Mick wrote:
> On Monday, 14 May 2018 21:07:17 BST Elijah Mark Anderson wrote:
> > On Monday, May 14, 2018 12:58:13 PM CDT Mick wrote:
> > > On Monday, 14 May 2018 18:20:01 BST Elijah Mark Anderson wrote:
> > > > I'm having an issue with about a dozen packages not upgrading. I'd
> > > > really
> > > > appreciate some help getting them to build and install. I'm getting
> > > > the
> > > > feeling that the problems are somehow related, but really not sure.
> > > >
> > > > First up: dev-libs/appstream-0.11.5::gentoo
> > > > Anyone know what's going on here? This package is blocking at least 5
> > > > other
> > > > packages from upgrading, and I find the information in the logs only
> > > > slightly more helpful than WIndows "Something went wrong" errors.
> > >
> > > It's worth checking in BGO to see if your problems with ~amd64 packages
> > > are
> > > already reported and if any patches/fixes/workarounds have been posted.
> > > In
> > > this case have a look here, I think it is the same problem you have
> > > experienced:
> > >
> > > https://bugs.gentoo.org/640916
> > >
> > > --
> > > Regards,
> > > Mick
> >
> > I did come across that. I don't believe it is the same problem. For them,
> > the problem is during the install phase. Mine is occurring in compile
> > phase.
>
> Fair enough, I did not dig into it at any depth.  Without knowing the real
> cause of this failure and if nothing else resolves it, I would try to
> rebuild gettext & perhaps libxml2:
>
> emerge -1aDv sys-devel/gettext dev-libs/libxml2
>
> then try emerging dev-libs/appstream once more.  Running ~arch involves more
> troubleshooting and experimenting than I have time at present, hence I
> stick with stable where I can.
>
> --
> Regards,
> Mick

I tried as you suggested, to no avail. But, I *finally* found the actual error 
in the build log. I had forgotten that I was running emerge with MAKEOPTS="-
j9", which means that errors are not always at the bottom of the log. When I 
remembered it, I searched the log for "error[: ]", and bingo! Here's the 
relevant entry:

[39/106] /usr/bin/python3.5 /usr/lib/python-exec/python3.5/meson --internal 
msgfmthelper ../appstream-APPSTREAM_0_11_5/data/
org.freedesktop.appstream.cli.metainfo.xml data/
org.freedesktop.appstream.cli.metainfo.xml xml /var/tmp/portage/dev-libs/
appstream-0.11.5/work/appstream-APPSTREAM_0_11_5/po --datadirs=/var/tmp/
portage/dev-libs/appstream-0.11.5/work/appstream-APPSTREAM_0_11_5/data/
FAILED: data/org.freedesktop.appstream.cli.metainfo.xml 
/usr/bin/python3.5 /usr/lib/python-exec/python3.5/meson --internal 
msgfmthelper ../appstream-APPSTREAM_0_11_5/data/
org.freedesktop.appstream.cli.metainfo.xml data/
org.freedesktop.appstream.cli.metainfo.xml xml /var/tmp/portage/dev-libs/
appstream-0.11.5/work/appstream-APPSTREAM_0_11_5/po --datadirs=/var/tmp/
portage/dev-libs/appstream-0.11.5/work/appstream-APPSTREAM_0_11_5/data/
msgfmt: error while opening "/var/tmp/portage/dev-libs/appstream-0.11.5/work/
appstream-APPSTREAM_0_11_5/po/zh_TW.po/nja.po/npt_BR.po/nsr@×××××.po/ncs.po/
ngd.po/nfi.po/nid.po/nlt.po/nen_GB.po/nzh_CN.po/nuk.po/nckb.po/nar.po/nnl.po/
nru.po/nko.po/nda.po/nsr.po/nfr.po/nhu.po/npt.po/nit.po/nsv.po/nca.po/nes.po/
nde.po/nsl.po/noc.po/ngl.po/npl.po/ntr.po/nsk.po/neu.po" for reading: Not a 
directory

Looks like you were right after all, as https://bugs.gentoo.org/640916#c7 is 
indeed a pretty dang close match. Looks like a bug in the package itself. I'll 
mask this version, as #c13 claims this is fixed in 0.11.8. Hopefully that'll be 
in the tree soon™.
-- 
Elijah Mark Anderson
mark@××××××.name
--
「塵も積もれば山となる。」
"Even dust, when piled up, becomes a mountain" - Ancient Japanese proverb