Bug#977960: [Pkg-javascript-devel] Bug#977960: dangling /usr/share/javascript/jquery/jquery.js symlink

2020-12-27 Thread Xavier
Le 27/12/2020 à 19:04, Thorsten Glaser a écrit : > Package: node-jquery > Version: 3.5.1+dfsg+~3.5.5-3 > Followup-For: Bug #977960 > X-Debbugs-Cc: t...@mirbsd.de > > Even for the latest versions of these packages, adequate reports: > > node-jquery: broken-symlink

Bug#956355: marked as done (pam: Please stop using deprecated and headers)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 06:33:27 + with message-id and subject line Bug#956355: fixed in pam 1.4.0-1 has caused the Debian Bug report #956355, regarding pam: Please stop using deprecated and headers to be marked as done. This means that you claim that the problem has been

Bug#972555: marked as done (FTBFS on buster (amd64/i386))

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 06:33:27 + with message-id and subject line Bug#956355: fixed in pam 1.4.0-1 has caused the Debian Bug report #956355, regarding FTBFS on buster (amd64/i386) to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#976322: marked as done (searx: fails to do any search, python3 compatibility issue)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 05:18:31 + with message-id and subject line Bug#976322: fixed in searx 0.17.0+dfsg1-2 has caused the Debian Bug report #976322, regarding searx: fails to do any search, python3 compatibility issue to be marked as done. This means that you claim that the

Bug#976917: simavr: FTBFS on ppc64el: obj-powerpc64le-linux-gnu/avr_adc.d:5: *** missing separator. Stop.

2020-12-27 Thread Milan Kupcevic
tags 976917 unreproducible moreinfo severity 976917 normal thanks On 12/9/20 3:41 AM, Lucas Nussbaum wrote: [...] > > During a rebuild of all packages in sid, your package failed to build > on ppc64el. At the same time, it did not fail on amd64. > > I'm marking this bug as severity:serious

Processed: Re: Bug#976917: simavr: FTBFS on ppc64el: obj-powerpc64le-linux-gnu/avr_adc.d:5: *** missing separator. Stop.

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 976917 unreproducible moreinfo Bug #976917 [src:simavr] simavr: FTBFS on ppc64el: obj-powerpc64le-linux-gnu/avr_adc.d:5: *** missing separator. Stop. Added tag(s) unreproducible and moreinfo. > severity 976917 normal Bug #976917

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

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 04:20:14 + with message-id and subject line Bug#978268: fixed in pytest-xdist 1.32.0-3 has caused the Debian Bug report #978268, regarding pytest-xdist: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as

Processed: Bug#978268 marked as pending in pytest-xdist

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978268 [src:pytest-xdist] pytest-xdist: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 978268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978268 Debian Bug Tracking System

Bug#978268: marked as pending in pytest-xdist

2020-12-27 Thread Scott Talbert
Control: tag -1 pending Hello, Bug #978268 in pytest-xdist 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#978281: marked as done (execnet: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 03:48:31 + with message-id and subject line Bug#978281: fixed in execnet 1.7.1-4 has caused the Debian Bug report #978281, regarding execnet: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This

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

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 03:48:22 + with message-id and subject line Bug#978197: fixed in apipkg 1.5-6 has caused the Debian Bug report #978197, regarding apipkg: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This means

Processed: Bug#978197 marked as pending in apipkg

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978197 [src:apipkg] apipkg: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 978197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978197 Debian Bug Tracking System Contact

Bug#978197: marked as pending in apipkg

2020-12-27 Thread Scott Talbert
Control: tag -1 pending Hello, Bug #978197 in apipkg 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: closing 934687

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 934687 0.9.0-1 Bug #934687 [heudiconv] heudiconv, indirectly build-depends on cruft package, needs to migrate to python 3 Marked as fixed in versions heudiconv/0.9.0-1. Bug #934687 [heudiconv] heudiconv, indirectly build-depends on cruft

Processed: notfixed 934687 in 0.5.3-1+rm

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 934687 0.5.3-1+rm Bug #934687 [heudiconv] heudiconv, indirectly build-depends on cruft package, needs to migrate to python 3 There is no source info for the package 'heudiconv' at version '0.5.3-1+rm' with architecture '' Unable to

Processed (with 2 errors): unarchiving 934687, reopening 934687, unarchiving 933215, reopening 933215, unarchiving 936696 ...

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # src:heudiconv was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org > unarchive 934687 > reopen 934687 Bug #934687 [heudiconv] heudiconv, indirectly build-depends on cruft package,

Bug#978483: marked as done (r-cran-pbkrtest: not installable in sid)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 01:04:10 + with message-id and subject line Bug#978483: fixed in r-cran-pbkrtest 0.5-0.1-2 has caused the Debian Bug report #978483, regarding r-cran-pbkrtest: not installable in sid to be marked as done. This means that you claim that the problem has been

Bug#978354: marked as done (mozjs78: FTBFS: dwz: debian/libmozjs-78-0/usr/lib/x86_64-linux-gnu/libmozjs-78.so.78.4.0: Couldn't find DIE referenced by DW_AT_abstract_origin)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 00:35:02 + with message-id and subject line Bug#978354: fixed in mozjs78 78.4.0-2 has caused the Debian Bug report #978354, regarding mozjs78: FTBFS: dwz: debian/libmozjs-78-0/usr/lib/x86_64-linux-gnu/libmozjs-78.so.78.4.0: Couldn't find DIE referenced by

Processed: owner of #978185

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 978185 po...@debian.org Bug #978185 [src:puppetlabs-http-client-clojure] puppetlabs-http-client-clojure: FTBFS: src/java/com/puppetlabs/http/client/impl/SslUtils.java:36: error: unreported exception NoSuchProviderException; must be

Bug#978380: marked as done (ssl-utils-clojure: FTBFS: missing deps)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 00:18:58 + with message-id and subject line Bug#978380: fixed in ssl-utils-clojure 3.1.0-2 has caused the Debian Bug report #978380, regarding ssl-utils-clojure: FTBFS: missing deps to be marked as done. This means that you claim that the problem has been

Bug#978190: marked as done (xfce4-verve-plugin: FTBFS: collect2: error: ld returned 1 exit status)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 00:05:04 + with message-id and subject line Bug#978190: fixed in xfce4-verve-plugin 2.0.1-1 has caused the Debian Bug report #978190, regarding xfce4-verve-plugin: FTBFS: collect2: error: ld returned 1 exit status to be marked as done. This means that you

Bug#978093: marked as done (uhd-doc: missing Breaks+Replaces: uhd-host (<< 4.0.0.0-3))

2020-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 00:04:58 + with message-id and subject line Bug#978093: fixed in uhd 4.0.0.0-4 has caused the Debian Bug report #978093, regarding uhd-doc: missing Breaks+Replaces: uhd-host (<< 4.0.0.0-3) to be marked as done. This means that you claim that the problem

Bug#978489: missing dependency on qml-module-qtquick-controls

2020-12-27 Thread Marco d'Itri
Package: linphone-desktop Version: 4.2.5-2 Severity: grave Or else linphone will crash with: [00:50:46:566][0x5618e548aed0][Info]app/App.cpp:784: "Open Linphone app." [00:50:46:566][0x5618e548aed0][Info]app/App.cpp:225: "Creating subwindow: `qrc:/ui/views/App/Calls/CallsWindow.qml`."

Processed: severity of 978444 is important

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 978444 important Bug #978444 [src:racket-mode] FTBFS: fails to contact repl server in tests Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 978444:

Bug#978483: r-cran-pbkrtest: not installable in sid

2020-12-27 Thread Dirk Eddelbuettel
On 28 December 2020 at 00:25, Aurelien Jarno wrote: | Package: r-cran-pbkrtest | Version: 0.5-0.1-1 | Severity: serious | | r-cran-pbkrtest is currently not installable in sid: | | # apt-get install r-cran-pbkrtest | Reading package lists... Done | Building dependency tree | Reading state

Bug#978483: r-cran-pbkrtest: not installable in sid

2020-12-27 Thread Aurelien Jarno
Package: r-cran-pbkrtest Version: 0.5-0.1-1 Severity: serious r-cran-pbkrtest is currently not installable in sid: # apt-get install r-cran-pbkrtest Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that

Bug#978412: src:picolibc: fails to migrate to testing for too long: maintainer built arch:all binaries

2020-12-27 Thread Keith Packard
Paul Gevers writes: > Your package is only blocked because the arch:all binary package(s) > aren't built on a buildd. Unfortunately the Debian infrastructure > doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will > shortly do a no-changes source-only upload to DELAYED/15,

Bug#978478: tegrarcm: upload required for libcrypto++ transition

2020-12-27 Thread Sebastian Ramacher
Source: tegrarcm Version: 1.8-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Tags: sid bullseye tegrarcm is in non-free and is not buildable on the buillds. So it requires an upload to complete the libcrypto++ transition. Cheers -- Sebastian Ramacher signature.asc Description: PGP

Bug#978477: entropybroker: FTBFS on 32 bit architectures: error: narrowing conversion of ‘2147763207’ from ‘long unsigned int’ to ‘long int’ [-Wnarrowing]

2020-12-27 Thread Sebastian Ramacher
Source: entropybroker Version: 2.9-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org entropybroker FTBFS on 32 bit architectures: | In file included from ComScire_R2000KU/qwqng.cpp:32: |

Processed: tagging 978334

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 978334 + experimental Bug #978334 [src:php-finder-facade] php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage() Added tag(s) experimental. > thanks Stopping processing here. Please contact me if

Processed: tagging 978289

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 978289 + experimental Bug #978289 [src:pytest] pytest: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) experimental. > thanks Stopping processing here. Please contact me if you need

Processed: affects 978341

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 978341 src:node-recast src:node-ast-types Bug #978341 [node-babel7] node-recast: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: Could not find a declaration file for module '@babel/types'.

Bug#975202: marked as done (pikepdf: FTBFS: RuntimeError: Prohibited to create memoryview without Py_buffer)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 14:44:54 -0700 with message-id <871rfaappl@melete.silentflame.com> and subject line Patch applied has caused the Debian Bug report #975202, regarding pikepdf: FTBFS: RuntimeError: Prohibited to create memoryview without Py_buffer to be marked as done. This

Bug#978378: marked as done (php-gettext: FTBFS: test failed)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:33:22 + with message-id and subject line Bug#978378: fixed in php-gettext 1.0.12-3 has caused the Debian Bug report #978378, regarding php-gettext: FTBFS: test failed to be marked as done. This means that you claim that the problem has been dealt with.

Bug#976941: marked as done (python-prometheus-client: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:33:28 + with message-id and subject line Bug#976941: fixed in python-prometheus-client 0.9.0-1 has caused the Debian Bug report #976941, regarding python-prometheus-client: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test

Bug#978412: marked as done (src:picolibc: fails to migrate to testing for too long: maintainer built arch:all binaries)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:20:15 + with message-id and subject line Bug#978412: fixed in picolibc 1.4.7-2 has caused the Debian Bug report #978412, regarding src:picolibc: fails to migrate to testing for too long: maintainer built arch:all binaries to be marked as done. This

Bug#978349: marked as done (bitshuffle: FTBFS: opal_pmix_base_select failed)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978349, regarding bitshuffle: FTBFS: opal_pmix_base_select failed to be marked as done. This means that you

Bug#978385: marked as done (elpa: FTBFS: tests failed)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978385, regarding elpa: FTBFS: tests failed to be marked as done. This means that you claim that the problem

Bug#978374: marked as done (sundials: FTBFS: tests failed)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978374, regarding sundials: FTBFS: tests failed to be marked as done. This means that you claim that the

Bug#978332: marked as done (gpaw: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 --test-pytest "--test-args=-v -m ci" returned exit code 13)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978332, regarding gpaw: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9

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

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978329, regarding p4est: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be

Bug#978307: marked as done (scalapack: FTBFS: dh_auto_test: error: cd build-openmpi && make -j4 test ARGS\+=-j4 returned exit code 2)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978307, regarding scalapack: FTBFS: dh_auto_test: error: cd build-openmpi && make -j4 test ARGS\+=-j4

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

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978314, regarding mpgrafic: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be

Bug#978260: marked as done (xmds2: FTBFS: AssertionError: False is not true : Failed to execute compiled simulation correctly. Got returnCode 1;)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978260, regarding xmds2: FTBFS: AssertionError: False is not true : Failed to execute compiled simulation

Bug#978306: marked as done (med-fichier: FTBFS: dh_auto_test: error: cd build.python3.9 && make -j1 check VERBOSE=1 returned exit code 2)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978306, regarding med-fichier: FTBFS: dh_auto_test: error: cd build.python3.9 && make -j1 check VERBOSE=1

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

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978292, regarding superlu-dist: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test

Bug#978247: marked as done (ruby-mpi: FTBFS: ERROR: Test "ruby2.7" failed.)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978247, regarding ruby-mpi: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you

Bug#978211: marked as done (dune-common: FTBFS: tests failed)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978211, regarding dune-common: FTBFS: tests failed to be marked as done. This means that you claim that the

Bug#978205: marked as done (dune-grid: FTBFS: tests failed)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978205, regarding dune-grid: FTBFS: tests failed to be marked as done. This means that you claim that the

Bug#978193: marked as done (mpi4py: FTBFS: ld: cannot find -llmpe)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978193, regarding mpi4py: FTBFS: ld: cannot find -llmpe to be marked as done. This means that you claim that

Bug#978180: marked as done (dune-functions: FTBFS: tests failed)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 21:48:47 +0100 with message-id <20201227204847.ga24...@xanadu.blop.info> and subject line bug fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978180, regarding dune-functions: FTBFS: tests failed to be marked as done. This means that you claim that

Bug#978096: marked as done (libvolk2-dev: /usr/include/cpu_features/*.h is now packaged separately as libcpu-features-dev)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 20:49:04 + with message-id and subject line Bug#978096: fixed in volk 2.4.1-2 has caused the Debian Bug report #978096, regarding libvolk2-dev: /usr/include/cpu_features/*.h is now packaged separately as libcpu-features-dev to be marked as done. This

Bug#957575: marked as done (naev: ftbfs with GCC-10)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 20:48:56 + with message-id and subject line Bug#957575: fixed in naev 0.8.0-1 has caused the Debian Bug report #957575, regarding naev: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: atftp: diff for NMU version 0.7.git20120829-3.2

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > tags 970066 + patch Bug #970066 [src:atftp] atftp: CVE-2020-6097 Added tag(s) patch. > tags 970066 + pending Bug #970066 [src:atftp] atftp: CVE-2020-6097 Added tag(s) pending. -- 970066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970066 Debian Bug Tracking

Bug#970066: atftp: diff for NMU version 0.7.git20120829-3.2

2020-12-27 Thread Salvatore Bonaccorso
Control: tags 970066 + patch Control: tags 970066 + pending Dear maintainer, I've prepared an NMU for atftp (versioned as 0.7.git20120829-3.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Salvatore diff -u

Bug#964143: marked as done (schleuder: ftbfs with Rails 6 in experimental - Could not find 'activerecord' (~> 5.2) - did find: [activerecord-6.0.3.1])

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 19:48:48 + with message-id and subject line Bug#964143: fixed in schleuder 3.5.3-2 has caused the Debian Bug report #964143, regarding schleuder: ftbfs with Rails 6 in experimental - Could not find 'activerecord' (~> 5.2) - did find: [activerecord-6.0.3.1]

Bug#933948: Config value incorrectly parsed in init.d script

2020-12-27 Thread Norbert Harrer
Hi Markus. I replaced my init scripts with the versions from your merge. And tried with various combinations of spaces and quotes. Works very well. Great regex/escape-fu. Best Regads, Norbert. On 27.12.2020 14:32, Markus Wanner wrote: Control: -1 severity grave Control: -1 tags +pending

Processed: bug 978315 is forwarded to bug-gnu-gett...@gnu.org

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 978315 bug-gnu-gett...@gnu.org Bug #978315 [src:dasher] dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Ignoring request to change the forwarded-to-address of bug#978315 to the same value > thanks

Bug#978315: xgettext complains about UTF conformance of strings not marked for translation

2020-12-27 Thread Bruno Haible
Hi Santiago, Samuel, > The upload of gettext 0.21 for Debian unstable has made package "dasher", > maintained by Samuel Thibault (in Cc), not to build anymore, as reported here > by Lucas Nussbaum: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978315 > > We are not sure where is exactly

Bug#978452: python3-opencv: missing dependency on libcharls2

2020-12-27 Thread Sandro Tosi
Package: python3-opencv Version: 4.5.1+dfsg-1 Severity: grave Hello, i've just upgraded to opencv 4.5.1 and when importing the python module, i got this error: Traceback (most recent call last): File "tool", line 10, in import cv2 ImportError: libcharls.so.2: cannot open shared object

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

2020-12-27 Thread Roger Shimizu
On Thu, Dec 24, 2020 at 6:33 AM Hans-Christoph Steiner wrote: > > As far as I know, the blocker for fastbook is android-platform-art. It > has a crazy upstream build system. Right now, it almost building, but > the build is currently dying on this error: I fixed the above issue by branch

Processed: reopening 718272

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 718272 Bug #718272 {Done: Jonas Smedegaard } [src:bitcoin] upstream does not support stable releases (block migration to testing) Bug reopened Ignoring request to alter fixed versions of bug #718272 to the same values previously set >

Processed: unarchiving 718272

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 718272 Bug #718272 {Done: Jonas Smedegaard } [src:bitcoin] upstream does not support stable releases (block migration to testing) Unarchived Bug 718272 > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: severity of 970066 is grave

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 970066 grave Bug #970066 [src:atftp] atftp: CVE-2020-6097 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 970066:

Bug#977960: dangling /usr/share/javascript/jquery/jquery.js symlink

2020-12-27 Thread Thorsten Glaser
Package: node-jquery Version: 3.5.1+dfsg+~3.5.5-3 Followup-For: Bug #977960 X-Debbugs-Cc: t...@mirbsd.de Even for the latest versions of these packages, adequate reports: node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.js -> ../../nodejs/jquery/dist/jquery.js node-jquery:

Bug#977960: dangling /usr/share/javascript/jquery/jquery.js symlink

2020-12-27 Thread Thorsten Glaser
Package: libjs-jquery Version: 3.5.1+dfsg+~3.5.5-3 Followup-For: Bug #977960 X-Debbugs-Cc: t...@mirbsd.de Even for the latest versions of these packages, adequate reports: node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.js -> ../../nodejs/jquery/dist/jquery.js node-jquery:

Processed: Bug#978354 marked as pending in mozjs

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978354 [src:mozjs78] mozjs78: FTBFS: dwz: debian/libmozjs-78-0/usr/lib/x86_64-linux-gnu/libmozjs-78.so.78.4.0: Couldn't find DIE referenced by DW_AT_abstract_origin Added tag(s) pending. -- 978354:

Bug#978354: marked as pending in mozjs

2020-12-27 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #978354 in mozjs 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 976134 is forwarded to https://github.com/borgbase/vorta/issues/748

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 976134 https://github.com/borgbase/vorta/issues/748 Bug #976134 {Done: Nicholas D Steeves } [src:vorta] vorta: flaky autopkgtest Set Bug forwarded-to-address to 'https://github.com/borgbase/vorta/issues/748'. > thanks Stopping

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

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 17:19:27 + with message-id and subject line Bug#978308: fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978308, regarding pyzoltan: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to be

Bug#978203: marked as done (fckit: FTBFS: dh_auto_test: error: cd debian/build-gfortran && make -j4 test ARGS\+=-j4 returned exit code 2)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 17:19:27 + with message-id and subject line Bug#978203: fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978203, regarding fckit: FTBFS: dh_auto_test: error: cd debian/build-gfortran && make -j4 test ARGS\+=-j4 returned exit code 2 to be marked

Bug#978066: marked as done (pmix: breaks openmpi autopkgtest)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 17:19:27 + with message-id and subject line Bug#978066: fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978066, regarding pmix: breaks openmpi autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#978022: marked as done (libopenmpi3 Runtime failure opal_pmix_base_select failed)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 17:19:27 + with message-id and subject line Bug#978022: fixed in openmpi 4.1.0-2 has caused the Debian Bug report #978022, regarding libopenmpi3 Runtime failure opal_pmix_base_select failed to be marked as done. This means that you claim that the problem

Processed: Re: Bug#970878: ghostscript breaks doc-rfc autopkgtest: segmentation fault

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #970878 [src:ghostscript] ghostscript breaks doc-rfc autopkgtest: segmentation fault Severity set to 'important' from 'serious' -- 970878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970878 Debian Bug Tracking System Contact

Bug#970878: ghostscript breaks doc-rfc autopkgtest: segmentation fault

2020-12-27 Thread Jonas Smedegaard
Control: severity -1 important Quoting Paul Gevers (2020-12-04 22:14:44) > On Fri, 23 Oct 2020 12:07:27 +0200 Jonas Smedegaard wrote: > > > Of course, I'm biased since I'm the maintainer of doc-rfc, but I think > > > it's a fair assesment. > > > > For the record it is not a PDF file but a

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

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 18:05:54 +0100 with message-id <20201227170554.GA31040@nuc> has caused the report #978315, regarding dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as having been forwarded to the upstream software author(s)

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-27 Thread Jonas Smedegaard
Control: severity -1 important Quoting Graham Inggs (2020-11-25 09:59:36) > The upload of link-grammar 5.8.0-1 intermittently FTBFS on several > architectures, e.g. arm64 [1], armel [2] and ppc64 [3]. The failures > all happen during the multi-thread test with various errors: > double free or

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #975696 [src:link-grammar] link-grammar: multi-thread test fails Severity set to 'important' from 'serious' -- 975696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975696 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#978315: xgettext complains about UTF conformance of strings not marked for translation

2020-12-27 Thread Santiago Vila
Greetings. The upload of gettext 0.21 for Debian unstable has made package "dasher", maintained by Samuel Thibault (in Cc), not to build anymore, as reported here by Lucas Nussbaum: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978315 We are not sure where is exactly the problem (either

Bug#933948: too many split f the same things

2020-12-27 Thread PICCORO McKAY Lenz
El dom, 27 de dic. de 2020 a la(s) 12:42, Markus Wanner (mar...@bluegap.ch) escribió: > On 12/27/20 5:22 PM, PICCORO McKAY Lenz wrote: > > > it seems has several inter-dependencies.. or as you mantainers called > > circular dependences.. so i'm unable to check in production cos does not > > buil

Processed: Bug#978263 marked as pending in python-django

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978263 [src:python-django] python-django: FTBFS: AssertionError: 'code_sample.py:4' not found in 'processing locale de\n' Added tag(s) pending. -- 978263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978263 Debian Bug Tracking System

Bug#978263: marked as pending in python-django

2020-12-27 Thread Chris Lamb
Control: tag -1 pending Hello, Bug #978263 in python-django 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: golang-github-henrydcase-nobs: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_build: error: cd obj-powerpc64le-linux-gnu && go install -trimpath -v -p 160

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 976913 https://github.com/henrydcase/nobs/issues/37 Bug #976913 [src:golang-github-henrydcase-nobs] golang-github-henrydcase-nobs: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_build: error: cd obj-powerpc64le-linux-gnu && go

Bug#933948: too many split f the same things

2020-12-27 Thread Markus Wanner
On 12/27/20 5:22 PM, PICCORO McKAY Lenz wrote: the review needs registration etc etc..  i try to analize but it has too complicated things for quick review.. It's a gitlab instance used for Debian packaging. Registration is free. For your convenience, I'm attaching the patch. Note that

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

2020-12-27 Thread James McCoy
On Sun, Dec 27, 2020 at 10:46:24AM -0500, Justin Erenkrantz wrote: > Thanks.  I expect that this might be due to the last change - erroring out on > an expired self-signed root cert.  Though I thought we didn’t check in a root > cert for our test chain...could Debian’s packaging be including a

Bug#933948: too many split f the same things

2020-12-27 Thread PICCORO McKAY Lenz
the review needs registration etc etc.. i try to analize but it has too complicated things for quick review.. it seems has several inter-dependencies.. or as you mantainers called circular dependences.. so i'm unable to check in production cos does not buil in a OBS environment.. again as i

Processed: bug 978348 is forwarded to https://github.com/OpenPrinting/ipp-usb/issues/18, tagging 978348

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 978348 https://github.com/OpenPrinting/ipp-usb/issues/18 Bug #978348 [src:ipp-usb] ipp-usb: FTBFS: src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use int32(err) (type int32) as type _Ctype_int in argument to

Bug#978071: marked as done (entropybroker FTBFS with Crypto++ 8.3.0)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 16:03:27 + with message-id and subject line Bug#978071: fixed in entropybroker 2.9-4 has caused the Debian Bug report #978071, regarding entropybroker FTBFS with Crypto++ 8.3.0 to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 963640

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 963640 + patch Bug #963640 [src:jansson] jansson: FTBFS with Sphinx 3.1: TypeError: add_directive() takes from 3 to 4 positional arguments but 5 were given Added tag(s) patch. > thanks Stopping processing here. Please contact me if you

Bug#978444: FTBFS: fails to contact repl server in tests

2020-12-27 Thread David Bremner
Source: racket-mode Version: 20201227git0-1 Severity: serious Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: tag -1 help This is a different test problem than Lucas reported in #978345. I can duplicate the bug in sbuild, but if I use -

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

2020-12-27 Thread Justin Erenkrantz
Thanks. I expect that this might be due to the last change - erroring out on an expired self-signed root cert. Though I thought we didn’t check in a root cert for our test chain...could Debian’s packaging be including a cert for testing? I will try to take a look this week with Debian sid...I

Processed: Re: Bug#977657 closed by Debian FTP Masters (reply to Lev Lamberov ) (Bug#977657: fixed in swi-prolog 8.2.3+dfsg-2)

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 977657 Bug #977657 {Done: Lev Lamberov } [swi-prolog] swi-prolog: FTBFS with OpenSSL 1.1.1i 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug

Bug#977657: closed by Debian FTP Masters (reply to Lev Lamberov ) (Bug#977657: fixed in swi-prolog 8.2.3+dfsg-2)

2020-12-27 Thread Kurt Roeckx
reopen 977657 thanks Hi, The CI test still fails with 1.1.1i: Testing package ssl:ssl Script test_ssl.pl failed: Unknown message: exit(1) % PL-Unit: ssl_options ... done % PL-Unit: ssl_server . done % PL-Unit: ssl_keys . done % PL-Unit: ssl_certificates .

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

2020-12-27 Thread James McCoy
On Sat, Dec 26, 2020 at 11:09:41PM +0100, Lucas Nussbaum wrote: > Source: serf > Version: 1.3.9-8 > [...] > > Trailer-Test: f > > ...F.. > > > > There was 1 failure: > > 1) test_ssl_handshake: test/test_util.c:456: expected <0> but was

Processed: Close #976381

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 976381 2.4.4-7 Bug #976381 {Done: =?utf-8?q?Rafael_Laboissi=C3=A8re?= } [src:mathgl] FTBFS against octave 6: mathglOCTAVE_wrap.cxx:1768:10: error: ‘oct_mach_info’ has not been declared Marked as fixed in versions mathgl/2.4.4-7. > End of

Processed: retitle 978353 to serf: FTBFS: tests failed with OpenSSL 1.1.1i

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 978353 serf: FTBFS: tests failed with OpenSSL 1.1.1i Bug #978353 [src:serf] serf: FTBFS: tests failed Changed Bug title to 'serf: FTBFS: tests failed with OpenSSL 1.1.1i' from 'serf: FTBFS: tests failed'. > thanks Stopping processing

Bug#978441: singularity-container: FTBFS: cannot find package "github.com/kr/pty"

2020-12-27 Thread Cyril Brulebois
Source: singularity-container Version: 3.5.2+ds1 Severity: serious Justification: FTBFS Hi, While trying to update the golang-github-gin-gonic-gin-dev package, ratt picked up 35 packages, and yours triggers 1 of the 3 resulting failures. Trying to build it in a pristine unstable chroot led to

Processed: affects 978384, affects 978341

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 978384 node-recast Bug #978384 [node-babel7] node-ast-types: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: Could not find a declaration file for module '@babel/types'.

Bug#978263: python-django: FTBFS: AssertionError: 'code_sample.py:4' not found in 'processing locale de\n'

2020-12-27 Thread Dmitry Shachnev
Control: forwarded -1 https://code.djangoproject.com/ticket/31850 Control: tags -1 + fixed-upstream On Sat, Dec 26, 2020 at 10:45:33PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > >

Processed: Re: Bug#978263: python-django: FTBFS: AssertionError: 'code_sample.py:4' not found in 'processing locale de\n'

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://code.djangoproject.com/ticket/31850 Bug #978263 [src:python-django] python-django: FTBFS: AssertionError: 'code_sample.py:4' not found in 'processing locale de\n' Set Bug forwarded-to-address to 'https://code.djangoproject.com/ticket/31850'. >

  1   2   3   >