Processed: Re: flatbuffers FTBFS: MISSING symbols for libflatbuffers1

Processing control commands: > fixed -1 1.11.0+dfsg1-1.4 Bug #961550 [src:flatbuffers] flatbuffers FTBFS: MISSING symbols for libflatbuffers1 The source 'flatbuffers' and version '1.11.0+dfsg1-1.4' do not appear to match any binary packages Marked as fixed in versions

Bug#961550: flatbuffers FTBFS: MISSING symbols for libflatbuffers1

control: fixed -1 1.11.0+dfsg1-1.4 control: close -1 closing! On Mon, 25 May 2020 21:40:04 + Vasyl Gello wrote: > Source: flatbuffers > Version: 1.11.0+dfsg1-1.3 > Severity: serious > Tags: patch ftbfs > > Dear colleagues, > > I tried to build flatbuffers for buster/amd64, and got the

Bug#961285: marked as done (theme-d-gnome: Failed to migrate to testing for too long)

Your message dated Fri, 29 May 2020 10:35:45 + with message-id and subject line Bug#960584: fixed in theme-d-gnome 0.9.0-1.1 has caused the Debian Bug report #960584, regarding theme-d-gnome: Failed to migrate to testing for too long to be marked as done. This means that you claim that the

Bug#960584: marked as done (src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries)

Your message dated Fri, 29 May 2020 10:35:45 + with message-id and subject line Bug#960584: fixed in theme-d-gnome 0.9.0-1.1 has caused the Debian Bug report #960584, regarding src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries to be marked as done.

Bug#961631: marked as done (libopenmpi3: causes openmpi-bin/buster to segfault)

Your message dated Fri, 29 May 2020 10:49:01 + with message-id and subject line Bug#961631: fixed in openmpi 4.0.3-8 has caused the Debian Bug report #961631, regarding libopenmpi3: causes openmpi-bin/buster to segfault to be marked as done. This means that you claim that the problem has

Bug#950858: marked as done (fades fails autopkg tests with python 3.8)

Your message dated Fri, 29 May 2020 11:04:12 + with message-id and subject line Bug#950858: fixed in fades 9.0-1 has caused the Debian Bug report #950858, regarding fades fails autopkg tests with python 3.8 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#954148: doit: diff for NMU version 0.31.1-3.3

On Wed, 27 May 2020 10:11:26 +0300 Adrian Bunk wrote: > Control: tags 954148 + patch > Control: tags 954148 + pending > > Dear maintainer, > > I've prepared an NMU for doit (versioned as 0.31.1-3.3) and uploaded > it to DELAYED/15. Please feel free to tell me if I should cancel it. > > cu >

Bug#961777: marked as done (bamtools: binary-all FTBFS)

Your message dated Fri, 29 May 2020 11:33:33 + with message-id and subject line Bug#961777: fixed in bamtools 2.5.1+dfsg-7 has caused the Debian Bug report #961777, regarding bamtools: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#961759: marked as done (libpbcopper1.6.0: missing Breaks+Replaces: libpbcopper1.3.0 (>= 1.6))

Your message dated Fri, 29 May 2020 11:50:02 + with message-id and subject line Bug#961759: fixed in pbcopper 1.6.0+dfsg-4 has caused the Debian Bug report #961759, regarding libpbcopper1.6.0: missing Breaks+Replaces: libpbcopper1.3.0 (>= 1.6) to be marked as done. This means that you claim

Bug#961755: marked as done (dh-golang: dh_golang_autopkgtest no longer detects debian/rules targets with make-4.3)

Your message dated Fri, 29 May 2020 10:18:38 + with message-id and subject line Bug#961755: fixed in dh-golang 1.49 has caused the Debian Bug report #961755, regarding dh-golang: dh_golang_autopkgtest no longer detects debian/rules targets with make-4.3 to be marked as done. This means that

Bug#961779: obs-studio: FTBFS when using SIMDE

Attached is a fix , also available at https://salsa.debian.org/multimedia-team/obs-studio/-/merge_requests/3 for the convenience of the maintainers On Fri, May 29, 2020 at 7:51 AM Adrian Bunk wrote: > Source: obs-studio > Version: 25.0.8+dfsg1-1 > Severity: serious > Tags: ftbfs > >

Bug#961779: marked as done (obs-studio: FTBFS when using SIMDE)

Your message dated Fri, 29 May 2020 10:12:35 + with message-id and subject line Bug#961779: fixed in obs-studio 25.0.8+dfsg1-2 has caused the Debian Bug report #961779, regarding obs-studio: FTBFS when using SIMDE to be marked as done. This means that you claim that the problem has been

Bug#959138: nipy: resolve nipy autopkgtest failure due to numpy testing decorators

On Fri, May 29, 2020 at 12:50:07AM -0400, Sandro Tosi wrote: > On Wed, 20 May 2020 15:22:37 -0500 Matthieu Clemenceau > wrote: > > Source: nipy > > Followup-For: Bug #959138 > > User: ubuntu-de...@lists.ubuntu.com > > Usertags: origin-ubuntu groovy ubuntu-patch > > > > Dear Maintainer, > > > >

Bug#961798: python-pyaudio: FTBFS for doc package

Package: python-pyaudio Version: 0.2.11-1.1 Severity: serious python-pyaudio fails to build from source in both testing and unstable with the following error: dh_installinit: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_perl -O--buildsystem=pybuild dh_link

Bug#961700: picard-tools build depends on the removed libguava-java-doc

Le jeu. 28 mai 2020 à 13:00, Andreas Tille a écrit : > Hi Olivier and Vincent > > On Thu, May 28, 2020 at 09:47:37AM +0300, Adrian Bunk wrote: > > > > picard-tools build depends on libguava-java-doc, > > which is no longer built by src:guava-libraries. > Hi andreas, looking at issue, where did

Processed: fixed 960558 in 3.2.1-1

Processing commands for cont...@bugs.debian.org: > fixed 960558 3.2.1-1 Bug #960558 [cyrus-common] cyrus-common: lmtpd aborts when compiled with optimisation and FORTIFY_SOURCE flags Marked as fixed in versions cyrus-imapd/3.2.1-1. > thanks Stopping processing here. Please contact me if you

Bug#936798: Please port KisSplice to Python3 (Was: Bug#936798: kissplice: Python2 removal in sid/bullseye)

Hi, I've uploaded since the Python3 issue is solved. For upstream please note: There are some remaining Python2 files in the test suite. Please consider the patch https://salsa.debian.org/med-team/kissplice/-/blob/master/debian/patches/tests-2to3.patch There are build time errors

Processed: Re: Bug#918572: fixed in check 0.12.0-0.2

Processing control commands: > clone -1 -2 Bug #918572 {Done: Paul Gevers } [src:check] check FTBFS on ppc*: test failure Bug 918572 cloned as bug 961781 > reopen -2 Bug #961781 {Done: Paul Gevers } [src:check] check FTBFS on ppc*: test failure 'reopen' may be inappropriate when a bug has been

Bug#918572: fixed in check 0.12.0-0.2

Control: clone -1 -2 Control: reopen -2 Control: retitle -2 [ppc64el] build time tests FAIL and are disabled Control: severity -2 important Hi, On 28-05-2020 22:21, Debian FTP Masters wrote: > Changed-By: Paul Gevers > Closes: 918572 > Changes: > check (0.12.0-0.2) unstable; urgency=medium >

Processed: severity of 961755 is serious

Processing commands for cont...@bugs.debian.org: > severity 961755 serious Bug #961755 [dh-golang] dh-golang: dh_golang_autopkgtest no longer detects debian/rules targets with make-4.3 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Bug#959410: jinja2 breaks oca-core autopkgtest: The server encountered an internal error and was unable to complete your request

Control: reassign -1 python3-jinja2 2.11.1-1 Control: affects -1 src:oca-core According to the discussion at [1] this was broken by a change in jinja2 that has been reverted in 2.11.2. cu Adrian [1] https://github.com/odoo/odoo/issues/50552

Processed: Re: Bug#959410: jinja2 breaks oca-core autopkgtest: The server encountered an internal error and was unable to complete your request

Processing control commands: > reassign -1 python3-jinja2 2.11.1-1 Bug #959410 [src:oca-core] jinja2 breaks oca-core autopkgtest: The server encountered an internal error and was unable to complete your request Bug reassigned from package 'src:oca-core' to 'python3-jinja2'. Ignoring request to

Bug#961782: glue-sprite is not installable in unstable

Package: glue-sprite Version: 0.13-3 Severity: serious The following packages have unmet dependencies: glue-sprite : Depends: python3-jinja2 (< 2.11) but 2.11.1-1 is to be installed

Processed: bug 960558 is forwarded to https://github.com/cyrusimap/cyrus-imapd/issues/1981

Processing commands for cont...@bugs.debian.org: > forwarded 960558 https://github.com/cyrusimap/cyrus-imapd/issues/1981 Bug #960558 [cyrus-common] cyrus-common: lmtpd aborts when compiled with optimisation and FORTIFY_SOURCE flags Set Bug forwarded-to-address to

Bug#960558: marked as done (cyrus-common: lmtpd aborts when compiled with optimisation and FORTIFY_SOURCE flags)

Your message dated Fri, 29 May 2020 08:35:42 + with message-id and subject line Bug#960558: fixed in cyrus-imapd 3.2.1-3 has caused the Debian Bug report #960558, regarding cyrus-common: lmtpd aborts when compiled with optimisation and FORTIFY_SOURCE flags to be marked as done. This means

Bug#961700: marked as done (picard-tools build depends on the removed libguava-java-doc)

Your message dated Fri, 29 May 2020 08:36:50 + with message-id and subject line Bug#961700: fixed in picard-tools 2.18.25+dfsg-3 has caused the Debian Bug report #961700, regarding picard-tools build depends on the removed libguava-java-doc to be marked as done. This means that you claim

Bug#961700: picard-tools build depends on the removed libguava-java-doc

On Fri, May 29, 2020 at 08:55:48AM +0200, Andreas Tille wrote: > Hi Adrian, > > I think this question is for you ... > > Kind regards > >Andreas. > > On Fri, May 29, 2020 at 08:12:02AM +0200, olivier sallou wrote: > > Le jeu. 28 mai 2020 à 13:00, Andreas Tille a écrit : > > > > > Hi

Bug#961700: picard-tools build depends on the removed libguava-java-doc

Hi Adrian, I think this question is for you ... Kind regards Andreas. On Fri, May 29, 2020 at 08:12:02AM +0200, olivier sallou wrote: > Le jeu. 28 mai 2020 à 13:00, Andreas Tille a écrit : > > > Hi Olivier and Vincent > > > > On Thu, May 28, 2020 at 09:47:37AM +0300, Adrian Bunk

Processed: tagging 961755

Processing commands for cont...@bugs.debian.org: > tags 961755 + pending Bug #961755 [dh-golang] dh-golang: dh_golang_autopkgtest no longer detects debian/rules targets with make-4.3 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 961755:

Bug#936798: marked as done (kissplice: Python2 removal in sid/bullseye)

Your message dated Fri, 29 May 2020 07:33:39 + with message-id and subject line Bug#936798: fixed in kissplice 2.5.1-1 has caused the Debian Bug report #936798, regarding kissplice: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#960877: meson 0.54.2-1 breaks bali-phy build

This should already be fixed in the current meson master with https://github.com/mesonbuild/meson/pull/7179 pgpgrVZyLIdu1.pgp Description: OpenPGP digital signature

Bug#952171: yubico-pam: diff for NMU version 2.26-1.1

Control: tags 952171 + patch Control: tags 952171 + pending Dear maintainer, I've prepared an NMU for yubico-pam (versioned as 2.26-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru yubico-pam-2.26/debian/changelog

Processed: yubico-pam: diff for NMU version 2.26-1.1

Processing control commands: > tags 952171 + patch Bug #952171 [src:yubico-pam] yubico-pam: FTBFS: dh_auto_test: error: cd build && make -j4 check VERBOSE=1 returned exit code 2 Added tag(s) patch. > tags 952171 + pending Bug #952171 [src:yubico-pam] yubico-pam: FTBFS: dh_auto_test: error: cd

Bug#961486: marked as done (perl6-zef FTBFS: Failed to create directory '/sbuild-nonexistent/.raku/precomp')

Your message dated Fri, 29 May 2020 15:03:54 + with message-id and subject line Bug#961486: fixed in perl6-zef 0.8.4-2 has caused the Debian Bug report #961486, regarding perl6-zef FTBFS: Failed to create directory '/sbuild-nonexistent/.raku/precomp' to be marked as done. This means that

Bug#961811: baresip FTBFS with make 4.3

Source: baresip Version: 0.6.1-1 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/baresip.html ... modules/bv32/bv32.c:9:10: fatal error: bv32/bv32.h: No such file or directory 9 | #include | ^

Processed: found 961741 in 0.48.0-3, tagging 961122

Processing commands for cont...@bugs.debian.org: > found 961741 0.48.0-3 Bug #961741 {Done: Drew Parsons } [src:numba] python3-sphinx: new release broke sphinx-build OUTPUTDIR The source 'numba' and version '0.48.0-3' do not appear to match any binary packages Marked as found in versions

Processed: closing 959578

Processing commands for cont...@bugs.debian.org: > close 959578 Bug #959578 [src:python-bumps] python-bumps: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13 Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Processed (with 1 error): Merge duplicates

Processing commands for cont...@bugs.debian.org: > unarchive 713688 Bug #713688 {Done: Chris Taylor } [src:audtty] audtty: FTBFS: ld: main.o: undefined reference to symbol 'g_type_init' Unarchived Bug 713688 > forcemerge 713688 704539 Bug #713688 {Done: Chris Taylor } [src:audtty] audtty:

Bug#959634: audtty: diff for NMU version 0.1.12-5.1

Control: tags 959634 + patch Control: tags 959634 + pending Dear maintainer, I've prepared an NMU for audtty (versioned as 0.1.12-5.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru audtty-0.1.12/debian/changelog

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 704539 src:audtty Bug #704539 [audtty] audtty: ftbs with ld --no-add-needed Bug reassigned from package 'audtty' to 'src:audtty'. No longer marked as found in versions audtty/0.1.12-3. Ignoring request to alter fixed versions of bug

Processed: audtty: diff for NMU version 0.1.12-5.1

Processing control commands: > tags 959634 + patch Bug #959634 [src:audtty] audtty: FTBFS: audctrl.h:25:10: fatal error: dbus/dbus-glib.h: No such file or directory Added tag(s) patch. > tags 959634 + pending Bug #959634 [src:audtty] audtty: FTBFS: audctrl.h:25:10: fatal error:

Bug#961814: Not ready for using

Package: golang-google-protobuf Severity: serious Though it has been packaged, it's not ready for using. The current version will generate .pb.go files which requires v1.4+ version of `github.com/golang/protobuf/proto`. See the reason at https://github.com/golang/protobuf/issues/1077 Besides, I

Bug#959564: marked as done (openslide-python: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py))

Your message dated Fri, 29 May 2020 16:19:13 + with message-id and subject line Bug#959564: fixed in openslide-python 1.1.1-5 has caused the Debian Bug report #959564, regarding openslide-python: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools'

Bug#959157: fix for CVE-2020-1749 in linux-image-4.19.0-9 breaks wireguard

Hello, I'm experiencing the same error: " DKMS make.log for wireguard-1.0.20200506 for kernel 4.19.118 (x86_64) Fri 29 May 2020 06:12:30 PM CEST make: Entering directory '/usr/src/linux-source-4.19' CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/main.o CC [M]

Bug#959548: eukleides: diff for NMU version 1.5.4-4.2

Control: tags 959548 + patch Control: tags 959548 + pending Dear maintainer, I've prepared an NMU for eukleides (versioned as 1.5.4-4.2) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru eukleides-1.5.4/debian/changelog

Processed: eukleides: diff for NMU version 1.5.4-4.2

Processing control commands: > tags 959548 + patch Bug #959548 [src:eukleides] eukleides: FTBFS: make[1]: mktexlsr: Command not found Added tag(s) patch. > tags 959548 + pending Bug #959548 [src:eukleides] eukleides: FTBFS: make[1]: mktexlsr: Command not found Added tag(s) pending. -- 959548:

Bug#959552: python-canmatrix: diff for NMU version 0.9.1~github-1.1

Control: tags 959552 + patch Control: tags 959552 + pending Dear maintainer, I've prepared an NMU for python-canmatrix (versioned as 0.9.1~github-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru

Processed: python-canmatrix: diff for NMU version 0.9.1~github-1.1

Processing control commands: > tags 959552 + patch Bug #959552 [src:python-canmatrix] python-canmatrix: FTBFS: dh_install: error: missing files, aborting Added tag(s) patch. > tags 959552 + pending Bug #959552 [src:python-canmatrix] python-canmatrix: FTBFS: dh_install: error: missing files,

Bug#961536: openmw FTBFS with openscenegraph 3.6.5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 That's a pity but give a few more days and 0.46 will be released. No point in patching and going through this whole process again, I'll make sure everything is ready to go to to upload. Cheers, Bret -BEGIN PGP SIGNATURE- Version: FlowCrypt

Bug#961702: git breaks fdroidserver autopkgtest: Failed to parse line: ' git config pull.rebase false

reassign 961702 python3-git 3.1.1-1 affects 961702 git quit Hi, Hans-Christoph Steiner wrote: > I can't find any possible reference in fdroidserver, or in python3-git > for that matter. My guess is that the issue is caused by python3-git > failing to parse something that was added in the most

Processed: Re: git breaks fdroidserver autopkgtest: Failed to parse line: ' git config pull.rebase false

Processing commands for cont...@bugs.debian.org: > reassign 961702 python3-git 3.1.1-1 Bug #961702 [src:git,python3-git] git breaks fdroidserver autopkgtest: Failed to parse line: ' git config pull.rebase false Bug reassigned from package 'src:git,python3-git' to 'python3-git'. No longer marked

Processed: tagging 936105

Processing commands for cont...@bugs.debian.org: > tags 936105 + fixed-upstream Bug #936105 [src:abinit] abinit: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936105:

Bug#921298: marked as done (libstxxl: FTBFS with upcoming doxygen 1.8.15)

Your message dated Fri, 29 May 2020 22:20:18 +0300 with message-id <20200529192017.GA15547@localhost> and subject line Re: Bug#921298: FTBFS also with doxygen 1.8.16-1~exp3 from experimental has caused the Debian Bug report #921298, regarding libstxxl: FTBFS with upcoming doxygen 1.8.15 to be

Processed: closing 955657

Processing commands for cont...@bugs.debian.org: > close 955657 2.14.1-1 Bug #955657 [src:ufo2ft] ufo2ft: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13 Marked as fixed in versions ufo2ft/2.14.1-1. Bug #955657 [src:ufo2ft] ufo2ft:

Bug#960819: squid command failure without systemd

On Saturday, May 23 2020, Amos Jeffries wrote: > On Mon, 18 May 2020 18:27:04 -0400 Sergio Durigan Junior wrote: >> On Monday, May 18 2020, I wrote: >> >> > Just a few more details I've been able to gather this afternoon. >> > >> > I'm using a Debian sid VM where I installed sysvinit to replace

Bug#735260: marked as done (installation-reports: Jessie Netinst for PowerPC-64 creates will not boot after installation -- but works for PowerPC-32)

Your message dated Fri, 29 May 2020 22:24:55 +0200 with message-id <20200529222455.f5892e83f813eb4f716ba...@mailbox.org> and subject line bugreports housekeeping: closing yaboot-installer bugs has caused the Debian Bug report #735260, regarding installation-reports: Jessie Netinst for PowerPC-64

Bug#771040: marked as done (installation-reports: Messes up Mac OS 9 driver partitions)

Your message dated Fri, 29 May 2020 22:24:55 +0200 with message-id <20200529222455.f5892e83f813eb4f716ba...@mailbox.org> and subject line bugreports housekeeping: closing yaboot-installer bugs has caused the Debian Bug report #771040, regarding installation-reports: Messes up Mac OS 9 driver

Bug#960256: marked as done (drumgizmo FTBFS with lv2-dev 1.18.0-1)

Your message dated Fri, 29 May 2020 20:23:03 + with message-id and subject line Bug#960256: fixed in drumgizmo 0.9.18.1-2 has caused the Debian Bug report #960256, regarding drumgizmo FTBFS with lv2-dev 1.18.0-1 to be marked as done. This means that you claim that the problem has been dealt

Bug#795211: marked as done (Yaboot in Jessie, following Jessie OS installation, fails to boot Mac OS X)

Your message dated Fri, 29 May 2020 22:24:55 +0200 with message-id <20200529222455.f5892e83f813eb4f716ba...@mailbox.org> and subject line bugreports housekeeping: closing yaboot-installer bugs has caused the Debian Bug report #795211, regarding Yaboot in Jessie, following Jessie OS installation,

Bug#959180: mitmproxy: Support for tornado 6

Hi Gordon, > mitmproxy is the only blocker I've found (so far) which is incompatible > (at least to build) with this version (as opposed to 5.1.1 in unstable). Given that you say this was a build incompatibility, could you explain why you thought it was necessary to add a runtime Breaks:? --

Bug#960819: squid command failure without systemd

On Friday, May 29 2020, I wrote: > On Saturday, May 23 2020, Amos Jeffries wrote: >> To fix we will either have to find a way to stop systemd erasing the >> /run/squid directory, or patch the Squid code to create the PID file >> path as-needed not just the file itself. >> For the latter, PRs are

Bug#961702: marked as forwarded (git breaks fdroidserver autopkgtest: Failed to parse line: ' git config pull.rebase false)

Your message dated Fri, 29 May 2020 22:52:21 -0400 with message-id <20200530025221.ga3014...@lena.dartmouth.edu> has caused the report #961702, regarding git breaks fdroidserver autopkgtest: Failed to parse line: ' git config pull.rebase false to be marked as having been forwarded to the

Bug#953487: marked as done (runescape: binaries for non-free not auto-built)

Your message dated Fri, 29 May 2020 21:04:40 + with message-id and subject line Bug#953487: fixed in runescape 0.8-2 has caused the Debian Bug report #953487, regarding runescape: binaries for non-free not auto-built to be marked as done. This means that you claim that the problem has been

Processed: Re: bugreports housekeeping: closing yaboot-installer bugs

Processing commands for cont...@bugs.debian.org: > fixed 735260 1.1.41+rm Bug #735260 {Done: Holger Wansing } [yaboot-installer] installation-reports: Jessie Netinst for PowerPC-64 creates will not boot after installation -- but works for PowerPC-32 There is no source info for the package