@Vlad-Nirky Yes, people routinely underestimate the effort needed to perfect and maintain a port.

@messayisto said:

Will all the good stuff landed in 24.04.2 be backported to 24.04.1?

No, not all the good stuff. But some of it might

@nbdynl said:

maintaining convergence

By 'convergence' in this instance I suppose you mean 'the same OS features across the different device ports"? Because people might mistake your meaning since that word is heavily in use for a specific features of the OS.

@kugiigi clickable works fine on UT now. Install clickable snap and docker snap connect some.slots and you're off to the races.

@grgraf I think container-mode is and option for clickable in general. But it doesn't make much sense to run clickable desktop inside a container created by clickable itself. i.e. that was not an envisioned use case.

Container mode is primarily used for building your click inside a ci container on GitHub / GitLab / whatever CI infrastructure you use, if it leverages containers.

@Blackbomber I guess what @kugiigi is saying is, swapping out one long since unsupported OS for another now also unsupported OS doesn't seem to align with your stated goal.

@vince.vs The path is. Not a (full) filesystem path
Rather this is probably the left-overs of some app that shared status info to the greeter infographic, which you have since uninstalled.

@Turbolqk said:

@kugiigi I see, I haven't used UT in a few months, so I might've missed a few things.

These things you think you might have missed have been implemented for years, so even the few months ago that you used UT last, you should have come across them.

@AntiMS said:

My Pixel 3a running Ubuntu Touch 24.04 (24.04-1.3) abruptly stopped being able to send/receive texts/calls a few weeks ago.

Did your carrier completely switch over to VoLTE and switch off 2g/3g for calls? That would explain the sudden inability to receive or place calls.

@idonthatevests that would depend on what exactly needs patching. If it is some.module that is loaded at initialization time, but is packaged separately, then a new root image would carry the patch. If it is the kernel itself that needs patching, then the port maintainers would have to step up.

@Question_Asker There is no need to maintain a mirror of the source code if you would be distributing unchanged binaries. In that case simply pointing the customer to the license and the original source code, in whatever form, by link or in writing, is enough to comply with the license.

Only when modifying the source and producing distributing builds based on those modifications, would you be required to link to your own changes.

In any case, the license never requires you to ship the source code with every rrdistribution of your product. It merely requires you to make the source code available. Providing links to the relevant places complies with that requirement.

@MalocDegray said:

Via the phone terminal like @tafitson recommended is possible, but the phone is no longer detected via adb via computer.

When the device is in fasboot/bootloader mode it is never recognized via adb. You need to have fastboot installed and with that command it should be recognized.

@developerbayman This post is two years old. And the OP hasn't been on the forums in over a year. I doubt they will benefit from any advice now.
I will proceed to lock the thread.

@brenno.almeida the source needs to be available if it is an open source app. But as long as it is fully confined it doesn't need to be open source to be published in the store. The 'open' in Open Store originally was because it was also open to unconfined apps, whereas those were not allowed in the Canonical store.

@developerbayman it's just an update of an app that I have had in the store for years now.

This is an open ecosystem. User choice is welcomed. If it is a different app, inspired on Syncthing or no, then there's definitely no objection.

Even if it were the same app, then I am in no capacity to object anyhow. But in the latter case I would rather appreciate collaboration rather than having two distinct versions of the same app in the store.

But since this is not even the case with your app, by all means follow your intuition.

@Moem so it is!

@developerbayman It is never "that simple". If it were, it would already have been done.

A new version (2.0.16) of Syncthing has been uploaded to the Open Store. This release follows the upstream release. See here for the release notes.