-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ungoogled-chromium-bin/ungoogled-chromium-bin-84.0.4147.89_p1: neither the suid nor the convert-dict use flags work #38
Comments
Which use flags are you installing it with? Oh right, I've forgot to include this file. Wrt Please test, if this issue is fixed with the latest commit. |
Package-Manager: Portage-2.3.99, Repoman-2.3.23
I tried with "convert-dict -core2 -generic haswell suid widevine". I see that you have removed suid from IUSE, and updated the update-dicts path. But there is still a reference to suid, which might make portage complain.
And I'd guess you don't need pkg_setup() either then. |
Package-Manager: Portage-2.3.99, Repoman-2.3.23
And it indeed is important. As far as I understand, without
You're absolutely right, I should've had this done more carefully. |
Yeah, I mean that I would have thought that suid was a bit important. :) There is however another one, which I just mention in passing, as it's a bit complicated to solve in an easy and good-for-all way. It has to do with dependencies. I think that, in order for this binary to work well, the system the package is installed to somehow (bundled or forced by ebuild) needs to have the same versions of required libs that you had when you compiled the package. When I installed the package portage warned me of some referred libs not being on my system. |
#39 might be related |
I have established testing. Although this won't outright prevent such issues from happening, I do hope being able to catch them early on. BTW one issue with |
"./usr/lib64/chromium-browser/ungoogled-chromium-update-dicts.sh" does not exist. And neither does chrome_sandbox.
The text was updated successfully, but these errors were encountered: