Bug#966904: pfstools: FTBFS: array2d.h:173:9: error: ‘__assert_fail’ was not declared in this scope; did you mean ‘MagickCore::__assert_fail’?

On 24/09/2020 06:25, Andreas Metzler wrote: On 2020-08-28 peter green wrote: Tags 966904 +patch thanks The issue is that Magick++.h (indirectly) includes assert.h inside a namespace. [...] I would argue that is a bug in imagemagick and have filed bugs in both Debian and upstream as

Bug#966904: pfstools: FTBFS: array2d.h:173:9: error: ‘__assert_fail’ was not declared in this scope; did you mean ‘MagickCore::__assert_fail’?

On 2020-08-28 peter green wrote: > Tags 966904 +patch > thanks > The issue is that Magick++.h (indirectly) includes assert.h inside a > namespace. [...] > I would argue that is a bug in imagemagick and have filed bugs in both Debian > and upstream as >

Bug#970768: torbrowser-launcher: error while checking version number after TorBrowser 10.0 release

Hi Roger, Чт 24 сен 2020 @ 01:43 Roger Shimizu : > Dear Lev, > > Thanks for your report! > > On Wed, Sep 23, 2020 at 4:00 PM Lev Lamberov wrote: >> >> Package: torbrowser-launcher >> Version: 0.3.2-13 >> Severity: grave >> Tags: upstream >> Justification: renders package unusable >> >> Dear

Bug#970664: libvte-2.91-0: Terminal not displaying correctly

Thanks!. El mié., 23 sept. 2020 a las 6:02, Simon McVittie () escribió: > > Control: forwarded -1 https://gitlab.gnome.org/GNOME/vte/-/issues/284 > > On Wed, 23 Sep 2020 at 08:22:48 +0100, Simon McVittie wrote: > > I think it's caused by > > the change made for

Bug#953875: Debian FTP Masters

It's not solved on my end with Debian 10... here is what I see when I try to install git-all. ``` root:/home/admin# apt update && apt install git-all ... The following packages will be REMOVED: libpam-systemd systemd-sysv ``` Please check my previous message for context.

Bug#970798: [Pkg-net-snmp-devel] Bug#970798: net-snmp: Not built on buildd: arch all binaries, source-only upload required

On Thu, 24 Sep 2020 at 01:27, Chris Hofstaedtler wrote: > * Not built on buildd: arch amd64 binaries uploaded by csmall > * Not built on buildd: arch all binaries uploaded by csmall, a new > source-only upload is needed to allow migration > > While the first one could be fixed by a binNMU,

Bug#970820: missing bid_functions.h header

Package: libintelrdfpmath-dev Version: 2.0u2-2 Severity: serious Dear Maintainer, The bid_functions.h header is not included in the package. This header is required when compiling a program against the library. In particular, it defines the BID_UINT32, BID_UINT64 and BID_UINT128 types, and

Bug#950839: marked as done (reprounzip autopkg test fails with python 3.8)

Your message dated Wed, 23 Sep 2020 19:48:31 + with message-id and subject line Bug#950839: fixed in reprounzip 1.0.16-1 has caused the Debian Bug report #950839, regarding reprounzip autopkg test fails with python 3.8 to be marked as done. This means that you claim that the problem has been

Bug#951957: marked as done (reprounzip: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13)

Your message dated Wed, 23 Sep 2020 19:48:31 + with message-id and subject line Bug#950839: fixed in reprounzip 1.0.16-1 has caused the Debian Bug report #950839, regarding reprounzip: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13 to be

Bug#943442: marked as done (reprozip needs a new upstream version for Python 3.8)

Your message dated Wed, 23 Sep 2020 19:48:38 + with message-id and subject line Bug#943442: fixed in reprozip 1.0.16-1 has caused the Debian Bug report #943442, regarding reprozip needs a new upstream version for Python 3.8 to be marked as done. This means that you claim that the problem has

Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

Source: mrpt Version: 1:2.1.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: Builds of mrpt on mips64el run into a timeout: | [ 84%] Building CXX object libs/slam/CMakeFiles/slam.dir/src/registerAllClasses.cpp.o | cd

Bug#963381: marked as done (rally FTBFS with mock 4.x)

Your message dated Wed, 23 Sep 2020 19:35:11 + with message-id and subject line Bug#963381: fixed in rally 3.1.0-1 has caused the Debian Bug report #963381, regarding rally FTBFS with mock 4.x to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#970334: marked as done (wslay: autopkgtest needs update for new version of cmake: warning on stderr)

Your message dated Wed, 23 Sep 2020 19:35:24 + with message-id and subject line Bug#970334: fixed in wslay 1.1.1-2 has caused the Debian Bug report #970334, regarding wslay: autopkgtest needs update for new version of cmake: warning on stderr to be marked as done. This means that you claim

Bug#963381: marked as pending in rally

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

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

Bug#961373: slic3r-prusa FTBFS on armhf: cc1plus: out of memory

> cc1plus: out of memory allocating 9048820 bytes after a total of 77602816 > bytes How about increasing the memory on the build machine or preventing a parallel make? 90MB memory usage doesn't sound dramatic to me.

Bug#963392: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

Hello again Andreas, This [commit] now rectifies the build issue for r-cran-prophet. I can build r-cran-prophet successfully after re-building r-cran-rstan with the new patch. Within r-cran-prophet: $ autopkgtest . -- null [TRUNCATED] /usr/bin/ld: cannot find -lStanHeaders collect2: error: ld

Bug#969436: Fixing wrong changelog entry

Hi Keith, On 23-09-2020 15:17, Keith Max wrote: > This small mess has been existing couple of days now. Is it possible to > fix this package please? There are a bunch of packages stuck in unstable > because of this situation this package is in. >   > If I'm correct, the changelog of -2 closed the

Bug#970768: torbrowser-launcher: error while checking version number after TorBrowser 10.0 release

Dear Lev, Thanks for your report! On Wed, Sep 23, 2020 at 4:00 PM Lev Lamberov wrote: > > Package: torbrowser-launcher > Version: 0.3.2-13 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > > because of faulty version number check,

Bug#970809: python3-venv is gone

Package: pipx Version: 0.12.3.1-3 Severity: serious Tags: sid bullseye This package depends or build-depends on python3-venv, which is gone upstream. Please remove or re-implement that usage.

Bug#970807: python3-venv is gone

Package: xonsh Version: 0.9.20+dfsg-1 Severity: serious Tags: sid bullseye This package depends or build-depends on python3-venv, which is gone upstream. Please remove or re-implement that usage.

Bug#970808: python3-venv is gone

Package: thonny Version: 3.2.7-1 Severity: serious Tags: sid bullseye This package depends or build-depends on python3-venv, which is gone upstream. Please remove or re-implement that usage.

Bug#970810: python3-venv is gone

Package: dh-virtualenv Version: 1.2.1-1 Severity: serious Tags: sid bullseye This package depends or build-depends on python3-venv, which is gone upstream. Please remove or re-implement that usage.

Bug#970806: python3-venv is gone

Package: yubikey-manager Version: 3.1.1-1 Severity: serious Tags: sid bullseye This package depends or build-depends on python3-venv, which is gone upstream. Please remove or re-implement that usage.

Bug#970768: marked as done (torbrowser-launcher: error while checking version number after TorBrowser 10.0 release)

Your message dated Wed, 23 Sep 2020 16:18:33 + with message-id and subject line Bug#970768: fixed in torbrowser-launcher 0.3.2-14~exp1 has caused the Debian Bug report #970768, regarding torbrowser-launcher: error while checking version number after TorBrowser 10.0 release to be marked as

Bug#968046: Workaround

I hit this error when just upgrading unstable container some months old. It as not obvious to me. Recommended workaround is: apt-get upgrade python apt-get upgrade Is there reason it is not yet fixed? -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemen...@redhat.com

Bug#963392: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

Hello Andreas, I see the error within r-cran-prophet's build. It seems like this issue stems from r-cran-rstan (as the call stack shows). Specifically: $ grep -r "system.file(\"lib\"" R/plugin.R:RcppParallel_pkg_libs <- system.file("lib", .Platform$r_arch, R/plugin.R:rstan_StanServices

Bug#970798: net-snmp: Not built on buildd: arch all binaries, source-only upload required

Package: net-snmp Version: 5.9+dfsg-2 Severity: serious Justification: testing migration blocked Dear Maintainer, your package is prohibited from migrating to testing for these reasons: * Not built on buildd: arch amd64 binaries uploaded by csmall * Not built on buildd: arch all binaries

Bug#967194: pam-python/libpam-mklocaluser/debian-edu-config python3 migration.

Hi, Am Samstag, 19. September 2020 schrieb peter green: > The debian python maintainers are trying to phase out python 2. > > python 2 has been granted a stay of execution as some important software > requires it to build. However we should still > be attempting to get rid of use at runtime if

Bug#963392: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

Hi Shayan, On Wed, Sep 23, 2020 at 01:27:52PM +0100, Shayan Doust wrote: > The [commit] is now pushed for r-cran-rcppparallel, which fixes the "TBB > library > not found" error thrown for r-cran-rstanarm. > > Just a note that I did not make it through the entire build process. I gave > the >

Bug#969436: Fixing wrong changelog entry

Hi guys, This small mess has been existing couple of days now. Is it possible to fix this package please? There are a bunch of packages stuck in unstable because of this situation this package is in. If I'm correct, the changelog of -2 closed the wrong bug number. Then the wrong changelog entry

Bug#963392: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

Hello Andreas, The [commit] is now pushed for r-cran-rcppparallel, which fixes the "TBB library not found" error thrown for r-cran-rstanarm. Just a note that I did not make it through the entire build process. I gave the build 40 mins before giving up. Compiling r-cran-stanarm used almost all of

Processed: wait for node-bootstrap-switch

Processing commands for cont...@bugs.debian.org: > block 970782 by 970786 Bug #970782 [ruby-bootstrap-switch-rails] ruby-bootstrap-switch-rails: 3.3.4 version is broken, downgrade to 3.3.3 970782 was not blocked by any bugs. 970782 was not blocking any bugs. Added blocking bug(s) of 970782:

Bug#963392: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

Hi Shayan, On Tue, Sep 22, 2020 at 06:44:39PM +0100, Shayan Doust wrote: > I'll try to write a simple patch for this hook file. For a Debian package, > this > assumption for library location is plain wrong. That would be really great. My guess is that once this is solved also r-cran-prophet[1]

Processed: bug 970782 is forwarded to https://github.com/Bttstrp/bootstrap-switch/issues/691

Processing commands for cont...@bugs.debian.org: > forwarded 970782 https://github.com/Bttstrp/bootstrap-switch/issues/691 Bug #970782 [ruby-bootstrap-switch-rails] ruby-bootstrap-switch-rails: 3.3.4 version is broken, downgrade to 3.3.3 Ignoring request to change the forwarded-to-address of

Processed: add forwarded info

Processing commands for cont...@bugs.debian.org: > forwarded 970782 https://github.com/Bttstrp/bootstrap-switch/issues/691 Bug #970782 [ruby-bootstrap-switch-rails] ruby-bootstrap-switch-rails: 3.3.4 version is broken, downgrade to 3.3.3 Set Bug forwarded-to-address to

Bug#957753: marked as done (rdkit: ftbfs with GCC-10)

Your message dated Wed, 23 Sep 2020 12:34:18 +0200 with message-id <5f6b24ab.1c69fb81.9bc76.0...@mx.google.com> and subject line Re: [Debichem-devel] Bug#957753: rdkit: ftbfs with GCC-10 has caused the Debian Bug report #957753, regarding rdkit: ftbfs with GCC-10 to be marked as done. This means

Bug#970782: ruby-bootstrap-switch-rails: 3.3.4 version is broken, downgrade to 3.3.3

Package: ruby-bootstrap-switch-rails Version: 3.3.4-1 Severity: grave Control: forwarded -1 https://github.com/Bttstrp/bootstrap-switch/issues/691 It does not seem to be fixed in 3.3.5 as well (https://github.com/diaspora/diaspora/pull/8149) So we need to downgrade it to 3.3.3 which works.

Bug#966523: marked as done (r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’)

Your message dated Wed, 23 Sep 2020 11:48:25 +0200 with message-id <20200923094825.gi...@an3as.eu> and subject line Re: Potential gcc-10 issue "error: conflicting types for ‘uintptr_t’" (Was: Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’) has caused the

Bug#970334: wslay: autopkgtest needs update for new version of cmake: warning on stderr

Hi, please find a possible patch attached for this issue: * Paul Gevers [200923 09:20]: > autopkgtest [18:08:26]: test build1: - - - - - - - - - - results - - - > - - - - - - - > build1 FAIL stderr: CMake Warning (dev) at >

Processed: bug 970334 is forwarded to https://github.com/tatsuhiro-t/wslay/issues/59

Processing commands for cont...@bugs.debian.org: > forwarded 970334 https://github.com/tatsuhiro-t/wslay/issues/59 Bug #970334 [src:wslay] wslay: autopkgtest needs update for new version of cmake: warning on stderr Set Bug forwarded-to-address to

Bug#967212: marked as done (solfege: Unversioned Python removal in sid/bullseye)

Your message dated Wed, 23 Sep 2020 09:06:32 + with message-id and subject line Bug#967212: fixed in solfege 3.23.4-9 has caused the Debian Bug report #967212, regarding solfege: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#970664: libvte-2.91-0: Terminal not displaying correctly

Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/vte/-/issues/284 Bug #970664 [libvte-2.91-0] libvte-2.91-0: Terminal not displaying correctly in non-default themes Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/vte/-/issues/284'. -- 970664:

Bug#970664: libvte-2.91-0: Terminal not displaying correctly

Control: forwarded -1 https://gitlab.gnome.org/GNOME/vte/-/issues/284 On Wed, 23 Sep 2020 at 08:22:48 +0100, Simon McVittie wrote: > I think it's caused by > the change made for . Yes, it is. I've contacted upstream and suggested a change that

Bug#966523: Potential gcc-10 issue "error: conflicting types for ‘uintptr_t’" (Was: Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’)

Apologies for my delayed response. We will investigate this and try to fix it soon. Regards Wei Professor Wei Shi, PhD Head, Bioinformatics and Cancer Genomics Laboratory Olivia Newton-John Cancer Research Institute Level 5, ONJ Centre, 145 Studley Road, Heidelberg Vic 3084 Australia E:

Bug#965007: pitivi: ships a copy of gstreamer libraries

On Wed, 23 Sep 2020 10:45:41 +0300 Sebastian =?ISO-8859-1?Q?Dr=F6ge?= wrote: > On Wed, 2020-09-23 at 09:36 +0200, Gianfranco Costamagna wrote: > > > > Hello, I found that pitivi was using the gst-transcoder only if not found > > on the system, > > and upstream commit

Bug#966523: Potential gcc-10 issue "error: conflicting types for ‘uintptr_t’" (Was: Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’)

On Wed, Sep 23, 2020 at 7:40 AM Andreas Tille wrote: > unfortunately upstream has not yet responded to this mail. My guess is > that this is a general gcc-10 issue. > > Any hint how to solve this? It looks like r-base-core is duplicating standard C types and defining them incorrectly. If you

Bug#965007: pitivi: ships a copy of gstreamer libraries

On Wed, 2020-09-23 at 09:36 +0200, Gianfranco Costamagna wrote: > > Hello, I found that pitivi was using the gst-transcoder only if not found on > the system, > and upstream commit "51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e" worked in > fixing that. > > I prepared a version on Debomatic with

Bug#963637: marked as done (rdkit: FTBFS with Sphinx 3.1: ! LaTeX Error: Too deeply nested.)

Your message dated Wed, 23 Sep 2020 07:49:55 + with message-id and subject line Bug#963637: fixed in rdkit 202003.4-2 has caused the Debian Bug report #963637, regarding rdkit: FTBFS with Sphinx 3.1: ! LaTeX Error: Too deeply nested. to be marked as done. This means that you claim that the

Bug#964656: marked as done (rdkit: FTBFS: elog.h:224:34: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Wed, 23 Sep 2020 07:49:55 + with message-id and subject line Bug#964656: fixed in rdkit 202003.4-2 has caused the Debian Bug report #964656, regarding rdkit: FTBFS: elog.h:224:34: error: format not a string literal and no format arguments [-Werror=format-security] to be

Processed: Potential gcc-10 issue "error: conflicting types for ‘uintptr_t’" (Was: Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’)

Processing control commands: > tags -1 help Bug #966523 [src:r-bioc-rsubread] r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’ Added tag(s) help. > tags -1 upstream Bug #966523 [src:r-bioc-rsubread] r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’

Bug#966523: Potential gcc-10 issue "error: conflicting types for ‘uintptr_t’" (Was: Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’)

Control: tags -1 help Control: tags -1 upstream Control: forwarded -1 Wei Shi , Yang Liao , Gordon K Smyth Hi, unfortunately upstream has not yet responded to this mail. My guess is that this is a general gcc-10 issue. Any hint how to solve this? Kind regards Andreas. On Tue, Sep

Bug#965007: pitivi: ships a copy of gstreamer libraries

On Mon, 17 Aug 2020 10:21:48 -0300 Antonio Terceiro wrote: > Control: reassign -1 pitivi > Control: retitle -1 pitivi: ships a copy of gstreamer libraries > Control: found -1 0.999-2 > > On Mon, Aug 17, 2020 at 03:27:21PM +0300, Sebastian Dröge wrote: > > On Mon, 2020-08-17 at 09:10 -0300,

Processed: Re: Bug#970664: libvte-2.91-0: Terminal not displaying correctly

Processing control commands: > retitle -1 libvte-2.91-0: Terminal not displaying correctly in non-default > themes Bug #970664 [libvte-2.91-0] libvte-2.91-0: Terminal not displaying correctly Changed Bug title to 'libvte-2.91-0: Terminal not displaying correctly in non-default themes' from

Bug#970664: libvte-2.91-0: Terminal not displaying correctly

Control: retitle -1 libvte-2.91-0: Terminal not displaying correctly in non-default themes Control: tags -1 = confirmed On Wed, 23 Sep 2020 at 00:02:09 -0300, Fabián Inostroza wrote: > The issue happens with some themes, normally I use Numix from the > repositories, when using HighContrast or

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 970768 + Bug #970768 [torbrowser-launcher] torbrowser-launcher: error while checking version number after TorBrowser 10.0 release Requested to add no tags; doing nothing. > thanks Stopping processing here. Please contact me if you need

Bug#970768: Acknowledgement (torbrowser-launcher: error while checking version number after TorBrowser 10.0 release)

I've tested the patch proposed in upstream merge request and it solves the problem. Cheers! Lev

Bug#970768: torbrowser-launcher: error while checking version number after TorBrowser 10.0 release

Package: torbrowser-launcher Version: 0.3.2-13 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, because of faulty version number check, torbrowser-launcher cannot correctly handle TorBrowser 10.0 release. Now it shows the following error message: The