On 25-01-2024 08:18, David C. Rankin wrote:
Devs,
The "[Postfix] Warn that databases need regeneration" thread touched
on a proposed change from BDB to another, either cdb or lmdb. This
loosely mentions "licensing" issues. What licensing issue is the problem?
The Oracle open-source lic
Currently, I'm using `libjxl v0.9.1-1` from 'extra' repository with no problems
alongside Telegram Desktop.
What breakage do you exactly experience?
--
Best Regards,
Abraham
Sent with Tutanota; https://tuta.com
Jan 20, 2024, 16:48 by br...@allred.io:
> Hey all,
>
> After this morning's upgrad
Jan 25, 2024, 07:58 by arash@tuta.io:
> Currently, I'm using `libjxl v0.9.1-1` from 'extra' repository with no
> problems alongside Telegram Desktop.
> What breakage do you exactly experience?
>
> --
> Best Regards,
> Abraham
> Sent with Tutanota; https://tuta.com
>
>
>
> Jan 20, 2024, 16:
Do you have that installed?
--
Cheers,
Aᴀʀᴏɴ
OpenPGP_0x4E85967FC7C436BE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
On Thu, 2024-01-25 at 21:27 +0100, Brian Allred wrote:
...
> the same issue with libvpx after today's update. Discord, Telegram,
and xfreerdp all complain about missing the shared library
"libvpx.so.8".
>
>
May or may not be the issue, but best I can tell libvpx package is not
a dependency of dis
On Thu, 25 Jan 2024 21:27:28 +0100 (CET)
Brian Allred wrote:
> Actually, I updated again the next day and all was well. But it's funny you
> sent this message this morning, because now I'm experiencing the same issue
> with libvpx after today's update. Discord, Telegram, and xfreerdp all
> compla
Le 26/01/2024 à 02:30, Doug Newgard a écrit :
On Thu, 25 Jan 2024 21:27:28 +0100 (CET)
Brian Allred wrote:
Actually, I updated again the next day and all was well. But it's funny you
sent this message this morning, because now I'm experiencing the same issue
with libvpx after today's update. D
Jan 25, 2024, 19:45 by archa...@archlinux.org:
> Le 26/01/2024 à 02:30, Doug Newgard a écrit :
>
>> On Thu, 25 Jan 2024 21:27:28 +0100 (CET)
>> Brian Allred wrote:
>>
>>> Actually, I updated again the next day and all was well. But it's funny you
>>> sent this message this morning, because now
