Summary: | rofi-wayland fails to compile because meson_build_manpages.sh is not present. | ||
---|---|---|---|
Product: | GURU | Reporter: | Bartek Stalewski <ftpd+sites> |
Component: | Package issues | Assignee: | Rahul Sandhu <rahul> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | jfmfour22 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
buid log
emerge --info Updated ebuild |
Description
Bartek Stalewski
2023-02-13 12:33:34 UTC
Created attachment 850678 [details]
buid log
Created attachment 850680 [details]
emerge --info
Hmmmmm this is an interesting one as I can't reproduce it locally. Would you mind trying an ebuild for me in a bit? (In reply to Rahul Sandhu from comment #3) > Hmmmmm this is an interesting one as I can't reproduce it locally. Would you > mind trying an ebuild for me in a bit? I wonder if you can't reproduce because you have some package(s) providing the missing script installed, which is not marked in dependencies. Sure I can try your ebuild. (In reply to Rahul Sandhu from comment #3) > Hmmmmm this is an interesting one as I can't reproduce it locally. Would you > mind trying an ebuild for me in a bit? So, do you have anything for me to test? (In reply to hypersyd from comment #6) > https://www.reddit.com/r/linuxquestions/comments/xn6vm7/ > cant_buildinstall_rofi_wayland_fork_with_either/ This is the issue. Tested it. I have dev-go/go-md2man, but it's required for packages more important (for me!) than rofi - docker, runc and containerd. So I still think this ebuild should be fixed to deal with that, as I won't delete gomd2man. Created attachment 869560 [details] Updated ebuild This bug was fixed upstream: https://github.com/lbonn/rofi/pull/62/commits/006ae56291e543cf3f9dcd374213b65683db14dc This was included in the most recent release (1.7.5+wayland2), and the attached ebuild builds successfully (with go-md2man installed). One thing to note, however, is that the naming for this ebuild might need a revision bump. I'm not sure what naming convention to use here. I'd assume a revbump and some customization using something like MY_PN/MY_PV might work best. The current ebuild in guru is version 1.7.5+wayland1. |