Re: Python Policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-20 22:53, Barry Warsaw wrote: > +Any·Debian·developer·who·wishes·to·integrate·his·packages·in·the·team ·can·do > > +so·without·requesting·access·(as·the·repository·is·writable·by·all·DD). ·If·one >

Re: DPMT Policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-22 11:30, Piotr Ożarowski wrote: >> i have to admit i'm not totally used to an reviewing git patches >> per mailinglists, and in this case i got lost a little bit what >> the current draft is. would it be possible to put a complete >>

Re: Python Policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-20 22:53, Barry Warsaw wrote: > +Any·Debian·developer·who·wishes·to·integrate·his·packages·in·the·team ·can·do > > +so·without·requesting·access·(as·the·repository·is·writable·by·all·DD). ·If·one >

Re: Python Policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-21 15:54, Barry Warsaw wrote: > Hopefully, the latest changes (see previous follow up) are both > more concise and coherent. maybe. i have to admit i'm not totally used to an reviewing git patches per mailinglists, and in this case i

Re: Python Policy

thanks a lot for preparing all this. On 10/20/2015 10:53 PM, Barry Warsaw wrote: > +DPMT requires upstream tarballs; releases cannot be made from upstream git > +repositories directly. This is because PyPI contains upstream tarballs, and > +tarballs are what we upload to the Debian archive. i

git instead of svn in policy (was Re: team vs individual as maintainer)

On 10/16/2015 11:53 PM, Piotr Ożarowski wrote: > (it still clearly states we use SVN only, though!) since you have already mentioned this a few times: how about changing the policy then, to clearly state that we use GIT only? as you haven't done that yet, i guess there is some catch; but since i

Re: Python Policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-21 02:17, Ben Finney wrote: > "IOhannes m zmölnig (Debian/GNU)" <umlae...@debian.org> writes: > >> thanks a lot for preparing all this. >> >> On 10/20/2015 10:53 PM, Barry Warsaw wrote: >&g

Re: packages missing from https://anonscm.debian.org/cgit/python-modules/packages/

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-12 08:56, Brian May wrote: > Hello, > > Why are packages missing from anonscm.debian.org which are on > git.debian.org? > > e.g. > > https://anonscm.debian.org/cgit/python-modules/packages/django-model-u tils.git > > >

Re: [DPMT] radical changes: automation, carrot and stick

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-07 14:18, Piotr Ożarowski wrote: > I no longer think requiring contribution (the 3 months thing) is a > good idea for DPMT (might be for a new team). > > I assume you all like other ideas, like no team in Maintainer, > right? if that's

Re: Git migration schedule

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-05 23:24, Barry Warsaw wrote: > On Oct 05, 2015, at 10:36 PM, Stefano Rivera wrote: > >> How about: We move away existing repositories, and put the >> migrated ones in the /packages/ path. If people have existing >> repositories, that

Re: Git migration schedule

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-04 23:06, Stefano Rivera wrote: > Hi Sandro (2015.10.04_21:31:07_+0200) >> sorry, i forgot to ask another question: how will the packages >> already maintained in git be handled? > > Up to their maintainers (assuming they're following

Re: [DPMT] radical changes: automation, carrot and stick

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-02 10:30, Piotr Ożarowski wrote: > it's 3 months to contribute to other packages (the ones where > you're not listed in Maintainer). hmm. if i - hypthotically, because i really currently do not - cared a so much about e.g. 30 DPMT

Re: [DPMT] radical changes: automation, carrot and stick

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-02 18:12, Nikolaus Rath wrote: > On Oct 02 2015, Piotr Ożarowski wrote: >> I think that the main problem of our team is that we have over >> 300 members and only few people contribute to packages they >> didn't inject

Re: Pushing a bunch of packages to jessie-backports

On 2015-11-26 09:32, Piotr Ożarowski wrote: > PS I didn't "kick" him, i think the kick in question is not your disapproval of the current affair, but referring to past action <560c3acd.9000...@debian.org>. fgmasdr IOhannes

Re: How to split modules in multiple deb packages

On 2017-02-18 09:16, Simone Rossetto wrote: > One of the module is specific for Raspberry Pi, it adds some > functionalities, but > the daemon itself doesn't require a Pi hardware and can still do its job > without that module even on a Pi. What I want to do is to split the modules > in two deb

Re: Binary naming for Django Related Packages

On 2017-01-18 07:46, Scott Kitterman wrote: > +··named·django_packagename·upstream.··These·are·then·packaged·as > +··python3-django-package·and please use "package" vs "packagename" consistently. e.g. an upstream named "django_packagename" should be packaged as

Re: pypi2deb 1.20160809 and --profile dpmt

On 08/09/2016 09:27 PM, Piotr Ożarowski wrote: > > FYI: I just uploaded pypi2deb 1.20160809 which initializes all the git-dpm > stuff if you invoke py2dsp with --profile dpmt option OMG: i just discovered pypi2deb and its wonderful. unfortunately i missed this mail when it was sent (or - more

Re: Issue on setup.py with imports

On 2016-09-03 10:18, Marcos wrote: > I'm migrating Gufw [1] from python2 to python3 and honestly I'm stuck > with an error from the setup.py: Python module controller not found: > > costales@dev:~/Desktop/16.10$ sudo python3 setup.py install --prefix=/usr > ERROR: Python module controller not

Bug#836163: ITP: python-bottle-cork -- authentication for the bottle web framework

Package: wnpp Severity: wishlist Owner: "IOhannes m zmölnig (Debian/GNU)" <umlae...@debian.org> * Package name: python-bottle-cork Version : 0.12.0 Upstream Author : Federico Ceratto <federico.cera...@gmail.com> * URL : http://cork.firelet.net/ *

Re: Bug#837805: Acknowledgement (ITP: python-can -- Controller Area Network interface module for Python)

message was also forwarded to > debian-python@lists.debian.org, debian-de...@lists.debian.org > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > w...@debian.org > IOhannes m zmölnig (Debia

Re: policy question: tag format for patch-less packages

On 11/16/2016 06:07 AM, chrysn wrote: > Should git-dpm be used even though no patches are present? how do you make sure that you will never need patches? (unless this is a native package) gfmards IOhannes signature.asc Description: OpenPGP digital signature

Re: [Python-modules-team] python-pip ancient version 1.5 for Debian 8

On 06/08/2017 01:08 PM, Brian May wrote: > CCing to correct mailing list. debian-python@lists.debian.org > > I don't actually understand the issue. jessie: python-pip_1.5.6-5 stretch: python-pip_9.0.1-2 no backports. i guess the OP has problems using pip as packaged in jessie with newer

Re: DPMT and git workflows

On 01/19/2018 12:45 PM, Simon McVittie wrote: > On Fri, 19 Jan 2018 at 14:25:57 +0300, Dmitry Shachnev wrote: >> I think for new packages it is better to use gbp-pq based workflow: >> https://wiki.debian.org/Python/GitPackagingPQ > > Is there consensus that the gbp-pq workflow is now allowed? I

Re: Move to salsa? Team structure preview ready

thanks for taking the lead. On 2018-02-08 15:16, Ondrej Novy wrote: > > But I don't think all DD are masters in our team. This is true only > for 'Debian' team. Even if you are DD, you need to join team or > subteam to have commit access to it. i think this is true. at least i had to request

Re: pyapi-gitlab vs python-gitlab

On 02/09/2018 05:19 AM, Paul Wise wrote: > On Fri, Feb 9, 2018 at 11:17 AM, Scott Kitterman wrote: > >> I'd encourage you to work with the upstreams to deconflict the namespace. >> This isn't really a problem Debian should solve. > > Good point, I've contacted them via email and will file

Re: pybuild mysteriously does not copy all testfiles

On 10.09.19 16:14, Ole Streicher wrote: > Hi IOhannes, > > I have basically the same problem, funnily with almost the same subject: which was entirely intentional :-) i decided to start a new thread because i'm not sure whether the problem is really the same. but i guess, i'll just file a bug

pybuild mysteriously does not copy all testfiles

updating one of my packages (python-can), the test-suite started to fail, with an error-code 5, indicating that "no tests have been run". since there *are* tests to be run, i investigated and - after scratching my head - found that 'pybuild' did not fully copy the test-directory from the

Re: debian/watch: How to watch version tags and what to capture?

On 9/17/23 10:41, c.bu...@posteo.jp wrote: Hello, maybe it depends on my non-nativ English that I'm not able to make myself clear. On 2023-09-17 09:56 Mechtilde Stehmann wrote: What do you expect? As I told. Information just in time. Within in a delay of 1 or 2 hours the tracker/dashboard

joining the team

hi all, i would like to join the python modules team, mainly to maintain a few python-modules (who would have guessed that?), that I need as dependencies for other packages I maintain. I'm a long-term Debian user, and have become involved in packaging as late as ~2010, when I joined the

DPMT: server-side git hooks

hi all, while toying around with managing a few python packages in git, i noticed that the post-receive hook installed by the setup-repository script is not working as advertised. for one thing, it complains that dam.homelinux.net:9418 is unreachable (and indeed that name cannot be resolved via