Processing control commands:
> severity -1 serious
Bug #947004 [r-bioc-s4vectors] Tests segfaults (since the r-base-core update?)
Severity set to 'serious' from 'normal'
--
947004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947004
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> severity -1 serious
Bug #947001 [r-bioc-iranges] Tests segfaults (since the r-base-core update?)
Severity set to 'serious' from 'normal'
--
947001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947001
Debian Bug Tracking System
Contact ow...@bugs.debian.org
* Ximin Luo [191223 12:58]:
> dpkg and all other debian tools support it right now. It is only reprepro
> with this artifical constraint, which makes it not work for packages that are
> processable by dpkg and other debian tools.
If it is artifical, then it is artifically high. It is 128 times
Processing commands for cont...@bugs.debian.org:
> tags 937212 + fixed-upstream
Bug #937212 [src:opensips] opensips: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937212:
Your message dated Tue, 24 Dec 2019 06:22:26 +
with message-id
and subject line Bug#937449: Removed package(s) from unstable
has caused the Debian Bug report #947303,
regarding pygopherd: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 24 Dec 2019 06:23:40 +
with message-id
and subject line Bug#947232: Removed package(s) from unstable
has caused the Debian Bug report #938507,
regarding snappea: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 24 Dec 2019 06:23:10 +
with message-id
and subject line Bug#947231: Removed package(s) from unstable
has caused the Debian Bug report #938783,
regarding virtio-forwarder: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> retitle 937174 RM: nwsserver -- removal triggered by the Python2 removal
Bug #937174 [ftp.debian.org] nwsserver: Python2 removal in sid/bullseye
Changed Bug title to 'RM: nwsserver -- removal triggered by the Python2
removal' from 'nwsserver:
Processing commands for cont...@bugs.debian.org:
> reassign 937174 ftp.debian.org
Bug #937174 [src:nwsserver] nwsserver: Python2 removal in sid/bullseye
Bug reassigned from package 'src:nwsserver' to 'ftp.debian.org'.
No longer marked as found in versions nwsserver/2.0.0-2.
Ignoring request to
Processing commands for cont...@bugs.debian.org:
> block 937170 with 941228
Bug #937170 [src:nvpy] nvpy: Python2 removal in sid/bullseye
937170 was not blocked by any bugs.
937170 was blocking: 937695 937907 938168 938198
Added blocking bug(s) of 937170: 941228
> thanks
Stopping processing here.
Control: tags 936992 + patch
Control: tags 936992 + pending
Dear maintainer,
I've prepared an NMU for maradns (versioned as 2.0.13-1.3) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru maradns-2.0.13/debian/changelog
Processing control commands:
> tags 936992 + patch
Bug #936992 [src:maradns] maradns: Python2 removal in sid/bullseye
Added tag(s) patch.
> tags 936992 + pending
Bug #936992 [src:maradns] maradns: Python2 removal in sid/bullseye
Added tag(s) pending.
--
936992:
Processing commands for cont...@bugs.debian.org:
> tags 936839 + fixed-upstream
Bug #936839 [src:lepton-eda] lepton-eda: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936839:
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # ipython-genutils
> block 936744 by 947298
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Processing commands for cont...@bugs.debian.org:
> tags 936830 + fixed-upstream
Bug #936830 [src:ldaptor] ldaptor: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936830:
Processing control commands:
> tags 936829 + patch
Bug #936829 [src:lcm] lcm: Python2 removal in sid/bullseye
Added tag(s) patch.
> tags 936829 + pending
Bug #936829 [src:lcm] lcm: Python2 removal in sid/bullseye
Added tag(s) pending.
--
936829:
Control: tags 936829 + patch
Control: tags 936829 + pending
Dear maintainer,
I've prepared an NMU for lcm (versioned as 1.3.1+repack1-2.3) and
uploaded it to DELAYED/15. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru lcm-1.3.1+repack1/debian/changelog
Processing commands for cont...@bugs.debian.org:
> tags 936825 + fixed-upstream
Bug #936825 [src:lazyarray] lazyarray: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936825:
Am Sonntag, den 22.12.2019, 22:11 +0200 schrieb Juhani Numminen:
> On Fri, 30 Aug 2019 07:25:11 + Matthias Klose
> wrote:
> > Package: src:londonlawVersion: 0.2.1-20Severity: normalTags: sid
> > bullseyeUser: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> > Python2 becomes
Your message dated Tue, 24 Dec 2019 04:37:08 +
with message-id
and subject line Bug#938231: fixed in python-tunigo 1.0.0-4
has caused the Debian Bug report #938231,
regarding python-tunigo: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Control: tags -1 moreinfo
On 12/23/19 10:01 PM, Andreas Beckmann wrote:
> python3-geopandas ships files with generic names at the generic location
> /usr/lib/python3/dist-packages/examples/ causing file clashes (e.g. on
> README.txt) with other packages doing the same wrong thing.
> Moving this
Processing control commands:
> tags -1 moreinfo
Bug #947266 [python3-geopandas] python3-geopandas: ships
/usr/lib/python3/dist-packages/examples/*
Added tag(s) moreinfo.
--
947266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947266
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Sandro Tosi writes:
>
> I've prepared an NMU for zfec (versioned as 1.5.2-2.1). The diff
> is attached to this message.
Thanks Sandro. I've merged your patch into Git.
Cheers,
Vasudev
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Package: libkate
Version: 0.4.1-10
Severity: serious
Tags: patch
Justification: autopkgtest regression
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Dear maintainers,
With the removal of libkate-tools in libkate 0.4.1-10, the libkate
autopkgtest consistently
Package: nyancat-server
Version: 1.5.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After installing nyancat-server and connecting to the socket, the client is
disconnected
and the following log entries are produced:
nyancat-server.socket: Failed to queue service
Your message dated Mon, 23 Dec 2019 20:43:29 -0500
with message-id
and subject line Re: osc-plugins-dput: Python2 removal in sid/bullseye
has caused the Debian Bug report #945679,
regarding osc-plugins-dput: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that
Your message dated Mon, 23 Dec 2019 23:36:54 +
with message-id
and subject line Bug#937809: fixed in python-hidapi 0.7.99.post21-1.1
has caused the Debian Bug report #937809,
regarding python-hidapi: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Mon, 23 Dec 2019 18:29:05 -0500
with message-id
and subject line Re: Bug#947216: yapps2: should this package be removed?
has caused the Debian Bug report #947216,
regarding yapps2: should this package be removed?
to be marked as done.
This means that you claim that the
Processing control commands:
> tags 937809 + patch
Bug #937809 [src:python-hidapi] python-hidapi: Python2 removal in sid/bullseye
Added tag(s) patch.
--
937809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 937809 + patch
Dear maintainer,
I've prepared an NMU for python-hidapi (versioned as 0.7.99.post21-1.1). The
diff
is attached to this message.
Regards.
diff -Nru python-hidapi-0.7.99.post21/debian/changelog python-hidapi-0.7.99.post21/debian/changelog
---
Source: freshplayerplugin
Version: 0.3.9-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
freshplayerplugin cannot be built in a current sid environment any more:
-- Checking for modules
Your message dated Mon, 23 Dec 2019 23:05:04 +
with message-id
and subject line Bug#936736: fixed in input-pad 1.0.3-4
has caused the Debian Bug report #936736,
regarding input-pad: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> forwarded 936804 https://github.com/guelfoweb/knock/issues/9
Bug #936804 [src:knockpy] knockpy: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 'https://github.com/guelfoweb/knock/issues/9'.
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> tags 936803 + fixed-upstream
Bug #936803 [src:kmodpy] kmodpy: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936803:
Your message dated Mon, 23 Dec 2019 22:51:12 +
with message-id
and subject line Bug#938015: fixed in python-pecan 1.3.3-2
has caused the Debian Bug report #938015,
regarding python-pecan: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 23 Dec 2019 22:35:39 +
with message-id
and subject line Bug#938010: fixed in python-pbkdf2
1.3+20110613.git2a0fb15~ds0-3.1
has caused the Debian Bug report #938010,
regarding python-pbkdf2: Python2 removal in sid/bullseye
to be marked as done.
This means that you
Your message dated Mon, 23 Dec 2019 22:36:12 +
with message-id
and subject line Bug#938818: fixed in whatthepatch 0.0.5-2.1
has caused the Debian Bug report #938818,
regarding whatthepatch: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Control: tags 938818 + patch
Dear maintainer,
I've prepared an NMU for whatthepatch (versioned as 0.0.5-2.1). The diff
is attached to this message.
Regards.
diff -Nru whatthepatch-0.0.5/debian/changelog whatthepatch-0.0.5/debian/changelog
--- whatthepatch-0.0.5/debian/changelog 2018-04-23
Processing control commands:
> tags 938818 + patch
Bug #938818 [src:whatthepatch] whatthepatch: Python2 removal in sid/bullseye
Added tag(s) patch.
--
938818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Mon, Dec 23, 2019 at 06:42:00PM +, Colin Watson wrote:
> On Sun, Dec 22, 2019 at 06:57:24PM -0500, Sandro Tosi wrote:
> > Python 2 is end-of-life, and there are no more rdeps for python-yapps2, but
> > python3-yapps2 seems broken beyond repair: #911753, #911752.
> >
> > I believe this is a
Processing commands for cont...@bugs.debian.org:
> # FTBFS in experimental
> found 936854 20171104-1
Bug #936854 {Done: Raphaël Hertzog }
[src:libewf] libewf: Python2 removal in sid/bullseye
Marked as found in versions libewf/20171104-1 and reopened.
> severity 936854 serious
Bug #936854
Processing commands for cont...@bugs.debian.org:
> tags 911730 patch pending
Bug #911730 [src:yapps2] yapps2: writes __future__ import after preparser
Added tag(s) pending and patch.
> tags 911752 patch pending
Bug #911752 [src:yapps2] yapps2: half of examples in source package broken with
Processing control commands:
> tags 938010 + patch
Bug #938010 [src:python-pbkdf2] python-pbkdf2: Python2 removal in sid/bullseye
Added tag(s) patch.
--
938010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 938010 + patch
Dear maintainer,
I've prepared an NMU for python-pbkdf2 (versioned as
1.3+20110613.git2a0fb15~ds0-3.1). The diff
is attached to this message.
Regards.
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog
I just tested it and the problem is that the dm_cache_smq module is missing
from initramfs. Adding it to "/etc/initramfs-tools/modules" and running
"update-initramfs -u" addresses the problem.
I guess that lvm2 should add dm_cache and dm_cache_smq to
/usr/share/initramfs-tools/hooks/lvm2, just
Package: src:paraview
Version: 5.7.0-3
Severity: serious
Tags: patch
Justification: FTBFS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
The same error is spotted in the logs of failed paraview 5.7.0 builds for
armel[1] and mipsel[2]:
/usr/bin/ld:
Source: xmlelements
Version: 1.0~prerelease-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
xmlelements/experimental FTBFS:
fakeroot debian/rules clean
dh clean --with=python2,python3
dh: unable to load addon python3: Can't locate
Source: arriero
Version: 0.7~20161228-1+build1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
arriero/experimental FTBFS:
fakeroot debian/rules clean
dh clean --with python3
dh: unable to load addon python3: Can't locate
Debian/Debhelper/Sequence/python3.pm in
Your message dated Mon, 23 Dec 2019 21:54:13 +
with message-id
and subject line Bug#943194: fixed in raccoon 1.0b-5
has caused the Debian Bug report #943194,
regarding raccoon: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
> (gdb) bt
> #0 __memmove_avx_unaligned_erms () at
> ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:416
> #1 0x706c6dcd in memcpy (__len=3556, __src=,
> __dest=0x0) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
> #2 _soxr_interleave_f (data_type=,
>
Source: singularity
Version: 1.0a1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
singularity/experimental FTBFS in a minimal chroot:
fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh_auto_clean
Processing commands for cont...@bugs.debian.org:
> reassign 947212 src:wordpress
Bug #947212 [wordpress] wordpress: 5.3.2 new upstream bug-fixing release
available.
Bug reassigned from package 'wordpress' to 'src:wordpress'.
No longer marked as found in versions wordpress/5.2.4+dfsg1-1.
Ignoring
Source: odhcp6c
Version: 1.1+git20160131-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
odhcp6c FTBFS with GCC 9:
[ 33%] Building C object CMakeFiles/odhcp6c.dir/src/dhcpv6.c.o
/usr/bin/cc -D_GNU_SOURCE -g -O2
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Source: blt
Version: 2.5.3+dfsg-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
blt/experimental FTBFS, most likely due to GCC 9 bieng the default
compiler nowadays:
x86_64-linux-gnu-gcc -c -Wall -g -O2
Package: gnat-gps-common
Version: 19.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships a file owned by
libjs-prototype:
/usr/share/javascript/prototype/prototype.js
>From the attached log (scroll to the
Control: tags 936729 + patch
Control: tags 936729 + pending
Dear maintainer,
I've prepared an NMU for imgsizer (versioned as 2.10-0.1) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru imgsizer-2.7/control imgsizer-2.10/control
---
On Mon, Dec 23, 2019 at 03:06:37PM -0500, Chen-Tse Tsai wrote:
> I have a quick question. Previously the python modules are installed to
> /usr/share/pyshared/. Should I use /usr/lib/python3/dist-packages instead
> if I change it to python3? I see this in the policy and this is also what
>
Processing control commands:
> tags 936729 + patch
Bug #936729 [src:imgsizer] imgsizer: Python2 removal in sid/bullseye
Added tag(s) patch.
> tags 936729 + pending
Bug #936729 [src:imgsizer] imgsizer: Python2 removal in sid/bullseye
Added tag(s) pending.
--
936729:
Processing commands for cont...@bugs.debian.org:
> fixed 943923 4.4.0-4
Bug #943923 {Done: Sandro Tosi } [src:python-apptools]
python-apptools: please stop build-depending on python-pandas
Marked as fixed in versions python-apptools/4.4.0-4.
> thanks
Stopping processing here.
Please contact me
Package: python3-lmfit
Version: 1.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
python3-lmfit ships files with generic names at the generic location
/usr/lib/python3/dist-packages/examples/ causing file clashes (e.g. on
README.txt) with other packages doing the
> python-clang - transitional package to python3-clang
> python-lldb - transitional package to python3-lldb
i dont think that's how you're supposed to use python- packages -
what's the reason for keeping them around as transitionals? people
either gets them as a dependency or will need to
Package: python3-geopandas
Version: 0.6.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
python3-geopandas ships files with generic names at the generic location
/usr/lib/python3/dist-packages/examples/ causing file clashes (e.g. on
README.txt) with other packages
Processing commands for cont...@bugs.debian.org:
> reassign 943923 src:python-apptools 4.4.0-3
Bug #943923 {Done: Sandro Tosi } [python-apptools]
python-apptools: please stop build-depending on python-pandas
Bug reassigned from package 'python-apptools' to 'src:python-apptools'.
No longer marked
Control: reassign -1 src:python-apptools 4.4.0-3
Package: python3-iniparse
Version: 0.4-2.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite
Control: found -1 src:python-apptools/4.4.0-3
Control: fixed -1 src:python-apptools/4.4.0-4
Attempting to get this package to migrate, which I think it failing
because the python-apptools binary package is now gone.
Your message dated Mon, 23 Dec 2019 20:39:42 +
with message-id
and subject line Bug#944043: fixed in q2-types 2019.10.0-1
has caused the Debian Bug report #944043,
regarding q2-types: autopkgtest fail with pandas 0.25
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> fixed 944017 0.1.3-1
Bug #944017 [src:libsoxr] libsoxr: autopkgtest regression: segmentation fault
Marked as fixed in versions libsoxr/0.1.3-1.
> reassign -1 src:libsoxr
Bug #947211 [libsoxr0] Regression in libsoxr0 0.1.3-2 makes ffmpeg segfault
Bug reassigned from
Your message dated Mon, 23 Dec 2019 20:16:04 +
with message-id
and subject line Bug#944486: fixed in trilinos 12.14.1-2~exp1
has caused the Debian Bug report #944486,
regarding libtrilinos-belos-dev: missing Breaks+Replaces: libtrilinos-muelu-dev
(<< 12.14)
to be marked as done.
This means
Your message dated Mon, 23 Dec 2019 20:16:04 +
with message-id
and subject line Bug#944688: fixed in trilinos 12.14.1-2~exp1
has caused the Debian Bug report #944688,
regarding trilinos: intrepid2 package is not shipped
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 23 Dec 2019 20:16:14 +
with message-id
and subject line Bug#946984: fixed in yade 2019.12~git~0~e74819ea-6
has caused the Debian Bug report #946984,
regarding yade: Ships python3.8 scripts, without any python3 or python3.8 deps
to be marked as done.
This means that
Your message dated Mon, 23 Dec 2019 20:15:39 +
with message-id
and subject line Bug#938559: fixed in squaremap 1:1.0.5-1
has caused the Debian Bug report #938559,
regarding squaremap: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 23 Dec 2019 20:14:39 +
with message-id
and subject line Bug#945660: fixed in llvm-defaults 0.49~exp2
has caused the Debian Bug report #945660,
regarding llvm-defaults: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 23 Dec 2019 20:15:16 +
with message-id
and subject line Bug#938224: fixed in python-traitsui 6.1.3-1
has caused the Debian Bug report #938224,
regarding python-traitsui: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 23 Dec 2019 20:13:28 +
with message-id
and subject line Bug#943961: fixed in ceph 14.2.4-1
has caused the Debian Bug report #943961,
regarding ceph: autopkgtest needs update for new version of python3.7:
deprecation warning
to be marked as done.
This means that you
Your message dated Mon, 23 Dec 2019 20:13:49 +
with message-id
and subject line Bug#943014: fixed in derpconf 0.8.2-3
has caused the Debian Bug report #943014,
regarding derpconf: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 23 Dec 2019 20:15:15 +
with message-id
and subject line Bug#938058: fixed in python-pydot-ng 1.0.0-4
has caused the Debian Bug report #938058,
regarding python-pydot-ng: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 23 Dec 2019 20:13:28 +
with message-id
and subject line Bug#936282: fixed in ceph 14.2.4-1
has caused the Debian Bug report #936282,
regarding ceph: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 23 Dec 2019 20:13:48 +
with message-id
and subject line Bug#945633: fixed in debian-multimedia 0.7+nmu1
has caused the Debian Bug report #945633,
regarding debian-multimedia: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Mon, 23 Dec 2019 20:13:45 +
with message-id
and subject line Bug#934251: fixed in coinor-dylp 1.10.4-1
has caused the Debian Bug report #934251,
regarding coinor-dylp: unbuildable in testing due to B-D on texlive-omega
to be marked as done.
This means that you claim that
Your message dated Mon, 23 Dec 2019 20:13:28 +
with message-id
and subject line Bug#936015: fixed in ceph 14.2.4-1
has caused the Debian Bug report #936015,
regarding ceph: CVE-2019-10222
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
I have a quick question. Previously the python modules are installed to
/usr/share/pyshared/. Should I use /usr/lib/python3/dist-packages instead
if I change it to python3? I see this in the policy and this is also what
liblinear uses. Just want to double check.
Thanks,
Chen-Tse
On Mon, Dec 23,
Hi Markus,
Yes Nils was doing a nmu for me. Unless they are very keen I'll handle
the backports. As you said the confusion is on the sponsorship. We were
using a
Mentors as a way of getting the package from him to me in the standard way.
- Craig
On Tue, 24 Dec. 2019, 4:27 am Markus Koschany,
Your message dated Mon, 23 Dec 2019 19:00:11 +
with message-id
and subject line Bug#937259: fixed in pcapy 0.11.4-1
has caused the Debian Bug report #937259,
regarding pcapy: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> # please stop raising the severity
> severity 937808 important
Bug #937808 [src:python-hglib] python-hglib: Python2 removal in sid/bullseye
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.
Please contact me
On Sun, Dec 22, 2019 at 06:57:24PM -0500, Sandro Tosi wrote:
> Python 2 is end-of-life, and there are no more rdeps for python-yapps2, but
> python3-yapps2 seems broken beyond repair: #911753, #911752.
>
> I believe this is a good enough reason to have this package removed from
> debian.
> if i
Your message dated Mon, 23 Dec 2019 18:37:04 +
with message-id
and subject line Bug#946732: fixed in python-django-braces 1.13.0-2
has caused the Debian Bug report #946732,
regarding python-django-braces: autopkgtest failure: No module named
'django_braces'
to be marked as done.
This means
Your message dated Mon, 23 Dec 2019 18:06:02 +
with message-id
and subject line Bug#938515: fixed in sortedcontainers 2.1.0-2
has caused the Debian Bug report #938515,
regarding sortedcontainers: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> forwarded 940199 https://github.com/mate-desktop/pluma/issues/305
Bug #940199 [src:pluma] pluma: Python2 removal in sid/bullseye
Bug #945690 [src:pluma] pluma: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to
Control: fixed -1 0.4.1-2
I can reproduce it in wheezy, but not in jessie or later releases.
Andreas
Processing control commands:
> fixed -1 0.4.1-2
Bug #734557 {Done: Sandro Tosi } [python-augeas]
python-augeas: doesn't depend on libpython2.7
Marked as fixed in versions python-augeas/0.4.1-2.
--
734557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734557
Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:
> reassign 946926 ftp.debian.org
Bug #946926 [src:pysparse] pysparse: should this package be removed?
Bug reassigned from package 'src:pysparse' to 'ftp.debian.org'.
No longer marked as found in versions pysparse/1.1.1-2.
Ignoring request to alter
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Hello Niels,
Am 23.12.19 um 15:04 schrieb DebBug:
> Anyone to chime in? Craig? Markus?
There is a bit of confusion here, so I try to explain the situation and
how we should proceed. Thank you for filing bug report #947212 to track
the security issues in Wordpress. This will help to answer those
Processing control commands:
> severity -1 serious
Bug #936966 [src:londonlaw] londonlaw: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
--
936966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> forcemerge 947212 946905
Bug #947212 [wordpress] wordpress: 5.3.2 new upstream bug-fixing release
available.
Unable to merge bugs because:
package of #946905 is 'src:wordpress' not 'wordpress'
Failed to forcibly merge 947212: Did not alter
Processing commands for cont...@bugs.debian.org:
> severity 947212 grave
Bug #947212 [wordpress] wordpress: 5.3.2 new upstream bug-fixing release
available.
Severity set to 'grave' from 'critical'
> tags 947212 security upstream
Bug #947212 [wordpress] wordpress: 5.3.2 new upstream bug-fixing
1 - 100 of 143 matches
Mail list logo
