Luis Guzman
Luis Guzman
Well, seems like there is a bug in the jammy sdl2 version that may be causing the issue as even the bullseye one is working. So something there is weird....
Interesting, I'm using sbuild to build on a chroot, it looks similar but not quite. This is the error I get. ``` ... WARNING: Skipping non-existant path: //third_party/opus/src/doc/release.txt WARNING: Skipping...
Indeed, ``` CLANG_REVISION = 'llvmorg-17-init-8029-g27f27d15' CLANG_SUB_REVISION = 3 ``` to ``` CLANG_REVISION = 'llvmorg-17-init-857-g4f2fde78' CLANG_SUB_REVISION = 1 ``` at tools/clang/scripts/update.py That should get you pass that line. Regards.
Oh well, later on seems that we need a specific version otherwise it will fail. ``` [14976/54516] CXX obj/chrome/common/channel_info/channel_info.o FAILED: obj/chrome/common/channel_info/channel_info.o clang++-14 -MMD -MF obj/chrome/common/channel_info/channel_info.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD...
So far, no idea. I also would like to build for a jammy base, but 'til a developer give us some light on the matter, I'm just like everyone else...
@raphael10-collab based on the open PR #328 there is already a PPA with the latest version. * https://launchpad.net/~xtradeb/+archive/ubuntu/apps/ I've been testing it and it works and builds correctly, thanks to...
@jhonny-oliveira I was able to build using your PPA source in amd64, for ppc64el I added this [patch](https://gitlab.trisquel.org/Ark74/package-helpers/-/blob/82f172468cb40238f78068b4a3a7a218fdb5d292/helpers/DATA/ungoogled-chromium/disable_thin_lto_ppc64el.patch) and some [small changes](https://gitlab.trisquel.org/Ark74/package-helpers/-/blob/82f172468cb40238f78068b4a3a7a218fdb5d292/helpers/make-ungoogled-chromium) in our helper, it is still building. armhf...
@raphael10-collab dpkg-source -x works with tarballs and .dsc files, .deb are binaries, they don't have source in it, unless it's stated the binary contains the source, but that's not the...
@iskunk I did several testing, and I always hit the same error, something along the lines: ``` .... test -f ungoogled-domain-substitution.orig.tar \ || debian/ungoogled-domain-substitution.sh Creating backup archive ... Applying ungoogled-chromium...
@iskunk you are right, removing `current_cpu != "ppc64"` does pass the initial error on ppc64el, there are some hours ahead to confirm build, hopefully it will pass. arm64/hf didn't show...