Processed: retitle 961116 to gnome-shell-extension-suspend-button: Not suitable for next release: Does not work with gnome 3.36

Processing commands for cont...@bugs.debian.org: > retitle 961116 gnome-shell-extension-suspend-button: Not suitable for next > release: Does not work with gnome 3.36 Bug #961116 [gnome-shell-extension-suspend-button] gnome-shell-extension-suspend-button: Does not work with gnome 3.36 Changed

Bug#960752: marked as done (FTBFS on IPv6-only hosts)

Your message dated Thu, 28 May 2020 05:18:50 + with message-id and subject line Bug#960752: fixed in cockpit 220-1 has caused the Debian Bug report #960752, regarding FTBFS on IPv6-only hosts to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#961415: marked as done (symfony: CVE-2020-5275 CVE-2020-5274 CVE-2020-5255)

Your message dated Thu, 28 May 2020 04:33:44 + with message-id and subject line Bug#961415: fixed in symfony 4.4.8-1 has caused the Debian Bug report #961415, regarding symfony: CVE-2020-5275 CVE-2020-5274 CVE-2020-5255 to be marked as done. This means that you claim that the problem has

Bug#943135: marked as done (numba: Python2 removal in sid/bullseye)

Your message dated Thu, 28 May 2020 04:18:56 + with message-id and subject line Bug#943135: fixed in numba 0.48.0-2 has caused the Debian Bug report #943135, regarding numba: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#961691: linux-image-5.6.0-1-amd64: System hangs all the time

Package: src:linux Version: 5.6.7-1 Severity: grave Justification: renders package unusable Dear Maintainer, Since upgrade of 2020-05-18 system started to hang all the time without any reason, forcing me to reboot computer each time loosing my work. -- Package-specific info: ** Version: Linux

Bug#921926: marked as done (pki-base: Does not work with Java 11)

Your message dated Wed, 27 May 2020 23:33:36 + with message-id and subject line Bug#921926: fixed in dogtag-pki 10.9.0~a1-1 has caused the Debian Bug report #921926, regarding pki-base: Does not work with Java 11 to be marked as done. This means that you claim that the problem has been dealt

Bug#920725: marked as done (pki-base-java: Depends on openjdk-8-jre-headless which will not be in buster)

Your message dated Wed, 27 May 2020 23:33:36 + with message-id and subject line Bug#920725: fixed in dogtag-pki 10.9.0~a1-1 has caused the Debian Bug report #920725, regarding pki-base-java: Depends on openjdk-8-jre-headless which will not be in buster to be marked as done. This means that

Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel

Paul, Shall I close this one 'by hand'? Or will it get closed by migrating quantlib-swig? I just close the other one (#956830) that was at the start of this by hand. Best, Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#956830: marked as done (quantlib-swig: FTBFS on mipsel)

Your message dated Wed, 27 May 2020 18:12:41 -0500 with message-id <24270.62441.723302.256...@rob.eddelbuettel.com> and subject line Re: Bug#956830: quantlib-swig: FTBFS on mipsel has caused the Debian Bug report #956830, regarding quantlib-swig: FTBFS on mipsel to be marked as done. This means

Bug#948087: future of aufs in Debian.

On Wed, 27 May 2020 at 14:33, Noah Meyerhans wrote: > Docker no longer users aufs by default, though, having switched to > overlayfs some time ago. I'm sure we could get them to drop the > Recommends if we're considering getting rid of it. This is something I'd been considering for quite a

Bug#961684: marked as done (lintian: exits with error: Can't use an undefined value as a HASH reference)

Your message dated Wed, 27 May 2020 22:18:49 + with message-id and subject line Bug#961684: fixed in lintian 2.77.1 has caused the Debian Bug report #961684, regarding lintian: exits with error: Can't use an undefined value as a HASH reference to be marked as done. This means that you claim

Processed: Bug#961684 marked as pending in lintian

Processing control commands: > tag -1 pending Bug #961684 [lintian] lintian: exits with error: Can't use an undefined value as a HASH reference Added tag(s) pending. -- 961684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961684 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#961684: marked as pending in lintian

Control: tag -1 pending Hello, Bug #961684 in lintian 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#961684: lintian: exits with error: Can't use an undefined value as a HASH reference

Package: lintian Version: 2.77.0 Severity: grave Justification: renders package unusable Hello, while attempting to check a just built package within my sid pbuilder-managed chroot enviroment, I see that lintian is no longer working. Please note that lintian/2.76.0 was working fine in the same

Bug#948087: future of aufs in Debian.

On Tue, May 26, 2020 at 05:10:10PM +0300, Adrian Bunk wrote: > > Adrian filed a rc bug in November 2019 which received no maintainer > > response, however the package was not autoremoved from testing due to aufs > > and aufs-tools being considered a "key packages" due to high popcon. This > >

Bug#867775: marked as done (golang-github-optiopay-kafka FTBFS: FAIL: TestProduceRequest)

Your message dated Wed, 27 May 2020 21:03:35 + with message-id and subject line Bug#867775: fixed in golang-github-optiopay-kafka 2.1.1-1 has caused the Debian Bug report #867775, regarding golang-github-optiopay-kafka FTBFS: FAIL: TestProduceRequest to be marked as done. This means that you

Bug#961591: marked as done (r-bioc-graph: autopkgtest regression)

Your message dated Wed, 27 May 2020 20:37:16 + with message-id and subject line Bug#961591: fixed in r-bioc-graph 1.66.0-2 has caused the Debian Bug report #961591, regarding r-bioc-graph: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt

Bug#961591: [RFS] r-bioc-graph

On Thu, 28 May 2020, 01:43 Dylan Aïssi, wrote: > Hi, > > Le mer. 27 mai 2020 à 20:04, Nilesh Patra a écrit : > > > > The second test (needing the library) failed on gitlab-ci, w/o adding > r-cran-xml and r-cran-runit, possible because this doesn't pick up depends > from test-depends. > > This

Bug#928813: libapache2-mod-jk: Jk can not find any configured worker

Am 27.05.20 um 21:54 schrieb Thorsten Glaser: [...] > Thank you. Please also take care of buster. I will take care of Buster eventually. Markus signature.asc Description: OpenPGP digital signature

Bug#961591: [RFS] r-bioc-graph

Hi, Le mer. 27 mai 2020 à 20:04, Nilesh Patra a écrit : > > The second test (needing the library) failed on gitlab-ci, w/o adding > r-cran-xml and r-cran-runit, possible because this doesn't pick up depends > from test-depends. > This passed on my local machine though. Since I wanted to be

Bug#928813: libapache2-mod-jk: Jk can not find any configured worker

Markus Koschany dixit: >The mods-available directory is correct. Both conf and load file have to >be installed into it but the file naming is wrong. httpd-jk.conf should >be jk.conf. OK, so the way it is in stretch is correct. >Just renaming the file should be sufficient. That plus renaming

Bug#931654: marked as done (node-json3: json3 is no more maintained)

Your message dated Wed, 27 May 2020 19:16:57 + with message-id and subject line Bug#931653: Removed package(s) from unstable has caused the Debian Bug report #931654, regarding node-json3: json3 is no more maintained to be marked as done. This means that you claim that the problem has been

Bug#938860: marked as done (yagtd: Python2 removal in sid/bullseye)

Your message dated Wed, 27 May 2020 19:15:11 + with message-id and subject line Bug#961626: Removed package(s) from unstable has caused the Debian Bug report #938860, regarding yagtd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#902255: marked as done (llvm-toolchain-6.0: unicode non free license)

Your message dated Wed, 27 May 2020 19:16:27 + with message-id and subject line Bug#916837: Removed package(s) from unstable has caused the Debian Bug report #902255, regarding llvm-toolchain-6.0: unicode non free license to be marked as done. This means that you claim that the problem has

Bug#936928: marked as done (libtuxcap: Python2 removal in sid/bullseye)

Your message dated Wed, 27 May 2020 19:14:43 + with message-id and subject line Bug#961625: Removed package(s) from unstable has caused the Debian Bug report #936928, regarding libtuxcap: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#928813: marked as done (libapache2-mod-jk: Jk can not find any configured worker)

Your message dated Wed, 27 May 2020 18:49:47 + with message-id and subject line Bug#928813: fixed in libapache-mod-jk 1:1.2.46-2 has caused the Debian Bug report #928813, regarding libapache2-mod-jk: Jk can not find any configured worker to be marked as done. This means that you claim that

Bug#928813: marked as pending in libapache-mod-jk

Control: tag -1 pending Hello, Bug #928813 in libapache-mod-jk 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#928813 marked as pending in libapache-mod-jk

Processing control commands: > tag -1 pending Bug #928813 [libapache2-mod-jk] libapache2-mod-jk: Jk can not find any configured worker Added tag(s) pending. -- 928813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928813 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: tagging 936244

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

Processed: Bug#961320 marked as pending in npm

Processing control commands: > tag -1 pending Bug #961320 [npm] backported version needs newer node-dot-prop to work Added tag(s) pending. -- 961320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#961320: marked as pending in npm

Control: tag -1 pending Hello, Bug #961320 in npm 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: https://salsa.debian.org/js-team/npm/-/commit/38be7079d06ec8b1624acdfc0176ad779883aee7

Bug#961591: [RFS] r-bioc-graph

On Wed, 27 May 2020, 23:28 Dylan Aïssi, wrote: > Hi Nilesh, > > Le mer. 27 mai 2020 à 19:36, Nilesh Patra a écrit : > > > > Hi, > > Currently r-bioc-graph has failing tests, and has RC bug - #961591 filed > against this. > > I have fixed this and pushed my changes to the team repo here[1]. > >

Bug#961591: [RFS] r-bioc-graph

Hi Nilesh, Le mer. 27 mai 2020 à 19:36, Nilesh Patra a écrit : > > Hi, > Currently r-bioc-graph has failing tests, and has RC bug - #961591 filed > against this. > I have fixed this and pushed my changes to the team repo here[1]. > Need review and sponsorship. > Thanks for #961591 !!! I don't

Bug#961591: [RFS] r-bioc-graph

Hi, Currently r-bioc-graph has failing tests, and has RC bug - #961591 filed against this. I have fixed this and pushed my changes to the team repo here[1]. Need review and sponsorship. [1]: https://salsa.debian.org/r-pkg-team/r-bioc-graph

Bug#928813: libapache2-mod-jk: Jk can not find any configured worker

Am 27.05.20 um 17:28 schrieb Thorsten Glaser: [...] > In stretch, an “a2enmod jk” will enable mods-available/jk.conf > and make things work. > > From reading the changelog, you wanted to “Install new httpd-jk.conf > file which follows Apache 2.4 syntax”, but the directory is wrong; > these files

Bug#960571: marked as done (Missing dependency on fontconfig)

Your message dated Wed, 27 May 2020 16:21:24 + with message-id and subject line Bug#960571: fixed in rst2pdf 0.97-2 has caused the Debian Bug report #960571, regarding Missing dependency on fontconfig to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#960571 marked as pending in pdfposter

Processing control commands: > tag -1 pending Bug #960571 [rst2pdf] Missing dependency on fontconfig Added tag(s) pending. -- 960571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#960571: marked as pending in pdfposter

Control: tag -1 pending Hello, Bug #960571 in pdfposter 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#960402: marked as done (mwrap FTBFS with bison 3.6.1)

Your message dated Wed, 27 May 2020 15:48:57 + with message-id and subject line Bug#960402: fixed in mwrap 0.33-10 has caused the Debian Bug report #960402, regarding mwrap FTBFS with bison 3.6.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#955316: marked as done (r-cran-svglite autopkgtest fails: Error: symbol font)

Your message dated Wed, 27 May 2020 15:49:45 + with message-id and subject line Bug#955316: fixed in r-cran-svglite 1.2.3-3 has caused the Debian Bug report #955316, regarding r-cran-svglite autopkgtest fails: Error: symbol font to be marked as done. This means that you claim that the

Processed: Reopen

Processing commands for cont...@bugs.debian.org: > reopen 960571 Bug #960571 {Done: Sandro Tosi } [rst2pdf] Missing dependency on fontconfig Bug reopened Ignoring request to alter fixed versions of bug #960571 to the same values previously set > thanks Stopping processing here. Please contact

Bug#960571: rst2pdf: Bad dependency on "fontconfing"

Package: rst2pdf Version: 0.97-1 Followup-For: Bug #960571 The last upload clearly was not tested, as it now depends on the misspelled package "fontconfing". New package is uninstallable. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500,

Processed: Re: libapache2-mod-jk: Jk can not find any configured worker

Processing control commands: > severity -1 serious Bug #928813 [libapache2-mod-jk] libapache2-mod-jk: Jk can not find any configured worker Severity set to 'serious' from 'important' > notfound -1 1:1.2.46-0+deb9u1 Bug #928813 [libapache2-mod-jk] libapache2-mod-jk: Jk can not find any

Bug#960402: marked as pending in mwrap

Control: tag -1 pending Hello, Bug #960402 in mwrap 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#960402 marked as pending in mwrap

Processing control commands: > tag -1 pending Bug #960402 [src:mwrap] mwrap FTBFS with bison 3.6.1 Added tag(s) pending. -- 960402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#959675: libgrpc++1: endless looping with default settings

Processing control commands: > tags -1 +pending Bug #959675 [libgrpc++1] libgrpc++1: endless looping with default settings Added tag(s) pending. -- 959675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#959675: libgrpc++1: endless looping with default settings

Control: tags -1 +pending On Wed, May 27, 2020 at 4:42 PM Thomas Goirand wrote: > Any progress on this? I've been watching this bug activity, and > nothing's happening. I'm worried for my packages removal in Bullseye > (ie: most of OpenStack...). Quoting the package tracker: "grpc is marked for

Bug#959675: libgrpc++1: endless looping with default settings

Hi Benjamin, Any progress on this? I've been watching this bug activity, and nothing's happening. I'm worried for my packages removal in Bullseye (ie: most of OpenStack...). Cheers, Thomas Goirand (zigo)

Bug#959818: marked as done (libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl)

Your message dated Wed, 27 May 2020 14:35:06 + with message-id and subject line Bug#959818: fixed in libcatmandu-perl 1.2012-1 has caused the Debian Bug report #959818, regarding libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl to be marked as done. This means that you claim that

Processed: Bug#959818 marked as pending in libcatmandu-perl

Processing control commands: > tag -1 pending Bug #959818 [libcatmandu-perl] libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl Added tag(s) pending. -- 959818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959818 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#959818: marked as pending in libcatmandu-perl

Control: tag -1 pending Hello, Bug #959818 in libcatmandu-perl 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#961584: lxc-stop fails with exit code 1

El 26/5/20 a las 23:35, Antonio Terceiro escribió: > is there an easy/documented way of reproducing the salsa ci environment > (i.e. lxc working under docker) locally? Attached is a Dockerfile. It should be sufficient to reproduce the problem. Changing the FROM statement from debian:unstable to

Bug#961377: raspi3-firmware: recent stable update causes non-booting systems

Hi Gunnar, >VERY GOOD CATCH! Thanks a lot for this. I'm pushing it to Git right you’re welcome. > > https://salsa.debian.org/debian/raspi-firmware/-/commit/2bf38f62de0514c2759f2c33d147c935e4d044bf Note this caused unbootable RPi 3B+ systems, so it was actually a severe regression wrt. the

Bug#961505: marked as done (failed mips64el build of flint 2.5.2-22)

Your message dated Wed, 27 May 2020 13:18:45 + with message-id and subject line Bug#961505: fixed in flint 2.5.2-23 has caused the Debian Bug report #961505, regarding failed mips64el build of flint 2.5.2-22 to be marked as done. This means that you claim that the problem has been dealt

Bug#961501: remmina is calling home for update notifications

Hi all, patch is on its way. Progress can be tracked on our gitlab [0] Any feedback is much appreciated as it'll easy the resolution of the bug. Thanks! Kind regards Antenore - [0] https://gitlab.com/Remmina/Remmina/-/merge_requests/2066

Processed (with 5 errors): Raise severity

Processing commands for cont...@bugs.debian.org: > severity 960558 grave Bug #960558 [cyrus-common] cyrus-common: lmtpd aborts when compiled with optimisation and FORTIFY_SOURCE flags Severity set to 'grave' from 'important' > tags 960558 patch Bug #960558 [cyrus-common] cyrus-common: lmtpd

Bug#961647: marked as done (akonadi: FTBFS on armel: missing -latomic)

Your message dated Wed, 27 May 2020 10:18:32 + with message-id and subject line Bug#961647: fixed in akonadi 4:20.04.1-2 has caused the Debian Bug report #961647, regarding akonadi: FTBFS on armel: missing -latomic to be marked as done. This means that you claim that the problem has been

Bug#961646: marked as done (node-deep-for-each breaks node-grunt-webpack)

Your message dated Wed, 27 May 2020 10:19:22 + with message-id and subject line Bug#961646: fixed in node-deep-for-each 3.0.0-2 has caused the Debian Bug report #961646, regarding node-deep-for-each breaks node-grunt-webpack to be marked as done. This means that you claim that the problem

Bug#961591: Bug#961592: r-bioc-gviz: autopkgtest regression

On Wed, May 27, 2020 at 11:22:34AM +0200, Dylan Aïssi wrote: > > But, regarding https://bugs.debian.org/961591 , I have no idea how to fix it. I have no idea either. What about seeking help at upstream? Kind regards Andreas. -- http://fam-tille.de

Bug#961592: marked as done (r-bioc-gviz: autopkgtest regression)

Your message dated Wed, 27 May 2020 10:04:09 + with message-id and subject line Bug#961592: fixed in r-bioc-gviz 1.32.0+dfsg-2 has caused the Debian Bug report #961592, regarding r-bioc-gviz: autopkgtest regression to be marked as done. This means that you claim that the problem has been

Bug#961581: marked as done (pbcopper: ftbfs on ppc64el)

Your message dated Wed, 27 May 2020 10:00:10 + with message-id and subject line Bug#961581: fixed in pbcopper 1.6.0+dfsg-2 has caused the Debian Bug report #961581, regarding pbcopper: ftbfs on ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#960219: marked as done (pbcopper FTBFS on 32bit: int128 not available)

Your message dated Wed, 27 May 2020 10:00:10 + with message-id and subject line Bug#960219: fixed in pbcopper 1.6.0+dfsg-2 has caused the Debian Bug report #960219, regarding pbcopper FTBFS on 32bit: int128 not available to be marked as done. This means that you claim that the problem has

Bug#959409: marked as done (pbcopper breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared object file: No such file or directory)

Your message dated Wed, 27 May 2020 10:00:10 + with message-id and subject line Bug#959409: fixed in pbcopper 1.6.0+dfsg-2 has caused the Debian Bug report #959409, regarding pbcopper breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared object file: No such file or directory

Bug#961647: akonadi: FTBFS on armel: missing -latomic

Hey, Whoo I'm quite impressed to have two different solutions that fast! Thank you both for proposing me solutions. You made my day! > The easy workaround is in debian/rules: > > ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc sh4)) > export DEB_LDFLAGS_MAINT_APPEND =

Processed: Bug#961646 marked as pending in node-deep-for-each

Processing control commands: > tag -1 pending Bug #961646 [node-deep-for-each] node-deep-for-each breaks node-grunt-webpack Added tag(s) pending. -- 961646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#961646: marked as pending in node-deep-for-each

Control: tag -1 pending Hello, Bug #961646 in node-deep-for-each 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#961647: akonadi: FTBFS on armel: missing -latomic

On Wed, May 27, 2020 at 11:02:50AM +0200, Sandro Knauß wrote: > Hey, > > > This is caused by a missing -latmoic. See also > > https://buildd.debian.org/status/fetch.php?pkg=akonadi=armel=4%3A20 > > .04.1-1=1590553675=0 > > thanks for this fast scan and also proposing a solution. But I have no >

Processed: Bug#959558 marked as pending in sphinx

Processing control commands: > tag -1 pending Bug #959558 [python3-sphinx] case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip' Added tag(s) pending. -- 959558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959558 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#959558: marked as pending in sphinx

Control: tag -1 pending Hello, Bug #959558 in sphinx 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#961647: akonadi: FTBFS on armel: missing -latomic

Hi On 2020-05-27 11:02:50 +0200, Sandro Knauß wrote: > > This is caused by a missing -latmoic. See also > > https://buildd.debian.org/status/fetch.php?pkg=akonadi=armel=4%3A20 > > .04.1-1=1590553675=0 > > thanks for this fast scan and also proposing a solution. But I have no > example > of how

Processed: Re: Bug#959558: case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip'

Processing control commands: > reassign -1 python3-sphinx 2.4.3-2 Bug #959558 [src:case] case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip' Bug reassigned from package 'src:case' to 'python3-sphinx'. No longer marked as found in versions case/1.5.3+dfsg-3. Ignoring request to

Bug#959558: case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip'

Control: reassign -1 python3-sphinx 2.4.3-2 On Sun, May 03, 2020 at 02:47:46PM +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > [...] > > AttributeError: 'tuple' object has no attribute 'lstrip' I

Bug#961592: r-bioc-gviz: autopkgtest regression

Hi, Le mer. 27 mai 2020 à 11:12, Andreas Tille a écrit : > > Ahhh, its new to me that pkg-r-autopkgtest does more than just > loading the library. Hmmm, Dylan, do you have any idea besides > patching the test suite? > I am testing my patch that skip the test if "BSgenome.Hsapiens.UCSC.hg19" is

Bug#961592: r-bioc-gviz: autopkgtest regression

Hi Graham, On Wed, May 27, 2020 at 11:13:07AM +0200, Graham Inggs wrote: > > Note this is not run-unit-test, this is pkg-r-autopkgtest. Ahhh, its new to me that pkg-r-autopkgtest does more than just loading the library. Hmmm, Dylan, do you have any idea besides patching the test suite? Kind

Bug#961592: r-bioc-gviz: autopkgtest regression

Hi Andreas On Wed, 27 May 2020 at 10:55, Andreas Tille wrote: > That's strange. The autopkgtest should not run. r-bioc-gviz source > has > > debian/tests/control_unused > > to deactivate its test. Has anything changed in debci that fetches > anything that looks like a test script? Note

Bug#961647: akonadi: FTBFS on armel: missing -latomic

Hey, > This is caused by a missing -latmoic. See also > https://buildd.debian.org/status/fetch.php?pkg=akonadi=armel=4%3A20 > .04.1-1=1590553675=0 thanks for this fast scan and also proposing a solution. But I have no example of how I need to modify cmake to end up having -latomic for armel

Bug#961592: r-bioc-gviz: autopkgtest regression

Hi Graham, On Tue, May 26, 2020 at 02:37:04PM +0200, Graham Inggs wrote: > Since the upload of 1.32.0+dfsg-1, r-bioc-gviz has been failing its > own autopkgtests [1]. This now prevents the migration of r-base. > I've copied what I hope is the relevant part of the log below. That's strange.

Bug#961357: marked as done (r-cran-etm: autopktest failure)

Your message dated Wed, 27 May 2020 08:36:24 + with message-id and subject line Bug#961357: fixed in r-cran-etm 1.1-2 has caused the Debian Bug report #961357, regarding r-cran-etm: autopktest failure to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#961490: fwupd: version in stable too old, no updates possible

On Wed, 2020-05-27 at 02:58 +0200, Matthias Klumpp wrote: > Am Di., 26. Mai 2020 um 20:24 Uhr schrieb : > > > -Original Message- > > > From: Ansgar > > > Sent: Tuesday, May 26, 2020 8:01 AM > > > To: Steffen Schreiber; 961...@bugs.debian.org > > > Subject: Bug#961490: fwupd: version in

Bug#961636: [debian-mysql] Bug#961636: src:galera-3: fails to migrate to testing for too long: ftbfs on armel

Thanks for the report! There are new upstream releases of both Galera 3 and Galera 4, and I intend to upload them and work with any remaining FTBFS issues in coming weeks.

Bug#961485: marked as done (r-cran-sp: autopkgtest regression)

Your message dated Wed, 27 May 2020 07:49:50 + with message-id and subject line Bug#961485: fixed in r-cran-sp 1:1.4-2-2 has caused the Debian Bug report #961485, regarding r-cran-sp: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with.

Bug#961649: php-horde-gollem: CVE-2020-8034

Source: php-horde-gollem Version: 3.0.12-5 Severity: grave Tags: security upstream Control: found -1 3.0.12-3 Hi, The following vulnerability was published for php-horde-gollem. CVE-2020-8034[0]: | Gollem before 3.0.13, as used in Horde Groupware Webmail Edition | 5.2.22 and other products, is

Processed: php-horde-gollem: CVE-2020-8034

Processing control commands: > found -1 3.0.12-3 Bug #961649 [src:php-horde-gollem] php-horde-gollem: CVE-2020-8034 Marked as found in versions php-horde-gollem/3.0.12-3. -- 961649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961649 Debian Bug Tracking System Contact ow...@bugs.debian.org

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

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 Adrian diff -Nru doit-0.31.1/debian/changelog doit-0.31.1/debian/changelog

Processed: doit: diff for NMU version 0.31.1-3.3

Processing control commands: > tags 954148 + patch Bug #954148 [src:doit] src:doit: autopkgtest requires packages outside the Debian archive Added tag(s) patch. > tags 954148 + pending Bug #954148 [src:doit] src:doit: autopkgtest requires packages outside the Debian archive Added tag(s)

Bug#961647: akonadi: FTBFS on armel: missing -latomic

Source: akonadi Version: 4:20.04.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) akonadi failed to build on armel: | cd /<>/obj-arm-linux-gnueabi/src/server && /usr/bin/cmake -E cmake_link_script

Bug#961581: pbcopper: ftbfs on ppc64el

On Wed, May 27, 2020 at 09:53:44AM +1200, Michael Hudson-Doyle wrote: > > Thanks. I think a fixed simde has been uploaded now, so my patch might not > be needed at all... OK, while pbcopper is doing another cycle in new queue I commited pbcopper(master) $ git diff diff --git a/debian/changelog