Re: Orphaning mu-editor, firmware-microbit-micropython, and their (build)-deps

Hey Nick, Thanks for maintaining mu-editor, my kids are just getting started with it. So I might be interested in taking it over. Are the updates a lot of work? I see the tarball is tagged with dfsg so there's that... .hc Nick Morrott: Dear team, I intend to orphan two of my team

uploading paramiko 3.0.0

paramiko 3.0.0 was released two weeks ago. Any reason to not upload it now? It would be nice to get into bookworm. .hc

Re: Ask for reviewing

Andrey Rahmatullin: On Sat, May 28, 2022 at 06:39:56PM +0430, Danial Behzadi wrote: Hey folks, I recently uploaded my python app to deb-expo. As this is my first packaging experience in Debian, I would love to get some feedback on my packaging to make it better. Here is my package:

Re: The python command in Debian

Piotr Ożarowski: > FTR: I didn't change my mind. /usr/bin/python is still used outside > Debian packages, in /usr/local/bin scripts and applications and I > strongly disagree to touch it. Sometimes breaking things can be helpful. If someone is not aware that something still requires Python

Re: The python command in Debian

Ondrej Novy: > Hi, > > čt 9. 7. 2020 v 15:27 odesílatel Matthias Klose napsal: > >> Describing here a solution which is implemented for Ubuntu focal (20.04 >> LTS). A >> new source package what-is-python (-perl-dont-hurt-me) ships binary >> packages >> python-is-python2,

Re: joining the PAPT

Louis-Philippe Véronneau: > On 20-05-11 17 h 02, Louis-Philippe Véronneau wrote: >> On 20-05-11 16 h 48, Utkarsh Gupta wrote: >>> Hi Hans, >>> >>> On Tue, May 12, 2020 at 2:03 AM Hans-Christoph Steiner >>> wrote: >>>> Ok, this has be

Re: joining the PAPT

not fine with being locked out of my package. .hc Hans-Christoph Steiner: > > Hey all, > > I'm a DD and a long time member of PMPT I would like to join the PAPT. > I am packaging https://github.com/cryptax/droidlysis and I think it > fits best in PAPT. I am also willi

joining the PAPT

Hey all, I'm a DD and a long time member of PMPT I would like to join the PAPT. I am packaging https://github.com/cryptax/droidlysis and I think it fits best in PAPT. I am also willing to be a sponsor for packages I know something about or are simple enough that I can understand them. I have

Re: Streamlining the use of Salsa CI on team packages

Raphael Hertzog: > Hi, > > On Sun, 15 Sep 2019, Louis-Philippe Véronneau wrote: >> For step 1, I proposed we use the "Salsa Pipeline" [1], as I feel it is >> the most mature solution, has more contributors and has more features >> (including reprotest and piuparts). This option seems to have had

Re: Streamlining the use of Salsa CI on team packages

lsa.debian.org/python-team/modules/libcloud/-/jobs/248526 The whole androguard took ~13 minutes: https://salsa.debian.org/python-team/modules/androguard/pipelines Seems like there needs to be some load testing before pushing heavy processes like reprotest and piuparts. > Hans-Christoph Ste

Re: Streamlining the use of Salsa CI on team packages

Gregor Riepl: > >> I am not a fan of pointing to a moving target with the "include" statement: >> >> include: >> - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml >> - >> https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml >> >> "master"

Re: Streamlining the use of Salsa CI on team packages

I think we should definitely use Gitlab-CI! The 'salsa-ci-team/pipeline' project does have good coverage, with reprotest and piuparts. I'm the lead dev on another approach, also part of the salsa-ci-team, called 'ci-image-git-buildpackage':

Re: GitLab CI on salsa.debian.org

it'll run per commit. .hc > On Wed, 2018-03-21 at 15:27 +0100, Hans-Christoph Steiner wrote: >> Since I got only crickets on this email, let me elaborate: gitlab-ci >> lets you run whatever you want as root via Docker images. That means >> its easy to run full builds, ins

Re: Buildbot maintenance by PAPT

* Create an account on salsa and click "request to join" on the team page: https://salsa.debian.org/python-team/applications * Change the Vcs-* tags in debian/control to point to: https://salsa.debian.org/python-team/applications/buildbot * set the Maintainer or Uploaders in debian/control

Re: Help proposed for migration of PAPT repos to Salsa

Joseph Herlant: > Hi, > > I've seen that there are some SVN repositories for PAPT on alioth and > I was wondering if you'd want help to move them to Salsa. > > I'm familiar with the procedure to transfert a repo from svn to git > without loosing the tags, commits, branches, etc and I can do

GitLab CI on salsa.debian.org

One great addition that GitLab gives us is CI builds with custom Docker images, which will run the whole build/test process for each merge request. For example: https://salsa.debian.org/eighthave/python-vagrant/-/jobs/4005 I have set up a prototype Docker image for running git-buildpackage

Re: GnuPG signatures on PyPI: why so few?

Donald Stufft: > >> On Mar 12, 2017, at 10:35 PM, Paul Wise wrote: >> >> On Mon, Mar 13, 2017 at 4:28 AM, Jeremy Stanley wrote: >> >>> upload them to PyPI since the authors of the coming Warehouse >>> replacement for the current CheeseShop PyPI have already indicated >>> that

Re: #850098 subliminal: change of upstream structure

I don't work on any of those packages, but I think your logic makes sense. .hc Carl Suster: > I see that subliminal is currently using the tarballs from PyPI and then > patching in the source for the nautilus extension which is of course > absent from there. Also the Github-hosted tarballs

Re: pip for stretch

Donald Stufft: >> >> On Nov 21, 2016, at 6:33 PM, Barry Warsaw wrote: >> >> I have not started to look at what if anything needs to be done to transition >> to pip 9, but if you have a strong opinion one way or the other, please weigh >> in. >> > > > As one might expect, I

Re: Source package name with python- or without?

Scott Kitterman: On June 9, 2015 9:08:06 AM EDT, Thomas Goirand z...@debian.org wrote: On 06/08/2015 08:13 AM, Piotr Ożarowski wrote: [Tim Landscheidt, 2015-06-08] Should source package names (Source: in debian/control) be prefixed with python-? no. I use python- prefix for source

Re: Resources/best practices for making a .deb out of a virtualenv

I've used python-stdeb to make Debian packages out of standard projects, then you can upload those packages to a PPA like on launchpad.net, and it is also easy to get them into Debian-proper. https://packages.debian.org/python-stdeb Try py2deb or pypi-install from that package. .hc Tim

Re: Keeping upstream commits separate from Debian packaging commits

Barry Warsaw wrote: On Oct 16, 2014, at 09:26 AM, Tristan Seligmann wrote: I would expect it to make merging / rebasing Debian patches on top of a new upstream version easier, since you have the granular history of changes to the source tree, not one massive single commit which may not be

Re: Keeping upstream commits separate from Debian packaging commits

Thomas Goirand wrote: On 10/12/2014 05:15 PM, Tristan Seligmann wrote: I wasn't at Debconf, maybe this is why I'm a bit confused by what you wrote here. pristine-tar and upstream VCS merge are in no way mutually exclusive, but you seem to be implying that they are Using pristine-tar and

Re: Keeping upstream commits separate from Debian packaging commits

Thomas Goirand wrote: On 10/12/2014 05:15 PM, Tristan Seligmann wrote: I wasn't at Debconf, maybe this is why I'm a bit confused by what you wrote here. pristine-tar and upstream VCS merge are in no way mutually exclusive, but you seem to be implying that they are Using pristine-tar and

Re: Keeping upstream commits separate from Debian packaging commits

Tristan Seligmann wrote: On 16 October 2014 18:01, Thomas Goirand z...@debian.org wrote: Using pristine-tar and pulling from upstream VCS is silly. If you do like this, then why not just doing tag-based packaging? That's a lot safer than just re-tagging on top of what upstream does (ie: no

Re: Proposed git migration plan

I think this plan makes a lot of sense. I'll just throw in my two bits for a couple of other points: * the git-buildpackage workflow is really quite wonderful and reasonably flexible, I highly recommend it, and I think it will improve the productivity of this team. * Vcs-Git and Vcs-Browser

Re: policy for source package names

Barry Warsaw wrote: On Aug 05, 2014, at 04:09 PM, Hans-Christoph Steiner wrote: I think it is a good practice to make the source package name the same as the binary package name as long is there isn't a good reason to do otherwise. So with any source package that produces one binary

Re: policy for source package names

olivier.sal...@codeless.fr wrote: On 08/05/2014 12:04 AM, Vincent Cheng wrote: On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino antonio.valent...@tiscali.it wrote: Hi list, I read in [1] and [2] that binary packages with public modules should have the python- (or python3-) prefix in the

upgrading python-libcloud to latest upstream

I'd like to update python-libcloud to the latest (0.14.1) or at least a newer one. In the package's SVN, there is already an 0.10 update in it. Anyone know the status of this? Are there any blockers or shall I just commit and upload? http://packages.qa.debian.org/libc/libcloud.html .hc

Re: Using git-svn and gbp for DPMT - Was: Re: Joining the DPMT and git.debian.org access

On 01/14/2014 09:31 AM, Barry Warsaw wrote: On Jan 14, 2014, at 02:40 PM, Olivier Berger wrote: I've used git-buildpackage with git-svn on submodules of the DPMT SVN repo without too many difficulties so far. I need to spend more time playing with git-bp, but last time I looked at it

Re: Joining the DPMT and git.debian.org access

On 01/14/2014 08:24 AM, Alexandre Rossi wrote: Hi, My goal is to maintain sockjs-twisted (#735154). the problem is... we don't use git, not yet at least (nobody had time to propose a transition) The Wiki page[1] suggests there are some git repositories, but I cannot find/see them. I

Re: RFR: python-qrcode -- native python module to generate QR codes

On 04/14/2013 03:10 AM, Cornelius Kölbel wrote: Am 13.04.2013 05:46, schrieb Hans-Christoph Steiner: On 02/21/2013 03:34 PM, Cornelius Kölbel wrote: Am 21.02.2013 20:42, schrieb Jakub Wilk: * Cornelius Kölbel cornelius.koel...@lsexperts.de, 2013-02-21, 20:14: http://mentors.debian.net/debian

Re: RFR: python-qrcode -- native python module to generate QR codes

On 02/21/2013 03:34 PM, Cornelius Kölbel wrote: Am 21.02.2013 20:42, schrieb Jakub Wilk: * Cornelius Kölbel cornelius.koel...@lsexperts.de, 2013-02-21, 20:14: http://mentors.debian.net/debian/pool/main/q/qrcode/qrcode_2.4.2-1.dsc Great. The mentors site suddenly gives me lintian warnings,

Re: DD requesting to join python-modules-team

On Oct 9, 2012, at 4:48 AM, Jakub Wilk wrote: * Hans-Christoph Steiner h...@eds.org, 2012-10-08, 20:14: I'm a DD that is working on a couple python module packages. I have 'pyjavaproperties' already in wheezy/unstable and python-pure-otr in the works, packaged as 'python-potr' since

DD requiesting to join python-modules-team

hey all, I'm a DD that is working on a couple python module packages. I have 'pyjavaproperties' already in wheezy/unstable and python-pure-otr in the works, packaged as 'python-potr' since that was the original name and the library is still called 'potr', i.e. import potr I'm putting the