Re: Packages that pretend to support Python 2.4

ion isn't as clear as it could be about specifying python-version compatibility. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsu

Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex

gs/0.14.1-1new upstream release I see some trailing whitespace in debian/changelog. Mixed tabs and spaces in debian/postinst (naughty jwilk) SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python

Re: Sponsors and ‘UNRELE ASED ’ suite (was: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex)

n.org/python-modules-policy.html Yes, it does mean the sponsoree has to state which suite is desired. But it saves on a lot of untagging and retagging in each round of review, and makes it a little easier to know the state of things when reading the repo. SR -- Stefano Rivera http://tumblewee

Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex

). If I have to go back and fix something which hasn't been published yet, then there won't be a changelog entry, so I have to provide my own commit message with svn commit. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UN

Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex

link to the wrapper, which you put in /usr/share/didjvu. didjvu is missing a dependency on python-gamera. > Files: debian/* > -Copyright: 2009, 2010 Jakub Wilk > +Copyright: 2010 Daniel Stender I don't think you should forget Jakub, just add yourself. Otherwise no issues I

Re: Compressing objects.inv?

hinx docs subtree...) [0]: http://lists.debian.org/20101108231614.gu12...@onerussian.com SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscr

Re: RFS: didjvu

ike using Breaks: ${python:Breaks}. It separates the Python version dependencies out of Depends. The --with should come after $@: dh $@ --with python2 The DEP5 copyright file doesn't include a revision in the Format. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72

Re: RFS: didjvu

a bit and see if this happens. Otherwise it will probably happen before this gets through NEW. BTW: You have a trailing space, in debian/copyright, and "Upstream-contact" isn't the canonical case. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 4

Re: RFS: didjvu

sted before), this won't be an issue, as it won't need another upload for 2.7 support. You really should consider doing it, this package doesn't need to be in the public python namespace. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419

Re: shebang lines for Python scripts

ot --no-site-packages) virtualenvs for development, and being able to execute things like unit2, twistd, trial, or nose inside the virtualenv. But I do understand why this is wanted. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRI

Re: E: dh_python2:146: you most probably have to build extension for python2.5.

n't. I build with DH_VERBOSE when I want to see what arguments are being passed around, that's about it. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subj

Re: Python Policy Updates

it deprecated? SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.d

Re: Python Policy Updates

handle > it differently). And then there's PEP-384, which may negate this entirely in Python3 for some packages... SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with

Re: Python Policy Updates

. Nobody even uses them for their intended reason. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.

distutils packages fail to build on some buildds at the moment

;, line 329, in find_config_files > check_environ() > File "/usr/lib/python2.5/distutils/util.py", line 205, in check_environ > os.environ['HOME'] = pwd.getpwuid(os.getuid())[5] > KeyError: 'getpwuid(): uid not found: 2952' The buildd admins ar

Re: Help with conversion to dh_python2 needed

ail for the first python version. * The whole loop should be inside a check for DEB_BUILD_OPTIONS's nocheck option. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org w

Re: Starting First Python Transition

's been rebuilt but had a couple of failures will show Red Xs for the failures because new binaries haven't replaced the old "bad" binaries on those architectures yet. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- T

Re: Packaging python programs (with private modules) using the current Python version and binNMU:able when that changes

n't provide pythonX.Y-foo, and many that do don't do it correctly. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble

Re: About the file structure

X.Y/site-packages/, such > as Gwibber, but I think it is a packaging mistake. We switched to dist-packages in Python 2.6. 2.5 still uses site-packages. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-pyt

Re: list of package for python_support -> dh_python2 ?

(and most other debian-python usertags too), but they aren't blockers: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python2.7;users=debian-python@lists.debian.org SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE,

Re: Avoiding download of intersphinx inventories during build

tory shouldn't be a major problem. You could even persuade the upstream to include a cached version. > Should I ship the pickled sphinx environment as a debian patch? This > seems rather fragile.. Yeah, that would be a pretty terrible solution. SR -- Stefano Rivera http://tumblewee

Re: Package upload

, and can review it more quickly. Otherwise, put the packages in the DPMT / PAPT lists in the #debian-python IRC channel topic, or add them to the Todo pages: http://wiki.debian.org/Teams/PythonModulesTeam/TODO http://wiki.debian.org/Teams/PythonAppsPackagingTeam/TODO SR -- Stefano Rive

Re: New python-defaults upload to experimental

s, and call (by default) dh_python2 and/or dh_python3 during the build. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble

Re: python2.7 as default: where are we? (Was: Bug#641207: ITP: ordereddict)

2279 > [1] http://release.debian.org/transitions/html/python2.7.html Nicer view of [0]: http://alioth.debian.org/~stefanor/pytransition/ SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.

Re: Python 2.7 for Squeeze?

e for very few packages, primarily virtualenv. > Because if you have that, you can install what you need into a virtual > env. virtualenv uses python-support, so to get it to work under 2.7, you'd have to change python-support, which means everything else using python-support would have

Re: Magical Python Depends was: Re: Dependencies with cType

lper and some dh_ tools your expectations are different, and magical code inspection sounds horrible and unworkable. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a

Re: Magical Python Depends was: Re: Dependencies with cType

packagers who aren't aware that dh_* programs are documented in manpages... SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". T

Re: Request for Review - Nuitka the Python compiler

ugly and should be avoided). However, we cannot deal with differences like that in scripts in /usr/bin. There's only one of those, shared between all the python versions, so if you put things in it that depend on a particular python version, things get ugly. SR -- Stefano Rivera http://tumble

Re: How do I add support for python3 to my package?

t in the realm of things py2dsc can safely do, yet. Basically, you'd need to override all the dh_auto_* rules to loop over all supported python2 and python3 versions. If you don't need the python3 version, yet, I'd ignore this until the tools improve. SR -- Stefano Rivera http:

Re: How do I add support for python3 to my package?

Hi Paul (2011.11.17_15:17:07_+0200) > Would dh --with python2,python3 not work? I've seen that in some packages > IIRC. No. That'll run dh_python2 & dh_python3, but do nothing to build the module for python3. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 46

Re: Packaging pypy

would be using upstream's HEAD anyway. Of course, it would have to be packaged as a separate Python stack, again. Although it would be interesting to allow modules to be built for alternate Python implementations, but that's not a trivial project... SR -- Stefano Rivera http://tum

Re: Packaging pypy

7;s bytecode format? Do we expect it to change for 2.x-compatible PyPy? SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Tr

Re: Packaging pypy

ere the fun is, right? :) SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http

Re: Packaging pypy

ndergoing language changes, like cpython - for 2.x) Or we just live with a fair amount of PyPy module brokenness while we are bootstrapping the modules. XB-PyPy-Versions? SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, em

Re: Packaging pypy

still rare-ish) for modules with extensions to have variation in pure-python code. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Tr

Re: Packaging pypy

o for a pure-python module package? SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Arc

Re: Packaging pypy

n inside the virtualenv. It then isn't in /usr and so can't find its modules. I'm thinking a better solution here is to *always* look in /usr unless an environment variable (that we'll have set at build time, for the tests) is present. I'm building some binaries now

Re: Packaging pypy

alenv. Grumble, more thought needed. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.

Re: Packaging pypy

ough they aren't from the cleanest build ever) I've kicked off clean amd64 and i386 builds, and will upload the results, when they are complete. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-p

Re: RFS: python-gnatpython [fourth try]

y, and we encourage people to not use ${python:Provides} unless its needed (which is very rare). SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubs

Re: style guide

Hi Dmitry (2012.02.15_17:13:17_+0200) > Does it make any sense to run "setup.py install" for all python3 > versions? Actually the every next python3 version will overwrite what > the previous one writes. That's assuming it's all pure-python. SR -- Stefano Rivera

Re: Possible misbuilt python3 module packages

Hi Scott (2012.03.17_08:08:44_+0200) > Charlie Smotherman >nose (U) I sponsored that, and I've uploaded a rebuild. > Stefano Rivera >python-wadllib Coming soon, together with a fix for LP: #924240, as soon as upstream reviews my patch. SR -- Stef

Re: How do I add support for python3 to my package?

oing write the > neccessary infrastructure so that one could write That was: http://wiki.debian.org/SummerOfCode2011/PythonMultibuild Unfortunately, it stalled. But Piotr is intending to finish it, last I heard. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C

Re: How do I add support for python3 to my package?

;ll also improve a bunch of other situations where dh doesn't handle debian-python's needs (e.g. autotools packages). In the meantime, doing it by hand with overrides really isn't that hard or fragile. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27

Re: how to take a public package private?

o_install: dh_auto_install -- --install-lib /usr/share/openastromod \ --install-scripts /usr/share/openastromod Then symlink /usr/share/openastromod/openastromod to /usr/bin/openastromod. python will dereference the symlink when setting up sys.path. SR -- Stefa

Re: suffix for packages with (optional?) Python extensions

also know of a -helpers (veusz-helpers) +1 to some standardisation. Propose a policy patch? SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe".

Re: Debian python-pywbem IPv6 support

s on Debians pywbem package. > > Will there be any future changes to pywbem ? This seems like a question for the pywbem upstream maintainers. You can find their contact details on the homepage: http://sourceforge.net/apps/mediawiki/pywbem/index.php?title=Main_Page SR -- Stefano Rivera http

Re: Is virtualenv --setuptools still useful?

instead. It'd be nice if we can get the upstream to make distribute the default. I see https://github.com/pypa/virtualenv/issues/217 but it's fairly dead... So, I am affected by this, but don't mind too much if you do it. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461

Re: Packaging applications with extensions modules

. Not going to a problem with 3.x > - dh_python2 (which, for some reason, everyone wants to use) doesn't > generate §3.1.1-compliant dependency for such setup. Yeah, we should fix that. I don't think the problems with C are big enough to warrant changing the policy. I think the

Re: Removing /usr/bin/nosetests-3.x scripts

es on all python3.Xs Cons: - You are creating and deleting things in /usr/bin in maintainer scripts - this made some people cringe. 2 seemed better than 1, and was dead easy. Given the fairly low number of packages using python3-nose, fixing them wasn't hard. SR -- Stefano River

Re: Packaging applications with extensions modules

Hi Jakub (2013.02.22_23:48:24_+0200) > * Stefano Rivera , 2013-02-22, 23:31: > >* you can ship extensions for more than one 3.x version in the > >same private directory, thanks to tags > > Does dh_python3 support such setup? (I would be very surprised if it > did.) You

Re: Packaging applications with extensions modules

tutils, though. So, maybe that's only a very minor issue. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2013023849.gd29...@bach.rivera.co.za

Re: Removing /usr/bin/nosetests-3.x scripts

.Y-dbg which isn't provided. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: ht

Re: Taking over SQLObject package?

so, and ask if he minds you co-maintaining. [0]: http://python-modules.alioth.debian.org/python-modules-policy.html#maintainership SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a

Re: dh-python in unstable

lose the ability to express pypy support in dependencies. > in which case, can pypy2 become an alias for pypy to at least match > python2, python3 ? Those aliases certainly sound like something we want. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419

Re: debian/rules for packages using Cython

fiona_debian/view/head:/rules That's crazily complicated and looks like it's been cargo-culted from multiple other packages? I recommend pybuild for sanity. https://wiki.debian.org/Python/LibraryStyleGuide SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +2

Re: Modest suggestion for pybuild/dhpy2/dhpy3

h :P ) I always used to use set -x shell loops for precisely this reason. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Troub

Re: Proposed changes to python-virtualenv

nt . Won't python 3 users be using python3 -m venv? The only real advantage of virtualenv over venv is bundled pip, but stdlib python has that too, now... SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-pyth

DebConf14 Python BOF notes

ith a list of packages that lack py3 support in Debian. * barry to help with scripting python3 addition for DPMT packages. * piotr to sponsor uploads for dh_pysupport->dh_python2 transition in DPMT. And that's about all. The git migration discussion will come in a separate e-mail. SR

DebConf14 svn->git migration BOF notes

reeze, do that. Say one with dpm, and one with pq, and report back. == End of minutes == I've done some personal investigation since the BOF, and am preparing some really simple migration scripts, so we can get a feel for what it will look like. My scripts so far (very very simple) git://git.

Re: Quick update on git-dpm migration script

svn2git for n revisions, copying git repos, then running another m revisions, etc. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 signature.asc Description: Digital signature

Re: PyPI and debian/watch

’t know if that’s true or not but I certainly think that uscan _should_ > ignore anything that comes after a # (similarly to how it ignores anything > that > comes after a ?). Agreed. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email t

PyCon BoF: Stretch goals for cPython, PyPy & CFFI

multiple interpreters. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150413

Re: PyCon BoF: Stretch goals for cPython, PyPy & CFFI

Hi Scott (2015.04.14_01:20:47_+0200) > What is a /usr/bin/python launcher? I think that was what Donald was asking for. My gut feeling here is that that's a crazy idea. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-pyt

Re: PyCon BoF: Stretch goals for cPython, PyPy & CFFI

om 513b. Still on for 3pm SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150414182725.ga3...@bach.rivera.co.za

Re: Bits from the Debian PyCon Hangout - PyPy

interpreter and a standard, cross-interpreter dist-packages path: /usr/lib/python3/dist-packages/ This isn't a particularly different situation to pypy2, except that there's less legacy cruft (atm) So, I'll attempt to build a pypy3 package for experimental (or something) that uses a

Re: Upstream source merge only when building Debian source (was: Bits from the Debian PyCon Hangout)

n git separately, is conceptually cleaner (and friendlier to the small laptop SSD). But I've given this up as an un-winnable battle. The tools for this workflow aren't as good as full source, and full source is actually kind of nice to work on. SR -- Stefano Rivera http://tumbleweed.

Re: Bits from the Debian PyCon Hangout - /usr/bin/python

or not the change is a massive win for us. There's a long discussion in https://mail.python.org/pipermail/python-dev/2014-September/136374.html That didn't have much in the way of conclusion. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE,

Re: Bits from the Debian PyCon Hangout - PyPy

a dist-packages tree with cpython, without .pyc files clashing. In pypy, that'd be hacky, in pypy3, that'd be by design - this is what PEP3147 set out to solve. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-python-requ...

Re: Bits from the Debian PyCon Hangout - /usr/bin/python

e were many confused people in #python, after Arch did that. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: htt

Re: Bits from the Debian PyCon Hangout - PyPy

as to either depend on both stacks, or the app has to know to depend on pypy3-foo, as well as pypy3-bar. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe&qu

Sample DPMT SVN-GIT migration

do we do about people who've already started using git? I guess they've already shown that they don't care about the package's history... And then there's PAPT... SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to

Re: Sample DPMT SVN-GIT migration

viewed an earlier iteration of the migration. The current one has the experimental upload. Those example packages I mentioned were all from the earlier review, I guess we should double check them :) SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email

Re: Sample DPMT SVN-GIT migration

g we do to all the packages, at a single point in time, not retroactively. > I know we haven't yet decided on a patch regime, but we should... soon! :) Yes, that's the big decision in front of us, now. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCR

Re: Sample DPMT SVN-GIT migration

Hi Barry (2015.05.02_04:37:08_+0200) > I cloned the enum34.git repo, and then did an apt-get source to grab the > orig.tar.gz. Then: There are pristine-tar branches, so you should be able to git-buildpackage -S and get orig tars from them. SR -- Stefano Rivera http://tumbleweed.org.za

python-support removal effort

, wrar, NMUed > pytracer: #786195, wrar, NMUed > pyzor: #786045, piotr, uploaded > sciscipy: 786081, ginggs, done > simpleparse: #786007, larissa, false positive > spkproxy: doko, NMUed > tor-arm: doko, NMUed > trac-graphviz: #786022, arl sponsored by piotr > treeline: #786217, wrar, NMUed > xtalk: #786058 elbrus NMUed > viewmol: #786214, ginggs, done > vim-latexsuite: #786115, pitti, NMUed > w3af: elbrus NMUed > woof: #786030, bdrung, NMUed, sponsored by ginggs > xmldiff: #786023, bdrung > yagtd: #786302 paultag, NMUed > zhpy: doko, NMUed > > > < NMU ALL THE THINGS > > > \ ^__^ > \ (oo)\___ > (__)\ )\/\ > ||w | > || || -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: git migration (AKA missing old good svn days)

s such. I just rolled my thoughts into the migration proposal discussions. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

that several months ago. https://lists.debian.org/debian-python/2015/04/msg00170.html I'll do another run now. I'll also work on an mr config. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

ot; package: pywavelets Cannot "git-dpm init" package: quixote1 Cannot "git-dpm init" package: scandir Cannot "git-dpm init" package: scipy Cannot "git-dpm init" package: sparqlwrapper Cannot "git-dpm init" package: sphinxcontrib-aafig Cannot "git-dpm init" package: svg.path Cannot "git-dpm init" package: tgmochikit Cannot "git-dpm init" package: urlgrabber I think these are mostly because the package has never been uploaded to Debian, or has a new release staged, or has patch problems. Then: liblarch has Orphaned tag commit: b'935216b70ff944f4fdef508a3ad9a53ede9aff93' b'refs/tags/3.0-1' namebench has Orphaned tag commit: b'06ab8961db663cfd9002288ba098cd8aa523f81b' b'refs/tags/1.1+dfsg-1' These, I don't care about. We can't merge the svn head into master on: alembic pycryptopp pyme python-concurrent.futures python-django python-eventlet python-pip python-reportlab python-socksipy Presumably a new upstream release, staged. That's it. Please poke around. Migration scripts: http://anonscm.debian.org/cgit/users/stefanor/dpmt-migration.git/ patches welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

we can strip it down to packages still in the archive (and move everything else off to an attic directory, or something). SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

ic migration at a calmer > moment for python modules. Further automation is a *lot* more work. I don't think it's worth it. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

ldn't be an issue :) SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

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

own? Many of the problems arising from inactive team members are problems that affect the wider Debian, equally. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

come under the same vcs regime, IMHO. One step at a time. The same scripts should work, with minimal tweaks :) SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

t ensures that everything is the same layout. And that any deviation was intentional, not accidental. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

kage, and it gets forgotten. Yeah, I'd like us to quickly sprint through them, too. > Just one problem(?) I do see, some of the commits corresponding to patches > have the following committer: > > Stefano Rivera ... > Suspect it might be a default used because there was no author

Re: Git migration schedule

Hi Barry (2015.10.02_16:24:28_+0200) > 8-Oct - Assuming no objections or showstoppers, turn off write access to all > of DPMT svn. Done. And kicking off the migration now... SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

Hi Brian (2015.10.09_01:52:20_+0200) > Will the migration do packages like python-django? It migrated everything that's in SVN. What happens to the result is up to us. We can replace migrated results with existing git packages. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

Hi debian-python (2015.10.08_17:06:29_+0200) > Done. And kicking off the migration now... And it's done. Things that need to be looked at: http://whiteboard.debian.net/dpmt-git-migration.wb Please mark them off if you've looked at them. SR -- Stefano Rivera http://tumbleweed

Re: Git migration schedule

/GitPackaging Here: https://wiki.debian.org/Python/GitPackaging#Where_do_the_team.27s_git_branches_live.3F SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

Hi Barry (2015.10.10_21:02:00_+0200) > I don't want to wiki-churn so what do you think about backing out this change > and suggesting the ssh config instead? I'd suggest ssh config too. +1. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Git migration schedule

re tags that aren't linked into the rest of the history. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: git.debian.org broken link

django-ajax-selects.git/commit/?id=9d026b46d628f626a0be0d1bf78e826883ac7b71 SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

git repo lint tool

ter-core E: Unknown package: codespeak-lib E: Unknown package: lightblue E: Unknown package: python-sk1libs E: Unknown package: nbformat E: Unknown package: pickleshare E: Unknown package: pyuca E: Unknown package: traitlets E: Unknown package: django-colorful E: Unknown package: nbconvert SR -- Stef

Re: git repo lint tool

Hi Sebastian (2015.10.13_16:57:03_+0200) > codespeak-lib is no longer in the archive. > >breathe > >flask-openid > >python-libdiscid (U) > They are no longer maintained under the DPMT umbrella. Deleted them all, thanks. SR -- Stefano Rivera http://tumblew

Re: git repo lint tool

Hi Daniel (2015.10.13_17:47:01_+0200) > In all packages, Vcs points to > Vcs-Git: git://anonscm.debian.org/python-modules/packages/.git > Vcs-Browser: > http://anonscm.debian.org/cgit/python-modules/packages/.git The linter script wants https for Vcs-Browser. SR -- Stefano R

Re: git repo lint tool

Hi Sandro (2015.10.13_16:48:54_+0200) > On Tue, Oct 13, 2015 at 3:30 PM, Stefano Rivera wrote: > > Many of the non-migrated git repos are a bit of a mess. I've written a > > tool that looks for common problems. > > thanks! could it also emit a hint on how to address the

Re: git repo lint tool

, I was expecting that. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: git-dpm merge conflicts

Hi Brian (2015.10.20_03:54:40_+0200) > When the following error occurs, how can I tell what patch it was > attempting to apply at the time? It's an aborted git rebase, so you should be able to: git show HEAD SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: accidental import with git-buildpackage

-dpm. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

  1   2   3   4   >