How do I include info and man pages in an installer?
I'm trying to make my first .deb package. For that I have read https://www.debian.org/doc/debian-policy/ and https://wiki.debian.org/Packaging/Intro. The latest guide was the most useful for me because I had no experience. Apart from all the warnings from lintian, after building the .deb I could install it and it worked, but the manuals didn't. Now running lintian... W: ducker source: non-native-package-with-native-version W: ducker source: no-debian-copyright W: ducker source: ancient-standards-version 3.9.2 (current is 3.9.5) W: ducker: wrong-bug-number-in-closes l3:#XX W: ducker: copyright-without-copyright-notice W: ducker: spelling-error-in-description searchs searches W: ducker: zero-byte-file-in-doc-directory usr/share/doc/ducker/copyright W: ducker: binary-without-manpage usr/bin/duck W: ducker: binary-without-manpage usr/bin/ducker E: ducker: python-script-but-no-python-dep usr/bin/duck E: ducker: python-script-but-no-python-dep usr/bin/ducker Finished running lintian. The tutorial I read is so basic that it doesn't show how to include the man and info pages. I'm using Sphinx to build the info page and the man page its already build in the repository. I also have a Bash autocompletion file. Anyone can point me in the right direction? There are so many packaging guides and I find most of them very confusing? This is the program I'm trying to package in case you wonder: https://notabug.org/Ducker/ducker
Re: #!/usr/bin/python3 vs virtualenv
Would it be hard to support both philosophies? I would like to suggest a couple of configuration options that by default disallow using pip outside a virtual environment but that users with root privilege can modify by editing a config file (probably somewhere in /etc) and that would enable using pip outside a virtual environment, both as root and as regular user respectively. I feel this would satisfy the needs of regular users to be protected against accidentally breaking their system while enabling power users to have full control of their computer and enjoy the simplicity of a single environment. Clearly this discussion suggests that debian has both types of users and we should support them both if we can. Thank you. On Fri, Mar 3, 2023 at 2:17 PM Jeremy Stanley wrote: > On 2023-03-03 18:44:19 + (+), Danial Behzadi دانیال بهزادی wrote: > > You just want to install sphinx via pip in the virtual environment > > too. Each venv should be atomic and isolated which means not > > depended to system packages. > > However a venv can be made to use system packages if you use the > --system-site-packages option when creating it. > -- > Jeremy Stanley >
Re: #!/usr/bin/python3 vs virtualenv
Jeremy, Thank you for your quick reply! I did not know about `sudo pip install --break-system-packages foo` or `sudo rm /usr/lib/python3.11/EXTERNALLY-MANAGED` (Frankly I only knew about this issue what I have read on this discussion). This is very helpful and it really changes my outlook on this topic. IMHO the existence of these options completely satisfies the requirements of advanced users. In particular because, if I understand it correctly, the second of these options would leave the configuration as it used to be in previous releases of debian for those who want that. So then, for those that raised the issue, were you aware of these approaches? Will either of them satisfy your requirements? And if not, could you elaborate further on why not? Thank you again. On Fri, Mar 3, 2023 at 3:43 PM Jeremy Stanley wrote: > On 2023-03-03 15:29:09 -0500 (-0500), Jorge Moraleda wrote: > > Would it be hard to support both philosophies? > > > > I would like to suggest a couple of configuration options that by default > > disallow using pip outside a virtual environment but that users with root > > privilege can modify by editing a config file (probably somewhere in > /etc) > > and that would enable using pip outside a virtual environment, both as > root > > and as regular user respectively. > > > > I feel this would satisfy the needs of regular users to be protected > > against accidentally breaking their system while enabling power users to > > have full control of their computer and enjoy the simplicity of a single > > environment. Clearly this discussion suggests that debian has both types > of > > users and we should support them both if we can. > [...] > > "Power users" who like to break their systems can simply `sudo pip > install --break-system-packages foo` or even just `sudo rm > /usr/lib/python3.11/EXTERNALLY-MANAGED` and then do whatever they > want anyway. It doesn't seem to me like there's much need for a > config option that does that for you, and adding one would imply > that Debian will help you fix things once you've done it. This > feature is simply a guard rail for users who otherwise wouldn't know > where the edge of that cliff is located. > > There are already solutions for your power users, but as is often > said in such situations: If it breaks you get to keep the pieces. > Have fun! > -- > Jeremy Stanley >
Re: #!/usr/bin/python3 vs virtualenv
FWIW, I am one of those power users that develop python applications and prefer the simplicity of a single environment. In my personal experience, installing using `sudo pip` (or user pip, which I don't do at all) is not a frequent operation for users that choose to manage a single environment. Personally, I use it only after searching in apt and confirming the package is not there. Having to type --break-system-packages every time when I have to do it is a good solution for me that I find completely reasonable. Thank you! On Sun, Mar 5, 2023 at 5:47 AM Julian Gilbey wrote: > On Fri, Mar 03, 2023 at 04:22:11PM -0500, Jorge Moraleda wrote: > > Jeremy, Thank you for your quick reply! > > > > I did not know about `sudo pip install --break-system-packages foo` or > `sudo rm > > /usr/lib/python3.11/EXTERNALLY-MANAGED` (Frankly I only knew about this > issue > > what I have read on this discussion). This is very helpful and it really > changes > > my outlook on this topic. > > The --break-system-packages option is noted in > /usr/share/doc/python3.11/README.venv, and this file is mentioned in > the NEWS file for python3.11. The > /usr/lib/python3.11/EXTERNALLY-MANAGED file is not mentioned there; I > personally think that having to type --break-system-packages every > time one installs a package via pip globally or on a per-user basis is > safer, as it reminds you that you run risks doing so. > > Best wishes, > >Julian >
Bug#737485: RFP: python-django-localflavor -- Country-specific Django helpers
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-python@lists.debian.org * Package name: python-django-localflavor Version : 1.0 Upstream Author : Django Software Foundation * URL : http://github.com/cowboy/grunt/ * License : BSD Programming Lang: Python Description : Country-specific Django helpers Django's "localflavor" packages offer additional functionality for particular countries or cultures. For example, these might include form fields for your country's postal codes, phone number formats or government ID numbers. This code used to live in Django proper -- in django.contrib.localflavor -- but was separated into a standalone package in Django 1.5 to keep the framework's core clean. Cheers, -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org http://metaldot.alucinados.com signature.asc Description: This is a digitally signed message part
[Package Fastaq] - How to incorporate manpages into python package
Hi all, I'm packagin up Fastaq: Vcs-Browser: http://anonscm.debian.org/gitweb/?p=debian-med/fastaq.git Homepage: https://github.com/js21/Fastaq The package builds fine, but lintian is complaining about man pages. I've committed all my work to the debian git repository. I essentially used the same approach as I did for the package snp-sites: http://anonscm.debian.org/cgit/debian-med/snp-sites.git/ Essentially overriding dh_installman and using asciidoc to convert form txt to man. The conversion takes place and the man files are moved to the directory: debian/man. But the man files don't seem to be linked to the python executables once the package is built. There probably is another way to do this in python? Off the top of your head, does anyone know how to fix this? >From [1] I can't really see how to. Kind regards, Jorge [1] - https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-docs
[iva] - Python 3 code depends on pysam
Hi all, I started packaging iva - Iterative Virus Assembler Upstream - https://github.com/sanger-pathogens/iva Debian - http://anonscm.debian.org/cgit/debian-med/iva.git/ The package has several dependencies, but I seem to have stumbled into an annoying one. iva depends on Pysam. But iva is Python3 code. It seems to me that there is no python3-pysam package in Debian. vagrant@debian:~$ apt-cache search pysam python-pysam - interface for the SAM/BAM sequence alignment and mapping format python-pysam-tests - interface for the SAM/BAM sequence alignment and mapping format (test data) python-pysaml2 - SAML Version 2 to be used in a WSGI environment - Python 2.x python-pysaml2-doc - SAML Version 2 to be used in a WSGI environment - doc Looking further into python-pysam: vagrant@debian:~$ aptitude show python-pysam Package: python-pysam State: not installed Version: 0.7.7-1 Priority: optional Section: python Maintainer: Debian Med Packaging Team < debian-med-packag...@lists.alioth.debian.org> Architecture: amd64 Uncompressed Size: 2,233 k Depends: libc6 (>= 2.15), zlib1g (>= 1:1.2.3.3), python:any (>= 2.7.5-5~), cython, python (< 2.8), python (>= 2.7~), python-pyrex Description: interface for the SAM/BAM sequence alignment and mapping format Pysam is a Python module for reading and manipulating Samfiles. It's a lightweight wrapper of the samtools C-API. Homepage: https://github.com/pysam-developers/pysam Does anyone know if python3-pysam will be available soon? Or if there are any plans to have it as a Debian package at all? Kind regards, Jorge
Fwd: [iva] - Python 3 code depends on pysam
Forgot to CC debian python: -- Forwarded message -- From: Jorge Sebastião Soares Date: Mon, Nov 24, 2014 at 11:31 AM Subject: Re: [iva] - Python 3 code depends on pysam To: Debian Med Project List Hi Bary, all On Fri, Nov 21, 2014 at 7:29 PM, Barry Warsaw wrote: > On Nov 21, 2014, at 05:30 PM, Jorge Sebastião Soares wrote: > > >Does anyone know if python3-pysam will be available soon? > >Or if there are any plans to have it as a Debian package at all? > > I took a *very* quick look, but unfortunately don't have time to dig in > deeper. It seems that pysam is Python 3 compatible upstream, and the > Debian > packaging already uses pybuild. It might be as easy as adding --with > python3 > and then adding the appropriate additional binary packaging goodness. > > So, my rules file already has the '--with python3' statement. You can see this in [1] I think the problem is that when calling pysam, it looks inside '/usr/lib/python3/' and pysam is not deployed there. I'll have a look to see what I can find online. Any other suggestions are very welcome. Regards, Jorge [1] - http://anonscm.debian.org/cgit/debian-med/iva.git/tree/debian/rules
Re: Fwd: [iva] - Python 3 code depends on pysam
Hi Piotr, Thanks for having a look. On Mon, Nov 24, 2014 at 11:57 AM, Piotr Ożarowski wrote: > [Jorge Sebastião Soares, 2014-11-24] > > [1] - > http://anonscm.debian.org/cgit/debian-med/iva.git/tree/debian/rules > > just a quick look: > * invoking dh_python3 before dh_auto_build doesn't make sense, remove this > line > So I just let dh_auto_build cal dh_python3 automatically? > * you'd not need "rm -rf build .pybuild" line if you re-enable > dh_auto_clean > So I only override auto_clean to get rid of the man page directory? Best, Jorge
Re: Fwd: [iva] - Python 3 code depends on pysam
Piotr, On Mon, Nov 24, 2014 at 12:26 PM, Piotr Ożarowski wrote: > [Jorge Sebastião Soares, 2014-11-24] > > > http://anonscm.debian.org/cgit/debian-med/iva.git/tree/debian/rules > > > > > > just a quick look: > > > * invoking dh_python3 before dh_auto_build doesn't make sense, remove > this > > > line > > > > > > > So I just let dh_auto_build cal dh_python3 automatically? > > dh_auto_build doesn't call it, --with python3 enables it at the right > stage (after dh_auto_install) > I see. Thanks for the tip. > > > > * you'd not need "rm -rf build .pybuild" line if you re-enable > > > dh_auto_clean > > > > > > > So I only override auto_clean to get rid of the man page directory? > > yes, if you don't want to disable dh_foo, use something like: > > override_dh_foo: > whatever you want to call before dh_foo > dh_foo > whatever you want to call after dh_foo > Cool. I've implemented both things. Pushed it. > -- > Piotr Ożarowski Debian GNU/Linux Developer > www.ozarowski.pl www.griffith.cc www.debian.org > GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 > > > -- > 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/20141124122602.gs4...@sts0.p1otr.com > >
Re: Fwd: [iva] - Python 3 code depends on pysam
Hi guys, So essentially the package build halts when it tries to run the test suite: This is the error I'm getting when the pysam module is being imported: root@debian:~/iva-0.10.0# python3.4 setup.py test running test running egg_info writing top-level names to iva.egg-info/top_level.txt writing iva.egg-info/PKG-INFO writing dependency_links to iva.egg-info/dependency_links.txt reading manifest file 'iva.egg-info/SOURCES.txt' writing manifest file 'iva.egg-info/SOURCES.txt' running build_ext Failure: ImportError (No module named 'pysam') ... ERROR == ERROR: Failure: ImportError (No module named 'pysam') -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 414, in loadTestsFromName addr.filename, addr.module) File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.4/imp.py", line 245, in load_module return load_package(name, filename) File "/usr/lib/python3.4/imp.py", line 217, in load_package return methods.load() File "", line 1220, in load File "", line 1200, in _load_unlocked File "", line 1129, in _exec File "", line 1471, in exec_module File "", line 321, in _call_with_frames_removed File "/tmp/buildd/iva-0.10.0/iva/__init__.py", line 20, in from iva import * File "/tmp/buildd/iva-0.10.0/iva/assembly.py", line 2, in import pysam ImportError: No module named 'pysam' -- Ran 1 test in 0.016s FAILED (errors=1) If pysam is python 3 compliant, I'm tempted to create the needed symlinks in python3.4 pointing to pysam in python2.7, eg. ln -s /usr/lib/python2.7/dist-packages/pysam /usr/lib/python3.4/dist-packages/pysam I'm sure that this is not the proper way of doing things, so is there any other way I can get pysam to be installed under python3.4 rather than python2.7? Regards, Jorge
Re: Fwd: [iva] - Python 3 code depends on pysam
Hi Ghis On Mon, Nov 24, 2014 at 4:58 PM, Ghislain Vaillant wrote: > At worst, can't you just disable the test suite for the Python 3 builds ? > Pybuild should allow to do that easily. > Trying that now. But I would still need to link pysam to the iva package at some point, no? Regards, Jorge > 2014-11-24 16:36 GMT+00:00 Jorge Sebastião Soares : > >> Hi guys, >> >> So essentially the package build halts when it tries to run the test >> suite: >> >> This is the error I'm getting when the pysam module is being imported: >> >> root@debian:~/iva-0.10.0# python3.4 setup.py test >> running test >> running egg_info >> writing top-level names to iva.egg-info/top_level.txt >> writing iva.egg-info/PKG-INFO >> writing dependency_links to iva.egg-info/dependency_links.txt >> reading manifest file 'iva.egg-info/SOURCES.txt' >> writing manifest file 'iva.egg-info/SOURCES.txt' >> running build_ext >> Failure: ImportError (No module named 'pysam') ... ERROR >> >> == >> ERROR: Failure: ImportError (No module named 'pysam') >> -- >> Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in >> runTest >> raise self.exc_val.with_traceback(self.tb) >> File "/usr/lib/python3/dist-packages/nose/loader.py", line 414, in >> loadTestsFromName >> addr.filename, addr.module) >> File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in >> importFromPath >> return self.importFromDir(dir_path, fqname) >> File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in >> importFromDir >> mod = load_module(part_fqname, fh, filename, desc) >> File "/usr/lib/python3.4/imp.py", line 245, in load_module >> return load_package(name, filename) >> File "/usr/lib/python3.4/imp.py", line 217, in load_package >> return methods.load() >> File "", line 1220, in load >> File "", line 1200, in _load_unlocked >> File "", line 1129, in _exec >> File "", line 1471, in exec_module >> File "", line 321, in >> _call_with_frames_removed >> File "/tmp/buildd/iva-0.10.0/iva/__init__.py", line 20, in >> from iva import * >> File "/tmp/buildd/iva-0.10.0/iva/assembly.py", line 2, in >> import pysam >> ImportError: No module named 'pysam' >> >> -- >> Ran 1 test in 0.016s >> >> FAILED (errors=1) >> >> >> If pysam is python 3 compliant, I'm tempted to create the needed symlinks >> in python3.4 pointing to pysam in python2.7, eg. >> >> ln -s /usr/lib/python2.7/dist-packages/pysam >> /usr/lib/python3.4/dist-packages/pysam >> >> I'm sure that this is not the proper way of doing things, so is there any >> other way I can get pysam to be installed under python3.4 rather than >> python2.7? >> >> Regards, >> >> Jorge >> > >
Re: Fwd: [iva] - Python 3 code depends on pysam
Hi Ghis, Disabling the tests worked. The package builds at least, but not lintian clean . I'll cary on tomorrow. Regards, Jorge On Mon, Nov 24, 2014 at 5:02 PM, Jorge Sebastião Soares < j.s.soa...@gmail.com> wrote: > Hi Ghis > > On Mon, Nov 24, 2014 at 4:58 PM, Ghislain Vaillant > wrote: > >> At worst, can't you just disable the test suite for the Python 3 builds ? >> Pybuild should allow to do that easily. >> > > Trying that now. > > But I would still need to link pysam to the iva package at some point, no? > > Regards, > > Jorge > > > >> 2014-11-24 16:36 GMT+00:00 Jorge Sebastião Soares : >> >>> Hi guys, >>> >>> So essentially the package build halts when it tries to run the test >>> suite: >>> >>> This is the error I'm getting when the pysam module is being imported: >>> >>> root@debian:~/iva-0.10.0# python3.4 setup.py test >>> running test >>> running egg_info >>> writing top-level names to iva.egg-info/top_level.txt >>> writing iva.egg-info/PKG-INFO >>> writing dependency_links to iva.egg-info/dependency_links.txt >>> reading manifest file 'iva.egg-info/SOURCES.txt' >>> writing manifest file 'iva.egg-info/SOURCES.txt' >>> running build_ext >>> Failure: ImportError (No module named 'pysam') ... ERROR >>> >>> == >>> ERROR: Failure: ImportError (No module named 'pysam') >>> -- >>> Traceback (most recent call last): >>> File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in >>> runTest >>> raise self.exc_val.with_traceback(self.tb) >>> File "/usr/lib/python3/dist-packages/nose/loader.py", line 414, in >>> loadTestsFromName >>> addr.filename, addr.module) >>> File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in >>> importFromPath >>> return self.importFromDir(dir_path, fqname) >>> File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in >>> importFromDir >>> mod = load_module(part_fqname, fh, filename, desc) >>> File "/usr/lib/python3.4/imp.py", line 245, in load_module >>> return load_package(name, filename) >>> File "/usr/lib/python3.4/imp.py", line 217, in load_package >>> return methods.load() >>> File "", line 1220, in load >>> File "", line 1200, in _load_unlocked >>> File "", line 1129, in _exec >>> File "", line 1471, in exec_module >>> File "", line 321, in >>> _call_with_frames_removed >>> File "/tmp/buildd/iva-0.10.0/iva/__init__.py", line 20, in >>> from iva import * >>> File "/tmp/buildd/iva-0.10.0/iva/assembly.py", line 2, in >>> import pysam >>> ImportError: No module named 'pysam' >>> >>> -- >>> Ran 1 test in 0.016s >>> >>> FAILED (errors=1) >>> >>> >>> If pysam is python 3 compliant, I'm tempted to create the needed >>> symlinks in python3.4 pointing to pysam in python2.7, eg. >>> >>> ln -s /usr/lib/python2.7/dist-packages/pysam >>> /usr/lib/python3.4/dist-packages/pysam >>> >>> I'm sure that this is not the proper way of doing things, so is there >>> any other way I can get pysam to be installed under python3.4 rather than >>> python2.7? >>> >>> Regards, >>> >>> Jorge >>> >> >> >
Re: Fwd: [iva] - Python 3 code depends on pysam
Hi all, I am thinking to go about this in one of two ways: 1 - State python3-pip as a dependency and use pip3 to install pysam the python3 lib folder; 2 - Package python3-pysam. I really don't want to have to package another piece of software right now though. Do you see any other way to do this? Jorge On Mon, Nov 24, 2014 at 5:28 PM, Jorge Sebastião Soares < j.s.soa...@gmail.com> wrote: > Hi Ghis, > > Disabling the tests worked. > > The package builds at least, but not lintian clean > . > > I'll cary on tomorrow. > > Regards, > > Jorge > > On Mon, Nov 24, 2014 at 5:02 PM, Jorge Sebastião Soares < > j.s.soa...@gmail.com> wrote: > >> Hi Ghis >> >> On Mon, Nov 24, 2014 at 4:58 PM, Ghislain Vaillant >> wrote: >> >>> At worst, can't you just disable the test suite for the Python 3 builds >>> ? Pybuild should allow to do that easily. >>> >> >> Trying that now. >> >> But I would still need to link pysam to the iva package at some point, no? >> >> Regards, >> >> Jorge >> >> >> >>> 2014-11-24 16:36 GMT+00:00 Jorge Sebastião Soares >>> : >>> >>>> Hi guys, >>>> >>>> So essentially the package build halts when it tries to run the test >>>> suite: >>>> >>>> This is the error I'm getting when the pysam module is being imported: >>>> >>>> root@debian:~/iva-0.10.0# python3.4 setup.py test >>>> running test >>>> running egg_info >>>> writing top-level names to iva.egg-info/top_level.txt >>>> writing iva.egg-info/PKG-INFO >>>> writing dependency_links to iva.egg-info/dependency_links.txt >>>> reading manifest file 'iva.egg-info/SOURCES.txt' >>>> writing manifest file 'iva.egg-info/SOURCES.txt' >>>> running build_ext >>>> Failure: ImportError (No module named 'pysam') ... ERROR >>>> >>>> == >>>> ERROR: Failure: ImportError (No module named 'pysam') >>>> -- >>>> Traceback (most recent call last): >>>> File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in >>>> runTest >>>> raise self.exc_val.with_traceback(self.tb) >>>> File "/usr/lib/python3/dist-packages/nose/loader.py", line 414, in >>>> loadTestsFromName >>>> addr.filename, addr.module) >>>> File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in >>>> importFromPath >>>> return self.importFromDir(dir_path, fqname) >>>> File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in >>>> importFromDir >>>> mod = load_module(part_fqname, fh, filename, desc) >>>> File "/usr/lib/python3.4/imp.py", line 245, in load_module >>>> return load_package(name, filename) >>>> File "/usr/lib/python3.4/imp.py", line 217, in load_package >>>> return methods.load() >>>> File "", line 1220, in load >>>> File "", line 1200, in _load_unlocked >>>> File "", line 1129, in _exec >>>> File "", line 1471, in exec_module >>>> File "", line 321, in >>>> _call_with_frames_removed >>>> File "/tmp/buildd/iva-0.10.0/iva/__init__.py", line 20, in >>>> from iva import * >>>> File "/tmp/buildd/iva-0.10.0/iva/assembly.py", line 2, in >>>> import pysam >>>> ImportError: No module named 'pysam' >>>> >>>> -- >>>> Ran 1 test in 0.016s >>>> >>>> FAILED (errors=1) >>>> >>>> >>>> If pysam is python 3 compliant, I'm tempted to create the needed >>>> symlinks in python3.4 pointing to pysam in python2.7, eg. >>>> >>>> ln -s /usr/lib/python2.7/dist-packages/pysam >>>> /usr/lib/python3.4/dist-packages/pysam >>>> >>>> I'm sure that this is not the proper way of doing things, so is there >>>> any other way I can get pysam to be installed under python3.4 rather than >>>> python2.7? >>>> >>>> Regards, >>>> >>>> Jorge >>>> >>> >>> >> >
Re: Fwd: [iva] - Python 3 code depends on pysam
Hi Piotr On Tue, Nov 25, 2014 at 4:00 PM, Piotr Ożarowski wrote: > [Jorge Sebastião Soares, 2014-11-25] > > Hi all, > > > > I am thinking to go about this in one of two ways: > > > > 1 - State python3-pip as a dependency and use pip3 to install pysam the > > python3 lib folder; > > > > 2 - Package python3-pysam. > > > > > > I really don't want to have to package another piece of software right > now > > though. > > > > Do you see any other way to do this? > > you can add python3-pysam binary package yourself or ask someone else to > add it (wishlist bug against src:python-pysam in both cases if you're > not in Debian Med Packaging Team). > There's no other way. You cannot use > pip, you cannot disable tests (if you need this library runtime anyway) > That's what I thought. And yes, disabeling the tests was really just a proof of concept. > and you cannot bundle pysam in python3-iva package > Fine. I've had a chat with my team and there is room for me to package the python3-pysam. Regards, Jorge
[python3-pysam + iva] - Pysam depends on pyrex
Good morning, This is just like a Matryoshka doll... So I tentatively started packaging python3-pysam. Still haven't created a git alioth project for it. I did clone the python-pysam project [1], in hopes that it would be just a couple of minor changes. Only to find that pysam depends on python-pyrex. So to package python3-pysam, I have also to packge python3-pyrex. It seems that python-pyrex has not seen much development [2]. Is anyone working on this package? Sorry to be a pain, but it really starts to feel like a pontless task to be packaging iva... I don't know what to expect from this email. I suppose it's more of a rant. Best, Jorge [1] - http://anonscm.debian.org/cgit/debian-med/python-pysam.git/ [2] - https://tracker.debian.org/pkg/pyrex
Re: [python3-pysam + iva] - Pysam depends on pyrex
Ok, Rant is over. I have just been in touch with the pysam developers and they assured me that pysam only depends on Cython and not on pyrex. Pyrex is still stated as a dependency of python-pysam. I am thinking of making changes to the python-pysam package for it to create a new binary python3-pysam. I will test if removing the python-pyrex dependency breaks the package. Regards, Jorge On Wed, Nov 26, 2014 at 9:08 AM, Jorge Sebastião Soares < j.s.soa...@gmail.com> wrote: > Good morning, > > This is just like a Matryoshka doll... > So I tentatively started packaging python3-pysam. > > Still haven't created a git alioth project for it. > > I did clone the python-pysam project [1], in hopes that it would be just a > couple of minor changes. > > Only to find that pysam depends on python-pyrex. > > So to package python3-pysam, I have also to packge python3-pyrex. > > It seems that python-pyrex has not seen much development [2]. > > Is anyone working on this package? Sorry to be a pain, but it really > starts to feel like a pontless task to be packaging iva... > > I don't know what to expect from this email. > > I suppose it's more of a rant. > > > Best, > > Jorge > > > > [1] - http://anonscm.debian.org/cgit/debian-med/python-pysam.git/ > [2] - https://tracker.debian.org/pkg/pyrex >
[python-pysam] - 4 packages built and all lintian clean
Hi all, I have commited my last changes to [1]. The test suite does not run automatically. I believe that pysam needs to be installed before hand in order to test it. I have installed python3-pysam on my system and ran the test suite and it seemed to ran fine. I emailed the test report to the guys at the Pysam project to see if that's what they expect. Essentially removed most of the rules in the rules file and the package is built with a simple: dh $@ --with python2,python3 --buildsystem=pybuild I have to get rid of the commented out stuff in there, but was hoping for someone to have a look at the state of python-pysam before I tidy everything up. So, can someone have a look at [1]? Regards, Jorge [1] - http://anonscm.debian.org/cgit/debian-med/python-pysam.git/
Re: [python-pysam] - 4 packages built and all lintian clean
It's been a while since I posted this first. Is someone able to have a look at this package? Jorge On Fri, Nov 28, 2014 at 12:58 PM, Jorge Sebastião Soares < j.s.soa...@gmail.com> wrote: > Hi all, > > I have commited my last changes to [1]. > > The test suite does not run automatically. I believe that pysam needs to > be installed before hand in order to test it. > > I have installed python3-pysam on my system and ran the test suite and it > seemed to ran fine. > I emailed the test report to the guys at the Pysam project to see if > that's what they expect. > > Essentially removed most of the rules in the rules file and the package is > built with a simple: > > dh $@ --with python2,python3 --buildsystem=pybuild > > I have to get rid of the commented out stuff in there, but was hoping for > someone to have a look at the state of python-pysam before I tidy > everything up. > > So, can someone have a look at [1]? > > Regards, > > Jorge > > > > [1] - http://anonscm.debian.org/cgit/debian-med/python-pysam.git/ >
Re: [python-pysam] - 4 packages built and all lintian clean
Hi Charles, Much appreciated! Regards, Jorge On Sat, Dec 6, 2014 at 8:38 AM, Charles Plessy wrote: > Le Sat, Dec 06, 2014 at 08:19:39AM +0000, Jorge Sebastião Soares a écrit : > > It's been a while since I posted this first. > > > > Is someone able to have a look at this package? > > Hi Jorge, > > I am a bit short of time, but I will have a look next Wednesday if nobody > does before. > > Cheers > > -- > Charles >
pexif package
Hi team, (I am not subscribed to the list, so please include me in the reply) I am packaging pexif because it is a dependency for Thumbor [0]. My question is, pexif has some scripts with generic names [1], like 'timezone', should I rename it? [0] https://github.com/thumbor/thumbor [1] https://github.com/bennoleslie/pexif/tree/master/scripts Cheers, -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org http://metaldot.alucinados.com signature.asc Description: This is a digitally signed message part
Re: pexif package
Hi Dmitry, On Fri, 2015-05-22 at 20:04 +0300, Dmitry Shachnev wrote: > Hi, > > On Tue, 19 May 2015 10:36:13 -0300, Marcelo Jorge Vieira wrote: > > I am packaging pexif because it is a dependency for Thumbor [0]. My > > question is, pexif has some scripts with generic names [1], like > > 'timezone', should I rename it? > > > > [0] https://github.com/thumbor/thumbor > > [1] https://github.com/bennoleslie/pexif/tree/master/scripts > > This package definitely should _not_ ship /usr/bin/timezone. > > I see these are just example scripts, can you just install them > to something like /usr/share/pyexif/examples/? Sounds good for me, thanks for your reply. Cheers, -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org http://metaldot.alucinados.com signature.asc Description: This is a digitally signed message part
Re: Request to join the Python Team
Hi Stefano, On Mon, 2021-01-25 at 01:50 +, Stefano Rivera wrote: > Hi Pablo (2021.01.24_23:33:52_+) > > I'm sending this message as a request to join the Python Team. > > Added. Welcome. Thank you! -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org https://metaldot.alucinados.com signature.asc Description: This is a digitally signed message part
