We've updated obsidian to 1.5.12 and Electron 28.
We'll update it again when Obsidian releases with Electron 30.
On Sun, 16 Jun 2024 13:08:53 +0200
Daniel Engberg wrote:
> On 2024-06-16T12:37:28.000+02:00, Gleb Popov
> wrote:
>
> > This is partly my fault as a maintainer. We've updated Obsidian in our
> >
> > $WORK tree, but I forgot to upstream it.
> >
> > But I also agree that we should make an except
Am Sun, 16 Jun 2024 11:32:02 +0200
Harry Schmalzbauer schrieb:
+1
> Please stop removing perfectly working ports from the tree.
>
> textproc/obsidian is the latest victim, just because it currently
> depends on devel/electron25 - which builds and runs perfectly well too.
> User can in-app upda
This is partly my fault as a maintainer. We've updated Obsidian in our
$WORK tree, but I forgot to upstream it.
But I also agree that we should make an exception for Electron ports, because
- Electron itself is pretty fast-moving, but at the same time has a
lot of commercial consumers that aren't
Please stop removing perfectly working ports from the tree.
textproc/obsidian is the latest victim, just because it currently
depends on devel/electron25 - which builds and runs perfectly well too.
User can in-app update obsidian.
If the package building team already blacklisted devel/electron2
