Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Patrick Zanon]

Package: spyder
Version: 5.4.2+ds-5
Severity: minor
X-Debbugs-Cc: ne...@libero.it

Dear Maintainer,

Spyder on startup says there is a missin dependency problem with pylsp_black that
should be >= 1.2.0;however on my installation I have python3-pylsp-black 1.2.1-2.

The popup warning does not affect the spyder configuration nor functionality.

P.Z


-- System Information:
Debian Release: bookworm/sid
APT prefers testing-security
APT policy: (990, 'testing-security'), (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages spyder depends on:
ii python3 3.11.2-1
ii python3-spyder 5.4.2+ds-5

spyder recommends no packages.

Versions of packages spyder suggests:
pn python3-spyder-unittest <none>

Versions of packages python3-spyder depends on:
ii ipython3 8.5.0-4
ii libjs-jquery 3.6.1+dfsg+~3.5.14-1
ii libjs-mathjax 2.7.9+dfsg-1
ii pyflakes3 2.5.0-1
ii pylint 2.15.10-1
ii python3 3.11.2-1
ii python3-atomicwrites 1.4.1-1
ii python3-autopep8 2.0.1-1
ii python3-chardet 5.1.0+dfsg-2
ii python3-cloudpickle 2.2.0-1
ii python3-cookiecutter 1.7.3-2
ii python3-diff-match-patch 20200713-2
ii python3-docutils 0.19+dfsg-6
ii python3-flake8 5.0.4-4
ii python3-intervaltree 3.0.2-1.1
ii python3-ipython 8.5.0-4
ii python3-jedi 0.18.2-1
ii python3-jellyfish 0.8.9-1+b4
ii python3-jsonschema 4.10.3-1
ii python3-keyring 23.9.3-2
ii python3-mccabe 0.7.0-1
ii python3-nbconvert 6.5.3-3
ii python3-numpydoc 1.5.0-1
ii python3-parso 0.8.3-1
ii python3-pexpect 4.8.0-4
ii python3-pickleshare 0.7.5-5
ii python3-pkg-resources 66.1.1-1
ii python3-psutil 5.9.4-1+b1
ii python3-pycodestyle 2.10.0-1
ii python3-pydocstyle 6.2.3-3
ii python3-pygments 2.14.0+dfsg-1
ii python3-pylint-venv 2.3.0-2
ii python3-pyls-spyder 0.4.0-2
ii python3-pylsp 1.7.1-1
ii python3-pylsp-black 1.2.1-2
ii python3-pyqt5 5.15.9+dfsg-1
ii python3-pyqt5.qtwebengine 5.15.6-1
ii python3-qdarkstyle 3.1+ds1-1
ii python3-qstylizer 0.2.2-1
ii python3-qtawesome 1.2.2+dfsg-1
ii python3-qtconsole 5.4.0-1
ii python3-qtpy 2.3.0-1
ii python3-rope 1.7.0-1
ii python3-rtree 1.0.1-1
ii python3-setuptools 66.1.1-1
ii python3-sphinx 5.3.0-3
ii python3-spyder-kernels 2.4.2-1
ii python3-textdistance 4.5.0-1
ii python3-three-merge 0.1.1-4
ii python3-watchdog 2.2.1-1
ii python3-xdg 0.28-2
ii python3-zmq 24.0.1-4+b1
ii spyder-common 5.4.2+ds-5
ii yapf3 0.32.0-1

python3-spyder recommends no packages.

Versions of packages python3-spyder suggests:
ii cython3 0.29.32-2+b1
ii python3-matplotlib 3.6.3-1+b1
ii python3-numpy 1:1.24.2-1
ii python3-pandas 1.5.3+dfsg-2
ii python3-pil 9.4.0-1.1+b1
ii python3-scipy 1.10.0-12
ii python3-sympy 1.11.1-1

Versions of packages python3-pyqt5 depends on:
ii libc6 2.36-8
ii libgcc-s1 12.2.0-14
ii libpython3.11 3.11.2-4
ii libqt5core5a [qtbase-abi-5-15-8] 5.15.8+dfsg-2
ii libqt5dbus5 5.15.8+dfsg-2
ii libqt5designer5 5.15.8-2
ii libqt5gui5 5.15.8+dfsg-2
ii libqt5help5 5.15.8-2
ii libqt5network5 5.15.8+dfsg-2
ii libqt5printsupport5 5.15.8+dfsg-2
ii libqt5test5 5.15.8+dfsg-2
ii libqt5widgets5 5.15.8+dfsg-2
ii libqt5xml5 5.15.8+dfsg-2
ii libstdc++6 12.2.0-14
ii python3 3.11.2-1
ii python3-pyqt5.sip 12.11.1-1

-- no debconf information

[Julian Gilbey]

tags 1032995 + unreproducible
thanks

On Wed, Mar 15, 2023 at 10:25:01AM -0300, Patrick Zanon wrote:
> Package: spyder
> Version: 5.4.2+ds-5
> Severity: minor
> X-Debbugs-Cc: ne...@libero.it
>
> Dear Maintainer,
>
> Spyder on startup says there is a missin dependency problem with pylsp_black that
> should be >= 1.2.0;however on my installation I have python3-pylsp-black 1.2.1-2.
>
> The popup warning does not affect the spyder configuration nor functionality.
>
> P.Z

Dear Patrick,

I'm bemused by this one; I seem to have the same setup as you but I
don't receive this warning. Is it possible that you are running
spyder in some sort of virtual environment which does not have the
correct dependencies?

One thing you could try: select Help > About Spyder..., click "Copy
version info" and paste it into a reply to this bug report; then do
Help > Dependencies, click "Copy to clipboard" and paste that in as
well. That may well give us more of an idea of what is happening
here.

Best wishes,

Julian

[Julian Gilbey]

On Sun, Apr 09, 2023 at 11:04:03AM +0100, Julian Gilbey wrote:
> On Wed, Mar 15, 2023 at 10:25:01AM -0300, Patrick Zanon wrote:

> [...]

>
> Dear Patrick,
>
> I'm bemused by this one; I seem to have the same setup as you but I
> don't receive this warning. Is it possible that you are running
> spyder in some sort of virtual environment which does not have the
> correct dependencies?
>
> One thing you could try: select Help > About Spyder..., click "Copy
> version info" and paste it into a reply to this bug report; then do
> Help > Dependencies, click "Copy to clipboard" and paste that in as
> well. That may well give us more of an idea of what is happening
> here.

Another thought I've just had, based on your report #1033593: is it
possible you have locally installed Python libraries in
~/.local/lib/python3.11?

Best wishes,

Julian

[Brian Vaughan]

I'm seeing the same issue, on two different systems, both running Debian
Sid.

On one system, there were some libraries under ~/.local/lib/python3.10;
I deleted those, deleted the config files for spyder, reinstalled it,
and rebooted, but still saw the error.

[Julian Gilbey]

Oh dear, this is weird. Thanks for letting me know.

Please could you start spyder (acknowledging the missing-dependency
warning) and then do Help > Dependencies. It will give you a list of
dependencies loaded which you can then copy to the clipboard; please
can you send the results to this bug report? Please do the same with
Help > About Spyder... These may give some clues.

The next thing we can try is running the following in the iPython
console within Spyder:

import sys
sys.executable
sys.path
import pylsp_black
sys.modules["pylsp_black"]

Please send the output to this report, as there may be some clues
there.

Best wishes,

Julian

[Brian Vaughan]

# Spyder, Help > Dependencies

# Mandatory:
atomicwrites >=1.2.0          :  1.4.1 (OK)
chardet >=2.0.0               :  5.1.0 (OK)
cloudpickle >=0.5.0           :  2.2.0 (OK)
cookiecutter >=1.6.0          :  1.7.3 (OK)
diff_match_patch >=20181111   :  20200713 (OK)
intervaltree >=3.0.2          :  3.0.2 (OK)
IPython >=7.31.1;<9.0.0       :  8.5.0 (OK)
jedi >=0.17.2;<0.19.0         :  0.18.2 (OK)
jellyfish >=0.7               :  0.8.9 (OK)
jsonschema >=3.2.0            :  4.10.3 (OK)
keyring >=17.0.0              :  23.9.3 (OK)
nbconvert >=4.0               :  6.5.3 (OK)
numpydoc >=0.6.0              :  1.5.0 (OK)
parso >=0.7.0;<0.9.0          :  0.8.3 (OK)
pexpect >=4.4.0               :  4.8.0 (OK)
pickleshare >=0.4             :  0.7.5 (OK)
psutil >=5.3                  :  5.9.4 (OK)
pygments >=2.0                :  2.15.1 (OK)
pylint >=2.5.0;<3.0           :  2.16.2 (OK)
pylint_venv >=2.1.1           :  2.3.0 (OK)
pyls_spyder >=0.4.0           :  0.4.0 (OK)
pylsp >=1.7.1;<1.8.0          :  1.7.1 (OK)
pylsp_black >=1.2.0           :  None (NOK)
qdarkstyle >=3.0.2;<3.2.0     :  3.1 (OK)
qstylizer >=0.2.2             :  0.2.2 (OK)
qtawesome >=1.2.1             :  1.2.2 (OK)
qtconsole >=5.4.0;<5.5.0      :  5.4.0 (OK)
qtpy >=2.1.0                  :  2.3.0 (OK)
rtree >=0.9.7                 :  1.0.1 (OK)
setuptools >=49.6.0           :  66.1.1 (OK)
sphinx >=0.6.6                :  5.3.0 (OK)
spyder_kernels >=2.4.2;<2.5.0 :  2.4.2 (OK)
textdistance >=4.2.0          :  4.5.0 (OK)
three_merge >=0.1.1           :  0.1.1 (OK)
watchdog >=0.10.3             :  2.2.1 (OK)
xdg >=0.26                    :  0.28 (OK)
zmq >=22.1.0                  :  24.0.1 (OK)

# Optional:
cython >=0.21                 :  None (NOK)
matplotlib >=3.0.0            :  3.6.3 (OK)
numpy >=1.7                   :  1.24.2 (OK)
pandas >=1.1.1                :  None (NOK)
scipy >=0.17.0                :  1.10.1 (OK)
sympy >=0.7.3                 :  1.11.1 (OK)


# Spyder, Help > About Spyder

* Spyder version: 5.4.2  (pip)
* Python version: 3.11.2 64-bit
* Qt version: 5.15.8
* PyQt5 version: 5.15.9
* Operating System: Linux 6.1.0-9-amd64


# Commands in the iPython console

Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
Type "copyright", "credits" or "license" for more information.

IPython 8.5.0 -- An enhanced Interactive Python.

import sys

sys.executable
Out[2]: '/usr/bin/python3'

sys.path
Out[3]:
['/usr/lib/python311.zip',
 '/usr/lib/python3.11',
 '/usr/lib/python3.11/lib-dynload',
 '',
 '/usr/local/lib/python3.11/dist-packages',
 '/usr/lib/python3/dist-packages',
 '/usr/lib/python3.11/dist-packages']

import pylsp_black

sys.modules["pylsp_black"]
Out[5]: <module 'pylsp_black' from
'/usr/lib/python3/dist-packages/pylsp_black/__init__.py'>

[Julian Gilbey]

On Thu, May 25, 2023 at 09:25:50AM -0700, Brian Vaughan wrote:
> # Spyder, Help > Dependencies
> [...]

> pylsp >=1.7.1;<1.8.0          :  1.7.1 (OK)
> pylsp_black >=1.2.0           :  None (NOK)

Hi Brian,

Thanks for sending all this through. This is so weird.

> # Commands in the iPython console
>

All looks normal here.

I am utterly mystified why spyder is not finding pylsp_black. I'll
have a think about it and get back to you.

Best wishes,

Julian

[Julian Gilbey]

On Thu, May 25, 2023 at 08:03:19PM +0100, Julian Gilbey wrote:
> On Thu, May 25, 2023 at 09:25:50AM -0700, Brian Vaughan wrote:
> > # Spyder, Help > Dependencies
> > [...]
> > pylsp >=1.7.1;<1.8.0          :  1.7.1 (OK)
> > pylsp_black >=1.2.0           :  None (NOK)
>
> Hi Brian,
>
> Thanks for sending all this through. This is so weird.

> [...]

> All looks normal here.
>
> I am utterly mystified why spyder is not finding pylsp_black. I'll
> have a think about it and get back to you.

If you're able to do the following tests, it might help shed some
light on what's going wrong. The attached is a patch for the file
/usr/lib/python3/dist-packages/spyder/dependencies.py
to give more debugging output. Please apply the patch; you can do
this by saving the patch to a file, say /tmp/dependencies.py.diff,
then running the commands:

cd /usr/lib/python3/dist-packages/spyder/dependencies.py
patch --backup < /tmp/dependencies.py.diff

where the "--backup" option saves a copy of the original
dependencies.py file as dependencies.py.orig.

Once this patch is applied, start spyder from a terminal using the
command:

spyder --debug-info verbose

and let it run at least until it gives the warning message about
pylsp_black not being found, then quit spyder. There will be lots of
messages written to the terminal, but they will also be saved in the
file .config/spyder-py3/spyder-debug.log

Have a look through this file for "pylsp_black". Here's what I see:

2023-05-29 11:00:24,689 [DEBUG] [spyder.dependencies] -> Dependency(pylsp_black, python_lsp_black) starting
2023-05-29 11:00:24,931 [DEBUG] [spyder.dependencies] -> Dependency: get_module_version returned None for pylsp_black
2023-05-29 11:00:24,932 [DEBUG] [spyder.dependencies] -> Dependency: get_package_version returned 1.2.1 for pylsp_black

I'm guessing you'll get something quite different, probably with some
further debugging output following it (perhaps "Dependency: exception
raised..." followed by "Dependency: when exception raised..."). If
you're able to do this experiment, please could you send me these
lines of the log file. (I don't imagine that I would need any more of
the log file at this point.)

I do hope this will help to find the source of the problem!

Best wishes,

Julian

[Brian Vaughan]

Thank you for the clear instructions. I appreciate it.

The complete output is here:

https://www.geany.org/p/TQ2R2/

I believe this is the relevant part:

2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] ->
Dependency(pylsp, pytho
n_lsp_server) starting
2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] -> Dependency:
get_module_version returned 1.7.1 for pylsp
2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] ->
Dependency(pylsp_black, python_lsp_black) starting
2023-05-29 09:28:09,471 [DEBUG] [spyder.dependencies] -> Dependency:
exception raised: Invalid version: 'v0.9.4.4-ds-git20221205-12a9702d29ab'
2023-05-29 09:28:09,471 [DEBUG] [spyder.dependencies] -> Dependency:
when exception raised: sys.path = ['',
'/usr/lib/python3/dist-packages/spyder/plugins/help/utils', '/usr/bin',

'/usr/lib/python311.zip', '/usr/lib/python3.11',
'/usr/lib/python3.11/lib-dynload',

[Julian Gilbey]

On Mon, May 29, 2023 at 09:51:48AM -0700, Brian Vaughan wrote:
> Thank you for the clear instructions. I appreciate it.

Thanks Brian!

> The complete output is here:
>
> https://www.geany.org/p/TQ2R2/

Though for some reason this gives a 404 Not Found error. But it
doesn't matter, as I think the snippet quoted below is enough.

> I believe this is the relevant part:
>
> 2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] -> Dependency(pylsp,
> pytho
> n_lsp_server) starting
> 2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] -> Dependency:
> get_module_version returned 1.7.1 for pylsp
> 2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] ->
> Dependency(pylsp_black, python_lsp_black) starting
> 2023-05-29 09:28:09,471 [DEBUG] [spyder.dependencies] -> Dependency:
> exception raised: Invalid version: 'v0.9.4.4-ds-git20221205-12a9702d29ab'
> 2023-05-29 09:28:09,471 [DEBUG] [spyder.dependencies] -> Dependency: when
> exception raised: sys.path = ['',
> '/usr/lib/python3/dist-packages/spyder/plugins/help/utils', '/usr/bin',
> '/usr/lib/python311.zip', '/usr/lib/python3.11',
> '/usr/lib/python3.11/lib-dynload',
> '/usr/local/lib/python3.11/dist-packages', '/usr/lib/python3/dist-packages',
> '/usr/lib/python3.11/dist-packages']

OK, this is strange. pkg_resources is picking up an old or broken
version of python_lsp_black-*.egg-info. Could you try

ls -R /usr/local/lib/python3.11/dist-packages/python_lsp_black*
ls -R /usr/local/lib/python3.11/dist-packages/pylsp_black*

ls -R /usr/lib/python3/dist-packages/python_lsp_black*
ls -R /usr/lib/python3/dist-packages/pylsp_black*

ls -R /usr/lib/python3.11/dist-packages/python_lsp_black*
ls -R /usr/lib/python3.11/dist-packages/pylsp_black*

One of these pairs of commands is likely to identify the culprit!

Best wishes,

Julian

[Brian Vaughan]

$ ls -lR /usr/lib/python3/dist-packages/python_lsp_black*
/usr/lib/python3/dist-packages/python_lsp_black-1.2.1.egg-info:
total 20
-rw-r--r-- 1 root root    1 Dec  9 22:58 dependency_links.txt
-rw-r--r-- 1 root root   41 Dec  9 22:58 entry_points.txt
-rw-r--r-- 1 root root 4077 Dec  9 22:58 PKG-INFO
-rw-r--r-- 1 root root   96 Dec  9 22:58 requires.txt
-rw-r--r-- 1 root root   12 Dec  9 22:58 top_level.txt


$ ls -lR /usr/lib/python3/dist-packages/pylsp_black*
/usr/lib/python3/dist-packages/pylsp_black:
total 12
-rw-r--r-- 1 root root    0 Apr 12  2022 __init__.py
-rw-r--r-- 1 root root 6337 Apr 12  2022 plugin.py
drwxr-xr-x 2 root root 4096 May 24 16:59 __pycache__

/usr/lib/python3/dist-packages/pylsp_black/__pycache__:
total 16
-rw-r--r-- 1 root root  163 May 24 16:59 __init__.cpython-311.pyc
-rw-r--r-- 1 root root 8963 May 24 16:59 plugin.cpython-311.pyc

[Julian Gilbey]

On Mon, May 29, 2023 at 12:59:05PM -0700, Brian Vaughan wrote:
> $ ls -lR /usr/lib/python3/dist-packages/python_lsp_black*
> /usr/lib/python3/dist-packages/python_lsp_black-1.2.1.egg-info:
> total 20

> [...]

These all look fine; did the other commands all return nothing (or
"file not found" errors)?

Best wishes,

Julian

[Brian Vaughan]

Yes, the other commands returned "file not found". (I hit send prematurely.)

[Julian Gilbey]

On Mon, May 29, 2023 at 01:35:50PM -0700, Brian Vaughan wrote:
> Yes, the other commands returned "file not found". (I hit send prematurely.)

OK, hmmm. That is just plain weird. I wonder where this originates?

What's the content of the file (up to the first blank line):
/usr/lib/python3/dist-packages/python_lsp_black-1.2.1.egg-info/PKG-INFO

It *should* begin with:

Metadata-Version: 2.1
Name: python-lsp-black
Version: 1.2.1
Summary: Black plugin for the Python LSP Server
[...]

but I wonder if it does?

Best wishes,

Julian

[Brian Vaughan]

Yes, that's what it starts with.

Metadata-Version: 2.1
Name: python-lsp-black
Version: 1.2.1
Summary: Black plugin for the Python LSP Server

Home-page: https://github.com/python-lsp/python-lsp-black
Author: Python LSP contributors
Author-email: f...@fidelramos.net
Project-URL: Bug Tracker,
https://github.com/python-lsp/python-lsp-black/issues
Project-URL: Changelog,
https://github.com/python-lsp/python-lsp-black/blob/master/CHANGELOG.md
Project-URL: Source Code, https://github.com/python-lsp/python-lsp-black
Classifier: Programming Language :: Python
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Requires-Python: >=3.7
Description-Content-Type: text/markdown
Provides-Extra: dev
License-File: LICENSE

[Julian Gilbey]

On Mon, May 29, 2023 at 02:15:55PM -0700, Brian Vaughan wrote:
> Yes, that's what it starts with.
>
> Metadata-Version: 2.1
> Name: python-lsp-black
> Version: 1.2.1

> [...]

OK, so the bug lies elsewhere.... pkg_resources complains about an
invalid version. Let's see if we can locate it....

Does this command return anything?

rgrep v0.9.4.4-ds-git20221205-12a9702d29ab /usr/lib/python3/dist-packages

(For any pedants reading this bug report: yes, '.' is a wildcard and
ought to be escaped, but there is unlikely to be anything that matches
this regex other than an actual '.'.)

Best wishes,

Julian

[Brian Vaughan]

It didn't return anything. Neither did "locate
'v0.9.4.4-ds-git20221205-12a9702d29ab'".

[Julian Gilbey]

On Mon, May 29, 2023 at 04:51:25PM -0700, Brian Vaughan wrote:
> It didn't return anything. Neither did "locate
> 'v0.9.4.4-ds-git20221205-12a9702d29ab'".

Hi Brian,

Thanks for bearing with me! Hmmm, this is strange indeed. Let's try
the other search directories as well, then:

rgrep 0.9.4.4-ds-git20221205-12a9702d29ab \
. /usr/lib/python3/dist-packages/spyder/plugins/help/utils \
/usr/lib/python3.11 /usr/local/lib/python3.11/dist-packages \
/usr/lib/python3/dist-packages /usr/lib/python3.11/dist-packages

(all one command; the "\" are line continuation characters and should
be omitted if the whole command is written on one line). The initial
"." means look in the current directory, so you might want to run
this command from an empty directory! (It would also be worth
checking that spyder still gives the pylsp_black warning when running
from this empty directory.)

Best wishes,

Julian

[Julian Gilbey]

On Tue, May 30, 2023 at 03:31:36PM -0700, Brian Vaughan wrote:
> That rgrep didn't find anything.
>
> Executing 'spyder' from the command line while in an empty directory still
> got the same 'pylsp_black' warning.

Oh, this is so bizarre! Let's try a sledge-hammer approach....

Assuming that you have the strace package installed, could you try
this and send the resulting log file (/tmp/spyder-trace.txt.gz); you
will need to wait at least until the warning message about pylsp_black
appears:

strace -f -o /tmp/spyder-trace.txt -s 256 -e openat,read spyder

gzip /tmp/spyder-trace.txt

Hopefully this will give a clue to where this strange behaviour is
coming from!

(BTW, this log file will include the first 256 characters of any files
you open, so I recommend you do this with a clean spyder profile.)

Best wishes,

Julian

[Brian Vaughan]

I have good news and bad news.

The good news is that the issue seems to have been fixed as of today. I
don't get the error popup, and Help > Dependencies shows pylsp_black
installed and at version 1.21.

The bad news is I'm not sure what fixed it. I realized I made the
mistake of following my daily routine of updating my system, which is
not a good idea when troubleshooting. I checked the changelog dates on
the dependencies for python3-spyder, and the most recently updated were
python3-pygments on April 19, and python3-cookiecutter and
python3-sphinx on March 29.

The only updates today were chromium, chromium-common, and
chromium-sandbox, updated to 114.0.5735.90-2. Maybe those are indirect
dependencies?

[Julian Gilbey]

Oh :( Well, I'm glad it's now working, but as you say, it will be
probably now be impossible to identify the source of the bug. I had a
quick look at the previous version of the chromium packages, and
there's nothing obvious there, so that's almost certainly not the
cause.

I wonder whether it's a package you updated yesterday that fixed
things? You could check the aptitude logs (assuming you used
aptitude).

Best wishes,

Julian

[Brian Vaughan]

I hadn't even noticed Synaptic kept logs.

There was one other set of updates, after the last time I saw the error
in Spyder:

Commit Log for Wed May 31 16:06:10 2023


Upgraded the following packages:
chromium (113.0.5672.126-1) to 114.0.5735.90-1
chromium-common (113.0.5672.126-1) to 114.0.5735.90-1
chromium-sandbox (113.0.5672.126-1) to 114.0.5735.90-1
libgc1 (1:8.2.2-3) to 1:8.2.4-1
libnautilus-extension4 (43.2-1) to 43.4-1
libssl-dev (3.0.8-1) to 3.0.9-1
libssl3 (3.0.8-1) to 3.0.9-1
libssl3:i386 (3.0.8-1) to 3.0.9-1
needrestart (3.6-3) to 3.6-4
openssl (3.0.8-1) to 3.0.9-1
signal-desktop (6.19.0) to 6.20.0
syncthing-gtk (0.9.4.4+ds+git20221205+12a9702d29ab-1) to
0.9.4.4+ds+git20221205+12a9702d29ab-2