Re: python-lsp-server new upstream version

Andrey Rakhmatullin <[email protected]> Sat, 22 Nov 2025 20:35:08 +0500

Newsgroups	gmane.linux.debian.devel.python
Message-ID	<[email protected]>

On Sat, Nov 22, 2025 at 12:30:29PM -0300, Aeliton G. Silva wrote:
>> No, the upload to Debian archive is only done by your sponsor.
>>
>> >
>> > Push your repo to salsa.debian.org:
>>
>> This is not about uploading to the archive.
>>
>
>Thanks for the clarifications Andrey.
>
>About pushing it to salsa, can I do it or this should also be done by a
>sponsor?

You should push but not tag.

>> > > Can you test if this is a test only dependency and can be
>> > > annotated
>> > > with <!nocheck>?
>> > >
>> >
>> > Good shout, thanks. websockets are in the [project.optional-
>> > dependencies] in the pyproject.toml of the upstream, so I assume it
>> > should be annotated with <!nocheck>.
>>
>> What matters is whether it's used for building or just for testing
>> and
>> whether the package builds fine with the nocheck build profile after
>> your
>> changes. You shouldn't just guess.
>
>If I remove either black or python3-websockets from debian/control, gbp
>buildpackage will succeed creating python_lsp_server-1.13.2-py3-none-
>any.whl, but the test session will fail when any of the packages is not
>installed.
>
>The debian package builds normally after annotating both dependencies
>with <!nocheck>.

Still, it's a bad idea to annotate deps with a build profile without 
actually testing it.


-- 
WBR, wRAR

signature.asc (application/pgp-signature, 894 B)