Processing control commands:
> severity -1 grave
Bug #994223 [lintian-brush] lintian-brush crashes with multiple sources
Severity set to 'grave' from 'important'
> retitle -1 lintian-brush unusable
Bug #994223 [lintian-brush] lintian-brush crashes with multiple sources
Changed Bug title to
> I've moved the package under the games-team [1]. I was going to give you
> access to it but I can't find a Salsa account for you. If you don't have an
> account yet, you can easily create one [2] and let me know your username.
> I'll then give you access to the repository and you can make all of
On Wednesday, September 15, 2021 2:48:01 P.M. CDT Timo Röhling wrote:
> Control: tags 994419 + ftbfs
I thought this tag was for the case that the package fails to build from
source. ?? https://www.debian.org/Bugs/Developer
> I just noticed that this bug not only breaks autopkgtest
What
Processing commands for cont...@bugs.debian.org:
> Tags 993832 +patch
Bug #993832 [src:synfig] synfig FTBFS with mlt 7
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
993832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993832
Debian Bug
Tags 993832 +patch
thanks
I found a fix in the upstream git repo and was able to apply it to the Debian
package and build sucessfully in raspbian bookworm-staging. A debdiff is
available at
https://debdiffs.raspbian.org/main/s/synfig/synfig_1.4.0+dfsg-2+rpi1.debdiff
no intent to NMU in Debian.
On Wednesday, September 15, 2021 2:25:49 P.M. CDT Timo Röhling wrote:
> Package: libgtest-dev
> Version: 1.10.0.20201025-1.1
I've discovered that upstream has released 1.11 -- which I'll package up.
> the GTestTargets.cmake that is shipped in libgtest-dev also exports
> the GTest::gmock and
On 20210915@22:12, Paul Gevers wrote:
> Source: octave-sparsersb
> Version: 1.0.8-3
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: flaky timesout
>
> Dear maintainer(s),
&
On Wednesday, September 15, 2021 2:48:01 P.M. CDT Timo Röhling wrote:
> > Please add Depends: libgmock-dev to libgtest-dev.
>
> I just noticed that this bug not only breaks autopkgtest but also
> causes fastcdr to FTBFS.
>
> In case you're wondering, apparently this bug has been exposed by
>
Hi Paul,
Paul Gevers, on 2021-09-15:
> On 15-09-2021 18:51, Étienne Mollier wrote:
> > I intend to adjust the d/tests/control Architecture field of
> > resfinder to match the (pending upload) list of architectures
> > supported by kma. Would this be sufficient to bring back
> > resfinder to
Your message dated Wed, 15 Sep 2021 22:50:04 +
with message-id
and subject line Bug#993861: fixed in zsh 5.8-8
has caused the Debian Bug report #993861,
regarding zsh: FTBFS iff transitional package libncursesw5-dev is not installed
but a package providing it (dpkg-gencontrol: error: parsing
Processing control commands:
> tags -1 +pending +patch
Bug #978813 [src:fswatch] fswatch: ftbfs with autoconf 2.70
Added tag(s) pending.
Bug #978813 [src:fswatch] fswatch: ftbfs with autoconf 2.70
Added tag(s) patch.
--
978813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978813
Debian Bug
Control: tags -1 +pending +patch
Dear maintainer,
I've prepared an NMU for fswatch (versioned as 1.14.0+repack-13.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru fswatch-1.14.0+repack/debian/changelog fswatch-
Hi Paul,
Paul Gevers, on 2021-09-14:
> With a recent upload of resfinder the autopkgtest of resfinder fails in
> testing on armhf and i386 when that autopkgtest is run with the binary
> packages of resfinder from unstable. It passes when run with only
> packages from testing.
True, newer
Your message dated Wed, 15 Sep 2021 20:23:38 +
with message-id
and subject line Bug#994349: fixed in python-cffi 1.14.6-2
has caused the Debian Bug report #994349,
regarding python-cffi: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim
Your message dated Wed, 15 Sep 2021 20:23:31 +
with message-id
and subject line Bug#994341: fixed in pystemmer 2.0.1+dfsg-3
has caused the Debian Bug report #994341,
regarding pystemmer: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim
Your message dated Wed, 15 Sep 2021 20:22:11 +
with message-id
and subject line Bug#992704: fixed in jupyter-notebook 6.4.3-1
has caused the Debian Bug report #992704,
regarding jupyter-notebook: CVE-2021-32798
to be marked as done.
This means that you claim that the problem has been dealt
On Wed, Sep 15, 2021 at 09:24:08PM +0200, Paul Gevers wrote:
> I looked at the results of the autopkgtest of you package on amd64
> because with a recent upload of glibc the autopkgtest of ocfs2-tools
> fails in testing. It seems to me that the failures are related to the
> worker that the test
Control: tag -1 patch
Hi Thibaut,
Since version 2.70, autoreconf has become somewhat more picky
about the macro expansions, and they seem to need a bit more
protection. I adjusted some parts of the configure.ac until it
fixed the configure process, in the patch in attachment. (Maybe
not all
Source: octave-sparsersb
Version: 1.0.8-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: flaky timesout
Dear maintainer(s),
I looked at the results of the autopkgtest of you package on armhf
because with a recent upload of
Processing commands for cont...@bugs.debian.org:
> severity 994228 important
Bug #994228 [gfortran-11] gfortran-11: generates incorrect Iftran compiler
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994228:
Source: pytorch-vision
Version: 0.8.2-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
| I: pybuild base:232: python3.9 setup.py clean
| Illegal instruction
| E: pybuild pybuild:353:
Source: spice-vdagent
Version: 0.20.0-2
Severity: serious
Tags: ftbfs
spice-vdagent fails to build from source in unstable. A non-parallel
build ends as follows:
| gcc -DHAVE_CONFIG_H -I. -I./src -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/include/libdrm -I/usr/include/spice-1 -pthread
Processing control commands:
> severity 994419 serious
Bug #994419 [libgtest-dev] libgtest-dev: missing dependency on libgmock-dev
Severity set to 'serious' from 'important'
> affects 994419 + src:fastcdr
Bug #994419 [libgtest-dev] libgtest-dev: missing dependency on libgmock-dev
Added indication
Oops, forgot the log
On 15-09-2021 21:42, Paul Gevers wrote:
> I looked at the results of the autopkgtest of you package on amd64
> because with a recent upload of glibc the autopkgtest of cdebootstrap
> fails in testing. It seems to me that the failures are related to the
> worker that the test
Your message dated Wed, 15 Sep 2021 19:48:47 +
with message-id
and subject line Bug#994259: fixed in resfinder 4.1.5-2
has caused the Debian Bug report #994259,
regarding resfinder: autopkgtest regression on armhf and i386: db_resfinder
--kmaPath /usr/bin/kma' returned non-zero exit status 1
Processing control commands:
> tag -1 pending
Bug #994341 [src:pystemmer] pystemmer: Removal of the python3-*-dbg packages in
sid/bookworm
Added tag(s) pending.
--
994341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #994349 in python-cffi 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:
Processing control commands:
> tag -1 pending
Bug #994349 [src:python-cffi] python-cffi: Removal of the python3-*-dbg
packages in sid/bookworm
Added tag(s) pending.
--
994349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #994341 in pystemmer 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:
Source: cdebootstrap
Version: 0.7.8
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package on amd64
because with a recent upload of glibc the
Source: ocfs2-tools
Version: 1.8.6-6
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package on amd64
because with a recent upload of glibc the
Your message dated Wed, 15 Sep 2021 18:48:55 +
with message-id
and subject line Bug#993992: fixed in ncl 6.6.2-10
has caused the Debian Bug report #993992,
regarding ncl: FTBFS on i386, mipsel, mips64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Package: glx-diversions
Followup-For: Bug #993338
X-Debbugs-Cc: witold.bary...@gmail.com
I noticed that removing the non-free and/or contrib from the suites
available during live-build process in my scripts, causes nvidia drivers
to not be installed, and bug no longer reproducible.
So indeed it
Processing commands for cont...@bugs.debian.org:
> tags 994286 + sid bookworm
Bug #994286 [r-bioc-destiny] r-bioc-destiny: Orphaned upstream, marked for
removal in next BioConductor release
Added tag(s) sid and bookworm.
> found 994286 3.4.0-1
Bug #994286 [r-bioc-destiny] r-bioc-destiny:
Hi,
On 15-09-2021 18:51, Étienne Mollier wrote:
> I intend to adjust the d/tests/control Architecture field of
> resfinder to match the (pending upload) list of architectures
> supported by kma. Would this be sufficient to bring back
> resfinder to testing, or is there some knob to twiddle on CI
Processing commands for cont...@bugs.debian.org:
> forwarded 994285 https://github.com/seccomp/libseccomp/issues/336
Bug #994285 [src:libseccomp] libseccomp: FTBFS on arm64, armhf, mips64el and
mipsel
Set Bug forwarded-to-address to
'https://github.com/seccomp/libseccomp/issues/336'.
> thanks
Your message dated Wed, 15 Sep 2021 17:04:28 +
with message-id
and subject line Bug#994299: fixed in dbus-python 1.2.18-3
has caused the Debian Bug report #994299,
regarding dbus-python: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim
Le 15/09/2021 à 16:10, Sebastiaan Couwenberg a écrit :
> Since this only exists as part of the node-carto dependency chain,
> removing this package along with node-millstone and node-carto is
> probably a better idea than spending time fixing this issue.
>
> Kind Regards,
>
> Bas
Hi JS Team,
Hallo again,
On Sun, Sep 12, 2021 at 10:29:35AM +0200, Benedikt Tuchen wrote:
> I've made an update to Debian 11 and after the update I tried to use
> "vdirsyncer metasync" with my old configuration. While trying I got
> the following error message:
>
>
> error: Unknown error occurred:
Processing control commands:
> tag -1 patch
Bug #978831 [src:gyoto] gyoto: ftbfs with autoconf 2.70
Added tag(s) patch.
--
978831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> notfound 994373 22.2.1-2
Bug #994373 {Done: Gordon Ball } [src:pyzmq] pyzmq:
Removal of the python3-*-dbg packages in sid/bookworm
No longer marked as found in versions pyzmq/22.2.1-2.
> fixed 994373 22.2.1-2
Bug #994373 {Done: Gordon Ball }
Processing commands for cont...@bugs.debian.org:
> found 994373 22.2.1-1
Bug #994373 {Done: Gordon Ball } [src:pyzmq] pyzmq:
Removal of the python3-*-dbg packages in sid/bookworm
Marked as found in versions pyzmq/22.2.1-1.
> fixed 994373 22.2.1-2
Bug #994373 {Done: Gordon Ball } [src:pyzmq]
Package: libgmp10
Version: 2:6.2.1+dfsg-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
mpz_inp_raw segfaults (SEGV_MAPERR) on large sizes. I suspect that
this is due to an integer overflow in mpz/inp_raw.c:
abs_xsize =
Your message dated Wed, 15 Sep 2021 15:36:11 +
with message-id
and subject line Bug#994109: fixed in scilab 6.1.1+dfsg2-2
has caused the Debian Bug report #994109,
regarding scilab FTBFS with hdf5 1.10.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 15 Sep 2021 15:20:13 +
with message-id
and subject line Bug#994336: fixed in pyqt5chart 5.15.4+dfsg-1
has caused the Debian Bug report #994336,
regarding pyqt5chart: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim
Your message dated Wed, 15 Sep 2021 17:55:54 +0300
with message-id
and subject line Re: Bug#994339: pyqt5webengine: Removal of the python3-*-dbg
packages in sid/bookworm
has caused the Debian Bug report #994339,
regarding pyqt5webengine: Removal of the python3-*-dbg packages in sid/bookworm
to
Since this only exists as part of the node-carto dependency chain,
removing this package along with node-millstone and node-carto is
probably a better idea than spending time fixing this issue.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1
Processing commands for cont...@bugs.debian.org:
> found 994307 2.9.10+dfsg-6.7
Bug #994307 [src:libxml2] libxml2: Removal of the python3-*-dbg packages in
sid/bookworm
Marked as found in versions libxml2/2.9.10+dfsg-6.7.
> thanks
Stopping processing here.
Please contact me if you need
Your message dated Wed, 15 Sep 2021 13:49:16 +
with message-id
and subject line Bug#993698: fixed in hacktv 0+git20210914-1
has caused the Debian Bug report #993698,
regarding hacktv: FTBFS with libsoapysdr 0.8
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 15 Sep 2021 13:35:18 +
with message-id
and subject line Bug#993847: fixed in link-grammar 5.10.1~dfsg-3
has caused the Debian Bug report #993847,
regarding link-grammar: FTBFS on 32bit
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 15 Sep 2021 12:36:50 +
with message-id
and subject line Bug#994368: fixed in python-reportlab 3.5.67-2
has caused the Debian Bug report #994368,
regarding python-reportlab: Removal of the python3-*-dbg packages in
sid/bookworm
to be marked as done.
This means that
Your message dated Wed, 15 Sep 2021 12:36:38 +
with message-id
and subject line Bug#994317: fixed in pillow 8.1.2+dfsg-1
has caused the Debian Bug report #994317,
regarding pillow: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim that the
Your message dated Wed, 15 Sep 2021 12:19:49 +
with message-id
and subject line Bug#994347: fixed in python-bsddb3 6.2.9-2
has caused the Debian Bug report #994347,
regarding python-bsddb3: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim
Your message dated Wed, 15 Sep 2021 14:12:19 +0200
with message-id <4a670600-d1bd-f01a-aa2f-190add771...@debian.org>
and subject line closing false positives
has caused the Debian Bug report #994342,
regarding python3-defaults: Removal of the python3-*-dbg packages in
sid/bookworm
to be marked as
Your message dated Wed, 15 Sep 2021 14:12:19 +0200
with message-id <4a670600-d1bd-f01a-aa2f-190add771...@debian.org>
and subject line closing false positives
has caused the Debian Bug report #994344,
regarding python3-stdlib-extensions: Removal of the python3-*-dbg packages in
sid/bookworm
to be
Package: vdirsyncer
Version: 0.16.8-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
See the attached console session transcript :
```sh
❯ vdirsyncer -vdebug sync
debug: Using 1 maximal workers.
error: Unknown error occurred: unmatched ')' (, line 1)
error: Use
Your message dated Wed, 15 Sep 2021 11:51:31 +
with message-id
and subject line Bug#994329: fixed in pygccjit 0.4-12
has caused the Debian Bug report #994329,
regarding pygccjit: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim that the
Your message dated Wed, 15 Sep 2021 11:51:25 +
with message-id
and subject line Bug#994319: fixed in pillow-sane 2.9.1-2
has caused the Debian Bug report #994319,
regarding pillow-sane: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> close 994370 1.2.2-2
Bug #994370 [src:python-setproctitle] python-setproctitle: Removal of the
python3-*-dbg packages in sid/bookworm
Marked as fixed in versions python-setproctitle/1.2.2-2.
Bug #994370 [src:python-setproctitle]
Your message dated Wed, 15 Sep 2021 11:33:37 +
with message-id
and subject line Bug#994308: fixed in lxml 4.6.3+dfsg-1
has caused the Debian Bug report #994308,
regarding lxml: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> block 871621 by 936935
Bug #871621 [wnpp] ITP: virt-bootstrap -- Tool to setpu the root file system
for libvirt-based containers in an easy way
871621 was not blocked by any bugs.
871621 was not blocking any bugs.
Added blocking bug(s) of
Quoting Roderich Schupp (2021-09-15 12:22:55)
> > mark /usr/share/ghostscript/* as not-installed,
> > which is clearly bogus but seems the only (simple) way
> > to ignore only for arch-dependent builds;
>
>
> Another way to fix this is to use ${env:GS_DOT_VERSION} in
> libgs9-common.install
>
Package: src:zope.interface
Version: 5.2.0-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:xrayutilities
Version: 1.7.1-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:uvloop
Version: 0.16.0+ds1-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:thrift
Version: 0.13.0-6
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:twisted
Version: 20.3.0-7
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:storm
Version: 0.24-2
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:sip5
Version: 5.5.0+dfsg-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:sip6
Version: 6.1.1+dfsg-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:sip4
Version: 4.19.25+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:simplejson
Version: 3.17.5-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:silx
Version: 0.14.0+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:rrdtool
Version: 1.7.2-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:scipy
Version: 1.7.1-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:reprozip
Version: 1.0.16-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:pyzmq
Version: 22.2.1-2
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:qscintilla2
Version: 2.11.5+dfsg-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:pyyaml
Version: 5.3.1-5
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-setproctitle
Version: 1.2.2-2
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-sfml
Version: 2.2~git20150611.196c88+dfsg-6
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-reportlab
Version: 3.5.59-2
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-regex
Version: 0.1.20201113-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-pylibacl
Version: 0.6.0-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-pyxattr
Version: 0.7.2-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-psutil
Version: 5.8.0-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-pygraphviz
Version: 1.7-2
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-multidict
Version: 5.1.0-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-mysqldb
Version: 1.4.4-2
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-ltfatpy
Version: 1.0.16-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-llfuse
Version: 1.3.8+dfsg-2
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-levenshtein
Version: 0.12.2-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-librtmp
Version: 0.3.0-1.1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-greenlet
Version: 0.4.17-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-ldap
Version: 3.2.0-4
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-gevent
Version: 20.9.0-2
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-fabio
Version: 0.12.0+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-fisx
Version: 1.2.0-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-dmidecode
Version: 3.12.2-11
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
Package: src:python-djvulibre
Version: 0.8.4-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
1 - 100 of 163 matches
Mail list logo
