On Wed, 18 Apr 2018 12:48:27 +0300 Dmitry Shachnev wrote:
> On Sun, Apr 15, 2018 at 01:26:50PM +0300, Dmitry Shachnev wrote:
> > Works for me in a clean sid chroot.
>
> The CI tests for pyqt5 are also passing [1], so I am closing this bug.
>
> [1]:
Requested amd64 strace for the failure.
Scott Kstrace python -c "import PyQt5.QtCore"
execve("/usr/bin/python", ["python", "-c", "import PyQt5.QtCore"],
0x7ffdbf72ace0 /* 32 vars */) = 0
brk(NULL) = 0x7ff0643bf000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT
Package: python-pyqt5
Version: 5.9.2+dfsg-1
Severity: grave
Justification: renders package unusable
Tried this on sid with both pyqt5 5.9.2 and 5.10.1:
Unpacking python-pyqt5 (5.10.1+dfsg-1) over (5.9.2+dfsg-1+b1) ...
Setting up python-pyqt5 (5.10.1+dfsg-1) ...
# python
Python 2.7.14+ (default,
On Thu, 18 Aug 2016 19:57:35 +0200 Anthon van der Neut wrote:
>
> I can confirm this still happens with python-yaml 3.10 and 3.11.2, as
> well as with the package python-ruamel.yaml 0.11.14-1 (a fork and
> superset of python-yaml).
>
> This has been fixed in version 0.12.3 of ruamel.yaml.
>
>
On October 9, 2018 1:02:10 PM UTC, Salvo Tomaselli wrote:
>Is this package unmaintained/abandoned?
>
>I could take it…
>
>--
>Salvo Tomaselli
DPMT is the maintainer, so you can update it with a team upload.
Scott K
___
Python-modules-team
Uploader's request.
Scott K
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
___
Python-modules-team mailing list
Package: python3-wget
Version: 3.2-1
Severity: normal
python3-wget has the following in it's Depends:
Depends: python-urllib3, ${misc:Depends}, ${python3:Depends}
Unfortunately, python-urllib3 is both wrong and unnecessary. It is wrong
because a python3 package needs to depend on the python3
Upstream withdrew this release. I'm in favor of switching to safe load by
default, but I think we need to be careful about it. I haven't checked the
details on why 4.1 was withdrawn. We may be better off cherry-picking the safe
load changes.
Thanks for working on pyyaml.
Scott K
These failures are because we're using libyaml and it supports a newer yaml
version than the pure python implementation that the tests were made for.
I've verified this by rebuilding pyyaml without libyaml. Then all the tests
pass.
Before making the failures fatal, these tests need to be
On Tue, 19 Mar 2019 11:03:37 + wmwmw wrote:
> Package: python3-celery
> Version: 4.2.1-3
> Severity: grave
> Justification: renders package unusable
>
> Should be fixed in the upstream, but current versions in repository are
incompatible.
>
> https://github.com/celery/celery/issues/5175
On Friday, April 05, 2019 08:16:51 AM Chris Lamb wrote:
> Hi Ivo,
>
> > The 2.7.4+git6-g9134ad92-2 upload you mentioned in this bug
>
> I think you are confusing me with someone else here? :)
>
> […]
>
> > Would you consider uploading a new version disabling this test for now, to
> > fix the
That only means Qt5 or pyqt5 is out of date on riscv64, so python-pyqt5 isn't
installable. Qscintilla2 is the victim here. Nothing you did wrong.
Scott K
On February 23, 2019 7:31:23 AM UTC, "Gudjon I. Gudjonsson"
wrote:
>Hi Manuel
>
>Sorry for a slow response. But can you please take at
This seems relevant:
https://github.com/python/typing/issues/523
Scott K
On Tuesday, February 05, 2019 11:02:56 PM Ruano Ruano Javier wrote:
> Hello Diane,
> The exact message is:
>
> args2 = [_get_recursive(dsk, k, cache) for k in args]
> File "/usr/lib/python3/dist-packages/dask/core.py",
Your debian/copyright lists "2017-2019 Sebastian Muszynski "
as an upstream copyright holder. On the assumption that is correct, you
should ask upstream to more completely document the copyright holders in the
work.
You list the maintainer as Debian Python Modules Team , but the Vcs-* fields
For your next upload, please note that this:
Build-Depends: debhelper (>=12), debhelper-compat (=12), ...
is redundant - it should be changed to:
Build-Depends: debhelper-compat (=12), ...
See man debhelper in the COMPATIBILITY LEVELS section for details.
Scott K
eque
> sts/1
>
> Please, review it :-)
>
> Thanks Scott.
> Regards!
>
>
> El mar., 5 de feb. de 2019 a la(s) 23:23, Scott Kitterman (
>
> ftpmas...@ftp-master.debian.org) escribió:
> > For your next upload, please note that this:
> >
&
In your debian/copyright you list Dmitry Sagalovskiy as a copyright holder,
but he is not listed as such. The fact that he's listed as an author, doesn't
mean he owns the copyright.
In debian/watch is says version=3, but the package uses version 4 features:
@ANY_VERSION@
@ARCHIVE_EXT@
Please
Since this package provides a python3 module social_django, the binary should
be named python3-social-django per the Python policy. There's no apparent
need to deviate in this package. There is no need to change the source
package name.
The package has an empty debian/patches directory that
In debian/copyright, you miss a year on the attribution:
Copyright: 2017, DCSO Deutsche Cyber-Sicherheitsorganisation GmbH
should be 2016,2017. Please fix on your next upload.
Scott K
___
Python-modules-team mailing list
Please lose the emoticon in the package descriptions. Yes, d/control is
UTF-8, but that doesn't mean you can rely on terminals using fancy fonts with
all the latest code points. It's not particularly cute and will mostly just
cause confusion (I'd have no idea what it was if I hadn't looked at
Unfortunately dbgsym packages are not particularly useful for Python packages
since they don't use/depend on the debug interpreter. Please consider
providing a traditional -dbg package instead in a future upload.
Scott K
___
Python-modules-team
You are correct to include the copyright notice and license from src/
css_parser/version.py in your debian/copyright. It does, however, seem
unlikley there there is anything actually copyrightable in that file. You
might want to take that up with upstream.
Scott K
:
>Dear Scott, Chris, and DPMT,
>
>On Mon, Feb 04, 2019 at 01:44:47PM +0000, Scott Kitterman wrote:
>> You are correct to include the copyright notice and license from src/
>> css_parser/version.py in your debian/copyright. It does, however,
>seem
>> unlikley th
On Sunday, April 14, 2019 06:08:28 PM Dmitry Shachnev wrote:
> Package: python-gdata
> Version: 2.0.18+dfsg1-2
> Severity: serious
> Tags: buster sid
>
> I am uploader of python-gdata and my intention is that it should not be
> part of Debian Buster release.
>
> There are two main reasons for
Unfortunately it's hard to determine programmatically if it's cruft or not.
You might mark this bug as being blocked by the bugs for the other packages.
Also, getting them cleaned up may help with getting Django updates to migrate
to Testing (not sure).
Scott K
Reverse depends python-celery causes the cruft python-* to stick around.
Scott K
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
On Tuesday, September 3, 2019 6:43:24 AM EDT Andrey Rahmatullin wrote:
> This can be RMed but has popcon 491.
Since it's a module, not an app (so no one should be installing it just
because), I think it can still go.
Scott K
___
Python-modules-team
On Thursday, August 29, 2019 8:22:47 AM EDT Debian FTP Masters wrote:
> binary:python-pomegranate-doc is NEW.
> binary:python3-pomegranate is NEW.
> binary:python3-pomegranate is NEW.
> binary:python-pomegranate-doc is NEW.
> source:python-pomegranate is NEW.
Is python-pomegranate really
On Sunday, September 1, 2019 2:35:21 PM EDT Miguel Landaeta wrote:
> On Fri, Aug 30, 2019 at 07:27:39AM +, Matthias Klose wrote:
> > Package: src:namebench
> > Version: 1.3.1+dfsg-2
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
>
Unfortunately this upload contains debian/copyright problems serious enough
that I have to reject the package. There are three classes of errors:
1. Missing licenses
2. Missing copyright holders
3. Incorrect copyright attributions
I'm only rejecting because of the first:
think there was anything GPL before).
Scott K
On September 2, 2019 9:45:11 AM UTC, Norbert Preining
wrote:
>Hi Scott,
>
>once again.
>
>On Mon, 02 Sep 2019, Scott Kitterman wrote:
>> I'm only rejecting because of the first:
>>
>> mechanize/polyglot.py:# Lice
I neglected to check reverse build-depends before I uploaded this, so python-
cxx-dev will stick around for awhile as cruft until it is no longer needed.
Scott K
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
Thanks. That'll do. On a side note, your 'python-all-dev, python3-all-dev'
build-depends should be changed to 'python-all, python3-all' since there's no
arch:any content in the package. No point in pulling in more build-depends
than needed and during transitions, the -dev build-dep is a key
Same rationale as other version.
Scott K
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
___
Python-modules-team mailing list
Unfortunately I am going to have to reject your package due to debian/
copyright issues.
The immeidately fatal issue is missing license information for
pyutilib/component/loader/plugin_eggLoader.py. It contains the
statement:
# Copyright (C) 2005-2008 Edgewall Software
# Copyright (C)
gt;>
>>
>> Accepted:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Format: 1.8
>> Date: Sat, 31 Aug 2019 11:35:45 -0400
>> Source: pycxx
>> Architecture: source
>> Version: 7.0.3-3
>> Distribution: unstable
>&g
I am going to accept your package, but please note:
The `License: Apache-2` stanza is said to apply to debian/,
but the content of that stanza includes the line "Copyright 2019 The
pybadge Authors".
The copyright years for Pybadge authors should include 2019
(see twine_upload.sh).
Scott K
Package: src:python-tablib
Version: 0.12.1-2
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package.
On Thu, 11 Jul 2019 10:16:48 +0300 mer...@debian.org wrote:
> Hello,
>
> According to [1] the unsafe loader yaml.UnsafeLoader is still
> vulnerable, and could be used upon request. While strictly speaking the
> vulnerability is fixed by using safe reader by default, I assume
> complete safety can
Package: src:python-markdown
Version: 3.0.1-3
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this
On Thu, 10 Jan 2019 11:19:01 + Simon McVittie wrote:
> Source: pyyaml
> Severity: wishlist
>
> pyyaml 4.1 is available.
>
> This version addresses CVE-2017-18342 (
Uploaded 5.1.2-1.
Scott K
___
Python-modules-team mailing list
On Monday, September 30, 2019 4:04:05 PM EDT Moritz Mühlenhoff wrote:
> On Sat, Sep 09, 2017 at 11:09:45PM +0200, Lisandro Damián Nicanor Pérez
Meyer wrote:
> > Source: shiboken
> > Version: 1.2.2-5
> > Severity: wishlist
> > User: debian-qt-...@lists.debian.org
> > Usertags: qt4-removal
> >
> >
On July 8, 2019 9:10:54 AM UTC, Gordon Ball wrote:
>Those that I'm involved with:
>
>* xonsh is compatibile with either prompt_toolkit 1.x or 2.x
>* updating jupyter_console -> 6 is blocked on prompt_toolkit 2
>* updating ipython -> 7 is blocked on prompt_toolkit 2
>
>The ipython case is
ttps protocol
>>* d/control: Remove ancient X-Python-Version field
>>* d/control: Remove ancient X-Python3-Version field
>> * Bump Standards-Version to 4.4.1.
>> .
>>[ Lennart Weller ]
>>* New upstream release (Closes: #914698)
>>* New debian Standard
On November 4, 2019 10:00:27 PM UTC, Diane Trout wrote:
>On Tue, 2019-10-29 at 09:15 +0800, Drew Parsons wrote:
>> On 2019-10-29 03:01, Rebecca N. Palmer wrote:
>> > Assuming we're talking about
>> >
>> >
On November 13, 2019 2:10:49 AM UTC, Sandro Tosi wrote:
>On Tue, Nov 12, 2019 at 9:24 AM peter green
>wrote:
>> I am guessing that many of these are to get testsuite coverage for
>optional features and are not strictly needed for the build, while
>testing stuff is nice I don't think it's vital
On Fri, 30 Aug 2019 07:11:11 + Matthias Klose wrote:
> Package: src:backports.ssl-match-hostname
> - If the package is dead upstream, cannot be converted or maintained
> in Debian, it should be removed from the distribution. If the
> package still has reverse dependencies, raise the
Unfortunately I am going to have to reject your package. While we can accept
some errors in debian/copyright, a missing license needs to be fixed before
the package enters the archive.
The following note from one of the FTP Team trainees explains:
NOTICE mentions that some source comes from
No need to defer this. Please reschedule it to delay 0.
Scott K
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
On Tue, 19 Nov 2019 06:59:36 + peter green wrote:
> unblock 936745 by 936995
> severity 936745 serious
> thanks
>
> matplotlib2 no longer has any dependencies or build-dependencies on packages
built from the ipywidgets source.
>
> According to
Package: src:impacket
Version: 0.9.15-5
Severity: serious
Justification: Policy 2.5
This is at least in part a problem in the existing package, so I am not
going to reject the package for this, but it should definitely be fixed.
The following significant issues need review/update in
Package: src:django-background-tasks
Severity: important
Upstream has vanished (github repo in the homepage field is 404) and
this is blocking removal of django-compat. It's already removed from
testing due to django-compat.
If it's going to stay, someone would need to take on the changes
On Thursday, February 27, 2020 8:11:32 AM EST Salvatore Bonaccorso wrote:
> Hi Scott,
>
> On Thu, Feb 27, 2020 at 01:41:44PM +0100, Salvatore Bonaccorso wrote:
> > Hi,
> >
> > On Thu, Feb 27, 2020 at 01:18:55PM +0100, Salvatore Bonaccorso wrote:
> > > I think though we mgiht need to revisit the
Package: python-dnspython
Version: 1.16.0-1
Severity: serious
As the primary maintianer of dnspython, I don't think it is suitable to
leave with a python2 binary for the bullseye release.
Scott K
___
Python-modules-team mailing list
On Tuesday, March 3, 2020 11:41:26 AM EST Salvatore Bonaccorso wrote:
> Hi Scott,
>
> On Tue, Mar 03, 2020 at 09:19:06AM -0500, Scott Kitterman wrote:
> > On Tuesday, March 3, 2020 2:29:51 AM EST Salvatore Bonaccorso wrote:
> > > Source: pyyaml
> > > Version
On Thursday, February 27, 2020 2:44:48 AM EST Salvatore Bonaccorso wrote:
> Hi Scott,
>
> On Sat, Feb 22, 2020 at 07:20:34PM -0500, Scott Kitterman wrote:
> > Debdiff for proposed stable security update attached.
> >
> > The first hunk of the patch has the actual
On February 27, 2020 12:18:53 PM UTC, Salvatore Bonaccorso
wrote:
>Hi Scott,
>
>On Thu, Feb 27, 2020 at 06:24:09AM -0500, Scott Kitterman wrote:
>> On Thursday, February 27, 2020 2:44:48 AM EST Salvatore Bonaccorso
>wrote:
>> > Hi Scott,
>> >
>>
On March 6, 2020 3:05:17 PM UTC, Ron Lovell wrote:
>I checked a couple of other distros I run. In Arch Linux
>distutils/util.py
>is provided by the base "python" pkg. In openSUSE Tumbleweed it is
>provided
>by python3-base. So among my installations, Debian Buster and Sid are
>the
>odd ducks in
This is due to a breaking change that was inappropriately included in
python3.8 3.8.1. See:
https://bugs.python.org/issue27657
https://github.com/mozilla/bleach/issues/503
Rather than "Fixed" in python-bleach, the breaking change in python3.8 should
be reverted. Python3 can break
Revert is being done upstream for python 3.8.2:
https://bugs.python.org/msg361815
Since it appears this is going to be solved in python3.8, I'm going to
reassign again. Please don't reassign back, there's no point. There's
another open bug against ptyhon-bleach for this.
Scott K
1.0/debian/changelog 2019-01-15 00:46:11.0 -0500
+++ python-bleach-3.1.1/debian/changelog 2020-02-22 19:08:53.0 -0500
@@ -1,3 +1,9 @@
+python-bleach (3.1.1-0+deb10u1) buster-security; urgency=medium
+
+ * New upstream security release (Closes: #951907)
+
+ -- Scott Kitterman Sat,
Package: src:python-bleach
Version: 3.1.0-1
Severity: serious
Tags: security upstream
From the upstream change log:
**Security fixes**
* ``bleach.clean`` behavior parsing ``noscript`` tags did not match
browser behavior.
Calls to ``bleach.clean`` allowing ``noscript`` and one or more of
I checked and I can find no evidence that the version in oldstable is affected.
Scott K
signature.asc
Description: This is a digitally signed message part.
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
Please wait for 5.3--1 to migrate to testing before uploading the change. This
should really be a wishlist bug. There's no Debian policy violation here.
Scott K
On January 9, 2020 2:45:06 PM UTC, Debian Bug Tracking System
wrote:
>Processing commands for cont...@bugs.debian.org:
>
>> tags
On Sunday, January 12, 2020 11:28:55 PM EST Drew Parsons wrote:
> On 2020-01-13 09:52, Sandro Tosi wrote:
> > we finally reach the point were src:python-scipy produces only leaf
> > binary packages (excluding packages that are not in testing because RC
> > already), so i think it's time to file
On January 13, 2020 5:00:24 AM UTC, Drew Parsons wrote:
>On 2020-01-13 12:47, Sandro Tosi wrote:
>>> Thanks Sandro. There is RC bug#946624 affecting python-scipy, with
>a
>>> counterpart in #946625 for python3-scipy. Something subtle has
>>> changed
>>> in the syntax for skipping tests, I
> These failures are because we're using libyaml and it supports a newer yaml
> version than the pure python implementation that the tests were made for.
>
> I've verified this by rebuilding pyyaml without libyaml. Then all the tests
> pass.
>
> Before making the failures fatal, these tests
On Tuesday, March 3, 2020 11:41:26 AM EST Salvatore Bonaccorso wrote:
> Hi Scott,
>
> On Tue, Mar 03, 2020 at 09:19:06AM -0500, Scott Kitterman wrote:
> > On Tuesday, March 3, 2020 2:29:51 AM EST Salvatore Bonaccorso wrote:
> > > Source: pyyaml
> > > Version
On Fri, 20 Dec 2019 13:27:54 +0100 Gabriel Corona wrote:
> Package: python3-pip
> Version: 18.1-5
> Severity: normal
>
> Dear Maintainer,
>
> The pip package as installed by python3-pip refuses to install
> manylinux2010 wheels (see PEP 571).
This needs a newer pip version to properly support.
The proposed change in https://github.com/yaml/pyyaml/pull/394 resolves this
issue.
Scott K
signature.asc
Description: This is a digitally signed message part.
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
On April 18, 2020 10:03:01 AM UTC, Adrian Bunk wrote:
>On Mon, Mar 23, 2020 at 09:43:19PM +0100, Paul Gevers wrote:
>> Source: pythonmagick
>> Version: 0.9.19-6
>> X-Debbugs-CC: debian...@lists.debian.org
>> Severity: serious
>> User: debian...@lists.debian.org
>> Usertags: regression
>>
>>
Historically I would have rejected this package due to incomplete
debian/copyright. Please see validators/email.py.
:copyright: (c) Django Software Foundation and individual contributors.
:license: BSD
Since email.py isn't compiled, the license statement is actually present in
the
On April 20, 2020 2:36:00 AM UTC, peter green wrote:
>(using -quiet aliases where multiple involved packages have the same
>maintainer listed.
>
>Hi
>
>I have just been running some self-contained buildability tests on
>bullseye and these tests indicated that the python-linecache2 and
On Monday, April 20, 2020 8:51:10 AM EDT peter green wrote:
> On 20/04/2020 08:57, Thomas Goirand wrote:
> >> Option 1: fix all four packages to be python 2 free.
> >>
> >> Option 2: Remove python2 stuff from traceback2, python-funcsigs and
> >> numba. Break the dependencies of nipype in sid.
>
I don't know of a reason not to go ahead, but if you do, please be careful of
what's already in git. Update to the new version is staged there. It is
blocked on updates for some of the packages it builds wheels from.
Scott K
On March 13, 2020 7:32:35 PM UTC, Sandro Tosi wrote:
>On Fri, 30
On Friday, March 13, 2020 6:36:59 PM EDT Sandro Tosi wrote:
> On Fri, Mar 13, 2020 at 3:51 PM Scott Kitterman
wrote:
> > I don't know of a reason not to go ahead, but if you do, please be careful
> > of what's already in git. Update to the new version is staged there. It
On Tue, 31 Mar 2020 15:03:30 -0400 Scott Kitterman
wrote:
> On Fri, 27 Mar 2020 08:50:28 -0400 Scott Kitterman
> wrote:
> > On Fri, 27 Mar 2020 01:39:04 -0400 Scott Kitterman
> > wrote:
> > > On Fri, 27 Mar 2020 01:25:28 -0400 Scott Kitterman
> >
On Tue, 17 Mar 2020 10:38:23 -0400 Scott Kitterman
wrote:
> On Fri, 10 Jan 2020 00:02:12 -0800 Nye Liu wrote:
> > this bug is now more than a year old.
> >
> > Please update python3-pip and python-pip packages to >19.1
>
> The same problem still exists with
On Tue, 30 Oct 2018 21:50:36 +0100 Ben Wiederhake
wrote:
> Package: python3-pip
> Version: 9.0.1-2.3
> Severity: normal
> File: /usr/bin/pip3
>
> Dear Maintainer,
>
> I'm having trouble running this command:
>
> pip3 list --outdated
>
> Expected behavior: A list of outdated, local
On Fri, 3 Apr 2020 21:55:04 +0200 Lucas Nussbaum wrote:
> Source: python-tablib
> Version: 0.13.0-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200402 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed
Package: azure-cli
Version: 2.0.81+ds-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it is the closest one we have.
Now that humanfriendly is fixed to provide the missing files, azure-cli
has what
On Thu, 19 Mar 2020 12:20:05 + Scott Kitterman
wrote:
> Thanks. The virtualenv package needs updating following the recent pip
update. I'm working on it.
I can still replicate this with the new virtualenv. Here's the verbose
version for posterity:
Installing collected packa
On Fri, 27 Mar 2020 01:39:04 -0400 Scott Kitterman
wrote:
> On Fri, 27 Mar 2020 01:25:28 -0400 Scott Kitterman
> wrote:
> > I can replicate this with the current pip in unstable (which is the
current
> > upstream release). We kept pep517 at version 0.7.0 because tha
On Fri, 10 May 2019 19:30:58 +0200 =?UTF-8?Q?Josu=c3=a9_Tille?=
wrote:
> Package: python-pip
>
> Hello,
>
>
>
> Debian version : 9.9
>
> probable package : python-pip 9.0.1-2+deb9u1
>
>
> I detected that since some days the install of package with pip fail
> randomly with this stacktrace:
On Friday, April 3, 2020 10:57:10 AM EDT Jörg-Volker Peetz wrote:
> Package: python3-pip
> Version: 20.0.2-3
> Severity: wishlist
>
> Dear Debian Python Modules Team,
>
> this package is one of two on my system which still depends on
> python3.7. When is the shift to dependency on python3.8
On Mon, 12 Mar 2018 14:53:11 +0100 Bernhard Reiter
wrote:
> Package: python3-pip
> Version: 9.0.1-2
> Severity: normal
>
> Hi Maintainers,
>
> according to `pip help install`::
>
> --user
> [..]
> On Debian systems, this is the default when running outside of a
> virtual environment and
This is not a major issue in the package, but the .tx directory with the
Transifex config file in it doesn't need to be shipped in the binary. You
might want to look at how mitya57 dealt with it in sphinxcontrib-
serializinghtml. It seems clean enough.
Scott K
Same comment about the .tx directory for this package as I just sent for the
qthelp one.
Scott K
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
Please do not add lintian overrides like this:
# I have not been able to run the testsuite successfully, and I'm not sure it's
# possible to run it on a headless machine.
# See https://github.com/jaseg/python-mpv/issues/108 for more details.
source: testsuite-autopkgtest-missing
# There is an
On Tue, 31 Mar 2020 14:31:40 +0200 Christoph Reiter
wrote:
> Package: python3-pip
> Version: 20.0.2-2
> Severity: important
>
> Dear Maintainer,
>
> (Note: This doesn't affect upstream pip, only the Debian/Ubuntu version)
>
> pip in Debian (and Ubuntu focal) fails to install Python packages
Package: src:python-bleach
Version: 3.1.2-0+deb10u1
Severity: important
Tags: security
Once again with a python-bleach security issue...
https://github.com/mozilla/bleach/security/advisories/GHSA-vqhp-cxgc-6wmm
Title
regular expression denial-of-service (ReDoS) in
This is just a minor issue, but I think it would make sense that both
python-requests and python3-requests would Suggest: python-requests-doc.
Please consider for your next upload.
Scott K
___
Python-modules-team mailing list
I am going to accept this package, however I noted two issues that should be
addressed in a future upload:
1. Please change py3versions -i to py3versions -s in your autopkgtest.
testing against whatever python3 versions that happen to be installed is
unreliable (this was a huge issue in the
I am going to accept this package. I did notice that there are copyright
attributions missing. Since this is for an Apache-2.0 project they are not
required for license compliance, but they are required by Debian policy.
Please add them in your next upload.
src/libais/decode_body.cpp://
I am going to accept this, but I suggest you reconider having the binary not
depend on python3-django. It's true that there is an indirect depends as
stated in the lintian override comment, but the standard Debian practice is
not to depend on indirect dependencies to pull things in. This package
Source: dateparser
Version: 0.7.2-1
Severity: normal
The current pip based install for the test includes two module not in
Debian:
jdatetime==3.1.0
umalqurra==0.2
As a result, 7 tests are skipped. Presumably this means that related
functionality isn't available to users of the Debian package.
Package: python3-dateparser
Version: 0.7.2-1
Severity: normal
While investigatin a resolution for #954147, I noticed the following
warning being emitted. Presumably this will turn to an error in the
future and should, at some point, be addressed:
Package: python3-dateparser
Version: 0.7.2-1
Severity: important
While investigating what the minimal package set that python3-dateparser
needs to run its tests, I learned that adding python3-convertdate to the
test environment causes 107 additional test cases to run. This seems
like it's an
On Tuesday, April 28, 2020 5:48:04 PM EDT Rainer Dorsch wrote:
> Hello,
>
> I have another basic virtualenv question:
>
> I install covidify in a virtualenv and if finds the dependency
>
> Requirement already satisfied: docopt in /usr/lib/python3/dist-packages
> (from covidify) (0.6.2)
>
>
I do have something that might address this, but I'm reluctant to promise
anything until I test it.
Scott K
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
1 - 100 of 135 matches
Mail list logo