Bug#987130: marked as done (libcrypt-dev misplaced pkg-config files)

Your message dated Mon, 19 Apr 2021 03:03:25 + with message-id and subject line Bug#987130: fixed in libxcrypt 1:4.4.18-4 has caused the Debian Bug report #987130, regarding libcrypt-dev misplaced pkg-config files to be marked as done. This means that you claim that the problem has been dealt

Bug#972230: Bug#976477 marked as pending in jruby

On 2021-04-18 17 h 54, Markus Koschany wrote: > Hi, > > I'm just investigating the current open RC bugs for the debian-java maintained > packages. You have marked #976477 and #977979 in jruby as pending. Could you > clarify why there hasn't been an upload yet? There also seems to be another RC > b

Bug#984862: marked as done (iptables-netflow-dkms: module wants to build with gcc instead of kernel's compiler)

Your message dated Sun, 18 Apr 2021 23:18:51 + with message-id and subject line Bug#984862: fixed in iptables-netflow 2.5.1-2 has caused the Debian Bug report #984862, regarding iptables-netflow-dkms: module wants to build with gcc instead of kernel's compiler to be marked as done. This mean

Bug#984614: #984614 - fixed in unstable

El mar., 13 abr. 2021 19:51, Chris Hofstaedtler escribió: > Hello again, > > just in case you are not aware - if snort should stay in testing, > someone will need to file an unblock bug against release.debian.org. > This was done already: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986908

Bug#972230: Bug#976477 marked as pending in jruby

Hi, I'm just investigating the current open RC bugs for the debian-java maintained packages. You have marked #976477 and #977979 in jruby as pending. Could you clarify why there hasn't been an upload yet? There also seems to be another RC bug, #972230. Do you have any suggestions how we can includ

Bug#980488: marked as done (wine-development: FTBFS in sid)

Your message dated Sun, 18 Apr 2021 21:34:12 + with message-id and subject line Bug#980488: fixed in wine-development 5.6-2 has caused the Debian Bug report #980488, regarding wine-development: FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt with.

Bug#931566: Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true")

On Sun, Apr 18, 2021 at 10:20:19PM +0200, Paul Gevers wrote: > Hi Julian, David, SRM, > > On Mon, 8 Jul 2019 09:11:48 +0200 Christoph Berg wrote: > > Fwiw, I think this needs fixing in buster, not just in unstable. > > We're getting close to the release of bullseye and it has been brought > to m

Bug#931566: Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true")

Hi Julian, David, SRM, On Mon, 8 Jul 2019 09:11:48 +0200 Christoph Berg wrote: > Fwiw, I think this needs fixing in buster, not just in unstable. We're getting close to the release of bullseye and it has been brought to my attention that this bug is still unfixed in buster. Once we release bulls

Bug#981798: marked as done ("convert --label" regressed and doesn't show text anymore)

Your message dated Sun, 18 Apr 2021 20:18:14 + with message-id and subject line Bug#980202: fixed in imagemagick 8:6.9.11.60+dfsg-1.1 has caused the Debian Bug report #980202, regarding "convert --label" regressed and doesn't show text anymore to be marked as done. This means that you claim t

Bug#980202: marked as done ("convert --label" regressed and doesn't show text anymore)

Your message dated Sun, 18 Apr 2021 20:18:14 + with message-id and subject line Bug#980202: fixed in imagemagick 8:6.9.11.60+dfsg-1.1 has caused the Debian Bug report #980202, regarding "convert --label" regressed and doesn't show text anymore to be marked as done. This means that you claim t

Bug#986220: fonts-font-awesome: unhandled directory to symlink conversion: /usr/share/fonts-font-awesome/scss -> ../sass/font-awesome

Hi Andreas, I tried to do what's below, but it doesn't seem to fix the problem. What am I doing wrong here? Cheers, Thomas Goirand (zigo) diff --git a/debian/fonts-font-awesome.postinst b/debian/fonts-font-awesome.postinst new file mode 100644 index ..51f176a4 --- /dev/null +++ b/debian

Bug#987168: fluidsynth: CVE-2021-28421

Source: fluidsynth Version: 2.1.7-1 Severity: grave Tags: security upstream Forwarded: https://github.com/FluidSynth/fluidsynth/issues/808 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for fluidsynth, filling it as grave to be on safe side be

Bug#987165: offlineimap3: flaky autopkgtest: OfflineImapError("Failed to start "

Source: offlineimap3 Version: 0.0~git20210225.1e7ef9e+dfsg-3 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), Your package has an autopkgtest, great. However, I looked into the history of your autopk

Bug#984862: iptables-netflow-dkms: module wants to build with gcc instead of kernel's compiler

On 18/04/2021 16.36, Axel Beckert wrote: Hi Andreas, Andreas Beckmann wrote: Please bump the dkms dependency for bullseye, this issue can trigger on upgrades from buster to bullseye where iptables-netflow-dkms is upgraded before dkms. Should that patch really close this bug report? IIRC you d

Bug#987149: xscreensaver: allows starting external programs with cap_net_raw

As I said, it's already fixed in 6.00. The fix is just to configure without setcap and use setuid instead, which works properly with Mesa. I assume that having 6.00 distributed by Debian prior to 2035 would be asking too much, but we dare to dream.

Bug#985089: marked as done (CVE-2020-36277 CVE-2020-36278 CVE-2020-36279 CVE-2020-36280 CVE-2020-36281)

Your message dated Sun, 18 Apr 2021 17:33:25 + with message-id and subject line Bug#985089: fixed in leptonlib 1.79.0-1.1 has caused the Debian Bug report #985089, regarding CVE-2020-36277 CVE-2020-36278 CVE-2020-36279 CVE-2020-36280 CVE-2020-36281 to be marked as done. This means that you c

Bug#987149: xscreensaver: allows starting external programs with cap_net_raw

On Sun, Apr 18, 2021 at 7:04 PM Salvatore Bonaccorso wrote: > Sure I did as I'm on the team alias as well. Given it looks unlikely > that mesa will fix it (at the moment?) I though/think we should > probably do something on xscreensaver's side in Debian as well. > > Is the sonar screensaver frequen

Bug#987149: xscreensaver: allows starting external programs with cap_net_raw

Hi Tormod, On Sun, Apr 18, 2021 at 07:04:37PM +0200, Salvatore Bonaccorso wrote: > Hi Tormod, > > [Adding the team@s.d.o to CC as we do not automatically follow > security tagged bugs] > > On Sun, Apr 18, 2021 at 06:57:53PM +0200, Tormod Volden wrote: > > Indeed, as Jamie points out, the problem

Bug#986806: CVE-2021-28965

Hi Pirate, On Sun, Apr 18, 2021 at 10:26:31PM +0530, Pirate Praveen wrote: > On Sun, 18 Apr 2021 15:04:56 +0200 Salvatore Bonaccorso > wrote: > > Hi, > > > > On Sat, Apr 17, 2021 at 10:34:24PM +0530, Pirate Praveen wrote: > > > > > > > > > On Sat, Apr 17, 2021 at 10:16 pm, Utkarsh Gupta > wrote:

Bug#987149: xscreensaver: allows starting external programs with cap_net_raw

Hi Tormod, [Adding the team@s.d.o to CC as we do not automatically follow security tagged bugs] On Sun, Apr 18, 2021 at 06:57:53PM +0200, Tormod Volden wrote: > Indeed, as Jamie points out, the problem is in Mesa. > > Salvatore, why did you file this against xscreensaver? I thought you > had fol

Bug#964494: marked as done (File system corruption with ext3 + kernel-4.19.0-9-amd64)

Your message dated Sun, 18 Apr 2021 19:01:41 +0200 with message-id and subject line Re: Bug#964494: Info received (Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64) has caused the Debian Bug report #964494, regarding File system corruption with ext3 + kernel-4.19.0-9-amd64 to

Bug#964494: Info received (Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64)

Hi, On Sun, Apr 18, 2021 at 09:04:52AM -0700, Sarah Newman wrote: > On 4/18/21 8:36 AM, Salvatore Bonaccorso wrote: > > On Tue, Aug 18, 2020 at 10:02:12PM -0700, Sarah Newman wrote: > > > We haven't had any further reports of file system corruption. I > > > would guess that converting to EXT4 is s

Bug#986806: CVE-2021-28965

On Sun, 18 Apr 2021 15:04:56 +0200 Salvatore Bonaccorso wrote: > Hi, > > On Sat, Apr 17, 2021 at 10:34:24PM +0530, Pirate Praveen wrote: > > > > > > On Sat, Apr 17, 2021 at 10:16 pm, Utkarsh Gupta wrote: > > > Makes sense. Probably the time to RM ruby-rexml from the archive is > > > *now*? >

Bug#987149: xscreensaver: allows starting external programs with cap_net_raw

Indeed, as Jamie points out, the problem is in Mesa. Salvatore, why did you file this against xscreensaver? I thought you had followed the e-mail discussion we had with Tavis? Tormod

Bug#987149: xscreensaver: allows starting external programs with cap_net_raw

Already fixed in XScreenSaver 6.00. The bug is in Mesa: it has a panoply of env vars that do what LD_PRELOAD does, except Mesa only checks geteuid instead of checking getauxval AT_SECURE, as the kernel does. So anything that uses both Mesa and setcap is vulnerable. Ironically, using setuid ins

Processed: tagging 984862

Processing commands for cont...@bugs.debian.org: > # Andreas' patch is committed in git and pushed > tags 984862 + pending Bug #984862 [iptables-netflow-dkms] iptables-netflow-dkms: module wants to build with gcc instead of kernel's compiler Added tag(s) pending. > thanks Stopping processing here

Bug#964494: Info received (Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64)

On 4/18/21 8:36 AM, Salvatore Bonaccorso wrote: On Tue, Aug 18, 2020 at 10:02:12PM -0700, Sarah Newman wrote: We haven't had any further reports of file system corruption. I would guess that converting to EXT4 is sufficient to avoid the issue. Should this bug be closed or is there anything we

Bug#987135: marked as done (sysvinit FTBFS: broken check for presence of -lcrypt)

Your message dated Sun, 18 Apr 2021 16:05:30 + with message-id and subject line Bug#987135: fixed in sysvinit 2.96-7 has caused the Debian Bug report #987135, regarding sysvinit FTBFS: broken check for presence of -lcrypt to be marked as done. This means that you claim that the problem has be

Bug#986220: Uploaded to delayed queue

Dear maintainer, What Andreas suggested works, I tried. I have uploaded the suggested debdiff from Andreas to Unstable, in the delayed/5 queue. If you wish to upload the fix yourself, please let me know, and I will cancel my upload. Otherwise, in 5 days, it will reach unstable. Cheers, Thomas G

Bug#900821: workaround confirmed

On Mon, Dec 14, 2020 at 08:38:02PM +, Florian Kain wrote: > Hi all, > > we were experiencing this bug in a debian 10.4 docker container (FROM > php:apache) > it only happens with plain http not with https. > > I can confirm that workaround from Stefan Fritsch > by turning EnableMMAP off is

Bug#964494: Info received (Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64)

On Tue, Aug 18, 2020 at 10:02:12PM -0700, Sarah Newman wrote: > We haven't had any further reports of file system corruption. I > would guess that converting to EXT4 is sufficient to avoid the > issue. Should this bug be closed or is there anything we still can/should do about it? Regards, Salvat

Processed: found 987065 in 5.6.1+dfsg1-1

Processing commands for cont...@bugs.debian.org: > found 987065 5.6.1+dfsg1-1 Bug #987065 {Done: Craig Small } [src:wordpress] wordpress: CVE-2021-29450: Authenticated disclosure of password-protected posts and pages Ignoring request to alter found versions of bug #987065 to the same values prev

Processed: found 987065 in 5.6.1+dfsg1-1

Processing commands for cont...@bugs.debian.org: > found 987065 5.6.1+dfsg1-1 Bug #987065 {Done: Craig Small } [src:wordpress] wordpress: CVE-2021-29450: Authenticated disclosure of password-protected posts and pages Marked as found in versions wordpress/5.6.1+dfsg1-1. > thanks Stopping processin

Bug#984862: iptables-netflow-dkms: module wants to build with gcc instead of kernel's compiler

Hi Andreas, Andreas Beckmann wrote: > Please bump the dkms dependency for bullseye, this issue can trigger on > upgrades from buster to bullseye where iptables-netflow-dkms is upgraded > before dkms. Should that patch really close this bug report? IIRC you didn't close all these bug reports with

Processed: tagging 987095

Processing commands for cont...@bugs.debian.org: > tags 987095 + fixed-upstream Bug #987095 [libgraph-perl] transitive_closure corrupted results, after vertex deleted Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 987095: https://bug

Bug#987095: transitive_closure corrupted results, after vertex deleted

On Sat, 17 Apr 2021 15:38:32 +0200, Dominique Dumont wrote: > I've created a bug upstream: > https://github.com/graphviz-perl/Graph/issues/20 Thanks. The issue is fixed upstream, and a new 0.9721 has been made. As we have 0.9716 in testing and unstable (and 0.9720 in master) and shouldn't uploa

Processed: Bug#987095 marked as pending in libgraph-perl

Processing control commands: > tag -1 pending Bug #987095 [libgraph-perl] transitive_closure corrupted results, after vertex deleted Added tag(s) pending. -- 987095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#987095: marked as pending in libgraph-perl

Control: tag -1 pending Hello, Bug #987095 in libgraph-perl 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: https://salsa.debian.org/perl-team/modules/packages/libgraph-perl/-/commit/2c

Processed: found 986806 in 3.2.4-2

Processing commands for cont...@bugs.debian.org: > found 986806 3.2.4-2 Bug #986806 {Done: Pirate Praveen } [ruby-rexml] CVE-2021-28965 Marked as found in versions ruby-rexml/3.2.4-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 986806: https://bugs.debian.org

Bug#986806: CVE-2021-28965

Hi, On Sat, Apr 17, 2021 at 10:34:24PM +0530, Pirate Praveen wrote: > > > On Sat, Apr 17, 2021 at 10:16 pm, Utkarsh Gupta wrote: > > Makes sense. Probably the time to RM ruby-rexml from the archive is > > *now*? > > Requested removal from archive in #987101 Thanks for filling the removal! I

Bug#987131: marked as done (dpkg: libreoffice upgrade failure)

Your message dated Sun, 18 Apr 2021 14:42:21 +0200 with message-id and subject line Re: Bug#987131: dpkg: libreoffice upgrade failure has caused the Debian Bug report #987131, regarding dpkg: libreoffice upgrade failure to be marked as done. This means that you claim that the problem has been dea

Bug#987131: dpkg: libreoffice upgrade failure

Hi! [ I'm assuming this is from Andreas Beckman? :) CCed explicitly. ] On Wed, 2021-03-17 at 12:04:32 +0100, piupar...@zam127.zam.kfa-juelich.de wrote: > Package: dpkg > Version: 1.20.7.1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: block 985297 with -1 >

Processed: found 987149 in 5.42+dfsg1-1

Processing commands for cont...@bugs.debian.org: > found 987149 5.42+dfsg1-1 Bug #987149 [src:xscreensaver] xscreensaver: allows starting external programs with cap_net_raw Marked as found in versions xscreensaver/5.42+dfsg1-1. > thanks Stopping processing here. Please contact me if you need ass

Bug#987149: xscreensaver: allows starting external programs with cap_net_raw

Source: xscreensaver Version: 5.45+dfsg1-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi Filling for tracking in the BTS as well. For full public reference see: https://www.openwall.com/lists/oss-security/2021/

Processed: Re: Bug#987133: marked as done (exim4: Exim 4.94's new tainting-feature will break many running configs)

Processing control commands: > reopen -1 Bug #987133 {Done: Andreas Metzler } [exim4] exim4: Exim 4.94's new tainting-feature will break many running configs Bug reopened Ignoring request to alter fixed versions of bug #987133 to the same values previously set > found -1 4.93-1 Bug #987133 [exim

Bug#987133: marked as done (exim4: Exim 4.94's new tainting-feature will break many running configs)

Control: reopen -1 Control: found -1 4.93-1 Control: tags -1 moreinfo Control: severity -1 normal On 2021-04-18 Marc Haber wrote: > On Sun, Apr 18, 2021 at 09:57:02AM +, Debian Bug Tracking System wrote: > > From: Andreas Metzler > > Subject: Re: Bug#987133: exim4: Exim 4.94's new tainting-f

Bug#987133: marked as done (exim4: Exim 4.94's new tainting-feature will break many running configs)

On Sun, Apr 18, 2021 at 09:57:02AM +, Debian Bug Tracking System wrote: > From: Andreas Metzler > Subject: Re: Bug#987133: exim4: Exim 4.94's new tainting-feature will break > many running configs > To: 987133-d...@bugs.debian.org Was the -done really intended? Getting the fix in bullseye th

Bug#987130: libcrypt-dev makes sysvinit FTBFS: ./src/sulogin.c:978: undefined reference to `crypt'

On Apr 18, Helmut Grohne wrote: > One aspect to this certainly is that the .pc files are now located in > /lib, which is wrong as pkg-config does not search that directory. I've I am not even sure that there is any point in having a .pc file for libcrypt (and I highly doubt that anything uses it

Processed: Re: libcrypt-dev makes sysvinit FTBFS: ./src/sulogin.c:978: undefined reference to `crypt'

Processing control commands: > affects -1 = Bug #987130 [libcrypt-dev] libcrypt-dev makes sysvinit FTBFS: ./src/sulogin.c:978: undefined reference to `crypt' Removed indication that 987130 affects src:sysvinit > clone -1 -2 Bug #987130 [libcrypt-dev] libcrypt-dev makes sysvinit FTBFS: ./src/sulo

Bug#987130: libcrypt-dev makes sysvinit FTBFS: ./src/sulogin.c:978: undefined reference to `crypt'

Control: affects -1 = Control: clone -1 -2 Control: reassign -2 src:sysvinit Control: retitle -2 sysvinit FTBFS: broken check for presence of -lcrypt Control: tags -2 + patch Control: tags -1 - ftbfs Control: retitle -1 libcrypt-dev misplaced pkg-config files On Sun, Apr 18, 2021 at 10:44:17AM +02

Bug#987133: marked as done (exim4: Exim 4.94's new tainting-feature will break many running configs)

Your message dated Sun, 18 Apr 2021 11:53:16 +0200 with message-id and subject line Re: Bug#987133: exim4: Exim 4.94's new tainting-feature will break many running configs has caused the Debian Bug report #987133, regarding exim4: Exim 4.94's new tainting-feature will break many running configs

Bug#987126: marked as done (golang-1.16: Fails to build anything due to missing files: undefined: StackGuardMultiplierDefault)

Your message dated Sun, 18 Apr 2021 09:48:32 + with message-id and subject line Bug#987126: fixed in golang-1.16 1.16.3-2 has caused the Debian Bug report #987126, regarding golang-1.16: Fails to build anything due to missing files: undefined: StackGuardMultiplierDefault to be marked as done.

Bug#986996: marked as done (openblas: SIGILL on arm64 due when HWCAP_CPUID is not set)

Your message dated Sun, 18 Apr 2021 09:49:27 + with message-id and subject line Bug#986996: fixed in openblas 0.3.14+ds-2 has caused the Debian Bug report #986996, regarding openblas: SIGILL on arm64 due when HWCAP_CPUID is not set to be marked as done. This means that you claim that the prob

Bug#987133: links to more info

On Exim-users: https://lists.exim.org/lurker/message/20201109.222746.24ea3904.de.html https://lists.exim.org/lurker/message/20210406.161056.f80935f1.en.html On Debian-User-German: Regards, Paul

Bug#987133: exim4: Exim 4.94's new tainting-feature will break many running configs

Package: exim4 Version: 4.94-17 Severity: serious Justification: The tainting-feature that has been introduced with 4.94 by upstream will break many running configurations. Dear Maintainers, the tainting-feature that has been introduced with 4.94 by upstream will break many running configurat

Bug#986996: marked as done (openblas: SIGILL on arm64 due when HWCAP_CPUID is not set)

Your message dated Sun, 18 Apr 2021 09:18:22 + with message-id and subject line Bug#986996: fixed in openblas 0.3.13+ds-3 has caused the Debian Bug report #986996, regarding openblas: SIGILL on arm64 due when HWCAP_CPUID is not set to be marked as done. This means that you claim that the prob

Processed: Bug#987126 marked as pending in golang

Processing control commands: > tag -1 pending Bug #987126 [golang-1.16] golang-1.16: Fails to build anything due to missing files: undefined: StackGuardMultiplierDefault Added tag(s) pending. -- 987126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987126 Debian Bug Tracking System Contact

Bug#987126: marked as pending in golang

Control: tag -1 pending Hello, Bug #987126 in golang 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: https://salsa.debian.org/go-team/compiler/golang/-/commit/eba682996ee92eabdc397de8c0

Processed: tagging 986814

Processing commands for cont...@bugs.debian.org: > tags 986814 + moreinfo Bug #986814 {Done: Lucas Nussbaum } [cloud.debian.org] Latest vagrant Buster libvirt image not found Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 986814: https://b

Bug#987130: libcrypt-dev makes sysvinit FTBFS: ./src/sulogin.c:978: undefined reference to `crypt'

On Sun, Apr 18, 2021 at 10:26:44AM +0200, Helmut Grohne wrote: > Not yet seen by reproducible, but I've rescheduled a build there. Likely > a matter of waiting. It also fails there now: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/sysvinit_2.96-6.rbuild.log.gz One aspect to

Processed: dpkg: libreoffice upgrade failure

Processing control commands: > block 985297 with -1 Bug #985297 [libreoffice-common] libreoffice-common: do not use dir_to_symlink for /usr/lib/libreoffice/share/registry 985297 was blocked by: 985401 985297 was not blocking any bugs. Added blocking bug(s) of 985297: 987131 -- 985297: https://b

Bug#987131: dpkg: libreoffice upgrade failure

Package: dpkg Version: 1.20.7.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 985297 with -1 Preparing to unpack .../0-ure_1%3a7.0.4-3_amd64.deb ... Unpacking ure (1:7.0.4-3) over (6.1.5-3+deb10u7) ... Preparing to unpack .../1-libreoffice-style-colibre

Processed: libcrypt-dev makes sysvinit FTBFS: ./src/sulogin.c:978: undefined reference to `crypt'

Processing control commands: > affects -1 + src:sysvinit Bug #987130 [libcrypt-dev] libcrypt-dev makes sysvinit FTBFS: ./src/sulogin.c:978: undefined reference to `crypt' Added indication that 987130 affects src:sysvinit -- 987130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987130 Debian

Bug#987130: libcrypt-dev makes sysvinit FTBFS: ./src/sulogin.c:978: undefined reference to `crypt'

Package: libcrypt-dev Version: 1:4.4.18-3 Severity: serious Tags: ftbfs Control: affects -1 + src:sysvinit User: helm...@debian.org Usertags: rebootstrap X-Debbugs-Cc: iv...@debian.org Since the latest libxcrypt upload, sysvinit fails to build from source. A build on amd64 ends with: | cc -Wl,-z,

Bug#987128: libjs-leaflet.markercluster: browser code completely broken: Contains Node.js "require()" calls

Package: libjs-leaflet.markercluster Version: 1.4.1~dfsg-9 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The JavaScript code provided with release -9 is completely unusable, because it contains Node.js require() calls instead of browser-co

Bug#987126: golang-1.16: Fails to build anything due to missing files: undefined: StackGuardMultiplierDefault

Package: golang-1.16 Version: 1.16.3-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: si...@ruderich.org Hello, since the update to 1.16.3-1 I cannot build any packages with go-1.16: $ printf 'package main\nmain(){}' > x.go $ /usr/lib/go-1.16/bin/go run x.go #