Re: RFS: python-unipath -- object-oriented approach to file/pathname manipulations
On Fri, Oct 28, 2011 at 12:34 AM, Arnaud Fontaine wrote: > Andrew Starr-Bochicchio writes: > >> I am looking for a sponsor for my package "python-unipath". It is >> needed as it is a dependency for new upstream versions of trash-cli. I >> would like to maintain it as part of the Python Modules Packaging >> Team. I've just applied on alioth for svn access. My username there is >> andrewsomething-guest. > > As no sponsor seems to have stepped up yet, I would happily sponsor this > package. snip... > Besides of that, your packages looks fine. Let me know when your package > is available in the SVN and you have made the changes mentioned above > and I will upload it. Thanks for the very helpful review. No one has gotten back to me on my request to join the project, so I still can't add this to SVN. I've re-uploaded the package to mentors. It should fix all of the issues you brought up. It can be retrieved with: dget -x http://mentors.debian.net/debian/pool/main/p/python-unipath/python-unipath_0.2.1+dfsg-1.dsc Thanks! -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Maintainer <http://qa.debian.org/developer.php?login=a.starr.b%40gmail.com> PGP/GPG Key ID: D53FDCB1 -- 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/CAL6k_Ax8KV8Ks7kc4Wj5g18qmYMYbRLhmYFPfQmJK2=fyyk...@mail.gmail.com
Re: RFS: python-unipath -- object-oriented approach to file/pathname manipulations
On Fri, Oct 28, 2011 at 10:43 PM, Arnaud Fontaine wrote: > Hi, > > Andrew Starr-Bochicchio writes: > >> Thanks for the very helpful review. No one has gotten back to me on my >> request to join the project, so I still can't add this to SVN. > > It seems that you have already been added[0]. Piotr added me shortly after my last message. (Thanks Piotr!) I'm getting permission denied errors when trying to use svn-inject. I hear that it can take up to 24 for hours for alioth account changes to take effect on the unix account. So I'll wait a bit longer. >> I've re-uploaded the package to mentors. It should fix all of the >> issues you brought up. It can be retrieved with: > > Thank you very much. I will upload it this evening or tomorrow then. Thank you! -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Maintainer <http://qa.debian.org/developer.php?login=a.starr.b%40gmail.com> PGP/GPG Key ID: D53FDCB1 -- 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/cal6k_ax87sg0d86p1kecut_kbe5mu1876gbm-7cvef_kjrv...@mail.gmail.com
Re: Bug#693335: RFS: pymarkups/0.2.3-1
On Sun, Nov 25, 2012 at 9:29 AM, Dmitry Shachnev wrote: > Control: retitle -1 RFS: pymarkups/0.2.4-1 > > Fixed these two issues, uploaded updated package to > mentors.debian.net. Can anybody upload it now please? > > The new .dsc file can be found at: > http://mentors.debian.net/debian/pool/main/p/pymarkups/pymarkups_0.2.4-1.dsc. I had previously taken a look this package, and with Jakub's concerns addressed it should be in good shape. I'll take one more look at it, and unless I find something else I'll upload it shortly. I just got this shinny new @debian.org address last week, and it's about time I return the favour of sponsorship that others had given me. Thanks, -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- 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/cal6k_ax98pbom1okjutbffbvyqbykxjzcmbvhdvyjgm6_p0...@mail.gmail.com
Re: Solving the multiarch triplet once and for all
On Tue, Dec 18, 2012 at 10:24 AM, Barry Warsaw wrote: > On Dec 18, 2012, at 02:22 PM, Julien Cristau wrote: >>Having some explanation of what's going on would definitely help. Is >>there a wiki or mailing list url that I missed and that describes what >>this is about? > > I don't think you missed anything specific to Python. The Debian multiarch > effort is described in this wiki page (with lots of sub-links): This is the only thing I've come across: http://wiki.debian.org/Python/MultiArch -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- 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/cal6k_azayckgr8xdkwgp8-wshrcwve_wfgbywzuenkinvot...@mail.gmail.com
Bug#710060: ITP: pyflot -- interface from Python to libjs-flot
Package: wnpp Severity: wishlist Owner: "Andrew Starr-Bochicchio" * Package name: pyflot Version : 0.1 Upstream Andre da Palma * URL : http://github.com/andrefsp/pyflot * License : MIT Programming Lang: Python Description : interface from Python to libjs-flot PyFlot makes it easy to generate flot graphs. Its primary goal is to allow one to specify data inputs and options in a Python application and generate the appropriate JSON. Common uses of this are rendering into a template as flot() arguments or as the payload of an XHR response. PyFlot takes care of all the annoying details of converting types to match up with how flot expects them. -- 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/20130527231332.6190.80525.reportbug@asb-laptop
Re: Indeed, python-concurrent.futures is the same
On Sat, Jan 25, 2014 at 3:53 PM, Thomas Goirand wrote: > I'm however confused how "import concurrent" works, even if there's > nothing in /usr/lib/python2.7/dist-packages in this package. How come? Take a look at /usr/share/doc/python-support/README.gz > * Public modules (.py files that should be installed in the default >sys.path) are handled through a foo.public file, which contains a >list of files to install. The files are normally installed in >/usr/share/pyshared/. They will be installed and bytecompiled in each >Python specific directory: /usr/lib/pymodules/pythonX.Y/. If the header >of the foo.public file contains a "pyversions=..." field, it will be >parsed for the list of python versions the module supports. It should >look like e.g.: > 2.2,2.4- >for a package supporting python2.2, and all versions starting from >python2.4. Also from Python Policy: > Modules managed by python-support are installed in another directory > which is added to the sys.path using the .pth mechanism. https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- 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/CAL6k_AxQmuEtOgqV2u38D9P=98baja+esrs-mcfagnk3obj...@mail.gmail.com
Re: HELP: something other than dh_python2 fails to install files if an additional binary package is added
On Tue, Feb 11, 2014 at 4:21 AM, Andreas Tille wrote: > On Tue, Feb 11, 2014 at 09:48:43AM +0100, Piotr Ożarowski wrote: >> [Andreas Tille, 2014-02-11] >> > directory. I can reproduce this behavious by simply deleting the >> > python-pysam-tests paragraph in debian/control. >> >> this part is very important > > Obviously. > >> > It seems that there is some problem in dh_python (or a related tool >> >> argh! dh_python2 doesn't install files :-P > > So what exactly *stopped* installing files since a new binary package > was added? Normally, when you produce a single binary package, the things get installed into debian/$package_name. If you create a second binary package by creating a new paragraph in debian/control and doing nothing else, the files are installed into debian/tmp. So you then need to move the files that you want to end up in each package to the corresponding directories. >From `man dh_install`: > maybe you have a large package that builds multiple binary packages. You can > use the upstream Makefile to install it all into debian/tmp, and then use > dh_install > to copy directories and files from there into the proper package build > directories. What it means by "the proper package build directories" is that by the end of the build process, everything that will be in the resulting foo.deb will be found in debian/foo. The files that will end up in foo-data.deb will be found in debian/foo-data. -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- 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/cal6k_aypeww6ltta00afky2wccevvl4rrmstejjazu2wiwf...@mail.gmail.com
Future of django-pagination in Debian
The Debian package of django-pagination was orphaned last year. [0] I hadn't noticed until someone stepped up and actually filed an orphan bug just the other week. [1] I intend to adopt it for the DPMT, and I have a release ready to upload in the team's svn repo. In the process of preparing the upload, I came across the fork you did incorporating bug fixes and translations the the original maintainer had left sitting around. [2] As upstream hasn't made a commit in ~4 years, your work it probably the best way forward. I wanted to solicit your (and the DPMT's) opinion on how to best handle this from the Debian side. There are a few options. The first is simply upgrading to your fork directly, which would be the most user friendly. Though the top level package name was changed from `pagination` to `linaro-django-pagination`. [3] That would suggest that a new source package would be in order. If I packaged linaro-django-pagination, should we just ask for the removal of django-pagination, or keep it around? Any one have any opinions? [0] http://packages.qa.debian.org/d/django-pagination/news/20130505T150425Z.html [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737294 [2] https://github.com/zyga/django-pagination [3] https://pypi.python.org/pypi/linaro-django-pagination/ Thanks! -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- 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/cal6k_aweynfsjscfcz+-u4tephw5z-ugdhg7wydyqoyk5pg...@mail.gmail.com
Re: Future of django-pagination in Debian
On Tue, Feb 11, 2014 at 10:12 PM, Paul Wise wrote: > On Wed, Feb 12, 2014 at 11:02 AM, Andrew Starr-Bochicchio wrote: > >> Any one have any opinions? > > How does the upstream Django community recommend to do pagination? Not sure if there is any official consensus. There are some built-in tools in Django which are fairly low-level, [0] but there are also a number of modules that have sprouted up to simplify things further (i.e. django-bootstrap-pagination, [1] django-endless-pagination [2]). In case github popularity is a useful judge: Project Stars Forks django-pagination412 166 django-bootstrap-pagination 5726 django-endless-pagination12926 django-pagination is packaged for Fedora, OpenSUSE, and (of course) Ubuntu. While django-endless-pagination seems to only be packaged for OpenSUSE and django-bootstrap-pagination doesn't seem to be packaged for any of the "big" distros. Arch packages the Linaro django-pagination fork as django-pagination-git. [0] https://docs.djangoproject.com/en/dev/topics/pagination/ [1] https://github.com/jmcclell/django-bootstrap-pagination [2] https://github.com/frankban/django-endless-pagination Thanks! -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- 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/cal6k_azef5qlk-dqd-3v9vpham2w6futpj3fyb84ad-bkat...@mail.gmail.com
Re: Explanation of tags from Lintian (and Lintian4Python) (was: Packaging review)
On Sun, Mar 23, 2014 at 7:28 PM, Ben Finney wrote: > I think Lintian4Python installs a 'lintian4py-info(1)' command to do the > same thing. You can then get an explanation with:: > > $ lintian4py-info --tags missing-dependency-on-byte-compilation-helper It's still not particularly informative: $ lintian4py-info --tags missing-dependency-on-byte-compilation-helper E: missing-dependency-on-byte-compilation-helper N: N: N: Severity: serious, Certainty: possible N: N: Check: python/bytecompilation, Type: binary, source N: -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- 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/cal6k_axxopurdpvw-cf0sz1mkhgux7tkuhumm6dukrik9fl...@mail.gmail.com
Bug#753949: smartypants: Please package newer upstream release (1.8.5)
Source: smartypants Severity: normal Hi! There have been a number of releases made since the last upload to Debian. I'd love to see a more recent release make it in before the freeze. Would you be interested in a co-maintainer? Ideally, we could add the package to the Debian Python Modules Team (DPMT). The same goes for python-typogrify which I filed #744978 on sometime back. Thanks! - Andrew Starr-Bochicchio -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-29-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20140706162237.23694.47769.reportbug@asb-laptop
Bug#753962: ITP: ghp-import -- Easily import docs to your gh-pages branch
Package: wnpp Severity: wishlist Owner: "Andrew Starr-Bochicchio" * Package name: ghp-import Version : 0.4.1 Upstream Author : Paul Joseph Davis * URL : https://github.com/davisp/ghp-import * License : Tumbolia Public License Programming Lang: Python Description : Easily import docs to your gh-pages branch ghp-import is a Python script meant to make using GitHub's gh-pages branches for hosting documentation simple. . Inside your repository just run `ghp-import $DOCS_DIR` where $DOCS_DIR is the path to the built documentation. This will write a commit to your gh-pages branch with the current documents in it. While I'm no fan of license proliferation, the Tumbolia Public License seems to meet the requitements of the DFSG. > Copying and distribution of this file, with or without modification, > are permitted in any medium without royalty provided the copyright > notice and this notice are preserved. > > TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION > > 0. opan saurce LOL Thoughts? Thanks! - Andrew Starr-Bochicchio -- 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/20140706171449.24962.47936.reportbug@asb-laptop
Re: python-django-contact-form maintenance
On Sun, Oct 11, 2015 at 10:49 AM, Christophe Siraut wrote: > I do not intend to continue maintaining python-django-contact-form, I > just removed myself from the uploaders field, maintainer is DPMT. > Tests are currently failing and package fails to build from source. > Upstream released a new version 3 months ago. Added myself to Uploaders and made an upload bringing in the new version and resolving the build failure. Thanks, -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1
Re: python-django-contact-form maintenance
On Sun, Oct 11, 2015 at 2:29 PM, W. Martin Borgert wrote: > On 2015-10-11 16:49, Christophe Siraut wrote: >> I do not intend to continue maintaining python-django-contact-form, I >> just removed myself from the uploaders field, maintainer is DPMT. >> Tests are currently failing and package fails to build from source. >> Upstream released a new version 3 months ago. > > Christoph, can you confirm that upstream moved from bitbucket to > github? Seems to be here: > https://github.com/ubernostrum/django-contact-form > Just to confuse me further, there is another, older project with > the same name: > https://github.com/jbergantine/django-contact-form GitHub is where the source of the package on PyPi originates from: https://pypi.python.org/pypi/django-contact-form/1.1 -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1
