Index | Thread | Search

From:
Kirill A. Korinsky <kirill@korins.ky>
Subject:
Re: update net/toxic to 0.15.1 and net/toxcore to 0.2.19
To:
Omar Polo <op@omarpolo.com>, Klemens Nanni <kn@openbsd.org>, ports@openbsd.org
Date:
Sun, 06 Oct 2024 19:46:28 +0200

Download raw body.

Thread
On Sun, 06 Oct 2024 19:33:59 +0200,
Kirill A. Korinsky <kirill@korins.ky> wrote:
> 
> On Sun, 06 Oct 2024 19:04:13 +0200,
> Omar Polo <op@omarpolo.com> wrote:
> > 
> > On 2024/10/06 16:52:39 +0000, Klemens Nanni <kn@openbsd.org> wrote:
> > > 06.10.2024 19:40, Omar Polo пишет:
> > > > Thank you!  I'm generally ok with these patches, provided that we remove
> > > > net/utox while here.  any oks to do so?
> > > 
> > > If it is indeed broken, by the update and/or deprecated upstream:  OK kn.
> > 
> > it is broken by the update, probably already slightly broken, and hasn't
> > seen a commit upstream in 3 years.
> > 
> > (there is a "fix double free in list when changing settings w/ empty
> > flist" committed just a couple of days after the last release in 2021)
> > 
> > I guess that if someone wants to work on it, or if upstream starts
> > working on it again, we can resurrect it from the attic.
> >
> 
> FYI: I just raised an issue: https://github.com/uTox/uTox/issues/1566
> 

Well, an attemp to try utox leads to a crash but this time it also
~/.config/tox by creating some file with wired names and brokes profile.

If anyone would like to try it, I suggest to keep backup nearby.

-- 
wbr, Kirill