On Thu, 14 Jan 2021, Torrance, Douglas wrote:
Hello!
There was just a new upstream release of git-big-picture, which I've
packaged:
https://salsa.debian.org/python-team/packages/git-big-picture
Would anyone be able to review/sponsor?
Uploaded, thanks!
Scott
On Wed, 22 Jul 2020, Andreas Tille wrote:
Hi,
I intend to package pyarrow[1] as a precondition for some Debian
Med package. Unfortunately I get:
...
-- Build output directory:
/build/python-pyarrow-0.17.1/build/temp.linux-x86_64-3.8/release
CMake Error at
On Mon, 29 Jun 2020, Scott Kitterman wrote:
More over, mock debhelper was upgraded to 13, for no apparent
reason
(yet another "cosmetic fix" that isn't helping?). I'd like to
remind
everyone that, increasing debhelper compat version to a number
that
isn't in stable,
Hi,
I have a couple of (mostly library) Python packages, src:wxpython3.0,
which was Python 2 only and has been recently RM'd and src:wxpython4.0
which is Python 3 only. wxpython3.0 had a subpackage, python-wxtools,
which contained a few utility scripts. wxpython4.0 can also provide those
On Thu, 18 Jun 2020, Shayan Doust wrote:
I have been having some issues with packaging intake[1] for the Debian
Med packaging team, specifically during pytest. There are a lot of tests
failing, so I contacted upstream for a solution.
According to upstream, the "entrypoints in the setup script
On Tue, 26 May 2020, Thomas Goirand wrote:
Hi there!
Does any of you knows how to fix this bug?
https://bugs.debian.org/959558
Almost all of OpenStack can removed from Bullseye if not fixed in time,
so I tried to fix, but couldn't.
It looks like it's a bug in sphinx. I tried sphinx 3.0.4
On Sat, 16 May 2020, Marcos Fouces wrote:
Hello
I packaged a new release for python-rq [1]. Please, consider review and
upload.
[1] https://salsa.debian.org/python-team/modules/python-rq
I added a gbp.conf and uploaded.
Thanks,
Scott
On Mon, 11 May 2020, Doug Torrance wrote:
On Thursday, April 23, 2020 10:32:42 PM EDT Doug Torrance wrote:
I am interested in joining the Python Applications Packaging Team. I'm
experienced in packaging for Debian and am an active member of the Window
Maker and Science teams. However, I
Hi,
I am currently a member as swt2c-guest, but I recently became a DD, so can
I please be re-added to DPMT and PAPT under swt2c.
I still accept all policies. :)
Thanks,
Scott
On Thu, 9 Jan 2020, Cindy Sue Causey wrote:
Oh, boy, oh, boy, an excuse for my first post!! *waving!*
Hi Cindy and welcome!
About an hour ago, I was installing more Python and other types of
developer-learning packages on a Bullseye debootstrap in chroot. A
couple of dependency packages
On Thu, 19 Dec 2019, Andreas Tille wrote:
Traceback (most recent call last):
File "/usr/bin/../lib/atac/bin/AtacDriver.py", line 18, in
import MyFile
File "/usr/lib/atac/lib/MyFile.py", line 6, in
class myfile(file):
NameError: name 'file' is not defined
On Thu, 12 Dec 2019, Andreas Tille wrote:
That hint was helpful anyway and I get further now. I think now the
problem is to convince scons to install in $(CURDIR)/debian/tmp which
seems to try rather /usr/share/pdb2pqr directly:
Looks like the debian/rules file is specifying
On Thu, 12 Dec 2019, Andreas Tille wrote:
Control: tags -1 help
Hi,
it seems pdb2pqr is orphaned upstream. However, it seems to be worth
keeping inside Debian thus I tried my luck to port it to Python3 in
Git[1]. Unfortunately the build runs into
scons: Building targets ...
Hi,
I'm already a member of DPMT, I would like to join PAPT as well so I can
also contribute to those packages. I have read the policy and accept it.
Salsa ID: swt2c-guest
Thanks,
Scott
On Wed, 4 Dec 2019, Andreas Tille wrote:
Hi,
I try to prepare the latest git commit from upstream of python-pbcore[1].
Unfortunately the build time test fails with:
...
dh_auto_test
I: pybuild base:217: python3.8 setup.py test
running pytest
running egg_info
writing pbcore.egg-info/PKG-INFO
On Wed, 4 Dec 2019, Dmitry Shachnev wrote:
Hi,
Can someone please do an upload of python-traits? I did an update to the
latest upstream release, plus various minor fixes. I didn't remove Python 2
support yet as there are still a few rdeps.
Hi,
Can someone please do an upload of python-traits? I did an update to the
latest upstream release, plus various minor fixes. I didn't remove Python
2 support yet as there are still a few rdeps.
https://salsa.debian.org/python-team/modules/python-traits
Thanks,
Scott
On Fri, 8 Nov 2019, Andreas Tille wrote:
Hi,
I started an attempt to port graphlan to Python3 in Git[1] but its
autopkgtest throws errors:
Running test script ./IBD_biogeography/run.sh .
Traceback (most recent call last):
File "/usr/bin/graphlan_annotate", line 26, in
from
On Thu, 5 Sep 2019, Andreas Tille wrote:
Control: tags -1 help
Hi,
for some reason I do not understand are the dependencies of the
binary package
Depends: python3-numpy (>= 1:1.16.0~rc1), python3-numpy-abi9, python3:any,
python:any
How can I get rid of the python:any dependency?
Very
On Thu, 15 Aug 2019, Jonathan Carter wrote:
- btfs
That's weird, this program is written in C and contains no python
whatsoever. Any idea how it ended up on the list? Perhaps there are some
other false positives too?
Probably because it Depends: python?
Scott
On Fri, 9 Aug 2019, Graham Inggs wrote:
However, there's one package that seems like it is going to cause a
problem. I uploaded pytest-xdist 1.29.0-1, which *requires* pytest 4, so
pytest-xdist won't migrate to testing until pytest 4 does. On the other
hand, pytest 4 won't migrate to testing
Hi,
Ondřej, I saw you uploaded pytest 4. This has caused autopkgtest failures
in a few of the packages I maintain, which I've been working on fixing. I
think those should be fine once they migrate to testing, as it should
clear the autopkgtest failure from pytest 4.
However, there's one
On Mon, 5 Aug 2019, Mattia Rizzolo wrote:
I did a major update for pytest-bdd (new upstream release, dropped py2
packages, other lintian fixes, etc.). Does someone mind uploading it?
https://salsa.debian.org/python-team/modules/pytest-bdd
Uploaded!
Just, please do not push debian/ tags
On Tue, 30 Jul 2019, Thomas Goirand wrote:
Hi,
út 23. 7. 2019 v 11:40 odesílatel Scott Talbert napsal:
When removing leaf python2 packages for bullseye, is there
anything
__modules__ package :)
special that needs to be done, other than removing the building
On Tue, 23 Jul 2019, Ondrej Novy wrote:
Hi,
út 23. 7. 2019 v 11:40 odesílatel Scott Talbert napsal:
When removing leaf python2 packages for bullseye, is there
anything
__modules__ package :)
special that needs to be done, other than removing the building
Hi,
I did a major update for pytest-bdd (new upstream release, dropped py2
packages, other lintian fixes, etc.). Does someone mind uploading it?
https://salsa.debian.org/python-team/modules/pytest-bdd
Thanks,
Scott
On Wed, 24 Jul 2019, Neil Williams wrote:
út 23. 7. 2019 v 11:40 odesílatel Scott Talbert
napsal: When removing leaf python2 packages for bullseye, is there
anything
__modules__ package :)
special that needs to be done, other than removing the
building of the
python2
On Wed, 24 Jul 2019, Neil Williams wrote:
napsal: When removing leaf python2 packages for bullseye, is there
anything
__modules__ package :)
special that needs to be done, other than removing the
building of the
python2 subpackage?
For example, obsoleting of the old
On Tue, 23 Jul 2019, Ondrej Novy wrote:
út 23. 7. 2019 v 11:40 odesílatel Scott Talbert napsal:
When removing leaf python2 packages for bullseye, is there
anything
__modules__ package :)
special that needs to be done, other than removing the building
When removing leaf python2 packages for bullseye, is there anything
special that needs to be done, other than removing the building of the
python2 subpackage?
For example, obsoleting of the old package or anything along those lines?
Scott
On Fri, 19 Jul 2019, Andrey Rahmatullin wrote:
I'm running dh_python2 in a package on a non-standard directory path so it
will handle byte compilation, etc. However, it seems to be removing empty
directories from the directory tree. Is there any way to avoid this
behavior?
From Python
On Fri, 19 Jul 2019, Andrey Rahmatullin wrote:
I'm running dh_python2 in a package on a non-standard directory path so it
will handle byte compilation, etc. However, it seems to be removing empty
directories from the directory tree. Is there any way to avoid this
behavior?
From Python
I'm running dh_python2 in a package on a non-standard directory path so it
will handle byte compilation, etc. However, it seems to be removing empty
directories from the directory tree. Is there any way to avoid this
behavior?
Thanks,
Scott
When packaging a pytest plugin and wanting to run the plugin's unit tests
during the build process, the plugin usually has to be installed before
running the tests, otherwise pytest cannot find the plugin. This seems to
require workarounds such as this [1].
Is there any way to avoid this
On Tue, 5 Jun 2018, Andrey Rahmatullin wrote:
Yes, I'm talking about the automatically generated -dbgsym packages that
contain the /usr/lib/debug/.build-id/... files.
Have you read Scott's email?
Yes, but wouldn't they still be useful for symbolicating core dumps?
Scott
On Mon, 4 Jun 2018, Matthias Klose wrote:
I've got a package (wxpython4.0) that builds modules for both Python 2.7
and Python 3. When I rebuilt the package in early May, I started getting
the lintian warning debug-file-with-no-debug-symbols for the Python 3
dbgsym packages only. Sure enough,
Hi,
I've got a package (wxpython4.0) that builds modules for both Python 2.7
and Python 3. When I rebuilt the package in early May, I started getting
the lintian warning debug-file-with-no-debug-symbols for the Python 3
dbgsym packages only. Sure enough, looking at those files, there is not
On Tue, 8 May 2018, Ben Finney wrote:
The source package in question is wxpython4.0. The reason I use
easy_install is for installing the python2 version of the module as an
egg.
Okay, so from that I understand that the Debian package is not invoking
‘easy_install’ to fetch files from the
On Mon, 7 May 2018, Ben Finney wrote:
About a month ago, Matthias removed easy_install from setuptools. I
have sent him a few mails and bugs asking about it, but I haven't
heard anything back. Anyone know why he did it? I have a package
that currently FTBFS because of it. :(
Why does a
About a month ago, Matthias removed easy_install from setuptools. I have
sent him a few mails and bugs asking about it, but I haven't heard
anything back. Anyone know why he did it? I have a package that
currently FTBFS because of it. :(
python-setuptools (39.0.1-2) unstable;
On Wed, 28 Mar 2018, Andrey Rahmatullin wrote:
I've got a package where I need to pass an argument to setup.py as part of
the build process. Is there a way to do this with dh_python2, ie, without
using overrides?
dh_python2 doesn't call setup.py, the build system (python_distutils or
pybuild)
Hi,
I've got a package where I need to pass an argument to setup.py as part of
the build process. Is there a way to do this with dh_python2, ie, without
using overrides?
Scott
Hi,
I'm looking for a sponsor to upload pytest-forked. It's quite a simple
package. It's a small bit of functionality that has been stripped out of
pytest-xdist and is needed for a new upstream release of pytest-xdist.
It's here on salsa and also uploaded to mentors:
On Fri, 9 Feb 2018, Scott Talbert wrote:
Hi,
I would like to join DPMT so that I could maintain the python-pytest-xdist
package (that I've recently discussed adopting with Daniel Stender).
Additionally, I'll need to package a new dependency for a new upstream
release of python-pytest-xdist
On Tue, 6 Feb 2018, Scott Talbert wrote:
Hi,
I would like to join DPMT so that I could maintain the python-pytest-xdist
package (that I've recently discussed adopting with Daniel Stender).
Additionally, I'll need to package a new dependency for a new upstream
release of python-pytest-xdist
Hi,
I would like to join DPMT so that I could maintain the python-pytest-xdist
package (that I've recently discussed adopting with Daniel Stender).
Additionally, I'll need to package a new dependency for a new upstream
release of python-pytest-xdist.
My Alioth login is swt2c-guest.
I've
46 matches
Mail list logo
