Built, failed to release [Scanning for processes to kill in build]

RUN: /usr/share/launchpad-buildd/bin/in-target scan-for-processes --backend=lxd --series=focal --arch=armhf SNAPBUILD-1592152
Scanning for processes to kill in build SNAPBUILD-1592152

Build Log: https://launchpadlibrarian.net/570479758/buildlog_snap_ubuntu_focal_armhf_ad3b0ea051e3b72894088f01c59879ba_BUILDING.txt.gz

No extra errors in the old dashboard.

What am I meant to do to resolve this issue? This: “Also, you can snap install review-tools and then run snap-review (mysnap) against your snap, to see if it fails any store review processes, locally.” ? But I can’t even build the snap online? Is there a way to build it offline?

I only changed one small line of code in my application, noticed it did not trigger an automatic rebuild which I thought was odd. Now it wont release and no explicit reason why is presented to me?

The “Scanning for processes to kill …” message is informational and entirely unrelated to your actual problem. Ignore that.

The real problem is shown on https://launchpad.net/~build.snapcraft.io/+snap/ad3b0ea051e3b72894088f01c59879ba/+build/1592152 (linked from the top of the build log):

__all__: The new version submitted for 'borger3' does not match the upload ('borg').

And that’s because when you first set up this snap to build on snapcraft.io, it was called borger3 (as shown on https://launchpad.net/~build.snapcraft.io/+snap/ad3b0ea051e3b72894088f01c59879ba), but you later changed your snap to say name: borg. I don’t quite recall how to convince snapcraft.io to update its idea of the name; you may need to disconnect the repository on snapcraft.io and reconnect it again.

Ah thank you, my mistake, thank you. I remember doing this now to try and fix the desktop icon issue not registering and forgot that it was linked to the snap registration.

What a pickle I’ve got myself into - correcting it all now.