Bug#972744: marked as done (openstack-debian-images: bullseye: /updates -> -security)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Mon, 02 Nov 2020 07:52:05 + with message-id and subject line Bug#972744: fixed in openstack-debian-images 1.49 has caused the Debian Bug report #972744, regarding openstack-debian-images: bullseye: /updates -> -security to be marked as done. This means that you claim that

Bug#973588: Update from pari 2.11 to 2.13 breaks giac compilation

2020-11-01 Thread Julien Puydt
Package: libpari-dev Version: 2.13.0-2 Severity: grave The last pari upload broke giac on amd64, arm64 and mipsel : https://buildd.debian.org/status/fetch.php?pkg=giac=amd64=1.6.0.25%2Bdfsg1-2%2Bb1=1604135053=0 The failing test on amd64 is a segfault. I could check that running the failing

Bug#972745: marked as pending in openstack-meta-packages

2020-11-01 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #972745 in openstack-meta-packages 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#972745 marked as pending in openstack-meta-packages

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #972745 [openstack-tempest-ci] openstack-tempest-ci: bullseye: /updates -> -security Added tag(s) pending. -- 972745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972745 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#972744: marked as pending in openstack-debian-images

2020-11-01 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #972744 in openstack-debian-images 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#972744 marked as pending in openstack-debian-images

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #972744 [openstack-debian-images] openstack-debian-images: bullseye: /updates -> -security Added tag(s) pending. -- 972744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972744 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: gnome-shell-pomodoro: No JS module 'tweener' found in search path

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #971704 [gnome-shell-pomodoro] gnome-shell-pomodoro: No JS module 'tweener' found in search path Severity set to 'grave' from 'normal' -- 971704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971704 Debian Bug Tracking System Contact

Processed: your mail

2020-11-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 973522 by 973467 Bug #973522 [autopkgtest] autopkgtest-virt-qemu does not support i386 uefi boot 973522 was blocked by: 973571 973522 was not blocking any bugs. Added blocking bug(s) of 973522: 973467 > retitle 973467 vmdb2 tries to install

Processed: tagging 973069

2020-11-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 973069 + pending Bug #973069 [src:mgba] mgba FTBFS: imported target "libzip::zipcmp" references the file "/usr/bin/zipcmp" but this file does not exist Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#972778: marked as done (zbar ftbfs with python3.9)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Mon, 02 Nov 2020 02:57:43 + with message-id and subject line Bug#972778: fixed in zbar 0.23.1-2 has caused the Debian Bug report #972778, regarding zbar ftbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#973149: marked as done (kwin: FTBFS: egl_dmabuf.cpp:97:9: error: ‘EGL_TEXTURE_Y_XUXV_WL’ was not declared in this scope)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Mon, 02 Nov 2020 01:06:06 + with message-id and subject line Bug#973149: fixed in kwin 4:5.19.5-2 has caused the Debian Bug report #973149, regarding kwin: FTBFS: egl_dmabuf.cpp:97:9: error: ‘EGL_TEXTURE_Y_XUXV_WL’ was not declared in this scope to be marked as done. This

Bug#973499: marked as done (rust-onig: autopkgtest fails on i386/armhf with new bindgen/onig-sys)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Mon, 02 Nov 2020 00:18:36 + with message-id and subject line Bug#973499: fixed in rust-onig-sys 69.5.1-2 has caused the Debian Bug report #973499, regarding rust-onig: autopkgtest fails on i386/armhf with new bindgen/onig-sys to be marked as done. This means that you claim

Processed: tagging 971147

2020-11-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 971147 - bullseye Bug #971147 {Done: Sylvestre Ledru } [src:rust-onig-sys] rust-onig-sys: FTBFS: unsatisfiable build-dependencies: librust-cexpr-0.3+default-dev (>= 0.3.3-~~), librust-clang-sys-0.28+clang-6-0-dev,

Bug#973235: marked as done (golang-github-c-bata-go-prompt: FTBFS: src/github.com/pkg/term/termios/ioctl.go:8:2: cannot find package "golang.org/x/sys/unix")

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 1 Nov 2020 22:26:21 +0100 with message-id <34f84d89-020c-cb62-c67c-6a5c3607e...@micard.lu> and subject line Bug fixed has caused the Debian Bug report #973235, regarding golang-github-c-bata-go-prompt: FTBFS: src/github.com/pkg/term/termios/ioctl.go:8:2: cannot find

Bug#972808: marked as done (cura-engine FTBFS: error: ‘find_if’ is not a member of ‘std’)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 21:20:09 + with message-id and subject line Bug#972808: fixed in cura-engine 1:4.7.1-2 has caused the Debian Bug report #972808, regarding cura-engine FTBFS: error: ‘find_if’ is not a member of ‘std’ to be marked as done. This means that you claim that the

Processed (with 5 errors): Re: [Pkg-rust-maintainers] Bug#973387: does debian's libclang-dev support static linking?

2020-11-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > Severity 973387 normal Bug #973387 [rust-bindgen] rust-bindgen: autopkg test failures for new featuresets. Severity set to 'normal' from 'serious' > Retitle 973387 rust-bindgen cannot be built with "static" feature. Bug #973387 [rust-bindgen]

Bug#972974: marked as done (clamav-freshclam start faild.)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 20:39:49 + with message-id and subject line Bug#972974: fixed in clamav 0.103.0+dfsg-2 has caused the Debian Bug report #972974, regarding clamav-freshclam start faild. to be marked as done. This means that you claim that the problem has been dealt with.

Bug#963853: marked as done (clamav: FTBFS on IPv6-only environments)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 20:39:49 + with message-id and subject line Bug#963853: fixed in clamav 0.103.0+dfsg-2 has caused the Debian Bug report #963853, regarding clamav: FTBFS on IPv6-only environments to be marked as done. This means that you claim that the problem has been

Bug#973560: src:xnnpack: fails to migrate to testing for too long: FTBFS on armhf

2020-11-01 Thread Paul Gevers
Source: xnnpack Version: 0.0~git20200425.54f5917-4 Severity: serious Control: close -1 0.0~git20200827.37297a6-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

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

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.7.7.2-1 Bug #973559 [src:rhino] src:rhino: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions rhino/1.7.7.2-1. Bug #973559 [src:rhino] src:rhino: fails to migrate to testing for too long: autopkgtest regression

Processed: src:xnnpack: fails to migrate to testing for too long: FTBFS on armhf

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.0~git20200827.37297a6-1 Bug #973560 [src:xnnpack] src:xnnpack: fails to migrate to testing for too long: FTBFS on armhf Marked as fixed in versions xnnpack/0.0~git20200827.37297a6-1. Bug #973560 [src:xnnpack] src:xnnpack: fails to migrate to testing for

Bug#973559: src:rhino: fails to migrate to testing for too long: autopkgtest regression

2020-11-01 Thread Paul Gevers
Source: rhino Version: 1.7.7.1-1 Severity: serious Control: close -1 1.7.7.2-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 970501 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are

Processed: src:r-cran-openmx: fails to migrate to testing for too long: autopkgtest regression

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.18.1-1 Bug #973558 [src:r-cran-openmx] src:r-cran-openmx: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r-cran-openmx/2.18.1-1. Bug #973558 [src:r-cran-openmx] src:r-cran-openmx: fails to migrate to testing

Bug#973558: src:r-cran-openmx: fails to migrate to testing for too long: autopkgtest regression

2020-11-01 Thread Paul Gevers
Source: r-cran-openmx Version: 2.17.4-1 Severity: serious Control: close -1 2.18.1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 971681 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are

Processed: Forward

2020-11-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 963853 https://bugzilla.clamav.net/show_bug.cgi?id=12633 Bug #963853 [src:clamav] clamav: FTBFS on IPv6-only environments Set Bug forwarded-to-address to 'https://bugzilla.clamav.net/show_bug.cgi?id=12633'. > End of message, stopping

Bug#971199: marked as done (texext: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 19:07:03 + with message-id and subject line Bug#971199: fixed in texext 0.6.6-2 has caused the Debian Bug report #971199, regarding texext: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 to be

Bug#972333: marked as done (llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid old size)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 1 Nov 2020 19:22:59 +0100 with message-id <3bb0c82b-ff45-8a31-e55d-c66f5dcec...@debian.org> and subject line fixed has caused the Debian Bug report #972333, regarding llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid old size to be marked as done. This means that you

Bug#972318: marked as done (FTBFS on ppc64el)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 1 Nov 2020 19:23:50 +0100 with message-id <55f1337b-52a4-8382-a724-c4443f2b0...@debian.org> and subject line fixed has caused the Debian Bug report #972318, regarding FTBFS on ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: fixed

2020-11-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 972318 1:10.0.1-8 Bug #972318 [src:llvm-toolchain-10] FTBFS on ppc64el Marked as fixed in versions llvm-toolchain-10/1:10.0.1-8. > thanks Stopping processing here. Please contact me if you need assistance. -- 972318:

Processed: fixed

2020-11-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 972333 1:11.0.0-4 Bug #972333 [src:llvm-toolchain-11] llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid old size Marked as fixed in versions llvm-toolchain-11/1:11.0.0-4. > thanks Stopping processing here. Please contact me if you

Bug#942973: marked as done (dipy: Python2 removal in sid/bullseye)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 16:00:09 + with message-id and subject line Bug#936400: fixed in dipy 1.2.0-1 has caused the Debian Bug report #936400, regarding dipy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#936400: marked as done (dipy: Python2 removal in sid/bullseye)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 16:00:09 + with message-id and subject line Bug#936400: fixed in dipy 1.2.0-1 has caused the Debian Bug report #936400, regarding dipy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966730: marked as done (dipy: Unversioned Python removal in sid/bullseye)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 16:00:09 + with message-id and subject line Bug#942973: fixed in dipy 1.2.0-1 has caused the Debian Bug report #942973, regarding dipy: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#966730: marked as done (dipy: Unversioned Python removal in sid/bullseye)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 16:00:09 + with message-id and subject line Bug#936400: fixed in dipy 1.2.0-1 has caused the Debian Bug report #936400, regarding dipy: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#936400: marked as done (dipy: Python2 removal in sid/bullseye)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 16:00:09 + with message-id and subject line Bug#942973: fixed in dipy 1.2.0-1 has caused the Debian Bug report #942973, regarding dipy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#942973: marked as done (dipy: Python2 removal in sid/bullseye)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 16:00:09 + with message-id and subject line Bug#942973: fixed in dipy 1.2.0-1 has caused the Debian Bug report #942973, regarding dipy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#972793: marked as done (hg-git: autopkgtest needs update for new version of dulwich: lots of deprecation *warnings*)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 15:03:37 + with message-id and subject line Bug#972793: fixed in hg-git 0.9.0-2 has caused the Debian Bug report #972793, regarding hg-git: autopkgtest needs update for new version of dulwich: lots of deprecation *warnings* to be marked as done. This

Bug#957062: bygfoot: ftbfs with GCC-10

2020-11-01 Thread Markus Koschany
Control: tags -1 pending Dear maintainer, I've prepared an NMU for bygfoot (versioned as 2.3.2-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Markus diff -Nru bygfoot-2.3.2/debian/bygfoot.desktop bygfoot-2.3.2/debian/bygfoot.desktop

Processed: Re: bygfoot: ftbfs with GCC-10

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #957062 [src:bygfoot] bygfoot: ftbfs with GCC-10 Added tag(s) pending. -- 957062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#973543: nvidia-cuda-toolkit: CVE-2020-5991

2020-11-01 Thread Salvatore Bonaccorso
Source: nvidia-cuda-toolkit Version: 10.2.89-5 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for nvidia-cuda-toolkit. I have no further details apart what is in [1],

Bug#973507: libsis-jhdf5-java: incorrect license text for source/c/jni/

2020-11-01 Thread Andreas Tille
Hi, argh, I misinterpretet your mail - I'll upload a fixed version to new in a couple of minutes. Kind regards Andreas. On Sun, Nov 01, 2020 at 03:05:06PM +0100, Andreas Tille wrote: > Hi Sean, > > at first thanks a lot for accepting the package and not requiring it to > do a new cycle

Bug#973507: libsis-jhdf5-java: incorrect license text for source/c/jni/

2020-11-01 Thread Andreas Tille
Hi Sean, at first thanks a lot for accepting the package and not requiring it to do a new cycle through new. That's very convenient since it enables us to fix the bug with the source-only upload. I'm just building a package with fixed copyright. Also thanks a lot for all your other ftpmaster

Processed: qtox autopkgtest fails: stderr: CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:44 (message)

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > block 972278 by -1 Bug #972278 [release.debian.org] transition: qtbase-opensource-src 972278 was blocked by: 972178 972175 972160 972176 972677 972157 972179 972354 972355 973538 973461 972163 973436 972166 972158 973539 972155 973458 972156 972154 957436 972177

Bug#973540: qtox autopkgtest fails: stderr: CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:44 (message)

2020-11-01 Thread Dmitry Shachnev
Source: qtox Version: 1.17.2-1 Severity: serious User: debian-qt-...@lists.debian.org Usertags: qt5.15 Control: block 972278 by -1 Dear Maintainer, qtox autopkgtest failed when run against Qt 5.15 from unstable: https://ci.debian.net/data/autopkgtest/testing/amd64/q/t/7855235/log.gz The test

Processed: qcustomplot autopkgtest fails: stderr: CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:44 (message)

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > block 972278 by -1 Bug #972278 [release.debian.org] transition: qtbase-opensource-src 972278 was blocked by: 972355 957436 973458 972676 972157 972155 972175 972177 972677 972160 973461 972163 972156 972354 972176 973538 972179 972154 973436 972158 972166 972178

Bug#973539: qcustomplot autopkgtest fails: stderr: CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:44 (message)

2020-11-01 Thread Dmitry Shachnev
Source: qcustomplot Version: 2.0.1+dfsg1-2 Severity: serious User: debian-qt-...@lists.debian.org Usertags: qt5.15 Control: block 972278 by -1 Dear Maintainer, qcustomplot autopkgtest failed when run against Qt 5.15 from unstable:

Processed: poppler autopkgtest fails: error: ‘template class QLinkedList’ is deprecated: Use std::list instead

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > block 972278 by -1 Bug #972278 [release.debian.org] transition: qtbase-opensource-src 972278 was blocked by: 972175 972157 973458 972177 957436 972166 972155 972163 972676 973461 972354 972178 972156 972179 972160 972176 972355 972158 972677 973436 972154 972278

Bug#973538: poppler autopkgtest fails: error: ‘template class QLinkedList’ is deprecated: Use std::list instead

2020-11-01 Thread Dmitry Shachnev
Source: poppler Version: 20.09.0-2 Severity: serious User: debian-qt-...@lists.debian.org Usertags: qt5.15 Control: block 972278 by -1 Dear Maintainer, poppler autopkgtest failed when run against Qt 5.15 from unstable:

Bug#972793: marked as pending in hg-git

2020-11-01 Thread Jelmer Vernooij
Control: tag -1 pending Hello, Bug #972793 in hg-git 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#973359: marked as done (booth: autopkgtest timed out on armhf and i386)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 13:48:21 + with message-id and subject line Bug#973359: fixed in booth 1.0-205-gc9e90fe-2 has caused the Debian Bug report #973359, regarding booth: autopkgtest timed out on armhf and i386 to be marked as done. This means that you claim that the problem

Processed: Bug#972793 marked as pending in hg-git

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #972793 [src:hg-git] hg-git: autopkgtest needs update for new version of dulwich: lots of deprecation *warnings* Added tag(s) pending. -- 972793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972793 Debian Bug Tracking System Contact

Bug#972317: marked as done (FTBFS on ppc64el)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 12:04:37 + with message-id and subject line Bug#972317: fixed in llvm-toolchain-11 1:11.0.0-4 has caused the Debian Bug report #972317, regarding FTBFS on ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#972802: rust-webpki-roots is marked for autoremoval from testing

2020-11-01 Thread Geert Stappers
On Sun, Nov 01, 2020 at 04:39:36AM +, Debian testing autoremoval watch wrote: > rust-webpki-roots 0.20.0-1 is marked for autoremoval from testing on > 2020-11-22 > > It is affected by these RC bugs: > 972802: rust-webpki-roots: duplicates ca-certificates, remove from Debian? >

Bug#973068: marked as done (undercover-el: FTBFS: tests failed)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 11:05:12 + with message-id and subject line Bug#973068: fixed in undercover-el 0.7.0-2 has caused the Debian Bug report #973068, regarding undercover-el: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt

Bug#973526: libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test"

2020-11-01 Thread Sebastian Ramacher
Source: libzeep Version: 5.0.5-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org libzeep fails to build on the arch: all buildds with test failures: | >>> building http-test | cd test; ./http-test |

Bug#973525: libzeep: configure: error: could not find the tools necessary to build the documentation

2020-11-01 Thread Sebastian Ramacher
Source: libzeep Version: 5.0.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org libzeep fails to build when building the architecture specific packages: | checking for doxygen... no | checking for

Bug#965269: marked as done (ruby-gon: ftbfs with rails 6 in experimental)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 10:49:16 + with message-id and subject line Bug#965269: fixed in ruby-gon 6.4.0-1 has caused the Debian Bug report #965269, regarding ruby-gon: ftbfs with rails 6 in experimental to be marked as done. This means that you claim that the problem has been

Bug#973190: marked as done (geneweb: FTBFS: ocamlc.opt: OCaml has been configured with -force-safe-string: -unsafe-string is not available.)

2020-11-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Nov 2020 10:03:22 + with message-id and subject line Bug#973190: fixed in geneweb 6.08+git20181019+dfsg-3 has caused the Debian Bug report #973190, regarding geneweb: FTBFS: ocamlc.opt: OCaml has been configured with -force-safe-string: -unsafe-string is not

Processed: Re: Bug#942814: libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #942814 [libhibernate-validator-java] libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies Severity set to 'important' from 'serious' -- 942814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942814 Debian Bug

Bug#942814: libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies

2020-11-01 Thread Paul Gevers
Control: severity -1 important Hi Emmanuel, On 29-10-2020 10:12, Paul Gevers wrote: > On 26-09-2020 15:31, Markus Koschany wrote: >> I will switch pdfsam to use libhibernator-validator4-java now but I can >> only address this problem when libsejda-commons-java has been approved >> by the ftp

Processed: Re: openstack-pkg-tools: uses python2

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #973520 [src:openstack-pkg-tools] openstack-pkg-tools: uses python2 Ignoring request to alter tags of bug #973520 to the same tags previously set > severity -1 important Bug #973520 [src:openstack-pkg-tools] openstack-pkg-tools: uses python2

Bug#973520: openstack-pkg-tools: uses python2

2020-11-01 Thread Gianfranco Costamagna
control: tags -1 pending control: severity -1 important After having another look, I don't think serious is appropriate as severity, and FYI I just committed the changes on git, will not make an upload just for this bug, but feel free to do it :) thanks G.

Bug#973520: marked as pending in openstack-pkg-tools

2020-11-01 Thread Gianfranco Costamagna
Control: tag -1 pending Hello, Bug #973520 in openstack-pkg-tools 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#973520 marked as pending in openstack-pkg-tools

2020-11-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #973520 [src:openstack-pkg-tools] openstack-pkg-tools: uses python2 Added tag(s) pending. -- 973520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#973520: openstack-pkg-tools: uses python2

2020-11-01 Thread Gianfranco Costamagna
Source: openstack-pkg-tools Version: 114 Severity: serious tags: patch Hello, diff -Nru openstack-pkg-tools-113/build-tools/pkgos-generate-snapshot openstack-pkg-tools-113ubuntu1/build-tools/pkgos-generate-snapshot --- openstack-pkg-tools-113/build-tools/pkgos-generate-snapshot 2019-11-20

Processed: your mail

2020-11-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 973068 https://github.com/undercover-el/undercover.el/issues/62 Bug #973068 [src:undercover-el] undercover-el: FTBFS: tests failed Set Bug forwarded-to-address to 'https://github.com/undercover-el/undercover.el/issues/62'. > thanks