Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 853199

Summary: zathura-pdf-mupdf-0.3.8-r1 failed in compile phase
Product: Gentoo Linux Reporter: Errelin <leon.errelin>
Component: Current packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: normal CC: flaviocamilo
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: build.log
emerge --info 'app-text/zathura-pdf-mupdf-0.3.8-r1::gentoo'

Description Errelin 2022-06-20 14:25:28 UTC
Created attachment 786473 [details]
build.log

It failed to build at almost the last step [10/11]:
ninja: build stopped: subcommand failed.

emerge -pqv '=app-text/zathura-pdf-mupdf-0.3.8-r1::gentoo'
[ebuild   R   ] app-text/zathura-pdf-mupdf-0.3.8-r1

Other info I've uploaded as attachments. Thank you for your help.
Comment 1 Errelin 2022-06-20 14:26:45 UTC
Created attachment 786476 [details]
emerge --info 'app-text/zathura-pdf-mupdf-0.3.8-r1::gentoo'
Comment 2 Another Mortal 2022-06-20 23:26:26 UTC
The issue appears to result from a new incompatible `mupdf` version.

Apparently, the dependency definition in the ebuild is wrong.

Zathura builds and works fine with 1.19.1, but fails with 1.20.0
despite the fact that the latter *also* matches `>=app-text/mupdf-1.19:=`.
Comment 3 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-06-20 23:28:58 UTC
(In reply to Another Mortal from comment #2)
> The issue appears to result from a new incompatible `mupdf` version.
> 
> Apparently, the dependency definition in the ebuild is wrong.
> 
> Zathura builds and works fine with 1.19.1, but fails with 1.20.0
> despite the fact that the latter *also* matches `>=app-text/mupdf-1.19:=`.

Well, yeah. Because it worked at the time and there wasn't a reason to believe it wouldn't work.

We don't tend to pre-emptively pin.
Comment 4 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-06-20 23:29:20 UTC

*** This bug has been marked as a duplicate of bug 853217 ***