Bug#994666: RFS: python-mockito/1.2.2-2 -- Spying framework for Python - documentation
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-mockito". It has already been uploaded with binary packages to unstable. To reach testing (bookworm), it needs this source-only upload, which is why I need a sponsor. * Package name: python-mockito Version : 1.2.2-2 Upstream Author : https://github.com/kaste/mockito-python/issues * URL : https://github.com/kaste/mockito-python * License : Expat * Vcs : https://salsa.debian.org/python-team/packages/python-mockito Section : python It builds those binary packages: python-mockito-doc - Spying framework for Python - documentation python3-mockito - Spying framework for Python To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-mockito/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-mockito/python-mockito_1.2.2-2.dsc Changes since the last upload: python-mockito (1.2.2-2) unstable; urgency=medium . * Source-only upload. Thanks in advance! Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
Bug#989486: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x
Nilesh Patra writes: > * The pristine tar contained .tar.gz.*, it should > instead contain .orig.tar.gz for origtargz both for the sake of > consistency and for origtargz to run fine Oops, OK, I have just re-run pristine-tar on the .orig file and committed. > * We are in freeze time, and a new version upload unless absolutely > necessary isn't appropriate[2]. This package does not seem to have any > (RC) bug or affecting any package that a version bump would be > desired. > > Hence, this should be uploaded after bullseye release. Feel free to > ping me then, and I'll happily sponsor. Also, please take a look at my > commits in salsa. > > [2]: https://release.debian.org/testing/freeze_policy.html I'm fine with waiting. After the freeze, I think it will be ready for uploading (I don't want to spam mentors.d.o during the freeze). Thanks a lot for your help! Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
Bug#989486: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-click-log": * Package name: python-click-log Version : 0.3.2-1 Upstream Author : [fill in name and email of upstream] * URL : https://github.com/click-contrib/click-log * License : Expat * Vcs : https://salsa.debian.org/python-team/packages/python-click-log Section : python It builds those binary packages: python3-click-log - Logging integration for Click - Python 3.x To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-click-log/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-click-log/python-click-log_0.3.2-1.dsc Changes since the last upload: python-click-log (0.3.2-1) unstable; urgency=medium . [ Debian Janitor ] * Bump debhelper from old 10 to 12. * Set upstream metadata fields: Bug-Database, Repository, Repository- Browse. * Remove constraints unnecessary since stretch: + Build-Depends: Drop versioned constraint on dh-python. . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Fabrice Bauzac-Stehly ] * New upstream release. * Upgrade d/watch to version 4. * Upgrade the Standards-Version to 4.5.1. * Declare Rules-Requires-Root: no. Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
Bug#985236: RFS: python-mockito/1.2.2-1 [ITP] -- Spying framework for Python
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-mockito": * Package name: python-mockito Version : 1.2.2-1 Upstream Author : https://github.com/kaste/mockito-python/issues * URL : https://github.com/kaste/mockito-python * License : Expat * Vcs : https://salsa.debian.org/python-team/packages/python-mockito Section : python It builds these binary packages: python3-mockito - Spying framework for Python python-mockito-doc - Spying framework for Python - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-mockito/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-mockito/python-mockito_1.2.2-1.dsc Changes since the last upload: python-mockito (1.2.2-1) unstable; urgency=low . * Initial release. Closes: #981067 Thanks! Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6 old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#983705: RFS: python-mockito/1.2.2-1 [ITP] -- Spying framework for Python - documentation
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-mockito": * Package name: python-mockito Version : 1.2.2-1 Upstream Author : https://github.com/kaste/mockito-python/issues * URL : https://github.com/kaste/mockito-python * License : Expat * Vcs : https://salsa.debian.org/python-team/packages/python-mockito Section : python It builds those binary packages: python-mockito-doc - Spying framework for Python - documentation python3-mockito - Spying framework for Python To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-mockito/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-mockito/python-mockito_1.2.2-1.dsc Changes since the last upload: python-mockito (1.2.2-1) unstable; urgency=low . * Initial release. Closes: #981067 Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6 old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#975465: RFS: python-opentracing/2.4.0-1 -- opentracing interface for Python - documentation
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-opentracing": * Package name: python-opentracing Version : 2.4.0-1 Upstream Author : opentrac...@googlegroups.com * URL : https://github.com/opentracing/opentracing-python * License : Apache-2.0, Expat * Vcs : https://salsa.debian.org/python-team/packages/python-opentracing Section : python It builds those binary packages: python-opentracing-doc - opentracing interface for Python - documentation python3-opentracing - opentracing interface for Python To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-opentracing/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-opentracing/python-opentracing_2.4.0-1.dsc Changes since the last upload: python-opentracing (2.4.0-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Fabrice BAUZAC ] * Switch to debhelper 13. * New upstream version 2.4.0. * Disable the tests of the gevent scope manager until #974051 is fixed. Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Re: Sponsor for DMX - The Context Machine
Andrey Rahmatullin writes: > On Sat, Apr 04, 2020 at 11:36:03PM +0200, Fabrice BAUZAC-STEHLY wrote: >> - By building the upstream source (main)? By packaging the upstream >> binary (contrib)? > Pre-built binaries are for non-free, not for contrib. Contrib is strictly > DFSG-free. Here the binaries seem to be free software (AGPL3 or GPL3). Are you sure? -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Re: Sponsor for DMX - The Context Machine
Juergen Neumann writes: > Hi all! > > I would like to file an ITP for DMX - The Context Machine [1], formerly > known as DeepaMehta [2]. As this will be my first project for Debian I > am kindly looking for a sponsor. So far I barely managed to create a > first lintian compliant result [3]. I will be happy to improve. :-) > > Thank you very much in advance! > > Juergen > > [1] https://git.dmx.systems/dmx-platform/dmx-platform > [2] https://www.deepamehta.de/ > [3] https://github.com/dmx-systems/dmx-build-deb Hello Juergen, I'm still quite new to Debian packaging and certainly can't talk for the Debian project but I'll try to give you some advice nevertheless. I hope the following advice is correct Debian-wise; sorry if I'm making mistakes, please correct me in that case. I can see in the README of dmx-build-deb: dmx-build-deb builds Debian packages from DMX binary files and loads them into the public repository at DMX Systems. Debian packages normally build software from source, not binary. That is required for your package to be part of Debian proper (the "main" section). If that's impossible though, there is the "contrib" section where such packages can be uploaded. It is recommended to build from source whenever possible. Also, I guess a Debian package should not load anything to some other repository. Your debian/README.source is basically a template. You should either remove it or write something interesting there. README.source is the place where you document specifics of your package with regards to how it should be built. debian/control, debian/copyright are templates (@@PACKAGENAME@@, @@CONFLICTS@@, ...). It looks like it is instantiated through .gitlab-ci.yml. I guess it is OK in principle, but remember that you have to upload a Debian-compliant source package in any case. I'm not sure whether a Debian package can be named "dmx-latest"; I guess it should just be named "dmx". Debian takes copyright and license information very seriously; if there is any doubt on the license of some file, it might need to be removed from the set of packaged files through a +dfsg modification. Therefore it is highly advised that the license of each source file in the upstream source code be very clear. The safest if you can is to add to each nontrivial source file the copyright line of each contributor with the years of contributions, and indicate which license applies to this file (and in particular if it is AGPL3 strict or "AGPL3 or later"); this is the case for the GNU project. Many projects don't do that, which may make it more difficult to be uploaded to Debian (sometimes a little more, sometimes a whole lot more). The clearer the better, and as a bonus it saves a lot of time to the people who are in charge of verifying the license of the software: if you can do that then that's the best; if not, try to be as clear as possible and cross fingers. It is not mandatory, but it is possible to format debian/copyright with a machine-readable format [1] It would be nice to also produce a "-doc" package containing the documentation [2], so that people with internet connectivity issues can still read the documentation. Through .gitlab-ci.yml you auto-generate debian/changelog. I doubt an auto-generated changelog can be used if you want your package integrated in Debian: end users should be able to modify your package at will, and add what they want to the changelog. In debian/postinst it looks like a password is stored into /etc/dmx/config.properties, but I don't see any provision (such as umask 077) to make sure it is not world-readable before "chmod 750 /etc/dmx". For you to check... debian/rules contains comments from the template; you should probably clean them up. I don't know debconf, but at what point is the equality between dmx/initial_admin_password and dmx/initial_admin_password_again checked? Once you have built the source package and the binary package(s) locally, you should run "lintian -EviIL+pedantic" to see if you have any important things to fix. One of the first things you need to make clear is how you want to create your package(s): - By building the upstream source (main)? By packaging the upstream binary (contrib)? - How do you organize the packaging files and your workflow for creating packages: with origtargz(1), uupdate(1), git-dpm, git-buildpackage, something else...? [1] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ [2] https://dmx.readthedocs.io/en/latest/ Hope this helps! Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#953333: RFS: python-opentracing/2.3.0-1 [ITP] -- opentracing interface for Python
Note that 2.2.0-1 is still in the NEW queue: https://ftp-master.debian.org/new/python-opentracing_2.2.0-1.html
Bug#953333: RFS: python-opentracing/2.3.0-1 -- opentracing interface for Python
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-opentracing" * Package name: python-opentracing Version : 2.3.0-1 Upstream Author : The OpenTracing Authors. * URL : https://github.com/opentracing/opentracing-python * License : Expat and Apache-2.0 * Vcs : https://salsa.debian.org/python-team/modules/python-opentracing Section : python It builds those binary packages: python3-opentracing - opentracing interface for Python python-opentracing-doc - opentracing interface for Python - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-opentracing Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-opentracing/python-opentracing_2.3.0-1.dsc Changes since the last upload: * New upstream release 2.3.0. Regards, -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#951804: RFS: golang-github-jfrog-gofrog/1.0.5-1 [ITP] -- Gofrog collection of go utilities (library)
Package: sponsorship-requests Severity: wishlist Dear Mentors and Go Packaging Team, I am looking for a sponsor for my package "golang-github-jfrog-gofrog": * Package name: golang-github-jfrog-gofrog Version : 1.0.5-1 Upstream Author : 2016 JFrog Ltd. * URL : https://github.com/jfrog/gofrog * License : Apache-2.0 * Vcs : https://salsa.debian.org/go-team/packages/golang-github-jfrog-gofrog Section : devel It builds those binary packages: golang-github-jfrog-gofrog-dev - Gofrog collection of go utilities (library) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-jfrog-gofrog Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-jfrog-gofrog/golang-github-jfrog-gofrog_1.0.5-1.dsc Changes since the last upload: * Initial release (closes: 950588) Thanks! Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#945178: RFS: opentracing-python/2.2.0-1 [ITP] -- opentracing interface for Python
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "opentracing-python" * Package name: opentracing-python Version : 2.2.0-1 Upstream Author : The OpenTracing Authors. * URL : https://github.com/opentracing/opentracing-python * License : Expat and Apache-2.0 * Vcs : https://salsa.debian.org/python-team/modules/opentracing-python Section : python It builds those binary packages: python3-opentracing - opentracing interface for Python python-opentracing-doc - opentracing interface for Python - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opentracing-python Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opentracing-python/opentracing-python_2.2.0-1.dsc Changes since the last upload: [ Fabrice BAUZAC ] * Initial release, closes: #942069. Thanks! Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D