On November 24, 2021 1:54:48 PM UTC, Stuart Prescott wrote:
>On Wednesday, 24 November 2021 18:05:57 AEDT Stuart Prescott wrote:
>> I've looked at them and fixed most of the tests locally without issues. I
>> guess I should push that somewhere so that it is visible. I'll start a
>> draft PR
On Tue, 16 Nov 2021 01:30:55 +1100 Stuart Prescott wrote:
> Hi Scott & Tobias
>
> On Monday, 15 November 2021 21:13:09 AEDT Dr. Tobias Quathamer wrote:
> > On Sun, 14 Nov 2021 20:30:06 -0500 Scott Kitterman
> >
> > wrote:
> > > I looked at this a bit t
Package: python3-eventlet
Version: 0.30.2-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
Once again, eventlet is incompatible with dnspython and needs fixing.
The specific test that is failing is
I looked at this a bit today and it looks like the test failures are due to
updates in the iso-codes data used by the tests, not any real failures. I
think disabling the failing tests for now would be a reasonable way to keep
this in testing (I'm interested to avoid transitive removal of
It's not clear that there's any postfix issue here. If there is in fact a
postfix issue please reopen and attach logs that demonstrate the issue along
with the output of postconf -n.
Scott K
Package: mailmain3
Version: 3.3.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
mailman3 now fails tests with authheaders 0.14.1 since support for
comments in ARC results was added. Although this isn't precisely an
FTBFS, a
ll depending packages are kicked out of testing.
>
> Best,
> Jan
>
> On Mon, 03 Aug 2020 13:54:57 + Scott Kitterman
>
> wrote:
> > This is probably a result of a new GCC version. C++ symbols can be
> > painful to manage. This will be trivial to update the next ti
On Tuesday, August 11, 2020 1:38:52 PM EDT Peter Wienemann wrote:
> Hi Scott,
>
> On 11.08.20 17:54, Scott Kitterman wrote:
> > Unless you object, I'll probably do an NMU to do that since this will
> > block dnspython testing migration. I'll post a diff to th
On Tuesday, August 11, 2020 1:38:52 PM EDT Peter Wienemann wrote:
> Hi Scott,
>
> On 11.08.20 17:54, Scott Kitterman wrote:
> > Unless you object, I'll probably do an NMU to do that since this will
> > block dnspython testing migration. I'll post a diff to th
Package: dnstwist
Version: 0~20200424-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using FTBTS tag since it's the closest thing we have to this
(since autopkgtest failures block testing migration).
>From the autopkgtest log
This is probably a result of a new GCC version. C++ symbols can be painful to
manage. This will be trivial to update the next time I update the package.
Scott K
On August 3, 2020 9:15:16 AM UTC, Szczepan Zalega | Nitrokey
wrote:
>On 8/3/20 10:41 AM, Lucas Nussbaum wrote:
>>
On June 20, 2020 2:40:58 AM UTC, Sandro Tosi wrote:
>Control: reopen -1
>
>This bug was closed, but the package has still some dependencies
>towards
>Python2 packages, in details:
>
>(source:python-pip)Build-Depends->python-pkg-resources
>(source:python-pip)Build-Depends->python-setuptools
>
ibió:
>> >
>> > Hi,
>> >
>> > I will fix it today
>> >
>> > Cheers,
>> > Arias Emmanuel
>> > @eamanu
>> > http://eamanu.com
>> >
>> > El mié., 17 de jun. de 2020 a la(s) 19:18, Scott Kitterman
>> >
On Wed, 17 Jun 2020 21:12:40 +0200 Paul Gevers wrote:
> Source: impacket, smbmap
> Control: found -1 impacket/0.9.21-1
> Control: found -1 smbmap/1.8.2-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks
On Wednesday, June 10, 2020 12:02:48 PM EDT Olek Wojnar wrote:
> On Wed, Jun 10, 2020 at 11:48 AM Scott Kitterman
>
> wrote:
> > The only one who ever uploaded the package does not appear to be active in
> > Debian any longer, so I would suggest you go ahead.
>
> Than
On Wednesday, June 10, 2020 11:39:31 AM EDT Olek Wojnar wrote:
> On Mon, Jun 8, 2020 at 2:03 PM Moritz Mühlenhoff wrote:
> > Has there been any update wrt lightyears/Py3 being moved to the Debian
> > Games
> > Team?
>
> I haven't heard anything although I'm still willing to sponsor once we
>
On Thu, 4 Jun 2020 21:21:53 +0100 peter green wrote:
> Package: vanguards
> Version: 0.3.1-2
> Severity: serious
>
> vanguards build-depends on pypy-pytest which depends on pypy-funcsigs which
is no longer built by the python-funcsigs source package. The pytest
maintainer has also said they
On Friday, June 5, 2020 9:44:03 AM EDT you wrote:
> Dear Maintainer
>
> I think I got it. Maybe updating the manpage would be very helpfull for
> other people who stumble over the same problem.
>
> DMARC needs to do an SPF check.
>
> Well I have milter-greylist already performing SPF check, so
progress on
+python2 removal (Closes: #956903)
+
+ -- Scott Kitterman Fri, 15 May 2020 12:25:16 -0400
+
llvm-toolchain-6.0 (1:6.0.1-14) unstable; urgency=medium
* debian/patches/947f9692440836dcb8d88b74b69dd379d85974ce.patch:
diff -Nru llvm-toolchain-6.0-6.0.1/debian/control llvm
On Thursday, May 7, 2020 2:00:58 PM EDT peter green wrote:
> I got a failure too when I cloned that branch and tried to build it, but
> once I added in the changes from the previous NMU it built fine. I would
> push that addition back to the branch but i'm not currently a member of the
> python
On Fri, 10 Apr 2020 02:40:07 + Scott Kitterman
wrote:
> This is not a bug. Python2 is no longer supported upstream and we are in
the process of removing it.
For anyone coming along looking for additional information, as of pip 20.1,
which as I write this is about to be uploaded to Deb
Package: src:kineticstools
Version: 0.6.1+20161222-1
Severity: serious
Justification: Policy 2.1
All versions of kineticstools in the archive include a non-free data
file:
doc/whitepaper/kinetics.tex
The file includes the following statement:
For Research Use Only. Not for use in diagnostic
Actually I was slightly wrong about the changes due to the upcoming policy
change. A copy of the license will still be needed in debian/copyright for
pkg_resources/_vendor/pyparsing.py:
setuptools/_vendor/pyparsing.py:
pkg_resources/_vendor/six.py:
setuptools/_vendor/six.py:
It's only the
Package: src:python-setuptools
Version: 40.8.0-1
Severity: serious
Justification: Policy 2.3
While reviewing src:setuptools in New, I noticed a number of omissions
from debian/copyright which apply to this package as well.
Copyright and license information from the following files is missing.
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.
>
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 April 19, 2020 1:55:20 PM UTC, Luke Kenneth Casson Leighton
wrote:
>On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System
> wrote:
>
>> #958166: python3-all: python3 can't import gmpy2
>> Python3.7 is no longer supported in Debian Unstable and Testing and
>will be removed shortly.
>
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
>>
>>
Package: tpm2-tools
Version: 4.1.1-1
Severity: serious
Justification: Policy 3.3
Policy requires a valid maintainer email address. Please see below:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
Package: clang-tidy-6.0
Version: 1:6.0.1-14
Severity: serious
The clang-tidy-6.0 package depends on python-yaml, which is now NBS and
will be removed from Testing at some point. I understand that llvm 6.0
is sticking around to support ghc, but is clang-tidy needed for that?
If that binary could
Package: python-reclass
Version: 1.4.1-3.1
Severity: serious
Python-yaml is now NBS and will be removed from Testing at some point.
Python-reclass either needs to drop the python-yaml depends (I haven't
investigated if this is feasible) or move to python3 and depend on
python3-yaml.
I'm aware
Package: sabnzbdplus
Version: 2.3.6+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag since it is the closest one we have.
sabnzbdplus depends on python-cheetah, which is not longer built by
cheetah.
What's the status on getting this fixed? This is causing quite a backlog on
Testing migration.
requests Migrates after: datalad-container
python-urllib3 Migrates after: requests
python-certifi Migrates after: requests
python-pip Migrates after: python-certifi, python-urllib3, requests
Those I
(Closes:
+#954478)
+
+ -- Scott Kitterman Sat, 28 Mar 2020 17:45:23 -0400
+
python-pbkdf2 (1.3+20110613.git2a0fb15~ds0-3.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control python-pbkdf2-1.3+20110613.git2a0fb15~ds0
On Wed, 25 Mar 2020 22:18:52 -0300 eamanu wrote:
> Hi,
>
> I attach a NMU patch. Please, consider apply it.
I intend to sponsor this.
Scott K
signature.asc
Description: This is a digitally signed message part.
On Wed, 25 Mar 2020 22:01:38 -0300 eamanu wrote:
> Hi,
>
> I attach a NMU patch. Please, consider apply it.
RC bug with no maintainer response for 7 days, so I intend to sponsor this.
Scott K
signature.asc
Description: This is a digitally signed message part.
On Wed, 25 Mar 2020 14:16:23 -0300 eamanu wrote:
> Hi,
>
> I attach a NMU patch. Please consider apply it.
RC bug with no maintainer response for 7 days, so I intend to sponsor this.
Scott K
signature.asc
Description: This is a digitally signed message part.
On Wed, 25 Mar 2020 11:07:49 -0300 eamanu wrote:
> Hi,
>
> I attach a NMU patch. Please, consider apply it.
RC bug with no response from the maintainer for a week, so I intend to sponsor
this.
Scott K
signature.asc
Description: This is a digitally signed message part.
On Friday, March 27, 2020 12:53:41 PM EDT Benjamin Drung wrote:
> Hi,
>
> Am Dienstag, den 17.03.2020, 09:47 -0400 schrieb Scott Kitterman:
> > Package: src:salt
> > Version: 3000+dfsg1-3
> > Severity: serious
> > Justification: Policy 2.2.1
> >
>
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
2019-10-05 21:50:32.0 -0400
+++ python-stem-1.7.1/debian/changelog 2020-03-24 16:47:02.0 -0400
@@ -1,3 +1,10 @@
+python-stem (1.7.1-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add fix from upstream to fix dictionary key error (Closes: #953863
+
+ -- Scott Kitterman
@@
+ariba (2.14.4+ds-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Build for all supported python3 versions to fix test failures in complex
+Python environments and ease python3 transitions (Closes: #951944)
+
+ -- Scott Kitterman Tue, 24 Mar 2020 11:14:59 -0400
+
ariba (2.14.4
The problem here is that py3versions -r falls back to supported versions when
no X-Python3-Versions header field is present in debian/control and pythonmagic
is only built for the current version:
https://packages.debian.org/sid/amd64/python3-pythonmagick/filelist
(shows only python3.8
Package: src:xapers
Version: 0.8.2-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
The following autopkgtest log extracted from [1] should be enough to
show the problem. It is currently showing up as a regression for
python3.8 as
Control: tag -1 pending
Hello,
Bug #954451 in tox reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #954467 in pydbus reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #954481 in python3-proselint reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: src:pyx3
Version: 0.15-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
python3-defaults
Package: src:wand
Version: 0.5.9-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:python3-proselint
Version: 0.10.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:python-tinyrpc
Version: 0.6-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:python-pbkdf2
Version: 1.3+20110613.git2a0fb15~ds0-3.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of
Package: src:python-jsonext
Version: 0.4.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:python-pynvim
Version: 0.4.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:python-jsbeautifier
Version: 1.10.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:python-h2
Version: 3.2.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:python-daemon
Version: 2.2.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:pystemd
Version: 0.7.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:pysha3
Version: 1.0.2-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag since that's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:pyethash
Version: 0.1.27-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag since that's the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:pyrlp
Version: 0.5.1-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag since it's the closes we have
This package failed a recent autopkgtest and this is one of the blockers for
python3-defaults
Package: src:pydbus
Version: 0.6.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it's the closest one we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:m2crypto
Version: 0.31.0-9
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using FTBFS as a tag since it is the closest we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:editorconfig-core-py
Version: 0.12.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Used FTBFS as a tag, since it's the closes we have.
This package failed a recent autopkgtest and this is one of the blockers for
Package: src:ariba
Version: 2.14.4+ds-2
Followup-For: Bug #951944
This package failed a recent autopkgtest and this is one of the blockers for
python3-defaults migration. It failed because python3.7 was installed in the
chroot and the current autopkgtest doesn't handle that.
Autopkgtests should
Now that I see PAPT is the maintainer, I guess it would be a team upload, not
an NMU. In any case if someone has a plan other than dropping the tests,
please say so in the bug.
Scott K
signature.asc
Description: This is a digitally signed message part.
Package: src:tox
Version: 3.13.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using FTBFS to cover autopkgtest failure as it is a rough
equivalent (package can't migrate to testing).
The python-virtualenv package can no
On Sat, 22 Feb 2020 10:54:23 +0100 Kay Hayen wrote:
> Hello,
>
> this is not explained in the FAQ, but the way I have done it is like this
> (in build-depends, removed irrelevant parts):
>
>python (>= 2.6.6-2) | base-files (>= 11),
>python-all-dbg (>= 2.6.6-2) |
On Thursday, March 19, 2020 6:24:22 PM EDT Salvatore Bonaccorso wrote:
> Hi Scott,
>
> On Thu, Mar 19, 2020 at 12:20:25AM -0400, Scott Kitterman wrote:
> > Upstream's 3.1.2 release had just the security fix in it. I propose
> > updating buster with it (I put 3.1.3 in uns
On Thursday, March 19, 2020 7:14:12 AM EDT you wrote:
> Package: ftp.debian.org
> Followup-For: Bug #953942
>
> Wow. Gone in 4 days.
> While I can understand that ftpmasters are triggerhappy due to the py2
> removal, that seems excessive.
>
> As for the "no upstream activity", that tends to
--
diff -Nru python-bleach-3.1.1/debian/changelog python-bleach-3.1.2/debian/changelog
--- python-bleach-3.1.1/debian/changelog 2020-02-27 05:53:52.0 -0500
+++ python-bleach-3.1.2/debian/changelog 2020-03-19 00:14:11.0 -0400
@@ -1,3 +1,9 @@
+python-bleach (3.1.2-0+
Control: tag -1 pending
Hello,
Bug #954236 in python-bleach reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: python3-bleach
Version: 3.1.1-0+deb10u1
Severity: serious
Tags: security upstream
>From the upstream CHANGES for 3.1.2, which I just noticed:
**Security fixes**
* ``bleach.clean`` behavior parsing embedded MathML and SVG content
with RCDATA tags did not match browser behavior and
Control: tag -1 pending
Hello,
Bug #948416 in automat reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Fix autopkgtest to reliably run with multiple python3 versions installed
+
+ -- Scott Kitterman Wed, 18 Mar 2020 15:30:59 -0400
+
appdirs (1.4.3-2) unstable; urgency=medium
* Move repository to salsa.debian.org
diff -Nru appdirs-1.4.3/debian/tests/control appdirs-1.4.3/debian/tests/control
-
@@
+python-lockfile (1:0.12.2-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix autopkgtest to work reliably with multiple supported python3 versions
+(Closes: #954205)
+
+ -- Scott Kitterman Wed, 18 Mar 2020 09:13:51 -0400
+
python-lockfile (1:0.12.2-2.1) unstable; urgency=medium
Package: src:python-lockfile
Version: 1:0.12.2-2.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Using FTBFS since autopkgtest failures are blocking and it's the closes
tag we have.
The python-lockfile autopkgtest runs against all
Package: src:salt
Version: 3000+dfsg1-3
Severity: serious
Justification: Policy 2.2.1
This package uses python pip to download and install packages from outside the
Debian archive to run autopkgtests. Main is required to be self-contained,
including for tests. See the FTP Master's reject FAQ
Package: src:python-virtualenv
Version: 15.1.0+ds-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
This is really an autopkgtest failure bug, but I think ftbfs is the
closest tag we have.
Please drop the autopkgtests for
Package: src:logbook
Version: 1.5.3-2
Severity: serious
Justification: Policy 2.2.1
This package uses python pip to download and install packages from outside the
Debian archive to run autopkgtests. Main is required to be self-contained,
including for tests. See the FTP Master's reject FAQ [1]
Package: src:ffc
Version: 2019.1.0.post0-2
Severity: serious
Justification: Policy 2.2.1
This package uses python pip to download and install packages from outside the
Debian archive to run autopkgtests. Main is required to be self-contained,
including for tests. See the FTP Master's reject FAQ
Package: src:doit
Version: 0.31.1-3.2
Severity: serious
Justification: Policy 2.2.1
This package uses python pip to download and install packages from outside the
Debian archive to run autopkgtests. Main is required to be self-contained,
including for tests. See the FTP Master's reject FAQ [1]
Package: src:dateparser
Version: 0.7.2-1
Severity: serious
Justification: Policy 2.2.1
This package uses python pip to download and install packages from outside the
Debian archive to run autopkgtests. Main is required to be self-contained,
including for tests. See the FTP Master's reject FAQ
-maintainer upload.
+ * Temporarily use internal msgpack to fix FTBFS and fix borgbackup to work
+again (Closes: #953989)
+
+ -- Scott Kitterman Mon, 16 Mar 2020 06:25:57 -0400
+
borgbackup (1.1.11-2) unstable; urgency=medium
[ Andrej Shadura ]
diff -Nru borgbackup-1.1.11/debian/patches/series
On Sun, 15 Mar 2020 12:16:54 + Gordon Ball wrote:
> Package: borgbackup
> Version: 1.1.11-2
> Severity: grave
> Justification: renders package unusable
>
> After updating python3-msgpack from 0.5.6-3 -> 0.6.2-1, attempting to
> run any borg command fails with the following message, making
Control: tag -1 pending
Hello,
Bug #938027 in python-pip reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
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
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
ainer upload.
+ * No change source upload to allow fixes for #937277 to make it to Testing
+
+ -- Scott Kitterman Mon, 09 Mar 2020 19:39:30 -0400
+
pg-activity (1.5.0-1) unstable; urgency=medium
* New upstream release
signature.asc
Description: This is a digitally signed message part.
Package: src:zorp
Version: 7.0.1~alpha2-3
Severity: serious
Justification: Policy 2.2.1
This package Depends/Build-Depends on python-dnspython which is an NBS cruft
package. Please update your package to use python3-dnspython, which is still
provided (if the package will be ported to python3).
Package: src:mailman
Version: 1:2.1.29-1
Severity: serious
Justification: Policy 2.2.1
This package Depends/Build-Depends on python-dnspython which is an NBS cruft
package. Please update your package to use python3-dnspython, which is still
provided (if the package will be ported to python3).
Package: src:linkchecker
Version: 9.4.0-2
Severity: serious
Justification: Policy 2.2.1
This package Depends on python-dnspython which is an NBS cruft package. Please
update your package to use python3-dnspython, which is still provided (if the
package will be ported to python3).
Scott K
Package: src:knockpy
Version: 4.1.0-1
Severity: serious
Justification: Policy 2.2.1
This package Depends/Build-Depends on python-dnspython which is an NBS cruft
package. Please update your package to use python3-dnspython, which is still
provided (if the package will be ported to python3).
Package: src:hash-slinger
Version: 2.7-1
Severity: serious
Justification: Policy 2.2.1
This package Depends on python-dnspython which is an NBS cruft package. Please
update your package to use python3-dnspython, which is still provided (if the
package will be ported to python3).
Scott K
Package: src:easyzone
Version: 1.2.2-1
Severity: serious
Justification: Policy 2.2.1
This package Depends/Build-Depends on python-dnspython which is an NBS cruft
package. Please update your package to use python3-dnspython, which is still
provided (if the package will be ported to python3).
Control: tag -1 pending
Hello,
Bug #952782 in dnspython reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #937331 in psycopg2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
-02 00:22:40.0 -0500
@@ -1,3 +1,10 @@
+pacparser (1.3.6-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drup python-pacparser - obsolete, no rdepends (Closes: #937229)
+
+ -- Scott Kitterman Mon, 02 Mar 2020 00:22:40 -0500
+
pacparser (1.3.6-1.1) unstable; urgency=medium
log 2020-02-07 12:57:44.0 -0500
+++ sympy-1.5.1/debian/changelog 2020-03-01 15:45:01.0 -0500
@@ -1,3 +1,11 @@
+sympy (1.5.1-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add d/p/python3-not-python.patch from Ubuntu to fix FTBFS with python3
+ (Closes: #952251)
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
101 - 200 of 966 matches
Mail list logo
