Processed: critical bluestore data corruption

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 947457 ! Bug #947457 [ceph-osd] critical bluestore data corruption Owner recorded as Milan Kupcevic . > tags 947457 + pending Bug #947457 [ceph-osd] critical bluestore data corruption Added tag(s) pending. > thanks Stopping processing here.

Bug#938243: marked as done (python-uritools: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 Dec 2019 07:04:47 + with message-id and subject line Bug#938243: fixed in python-uritools 3.0.0-1 has caused the Debian Bug report #938243, regarding python-uritools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#947457: critical bluestore data corruption

2019-12-26 Thread Milan Kupcevic
Package: ceph-osd Version: 14.2.4-4 Severity: grave Tags: upstream fixed-upstream A critical bluestore data corruption bug[0][1] affecting OSDs configured with separate db and/or wal devices has been introduced in 14.2.3 and is affecting both 14.2.3 and 14.2.4 upstream releases[2]. This bug has

Bug#936110: marked as done (aff4: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 Dec 2019 06:37:46 + with message-id and subject line Bug#947417: Removed package(s) from unstable has caused the Debian Bug report #936110, regarding aff4: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#938525: marked as done (spectacle: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 Dec 2019 06:34:01 + with message-id and subject line Bug#947353: Removed package(s) from unstable has caused the Debian Bug report #938525, regarding spectacle: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938277: marked as done (python-xmlbuilder: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 Dec 2019 06:35:10 + with message-id and subject line Bug#947359: Removed package(s) from unstable has caused the Debian Bug report #938277, regarding python-xmlbuilder: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#935212: marked as done (python-apns-client: Please port to Python 3 and/or drop Python 2 package)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 Dec 2019 06:34:27 + with message-id and subject line Bug#947358: Removed package(s) from unstable has caused the Debian Bug report #935212, regarding python-apns-client: Please port to Python 3 and/or drop Python 2 package to be marked as done. This means that you

Bug#945681: marked as done (gvb: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 Dec 2019 05:19:14 + with message-id and subject line Bug#945681: fixed in gvb 1.4-1.1 has caused the Debian Bug report #945681, regarding gvb: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: tagging 936251

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 936251 + upstream Bug #936251 [src:bup] bup: Python2 removal in sid/bullseye Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936251:

Bug#945681: gvb: diff for NMU version 1.4-1.1

2019-12-26 Thread Adrian Bunk
On Thu, Dec 26, 2019 at 04:18:36PM +0100, Pietro Battiston wrote: > Dear Adrian, Dear Pietro, > thank you, I really appreciate. I was planning to fix that packaging > mistake, but as you might have noticed, I have really slow reactions > lately no worries, everyone has sometimes more urgent

Bug#945605: python-neovim: diff for NMU version 0.3.0-1.1

2019-12-26 Thread James McCoy
On Mon, Dec 23, 2019 at 12:36:25PM +0200, Adrian Bunk wrote: > I've prepared an NMU for python-neovim (versioned as 0.3.0-1.1) and > uploaded it to DELAYED/15. Please feel free to tell me if I should > cancel it. I've uploaded the new upstream version (0.4.0) which contains these fixes. It's

Bug#947148: libltdl7: lt_dlopen() returns handle but lt_dlerror() returns non-NULL with OpenMPI4

2019-12-26 Thread Andreas Beckmann
Followup-For: Bug #947148 Control: reassign -1 libltdl7 2.4.6-11 Control: retitle -1 libltdl7: lt_dlopen() returns handle but lt_dlerror() returns non-NULL with OpenMPI4 Hi, the bug does not manifest with plain dlopen() (see test_dlopen.c), so this seems to be rather a ltdl problem: If

Processed: Re: libltdl7: lt_dlopen() returns handle but lt_dlerror() returns non-NULL with OpenMPI4

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libltdl7 2.4.6-11 Bug #947148 [src:openmpi] openmpi: causes lt_dlopen() to fail with 'can't close resident module' Bug reassigned from package 'src:openmpi' to 'libltdl7'. No longer marked as found in versions openmpi/4.0.2-4. Ignoring request to alter

Bug#947448: pyfeed: missing Build-Depends: dh-python

2019-12-26 Thread Andreas Beckmann
Source: pyfeed Version: 1.0~prerelease-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, pyfeed/experimental FTBFS with fakeroot debian/rules clean dh clean --with=python2,python3 dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm

Bug#947446: libreoffice: ure split lacks proper versioned Breaks+Replaces

2019-12-26 Thread Andreas Beckmann
Source: libreoffice Version: 1:6.4.0~rc1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi Rene, the ure package was split recently but this lacks proper versioned Breaks+Replaces in the new packages. This allows for unwanted partial upgrades mixing a pre-split ure

Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

2019-12-26 Thread Nis Martensen
On 26.12.2019 17.11, Holger Levsen wrote: > many thanks, merged and deployed, now this is left: > File > "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py", > line 58, in readline > empty = not self._refill() > File >

Bug#937627: marked as done (python-cachetools: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 22:19:55 + with message-id and subject line Bug#937627: fixed in python-cachetools 3.1.1-3 has caused the Debian Bug report #937627, regarding python-cachetools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#947444: flatzinc: ships a copy of minizinc: /usr/share/minizinc/gecode/*

2019-12-26 Thread Andreas Beckmann
Package: flatzinc Version: 6.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to

Bug#947443: nvidia-texture-tools: FTBFS: undefined reference to symbol '_ZN2nv3Fit37computePrincipalComponent_EigenSolverEiPKNS_7Vector4E'

2019-12-26 Thread Andreas Beckmann
Source: nvidia-texture-tools Version: 2.1.0-git20160229+dfsg-2~exp1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, nvidia-texture-tools/experimental FTBFS in a current sid/experimental environment:

Processed: limit source to esys-particle, tagging 936489

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source esys-particle Limiting to bugs with field 'source' containing at least one of 'esys-particle' Limit currently set to 'source':'esys-particle' > tags 936489 + pending Bug #936489 [src:esys-particle] esys-particle: Python2 removal in

Bug#947441: libignition-cmake2-dev: file conflicts with libignition-cmake-dev: /usr/share/ignition/ignition-cmake0/doxygen/*

2019-12-26 Thread Andreas Beckmann
Package: libignition-cmake2-dev Version: 2.1.1+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation.

Processed: py2removal RC severity updates - 2019-12-26 21:36:57.419682+00:00

2019-12-26 Thread Debian Bug Tracking System
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

Bug#947433: waitress: CVE-2019-16789

2019-12-26 Thread Salvatore Bonaccorso
Source: waitress Version: 1.3.1-4 Severity: grave Tags: security upstream Hi, The following vulnerability was published for waitress, filling a distinct bug for that as the already filled #947306 for two other CVEs as this one is only fixed in 1.4.1 upstream. CVE-2019-16789[0]: | In Waitress

Processed: tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694 CVE-2019-15695

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.9.0+dfsg-3 Bug #947428 [src:tigervnc] tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694 CVE-2019-15695 Marked as found in versions tigervnc/1.9.0+dfsg-3. -- 947428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947428 Debian Bug

Bug#947428: tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694 CVE-2019-15695

2019-12-26 Thread Salvatore Bonaccorso
Source: tigervnc Version: 1.9.0+dfsg-4 Severity: grave Tags: security upstream Control: found -1 1.9.0+dfsg-3 Hi, The following vulnerabilities were published for tigervnc. CVE-2019-15691[0]: | TigerVNC version prior to 1.10.1 is vulnerable to stack use-after- | return, which occurs due to

Processed: bug 947425 is forwarded to https://github.com/ar-/incron/issues/36

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 947425 https://github.com/ar-/incron/issues/36 Bug #947425 [incron] incron crashes in IncronTabEntry::GetSafePath due to use-after-free bug Set Bug forwarded-to-address to 'https://github.com/ar-/incron/issues/36'. > thanks Stopping

Bug#947426: python-pysam ftbfs with htslib 1.10.2

2019-12-26 Thread Paul Gevers
Source: python-pysam Version: 0.15.2+ds-2 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package is part of the htslib 1.10.2 transition. I tried to binNMU your package but it fails to build from source. Please have a look. Paul

Bug#947425: incron crashes in IncronTabEntry::GetSafePath due to use-after-free bug

2019-12-26 Thread Willi Mann
Package: incron Version: 0.5.12-1 Severity: grave Tags: security patch upstream Hi, incron crashes for me frequently. As incron runs as root, but is controllable by users, this bug might be security-relevant, so I'm reporting it a severity grave and tagging it security. Please downgrade if you

Bug#947424: qtltools 1.2+dfsg-1 ftbfs on mipsel

2019-12-26 Thread Paul Gevers
Source: qtltools Version: 1.2+dfsg-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your last upload failed to build on mipsel. Your package is part of the htslib 1.10.2 transition, but I can't binNMU it on mipsel. Please have a look. Paul

Processed: your mail

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 947328 + unreproducible Bug #947328 [src:xca] FTBFS: dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or directory Added tag(s) unreproducible. > End of message, stopping processing here. Please contact me if you

Bug#947328: FTBFS Not Reproducible in multiple build test envs (sbuild, pbuilder, etc.)

2019-12-26 Thread Thomas Ward
I ran this exact package through a rebuild in an sbuild environment just now, and cannot reproduce your FTBFS.  Automated build(s) failed to reproduce this in a pbuilder environment as well. Did you do anything to the package to make it trigger this FTBFS?  What Arch and Distro did you build

Bug#947423: kallisto ftbfs with htslib 1.10.2

2019-12-26 Thread Paul Gevers
Source: kallisto Version: 0.46.1+dfsg-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package is part of the htslib 1.10.2 transition. I tried to binNMU your package but it fails to build from source. Please have a look. Paul

Bug#947421: delly ftbfs with htslib 1.10.2

2019-12-26 Thread Paul Gevers
Source: delly Version: 0.8.1-2 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package is part of the htslib 1.10.2 transition. I tried to binNMU your package but it fails to build from source. Please have a look. Paul

Bug#936110: aff4: Python2 removal in sid/bullseye

2019-12-26 Thread Scott Kitterman
On Fri, 30 Aug 2019 07:09:56 + Matthias Klose wrote: > Package: src:aff4 > Version: 0.24.post1-4 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the

Processed: [bts-link] source package src:weevely

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:weevely > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: py2removal RC severity updates - 2019-12-26 17:37:05.950355+00:00

2019-12-26 Thread Debian Bug Tracking System
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

Processed: [bts-link] source package src:goldeneye

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:goldeneye > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#945683: marked as done (peony-extensions: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 16:50:16 + with message-id and subject line Bug#945683: fixed in peony-extensions 1.1.4-1 has caused the Debian Bug report #945683, regarding peony-extensions: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#937730: Bug#934264: Please update (4.6.2?) and provide/switch to python3

2019-12-26 Thread Scott Talbert
On Tue, Dec 24, 2019 at 10:07:02AM +0100, Andreas Tille wrote: > > python-envisage has not yet been converted to Python3 and seems to be > > required: > > $ mayavi2 > > Traceback (most recent call last): > > File "/usr/bin/mayavi2", line 464, in > > from mayavi.plugins.app import Mayavi,

Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

2019-12-26 Thread Holger Levsen
On Thu, Dec 26, 2019 at 03:59:54PM +0100, Nis Martensen wrote: > > TypeError: mynext() takes 1 positional argument but 2 were given > > again, help very welcome! > A new merge request has the next set of fixups: > https://salsa.debian.org/debian/piuparts/merge_requests/17 many thanks, merged and

Bug#938618: marked as done (syslog-ng: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 15:36:12 + with message-id and subject line Bug#938618: fixed in syslog-ng 3.25.1-1 has caused the Debian Bug report #938618, regarding syslog-ng: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#947043: marked as done (cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 15:34:26 + with message-id and subject line Bug#947043: fixed in cyrus-sasl2 2.1.27+dfsg-2 has caused the Debian Bug report #947043, regarding cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function to be marked as done. This means that you

Bug#947043: cyrus-sasl2: CVE-2019-19906: Off by one in _sasl_add_string function

2019-12-26 Thread Roberto C . Sánchez
On Fri, Dec 20, 2019 at 10:24:20PM +0100, Salvatore Bonaccorso wrote: > > And released as DSA 4591-1. Note: The patch was not upstream commited > at point of writing this. And I see Mike did as well release for LTS. > I saw that Mike did updates for jessie (LTS) and wheezy (ELTS). > > >

Bug#945681: gvb: diff for NMU version 1.4-1.1

2019-12-26 Thread Pietro Battiston
Dear Adrian, thank you, I really appreciate. I was planning to fix that packaging mistake, but as you might have noticed, I have really slow reactions lately - and then, I still need to go through a sponsor. So if you prefer, feel free to re-upload the package without delay. Pietro Il giorno

Bug#937269: peframe: Python2 removal in sid/bullseye

2019-12-26 Thread Sascha Steinbiss
Just an update: Python 3 compatibility is indeed introduced in the latest upstream version, however, that version also adds some new dependencies that would need to be packaged and pass NEW. For example, python-virustotal-api, which has been in NEW for quite some time. I have also looked at

Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

2019-12-26 Thread Nis Martensen
> TypeError: mynext() takes 1 positional argument but 2 were given > > again, help very welcome! A new merge request has the next set of fixups: https://salsa.debian.org/debian/piuparts/merge_requests/17

Bug#937082: marked as done (mopidy-tunein: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 14:49:32 + with message-id and subject line Bug#937082: fixed in mopidy-tunein 1.0.0-1 has caused the Debian Bug report #937082, regarding mopidy-tunein: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#937081: marked as done (mopidy-soundcloud: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 14:39:54 + with message-id and subject line Bug#937081: fixed in mopidy-soundcloud 3.0.0-1 has caused the Debian Bug report #937081, regarding mopidy-soundcloud: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#936932: libvigraimpex: Python2 removal in sid/bullseye

2019-12-26 Thread Andreas Metzler
Control: block -1 by 947365 On 2019-12-23 Andreas Metzler wrote: [...] > I will do a QA upload. I have opened a request for a transition slot. cu Andreas signature.asc Description: PGP signature

Processed: Re: Bug#936932: libvigraimpex: Python2 removal in sid/bullseye

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 947365 Bug #936932 {Done: Andreas Metzler } [src:libvigraimpex] libvigraimpex: Python2 removal in sid/bullseye 936932 was blocked by: 945659 936932 was blocking: 936227 937156 937695 937960 938114 Added blocking bug(s) of 936932: 947365 -- 936932:

Bug#939401: nvidia-driver: Xorg crashing in an endless loop after upgrade to version 430

2019-12-26 Thread Luca Boccassi
On Thu, 21 Nov 2019 at 15:30, Andreas Beckmann wrote: > > Hi Luca, > > On Sun, 08 Sep 2019 11:50:28 +0100 Luca Boccassi wrote: > > Ok scratch that, I can reproduce - it's because of the non-glvnd > > libraries. With the glvnd one there's no issue, and that's why 435 > > works - non-glvnd was

Bug#946563: there is no need for a versioned libxcrypt1-dev package

2019-12-26 Thread Andreas Metzler
On 2019-12-11 Marco d'Itri wrote: > On Dec 11, Matthias Klose wrote: > > there is really no need for a versioned libxcrypt1-dev package. > > Please rename that properly to libxcrypt-dev. > Can you be more specific in why this would not be allowed? > Currently I am not building libxcrypt2 and

Processed: Merge duplicates

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 912495 src:pydxcluster Bug #912495 [pydxcluster] pydxcluster: Please migrate to python3-pygame Bug reassigned from package 'pydxcluster' to 'src:pydxcluster'. Ignoring request to alter found versions of bug #912495 to the same values

Bug#945730: pyconfigure: Python2 removal in sid/bullseye

2019-12-26 Thread Adrian Bunk
Control: retitle -1 pyconfigure: Please drop alternative recommends of python-setuptools Control: unblock 938168 by -1 Control: severity -1 minor On Wed, Nov 27, 2019 at 11:58:52PM +, Sandro Tosi wrote: > Source: pyconfigure > Version: 0.2.3-2 > Severity: normal > Tags: sid bullseye > User:

Processed: Re: Bug#945730: pyconfigure: Python2 removal in sid/bullseye

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 pyconfigure: Please drop alternative recommends of > python-setuptools Bug #945730 [src:pyconfigure] pyconfigure: Python2 removal in sid/bullseye Changed Bug title to 'pyconfigure: Please drop alternative recommends of python-setuptools' from

Processed: tagging 945728

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 945728 + fixed-upstream Bug #945728 [src:zypper] zypper: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 945728:

Bug#933348: marked as done (mopidy-scrobbler: depends on removed package)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 13:35:19 + with message-id and subject line Bug#933348: fixed in mopidy-scrobbler 2.0.0-1 has caused the Debian Bug report #933348, regarding mopidy-scrobbler: depends on removed package to be marked as done. This means that you claim that the problem has

Bug#937079: marked as done (mopidy-scrobbler: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 13:35:20 + with message-id and subject line Bug#937079: fixed in mopidy-scrobbler 2.0.0-1 has caused the Debian Bug report #937079, regarding mopidy-scrobbler: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Processed: Merge duplicates

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 942777 src:nitroshare Bug #942777 [nitroshare-nautilus] nitroshare-nautilus: Please port to python3-nautlius Bug reassigned from package 'nitroshare-nautilus' to 'src:nitroshare'. No longer marked as found in versions

Processed: severity of 917840 is serious

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 917840 serious Bug #917840 [nitroshare-nautilus] nitroshare-nautilus expansion not working because of unmet python2 dependency Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: gvb: diff for NMU version 1.4-1.1

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > tags 945681 + patch Bug #945681 [src:gvb] gvb: Python2 removal in sid/bullseye Added tag(s) patch. > tags 945681 + pending Bug #945681 [src:gvb] gvb: Python2 removal in sid/bullseye Added tag(s) pending. -- 945681:

Bug#945681: gvb: diff for NMU version 1.4-1.1

2019-12-26 Thread Adrian Bunk
Control: tags 945681 + patch Control: tags 945681 + pending Dear maintainer, I've prepared an NMU for gvb (versioned as 1.4-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru gvb-1.4/debian/changelog gvb-1.4/debian/changelog ---

Processed: tagging 945673

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 945673 + fixed-upstream Bug #945673 [src:fvwm-crystal] fvwm-crystal: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 945673:

Processed: Re: Bug#945652: i3lock-fancy: Python2 removal in sid/bullseye

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 i3lock-fancy should stop listing python-tomahawk as alternative > dependency Bug #945652 [src:i3lock-fancy] i3lock-fancy: Python2 removal in sid/bullseye Changed Bug title to 'i3lock-fancy should stop listing python-tomahawk as alternative dependency'

Processed: tagging 945663

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 945663 + fixed-upstream Bug #945663 [src:drbdlinks] drbdlinks: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 945663:

Bug#945652: i3lock-fancy: Python2 removal in sid/bullseye

2019-12-26 Thread Adrian Bunk
Control: retitle -1 i3lock-fancy should stop listing python-tomahawk as alternative dependency Control: unblock 938676 by -1 Control: severity -1 minor On Wed, Nov 27, 2019 at 11:58:49PM +, Sandro Tosi wrote: > Source: i3lock-fancy > Version: 0.0~git20160228.0.0fcb933-2 > Severity: normal >

Bug#946217: marked as done (CVE-2019-19333 & CVE-2019-19334 in libyang)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 12:34:39 + with message-id and subject line Bug#946217: fixed in libyang 0.16.105-2 has caused the Debian Bug report #946217, regarding CVE-2019-19333 & CVE-2019-19334 in libyang to be marked as done. This means that you claim that the problem has been

Bug#925764: marked as done (libyang: ftbfs with GCC-9)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 12:34:39 + with message-id and subject line Bug#925764: fixed in libyang 0.16.105-2 has caused the Debian Bug report #925764, regarding libyang: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: block 945637 with 945840

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 945637 with 945840 Bug #945637 {Done: Alastair McKinstry } [src:ecflow] ecflow: Python2 removal in sid/bullseye 945637 was not blocked by any bugs. 945637 was not blocking any bugs. Added blocking bug(s) of 945637: 945840 and 946036 >

Processed: hkl FTBFS on arm64: sirius segfaults

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > block 939950 by -1 Bug #939950 {Done: Picca Frédéric-Emmanuel } [src:hkl] hkl: fails to build with gtk-doc 1.32 939950 was not blocked by any bugs. 939950 was blocking: 939500 Added blocking bug(s) of 939950: 947400 -- 939950:

Bug#947400: hkl FTBFS on arm64: sirius segfaults

2019-12-26 Thread Adrian Bunk
Source: hkl Version: 5.0.0.2569-1 Severity: serious Tags: ftbfs Control: block 939950 by -1 https://buildd.debian.org/status/fetch.php?pkg=hkl=arm64=5.0.0.2569-1=1576087153=0 Making all in figures make[4]: Entering directory '/<>/Documentation/figures' gcc -DHAVE_CONFIG_H -I. -I../.. -Wextra

Bug#937076: marked as done (mopidy-mpris: Python2 removal in sid/bullseye)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 11:06:28 + with message-id and subject line Bug#937076: fixed in mopidy-mpris 3.0.1-1 has caused the Debian Bug report #937076, regarding mopidy-mpris: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Processed: re: pysph: Python2 removal in sid/bullseye

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 937543 serious Bug #937543 {Done: Antonio Valentino } [src:pysph] pysph: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 937543:

Bug#947297: Bug#947397: transition: cppunit

2019-12-26 Thread Rene Engelhard
On Thu, Dec 26, 2019 at 10:59:32AM +0100, Rene Engelhard wrote: > Most packages just build-depend on it. A rebuild using ratt just works, > except some totally unrelated failures: The builds are still running but as said look good, siconos failed in its tests but with something which looks more

Processed: limit source to python-demgengeo, tagging 937697

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source python-demgengeo Limiting to bugs with field 'source' containing at least one of 'python-demgengeo' Limit currently set to 'source':'python-demgengeo' > tags 937697 + pending Bug #937697 [src:python-demgengeo] python-demgengeo:

Processed: re: actor-framework: Python2 removal in sid/bullseye

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > Severity 942907 serious Bug #942907 [src:actor-framework] actor-framework: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 942907:

Bug#947387: marked as done (python3-pcapy: missing Breaks+Replaces: python-pcapy)

2019-12-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Dec 2019 09:19:42 + with message-id and subject line Bug#947387: fixed in pcapy 0.11.4-2 has caused the Debian Bug report #947387, regarding python3-pcapy: missing Breaks+Replaces: python-pcapy to be marked as done. This means that you claim that the problem has

Bug#939260: websploit: Python2 removal in sid/bullseye

2019-12-26 Thread Raphael Hertzog
On Mon, 16 Dec 2019 14:28:33 +0100 Raphael Hertzog wrote: > Great. Looking forward to it. Do you have any idea how much time you need > to complete this Python 3 port of websploit? On the 21th, I got a private reply saying that he might need 20 days to complete the Python 3 port. Cheers, --

Processed: tagging 938660

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 938660 + fixed-upstream Bug #938660 [src:tftpy] tftpy: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 938660:

Processed: Tagging 944705 as fixed upstream

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 944705 + fixed-upstream Bug #944705 [python3-mako] alembic: failing tests with python3.8 Added tag(s) fixed-upstream. > forwarded 944705 https://github.com/sqlalchemy/mako/issues/287 Bug #944705 [python3-mako] alembic: failing tests with

Processed: bug 938649 is forwarded to https://github.com/brunobraga/termsaver/issues/34

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 938649 https://github.com/brunobraga/termsaver/issues/34 Bug #938649 [src:termsaver] termsaver: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/brunobraga/termsaver/issues/34'. > thanks Stopping

Bug#947387: [Python-modules-team] Bug#947387: python3-pcapy: missing Breaks+Replaces: python-pcapy

2019-12-26 Thread Raphael Hertzog
On Wed, 25 Dec 2019, Emmanuel Arias wrote: > Raphaël, please could you review my patch? Reviewed and uploaded. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS

Bug#945723: Upstream progress on python 3 port

2019-12-26 Thread Raphael Hertzog
Hello, upstream seems to be close to release a Python 3 version, current WIP is in https://github.com/epinna/weevely3/tree/Debian-master according to https://github.com/epinna/weevely3/pull/119#issuecomment-568770367 Sending this mail to reset the auto-rm clock, hoping that Samuel will upload a

Processed: tagging 938544

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 938544 + fixed-upstream Bug #938544 [src:sphinx-patchqueue] sphinx-patchqueue: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 938544:

Processed: Blocking issue for PySPH

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 945326 by 944705 Bug #945326 [src:pysph] pysph ftbfs in unstable 945326 was not blocked by any bugs. 945326 was not blocking any bugs. Added blocking bug(s) of 945326: 944705 > thanks Stopping processing here. Please contact me if you need

Bug#944705: Wrong patch for mako?

2019-12-26 Thread Antonio Valentino
Dear Thomas, dear Steve, On Wed, 20 Nov 2019 22:24:18 -0800 Steve Langasek wrote: > On Mon, Nov 18, 2019 at 09:07:14AM +0100, Thomas Goirand wrote: > > Hi Steve, > > > Thanks for this, however, the patch you've provided for this bug is for > > Alembic, not for Mako. Do you have a patch

Bug#938489: sinntp: diff for NMU version 1.6-0.1

2019-12-26 Thread Adrian Bunk
Control: tags 783971 + patch Control: tags 783971 + pending Control: tags 827146 + pending Control: tags 938489 + patch Control: tags 938489 + pending Dear maintainer, I've prepared an NMU for sinntp (versioned as 1.6-0.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should

Processed: sinntp: diff for NMU version 1.6-0.1

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > tags 783971 + patch Bug #783971 [sinntp] sinntp: please update Homepage field Ignoring request to alter tags of bug #783971 to the same tags previously set > tags 783971 + pending Bug #783971 [sinntp] sinntp: please update Homepage field Ignoring request to alter

Processed: sinntp: diff for NMU version 1.6-0.1

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > tags 783971 + patch Bug #783971 [sinntp] sinntp: please update Homepage field Ignoring request to alter tags of bug #783971 to the same tags previously set > tags 783971 + pending Bug #783971 [sinntp] sinntp: please update Homepage field Ignoring request to alter

Processed: sinntp: diff for NMU version 1.6-0.1

2019-12-26 Thread Debian Bug Tracking System
Processing control commands: > tags 783971 + patch Bug #783971 [sinntp] sinntp: please update Homepage field Added tag(s) patch. > tags 783971 + pending Bug #783971 [sinntp] sinntp: please update Homepage field Added tag(s) pending. > tags 827146 + pending Bug #827146 [src:sinntp] sinntp: please

Processed: Re: Bug#947367: lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0'

2019-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 947367 src:lebiniou Bug #947367 [src:lebiniou, src:lebiniou-data] lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0' Bug reassigned from package 'src:lebiniou, src:lebiniou-data'