Bug#866629: debian-installer: Installer showes Debootstrap Error debian stretch live installation

On Thu, 6 Jul 2017 00:35:21 +0530 Prahlad Yeri wrote: > Can confirm this bug on the live installer - tried both XFCE and LXDE > versions. > > Never expected such goof up on a debian stable version! I agree it was a let down and frustrating. > Granted that its just released, but we do go through

Processed: Makes planet not work at all

Processing commands for cont...@bugs.debian.org: > severity 845987 serious Bug #845987 [planet-venus] planet-venus: Fails with html5lib 0.9-1 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 845987: https://bugs.de

Bug#867651: ruby-rubymail: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-rubymail Version: 1.1.0-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#867653: ruby-license-finder: FTBFS: ERROR: Test "ruby2.3" failed: /etc/ssl/certs/T?RKTRUST_Elektronik_Sertifika_Hizmet_Sa?lay?c?s?_H5.pem (No such file or directory)

Source: ruby-license-finder Version: 2.1.2-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867655: ruby-gemnasium-gitlab-service: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: @connection.request(request)

Source: ruby-gemnasium-gitlab-service Version: 0.2.6-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part

Bug#867656: ruby-mixlib-install: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: res = http.request(request)

Source: ruby-mixlib-install Version: 1.1.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867650: berkshelf: FTBFS: ERROR: Test "ruby2.3" failed: Did you mean? Berkshelf::NullFormatter (NameError)

Source: berkshelf Version: 4.3.5-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Did

Bug#867654: ruby-omniauth-crowd: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: http.request(req)

Source: ruby-omniauth-crowd Version: 2.2.3-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867649: ruby-flowdock: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: resp = self.class.delete(api_url(path), :basic_auth => {:username => @api_token, :password => ''}, :headers => headers)

Source: ruby-flowdock Version: 0.7.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867648: jruby-maven-plugins: FTBFS: RailsService.java:[26,20] variable session might not have been initialized

Source: jruby-maven-plugins Version: 1.1.5+ds1-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

debian-bugs-rc@lists.debian.org

Source: ruby-rest-client Version: 1.8.0-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867644: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output[2]).to match('Found 2 errors. Giving up')

Source: ruby-puppet-syntax Version: 2.2.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867642: capistrano: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(out).to match(/\bCapistrano Version\b/)

Source: capistrano Version: 3.4.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867645: ruby-influxdb: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: http.request(req)

Source: ruby-influxdb Version: 0.2.3-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867646: gist: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: http.request request

Source: gist Version: 4.5.0-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Fail

Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

Source: schleuder Version: 3.1.1-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#867404: marked as done (python3-exam: incorrect dependencies)

Your message dated Sat, 08 Jul 2017 04:18:44 + with message-id and subject line Bug#867404: fixed in exam 0.10.5-2 has caused the Debian Bug report #867404, regarding python3-exam: incorrect dependencies to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#867404: marked as pending

tag 867404 pending thanks Hello, Bug #867404 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/exam.git/commit/?id=2f38f98 --- commit 2f38f983d6a7f46e41e26

Processed: Bug#867404 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 867404 pending Bug #867404 [python3-exam] python3-exam: incorrect dependencies Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86

Bug#867631: marked as done (python-nanomsg: missing build dependency on python3-all-dev)

Your message dated Sat, 08 Jul 2017 01:18:51 + with message-id and subject line Bug#867631: fixed in python-nanomsg 1.0-2 has caused the Debian Bug report #867631, regarding python-nanomsg: missing build dependency on python3-all-dev to be marked as done. This means that you claim that the pr

Bug#867631: marked as pending

tag 867631 pending thanks Hello, Bug #867631 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/python-nanomsg.git/commit/?id=8499c45 --- commit 8499c45b2bf

Processed: Bug#867631 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 867631 pending Bug #867631 [src:python-nanomsg] python-nanomsg: missing build dependency on python3-all-dev Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867631: https://bugs.debian.or

Bug#867633: python-confluent-kafka: missing build dependency on python3-all-dev

Source: python-confluent-kafka Version: 0.9.4-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-confluent-kafka.html ... x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -O2 -specs=/usr/share/dpkg/no-p

Bug#867481: [Python-modules-team] Bug#867481: Bug#867481: celery FTBFS: test_recursive runs forever with python 3.6

On July 7, 2017 8:16:01 PM EDT, Brian May wrote: >Adrian Bunk writes: > >>> * sphinx_celery >> >> https://tracker.debian.org/pkg/sphinx-celery > >Looks like there is only a Python3 version of the package... It's DPMT maintained, so you could add the python version. Scott K

Bug#867632: python-oslo.rootwrap FTBFS with python 3.6 as supported version

Source: python-oslo.rootwrap Version: 5.1.0-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-oslo.rootwrap.html ... == FAIL: oslo_rootwrap.tests.test_rootwrap.DaemonC

Bug#867631: python-nanomsg: missing build dependency on python3-all-dev

Source: python-nanomsg Version: 1.0-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-nanomsg.html ... I: pybuild base:184: python3.6 setup.py test running test running egg_info writing nanomsg.egg-info/PKG-INFO writing dependency_link

Bug#867324: marked as done (haskell-hgettext FTBFS: Expecting one more argument to `H.Module')

Your message dated Sat, 08 Jul 2017 00:19:00 + with message-id and subject line Bug#867324: fixed in haskell-hgettext 0.1.30-15 has caused the Debian Bug report #867324, regarding haskell-hgettext FTBFS: Expecting one more argument to `H.Module' to be marked as done. This means that you claim

Bug#867481: [Python-modules-team] Bug#867481: celery FTBFS: test_recursive runs forever with python 3.6

Adrian Bunk writes: >> * sphinx_celery > > https://tracker.debian.org/pkg/sphinx-celery Looks like there is only a Python3 version of the package... -- Brian May

Bug#867630: python-oslo.service FTBFS with python 3.6 as supported version

Source: python-oslo.service Version: 1.16.0-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-oslo.service.html ... ===> Testing with python3.6 (python3) ... == FAIL: o

Bug#867629: python-proliantutils FTBFS with python 3.6 as supported version

Source: python-proliantutils Version: 2.1.11-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-proliantutils.html ... == FAIL: proliantutils.tests.ilo.test_firmware_co

Bug#867628: python-muranoclient FTBFS with python 3.6 as supported version

Source: python-muranoclient Version: 0.11.1-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-muranoclient.html ... == FAIL: unittest2.loader._FailedTest.muranoclient.

Bug#864565: chromium-shell: Couldn't mmap v8 natives data file, status code is 1

tag 864565 +patch thanks hi, the chromium-shell binary is not supposed to be installed in /usr/bin but rather /usr/lib/chromium. debian/chromium-shell.install pushes it into /usr/bin at the moment. The v8 natives file referred to is /usr/lib/chromium/natives_blob.bin, other than that /usr/lib/ch

Processed: Re: Bug#864565: chromium-shell: Couldn't mmap v8 natives data file, status code is 1

Processing commands for cont...@bugs.debian.org: > tag 864565 +patch Bug #864565 [chromium-shell] chromium-shell: Couldn't mmap v8 natives data file, status code is 1 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 864565: https://bugs.debian.

Bug#867627: python-mox3 FTBFS with python 3.6 as supported version

Source: python-mox3 Version: 0.14.0-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-mox3.html ... == FAIL: mox3.tests.test_mox.RegexTest.testReprWithFlags mox3.tests.

Bug#867626: python-json-patch FTBFS with python 3.6 as supported version

Source: python-json-patch Version: 1.19-4 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-json-patch.html ... set -e ; for pyvers in 2.7 3.6 3.5; do \ PYTHONPATH=/build/1st/python-json-patch-1.19 python$pyvers ./tests.py ; \ do

Bug#866710: marked as done (golang-golang-x-tools FTBFS with gccgo)

Your message dated Fri, 07 Jul 2017 23:03:57 + with message-id and subject line Bug#866710: fixed in golang-golang-x-tools 1:0.0~git20170707.0.bce9606b+ds-1 has caused the Debian Bug report #866710, regarding golang-golang-x-tools FTBFS with gccgo to be marked as done. This means that you cl

Bug#867260: marked as done (FTBFS: not compatible with recent haskell-src-exts)

Your message dated Fri, 07 Jul 2017 22:34:02 + with message-id and subject line Bug#867260: fixed in hothasktags 0.3.8-1 has caused the Debian Bug report #867260, regarding FTBFS: not compatible with recent haskell-src-exts to be marked as done. This means that you claim that the problem has

Bug#866710: Pending fixes for bugs in the golang-go.tools package

tag 866710 + pending thanks Some bugs in the golang-go.tools package are closed in revision 13daba7747e5a45deebe473d73f4750ea702166f in branch 'master' by Anthony Fok The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-go.tools.git/commit/?id=13daba7 Commit messag

Processed: Pending fixes for bugs in the golang-go.tools package

Processing commands for cont...@bugs.debian.org: > tag 866710 + pending Bug #866710 [src:golang-golang-x-tools] golang-golang-x-tools FTBFS with gccgo Ignoring request to alter tags of bug #866710 to the same tags previously set > thanks Stopping processing here. Please contact me if you need ass

Bug#867532: marked as done (cacti: CVE-2017-10970: XSS vulnerability via link.php)

Your message dated Fri, 07 Jul 2017 21:03:55 + with message-id and subject line Bug#867532: fixed in cacti 1.1.12+ds1-1 has caused the Debian Bug report #867532, regarding cacti: CVE-2017-10970: XSS vulnerability via link.php to be marked as done. This means that you claim that the problem ha

Bug#863969: marked as done (ncurses-term: fails to upgrade from 'sid' - trying to overwrite /usr/share/terminfo/d/dvtm)

Your message dated Fri, 07 Jul 2017 20:49:42 + with message-id and subject line Bug#863969: fixed in ncurses 6.0+20170701-1 has caused the Debian Bug report #863969, regarding ncurses-term: fails to upgrade from 'sid' - trying to overwrite /usr/share/terminfo/d/dvtm to be marked as done. Thi

Bug#867609: python-dmidecode: stop linking with libxml2mod

On Fri, Jul 07, 2017 at 03:25:29PM -0400, Sandro Tosi wrote: > control: tags -1 -patch > > On Fri, Jul 7, 2017 at 2:39 PM, Adrian Bunk wrote: > > The attached patch copies the two functions used from libxml2mod > > instead of linking with libxml2mod. > > this seems wrong. Less wrong than before

Bug#867609: python-dmidecode: stop linking with libxml2mod

control: tags -1 -patch On Fri, Jul 7, 2017 at 2:39 PM, Adrian Bunk wrote: > The attached patch copies the two functions used from libxml2mod > instead of linking with libxml2mod. this seems wrong. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/Sa

Processed: Re: Bug#867609: python-dmidecode: stop linking with libxml2mod

Processing control commands: > tags -1 -patch Bug #867609 [python-dmidecode] python-dmidecode: stop linking with libxml2mod Removed tag(s) patch. -- 867609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#867510: marked as done (klaus: missing build dependency on python3-setuptools)

Your message dated Fri, 07 Jul 2017 19:04:23 + with message-id and subject line Bug#867510: fixed in klaus 1.2.1-3 has caused the Debian Bug report #867510, regarding klaus: missing build dependency on python3-setuptools to be marked as done. This means that you claim that the problem has bee

Bug#865303: Java JNI crashes post CVE-2017-1000364 fixes post 4.9.30-2+deb9u2

I am experiencing a related issue which is caused by calling the JNI JVM init from python. Steps to reproduce: 1. cd /usr/lib/x86_64-linux-gnu 2. sudo ln -s libpython3.5m.a libpython3.5.a 3. sudo ln -s libpython3.5m.so libpython3.5.so 4. python3 -m virtualenv -p python3 venv3 5. source venv3/bin/

Bug#867610: python3-libvhdi: Missing python3 interpreter depends

Package: python3-libvhdi Version: 20170223-1 Severity: serious Tags: patch Justification: Policy 3.5 python3-libvhdi requires a python3 interpreter to work, but does not have any dependency on an interpreter due to an incorrect substitution variable. Patch attached. As an added bonus, it would b

Bug#867609: python-dmidecode: stop linking with libxml2mod

Package: python-dmidecode Version: 3.12.2-3 Severity: serious Tags: patch buster sid python-libxml2 contains the following change: -/usr/lib/python2.7/dist-packages/libxml2mod.so +/usr/lib/python2.7/dist-packages/libxml2mod.x86_64-linux-gnu.so This makes python-dmidecode FTBFS since it wants to l

Bug#866662: marked as done (golang-gopkg-mcuadros-go-syslog.v2 FTBFS: FAIL: rfc6587_test.go:48: FormatSuite.TestRFC6587_GetSplitBadSplit)

Your message dated Fri, 07 Jul 2017 18:03:49 + with message-id and subject line Bug#82: fixed in golang-gopkg-mcuadros-go-syslog.v2 2.2.1-1 has caused the Debian Bug report #82, regarding golang-gopkg-mcuadros-go-syslog.v2 FTBFS: FAIL: rfc6587_test.go:48: FormatSuite.TestRFC6587_GetSp

Processed: Pending fixes for bugs in the golang-gopkg-mcuadros-go-syslog.v2 package

Processing commands for cont...@bugs.debian.org: > tag 82 + pending Bug #82 [src:golang-gopkg-mcuadros-go-syslog.v2] golang-gopkg-mcuadros-go-syslog.v2 FTBFS: FAIL: rfc6587_test.go:48: FormatSuite.TestRFC6587_GetSplitBadSplit Added tag(s) pending. > thanks Stopping processing here. Plea

Bug#866662: Pending fixes for bugs in the golang-gopkg-mcuadros-go-syslog.v2 package

tag 82 + pending thanks Some bugs in the golang-gopkg-mcuadros-go-syslog.v2 package are closed in revision 3741227bd26e087f631a801f3774b48f461fc15a in branch 'master' by Dr. Tobias Quathamer The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-gopkg-mcuadros-go-

Bug#867581: libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report)

Control: found -1 3.5.8-5 Control: severity -1 serious On 2017-07-07 Catalin Marinas wrote: > Package: libgnutls30 > Version: 3.5.8-5+deb9u1 [...] > Unrelated gnome-terminal or xfce4-terminal crashing when significant output > (e.g. running 'yes'; apparently because of the corruption of the encry

Processed: Re: Bug#867581: libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report)

Processing control commands: > found -1 3.5.8-5 Bug #867581 {Done: Andreas Metzler } [libgnutls30] libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report) Marked as found in versions gnutls28/3.5.8-5. > severity -1 serious Bug #867581 {Done:

Bug#866564: bind9: CVE-2017-3142 CVE-2017-3143

We thank you for the great job! -- Rogerio Bastos PoP-BA/RNP

Bug#867581: marked as done (libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report))

Your message dated Fri, 7 Jul 2017 19:22:50 +0200 with message-id <20170707172250.syainpyqkttzh...@argenau.bebt.de> and subject line Re: Bug#867581: libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report) has caused the Debian Bug report #8675

Bug#838974: marked as done (python-3to2: FTBFS: AssertionError: 'print(*args)\n\n' != 'print *args\n\n')

Your message dated Fri, 07 Jul 2017 17:19:31 + with message-id and subject line Bug#867264: Removed package(s) from unstable has caused the Debian Bug report #838974, regarding python-3to2: FTBFS: AssertionError: 'print(*args)\n\n' != 'print *args\n\n' to be marked as done. This means that y

Bug#866564: bind9: CVE-2017-3142 CVE-2017-3143

Hi On Fri, Jul 07, 2017 at 09:42:05AM -0300, rogeriobas...@pop-ba.rnp.br wrote: > Hi, > > This bug is marked as fixed in versions bind9/1:9.9.5.dfsg-9+deb8u12, > bind9/1:9.10.3.dfsg.P4-12.3+deb9u1 but they are not available in security > repository. > Is there anything holding it ? The reason

Bug#865664: marked as done (golang-github-microcosm-cc-bluemonday FTBFS: dh_auto_test fails)

Your message dated Fri, 07 Jul 2017 17:04:32 + with message-id and subject line Bug#865664: fixed in golang-github-microcosm-cc-bluemonday 0.0~git20161202.0.e797637-1 has caused the Debian Bug report #865664, regarding golang-github-microcosm-cc-bluemonday FTBFS: dh_auto_test fails to be mark

Bug#865664: Pending fixes for bugs in the golang-github-microcosm-cc-bluemonday package

tag 865664 + pending thanks Some bugs in the golang-github-microcosm-cc-bluemonday package are closed in revision 0124e497f1f1ec19371a183fce545f46db952f0b in branch 'master' by Dr. Tobias Quathamer The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-microcos

Processed: Pending fixes for bugs in the golang-github-microcosm-cc-bluemonday package

Processing commands for cont...@bugs.debian.org: > tag 865664 + pending Bug #865664 [src:golang-github-microcosm-cc-bluemonday] golang-github-microcosm-cc-bluemonday FTBFS: dh_auto_test fails Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 8

Bug#867595: nfs-kernel-server: nfsd freezes if underlying ext4 file system becomes full

Package: nfs-kernel-server Version: 1:1.2.8-9 Severity: critical Justification: breaks the whole system Dear Maintainer, after writing to an NFS which make the underlying ext4 file system full (no more available space), nfsd crashes with this trace: Mai 30 02:50:16 itmserver2 kernel: INFO: task

Bug#866640: marked as done (gtkpod: depends on libwebkitgtk-3.0-0 which is deprecated)

Your message dated Fri, 07 Jul 2017 15:50:00 + with message-id and subject line Bug#866640: fixed in gtkpod 2.1.5-6 has caused the Debian Bug report #866640, regarding gtkpod: depends on libwebkitgtk-3.0-0 which is deprecated to be marked as done. This means that you claim that the problem ha

Bug#867580: marked as done (d-shlibs FTBFS with shellcheck 0.4.6-1)

Your message dated Fri, 07 Jul 2017 15:35:49 + with message-id and subject line Bug#867580: fixed in d-shlibs 0.81 has caused the Debian Bug report #867580, regarding d-shlibs FTBFS with shellcheck 0.4.6-1 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#867503: marked as done (repsnapper FTBFS: error: no match for 'operator==' (operand types are 'const Cairo::RefPtr' and 'int'))

Your message dated Fri, 07 Jul 2017 14:52:19 + with message-id and subject line Bug#867503: fixed in repsnapper 2.5a4-1 has caused the Debian Bug report #867503, regarding repsnapper FTBFS: error: no match for 'operator==' (operand types are 'const Cairo::RefPtr' and 'int') to be marked as do

Bug#867581: libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report)

Package: libgnutls30 Version: 3.5.8-5+deb9u1 Severity: critical Tags: patch Justification: breaks unrelated software Dear Maintainer, * What led up to the situation? Unrelated gnome-terminal or xfce4-terminal crashing when significant output (e.g. running 'yes'; apparently because of the corr

Bug#867580: d-shlibs FTBFS with shellcheck 0.4.6-1

Source: d-shlibs Version: 0.80 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/d-shlibs.html ... /usr/bin/make -C . CFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-se

Bug#858539: should ca-certificates certdata.txt synchronize across all suites?

On Fri, Jul 07, 2017 at 03:57:35PM +0200, Philipp Kern wrote: > On 07/06/2017 08:01 PM, Antoine Beaupré wrote: > > In looking at fixing #858539 (blocking WoSign and StartCom, in CC) for > > wheezy, I noticed the issue was also pending in jessie. Furthermore, the > > idea originally raised by pabs[1

Bug#858539: should ca-certificates certdata.txt synchronize across all suites?

On 07/06/2017 08:01 PM, Antoine Beaupré wrote: > In looking at fixing #858539 (blocking WoSign and StartCom, in CC) for > wheezy, I noticed the issue was also pending in jessie. Furthermore, the > idea originally raised by pabs[1] was to also update the packages for > the latest changes in certdata

Bug#867435: marked as done (python3-hypothesis: missing dependencies)

Your message dated Fri, 07 Jul 2017 13:05:28 + with message-id and subject line Bug#867435: fixed in python-hypothesis 3.12.0-1 has caused the Debian Bug report #867435, regarding python3-hypothesis: missing dependencies to be marked as done. This means that you claim that the problem has bee

Bug#861445: getdns: Incomplete debian/copyright?

Control: tags -1 + patch On Sat, 29 Apr 2017 09:20:10 +0100 Chris Lamb wrote: ... > I just ACCEPTed getdns from NEW but noticed it was missing > attribution in debian/copyright for at least: > > m4/ax_check_compile_flag.m4 > src/compat/arc4random{,_uniform}.c > src/compat/getentropy_{linu

Processed: Re: getdns: Incomplete debian/copyright?

Processing control commands: > tags -1 + patch Bug #861445 [src:getdns] getdns: Incomplete debian/copyright? Added tag(s) patch. -- 861445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#867435 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 867435 pending Bug #867435 [python3-hypothesis] python3-hypothesis: missing dependencies Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867435: https://bugs.debian.org/cgi-bin/bugreport.

Bug#867435: marked as pending

tag 867435 pending thanks Hello, Bug #867435 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/python-hypothesis.git/commit/?id=795bbec --- commit 795bbecf

Bug#866564: bind9: CVE-2017-3142 CVE-2017-3143

Hi, This bug is marked as fixed in versions bind9/1:9.9.5.dfsg-9+deb8u12, bind9/1:9.10.3.dfsg.P4-12.3+deb9u1 but they are not available in security repository. Is there anything holding it ? -- Rogerio Bastos PoP-BA/RNP

Bug#867403: marked as done (python3-django-xmlrpc: incorrect dependencies)

Your message dated Fri, 07 Jul 2017 11:33:47 + with message-id and subject line Bug#867403: fixed in django-xmlrpc 0.1.7-1 has caused the Debian Bug report #867403, regarding python3-django-xmlrpc: incorrect dependencies to be marked as done. This means that you claim that the problem has bee

Bug#867481: [Python-modules-team] Bug#867481: celery FTBFS: test_recursive runs forever with python 3.6

On Fri, Jul 07, 2017 at 09:03:32PM +1000, Brian May wrote: > Adrian Bunk writes: > > test_recursive (celery.tests.app.test_log.test_logger_isa) ... Wed Aug 8 > > 21:54:56 UTC 2018 - pbuilder was killed by timeout after 18h. > > Thu Jul 6 15:31:49 UTC 2017 - total duration: 18h 0m 25s. > > Pres

Bug#867560: netfilter-persistent fails randomly during boot; restarting later works

Package: netfilter-persistent Version: 1.0.4+nmu2 Severity: grave Tags: security Justification: renders package unusable Dear Maintainer, * What led up to the situation? Upgrading from jessie to stretch. On two Debian systems, netfilter-persistent worked fine in jessie but randomly fails to

Bug#867481: [Python-modules-team] Bug#867481: celery FTBFS: test_recursive runs forever with python 3.6

Adrian Bunk writes: > test_recursive (celery.tests.app.test_log.test_logger_isa) ... Wed Aug 8 > 21:54:56 UTC 2018 - pbuilder was killed by timeout after 18h. > Thu Jul 6 15:31:49 UTC 2017 - total duration: 18h 0m 25s. Presumabley this is fixed in the latest celery. However it looks like the

Bug#867403: marked as pending

tag 867403 pending thanks Hello, Bug #867403 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/django-xmlrpc.git/commit/?id=71a4139 --- commit 71a4139d7bed

Processed: Bug#867403 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 867403 pending Bug #867403 [python3-django-xmlrpc] python3-django-xmlrpc: incorrect dependencies Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867403: https://bugs.debian.org/cgi-bin/b

Bug#867450: marked as done (python3-pyperclip: missing python3 dependency)

Your message dated Fri, 07 Jul 2017 10:50:05 + with message-id and subject line Bug#867450: fixed in python-pyperclip 1.5.27-3 has caused the Debian Bug report #867450, regarding python3-pyperclip: missing python3 dependency to be marked as done. This means that you claim that the problem has

Bug#867558: flask-ldapconn FTBFS: build dependencies python-ldap3/python3-ldap3 are only available in more recent versions

Source: flask-ldapconn Version: 0.6.13-1 Severity: serious # apt-get build-dep flask-ldapconn Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an

Bug#867549: marked as done (pysal FTBFS with python 3.6 as supported version)

Your message dated Fri, 07 Jul 2017 10:04:27 + with message-id and subject line Bug#867549: fixed in pysal 1.13.0-5 has caused the Debian Bug report #867549, regarding pysal FTBFS with python 3.6 as supported version to be marked as done. This means that you claim that the problem has been de

Bug#864974: marked as done (thunderbird: Missing AtomicOperations for multiple architectures cause FTBFS)

Your message dated Fri, 7 Jul 2017 11:48:23 +0200 with message-id <43277f85-2a09-f651-851f-c0e92ca93...@physik.fu-berlin.de> and subject line Re: Bug#864974: thunderbird: Missing AtomicOperations for multiple architectures cause FTBFS has caused the Debian Bug report #864974, regarding thunderbird

Bug#867551: pybind11: missing build dependency on python3-all-dev

Source: pybind11 Version: 2.0.1-3 Severity: serious Tags: buster sid FTBFS when more than one python3 version is supported: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pybind11.html ... cd /build/1st/pybind11-2.0.1/obj-x86_64-linux-gnu/tests && /usr/bin/c++ -Dpybind11_t

Processed: Re: Bug#867549: pysal FTBFS with python 3.6 as supported version

Processing control commands: > tags -1 pending Bug #867549 [src:pysal] pysal FTBFS with python 3.6 as supported version Added tag(s) pending. -- 867549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#867549: pysal FTBFS with python 3.6 as supported version

Control: tags -1 pending Hi Adrian, Thanks for reporting this issue, I've forwarded it upstream. Until upstream provides a fix for the Python 3.6, I've disabled the offending tests to allow the build to succeed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41

Processed: bug 867549 is forwarded to https://github.com/pysal/pysal/issues/948

Processing commands for cont...@bugs.debian.org: > forwarded 867549 https://github.com/pysal/pysal/issues/948 Bug #867549 [src:pysal] pysal FTBFS with python 3.6 as supported version Set Bug forwarded-to-address to 'https://github.com/pysal/pysal/issues/948'. > thanks Stopping processing here. Pl

Bug#867514: python2.7/cmake: find_package called with invalid argument "2.7.13+"

Control: reassign -1 cmake I disagree. cmake should be able to handle the trailing indicator about prereleases, beta releases and release candidates. On 07.07.2017 01:11, Adrian Bunk wrote: > Source: python2.7 > Version: 2.7.13-3 > Severity: serious > Control: affects -1 cmake src:libsolv > > mi

Processed: Re: Bug#867514: python2.7/cmake: find_package called with invalid argument "2.7.13+"

Processing control commands: > reassign -1 cmake Bug #867514 [src:python2.7] python2.7/cmake: find_package called with invalid argument "2.7.13+" Bug reassigned from package 'src:python2.7' to 'cmake'. No longer marked as found in versions python2.7/2.7.13-3. Ignoring request to alter fixed versi

Bug#867550: libgiftiio-dev: This package should have a strong dependance on libnifti-dev

Package: libgiftiio-dev Version: 1.0.9-1+b2 Severity: serious Justification: fails to build from source (but built successfully in the past) This package should have a strong dependance on libnifti-dev, as the gifti_io.h:6:23: includes nifti1_io.h. Furthermore there are missing library symbolic l

Processed: Also makes kdevelop FTBFS

Processing commands for cont...@bugs.debian.org: > affects 866354 src:kdevelop Bug #866354 [libstdc++6] armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 Added indication that 866354 affects src:kdevelop > thanks Stopping processing her

Bug#867549: pysal FTBFS with python 3.6 as supported version

Source: pysal Version: 1.13.0-4 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pysal.html ... I: pybuild base:184: cd /build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build; python3.6 -m nose --exclude test_DistanceBand_arc --exclude-dir=pysa

Bug#867421: marked as done (python3-certifi: missing python3 dependency)

Your message dated Fri, 07 Jul 2017 08:51:16 + with message-id and subject line Bug#867421: fixed in python-certifi 2017.4.17-2 has caused the Debian Bug report #867421, regarding python3-certifi: missing python3 dependency to be marked as done. This means that you claim that the problem has

Bug#867399: marked as done (python3-django-cors-headers: missing python3 dependency)

Your message dated Fri, 07 Jul 2017 08:48:52 + with message-id and subject line Bug#867399: fixed in django-cors-headers 2.1.0+github-2 has caused the Debian Bug report #867399, regarding python3-django-cors-headers: missing python3 dependency to be marked as done. This means that you claim t

Bug#867357: marked as done (ratbagd FTBFS: Dependency "python3" not found)

Your message dated Fri, 07 Jul 2017 07:48:43 + with message-id and subject line Bug#867357: fixed in ratbagd 0.4-2 has caused the Debian Bug report #867357, regarding ratbagd FTBFS: Dependency "python3" not found to be marked as done. This means that you claim that the problem has been dealt

Processed: Bug#867399 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 867399 pending Bug #867399 [python3-django-cors-headers] python3-django-cors-headers: missing python3 dependency Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867399: https://bugs.debi

Bug#867399: marked as pending

tag 867399 pending thanks Hello, Bug #867399 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/django-cors-headers.git/commit/?id=d444776 --- commit d44477

Processed: Re: Bug#867532: cacti: CVE-2017-10970: XSS vulnerability via link.php

Processing control commands: > notfound -1 0.8.8h+ds1-10 Bug #867532 [src:cacti] cacti: CVE-2017-10970: XSS vulnerability via link.php Ignoring request to alter found versions of bug #867532 to the same values previously set > found -1 1.1.3+ds1-1 Bug #867532 [src:cacti] cacti: CVE-2017-10970: XS

Bug#867542: enigmail: can't decrypt messages in thunderbird

Package: enigmail Version: 2:1.9.8-1 Severity: grave Dear Maintainer, decryption of messages in thunderbird fails. The log of enigmail shows this: --- %< --- 2017-07-07 08:34:46.501 [DEBUG] errorHandling.jsm: parseErrorOutputWith: statusFlags = 0020 2017-07-07 08:34:46.501 [DEBUG] errorHandl

  1   2   >