Bug#978452: marked as done (python3-opencv: missing dependency on libcharls2)

Your message dated Tue, 29 Dec 2020 07:03:35 + with message-id and subject line Bug#978452: fixed in opencv 4.5.1+dfsg-2 has caused the Debian Bug report #978452, regarding python3-opencv: missing dependency on libcharls2 to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

Processing control commands: > severity -1 serious Bug #978555 {Done: Steve Langasek } [libpam-modules] libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file Severity set to 'serious' from 'normal' -- 978555:

Bug#977473: Re-activate test for gdcm

Control: retitle -1 Reactivate test for gdcm which was excluded due to failure Control: severity -1 important This single test prevented testing migration of this package and all its dependencies. Thus the test was deactivated for the moment to enable building the package. But the issue should

Processed: Re-activate test for gdcm

Processing control commands: > retitle -1 Reactivate test for gdcm which was excluded due to failure Bug #977473 [src:insighttoolkit4] insighttoolkit4: FTBFS: TypeError: in method 'itkGDCMImageIO_GetValueFromTag', argument 3 of type 'std::string &' Changed Bug title to 'Reactivate test for gdcm

Bug#962203: NMU

On Mon, 2020-12-28 at 21:50 -0500, Calum McConnell wrote: > Yeah, when I tried to build it locally, it failed due to files that > are present in the source package but missing from Git. There are more changes than just the documentation build things though. > I eventually gave up and just

Bug#962203: NMU

On Tue, 2020-12-29 at 10:36 +0800, Paul Wise wrote: > On Mon, 14 Dec 2020 17:23:08 -0500 Calum McConnell wrote: > > > I have prepared an NMU for this package.  It is currently at > > https://mentors.debian.net/package/debdelta/ .  While I need a sponsor > > to > > get it into Debian, I am now

Bug#978188: marked as done (workrave: FTBFS: main.c:403:45: error: expected expression before ‘WorkraveApplet’)

Your message dated Tue, 29 Dec 2020 02:42:43 + with message-id and subject line Bug#978188: fixed in workrave 1.10.44-6 has caused the Debian Bug report #978188, regarding workrave: FTBFS: main.c:403:45: error: expected expression before ‘WorkraveApplet’ to be marked as done. This means

Bug#962203: NMU

On Mon, 14 Dec 2020 17:23:08 -0500 Calum McConnell wrote: > I have prepared an NMU for this package. It is currently at > https://mentors.debian.net/package/debdelta/ . While I need a sponsor to > get it into Debian, I am now reaching out to ment...@lists.debian.org to > see if I can expedite

Bug#978265: marked as done (sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

Your message dated Tue, 29 Dec 2020 00:35:44 + with message-id and subject line Bug#978265: fixed in sshuttle 1.0.5-1 has caused the Debian Bug report #978265, regarding sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This

Bug#911587: infnoise: busy-waits, using too much CPU

Hi Stephen, Stephen Kitt wrote: > I have figured out what was wrong (cue brown paper bag for me), I’ll upload a > fix shortly. Yay, thanks! Much appreciated! > > Not sure if any of these fix this issue. > > 0.3.1 was already in unstable, Oops, ok, sorry, my fault for not looking closer. >

Bug#977357: marked as done (libgdf ftbfs on s390x (test failures))

Your message dated Mon, 28 Dec 2020 23:48:27 + with message-id and subject line Bug#977357: fixed in libgdf 0.1.3-7 has caused the Debian Bug report #977357, regarding libgdf ftbfs on s390x (test failures) to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Bug#977357 marked as pending in libgdf

Processing control commands: > tag -1 pending Bug #977357 [src:libgdf] libgdf ftbfs on s390x (test failures) Added tag(s) pending. -- 977357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#977357: marked as pending in libgdf

Control: tag -1 pending Hello, Bug #977357 in libgdf 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: Re: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

Processing control commands: > severity -1 normal Bug #978555 [libpam-modules] libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file Severity set to 'normal' from 'grave' -- 978555:

Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

Control: severity -1 normal After a reboot too, the problem no longer occurs. Perhaps there should be a warning saying that some services may need to be restarted. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#978583: marked as done (libtrapperkeeper-filesystem-watcher-clojure: files in .jar don't follow the proper hierarchy)

Your message dated Mon, 28 Dec 2020 23:03:52 + with message-id and subject line Bug#978583: fixed in trapperkeeper-filesystem-watcher-clojure 1.2.2-2 has caused the Debian Bug report #978583, regarding libtrapperkeeper-filesystem-watcher-clojure: files in .jar don't follow the proper

Bug#978515: marked as done (grub2: non-standard gcc/g++ used for build (gcc-9))

Your message dated Mon, 28 Dec 2020 22:48:43 + with message-id and subject line Bug#978515: fixed in grub2 2.04-12 has caused the Debian Bug report #978515, regarding grub2: non-standard gcc/g++ used for build (gcc-9) to be marked as done. This means that you claim that the problem has been

Processed: Bug#978515 marked as pending in grub2

Processing control commands: > tag -1 pending Bug #978515 [grub2] grub2: non-standard gcc/g++ used for build (gcc-9) Added tag(s) pending. -- 978515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#978515: marked as pending in grub2

Control: tag -1 pending Hello, Bug #978515 in grub2 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#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

On Mon, Dec 28, 2020 at 5:00 PM Justin Erenkrantz wrote: > It's not clear to me if OpenSSL authors intended to make this breaking > change. On the serf side, we would need to think through what it would > mean to have our app callback return false upon failure in order to > short-circuit the

Bug#974011: xmille: Incorrect license/copyright for xmille

Adrian Bunk writes: > I am just a normal user enjoying the game, and looking at the number of > uploads in the past decade two maintainers might be sufficient to handle > the load. ;-) I've uploaded 'kgames' to the new queue :-) Thanks for playing. -- -keith signature.asc Description:

Bug#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

As an update, I've been able to triage this a bit further. It's definitely that last noted change (erroring out on expired self-signed root) that broke it. OpenSSL 1.1.1{g,h} are fine, but {i,-stable} are not. Reverting just x509_vfy.c to what is in 1.1.1h causes the test to pass. In this test

Bug#975193: marked as done (libkgapi: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2)

Your message dated Mon, 28 Dec 2020 22:42:09 +0100 with message-id <8751877.rMLUfLXkoz@tuxin> and subject line Re: Bug#975193: libkgapi: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2 has caused the Debian Bug report #975193, regarding

Bug#951588: kontact: akonadi is not operational

control: tags -1 + moreinfo control: severity -1 important Hey, please retry with the current version in testing/unstable and give us more information what you have tried to do before kontact returns with a segfault. Maybe this issue is more for the Akonadi package? At least from what I can

Processed: Re: Bug#951588: kontact: akonadi is not operational

Processing control commands: > tags -1 + moreinfo Bug #951588 [kontact] kontact: akonadi is not operational Added tag(s) moreinfo. > severity -1 important Bug #951588 [kontact] kontact: akonadi is not operational Severity set to 'important' from 'grave' -- 951588:

Bug#957574: marked as done (nas: ftbfs with GCC-10)

Your message dated Mon, 28 Dec 2020 21:48:40 + with message-id and subject line Bug#957574: fixed in nas 1.9.4-7 has caused the Debian Bug report #957574, regarding nas: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#978584: anyremote-doc: missing Breaks+Replaces: anyremote (<< 6.7.3-2)

Package: anyremote-doc Version: 6.7.3-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite

Bug#978583: libtrapperkeeper-filesystem-watcher-clojure: files in .jar don't follow the proper hierarchy

Package: libtrapperkeeper-filesystem-watcher-clojure Version: 1.2.2-1 Severity: grave Owner: po...@debian.org The .jar in this package contains the following .clj files: clj/ clj/puppetlabs/ clj/puppetlabs/trapperkeeper/ clj/puppetlabs/trapperkeeper/services/

Bug#976037: marked as done (ms-gsl's autopkg tests are broken by design)

Your message dated Mon, 28 Dec 2020 21:18:27 + with message-id and subject line Bug#976037: fixed in ms-gsl 3.1.0-4 has caused the Debian Bug report #976037, regarding ms-gsl's autopkg tests are broken by design to be marked as done. This means that you claim that the problem has been dealt

Bug#978343: marked as done (lincity: FTBFS: configure:14792: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

Your message dated Mon, 28 Dec 2020 21:03:43 + with message-id and subject line Bug#978343: fixed in lincity 1.13.1-15 has caused the Debian Bug report #978343, regarding lincity: FTBFS: configure:14792: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?) to be

Bug#978331: marked as done (libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)

Your message dated Mon, 28 Dec 2020 21:03:38 + with message-id and subject line Bug#978331: fixed in libpdf-builder-perl 3.021-1 has caused the Debian Bug report #978331, regarding libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 to be marked

Bug#978516: marked as done (openjdk-11-jre-dcevm: non-standard gcc/g++ used for build (gcc-9))

Your message dated Mon, 28 Dec 2020 20:48:51 + with message-id and subject line Bug#978516: fixed in openjdk-11-jre-dcevm 11.0.9+1-2 has caused the Debian Bug report #978516, regarding openjdk-11-jre-dcevm: non-standard gcc/g++ used for build (gcc-9) to be marked as done. This means that you

Processed: found 974797 in 1.6-1, block 974797 with 975931

Processing commands for cont...@bugs.debian.org: > found 974797 1.6-1 Bug #974797 {Done: Andreas Beckmann } [pocl] pocl: Please upgrade to llvm-toolchain-11 Bug #974823 {Done: Andreas Beckmann } [pocl] pocl: Please upgrade to llvm-toolchain-11 There is no source info for the package 'pocl' at

Bug#978560: marked as done (mediastreamer2: dropped pkgconfig file breaks kopete)

Your message dated Mon, 28 Dec 2020 20:19:47 + with message-id and subject line Bug#978560: fixed in mediastreamer2 1:4.4.21-2 has caused the Debian Bug report #978560, regarding mediastreamer2: dropped pkgconfig file breaks kopete to be marked as done. This means that you claim that the

Processed: Re: kalgebra: Output is always blank

Processing control commands: > tags -1 buster Bug #955567 [kalgebra] kalgebra: Output is always blank Added tag(s) buster. -- 955567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#955567: kalgebra: Output is always blank

Control: tags -1 buster Hi Charles, On 28-12-2020 20:51, Charles Samuels wrote: > On Monday, December 28, 2020 11:30:18 AM PST Paul Gevers wrote: >> I tried to reproduce this in current testing and for me it works. Is >> this issue still a problem for you? > > Yes it is still an issue (stable).

Bug#957732: marked as done (qtermwidget: ftbfs with GCC-10)

Your message dated Mon, 28 Dec 2020 21:07:15 +0100 with message-id <20e07c08-030f-d6cc-739c-13d75a456...@debian.org> and subject line Re: qtermwidget: ftbfs with GCC-10 has caused the Debian Bug report #957732, regarding qtermwidget: ftbfs with GCC-10 to be marked as done. This means that you

Bug#957732: qtermwidget: ftbfs with GCC-10

Version: 0.16.1-1 Hi, On Fri, 17 Apr 2020 11:09:35 + Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The > severity of this report will be raised before the bullseye release, > so nothing

Processed: owner 978516

Processing commands for cont...@bugs.debian.org: > owner 978516 tmanc...@debian.org Bug #978516 [openjdk-11-jre-dcevm] openjdk-11-jre-dcevm: non-standard gcc/g++ used for build (gcc-9) Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need

Bug#955567: kalgebra: Output is always blank

On Monday, December 28, 2020 11:30:18 AM PST Paul Gevers wrote: > wrote: > > KAlgebra shows nothing in its output screen. This only applies > > to the algebraic displays, the graphs and dictionary tabs seem > > to work fine. > > > > Reproduce: Enter any equation into the input text box and press

Bug#978315: marked as done (dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

Your message dated Mon, 28 Dec 2020 19:48:29 + with message-id and subject line Bug#978315: fixed in dasher 5.0.0~beta~repack2-2 has caused the Debian Bug report #978315, regarding dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This

Bug#957435: marked as done (libfabric: ftbfs with GCC-10)

Your message dated Mon, 28 Dec 2020 20:40:01 +0100 with message-id <5c9fb60e-8f45-b0ed-fddb-f4318d006...@debian.org> and subject line Re: libfabric: ftbfs with GCC-10 has caused the Debian Bug report #957435, regarding libfabric: ftbfs with GCC-10 to be marked as done. This means that you claim

Processed: Re: kalgebra: Output is always blank

Processing control commands: > notfound -1 4:20.08.0-1 Bug #955567 [kalgebra] kalgebra: Output is always blank Ignoring request to alter found versions of bug #955567 to the same values previously set -- 955567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955567 Debian Bug Tracking

Bug#955567: kalgebra: Output is always blank

Control: notfound -1 4:20.08.0-1 Hi Charles, On Thu, 02 Apr 2020 16:57:16 + (UTC) Charles Samuels wrote: > KAlgebra shows nothing in its output screen. This only applies > to the algebraic displays, the graphs and dictionary tabs seem > to work fine. > > Reproduce: Enter any equation into

Processed: cloning 978315, reassign -1 to gettext ..., severity of -1 is important, affects -1

Processing commands for cont...@bugs.debian.org: > clone 978315 -1 Bug #978315 [src:dasher] dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Bug 978315 cloned as bug 978580 > reassign -1 gettext Bug #978580 [src:dasher] dasher: FTBFS: dh_auto_test: error: make

Bug#978271: marked as done (inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#978387: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #978387, regarding inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be

Bug#978387: marked as done (runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility')

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#978271: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #978271, regarding runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for

Bug#978387: marked as done (runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility')

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#978387: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #978387, regarding runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for

Bug#977908: marked as done (mk-configure: Fails with 'Settings for gcc-10.2.1 is not available')

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#978387: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #978387, regarding mk-configure: Fails with 'Settings for gcc-10.2.1 is not available' to be marked as done. This means that

Bug#978387: marked as done (runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility')

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#977908: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #977908, regarding runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for

Bug#978271: marked as done (inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#978271: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #978271, regarding inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be

Bug#978271: marked as done (inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#977908: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #977908, regarding inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be

Bug#977908: marked as done (mk-configure: Fails with 'Settings for gcc-10.2.1 is not available')

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#978271: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #978271, regarding mk-configure: Fails with 'Settings for gcc-10.2.1 is not available' to be marked as done. This means that

Bug#977908: marked as done (mk-configure: Fails with 'Settings for gcc-10.2.1 is not available')

Your message dated Mon, 28 Dec 2020 19:19:57 + with message-id and subject line Bug#977908: fixed in mk-configure 0.35.really.0.33.0-1 has caused the Debian Bug report #977908, regarding mk-configure: Fails with 'Settings for gcc-10.2.1 is not available' to be marked as done. This means that

Bug#978097: marked as done (libcpu-features-dev: missing Breaks+Replaces: libvolk2-dev (<< 2.4.1-2 ???))

Your message dated Mon, 28 Dec 2020 18:33:27 + with message-id and subject line Bug#978097: fixed in cpu-features 0.6.0-3 has caused the Debian Bug report #978097, regarding libcpu-features-dev: missing Breaks+Replaces: libvolk2-dev (<< 2.4.1-2 ???) to be marked as done. This means that you

Processed: forcibly merging 978356 977844

Processing commands for cont...@bugs.debian.org: > forcemerge 978356 977844 Bug #978356 [src:libcxx-serial] libcxx-serial: FTBFS: dh_missing: error: missing files, aborting Bug #977844 [src:libcxx-serial] src:libcxx-serial: libcxx-serial FTBFS with new catkin (patch attached) Severity set to

Bug#975832: marked as done (python-aiosqlite: FTBFS: E: pybuild pybuild:353: build: plugin flit failed with: Not supported proxy scheme None)

Your message dated Tue, 29 Dec 2020 03:20:42 +0900 with message-id <9414a464016e60d09ec015e716bd0...@duckcorp.org> and subject line Re: python-aiosqlite: FTBFS: E: pybuild pybuild:353: build: plugin flit failed with: Not supported proxy scheme None has caused the Debian Bug report #975832,

Processed: src:rust-num-traits: fails to migrate to testing for too long: Depends on non-migrating rust-libm

Processing control commands: > close -1 0.2.14-1 Bug #978572 [src:rust-num-traits] src:rust-num-traits: fails to migrate to testing for too long: Depends on non-migrating rust-libm Marked as fixed in versions rust-num-traits/0.2.14-1. Bug #978572 [src:rust-num-traits] src:rust-num-traits: fails

Bug#978572: src:rust-num-traits: fails to migrate to testing for too long: Depends on non-migrating rust-libm

Source: rust-num-traits Version: 0.2.11-1+doctestfix Severity: serious Control: close -1 0.2.14-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync

Processed: src:scummvm: fails to migrate to testing for too long: FTBFS on armhf, mips64el and s390x

Processing control commands: > close -1 2.2.0+dfsg1-2 Bug #978570 [src:scummvm] src:scummvm: fails to migrate to testing for too long: FTBFS on armhf, mips64el and s390x Marked as fixed in versions scummvm/2.2.0+dfsg1-2. Bug #978570 [src:scummvm] src:scummvm: fails to migrate to testing for too

Bug#978571: xserver-xorg-video-amdgpu: FTBFS on mips64el, mipsel

package: src:xserver-xorg-video-amdgpu version: 19.1.0-2 severity: serious tags: ftbfs Hi, The latest upload of xserver-xorg-video-amdgpu to unstable fails on mips64el, mipsel: https://buildd.debian.org/status/package.php?p=xserver-xorg-video-amdgpu Cheers, Ivo

Bug#978570: src:scummvm: fails to migrate to testing for too long: FTBFS on armhf, mips64el and s390x

Source: scummvm Version: 2.1.2+dfsg1-1 Severity: serious Control: close -1 2.2.0+dfsg1-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 975492 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that

Bug#978567: src:godot: fails to migrate to testing for too long: FTBFS on mips64el

Source: godot Version: 3.2-stable-2 Severity: serious Tags: sid bullseye ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than

Bug#911587: marked as done (infnoise: busy-waits, using too much CPU)

Your message dated Mon, 28 Dec 2020 17:48:34 + with message-id and subject line Bug#911587: fixed in infnoise 0.3.1+git20190812+dfsg-1 has caused the Debian Bug report #911587, regarding infnoise: busy-waits, using too much CPU to be marked as done. This means that you claim that the problem

Processed: src:xmobar: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 0.36-2 Bug #978565 [src:xmobar] src:xmobar: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions xmobar/0.36-2. Bug #978565 [src:xmobar] src:xmobar: fails to migrate to testing for too long: autopkgtest regression

Bug#978565: src:xmobar: fails to migrate to testing for too long: autopkgtest regression

Source: xmobar Version: 0.33-1 Severity: serious Control: close -1 0.36-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 975472 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync

Processed: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

Processing control commands: > close -1 1.18.2-1 Bug #978564 [src:gst-plugins-bad1.0] src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating Marked as fixed in versions gst-plugins-bad1.0/1.18.2-1. Bug #978564 [src:gst-plugins-bad1.0]

Bug#978564: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

Source: gst-plugins-bad1.0 Version: 1.18.0-2 Severity: serious Control: close -1 1.18.2-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 976288 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that

Processed: [bts-link] source package src:golang-github-xenolf-lego

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > src:golang-github-xenolf-lego > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

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

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:bambootracker > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Bug#911587: infnoise: busy-waits, using too much CPU

Hi Axel, On Mon, 28 Dec 2020 09:29:04 +0100, Axel Beckert wrote: > Stephen Kitt wrote: > > Dear Maintainer, > > You're writing to yourself as "Dear Maintainer"? :-) I didn’t bother changing the reportbug template, and who knows the maintainer might not always be me ;-). > > Version 0.3 of

Bug#978411: marked as done (src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too long: maintainer built arch:all binary)

Your message dated Mon, 28 Dec 2020 17:04:20 + with message-id and subject line Bug#978411: fixed in golang-gopkg-lxc-go-lxc.v2 0.0+git20201012.d1943fb-2 has caused the Debian Bug report #978411, regarding src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too long: maintainer

Bug#963371: marked as done (isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

Your message dated Mon, 28 Dec 2020 17:04:32 + with message-id and subject line Bug#963371: fixed in isoquery 3.2.4-1 has caused the Debian Bug report #963371, regarding isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means that

Bug#978226: marked as done (perl6-zef: FTBFS: Errors while processing: rakudo raku-getopt-long raku-tap-harness prove6 sbuild-build-depends-main-dummy)

Your message dated Mon, 28 Dec 2020 17:04:46 + with message-id and subject line Bug#978226: fixed in prove6 0.0.12-3 has caused the Debian Bug report #978226, regarding perl6-zef: FTBFS: Errors while processing: rakudo raku-getopt-long raku-tap-harness prove6

Bug#978365: [Pkg-fonts-devel] Bug#978365: fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 'master_ufo/Inter.designspace' -> 'master_ufo/instance_ufo/Inter-Thin.ufo': Compiling UFO failed

Here's a bunch more context on this failure: https://github.com/rsms/inter/issues/184 https://github.com/googlefonts/fontmake/issues/581 https://github.com/rsms/inter/issues/200 https://github.com/rsms/inter/issues/210 I'm surprised the fonts-inter package is still using fontmake directly

Bug#958105: marked as done (ferm: v2.5 broke @ipfilter(), resulting in deferred=ARRAY(0x55b7a9219368) errors)

Your message dated Mon, 28 Dec 2020 16:48:36 + with message-id and subject line Bug#958105: fixed in ferm 2.5.1-1 has caused the Debian Bug report #958105, regarding ferm: v2.5 broke @ipfilter(), resulting in deferred=ARRAY(0x55b7a9219368) errors to be marked as done. This means that you

Processed: Reopening as the bug is still not fixed

Processing control commands: > reopen -1 Bug #975943 {Done: =?utf-8?q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= } [raspi-firmware] raspi-firmware: arm_64bit is missing and linux-image-arm64 unbootable 'reopen' may be inappropriate when a bug has been closed with a version; all fixed

Bug#975943: Reopening as the bug is still not fixed

Control: reopen -1 Turns out that DPKG_MAINTSCRIPT_ARCH can also have the value 'all' and then it still does the wrong thing. # aptitude reinstall udev ... Processing triggers for initramfs-tools (0.139) ... update-initramfs: Generating /boot/initrd.img-5.10.0-trunk-arm64 latest_kernel:

Processed: reassign 978226 to prove6, affects 978226

Processing commands for cont...@bugs.debian.org: > reassign 978226 prove6 Bug #978226 [src:perl6-zef] perl6-zef: FTBFS: Errors while processing: rakudo raku-getopt-long raku-tap-harness prove6 sbuild-build-depends-main-dummy Bug reassigned from package 'src:perl6-zef' to 'prove6'. No longer

Bug#978226: perl6-zef: FTBFS: Errors while processing: rakudo raku-getopt-long raku-tap-harness prove6 sbuild-build-depends-main-dummy

On Saturday, 26 December 2020 22:40:58 CET Lucas Nussbaum wrote: > > rakudo-helper.pl: Reinstalling all perl6 modules ... > > (1/3) reinstall: raku-tap-harness > > (2/3) reinstall: prove6 > > ===SORRY!=== Error while compiling > >

Bug#978348: marked as done (ipp-usb: FTBFS: src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use int32(err) (type int32) as type _Ctype_int in argument to _Cfunc_libusb_strerror)

Your message dated Mon, 28 Dec 2020 16:20:50 + with message-id and subject line Bug#978348: fixed in ipp-usb 0.9.15-1 has caused the Debian Bug report #978348, regarding ipp-usb: FTBFS: src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use int32(err) (type int32) as type

Bug#978351: requests: FTBFS: AttributeError: 'LookupDict' object has no attribute '__name__'

Hello Lucas, many thanks for the report! On Sat, 26 Dec 2020 23:08:21 +0100 Lucas Nussbaum wrote: > Source: requests > Version: 2.25.0+dfsg-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201226 ftbfs-bullseye > > Hi, > > During a rebuild of

Bug#978560: mediastreamer2: dropped pkgconfig file breaks kopete

Source: mediastreamer2 Version: 1:4.4.21-1 Severity: serious tags: patch Hello, kopete does use pkgconfig to find the mediastreamer2, and the new version with the cmake switch dropped the pkgconfig installation. I did craft a patch to install the pkgconfig file in cmake builds too (as it is

Bug#895037: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Hi, On Thu, Dec 10, 2020 at 03:08:00PM +, Simon McVittie wrote: > On Thu, 10 Dec 2020 at 14:37:21 +, Mike Gabriel wrote: > > On Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote: > > > We're running into the freeze of bullseye soon. The first bug I checked > > > is still only severity

Bug#970808: python3-venv is gone

Dear Matthias, Can you please explain the problem you reported on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970808 ? python3-venv seems to be present in buster, bullseye and sid. Best regards, Aivar

Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

On 2020-12-28 16:09:13 +0100, Vincent Lefevre wrote: > After the upgrade, I now get in my logs: > > Dec 28 16:00:01 zira CRON[2661963]: PAM unable to dlopen(pam_unix.so): > /lib/security/pam_unix.so: cannot open shared object file: No such file or > directory > Dec 28 16:00:01 zira

Bug#973848: hardware acceleration

Hi! I can confirm that adding --use-gl=desktop to /etc/chromium.d/default-flags makes hardware acceleration work (again) with chromium 87.0.4280.88-0.3 on unstable (on two systems with integrated intel graphics), according to chrome://gpu. NB: to get accelerated video decoding I had to

Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

Package: libpam-modules Version: 1.4.0-1 Severity: grave Justification: renders package unusable After the upgrade, I now get in my logs: Dec 28 16:00:01 zira CRON[2661963]: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file: No such file or directory

Bug#977824: marked as done (CI fails with PHPUnit 9)

Your message dated Mon, 28 Dec 2020 14:39:20 + with message-id and subject line Bug#977824: fixed in php-imagick 3.4.4-4.2 has caused the Debian Bug report #977824, regarding CI fails with PHPUnit 9 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#933948: marked as done (courier-mta randomly stops, cannot restart or start services, it just appears started, but it exists)

Your message dated Mon, 28 Dec 2020 14:34:01 + with message-id and subject line Bug#933948: fixed in courier 1.0.14-1 has caused the Debian Bug report #933948, regarding courier-mta randomly stops, cannot restart or start services, it just appears started, but it exists to be marked as done.

Bug#978411: src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too long: maintainer built arch:all binary

Hi Paul, On 27/12/2020 07:12, Paul Gevers wrote: > Source: golang-gopkg-lxc-go-lxc.v2 > Version: 0.0+git20190625.f4822c6-1 > Severity: serious > Control: close -1 0.0+git20201012.d1943fb-1 > Tags: sid bullseye pending > User: release.debian@packages.debian.org > Usertags: out-of-sync > >

Bug#971040: Fix available

Hi, on https://extensions.gnome.org/extension/690/easyscreencast/ I stumled over user's 'johncorso' comment pointing to a fix: > Working on Debian bullseye/sid with GNOME 3.38.2. > Thanks to Ian2020 for all the work. > Pull: https://github.com/EasyScreenCast/EasyScreenCast/pull/276 > Fork:

Bug#977824: php-imagick: diff for NMU version 3.4.4-4.2

Hi Ondřej, Le Mon, Dec 28, 2020 at 02:55:26PM +0100, Ondřej Surý a écrit : > David, feel free to upload directly. Thanks for the explicit and quick acknowledgment, rescheduled to 0-day. Regards David signature.asc Description: PGP signature

Bug#973848: security update of chromium in Debian stable?

On Mon, 28 Dec 2020, Jan Luca Naumann wrote: I have got a successful buster build half an hour ago :) Yay! As soon as [1] is fixed or at least worked around (so we do not release a version with a regression), I think we could do the update. Do you have your build available anywhere?

Bug#977000: marked as done (python3-apt: dak crashes after security update)

Your message dated Mon, 28 Dec 2020 13:53:34 + with message-id and subject line Bug#977000: fixed in python-apt 1.8.4.3 has caused the Debian Bug report #977000, regarding python3-apt: dak crashes after security update to be marked as done. This means that you claim that the problem has been

Bug#961491: marked as done (CVE-2020-10936: Security flaws in setuid wrappers)

Your message dated Mon, 28 Dec 2020 13:53:39 + with message-id and subject line Bug#961491: fixed in sympa 6.2.40~dfsg-1+deb10u1 has caused the Debian Bug report #961491, regarding CVE-2020-10936: Security flaws in setuid wrappers to be marked as done. This means that you claim that the

Bug#952428: marked as done (sympa: CVE-2020-9369: Security flaws in CSRF prevention)

Your message dated Mon, 28 Dec 2020 13:53:39 + with message-id and subject line Bug#952428: fixed in sympa 6.2.40~dfsg-1+deb10u1 has caused the Debian Bug report #952428, regarding sympa: CVE-2020-9369: Security flaws in CSRF prevention to be marked as done. This means that you claim that

Bug#977824: php-imagick: diff for NMU version 3.4.4-4.2

David, feel free to upload directly. Ondřej -- Ondřej Surý (He/Him) > On 28. 12. 2020, at 14:48, David Prévot wrote: > > Control: tags 977824 + pending > > Dear maintainer, > > I've prepared an NMU for php-imagick (versioned as 3.4.4-4.2) and > uploaded it to DELAYED/5. Please feel free to

Bug#978514: marked as done (gringo: non-standard gcc/g++ used for build (gcc-9))

Your message dated Mon, 28 Dec 2020 13:50:04 + with message-id and subject line Bug#978514: fixed in gringo 5.4.1-3 has caused the Debian Bug report #978514, regarding gringo: non-standard gcc/g++ used for build (gcc-9) to be marked as done. This means that you claim that the problem has

Bug#974011: xmille: Incorrect license/copyright for xmille

On Sat, Dec 26, 2020 at 12:25:37PM -0800, Keith Packard wrote: > Steven Robbins writes: >... > > If you are NOT interested in maintaining the package, then I can continue. > > Unless Adrian wants to do it? ;-) > > I'm easy; three is even better than two? >... I am just a normal user enjoying

  1   2   >