Thanks, I'll check it out.
On Mon, Aug 22, 2022 at 9:50 AM Olivier Tilloy <1987...@bugs.launchpad.net>
wrote:
> This upstream bug seems relevant:
> https://bugs.chromium.org/p/chromium/issues/detail?id=1340181
>
> --
> You received this bug notification because you are subscribed to the bug
> rep
OK, I'll take a look at that when time permits.
On Mon, Aug 22, 2022 at 8:36 AM Nathan Teodosio <1987...@bugs.launchpad.net>
wrote:
> > Can I adjust snapcraft.yaml to override 1.20.0 and specifically
> request 1.18.0?
>
> We used override-build to get newer versions of Libva:
> https://git.launch
Well, yes, that would be the problem. What would be the for-the-moment
hacky workaround (if any)? Can I adjust snapcraft.yaml to override 1.20.0
and specifically request 1.18.0? Or maybe I can check if there is a
development version of chromium that has already moved up to 1.20.0. This
is not a hig
** Description changed:
Following on an earlier bug report that related to simple core22
migration for chromium-browser, here is a blocker that I don't know how
to deal with.
After checking out the core22 branch from
git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (w
Public bug reported:
Following on an earlier bug report that related to simple core22
migration for chromium-browser, here is a blocker that I don't know how
to deal with.
After checking out the core22 branch from
git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which
already co
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986922
Title:
snapcraft build fails on second run as "l
Ok, thanks.
On Fri, Aug 19, 2022 at 8:10 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:
> > Perhaps one should create a core 22 branch where I can submit my
> changes.
>
> I think that is only possible with a team. See if you can push to
> https://code.launchpad.net/~chromium-core22/+git/
My interest in this is that I'm stress testing migrating snaps to core
22/snapcraft 7 as part of the update for the Snapcraft 101 course, and when
I asked my team for an example of a snap that would be challenging to
migrate, one of them immediately suggested chromium, so that's why I'm
working on
Last comment for the day ... from what little I've seen, it seems like it
might require defining a lengthy list of packages relative to 22.04 to
migrate this snap to 22.04. Or maybe I'm misreading it. In any event, I'd
still like to make this happen.
On Thu, Aug 18, 2022 at 3:56 PM Robert Day
wro
Actually, another part of my grep search produced the following, which
seems to suggest that an older version of libwayland-client0 is being used:
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el:
https://snapshot.debian.org/archive/debian/20220331T153654Z
A comprehensive grep includes the lines:
parts/launcher/state/build: - libwayland-client0=1.20.0-1
parts/va-drivers/state/build: - libwayland-client0=1.20.0-1
parts/pipewire/state/build: - libwayland-client0=1.20.0-1
parts/chromium-build/state/build: - libwayland-client0=1.20.0-1
parts/manpage
This appears to describe precisely this issue:
https://github.com/libsdl-org/SDL/pull/5092
On Thu, Aug 18, 2022 at 1:06 PM Robert Day
wrote:
> Yup, same errors ... lots of "wl "and "marshal" undefined references.
> Here's just a small sample:
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-
Yup, same errors ... lots of "wl "and "marshal" undefined references.
Here's just a small sample:
2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13:
error: use of undeclared identifier 'wl_proxy_marshal_flags'
2022-08-18 17:03:57.646 :: callback =
wl_proxy_marshal
That's what I did, but that's also when I got the errors I included in my
previous comment. I'm rebuilding just to make sure those errors are
reproducible.
On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:
> > but that appears to be because this newer gnome does
Just deleting that line seemed to allow the build to progress further,
but now I have a slew of errors; I'll post a snippet here, then must run
off but will be back in a bit:
2022-08-18 14:42:14.617 :: In file included from
../../third_party/angle/src/gpu_info_util/SystemInfo_vulkan.cpp:10:
I made that change, it still failed:
2022-08-18 14:31:54.099 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 14:31:54.099 :: Co
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986922
Title:
snapcraft build fails on second run as "ln -s libdrm.pc libdrm-
uninstalled.pc" already done
Status in chromiu
Ah:
build/args.gn:pkg_config = "/snap/gnome-3-38-2004/current/usr/bin/pkg-
config"
In my container, it's now /snap/gnome-42-2204; I'll change that and see
what happens.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
OK, I'm trying that now, but I would be astonished if that was the solution
as pkg-config is already installed, either because I installed it manually
at some point, or maybe it was installed by an earlier snap, who knows? But
it's definitely there so adding it to "build-packages" should make no
di
Hang on, look at that hard-coded directory name: "/snap/gnome-3-38-2004".
Since the gnome extension under core 22 is named just "gnome", any
hardcoded names to the old extension should fail.
On Thu, Aug 18, 2022 at 10:15 AM Robert Day
wrote:
> Same result:
>
> 2022-08-18 14:13:31.315 :: + OUT=ou
Same result:
2022-08-18 14:13:31.315 :: + OUT=out/Release
2022-08-18 14:13:31.316 :: + mkdir -p out/Release
2022-08-18 14:13:31.335 :: + cp /root/snaps/snap-from-source/stage/build/
args.gn out/Release/
2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'
2022-08-18 14:13:31.367 :: + '[' amd64 =
I know I don't need to suggest this, but the seeming solution is to just
replace "ln -s" with "ln -sf", unless there's something more subtle
going on.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bug
Let me know if there's anything you want me to test; I have the
container sitting here, ready for further experimentation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Public bug reported:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
exten
Public bug reported:
I'm trying to migrate the chromium browser snapcraft.yaml file to core22
and Snapcraft 7 and, after a build error on the first test (more on that
later), I cleaned and re-ran the build to make sure the build error was
reproducible, and got:
... big snip ...
2022-08-18 08:50:4
25 matches
Mail list logo
