Processed: theano: C-optimized ops fail with "module 'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"

Processing control commands: > tags -1 patch Bug #918090 [src:theano] theano: C-optimized ops fail with "module 'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'" Added tag(s) patch. -- 918090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918090 Debian Bug Tracking System

Bug#918090: theano: C-optimized ops fail with "module 'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"

Source: theano Version: 1.0.2+dfsg-1 Severity: serious Control: tags -1 patch Many Theano operations include C code for speed; the compilation process uses an undocumented Numpy function to check ABI compatibility. In Numpy 1.16 (recently added to sid), this function is moved, causing all

Bug#915765: marked as done (pystaticconfiguration FTBFS: test error)

Your message dated Thu, 03 Jan 2019 07:19:33 + with message-id and subject line Bug#915765: fixed in pystaticconfiguration 0.10.3-2 has caused the Debian Bug report #915765, regarding pystaticconfiguration FTBFS: test error to be marked as done. This means that you claim that the problem has

Bug#917001: MR

Here is the corresponding MR: https://salsa.debian.org/python-team/modules/python-twilio/merge_requests/1 Cheers, -- Seb

Bug#915765: MR

Here is the corresponding MR: https://salsa.debian.org/python-team/modules/pystaticconfiguration/merge_requests/1 Cheers, -- Seb

Bug#918088: autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)"

Package: autofs-ldap Version: 5.1.2-4 Severity: grave Justification: renders package unusable Good morning. After the latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) automount starts but dies immediately after accessing a automounter point. Automount is configured to authenticate via GSSAPI

Processed: gitlab: CVE-2018-20488 CVE-2018-20489 CVE-2018-20490 CVE-2018-20491 CVE-2018-20492 CVE-2018-20493 CVE-2018-20494 CVE-2018-20495 CVE-2018-20496 CVE-2018-20497 CVE-2018-20498 CVE-2018-20499 C

Processing control commands: > found -1 11.6.0+dfsg-1 Bug #918086 [src:gitlab] gitlab: CVE-2018-20488 CVE-2018-20489 CVE-2018-20490 CVE-2018-20491 CVE-2018-20492 CVE-2018-20493 CVE-2018-20494 CVE-2018-20495 CVE-2018-20496 CVE-2018-20497 CVE-2018-20498 CVE-2018-20499 CVE-2018-20500

Bug#918086: gitlab: CVE-2018-20488 CVE-2018-20489 CVE-2018-20490 CVE-2018-20491 CVE-2018-20492 CVE-2018-20493 CVE-2018-20494 CVE-2018-20495 CVE-2018-20496 CVE-2018-20497 CVE-2018-20498 CVE-2018-20499

Source: gitlab Version: 11.5.5+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 11.6.0+dfsg-1 Hi, The following vulnerabilities were published for gitlab, fixed in the 11.6.1, 11.5.6, and 11.4.13 versions, cf [15]. CVE-2018-20488[0]: Secret CI

Bug#917001: marked as done (python3-twilio: twilio missing dependency on requests)

Your message dated Thu, 03 Jan 2019 06:49:28 + with message-id and subject line Bug#917001: fixed in python-twilio 6.8.2-2 has caused the Debian Bug report #917001, regarding python3-twilio: twilio missing dependency on requests to be marked as done. This means that you claim that the

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tag 916805 fixed-upstream pending Bug #916805 [src:assess-el] assess-el: FTBFS with Emacs 26.1: tests fail Added tag(s) fixed-upstream and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 916805:

Bug#918083: cutesdr FTCBFS: does not pass cross flags to cmake

Source: cutesdr Version: 1.20-2 Severity: serious Justification: policy 4.6 Tags: patch User: helm...@debian.org Usertags: rebootstrap cutesdr fails to cross build from source, because its builds two cmake projects (one via dh_auto_foo and then the siqs directory explicitly in

Bug#917576: marked as done (stegosuite: depends on libswt-gtk2 which is no longer built)

Your message dated Thu, 03 Jan 2019 05:19:56 + with message-id and subject line Bug#917576: fixed in stegosuite 0.8.0-2 has caused the Debian Bug report #917576, regarding stegosuite: depends on libswt-gtk2 which is no longer built to be marked as done. This means that you claim that the

Bug#916548: marked as done (python3.7: Version constraint in pyzo breaks is too strict)

Your message dated Thu, 03 Jan 2019 04:04:49 + with message-id and subject line Bug#916548: fixed in python3.7 3.7.2-1 has caused the Debian Bug report #916548, regarding python3.7: Version constraint in pyzo breaks is too strict to be marked as done. This means that you claim that the

Bug#918079: pandas: FTBFS: B-D on python-nbsphinx which is no longer installable nor built any more

Source: pandas Version: 0.23.3-1 Severity: serious See #917418 for “python-nbsphinx (0.4.1+ds-1) is not installable”. src:nbsphinx (0.4.1+ds-3) now only builds the py3k package. python-nbsphinx (= 0.3.5+ds-1) is installable and usable, but no longer in Debian, so please move to python3-nbsphinx

Bug#906688: marked as done (ruby-netrc: FTBFS in buster/sid (test_missing_environment fails))

Your message dated Thu, 03 Jan 2019 02:43:47 + with message-id and subject line Bug#906688: fixed in ruby-netrc 0.11.0-2 has caused the Debian Bug report #906688, regarding ruby-netrc: FTBFS in buster/sid (test_missing_environment fails) to be marked as done. This means that you claim that

Bug#918077: python-meep-mpich2 fails to install, postinst script looks for wrong package name.

Package: python-meep-lam4 Version: 1.7.0-2 Severity: serious https://piuparts.debian.org/sid/fail/python-meep-lam4_1.7.0-2.log Setting up python-meep-lam4 (1.7.0-2) ... dpkg-query: package 'python-meep' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files

Bug#816640: Bug #816640 in ruby-eventmachine marked as pending

Hi, On Fri, 16 Feb 2018 13:48:16 + z...@debian.org wrote: > Bug #816640 in ruby-eventmachine 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#883778: problems building guile-2.0 on armel

Kurt Roeckx writes: > I've enabled guile-2.0 and 2.2 again on armel yesterday, and it > seems to build without issues now. Nice! And thanks much. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03

Bug#918074: python-meep-mpich2 fails to install, postinst script looks for wrong package name.

Package: python-meep-mpich2 Version: 1.7.0-2 Severity: serious https://piuparts.debian.org/sid/fail/python-meep-mpich2_1.7.0-2.log Setting up python-meep-mpich2 (1.7.0-2) ... dpkg-query: package 'python-meep' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive

Bug#918068: sagemath: still not building on unstable :-(

Package: sagemath Version: 8.4-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Thanks for fixing the build dependencies! Unfortunately the build of 8.4-3 is now failing on the buildds :-( I presume you realise this, but letting you know just in

Bug#918057: marked as done (gnucash: FTBFS: test suite failure)

Your message dated Wed, 02 Jan 2019 23:04:43 + with message-id and subject line Bug#918057: fixed in gnucash 1:3.4-1 has caused the Debian Bug report #918057, regarding gnucash: FTBFS: test suite failure to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#913604: Please downgrade [Lack of login storage API]

Package: firefox-esr Version: 60.3.0esr-1~deb9u1 Followup-For: Bug #913604 Bernie Elbourn wrote: > Hello, > > I am not maintainer. Just regular "Joe" trying to get to grips with why > firefox updates have stopped due to apt-listbugs. > > I have sympathy with the sentiment .. > > "By

Bug#906859: xul-ext-dom-inspector no longer works with firefox-esr 60

On Wed, Oct 03, 2018 at 05:19:49PM +0200, Moritz Mühlenhoff wrote: > On Sat, Sep 08, 2018 at 03:12:40PM +0800, Paul Wise wrote: > > On Tue, 21 Aug 2018 21:11:16 +0300 Adrian Bunk wrote: > > > > > Package: xul-ext-dom-inspector > > > > > > XUL addons are no longer supported. > > > > The native

Bug#906868: xul-ext-toggle-proxy no longer works with firefox-esr 60

On Wed, Sep 26, 2018 at 06:42:31PM +0200, Sascha Girrulat wrote: > Hi, > > would be ok for me. I've filed a removal bug now. Cheers, Moritz

Bug#906832: xul-ext-kwallet5 no longer works with firefox-esr 60

On Wed, Oct 03, 2018 at 05:20:23PM +0200, Moritz Mühlenhoff wrote: > On Tue, Aug 21, 2018 at 07:53:52PM +0300, Adrian Bunk wrote: > > On Tue, Aug 21, 2018 at 07:11:59PM +0300, Adrian Bunk wrote: > > > Package: xul-ext-kwallet5 > > > Version: 1.0-2 > > > Severity: serious > > > > > > XUL addons

Bug#918061: Should ckermit be removed?

Package: ckermit Severity: serious Should ckermit be removed from the archive? - Hasn't seen a maintainer upload in almost six years - Multiple RC bugs at this point Cheers, Moritz

Processed: bug 918057 is forwarded to https://bugs.gnucash.org/show_bug.cgi?id=797008

Processing commands for cont...@bugs.debian.org: > forwarded 918057 https://bugs.gnucash.org/show_bug.cgi?id=797008 Bug #918057 [src:gnucash] gnucash: FTBFS: test suite failure Set Bug forwarded-to-address to 'https://bugs.gnucash.org/show_bug.cgi?id=797008'. > thanks Stopping processing here.

Bug#918057: Bug #918057 in gnucash marked as pending

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

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

Processed: affects 915151

Processing commands for cont...@bugs.debian.org: > affects 915151 src:lbzip2 Bug #915151 [gnulib] gnulib does not work with glibc/2.28 Bug #915171 [gnulib] lbzip2 FTBFS with glibc 2.28 Added indication that 915151 affects src:lbzip2 Added indication that 915171 affects src:lbzip2 > thanks

Bug#918060: iwyu FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

Source: iwyu Version: 7.0-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=iwyu=armel=7.0-2=1545913678=0 ... /usr/bin/c++ -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -w -ffunction-sections -fdata-sections -Wl,-z,relro -Wl,-rpath-link,

Processed: lbzip2 copies the files at build time from gnulib

Processing commands for cont...@bugs.debian.org: > reassign 915171 gnulib Bug #915171 [src:lbzip2] lbzip2 FTBFS with glibc 2.28 Bug reassigned from package 'src:lbzip2' to 'gnulib'. No longer marked as found in versions lbzip2/2.5-2. Ignoring request to alter fixed versions of bug #915171 to the

Bug#917717: marked as done (pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13)

Your message dated Wed, 02 Jan 2019 21:34:19 + with message-id and subject line Bug#917717: fixed in pylint-django 2.0.5-1 has caused the Debian Bug report #917717, regarding pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13 to

Bug#918054: [Debichem-devel] Bug#918054: elkcode: frequent test hangs

Hi, On Wed, Jan 02, 2019 at 10:36:48PM +0200, Adrian Bunk wrote: > Source: elkcode > Version: 5.2.14-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/package.php?p=elkcode=sid > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elkcode.html > > Tests

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

On Wed, Jan 02, 2019 at 09:56:51PM +0100, Gregor Riepl wrote: > >> That, or the fix wasn't enough. > > > > Works for me. > > Odd. > > > What failure are you getting, and what is the contents > > of /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc ? > > I'm getting the same pthread detection

Bug#883778: problems building guile-2.0 on armel

I've enabled guile-2.0 and 2.2 again on armel yesterday, and it seems to build without issues now.

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

>> That, or the fix wasn't enough. > > Works for me. Odd. > What failure are you getting, and what is the contents > of /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc ? I'm getting the same pthread detection error as reported in the bug. Contents: $ cat

Bug#918057: gnucash: FTBFS: test suite failure

Source: gnucash Version: 1:3.3-2 Severity: serious Gnucash has a test suite problem. There is a log here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnucash.html showing: [pass] line:641, test: dual amount column, grand totals available [fail] line:644, test: dual amount

Bug#918055: gnss-sdr FTBFS: test failures on most architectures

Source: gnss-sdr Version: 0.0.10-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=gnss-sdr=sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnss-sdr.html At first sight I would sort the test failures as follows: Randomly: 6 -

Bug#918054: elkcode: frequent test hangs

Source: elkcode Version: 5.2.14-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=elkcode=sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elkcode.html Tests seems to frequently hang, with no clear pattern which test or which architecture (amd64

Bug#918053: elk-lapw is missing dependency on openmpi-bin

Package: elk-lapw Version: 4.0.15-2 Severity: serious Found at https://bugs.launchpad.net/ubuntu/+source/elkcode/+bug/1416296 and reproduced.

Bug#918052: python-ltfatpy FTBFS: TestPsech.test_exceptions failure

Source: python-ltfatpy Version: 1.0.12-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=python-ltfatpy=sid ... === FAILURES === __ TestPsech.test_exceptions

Processed: tagging 917635

Processing commands for cont...@bugs.debian.org: > tags 917635 + buster sid Bug #917635 [elkcode] elkcode FTBFS, undefined reference to xc_f90_mgga_x_tb09_set_par_ Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 917635:

Bug#917788: marked as done (libmedc11: Overwrites a file from libmedc1v5)

Your message dated Wed, 02 Jan 2019 19:35:38 + with message-id and subject line Bug#917788: fixed in med-fichier 4.0.0+repack-5 has caused the Debian Bug report #917788, regarding libmedc11: Overwrites a file from libmedc1v5 to be marked as done. This means that you claim that the problem

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

On Wed, Jan 02, 2019 at 05:28:13PM +0100, Gregor Riepl wrote: > > >> I will look into the issue. > >> If you have any idea why it might be occurring, please share. > > > > The actual error is in #917057, which was already correctly marked as > > affecting src:cura-engine. > > I'm positive that

Bug#917837: RM: clutter-gesture -- ROM; dead upstream

Package: ftp.debian.org Severity: wishlist Dear ftp-master, Please remove clutter-gesture. It is dead upstream. I don't have time to check if clutter/clutter-gesture-action.h from libclutter-1.0-dev is the replacement for same functionality. But since clutter-gesture losts its upstream source

Bug#917771: marked as done (python-pywebview: Incomplete debian/copyright?)

Your message dated Wed, 02 Jan 2019 17:19:51 + with message-id and subject line Bug#917771: fixed in python-pywebview 2.2.1+dfsg-2 has caused the Debian Bug report #917771, regarding python-pywebview: Incomplete debian/copyright? to be marked as done. This means that you claim that the

Bug#917869: python-escript FTBFS on armhf, mips, mipsel and mips64el

Thanks, I will take care of it. Anton Am Mi., 2. Jan. 2019 um 00:51 Uhr schrieb Adrian Bunk : > > On Mon, Dec 31, 2018 at 06:51:12AM +, peter green wrote: > >... while the mips and mipsel builds ran out of virtual memory. > > > > It may be worth playing with the settings, the first thing to

Bug#864709: xfce CD1 image should contain fonts for languages supported by debian installer

On Mon, Dec 31, 2018 at 12:54:52AM +0900, Hideki Yamane wrote: > >On Sun, 30 Dec 2018 18:46:45 +0530 >Pirate Praveen wrote: >> We have not stopped providing CD images. DVD is an additional option. I >> think this matters still. > > Well, we've already stopped it 3 years ago. >

Bug#912245: marked as done (ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key too small)

Your message dated Wed, 02 Jan 2019 16:35:16 + with message-id and subject line Bug#912245: fixed in ruby-nio4r 2.3.1-1~exp1 has caused the Debian Bug report #912245, regarding ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key too small to be marked as done. This means that you claim that

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

>> I will look into the issue. >> If you have any idea why it might be occurring, please share. > > The actual error is in #917057, which was already correctly marked as > affecting src:cura-engine. I'm positive that the problem is more complex than that, because I already committed and

Bug#916941: libvncserver: Multiple security vulnarabilities

Control: tags -1 + patch Attached is proposed debdiff for the update, but though not yet uploaded. The fix for CVE-2018-15126 unfortunately introduced two new symbols while dropping CloseUndoneFileTransfer, but afaics from sources.d.n search nobody is using it directly. Regards, Salvatore diff

Bug#916355: marked as done (cython: References to non-existent members of PyThreadState in Python 3.7)

Your message dated Wed, 02 Jan 2019 16:19:42 + with message-id and subject line Bug#916355: fixed in cython 0.29.2-1 has caused the Debian Bug report #916355, regarding cython: References to non-existent members of PyThreadState in Python 3.7 to be marked as done. This means that you claim

Processed: Re: Bug#916941: libvncserver: Multiple security vulnarabilities

Processing control commands: > tags -1 + patch Bug #916941 [libvncserver] libvncserver: Multiple security vulnerabilities Added tag(s) patch. -- 916941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug #912245 in ruby-nio4r marked as pending

Processing control commands: > tag -1 pending Bug #912245 [src:ruby-nio4r] ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key too small Added tag(s) pending. -- 912245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912245 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#904592: predict-gsat: No executable is included

El 30 de diciembre de 2018 14:17:00 CET, Christoph Berg escribió: >Re: Manolo Díaz 2018-07-25 ><153252250500.25469.2624480834566544223.reportbug@localhost> >> No gsat executable is included > >Good news: I fixed this in git. > >Bad news: predict doesn't start for me. It keeps asking for my

Bug#912245: Bug #912245 in ruby-nio4r marked as pending

Control: tag -1 pending Hello, Bug #912245 in ruby-nio4r 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#884658: marked as done (dkms: Should really depends on dpkg-dev for dpkg-architecture)

Your message dated Wed, 02 Jan 2019 15:50:39 + with message-id and subject line Bug#884658: fixed in dkms 2.6.1-2 has caused the Debian Bug report #884658, regarding dkms: Should really depends on dpkg-dev for dpkg-architecture to be marked as done. This means that you claim that the problem

Bug#914835: marked as done (python3-defaults breaks aiocoap autopkgtest)

Your message dated Wed, 02 Jan 2019 15:49:07 + with message-id and subject line Bug#914835: fixed in aiocoap 0.3-3 has caused the Debian Bug report #914835, regarding python3-defaults breaks aiocoap autopkgtest to be marked as done. This means that you claim that the problem has been dealt

Bug#915207: marked as done (gnudatalanguage: autopkgtests fail: test_bug_n000720, test_idlneturl, test_point_lun, test_save_restore, test_zip)

Your message dated Wed, 02 Jan 2019 15:34:41 + with message-id and subject line Bug#915207: fixed in gnudatalanguage 0.9.9-2 has caused the Debian Bug report #915207, regarding gnudatalanguage: autopkgtests fail: test_bug_n000720, test_idlneturl, test_point_lun, test_save_restore, test_zip

Bug#912236: marked as done (ruby-ffi-rzmq FTBFS: SSL_CTX_use_certificate: ee key too small)

Your message dated Wed, 02 Jan 2019 15:23:48 + with message-id and subject line Bug#912236: fixed in ruby-ffi-rzmq 2.0.6-2 has caused the Debian Bug report #912236, regarding ruby-ffi-rzmq FTBFS: SSL_CTX_use_certificate: ee key too small to be marked as done. This means that you claim that

Bug#918003: marked as done (nwchem FTBFS on 32bit: BLAS size mismatch with Global Arrays)

Your message dated Wed, 02 Jan 2019 15:22:35 + with message-id and subject line Bug#918003: fixed in nwchem 6.8.1-2 has caused the Debian Bug report #918003, regarding nwchem FTBFS on 32bit: BLAS size mismatch with Global Arrays to be marked as done. This means that you claim that the

Bug#912236: Bug #912236 in ruby-ffi-rzmq marked as pending

Control: tag -1 pending Hello, Bug #912236 in ruby-ffi-rzmq 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 #912236 in ruby-ffi-rzmq marked as pending

Processing control commands: > tag -1 pending Bug #912236 [src:ruby-ffi-rzmq] ruby-ffi-rzmq FTBFS: SSL_CTX_use_certificate: ee key too small Added tag(s) pending. -- 912236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912236 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#907149: marked as done (roodi: FTBFS in buster/sid FTBFS in buster/sid (failing tests))

Your message dated Wed, 02 Jan 2019 14:56:53 + with message-id and subject line Bug#907149: fixed in roodi 5.0.0-2 has caused the Debian Bug report #907149, regarding roodi: FTBFS in buster/sid FTBFS in buster/sid (failing tests) to be marked as done. This means that you claim that the

Bug#918003: Bug #918003 in nwchem marked as pending

Control: tag -1 pending Hello, Bug #918003 in nwchem 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#917904: tightvncserver does not ask for password set by vncpasswd

Hi Ola, thank you for your answer. I checked: $ ls -l /etc/alternatives/vnc* lrwxrwxrwx 1 root root 24 Jul 27  2017 /etc/alternatives/vncconnect -> /usr/bin/tightvncconnect lrwxrwxrwx 1 root root 40 Jul 27  2017 /etc/alternatives/vncconnect.1.gz -> /usr/share/man/man1/tightvncconnect.1.gz

Processed: Bug #918003 in nwchem marked as pending

Processing control commands: > tag -1 pending Bug #918003 [src:nwchem] nwchem FTBFS on 32bit: BLAS size mismatch with Global Arrays Added tag(s) pending. -- 918003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#913631: marked as done (FTBFS: libapache2-mod-auth-openidc on multiple arches)

Your message dated Wed, 02 Jan 2019 14:52:05 + with message-id and subject line Bug#913631: fixed in libapache2-mod-auth-openidc 2.3.10-1 has caused the Debian Bug report #913631, regarding FTBFS: libapache2-mod-auth-openidc on multiple arches to be marked as done. This means that you claim

Bug#916941: libvncserver: Multiple security vulnarabilities

Hi I have been working on an update for libvncserver for unstable (buster) as NMU. I will post a proposed debdiff when I'm relatively confident on the result. Regards, Salvatore

Processed: Bug #907149 in roodi marked as pending

Processing control commands: > tag -1 pending Bug #907149 [src:roodi] roodi: FTBFS in buster/sid FTBFS in buster/sid (failing tests) Added tag(s) pending. -- 907149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#907149: Bug #907149 in roodi marked as pending

Control: tag -1 pending Hello, Bug #907149 in roodi 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#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

Package: ruby-sinatra-contrib Version: 2.0.5-1 Severity: serious Justification: unsatisfiable dependencies # apt install ruby-sinatra-contrib Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have

Bug#915714: gnustep-base: Please use pkg-config to detect icu

Hugh McMaster wrote: > Control: severity -1 serious > Control: tags -1 + patch > As the removal of icu-config from Debian is imminent, I have prepared a > patch for gnustep-base so its build system uses pkg-config to detect icu. Thanks for the patch but AFAICT this is a cosmetic issue that

Bug#917990: marked as done (libplplotada1-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/ada/adalib/plplotada/plplot_auxiliary.ali)

Your message dated Wed, 02 Jan 2019 13:21:50 + with message-id and subject line Bug#917990: fixed in plplot 5.14.0+dfsg-2 has caused the Debian Bug report #917990, regarding libplplotada1-dev: fails to upgrade from 'testing' - trying to overwrite

Bug#912631: marked as done (liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips)

Your message dated Wed, 02 Jan 2019 13:21:26 + with message-id and subject line Bug#912631: fixed in lwjgl 2.9.3+dfsg-5 has caused the Debian Bug report #912631, regarding liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips to be marked as done. This means that

Bug#917726: globus-gass-copy: FTBFS: tests failed

Hi Lucas. I have a question regarding your report. Is it really a requirement that the package build should succeed even if the user account doing the package build is disabled for logins? Not accepting remote logins during the build is very reasonable. But a test that starts a server on the

Bug#915426: git breaks git-remote-hg autopkgtest

I can do yet another NMU to fix this, but am hesitating as I worry if that will masquerade a lack of responsive maintenance. Please tell if it is sensible that I take over maintenance of this package, or join as co-maintainer, or however is appreciated. Kind regards, - Jonas -- * Jonas

Processed: Bug #912631 in lwjgl marked as pending

Processing control commands: > tag -1 pending Bug #912631 [liblwjgl-java-jni] liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips Ignoring request to alter tags of bug #912631 to the same tags previously set -- 912631:

Bug#918014: REMOVE

Best Regards, John Gates, CISSP *Let’s Connect!* On Wed, Jan 2, 2019 at 6:33 AM Dominik George wrote: > Package: apache2 > Version: 2.4.37-1 > Severity: grave > Justification: renders package unusable > > apache2

Bug#912631: Bug #912631 in lwjgl marked as pending

Control: tag -1 pending Hello, Bug #912631 in lwjgl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Re: liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips

Processing control commands: > tags -1 pending Bug #912631 [liblwjgl-java-jni] liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips Added tag(s) pending. -- 912631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912631 Debian Bug Tracking System Contact

Bug#912631: liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips

Control: tags -1 pending Am 31.12.18 um 06:13 schrieb Le Gall Guillaume: > Hello, > > > and thank you very much for your answer. > > > First, about OpenJDK 11, and "debian/patches/javah.patch". You are > absolutely right to point that out. Actually, I had missed that the > "javah" tool was

Bug#918014: apache2: Segfault in mod_filter only wehen started by systemd

Package: apache2 Version: 2.4.37-1 Severity: grave Justification: renders package unusable apache2 segfaults on start, but only when started normally through systemd. Starting apache2 by hand with the samer command line does not result in a segfault… #0 0x7f6049d7c3d0 in ?? () from

Bug#912593: marked as done (sagemath has unfulfillable build-dependencies)

Your message dated Wed, 02 Jan 2019 12:05:04 + with message-id and subject line Bug#912593: fixed in sagemath 8.4-3 has caused the Debian Bug report #912593, regarding sagemath has unfulfillable build-dependencies to be marked as done. This means that you claim that the problem has been

Bug#912980: marked as done (sagemath is incompatible with GAP 4.9)

Your message dated Wed, 02 Jan 2019 12:05:04 + with message-id and subject line Bug#912980: fixed in sagemath 8.4-3 has caused the Debian Bug report #912980, regarding sagemath is incompatible with GAP 4.9 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#916586: marked as done (sagemath: depends on specific libsingular4 which is no longer being built in unstable)

Your message dated Wed, 02 Jan 2019 12:05:04 + with message-id and subject line Bug#912593: fixed in sagemath 8.4-3 has caused the Debian Bug report #912593, regarding sagemath: depends on specific libsingular4 which is no longer being built in unstable to be marked as done. This means that

Bug#890231: marked as done (sagemath should use gdb, not gdb-python2, to be removed for buster)

Your message dated Wed, 02 Jan 2019 12:05:04 + with message-id and subject line Bug#890231: fixed in sagemath 8.4-3 has caused the Debian Bug report #890231, regarding sagemath should use gdb, not gdb-python2, to be removed for buster to be marked as done. This means that you claim that the

Bug#917727: openhft-lang: FTBFS: [ERROR] /<>/lang/src/main/java/net/openhft/lang/io/IOTools.java:[85, 13] cannot find symbol

Le 30/12/2018 à 17:29, tony mancill a écrit : > Given that there aren't many (or any?) r-deps for the openhft libraries, > I'm tempted to pull the versions in experimental into unstable so we > have the libraries in buster. It's either that, or not include these > packages in buster at all. > >

Bug#917576: stegosuite: depends on libswt-gtk2 which is no longer built

Le 30/12/2018 à 15:45, tony mancill a écrit : > The issue I am running into is that ${maven:Depends} is injecting an > unresolvable dependency on "libswt-gtk-4-java (>= 4.x)" and so the > resulting binary package fails to install with: > > dpkg: dependency problems prevent configuration of

Bug#917717: [Python-modules-team] Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

Hi Joseph! El mar., 1 de ene. de 2019 a la(s) 21:27, Joseph Herlant ( aerosti...@debian.org) escribió: > Control: tags -1 - fixed > Control: tags -1 + patch > Hi guys, > > Thanks Lucas for the report. Sorry for the late reply, I was out of > the country with very limited internet access. > >

Bug#918012: docker-compose: invalid version of python3-docker dependency

Package: docker-compose Version: 1.21.0-3~bpo9+1 Severity: grave Justification: renders package unusable Dear Maintainer, I tried to run docker-compose but it fails: ; docker-compose --version Traceback (most recent call last): File "/usr/bin/docker-compose", line 11, in

Bug#917650: FTBFS: include/qi.h:104:29: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier]

On Wed, Jan 02, 2019 at 11:28:19AM +0200, Timo Lindfors wrote: >Hi, > >On Sat, 29 Dec 2018, Steve McIntyre wrote: >> Package: src:qi >> Version: 2013-1 >> Severity: serious >> Justification: fails to build from source (but built successfully in the >> past) > >thanks for working on ARM

Bug#915337: marked as done (rr: baseline violation on i386)

Your message dated Wed, 02 Jan 2019 11:19:42 + with message-id and subject line Bug#915337: fixed in rr 5.2.0-4 has caused the Debian Bug report #915337, regarding rr: baseline violation on i386 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#916262: marked as done (staden-io-lib: data/xx#unsorted.sam fails randomly)

Your message dated Wed, 02 Jan 2019 11:19:50 + with message-id and subject line Bug#916262: fixed in staden-io-lib 1.14.11-6 has caused the Debian Bug report #916262, regarding staden-io-lib: data/xx#unsorted.sam fails randomly to be marked as done. This means that you claim that the problem

Bug#904422: Bumped severity

Control: severity -1 important On Wed, 2 Jan 2019 10:57:31 +0100 Ruben Undheim wrote: > Bumped the severity since now nodejs 10 is in unstable. I don't think this warrants an rc bug. It is only a warning and does not affect npm functionality or violates any policy. Serious bugs are for packages

Processed: Re: Bumped severity

Processing control commands: > severity -1 important Bug #904422 [npm] npm: complains about too-new nodejs Severity set to 'important' from 'serious' -- 904422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#916115: marked as done (389-ds-base: Please use pkg-config to detect icu)

Your message dated Wed, 02 Jan 2019 11:04:12 + with message-id and subject line Bug#916115: fixed in 389-ds-base 1.4.0.19-3 has caused the Debian Bug report #916115, regarding 389-ds-base: Please use pkg-config to detect icu to be marked as done. This means that you claim that the problem

Processed: Bumping severity

Processing commands for cont...@bugs.debian.org: > severity 904422 serious Bug #904422 [npm] npm: complains about too-new nodejs Severity set to 'serious' from 'minor' > stop Stopping processing here. Please contact me if you need assistance. -- 904422:

Bug#917650: FTBFS: include/qi.h:104:29: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier]

Hi, On Sat, 29 Dec 2018, Steve McIntyre wrote: Package: src:qi Version: 2013-1 Severity: serious Justification: fails to build from source (but built successfully in the past) thanks for working on ARM support (much appreciated!). At this point I'm considering dropping qi completely

  1   2   >