On Fri, 2025-11-21 at 14:20 +0500, Andrey Rakhmatullin wrote:
> On Fri, Nov 21, 2025 at 06:06:31AM -0300, Aeliton G. Silva wrote:
> > There's one last thing I want to do: to build this package on a
> > newly
> > install of sid (to make sure all the build deps are on
> > debian/control).
>
> You sh
On Fri, 2025-11-21 at 11:20 +0100, Jochen Sprickerhof wrote:
>
> quoting form the wiki:
>
> > Once you've built and uploaded your package,
>
> Note the "uploaded" (to the Debian archive). So you should not tag.
I want to be extra careful to not disturb anyone, so I'd like to
clarify: is the upl
Hi Aeliton,
thanks for working on this. python-lsp-server is version locked by
python3-spyder and needs coordination with Julian (Cc).
@Julian: can we get a new version in?
* Aeliton G. Silva [2025-11-21 06:06]:
I managed to create a working package for python-lsp-server using the
upstream
On Fri, Nov 21, 2025 at 06:06:31AM -0300, Aeliton G. Silva wrote:
There's one last thing I want to do: to build this package on a newly
install of sid (to make sure all the build deps are on debian/control).
You should use a chroot build tool like sbuild instead of installing a sid
system manu
Hi all,
I managed to create a working package for python-lsp-server using the
upstream version 1.13.2 and I'd like to check if everything looks good.
According to [1] the next steps would be:
$ git push origin : --tags
but I'm not sure I should do that before any of the maintainers have a
look
5 matches
Mail list logo
