chromium-wayland-vaapi-next
No description set
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:zhmars:arch/chromium-wayland-vaapi-next && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
0001-adjust-buffer-format-order.patch | 0000002484 2.43 KB | |
0001-enable-linux-unstable-deb-target.patch | 0000001009 1009 Bytes | |
0001-ozone-wayland-implement-text_input_manager-fi |
0000001877 1.83 KB | |
0001-ozone-wayland-implement-text_input_manager_v3 |
0000022116 21.6 KB | |
0001-vaapi-flag-ozone-wayland.patch | 0000000770 770 Bytes | |
PKGBUILD | 0000012270 12 KB | |
REVERT-disable-autoupgrading-debug-info.patch | 0000002121 2.07 KB | |
_constraints | 0000000440 440 Bytes | |
_service | 0000001389 1.36 KB | |
_service:download_url:chromium-119.0.6045.59.tar.x |
3292462336 3.07 GB | |
_service:download_url:chromium-launcher-8.tar.gz | 0000004725 4.61 KB | |
_service:download_url:chromium-patches-119.tar.bz2 | 0000007630 7.45 KB | |
fetch-chromium-release | 0000001433 1.4 KB | |
use-oauth2-client-switches-as-default.patch | 0000001085 1.06 KB |
Latest Revision
mars zhou (zhmars)
committed
(revision 13)
up
Comments 2
Hello,
If you don't mind, can you take a look on my chromium package why it asked for sudo there thus caused the build to fail: https://build.opensuse.org/package/live_build_log/home:nhandt64:tsuki-bakery/chromium-qtmlabs/Arch/x86_64
Here is the package on GitHub for your convenience: https://github.com/Tsuki-Bakery/chromium-qtmlabs.
Many thanks!
Hello, I took a look on your PKGBUILD and compared against the one on AUR. So I have to declare all build dependencies before prepare() so I'm giving it a try on mine.
Update: it works, but then bsdtar couldn't untar the source code tarball due to (maybe) worker VMs using locale that is under different from UTF-8. Please check the build log from the URL in the comment above. I have looked through all of your project/repository settings and
diff
ed between the two of our PKGBUILD files but nothing more could be done to resolve this issue nor OBS docs provide any good help.This is by far the worst service I have worked with.