Bug#940575: RFS: fortran-language-server/1.10.2-1 [ITP] -- Fortran Language Server for the Language Server Protocol
Hi team, could you help me and sponsor upload of new package? It is Language Server (LSP) for fortran code and it is implemented in python. The package is available in Salsa https://salsa.debian.org/python-team/applications/fortran-language-server and uploaded to mentors.d.n https://mentors.debian.net/package/fortran-language-server as well. Thanks, Denis Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "fortran-language-server" * Package name: fortran-language-server Version : 1.10.2-1 Upstream Author : Chris Hansen * URL : https://github.com/hansec/fortran-language-server * License : Expat * Vcs : https://salsa.debian.org/python-team/applications/fortran-language-server Section : editors It builds those binary packages: fortran-language-server - Fortran Language Server for the Language Server Protocol To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fortran-language-server Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fortran-language-server/fortran-language-server_1.10.2-1.dsc Changes since the last upload: * Initial release (Closes: 936075). Regards, -- Denis Danilov
Re: 2Removal: handling circular dependencies / dropping tests before the binary?
> Note that having an unbuildable package in sid for several days, until > it's updated to a no-py2 version, is perfectly acceptable. please note that may not be fine with every maintainer. dont just drop packages without checking rdeps and/or if you know that will make packages uninstallable/unbuildable (unless you check with the people taking care of such packages first). btw sphinx-gallery d-b on pyhton-seaborh has been removed. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Re: I'll be offline for an indefinite period
On Sat, Sep 21, 2019 at 07:13:32PM +0200, wrote: > Hello, > > Unfortunately, I will be offline for an indefinite period. A man got to do what a man got to do. So face what you have to face. Thank you for reminding that there is life out side libre software life. I looking forward to your return. > I maintain those packages in python team: wikitrans, pyfribidi, okasha, > and python-uinput. > > okasha in git has a fix and needs to be uploaded. Groeten Geert Stappers DD -- Leven en laten leven
I'll be offline for an indefinite period
Hello, Unfortunately, I will be offline for an indefinite period. I maintain those packages in python team: wikitrans, pyfribidi, okasha, and python-uinput. okasha in git has a fix and needs to be uploaded. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7 GPG Fingerprints: 6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: PGP signature
Re: 2Removal: handling circular dependencies / dropping tests before the binary?
On Sat, Sep 21, 2019 at 10:18:16AM +0100, Rebecca N. Palmer wrote: > Some Python 2 packages have circular (build-)dependencies, making it > impossible to remove them one at a time without breaking anything. Unless I'm missing something, this shouldn't be a problem, just go away and remove them all and upload them in roughly the same time? > --- Cut the cycle by removing one of the dependencies. > > This may mean skipping (some of) the tests, as Python build dependencies are > often actually test dependencies. There might be cases where it isn't > reasonably possible at all. Unless some of those don't have Python 3 packages in the archive yet, why removing py2 from one package would break building another, if that another has py2 parts removed too? Note that having an unbuildable package in sid for several days, until it's updated to a no-py2 version, is perfectly acceptable. -- WBR, wRAR signature.asc Description: PGP signature
2Removal: handling circular dependencies / dropping tests before the binary?
Some Python 2 packages have circular (build-)dependencies, making it impossible to remove them one at a time without breaking anything. One such cycle is seaborn, sphinx-gallery and matplotlib2 (#940873); I have not attempted to systematically check for them. How should these be dealt with? --- Cut the cycle by removing one of the dependencies. This may mean skipping (some of) the tests, as Python build dependencies are often actually test dependencies. There might be cases where it isn't reasonably possible at all. (Related question: if a package with a large test suite is being uploaded anyway, should we consider removing the Python 2 tests just to save buildd/debci resources?) --- Prepare all the required packages in salsa / experimental, then remove the entire cycle at once. This is easy if the cycle is small and otherwise ready to remove, but if one member has a big dependency tree, the whole cycle might have to stay for some time. (Related question: does it make sense to create no-Python2 salsa branches of one's regular modules (particularly any that need nontrivial changes) and mark them "please upload when the reverse dependencies have been cleared", even if they aren't part of a cycle?)
Re: Bug#940811: ITP: python-simplenote -- Python3 API wrapper for the Simplenote web service
Hi, so 21. 9. 2019 v 8:32 odesílatel Geert Stappers napsal: > i'm not sure if the 3 should/must goto into package name. > src: python-foo binary-python3: python3-foo binary-doc: python-foo-doc Thanks. :) -- Best regards Ondřej Nový
Request to join the DPMT
[Re-sending again, this time using my full name, my @debian e-mail address and a gpg signature.] Hi -python, I'd like to join the DPMT! I am going to package omgifol[1] (python3-omg), a Python library for reading, manipulating and writing WAD files, i.e. Doom game data files. My plan is to use this library (instead of deutex) to create individual desktop icons for each Doom game in game-data-packager[2]. Currently, I own the corresponding ITP[3] originally opened by jmtd back in 2005. My salsa login is "fabian". I have read and accepted the policy in https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst Thanks! - Fabian [1] https://github.com/devinacker/omgifol [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803930 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354732 signature.asc Description: This is a digitally signed message part
Re: Bug#940811: ITP: python-simplenote -- Python3 API wrapper for the Simplenote web service
Control: retitle -1 ITP: python-simplenote -- Python3 API wrapper for the Simplenote web service On Thu, Sep 19, 2019 at 11:09:14PM -0700, Stefan van der Walt wrote: > On Thu, Sep 19, 2019, at 22:53, Geert Stappers wrote: > > On Thu, Sep 19, 2019 at 10:43:48PM -0700, Stefan van der Walt wrote: > > > * Package name: python-simplenote > > > Programming Lang: Python > > > Description : Python API wrapper for the Simplenote web service > > > > Python or Python3? > > Please provide clearity. > > I was planning on building only for Python 3 to support nvpy, which also now > runs on 3. Okay. "3" is now in the description. I'm not sure if the 3 should/must goto into package name. Hence the Cc to the Python mailinglist for asking advice. Groeten Geert Stappers -- Leven en laten leven
