Skip to content
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

Chromium manifest is incorrectly installing Ungoogled Chromium #3473

Closed
ghost opened this issue Jan 9, 2020 · 3 comments
Closed

Chromium manifest is incorrectly installing Ungoogled Chromium #3473

ghost opened this issue Jan 9, 2020 · 3 comments
Labels
package update Request for updating an app

Comments

@ghost
Copy link

ghost commented Jan 9, 2020

The Scoop manifest for Chromium is incorrectly installing Ungoogled Chromium.
This has been the case for the last 2 revisions.

Please edit the manifest to the correct installation as this change has resulted in the browser crashing on startup when updated.

@linsui linsui mentioned this issue Jan 11, 2020
@andselisk
Copy link

The issue is still there. scoop install chromium installs Ungoogled Chromium. There are two separate packages, ungoogled-chromium and chromium, but according to the manifest one can only install Ungoogled Chromium. This behavior makes no sense.

@ghost
Copy link
Author

ghost commented Jun 16, 2020

I just made a custom bucket pointing to the correct installation. There are instructions in the Scoop documentation on how to set this up.

chromium-hibbiki.json.txt

@stale
Copy link

stale bot commented Oct 27, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 27, 2021
@HUMORCE HUMORCE added package update Request for updating an app and removed stale labels Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package update Request for updating an app
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants