Bug#958657: marked as done (python-ldap3: FTBFS: test error: PyAsn1UnicodeDecodeError import failed)

Your message dated Fri, 24 Apr 2020 05:48:27 + with message-id and subject line Bug#958657: fixed in python-ldap3 2.7-2 has caused the Debian Bug report #958657, regarding python-ldap3: FTBFS: test error: PyAsn1UnicodeDecodeError import failed to be marked as done. This means that you claim

Bug#958657: marked as pending in python-ldap3

Control: tag -1 pending Hello, Bug #958657 in python-ldap3 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:

Processed: Bug#958657 marked as pending in python-ldap3

Processing control commands: > tag -1 pending Bug #958657 [src:python-ldap3] python-ldap3: FTBFS: test error: PyAsn1UnicodeDecodeError import failed Added tag(s) pending. -- 958657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958657 Debian Bug Tracking System Contact

Bug#958646: ffmpegfs: FTBFS caused by passing custom target flags in CFLAGS

Your are right, this was the only change to Makefile.am since 1.10 but not a good idea :) Fixed that upstream and will create a new packet with patch. On 24.04.20 00:57, John Paul Adrian Glaubitz wrote: Package: ffmpegfs Version: 1.98-1 Severity: serious Tags: upstream Justification: ftbfs

Bug#943075: marked as done (impressive: Python2 removal in sid/bullseye)

Your message dated Fri, 24 Apr 2020 00:37:40 -0400 with message-id and subject line Re: impressive: Python2 removal in sid/bullseye has caused the Debian Bug report #943075, regarding impressive: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#955776: marked as done (src:pillow: fails to migrate to testing for too long)

Your message dated Fri, 24 Apr 2020 07:21:39 +0300 with message-id and subject line Pillow migrated to testing has caused the Debian Bug report #955776, regarding src:pillow: fails to migrate to testing for too long to be marked as done. This means that you claim that the problem has been dealt

Bug#954462: marked as done (src:m2crypto: Autopkgtest failure due to use of py3versions -i)

Your message dated Fri, 24 Apr 2020 04:03:42 + with message-id and subject line Bug#954462: fixed in m2crypto 0.35.2-1 has caused the Debian Bug report #954462, regarding src:m2crypto: Autopkgtest failure due to use of py3versions -i to be marked as done. This means that you claim that the

Bug#958496: marked as done (python3-m2crypto: broken by Python3.8 - python3.8 http.client module expects that m2crypto handles short read)

Your message dated Fri, 24 Apr 2020 04:03:42 + with message-id and subject line Bug#958496: fixed in m2crypto 0.35.2-1 has caused the Debian Bug report #958496, regarding python3-m2crypto: broken by Python3.8 - python3.8 http.client module expects that m2crypto handles short read to be

Bug#958657: python-ldap3: FTBFS: test error: PyAsn1UnicodeDecodeError import failed

Source: python-ldap3 Version: 2.7-1 Severity: grave X-Debbugs-CC: andre...@debian.org b...@debian.org Dear Debian python-ldap3 maintainer, The latest python-ldap3/2.7-1 currently FTBFS due to test errors: dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:217: cd

Processed: Bug#958496 marked as pending in m2crypto

Processing control commands: > tag -1 pending Bug #958496 [python3-m2crypto] python3-m2crypto: broken by Python3.8 - python3.8 http.client module expects that m2crypto handles short read Added tag(s) pending. -- 958496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958496 Debian Bug

Bug#958496: marked as pending in m2crypto

Control: tag -1 pending Hello, Bug #958496 in m2crypto 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:

Bug#953537: xfsdump fails to install in /usr merged system.

I've been there once upon a time, I just figured a ping was in order, especially given the severity of the bug and the severity of the human malware situation. Joseph On Thu, Apr 23, 2020, at 16:11, Nathan Scott wrote: > Hi folks, > > Apologies for the slow response - yes, I'm around but not

Bug#954581: marked as done (deepin-terminal: FTBFS: command_panel.vala:302.40-302.63: error: Argument 1: Cannot convert from `char[]' to `unowned uint8[]?')

Your message dated Fri, 24 Apr 2020 00:18:50 + with message-id and subject line Bug#954581: fixed in deepin-terminal 5.0.0+ds1-2 has caused the Debian Bug report #954581, regarding deepin-terminal: FTBFS: command_panel.vala:302.40-302.63: error: Argument 1: Cannot convert from `char[]' to

Bug#958566: Additional info

It is an old problem with version 6.30.163.46. See e.g. https://bugs.gentoo.org/541080

Bug#956337: marked as done (depends on python-pil which is being removed in bullseye (testing))

Your message dated Thu, 23 Apr 2020 23:18:33 + with message-id and subject line Bug#956337: fixed in impressive 0.13.0~beta1a-1 has caused the Debian Bug report #956337, regarding depends on python-pil which is being removed in bullseye (testing) to be marked as done. This means that you

Bug#953537: xfsdump fails to install in /usr merged system.

Hi folks, Apologies for the slow response - yes, I'm around but not with alot of time for packaging work unfortunately. I appreciate all the help! On Mon, Mar 16, 2020 at 11:06 PM Goffredo Baroncelli wrote: > > This bug was already addressed in the past by Marco d'Itri. Now it reappears. Yes,

Bug#958646: ffmpegfs: FTBFS caused by passing custom target flags in CFLAGS

Package: ffmpegfs Version: 1.98-1 Severity: serious Tags: upstream Justification: ftbfs User: debian-powe...@lists.debian.org Usertags: powerpc ppc64 ppc64el Hello! ffmpegfs fails to build from source on multiple architectures [1], including release architectures because it passes target flags

Bug#953875: runit - default installation wants to remove systemd

Control: tag -1 - moreinfo + |confirmed I can reproduce with autopkgtest [1]. It's still not clear to me why I can't reproduce in a chroot or Virtulabox. Unfortunately the workaround proposed by Adam Borowski in #10 doesn't solve the issue, at least not in autopkgtest ( I'm not able to test in

Processed (with 1 error): Re: runit - default installation wants to remove systemd

Processing control commands: > tag -1 - moreinfo + |confirmed I can reproduce with autopkgtest [1]. It's > still not clear to Unknown tag/s: |confirmed, I, can, reproduce, with, autopkgtest, [1]., It's, still, not, clear, to. Recognized are: patch wontfix moreinfo unreproducible help security

Bug#938305: marked as done (pyxdg: Python2 removal in sid/bullseye)

Your message dated Thu, 23 Apr 2020 21:49:17 + with message-id and subject line Bug#938305: fixed in pyxdg 0.26-3 has caused the Debian Bug report #938305, regarding pyxdg: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Processed: severity of 936153 is serious

Processing commands for cont...@bugs.debian.org: > # B-D no longer installable > severity 936153 serious Bug #936153 [src:aseba-plugin-blockly] aseba-plugin-blockly: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if

Bug#958533: marked as done (pyxdg: autopkgtest regression: still tests Python2 package)

Your message dated Thu, 23 Apr 2020 21:49:17 + with message-id and subject line Bug#958533: fixed in pyxdg 0.26-3 has caused the Debian Bug report #958533, regarding pyxdg: autopkgtest regression: still tests Python2 package to be marked as done. This means that you claim that the problem

Bug#958643: sysdig: crash the whole machine and disables login after reboot by just installing package

Package: sysdig Version: 0.13.0-2 Severity: critical Justification: breaks the whole system Dear Maintainer, I installed sysdig from the regular debian 9 packet repository on my normal machine (not a VM) and after a few seconds of usage the whole system freezes. I had to hard-reset the machine.

Bug#937297: marked as done (RM: PKG -- removal triggered by the Python2 removal)

Your message dated Thu, 23 Apr 2020 21:38:59 + with message-id and subject line Bug#937297: Removed package(s) from unstable has caused the Debian Bug report #937297, regarding RM: PKG -- removal triggered by the Python2 removal to be marked as done. This means that you claim that the

Bug#958533: [Python-modules-team] Bug#958533: pyxdg: autopkgtest regression: still tests Python2 package

On Thu, Apr 23, 2020 at 3:12 PM Emmanuel Arias wrote: > I've push to salsa the fix. I will need sponsorship Uploading now. Thanks for your work! -- Andrew Starr-Bochicchio Debian Developer Ubuntu Developer

Bug#958547: [Pkg-rust-maintainers] Bug#958547: closing 958547 ( rust-curl-sys autopkgtest failure, looks for crate in the wrong place. )

peter green: > On 23/04/2020 17:07, Ximin Luo wrote: >> close 958547 >> thanks >> >> See >> https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2020-January/009512.html >> >> Just be patient and wait a few days, the issue usually resolves itself. > > I have read that thread and I am

Processed: tagging 958313

Processing commands for cont...@bugs.debian.org: > tags 958313 - buster Bug #958313 [src:libnitrokey] libnitrokey: FTBFS: symbol changes Removed tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 958313:

Processed: py2removal bugs severity updates - 2020-04-23 20:35:13.266782+00:00

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#958578: wav2cdr: autopkgtest failure on arm64: Assertion `sizeof(UINT32) == 4' failed

Source: wav2cdr Version: 2.3.4-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), With a recent upload of wav2cdr you added an autopkgtest, great. However it fails on arm64. I copied some of the output at the

Bug#958075: marked as done (crispy-doom: file conflict with chocolate-doom)

Your message dated Thu, 23 Apr 2020 20:33:40 + with message-id and subject line Bug#958075: fixed in crispy-doom 5.8.0-2 has caused the Debian Bug report #958075, regarding crispy-doom: file conflict with chocolate-doom to be marked as done. This means that you claim that the problem has

Processed: tagging 958492, found 912485 in 3.3-2, tagging 912485, found 933928 in 1.0.5-3, tagging 955092 ...

Processing commands for cont...@bugs.debian.org: > tags 958492 + sid bullseye Bug #958492 [xfonts-terminus] xfonts-terminus: Provide gtk-compatible fonts Added tag(s) bullseye and sid. > found 912485 3.3-2 Bug #912485 [src:childsplay] childsplay: Please migrate to python3-pygame Marked as found

Bug#958577: python3-docker Depends on python3-distutils but doesn't declare it

Package: python3-docker Version: 4.1.0-1 Severity: serious Dear maintainer, As can be seen by the autopkgtest of toil [1], python3-docker needs distutils.spawn to be able to support "from docker.errors import ImageNotFound". I believe python3-docker therefor Depends on python3-distutils, but it

Bug#958574: toil: autopkgtest regression in a superficial test

Source: toil Version: 4.0.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of toil the autopkgtest of toil fails in testing when that autopkgtest is run with the binary packages of toil

Bug#958571: hypercorn build-depends on package that is not in testing.

Source: hypercorn Version: 0.9.4-1 Severity: serious hypercorn build-depends on python3-uvloop which is not available in testing due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950165 . Either uvloop needs to be fixed, hypercorn needs to be modified to not build-depend on uvloop or

Bug#958566: b43-fwcutter: Wifi Broadcom at BCM4311 very slow after installing new firmware-b43-installer_019-5_all.deb

Package: b43-fwcutter Version: 1:019-5 Severity: grave Justification: renders package unusable Dear Maintainer, After the recent upgrade to package firmware-b43-installer_019-5_all wifi connection was extremely slow causing e.g. timeouts at Firefox. This package contains firmware version

Processed: Re: python3-caffe-cuda: No longer installable, please upgrade

Processing control commands: > tag -1 sid Bug #958335 [python3-caffe-cuda] python3-caffe-cuda: No longer installable, please upgrade Added tag(s) sid. > close -1 1.0.0+git20180821.99bd997-4+rm Bug #958335 [python3-caffe-cuda] python3-caffe-cuda: No longer installable, please upgrade There is no

Bug#958335: python3-caffe-cuda: No longer installable, please upgrade

Control: tag -1 sid Control: close -1 1.0.0+git20180821.99bd997-4+rm On Mon, 20 Apr 2020 18:19:56 +0200 Celelibi wrote: > Package: python3-caffe-cuda > Version: 1.0.0+git20180821.99bd997-2+b1 > python3-caffe-cuda is uninstallable because of its dependencies. Both > direct and indirect. > > It

Bug#953144: origami install fails with "ERROR: WGET RETRIEVAL FAILED!"

Followup-For: Bug #953144 Downloading works again, but ... In a minimal pbuilder sid chroot: # apt-get install lsb-release [...] # origami install INSTALLING... PLEASE BE PATIENT ls: cannot access 'foldingathome/CPU*/': No such file or directory ls: cannot access

Bug#958533: [Python-modules-team] Bug#958533: pyxdg: autopkgtest regression: still tests Python2 package

Hi, I've push to salsa the fix. I will need sponsorship Thanks! Cheers, Arias Emmanuel @eamanu http://eamanu.com El jue., 23 de abr. de 2020 a la(s) 10:45, Paul Gevers (elb...@debian.org) escribió: > > Source: pyxdg > Version: 0.26-2 > X-Debbugs-CC: debian...@lists.debian.org > Severity:

Bug#958547: closing 958547 ( rust-curl-sys autopkgtest failure, looks for crate in the wrong place. )

On 23/04/2020 17:07, Ximin Luo wrote: close 958547 thanks See https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2020-January/009512.html Just be patient and wait a few days, the issue usually resolves itself. I have read that thread and I am aware of the issue that testing

Bug#956882: statsmodels: FTBFS on armel

Control: tags -1 patch The failed tests are expecting an 0/0 warning from numpy, which it produces on amd64 but not armel: amd64$ python3 Python 3.8.2 (default, Apr 1 2020, 15:52:55) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import numpy

Bug#955535: Bug #955535: httping: flaky autopkgtest: PING google.com:80

Hi Abhijith, On Fri, 10 Apr 2020 19:19:20 +0530 Abhijith PA wrote: > On 03/04/20 7:24 am, Aron Xu wrote: > > Hi, > > > > The two different results are caused by different CI workers - some of > > our workers at ci.d.n does not have reliable network to public > > services, in this case to

Processed: Re: statsmodels: FTBFS on armel

Processing control commands: > tags -1 patch Bug #956882 [src:statsmodels] statsmodels: FTBFS on armel Added tag(s) patch. -- 956882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#958536: marked as done (chipmunk: FTBFS during binary-indep build)

Your message dated Thu, 23 Apr 2020 16:33:31 + with message-id and subject line Bug#958536: fixed in chipmunk 7.0.3-2 has caused the Debian Bug report #958536, regarding chipmunk: FTBFS during binary-indep build to be marked as done. This means that you claim that the problem has been dealt

Processed: Bug#958536 marked as pending in chipmunk

Processing control commands: > tag -1 pending Bug #958536 [src:chipmunk] chipmunk: FTBFS during binary-indep build Added tag(s) pending. -- 958536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#958536: marked as pending in chipmunk

Control: tag -1 pending Hello, Bug #958536 in chipmunk 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:

Bug#958547: closing 958547

close 958547 thanks See https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2020-January/009512.html Just be patient and wait a few days, the issue usually resolves itself.

Processed: closing 958547

Processing commands for cont...@bugs.debian.org: > close 958547 Bug #958547 [rust-curl-sys] rust-curl-sys autopkgtest failure, looks for crate in the wrong place. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 958547:

Bug#958554: beautifulsoup4: autopkgtest failure.

Source: beautifulsoup4 Version: 4.9.0-1 Severity: serious The autopkgtest for beautifulsoup4 is failing in both plain unstable tests and testing migration tests, but not in plain testing tests. ERROR: test_dangling_combinator (bs4.tests.test_tree.TestSoupSelector)

Bug#954137: virtualbox: Cannot boot VM: kernel modules fails with VERR_VMM_SMAP_BUT_AC_CLEAR

control: fixed -1 6.1.4-dfsg-1 control: close -1 already fixed according to upstream ticket please reopen if this isn't the case! G. On Tue, 17 Mar 2020 11:54:17 +0100 Ralf Jung wrote: > Package: virtualbox > Version: 6.1.2-dfsg-1 > Severity: important > > Dear Maintainer, > > One of my

Processed: Re: virtualbox: Cannot boot VM: kernel modules fails with VERR_VMM_SMAP_BUT_AC_CLEAR

Processing control commands: > fixed -1 6.1.4-dfsg-1 Bug #954137 [virtualbox] virtualbox: Cannot boot VM: kernel modules fails with VERR_VMM_SMAP_BUT_AC_CLEAR Marked as fixed in versions virtualbox/6.1.4-dfsg-1. > close -1 Bug #954137 [virtualbox] virtualbox: Cannot boot VM: kernel modules fails

Bug#958547: rust-curl-sys autopkgtest failure, looks for crate in the wrong place.

Package: rust-curl-sys Version: 0.4.30-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-curl-sys/5114465/log.gz autopkgtest [15:59:42]: test librust-curl-sys+http2-dev: [--- crate directory not found:

Processed: tagging 958533

Processing commands for cont...@bugs.debian.org: > tags 958533 + pending Bug #958533 [src:pyxdg] pyxdg: autopkgtest regression: still tests Python2 package Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 958533:

Bug#952951: botan: Replace PKCS11 headers provided by OASIS

On Thu, Apr 23, 2020 at 4:24 PM Sean Whitton wrote: > On Thu 23 Apr 2020 at 01:09PM +03, Adrian Bunk wrote: > > So what is the way forward you suggest? > > Asking someone (who?) for advice? > > RC bug also against p11-kit? > > ...??? > > Well, didn't the bug submitter suggest an alternative

Bug#958538: python-cobra build-dependencies unsatisfiable on mipsel

Source: python-cobra Version: 0.14.2-2 Severity: serious (this issue affects both 0.14.2-2 from testing and 0.18.0-1 from unstable) python-cobra's build-dependencies are not satisfiable in testing/unstable on mipsel, it build-depends on python3-sbml5 and libsbml5 which are built by the

Bug#938909: marked as done (zope.interface: Python2 removal in sid/bullseye)

Your message dated Thu, 23 Apr 2020 14:34:04 + with message-id and subject line Bug#938909: fixed in zope.interface 4.7.1-2 has caused the Debian Bug report #938909, regarding zope.interface: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

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

Your message dated Thu, 23 Apr 2020 14:33:51 + with message-id and subject line Bug#937687: fixed in python-dateutil 2.8.1-4 has caused the Debian Bug report #937687, regarding python-dateutil: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#952951: botan: Replace PKCS11 headers provided by OASIS

Hello, On Thu 23 Apr 2020 at 01:09PM +03, Adrian Bunk wrote: > On Tue, Mar 24, 2020 at 09:30:55PM -0700, Sean Whitton wrote: >> On Tue 10 Mar 2020 at 06:32PM +01, László Böszörményi (GCS) wrote: >> >> > Its CONTRIBUTING.md [3] adds: "Subject to applicable licensing rules, >> > the repository

Bug#958536: chipmunk: FTBFS during binary-indep build

Source: chipmunk Version: 7.0.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, chipmunk/experimental FTBFS during an arch-indep build (e.g. dpkg-buildpackage -A): debian/rules override_dh_installexamples make[1]: Entering

Processed: py2removal bugs severity updates - 2020-04-23 13:51:36.500489+00:00

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: Bug#958350 marked as pending in devscripts

Processing control commands: > tag -1 pending Bug #958350 [src:devscripts] devscripts: autopkgtest needs update for new version of debhelper Added tag(s) pending. -- 958350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958350 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#958350: marked as pending in devscripts

Control: tag -1 pending Hello, Bug #958350 in devscripts 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:

Bug#958531: pandas: broken by NaT/isnan changes in numpy 1.18

Package: python3-pandas Version: 0.25.3+dfsg-9 Severity: serious Tags: fixed-upstream patch numpy 1.18 includes two behaviour changes that affect pandas, causing a CI fail / presumed FTBFS. Both are fixed in pandas 1.0 (in experimental, but moving that to unstable causes other issues, see

Bug#958533: pyxdg: autopkgtest regression: still tests Python2 package

Source: pyxdg Version: 0.26-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of pyxdg the autopkgtest of pyxdg fails in testing when that autopkgtest is run with the binary packages of

Bug#958419: marked as done (swi-prolog breaks eye autopkgtest: Failed 7/15 subtests)

Your message dated Thu, 23 Apr 2020 13:03:38 + with message-id and subject line Bug#958419: fixed in eye 20.0411.2226~ds-2 has caused the Debian Bug report #958419, regarding swi-prolog breaks eye autopkgtest: Failed 7/15 subtests to be marked as done. This means that you claim that the

Bug#958419: fixed in eye 20.0411.2226~ds-1

Quoting Lev Lamberov (2020-04-23 14:31:32) > Чт 23 апр 2020 @ 14:15 Jonas Smedegaard : > > >> Ohhh, I see. Let me upload (source-only) 8.1.29 to unstable. Will > >> be OK for you? > > > > If I understand the situation correctly, then this is a bug in how > > eye is packaged: A prolog image is

Bug#958419: fixed in eye 20.0411.2226~ds-1

Чт 23 апр 2020 @ 14:15 Jonas Smedegaard : >> Ohhh, I see. Let me upload (source-only) 8.1.29 to unstable. Will be OK >> for you? > > If I understand the situation correctly, then this is a bug in how eye > is packaged: A prolog image is dumped during build and shipped as the > executable for

Bug#958419: fixed in eye 20.0411.2226~ds-1

Quoting Lev Lamberov (2020-04-23 13:46:17) > Чт 23 апр 2020 @ 13:05 Jonas Smedegaard : > > > Quoting Jonas Smedegaard (2020-04-23 12:56:23) > >> Quoting Lev Lamberov (2020-04-23 12:15:12) > >> > Чт 23 апр 2020 @ 11:58 Jonas Smedegaard : > >> > > >> > > Quoting Lev Lamberov (2020-04-23 11:38:36)

Bug#958419: fixed in eye 20.0411.2226~ds-1

Control: reopen -1 Quoting Paul Gevers (2020-04-23 13:37:43) > On 23-04-2020 12:56, Jonas Smedegaard wrote: > > Ohh, the test failure I reference was for _testing_ - I thought it > > was for _unstable_ and was puzzled why it also failed there. > > > > Yes, I agree that this looks like just an

Processed: Re: Bug#958419: fixed in eye 20.0411.2226~ds-1

Processing control commands: > reopen -1 Bug #958419 {Done: Jonas Smedegaard } [src:swi-prolog, src:eye] swi-prolog breaks eye autopkgtest: Failed 7/15 subtests Bug reopened Ignoring request to alter fixed versions of bug #958419 to the same values previously set -- 958419:

Bug#954866: Bug#953881: transition: ruby2.7 only

Hi James, On 23-04-2020 13:38, James McCoy wrote: > On Thu, Apr 23, 2020 at 10:13:15AM +0200, Paul Gevers wrote: >> It seems the ruby2.5 removal transition [1] is stalled by subversion >> [2]. Can the fix for 954866 please be uploaded to unstable such that >> subversion can migrate and we can

Bug#958419: fixed in eye 20.0411.2226~ds-1

Чт 23 апр 2020 @ 13:05 Jonas Smedegaard : > Quoting Jonas Smedegaard (2020-04-23 12:56:23) >> Quoting Lev Lamberov (2020-04-23 12:15:12) >> > Чт 23 апр 2020 @ 11:58 Jonas Smedegaard : >> > >> > > Quoting Lev Lamberov (2020-04-23 11:38:36) >> > >> > >> Чт 23 апр 2020 @ 10:59 Paul Gevers : >> >

Bug#944017: libsoxr: autopkgtest regression: segmentation fault

Hi Bernhard! On 12/12/19 2:42 AM, Bernhard Übelacker wrote: > In the end it runs: > > dd if=/dev/urandom count=1000 | /tmp/tmp.bQI47Dtfhv/4-split-channels 7 > 6 2 2 3 > (...) > Thread 1 received signal SIGTRAP, Trace/breakpoint trap. > 0x0485210a in lsx_rint16_clip_dither_f

Bug#954866: Bug#953881: transition: ruby2.7 only

On Thu, Apr 23, 2020 at 10:13:15AM +0200, Paul Gevers wrote: > It seems the ruby2.5 removal transition [1] is stalled by subversion > [2]. Can the fix for 954866 please be uploaded to unstable such that > subversion can migrate and we can finish the removal of ruby2.5 in testing? I'd rather not

Bug#958419: fixed in eye 20.0411.2226~ds-1

Hi Jonas, On 23-04-2020 12:56, Jonas Smedegaard wrote: > Ohh, the test failure I reference was for _testing_ - I thought it was > for _unstable_ and was puzzled why it also failed there. > > Yes, I agree that this looks like just an autopkgtest issue (but makes > me wonder if eye should

Bug#952951: botan: Replace PKCS11 headers provided by OASIS

On Thu, Apr 23, 2020 at 01:09:42PM +0300, Adrian Bunk wrote: > So what is the way forward you suggest? > Asking someone (who?) for advice? > RC bug also against p11-kit? > ...??? It might be worth contacting OASIS on this issue, not sure. Maybe they would be willing to relicense or clarify

Bug#958419: fixed in eye 20.0411.2226~ds-1

Quoting Jonas Smedegaard (2020-04-23 12:56:23) > Quoting Lev Lamberov (2020-04-23 12:15:12) > > Чт 23 апр 2020 @ 11:58 Jonas Smedegaard : > > > > > Quoting Lev Lamberov (2020-04-23 11:38:36) > > > > >> Чт 23 апр 2020 @ 10:59 Paul Gevers : > > > > >> > [Release team member hat on] > > >> > > >

Bug#958419: marked as done (swi-prolog breaks eye autopkgtest: Failed 7/15 subtests)

Your message dated Thu, 23 Apr 2020 12:56:23 +0200 with message-id <158763938357.706968.17592079271467320...@auryn.jones.dk> and subject line Re: Bug#958419: fixed in eye 20.0411.2226~ds-1 has caused the Debian Bug report #958419, regarding swi-prolog breaks eye autopkgtest: Failed 7/15 subtests

Bug#952102: marked as done (salmon: FTBFS: SalmonAlevin.cpp:780:6: error: ‘class rapmap::utils::MappingConfig’ has no member named ‘maxSlack’)

Your message dated Thu, 23 Apr 2020 10:36:27 + with message-id and subject line Bug#952102: fixed in salmon 1.2.1+ds1-1 has caused the Debian Bug report #952102, regarding salmon: FTBFS: SalmonAlevin.cpp:780:6: error: ‘class rapmap::utils::MappingConfig’ has no member named ‘maxSlack’ to be

Processed: Re: Bug#958350: devscripts: autopkgtest needs update for new version of debhelper

Processing control commands: > tags -1 + patch Bug #958350 [src:devscripts] devscripts: autopkgtest needs update for new version of debhelper Added tag(s) patch. > forwarded -1 https://salsa.debian.org/debian/devscripts/-/merge_requests/185 Bug #958350 [src:devscripts] devscripts: autopkgtest

Bug#958350: devscripts: autopkgtest needs update for new version of debhelper

Control: tags -1 + patch Control: forwarded -1 https://salsa.debian.org/debian/devscripts/-/merge_requests/185 On Mon, 20 Apr 2020 at 22:00:19 +0200, Paul Gevers wrote: > /tmp/autopkgtest-lxc.8rtfp1uo/downtmp/build.7Up/src/test/package_lifecycle/debuild.txt\n > expected:<0> but was:<1> > 10,11d9

Processed: Remove pkpgcounter

Processing commands for cont...@bugs.debian.org: > retitle 937297 RM: PKG -- removal triggered by the Python2 removal Bug #937297 [src:pkpgcounter] pkpgcounter: Python2 removal in sid/bullseye Changed Bug title to 'RM: PKG -- removal triggered by the Python2 removal' from 'pkpgcounter: Python2

Bug#958419: fixed in eye 20.0411.2226~ds-1

Чт 23 апр 2020 @ 11:58 Jonas Smedegaard : > Quoting Lev Lamberov (2020-04-23 11:38:36) >> Чт 23 апр 2020 @ 10:59 Paul Gevers : >> > [Release team member hat on] >> > >> > On 21-04-2020 23:48, Debian FTP Masters wrote: >> >> eye (20.0411.2226~ds-1) unstable; urgency=medium >> >> . >> >>[

Bug#952951: botan: Replace PKCS11 headers provided by OASIS

On Tue, Mar 24, 2020 at 09:30:55PM -0700, Sean Whitton wrote: > On Tue 10 Mar 2020 at 06:32PM +01, László Böszörményi (GCS) wrote: > > > Its CONTRIBUTING.md [3] adds: "Subject to applicable licensing rules, > > the repository content may be re-used freely, including the creation > > and

Processed: reopening 958419

Processing commands for cont...@bugs.debian.org: > reopen 958419 Bug #958419 {Done: Jonas Smedegaard } [src:swi-prolog, src:eye] swi-prolog breaks eye autopkgtest: Failed 7/15 subtests 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared,

Bug#958419: fixed in eye 20.0411.2226~ds-1

Quoting Lev Lamberov (2020-04-23 11:38:36) > Hi, > > Чт 23 апр 2020 @ 10:59 Paul Gevers : > > > [Release team member hat on] > > > > On 21-04-2020 23:48, Debian FTP Masters wrote: > >> eye (20.0411.2226~ds-1) unstable; urgency=medium > >> . > >>[ upstream ] > >>* new release(s) > >>

Processed: Re: Bug#958514: mkgmap-splitter: Running mkgmap-spitter fails with java exception

Processing control commands: > severity -1 important Bug #958514 [mkgmap-splitter] mkgmap-splitter: Running mkgmap-spitter fails with java exception Severity set to 'important' from 'grave' -- 958514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958514 Debian Bug Tracking System Contact

Bug#958514: mkgmap-splitter: Running mkgmap-spitter fails with java exception

Control: severity -1 important Since splitting an XML file works, an RC severity is not appropriate. A workaround is to convert the PBF to XML with osmium-tool or osmosis. On 4/23/20 10:58 AM, Guillaume Brocker wrote: > Exception in thread "main" java.lang.NoSuchMethodError: >

Bug#958419: fixed in eye 20.0411.2226~ds-1

Hi, Чт 23 апр 2020 @ 10:59 Paul Gevers : > [Release team member hat on] > > On 21-04-2020 23:48, Debian FTP Masters wrote: >> eye (20.0411.2226~ds-1) unstable; urgency=medium >> . >>[ upstream ] >>* new release(s) >> + FIXED: process_create/3: stderr was sent to stdout. >>

Bug#958419: fixed in eye 20.0411.2226~ds-1

Quoting Jonas Smedegaard (2020-04-23 11:27:47) > Quoting Paul Gevers (2020-04-23 10:59:02) > > [Release team member hat on] > > > > On 21-04-2020 23:48, Debian FTP Masters wrote: > > > eye (20.0411.2226~ds-1) unstable; urgency=medium > > > . > > >[ upstream ] > > >* new release(s) > > >

Bug#958419: fixed in eye 20.0411.2226~ds-1

Quoting Paul Gevers (2020-04-23 10:59:02) > [Release team member hat on] > > On 21-04-2020 23:48, Debian FTP Masters wrote: > > eye (20.0411.2226~ds-1) unstable; urgency=medium > > . > >[ upstream ] > >* new release(s) > > + FIXED: process_create/3: stderr was sent to stdout. > >

Bug#958419: fixed in eye 20.0411.2226~ds-1

Quoting Paul Gevers (2020-04-23 10:59:02) > On 21-04-2020 23:48, Debian FTP Masters wrote: > > eye (20.0411.2226~ds-1) unstable; urgency=medium > > . > >[ upstream ] > >* new release(s) > > + FIXED: process_create/3: stderr was sent to stdout. > >closes: Bug#958419, thanks

Bug#958515: diamond-aligner breaks proteinortho autopkgtest on arm64: Error: wrong fromat

Source: diamond-aligner, proteinortho Control: found -1 diamond-aligner/0.9.31-1 Control: found -1 proteinortho/6.0.14+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a

Processed: diamond-aligner breaks proteinortho autopkgtest on arm64: Error: wrong fromat

Processing control commands: > found -1 diamond-aligner/0.9.31-1 Bug #958515 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks proteinortho autopkgtest on arm64: Error: wrong fromat Marked as found in versions diamond-aligner/0.9.31-1. > found -1 proteinortho/6.0.14+dfsg-1 Bug

Bug#956908: marked as done (scilab: Fail to run: null pointer)

Your message dated Thu, 23 Apr 2020 09:07:14 + with message-id and subject line Bug#956908: fixed in scilab 6.1.0+dfsg1-2 has caused the Debian Bug report #956908, regarding scilab: Fail to run: null pointer to be marked as done. This means that you claim that the problem has been dealt

Bug#958419: fixed in eye 20.0411.2226~ds-1

Hi Jonas, [Release team member hat on] On 21-04-2020 23:48, Debian FTP Masters wrote: > eye (20.0411.2226~ds-1) unstable; urgency=medium > . >[ upstream ] >* new release(s) > + FIXED: process_create/3: stderr was sent to stdout. >closes: Bug#958419, thanks to Paul Gevers

Bug#958514: mkgmap-splitter: Running mkgmap-spitter fails with java exception

Package: mkgmap-splitter Version: 0.0.0+svn597-1 Severity: grave Justification: renders package unusable Dear Maintainer, I run mkgmap splitter on some OpenStreetMap data extract, and it failed with the following java exception : Exception in thread "main" java.lang.NoSuchMethodError:

Bug#953777: Incorrect fix [Was: php-doctrine-cache_1.10.0-4_source.changes ACCEPTED into unstable]

Control: severity -1 important Hi all, On Tue, 24 Mar 2020 09:59:48 +0100 =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= wrote: > Yes, you were right. It didn't help, so I've requested binNMUs for all the > extensions to remove dependency on PHP 7.3, so it will sort out when the > binNMU is finished. This

Processed: Re: Bug#953777: Incorrect fix [Was: php-doctrine-cache_1.10.0-4_source.changes ACCEPTED into unstable]

Processing control commands: > severity -1 important Bug #953777 [php-apcu] php-apcu breaks php-doctrine-cache autopkgtest: Class 'DOMDocument' not found Severity set to 'important' from 'serious' -- 953777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953777 Debian Bug Tracking System

Bug#875584: marked as done (FTBFS with Java 9: can't find jdk)

Your message dated Thu, 23 Apr 2020 08:21:55 + with message-id and subject line Bug#875584: fixed in jhdf 2.11.0+dfsg-4 has caused the Debian Bug report #875584, regarding FTBFS with Java 9: can't find jdk to be marked as done. This means that you claim that the problem has been dealt with.

  1   2   >