Bug#994269: marked as done (node-jest/experimental FTBFS: build hang)

2021-09-25 Thread Debian Bug Tracking System
Your message dated Sun, 26 Sep 2021 04:50:22 + with message-id and subject line Bug#994269: fixed in node-jest 27.2.1~ds+~cs67.45.24-1 has caused the Debian Bug report #994269, regarding node-jest/experimental FTBFS: build hang to be marked as done. This means that you claim that the problem

Bug#992527: [Pkg-javascript-devel] Bug#992527: node-srs: FTBFS with GDAL 3.3.1

2021-09-25 Thread Sebastiaan Couwenberg
On Wed, 15 Sep 2021 18:49:12 +0200 Yadd wrote: > Le 15/09/2021 à 16:10, Sebastiaan Couwenberg a écrit : > > Since this only exists as part of the node-carto dependency chain, > > removing this package along with node-millstone and node-carto is > > probably a better idea than spending time fixing

Processed: tagging 995038, tagging 995040, tagging 994859, tagging 994877, tagging 994930, tagging 994937 ...

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 995038 + sid bookworm Bug #995038 [src:ddccontrol] ddccontrol FTBFS: autoreconf: error: intltoolize failed with exit status: 1 Added tag(s) bookworm and sid. > tags 995040 + sid bookworm Bug #995040 [src:iverilog] iverilog FTBFS: configure:

Processed: merging 995015 995016

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 995015 995016 Bug #995015 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Bug #995016 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Merged 995015 995016 > thanks Stopping processing here. Please contact me if you need

Bug#993978: marked as done (linux-image-5.10.0-8-arm64: host hangs after some time of use)

2021-09-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Sep 2021 22:02:07 + with message-id and subject line Bug#993978: fixed in linux 5.10.46-5 has caused the Debian Bug report #993978, regarding linux-image-5.10.0-8-arm64: host hangs after some time of use to be marked as done. This means that you claim that the

Processed: bug 995073 is forwarded to https://github.com/yarnpkg/berry/issues/3496

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 995073 https://github.com/yarnpkg/berry/issues/3496 Bug #995073 [gitlab] gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2". Set Bug forwarded-to-address to

Bug#995073: gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2".

2021-09-25 Thread Pirate Praveen
On 25/9/21 11:11 PM, Ondrej Zary wrote: > Package: gitlab > Version: 13.12.9+ds1-1~fto10+1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > installing gitlab 13.12.9+ds1-1~fto10+1 on buster amd64 fails with: > > Installing node modules... > Resolving 2.4.2 to a

Bug#994551: libcifpp1: please split off static files to separate package

2021-09-25 Thread Étienne Mollier
Hi Nilesh, Nilesh Patra, on 2021-09-25: > > Hi Étienne, all, > > > I took the liberty to implement the change you suggest, and push > > to Salsa [1]. > > I do not see your changes on salsa, the last commit is 3 months old > there. > Did you forget to push? Yes, I forgot, sorry about that; I

Bug#993627: marked as done (ndpi: Bus error on armhf when built on 64bit hardware)

2021-09-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Sep 2021 20:35:11 + with message-id and subject line Bug#993627: fixed in ndpi 4.0-3 has caused the Debian Bug report #993627, regarding ndpi: Bus error on armhf when built on 64bit hardware to be marked as done. This means that you claim that the problem has been

Bug#995085: dlt-viewer: missing installed headers in -dev packages

2021-09-25 Thread Gianfranco Costamagna
Source: dlt-viewer Version: 2.21.2+dfsg-2 Severity: serious tags: patch Fixed: 2.21.2+dfsg-3 Hello, the package doesn't install lots of header files, see https://bugs.debian.org/993564 for more information. G.

Bug#995014: linux/linux-signe-* break zfs-linux autopkgtest: None of the expected "capability" interfaces were detected

2021-09-25 Thread Paul Gevers
Hi, On 24-09-2021 22:02, Salvatore Bonaccorso wrote: > zfs-linux needs an update to be compatible with Linux 5.14 and above. > This should be resolved in the 2.0.6 version upstream which was > uploaded earlier to unstable, at least according to > >

Bug#992914: libassa: FTBFS due to RPC removal from glibc

2021-09-25 Thread Shane McDonald
Thanks for the bug report and patch. I've come up with an alternate patch that only affects the utils/ directory. This patch will show up in my next upload in the next few days (currently on mentors.debian.net). On Wed, 25 Aug 2021 00:03:42 +0200 Aurelien Jarno wrote: > Source: libassa >

Bug#995020: macaulay2: autopkgtest regression and flaky test: SIGSEGV

2021-09-25 Thread Paul Gevers
Hi Torrance, On 25-09-2021 04:56, Torrance, Douglas wrote: > There's a problem though -- this macaulay2 autopkgtest regression is now > preventing ntl from migrating to testing! [1]  This seems like a chicken > and > egg situation -- we need it to migrate for the tests to pass, but we need > the

Processed: un-confuse bts

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 994265 src:pypy 7.3.5+dfsg-2 Bug #994265 {Done: Stefano Rivera } [src:pypy, src:python-virtualenv] pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded Bug reassigned from package

Bug#994971: NVENC issue

2021-09-25 Thread Alejandro Bringas
It has also affected the NVENC compatibility, using OBS-Studio it simply does not detect it and gives an error when wanting to record, it had to be reverted to the previous version.

Bug#995032: marked as done (GNOME components segfault as a result of libffi transition)

2021-09-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Sep 2021 17:49:33 + with message-id and subject line Bug#995032: fixed in gobject-introspection 1.70.0-2 has caused the Debian Bug report #995032, regarding GNOME components segfault as a result of libffi transition to be marked as done. This means that you claim

Bug#995073: gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2".

2021-09-25 Thread Ondrej Zary
Package: gitlab Version: 13.12.9+ds1-1~fto10+1 Severity: grave Justification: renders package unusable Dear Maintainer, installing gitlab 13.12.9+ds1-1~fto10+1 on buster amd64 fails with: Installing node modules... Resolving 2.4.2 to a url... error An unexpected error occurred: "Release not

Processed: Bug#995032 marked as pending in gobject-introspection

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #995032 [src:gobject-introspection] GNOME components segfault as a result of libffi transition Ignoring request to alter tags of bug #995032 to the same tags previously set -- 995032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995032

Bug#995032: marked as pending in gobject-introspection

2021-09-25 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #995032 in gobject-introspection 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#995032 marked as pending in gobject-introspection

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #995032 [src:gobject-introspection] GNOME components segfault as a result of libffi transition Added tag(s) pending. -- 995032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995032 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#995032: marked as pending in gobject-introspection

2021-09-25 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #995032 in gobject-introspection 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#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-09-25 Thread Sebastian Ramacher
On 2021-09-25 15:31:31 +0200, Francesco Poli wrote: > On Sat, 25 Sep 2021 12:25:16 +0200 Sebastian Ramacher wrote: > > [...] > > So this is crashing somewhere during the initialization of libglibmm. > > Hence I'm reassigning to libglibmm. > [...] > > Thanks, Sebastian! > > > By the way, I am

Bug#995050: ecere-sdk FTBFS with gcc 10

2021-09-25 Thread Jérôme St-Louis
Thank you Adrian for reporting this. We have fixes for this upstream: commit *c94efd6390599a4a291b7fe8b3d2d62699247380* Author: Jerome St-Louis Date:   Sun Sep 6 03:35:01 2020 -0400     compiler/bootstrap: Updated for GCC 10 Common fixes commit *7d835dd5c6e17ad1626ec7b6f1725e0f7f8a9371*

Bug#994265: marked as done (pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded)

2021-09-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Sep 2021 16:36:17 + with message-id and subject line Bug#994265: fixed in pypy 7.3.5+dfsg-3 has caused the Debian Bug report #994265, regarding pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded to be marked as

Bug#994910: tripwire segfaults while reading files in /etc

2021-09-25 Thread Russ Allbery
Package: tripwire Version: 2.4.3.7-3+b3 Followup-For: Bug #994910 Reproduced here following a libc6 upgrade. I suspect this is because tripwire is statically linked and there has been a new release of libc6, so I suspect the nsswitch interface has broken (which is a standard problem with

Processed: closing 994444

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 99 1.6.1-3 Bug #99 [src:panicparse] panicparse: autopkgtest failure Marked as fixed in versions panicparse/1.6.1-3. Bug #99 [src:panicparse] panicparse: autopkgtest failure Marked Bug as done > thanks Stopping processing here.

Processed: reassign 995032 to src:gobject-introspection, affects 995032

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 995032 src:gobject-introspection 1.70.0-1 Bug #995032 [gnome-shell] GNOME components segfault as a result of libffi transition Bug reassigned from package 'gnome-shell' to 'src:gobject-introspection'. No longer marked as found in

Bug#994612: marked as done (nodjes: Please fix nodejs debci regression)

2021-09-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Sep 2021 15:01:54 + with message-id and subject line Done has caused the Debian Bug report #994612, regarding nodjes: Please fix nodejs debci regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#994551: libcifpp1: please split off static files to separate package

2021-09-25 Thread Nilesh Patra
Hi Étienne, all, > I took the liberty to implement the change you suggest, and push > to Salsa [1]. I do not see your changes on salsa, the last commit is 3 months old there. Did you forget to push? > Since this is an RC bug which propagates on > several packages, and since it would have to go

Processed: cloning 994108, reassign -1 to gcc-9-doc, retitle -1 to gcc-9-doc: do not release with bookworm

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 994108 -1 Bug #994108 [src:gcc-9] gcc-9: do not release with bookworm Bug 994108 cloned as bug 995061 > reassign -1 gcc-9-doc 9.4.0-1 Bug #995061 [src:gcc-9] gcc-9: do not release with bookworm Bug reassigned from package 'src:gcc-9' to

Processed: closing 994931, fixed 994931 in 247.9-2+b1

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 994931 Bug #994931 [systemd] systemd: silently removed configuration files for systemd-timesyncd Marked Bug as done > fixed 994931 247.9-2+b1 Bug #994931 {Done: Michael Biebl } [systemd] systemd: silently removed configuration files for

Processed: your mail

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 995020 https://github.com/Macaulay2/M2/issues/2244 Bug #995020 [src:macaulay2] macaulay2: autopkgtest regression and flaky test: SIGSEGV Set Bug forwarded-to-address to 'https://github.com/Macaulay2/M2/issues/2244'. > thanks Stopping

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-09-25 Thread Francesco Poli
On Sat, 25 Sep 2021 12:25:16 +0200 Sebastian Ramacher wrote: [...] > So this is crashing somewhere during the initialization of libglibmm. > Hence I'm reassigning to libglibmm. [...] Thanks, Sebastian! By the way, I am now wondering whether I really need jackd2-firewire. Maybe I can keep it

Processed: Re: mpi4py breaks gyoto autopkgtest on i386: 1 process returned, a non-zero exit code

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > found -1 gyoto/1.4.4-4 Bug #994784 [src:openmpi,src:gyoto] openmpi breaks gyoto autopkgtest on i386 Ignoring request to alter found versions of bug #994784 to the same values previously set > found -1 gyoto/1.4.4-3 Bug #994784 [src:openmpi,src:gyoto] openmpi breaks

Bug#994784: mpi4py breaks gyoto autopkgtest on i386: 1 process returned, a non-zero exit code

2021-09-25 Thread Thibaut Paumard
Control: found -1 gyoto/1.4.4-4 Control: found -1 gyoto/1.4.4-3 Control: notfound -1 gyoto/1.4.4-5 Hi Paul, Le 24/09/2021 à 21:42, Paul Gevers a écrit : > Is the workaround inside the binary, or only (needed) in the test suite? > In other words, did openmpi *break* gyoto on i386 in some cases?

Bug#995032: gnome-session segfaults - no GNOME session possible at all (white screen to contact the system administrator)

2021-09-25 Thread Daniel Leidert
Am Samstag, dem 25.09.2021 um 03:48 -0400 schrieb Jeremy Bicha: > On Sat, Sep 25, 2021 at 12:30 AM Michael Ott wrote: > > The problem is not gnome-shell. It is the gobject-introspection. > > After downgrade this packages from 1.70.0-1+b1 to 1.70.0-1 it works > > again. Indeed, version

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-09-25 Thread Jeremy Bicha
On Sat, Sep 25, 2021 at 6:25 AM Sebastian Ramacher wrote: > So this is crashing somewhere during the initialization of libglibmm. > Hence I'm reassigning to libglibmm. Sebastian, My first guess is that this is more fallout from the incomplete libffi transition. See https://bugs.debian.org/995032

Processed: Re: Bug#995032: GNOME components segfault as a result of libffi transition

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > retitle 995032 GNOME components segfault as a result of libffi transition Bug #995032 [gnome-shell] GNOME components segfault as a result of libffi transition Ignoring request to change the title of bug#995032 to the same title -- 995032:

Bug#995032: GNOME components segfault as a result of libffi transition

2021-09-25 Thread Simon McVittie
Control: retitle 995032 GNOME components segfault as a result of libffi transition On Sat, 25 Sep 2021 at 03:48:20 -0400, Jeremy Bicha wrote: > On Sat, Sep 25, 2021 at 12:30 AM Michael Ott wrote: > > The problem is not gnome-shell. It is the gobject-introspection. > > After downgrade this

Processed: Re: Bug#995032: GNOME components segfault as a result of libffi transition

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > retitle 995032 GNOME components segfault as a result of libffi transition Bug #995032 [gnome-shell] gnome-session segfaults - no GNOME session possible at all (white screen to contact the system administrator) Changed Bug title to 'GNOME components segfault as a

Bug#995051: python3.9: FTBFS on i386: test timeout

2021-09-25 Thread Sebastian Ramacher
Source: python3.9 Version: 3.9.7-4 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org Control: block 994560 by -1 python3.9 fails to build on i386 due to tests that timeout: | 0:27:34 load

Processed: python3.9: FTBFS on i386: test timeout

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > block 994560 by -1 Bug #994560 [release.debian.org] transition: libffi 994560 was blocked by: 995045 995007 991096 995036 995044 994560 was not blocking any bugs. Added blocking bug(s) of 994560: 995051 -- 994560:

Bug#995050: ecere-sdk FTBFS with gcc 10

2021-09-25 Thread Adrian Bunk
Source: ecere-sdk Version: 0.44.15-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=ecere-sdk=0.44.15-1%2Bb4 ... gcc -Wl,-z,relro -Wl,--no-undefined -Wl,--no-undefined -Wl,--no-undefined -Wl,--no-undefined -L../ecere/obj/bootstrap.linux

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-09-25 Thread Sebastian Ramacher
Control: tags -1 = Control: reassign -1 libglibmm-2.4-1v5 2.66.1-1 On 2021-09-25 12:03:54 +0200, Francesco Poli wrote: > Control: tags -1 - moreinfo > > > On Fri, 24 Sep 2021 21:46:57 +0200 Sebastian Ramacher wrote: > > [...] > > I haven't tried that yet, but otherwise you can always install

Processed: Re: Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 = Bug #994969 [jackd2] jackd2: segfaults after today's upgrade of other Debian testing packages Removed tag(s) unreproducible. > reassign -1 libglibmm-2.4-1v5 2.66.1-1 Bug #994969 [jackd2] jackd2: segfaults after today's upgrade of other Debian testing

Processed: Re: Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - moreinfo Bug #994969 [jackd2] jackd2: segfaults after today's upgrade of other Debian testing packages Removed tag(s) moreinfo. -- 994969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994969 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-09-25 Thread Francesco Poli
Control: tags -1 - moreinfo On Fri, 24 Sep 2021 21:46:57 +0200 Sebastian Ramacher wrote: [...] > I haven't tried that yet, but otherwise you can always install -dbgsym > packages until all symbols are resolved. I have just tried. Not sure the Debuginfod method worked fine enough, but here's

Bug#992609: careless upload of Erlang v24 without a transition tracking with the release team (was: rabbitmq-server fails to start after erlang v24 update)

2021-09-25 Thread Antonio Terceiro
On Fri, Aug 27, 2021 at 10:26:39PM +0200, Paul Gevers wrote: > Hi, > > Sorry my previous message was weird. > > On 27-08-2021 22:11, Paul Gevers wrote: > > On 27-08-2021 21:58, Antonio Terceiro wrote: > >> One thing that happens when you do this type of change without > >> coordination is that

Processed: closing 993138

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 993138 3.9.4-1.1 Bug #993138 [rabbitmq-server] rabbitmq-server: uninstallable - typo in Depends: ? Marked as fixed in versions rabbitmq-server/3.9.4-1.1. Bug #993138 [rabbitmq-server] rabbitmq-server: uninstallable - typo in Depends: ?

Bug#993138: closing 993138

2021-09-25 Thread Antonio Terceiro
close 993138 3.9.4-1.1 thanks I forgot to close this bug in the changelog.

Bug#995021: osmnx: autopkgtest regression on armhf: iteration over a 0-d array

2021-09-25 Thread Jerome BENOIT
Hello Paul, thanks for pointing out the issue. I will try to have a look this week-end. Cheers, Jerome On 24/09/2021 22:23, Paul Gevers wrote: Source: osmnx Version: 1.1.1+ds-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear

Processed: Re: Bug#994453: linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop

2021-09-25 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #994453 [src:linux] linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop Severity set to 'important' from 'critical' -- 994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453 Debian Bug Tracking

Bug#994453: linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop

2021-09-25 Thread Bastian Blank
Control: severity -1 important On Thu, Sep 16, 2021 at 10:23:53AM +0200, Gert Wollny wrote: > Package: src:linux > Version: 5.14.3-1~exp1 > Severity: critical > Justification: breaks the whole system No, it does not. The kernel is the system. Bastian

Processed: block 994560 with 995007

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 994560 with 995007 Bug #994560 [release.debian.org] transition: libffi 994560 was blocked by: 995044 995045 991096 995036 994560 was not blocking any bugs. Added blocking bug(s) of 994560: 995007 > thanks Stopping processing here. Please

Processed: severity of 991096 is serious, tagging 991096, block 994560 with 991096 995044 995036 995045

2021-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 991096 serious Bug #991096 [src:llvm-toolchain-9] fix ftbfs with linux 5.11 Severity set to 'serious' from 'important' > tags 991096 + ftbfs Bug #991096 [src:llvm-toolchain-9] fix ftbfs with linux 5.11 Added tag(s) ftbfs. > block 994560

Bug#995045: llvm-toolchain-11: FTBFS with linux 5.14: fatal error: linux/cyclades.h: No such file or directory

2021-09-25 Thread Sebastian Ramacher
Source: llvm-toolchain-11 Version: 1:11.0.1-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | [ 8%] Building CXX object

Bug#995044: esorex: FTBFS on mips64el: FAIL: 1

2021-09-25 Thread Sebastian Ramacher
Source: esorex Version: 3.13.5+ds1-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org esorex failed to build on mips64el: | FAIL: esorex_python-test | | | | Start

Bug#995032: gnome-session segfaults - no GNOME session possible at all (white screen to contact the system administrator)

2021-09-25 Thread Jeremy Bicha
On Sat, Sep 25, 2021 at 12:30 AM Michael Ott wrote: > The problem is not gnome-shell. It is the gobject-introspection. > After downgrade this packages from 1.70.0-1+b1 to 1.70.0-1 it works > again. gobject-introspection was rebuilt as part of the libffi transition. (That's where the +b1 part of

Bug#994921: marked as done (librnd3-dev: missing Breaks+Replaces: librnd-dev)

2021-09-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Sep 2021 06:18:47 + with message-id and subject line Bug#994921: fixed in librnd 3.0.0-3 has caused the Debian Bug report #994921, regarding librnd3-dev: missing Breaks+Replaces: librnd-dev to be marked as done. This means that you claim that the problem has been

Bug#995032:

2021-09-25 Thread mabo
I have the same problem since updating today. I don't have gobject-inspection installed but I see segfault with libglib2.0-0. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#995040: iverilog FTBFS: configure: error: C preprocessor "/lib/cpp" fails sanity check

2021-09-25 Thread Helmut Grohne
Source: iverilog Version: 11.0-1 Severity: serious Tags: ftbfs iverilog fails to build from source in unstable on amd64. I'm not exactly sure what the relevant parts of the build log are. Here is my guess: | ... | checking how to run the C preprocessor... /lib/cpp | configure: error: in `/<>': |

Bug#995038: ddccontrol FTBFS: autoreconf: error: intltoolize failed with exit status: 1

2021-09-25 Thread Helmut Grohne
Source: ddccontrol Version: 0.4.4-1.2 Severity: serious Tags: ftbfs ddccontrol fails to build from source in unstable on amd64. A build ends as follows: |debian/rules override_dh_autoreconf | make[1]: Entering directory '/<>' | ./autogen.sh | Running autoreconf... | Copying file ABOUT-NLS |

Bug#994921: [Pkg-electronics-devel] Bug#994921: librnd3-dev: missing Breaks+Replaces: librnd-dev

2021-09-25 Thread Bdale Garbee
Andreas Beckmann writes: > I'm not sure whether it would be helpful, but a (versioned?) > Provides: librnd-dev (= ${binary:Version}) > could ease upgrading from librnd-dev to librnd3-dev. Yes, that makes sense. > BTW, why has the -dev package been renamed from librnd-dev to librnd3-dev? >