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://bugs.launchpad.net/bugs/1986922 Title: snapcraft build fails on second run as "ln -s libdrm.pc libdrm- uninstalled.pc" already done Status in chromium-browser package in Ubuntu: New Bug description: 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:45.224 :: + OUT=out/Release 2022-08-18 08:50:45.224 :: + mkdir -p out/Release 2022-08-18 08:50:45.243 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 'libdrm-uninstalled.pc': File exists 2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. Naturally, since that symlink had been created during the first run (in a persistent 22.04 LXD container), it was still there for the second run. Operations like that should be idempotent so one can run multiple builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
