Package upgrade needs deletion of config file in ~/
Hello. What is the preffered way of handling situations where a configuration file in ~/ needs to be deleted upon package upgrade? Regards Andreas Noteng -- 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/511a4ff1.9070...@noteng.no
How does team maintenace of python module works?
Hi, Because I'm currently packaging Openstack Grizzly, which will be out next April, I need a newer version of python-mock. So I filled: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699147 but no reply so far, and this worries me. I haven't done the bug fillings for other python modules which I'm concerned about, but the problem will be the same for others. So I wonder, how is the python module packaging policy? Since this module is marked as team maintained, and that I've been accepted in the python module packaging team on Alioth, am I allowed to just refresh the package, and upload version 1.0 in debian experimental? Or do I need approval from current uploaders? What does it mean for a package to be team maintained in the python packaging team? Cheers, Thomas Goirand (zigo) -- 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/511a58fa.5040...@debian.org
Re: Package upgrade needs deletion of config file in ~/
fresh entry in debian/NEWS and probably debian/changelog ? On Tue, 12 Feb 2013, Andreas Noteng wrote: Hello. What is the preffered way of handling situations where a configuration file in ~/ needs to be deleted upon package upgrade? Regards Andreas Noteng -- Yaroslav O. Halchenko http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20130212150407.ga8...@onerussian.com
Re: How does team maintenace of python module works?
Hi Thomas, On Tue, Feb 12, 2013 at 7:00 PM, Thomas Goirand z...@debian.org wrote: ... So I wonder, how is the python module packaging policy? Since this module is marked as team maintained, and that I've been accepted in the python module packaging team on Alioth, am I allowed to just refresh the package, and upload version 1.0 in debian experimental? Or do I need approval from current uploaders? What does it mean for a package to be team maintained in the python packaging team? If the team is in Maintainer field, I think you can freely upload the new version. See http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin#Policy_About_Maintainer_and_Uploaders_Fields for details. The same should apply to PAPT as well. -- Dmitry Shachnev -- 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/cakimphvb1xmozwmteb_+aauzj_3axxtnldjd2v30fwl2n+q...@mail.gmail.com
Re: Package upgrade needs deletion of config file in ~/
Andreas Noteng andr...@noteng.no writes: Hello. What is the preffered way of handling situations where a configuration file in ~/ needs to be deleted upon package upgrade? There is nothing the package can do, touching files under the users home directory is not allowed by policy (and for a very good reason). If it really is impossible for the program to update it's configuration, it should probably on startup show the user an error message containing instructions on what to do. -- Arto Jantunen -- 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/871ucly3u7@kirika.int.wmdata.fi
Re: How does team maintenace of python module works?
On 12 February 2013 15:08, Dmitry Shachnev mity...@gmail.com wrote: Hi Thomas, On Tue, Feb 12, 2013 at 7:00 PM, Thomas Goirand z...@debian.org wrote: ... So I wonder, how is the python module packaging policy? Since this module is marked as team maintained, and that I've been accepted in the python module packaging team on Alioth, am I allowed to just refresh the package, and upload version 1.0 in debian experimental? Or do I need approval from current uploaders? What does it mean for a package to be team maintained in the python packaging team? If the team is in Maintainer field, I think you can freely upload the new version. See http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin#Policy_About_Maintainer_and_Uploaders_Fields for details. But please join the team and update the svn repository, or alternatively ask somebody from the team to commit your upload. Regards, Dmitrijs. -- 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/CANBHLUj8e2LVJzSYcERve7+t33cANU+2w=q1cref0zhmheo...@mail.gmail.com
Re: PIL/python-imaging becomes a python package and gets Python3 support
On Feb 12, 2013, at 12:49 AM, Dmitrijs Ledkovs wrote: Debian HPIJS and HPLIP maintainers pkg-hpijs-de...@lists.alioth.debian.org hplip Matthias Klose d...@debian.org python-reportlab Does this mean that hplip python-reportlab are now have all their dependenices ported to python3 and hence can also be ported? \o/ I *think* so. AFAICT, there's no public vcs available for python-reportlab, but there is this github repo which reportedly ports it to Python 3. Seems active-ish: https://github.com/nakagami/reportlab but setup.py fails for me with Python 3.3 (could be shallow). I'm not aware of any work to get hplip ported to Python 3. -Barry -- 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/20130212103031.7765e...@anarchist.wooz.org
Re: How does team maintenace of python module works?
On 02/12/2013 11:13 PM, Dmitrijs Ledkovs wrote: On 12 February 2013 15:08, Dmitry Shachnev mity...@gmail.com wrote: Hi Thomas, On Tue, Feb 12, 2013 at 7:00 PM, Thomas Goirand z...@debian.org wrote: ... So I wonder, how is the python module packaging policy? Since this module is marked as team maintained, and that I've been accepted in the python module packaging team on Alioth, am I allowed to just refresh the package, and upload version 1.0 in debian experimental? Or do I need approval from current uploaders? What does it mean for a package to be team maintained in the python packaging team? If the team is in Maintainer field, I think you can freely upload the new version. See http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin#Policy_About_Maintainer_and_Uploaders_Fields for details. But please join the team and update the svn repository, or alternatively ask somebody from the team to commit your upload. Regards, Dmitrijs. Hi, Thanks for both of your replies. I've joined the team on Alioth already. The only problem is that I quite hate SVN (mostly because I never learn it). Don't you guys have plans to switch to git at some point? I've seed that in /git/python-modules/packages there's already 3 packages. Is it fine to switch to Git? There's a bunch of python modules which I maintain for Openstack. I'd happily move them in the /git/python-modules/packages repository. :) Cheers, Thomas -- 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/511a6a84.8000...@debian.org
Re: How does team maintenace of python module works?
* Thomas Goirand z...@debian.org, 2013-02-13, 00:15: The only problem is that I quite hate SVN (mostly because I never learn it). Don't you guys have plans to switch to git at some point? I've seed that in /git/python-modules/packages there's already 3 packages. Is it fine to switch to Git? http://lists.alioth.debian.org/pipermail/python-modules-team/2013-January/014959.html -- Jakub Wilk -- 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/20130212162309.ga8...@jwilk.net
Re: How does team maintenace of python module works?
On Wed, Feb 13, 2013 at 12:15:00AM +0800, Thomas Goirand wrote: The only problem is that I quite hate SVN (mostly because I never learn it). Just can use git-svn just fine: 'git svn clone' instead of 'git clone' 'git svn rebase' instead of 'git pull' 'git svn dcommit' instead of 'git push' and the rest is the normal git workflow. Berto -- 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/20130212161842.ga6...@igalia.com
Re: Package upgrade needs deletion of config file in ~/
Den 12. feb. 2013 16:04, skreiv Yaroslav Halchenko: fresh entry in debian/NEWS and probably debian/changelog ? Thanks. I've done this now, along with a friendly message upstream begging for these changes to be handled more elegantly by the application in the future. Andreas -- 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/511aa3b6.9060...@noteng.no
Re: RFR: python-astropy -- Core functionality for performing astrophysics with Python
* Ole Streicher debian-de...@liska.ath.cx, 2013-02-12, 14:46: http://mentors.debian.net/debian/pool/main/p/python-astropy/python-astropy_0.2~b2-1.dsc Where can I download .orig.tar from? uscan says: Newest version on remote site is 0.1, local version is 0.2~b2 debian/control contains a mixture of tabs and spaces, ewww. Typo in the package description: affilated - affiliated. Why do these need to be listed explicitly in Depends? libcfitsio3, libexpat1, libsofa-c0, zlib1g Why do you ignore errors from dh_sphinxdoc? Please run tests only if DEB_BUILD_OPTIONS=nocheck is unset. Please run tests against all supported Python versions, not only the default one. You shouldn't write see above in a DEP-5 copyright file. If you don't want to duplicate license text twice, use a stand-alone license paragraph. DEP-5 short license names cannot contains spaces. The package FTBFS here: | debian/rules build | dh build --with python2,sphinxdoc |dh_testdir |dh_auto_configure |debian/rules override_dh_auto_build | make[1]: Entering directory `/build/python-astropy-jrJ5eX/python-astropy-0.2~b2' | dh_auto_build -- --use-system-libraries --enable-legacy | Freezing version number to astropy/version.py | Traceback (most recent call last): | File setup.py, line 82, in module | package_dirs) | File /build/python-astropy-jrJ5eX/python-astropy-0.2~b2/astropy/setup_helpers.py, line 866, in update_package_files | extensions.extend(setuppkg.get_extensions()) | File astropy/utils/xml/setup_package.py, line 25, in get_extensions | ['expat'], ['expat'], include_dirs, library_dirs, libraries) | File /build/python-astropy-jrJ5eX/python-astropy-0.2~b2/astropy/setup_helpers.py, line 1247, in pkg_config | output = subprocess.check_output(command, shell=True) | AttributeError: 'module' object has no attribute 'check_output' | dh_auto_build: python2.6 setup.py build --force --use-system-libraries --enable-legacy returned exit code 1 | make[1]: *** [override_dh_auto_build] Error 1 | make[1]: Leaving directory `/build/python-astropy-jrJ5eX/python-astropy-0.2~b2' lintian4python emits: i: python-astropy source: python-provides-considered-harmful python-astropy i: python-astropy source: python-provides-considered-harmful python-astropy-legacy -- Jakub Wilk -- 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/20130212224339.ga7...@jwilk.net
