Bug#902901: FTBFS: Tests fail

Hello, On Tue 16 Jun 2020 at 07:53PM +03, Ilias Tsitsimpis wrote: > This package is still unbuildable after 2 years, with no response from > upstream. Since there are no rev dependencies for this package, I intend > to remove it from Debian. Please go ahead, since secret-sharing no longer

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 963548 964362 Bug #963548 [chromium] Received signal 11 SEGV_MAPERR Bug #964334 [chromium] segfault repeatedly Bug #964362 [chromium] chromium crash frequently, SEGV_MAPERR Severity set to 'grave' from 'important' Marked as found in

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 964334 963548 Bug #964334 [chromium] segfault repeatedly Bug #963548 [chromium] Received signal 11 SEGV_MAPERR Severity set to 'grave' from 'normal' Marked as found in versions chromium/83.0.4103.116-2. Bug #964334 [chromium] segfault

Processed: unarchiving 867436

Processing commands for cont...@bugs.debian.org: > unarchive 867436 Bug #867436 {Done: Scott Kitterman } [python3-icalendar] python3-icalendar: missing dependencies Unarchived Bug 867436 > thanks Stopping processing here. Please contact me if you need assistance. -- 867436:

Processed: unarchiving 879224

Processing commands for cont...@bugs.debian.org: > unarchive 879224 Bug #879224 {Done: Thomas Goirand } [websockify] websockify: missing dependency on python-pkg-resources Unarchived Bug 879224 > thanks Stopping processing here. Please contact me if you need assistance. -- 879224:

Processed: unarchiving 879170

Processing commands for cont...@bugs.debian.org: > unarchive 879170 Bug #879170 {Done: Adrian Bunk } [libswt-webkit-gtk-3-jni] libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep Unarchived Bug 879170 > thanks Stopping processing here. Please contact me if you need assistance. -- 879170:

Bug#961377: raspi3-firmware: recent stable update causes non-booting systems

tags 961377 + pending thanks I have uploaded the fix and mailed the Stable Release Managers, this should be fixed soon. Thanks!

Processed: Re: Bug#961377: raspi3-firmware: recent stable update causes non-booting systems

Processing commands for cont...@bugs.debian.org: > tags 961377 + pending Bug #961377 [raspi3-firmware] raspi3-firmware: recent stable update causes non-booting systems Ignoring request to alter tags of bug #961377 to the same tags previously set > thanks Stopping processing here. Please contact

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 962755 https://github.com/libexif/exif/issues/2 Bug #962755 [src:exif] exif: FTBFS on s390x: test failure Set Bug forwarded-to-address to 'https://github.com/libexif/exif/issues/2'. > stop Stopping processing here. Please contact me if

Processed: Bug#963933 marked as pending in glib2.0

Processing control commands: > tag -1 pending Bug #963933 [src:glib2.0,src:util-linux] glib2.0: autopkgtext: ld: cannot find -lcryptsetup Added tag(s) pending. -- 963933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963933 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#963933: marked as pending in glib2.0

Control: tag -1 pending Hello, Bug #963933 in glib2.0 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: tagging 964399

Processing commands for cont...@bugs.debian.org: > tags 964399 + bullseye sid Bug #964399 [src:ganglia] Should ganglia be removed? Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 964399:

Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

On Mon, 06 Jul 2020 at 18:50:01 +0200, Chris Hofstaedtler wrote: > src:util-linux will drop most static libraries in the 2.35.2-8 upload. > Please change the glib2.0 autopkgtest (by dropping the static test) > to allow this. libmount support in glib2.0 is temporarily disabled as a workaround for

Processed: Re: skales: Python2 removal in sid/bullseye

Processing control commands: > tags 943273 patch Bug #943273 [src:skales] skales: Python2 removal in sid/bullseye Added tag(s) patch. -- 943273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#943273: skales: Python2 removal in sid/bullseye

Control: tags 943273 patch The attached patch simply switches to python3. The code seems at a glance to be python3 compatible(e.g. 2to3 didn't have anything interesting to say), and is sufficient enough for help2man to work running with python3. But I haven't tested more extensively than that.

Bug#962221: Fixes for CVE-2020-13696 (#962221)

Hi Mattia! July 6, 2020 6:58:05 PM UTC, Mattia Rizzolo написав(-ла): >but could either of you do a bunch of housekeeping work as well, like: > * bumping dh compat > * drop --dbgsym-migration > * drop the .menu files > * would be awesome to have the copyright file rewrote using dep-5 > * I

Processed: tagging 962813

Processing commands for cont...@bugs.debian.org: > tags 962813 + bullseye sid Bug #962813 [src:haskell-tree-monad] does not build with ghc 8.8 Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 962813:

Bug#964252: marked as done (libbluray: FTBFS if texlive is installed in non-minimal build environment)

Your message dated Mon, 06 Jul 2020 20:28:22 + with message-id and subject line Bug#964252: fixed in libbluray 1:1.2.0-2 has caused the Debian Bug report #964252, regarding libbluray: FTBFS if texlive is installed in non-minimal build environment to be marked as done. This means that you

Processed: Re: fixed

Processing control commands: > fixed -1 2.0.0-1 Bug #955080 {Done: Michal Arbet } [src:python-ceilometermiddleware] python-ceilometermiddleware: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info' Marked as fixed in versions python-ceilometermiddleware/2.0.0-1. --

Bug#955080: fixed

Control: fixed -1 2.0.0-1 Dear Thomas, On Mon, 25 May 2020 09:44:09 +0200 Thomas Goirand wrote: > fixed Your package version 2.0.0-1 was not based (changelog entries) on version 1.5.0-3, which closed this bug. Hence, the BTS and the migration software don't know that the version currently in

Bug#956285: Problems identified in debian/copyright

[Michael Lustfield] > I noticed that this package appears to have some issues with debian/copyright. Hi. Any hope to have a fix for this in time for the next stable release? -- Happy hacking Petter Reinholdtsen

Bug#964405: marked as pending in lintian

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

Processing control commands: > tag -1 pending Bug #964405 [src:lintian] lintian: autopkgtest regression: No tests were selected by your filter: Added tag(s) pending. -- 964405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964405 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#964408: python-redisearch-py: autopkgtest failure: No module named 'redisearch_py'

Source: python-redisearch-py Version: 0.9.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package python-redisearch-py, great. However, it fails. Currently this

Bug#964407: ocaml-odoc: autopkgtest failure: Unknown tag '@raises'.

Source: ocaml-odoc Version: 1.5.1-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Ralf, You recently added an autopkgtest to your package ocaml-odoc, great. However, it fails. Currently this failure is

Bug#964334: segfault repeatedly

Package: chromium Version: 83.0.4103.116-2 Followup-For: Bug #964334 Also like said before, chromium crashes very soon after starting, usually in few minutes. System is up-to-date, no proprietary software. -- Stacktrace: daniil@apollopc:~$ chromium

Bug#964406: onionbalance: autopkgtest regression: debian/tests/upstream does not exist

Source: onionbalance Version: 0.2.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of onionbalance the autopkgtest of onionbalance fails in testing when that autopkgtest is run with the

Bug#963855: marked as done (capnproto: FTBFS on IPv6-only environments)

Your message dated Mon, 06 Jul 2020 19:34:01 + with message-id and subject line Bug#963855: fixed in capnproto 0.7.0-7 has caused the Debian Bug report #963855, regarding capnproto: FTBFS on IPv6-only environments to be marked as done. This means that you claim that the problem has been

Bug#964405: lintian: autopkgtest regression: No tests were selected by your filter:

Source: lintian Version: 2.82.0 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lintian the autopkgtest of lintian fails in testing when that autopkgtest is run with the binary packages

Processed: tagging 952009

Processing commands for cont...@bugs.debian.org: > tags 952009 - bullseye sid Bug #952009 {Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= } [src:c-icap-modules] c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant Removed tag(s) sid and bullseye. >

Processed: unarchiving 952009

Processing commands for cont...@bugs.debian.org: > unarchive 952009 Bug #952009 {Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= } [src:c-icap-modules] c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant Unarchived Bug 952009 > thanks Stopping

Bug#964404: quagga is replaced by frr

Source: quagga Version: 1.2.4-4 Severity: serious The maintained fork from quagga that continues the zebra codebase is frr, which is already in buster: https://tracker.debian.org/pkg/frr Additionally shipping quagga in bullseye might bring more confusion than benefits.

Bug#962221: Fixes for CVE-2020-13696 (#962221)

Hi Mattia! By partial I understood that upstream fixed the core part but the Debian patch sjould have been adapted to reflect new changes. Jeremy, can you please correct me if I am wrong? --  Vasyl Gello == Certified SolidWorks Expert Mob.:+380

Processed: tagging 964293

Processing commands for cont...@bugs.debian.org: > tags 964293 + moreinfo Bug #964293 [hubicfuse] hubicfuse: error while loading libssl.so.1.0.0 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 964293:

Bug#963583: sysdig: sysdig segfaults on start

Control: reassign -1 libgrpc++1 1.26.0-3 Control: retitle -1 libgrpc++1 changes ABI without changing soname Control: forwarded -1 https://github.com/grpc/grpc/issues/23205 Control: affects -1 src:sysdig On Tue, Jun 23, 2020 at 06:59:25PM -0700, Dima Kogan wrote: >... > $ sudo sysdig ... >

Bug#962221: Fixes for CVE-2020-13696 (#962221)

On Mon, Jul 06, 2020 at 05:10:30AM +, Vasyl Gello wrote: > Thanks for contributing the security release! I checked your changes and > pushed them to the team repo. > I do not have an upload rights, so CCing Sebastian and Mattia. Sure, but could either of you do a bunch of housekeeping work

Processed: Re: Bug#963583: sysdig: sysdig segfaults on start

Processing control commands: > reassign -1 libgrpc++1 1.26.0-3 Bug #963583 [sysdig] sysdig: sysdig segfaults on start Bug reassigned from package 'sysdig' to 'libgrpc++1'. No longer marked as found in versions sysdig/0.26.7-2. Ignoring request to alter fixed versions of bug #963583 to the same

Bug#964403: goxel FTBFS on armel: Must be linked with libatomic

Source: goxel Version: 0.10.6-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=goxel=armel=0.10.6-1=1592688053=0 ... g++ -o goxel -fsanitize=address -fsanitize=undefined -pthread -Wl,-z,relro src/yocto.o src/xxhash.o src/utils.o src/tools.o src/theme.o

Processed: Re: Bug#964377: bumblebee: please runtime depend on pciutils

Processing control commands: > severity -1 important Bug #964377 [src:bumblebee] bumblebee: please runtime depend on pciutils Severity set to 'important' from 'serious' -- 964377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964377 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#964377: bumblebee: please runtime depend on pciutils

Control: severity -1 important On Mon, Jul 06, 2020 at 02:40:37PM +0200, Andreas Beckmann wrote: > On 7/6/20 1:14 PM, Gianfranco Costamagna wrote: > > Hello, bumblebee and bumblebee-nvidia (in Ubuntu) use lspci in their > > postinst files, without > > a dependency on it > > Good catch! > Should

Processed: tagging 963745

Processing commands for cont...@bugs.debian.org: > tags 963745 + ftbfs Bug #963745 [src:haskell-regex-tdfa-text] haskell-regex-tdfa-text: Removal notice: Deprecated Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 963745:

Processed: tagging 963499

Processing commands for cont...@bugs.debian.org: > tags 963499 + ftbfs Bug #963499 [src:haskell-wl-pprint-extras] haskell-wl-pprint-extras: Removal notice: broken and unmaintained Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 963499:

Processed: tagging 962959

Processing commands for cont...@bugs.debian.org: > tags 962959 + ftbfs Bug #962959 [src:haskell-edison-api] haskell-edison-api: Removal notice: broken and unuseful Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962959:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > # turns this bug into non-RC, as I can't reproduce the actual crash > retitle 959885 inkscape: unnecessary error messages when called without X > server Bug #959885 [inkscape] inkscape: crashes when called without X server Changed Bug title to

Processed: tagging 963072

Processing commands for cont...@bugs.debian.org: > tags 963072 + ftbfs Bug #963072 [src:haskell-easytest] haskell-easytest: Does not build with hedgehog 1.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 963072:

Processed: tagging 962964

Processing commands for cont...@bugs.debian.org: > tags 962964 + ftbfs Bug #962964 [src:haskell-io-choice] haskell-io-choice: Removal notice: broken and obsolete Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962964:

Processed: tagging 962890

Processing commands for cont...@bugs.debian.org: > tags 962890 + ftbfs Bug #962890 [src:haskell-bytestring-show] haskell-bytestring-show: Removal notice: broken and unmaintained Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962890:

Processed: tagging 962813

Processing commands for cont...@bugs.debian.org: > tags 962813 + ftbfs Bug #962813 [src:haskell-tree-monad] does not build with ghc 8.8 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962813:

Processed: tagging 962962

Processing commands for cont...@bugs.debian.org: > tags 962962 + ftbfs Bug #962962 [src:haskell-hstatsd] haskell-hstatsd: Removal notice: broken and unmaintained Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962962:

Bug#964401: sight FTBFS on i386: error: conversion from ‘long long unsigned int’ to ‘size_t’ {aka ‘unsigned int’} may change value

Source: sight Version: 20.0.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=sight=i386=20.0.0-1=1593349313=0 ... /<>/libs/core/fwData/src/fwData/Mesh.cpp: In member function ‘size_t fwData::Mesh::getDataSizeInBytes() const’:

Processed: owner 963855

Processing commands for cont...@bugs.debian.org: > owner 963855 tmanc...@debian.org Bug #963855 [src:capnproto] capnproto: FTBFS on IPv6-only environments Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 963855:

Bug#964400: haskell-yesod-core: build fails on IPv6-only buildds

Source: haskell-yesod-core Version: 1.6.18-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=haskell-yesod-core=i386=1.6.18-1=1593282031=0 ... Failures: test/YesodCoreTest/RawResponse.hs:63:9: 1) RawResponse works uncaught exception: IOException of type

Bug#964399: Should ganglia be removed?

Source: ganglia Severity: serious Should ganglia be removed? It's dead upstream (last commits from over three years ago, last release from 2015), is now orphaned (last active maintainer is no longer a DD, but wasn't very actively maintained to begin with, the current packaged version is from

Processed: tagging 963184

Processing commands for cont...@bugs.debian.org: > tags 963184 + ftbfs Bug #963184 [src:ftphs] ftphs: Removal notice: broken and unmaintained Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 963184:

Bug#937378: purity-ng: Python2 removal in sid/bullseye

On Sun, Jun 07, 2020 at 01:03:15AM +0200, Moritz Mühlenhoff wrote: > On Fri, Aug 30, 2019 at 07:32:38AM +, Matthias Klose wrote: > > Package: src:purity-ng > > Version: 0.2.0-2.1 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > >

Processed: [bts-link] source package src:libieee1284

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libieee1284 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Bug#936783: kcachegrind: Python2 removal in sid/bullseye

Python 3 doesn't include hotshot, so the hotshot2calltree script should be dropped. Upstream still includes it but it doesn't appear to have seen any maintenance: https://invent.kde.org/sdk/kcachegrind/-/tree/master/converters signature.asc Description: This is a digitally signed message part.

Bug#963713: [Pkg-net-snmp-devel] Bug#963713: net-snmp: CVE-2019-20892

Hi, Do we have definite info on what versions are affected? I cannot reproduce the issue in jessie/stretch/buster (5.7.x). Incidentally Salvatore's test now yields an error in bullseye (5.8dfsg-3), though I suspect the issue is at the client's level: # snmpbulkget -v3 -Cn1 -Cr1472 -l authPriv

Bug#964339: marked as done (node-expat: autopkgtest regression: Cannot find module 'iconv')

Your message dated Mon, 06 Jul 2020 17:19:16 + with message-id and subject line Bug#964339: fixed in node-expat 2.3.18+ds-2 has caused the Debian Bug report #964339, regarding node-expat: autopkgtest regression: Cannot find module 'iconv' to be marked as done. This means that you claim that

Bug#964339: marked as pending in node-expat

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

Processing control commands: > tag -1 pending Bug #964339 [src:node-expat] node-expat: autopkgtest regression: Cannot find module 'iconv' Added tag(s) pending. -- 964339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964339 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#964377: bumblebee: please runtime depend on pciutils

Hello, > Good catch! > Should there be a lintian test for it? I remember fixing the same thing > in firmware-b43-installer recently. > it would probably help a lot, yes :) but a quick and incomplete look shows... https://codesearch.debian.net/search?q=lspci+path%3Apostinst%24=0 only two

Bug#964384: [Debian-iot-maintainers] Bug#964384: ulfius: FTBFS with recent libmicrohttpd

Hello, > This test fails while getting "http://[::1]:8080/empty;, maybe there's > an ipv6 issue in ubuntu autopkgtest environment? > they might not have ipv6 capability, or that port being already allocated? not sure. > The last 2 errors will probably tell us more after the release since the >

Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

Hi Simon, src:util-linux will drop most static libraries in the 2.35.2-8 upload. Please change the glib2.0 autopkgtest (by dropping the static test) to allow this. Many thanks, Chris

Bug#964242: marked as done (bsdmainutils: depends on non-existing version of bsdextrautils)

Your message dated Mon, 06 Jul 2020 16:06:52 + with message-id and subject line Bug#964242: fixed in util-linux 2.35.2-7 has caused the Debian Bug report #964242, regarding bsdmainutils: depends on non-existing version of bsdextrautils to be marked as done. This means that you claim that the

Processed: tagging 964242

Processing commands for cont...@bugs.debian.org: > tags 964242 + pending Bug #964242 [bsdmainutils] bsdmainutils: depends on non-existing version of bsdextrautils Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 964242:

Bug#964384: [Debian-iot-maintainers] Bug#964384: ulfius: FTBFS with recent libmicrohttpd

> Hello, can you please apply the two patches below to fix the build failure > with new libmicrohttpd and to give a more useful error message in case curl > fails? > (I don't know yet why, but the autopkgtest is failing in Ubuntu) > Since I'm also the upstream author, I'll fix the ftbfs in the

Bug#964245: patch from pull request

>From dab0c1f9abda5b17cc7488f89a6fe08be7bc56a0 Mon Sep 17 00:00:00 2001 From: wisp3rwind <17089248+wisp3rw...@users.noreply.github.com> Date: Tue, 9 Jun 2020 19:34:31 +0200 Subject: [PATCH] compatibility with breaking changes to the ast module new in 3.10, also backported to 3.8 and 3.9:

Processed: unarchiving 863567, unarchiving 873978, unarchiving 887064, unarchiving 893424, unarchiving 894535

Processing commands for cont...@bugs.debian.org: > unarchive 863567 Bug #863567 {Done: Andreas Beckmann } [rmail] rmail: unable to install because of unmet dependency Unarchived Bug 863567 > unarchive 873978 Bug #873978 {Done: Andreas Beckmann } [sendmail-base] sendmail-base: Please check for

Bug#964245: (no subject)

It looks like this was fixed in https://github.com/beetbox/beets/pull/3621

Bug#964384: ulfius: FTBFS with recent libmicrohttpd

Source: ulfius Version: 2.6.7-4 Severity: serious tags: patch Hello, can you please apply the two patches below to fix the build failure with new libmicrohttpd and to give a more useful error message in case curl fails? (I don't know yet why, but the autopkgtest is failing in Ubuntu)

Bug#963713: [Pkg-net-snmp-devel] Bug#963713: net-snmp: CVE-2019-20892

On Monday, June 29 2020, Craig Small wrote: > Hi All > There's a few goes of the required patches but I think I've got them all. > There was the v3doublefree2.patch, a format patch and then the first git > reference in the tracker where they have re-arranged the free function so > it tracks the

Bug#954604: Mailman 3.3.1

Hi, on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954604 I read that Mailman 3.3.1 should enter debian as soon as it is released. Mailman 3.3.1 has been released on 19 Apr 2020, according to https://list.org/ Are there any problems left to be solved? Regards, Wilfried

Bug#964203: marked as done (libnginx-mod-nchan distributes old/incompatible module)

Your message dated Mon, 6 Jul 2020 15:26:29 +0200 with message-id and subject line has caused the Debian Bug report #964203, regarding libnginx-mod-nchan distributes old/incompatible module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#964366: [aristocratos/bashtop] [BUG] insecure use of /tmp (#161)

Hi Jakub, Le lun. 6 juil. 2020 à 13:29, aristocratos a écrit : > > pytmpdir=$(mktemp -d "${TMPDIR:-/tmp}"/) > pywrapper=$(mktemp "${pytmpdir}"/bashtop.psutil.) > > Should fix the issue. > Does the proposed fix by upstream look good to you? Best, Dylan

Processed: tagging 964309

Processing commands for cont...@bugs.debian.org: > tags 964309 + pending Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing libncurses-dev dependency Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 964309:

Processed: Bug is also in stretch and buster

Processing commands for cont...@bugs.debian.org: > unarchive 941926 Bug #941926 {Done: gregor herrmann } [src:libembperl-perl] FTBFS: test failure in #238 EmbperlObject/epobase.htm Unarchived Bug 941926 > found 941926 2.5.0-10 Bug #941926 {Done: gregor herrmann } [src:libembperl-perl] FTBFS:

Bug#964377: bumblebee: please runtime depend on pciutils

On 7/6/20 1:14 PM, Gianfranco Costamagna wrote: Hello, bumblebee and bumblebee-nvidia (in Ubuntu) use lspci in their postinst files, without a dependency on it Good catch! Should there be a lintian test for it? I remember fixing the same thing in firmware-b43-installer recently. Andreas

Processed: python-sievelib: diff for NMU version 1.1.1-3.2

Processing control commands: > tags 960577 + patch Bug #960577 [src:python-sievelib] python-sievelib FTBFS with python3-pip 20.1 Bug #96 [src:python-sievelib] python-sievelib: FTBFS: AttributeError: 'ParsedRequirement' object has no attribute 'match_markers' Added tag(s) patch. Added tag(s)

Bug#960577: python-sievelib: diff for NMU version 1.1.1-3.2

Control: tags 960577 + patch Control: tags 960577 + pending Dear maintainer, I've prepared an NMU for python-sievelib (versioned as 1.1.1-3.2) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru python-sievelib-1.1.1/debian/changelog

Bug#964377: bumblebee: please runtime depend on pciutils

Source: bumblebee Version: 3.2.1-23 Severity: serious Hello, bumblebee and bumblebee-nvidia (in Ubuntu) use lspci in their postinst files, without a dependency on it ./debian/bumblebee.postinst:busid=$(lspci -d10de: -nn | grep '\[030[02]\]' | cut -d' ' -f1 | tr . : | head -1)

Bug#959579: adapta-gtk-theme: FTBFS: make[2]: *** [Makefile:1040: all] Error 1

On Mon, Jul 6, 2020 at 11:19 AM Samuel Henrique wrote: > > Hello Sudip, > > Just a quick update, I spoke to Franciscarlos (he will reply back here > soon) and he intends to keep the package, so your patch will be > accepted, he just wants to confirm that the package is working fine > with the

Bug#950772: marked as done (swupdate: FTBFS during separate arch/indep builds)

Your message dated Mon, 06 Jul 2020 11:00:10 + with message-id and subject line Bug#950772: fixed in swupdate 2020.04-1 has caused the Debian Bug report #950772, regarding swupdate: FTBFS during separate arch/indep builds to be marked as done. This means that you claim that the problem has

Bug#963346: marked as done (golang-github-openshift-api: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/openshift/api github.com/openshift/api/annotations github.com/open

Your message dated Mon, 06 Jul 2020 10:49:50 + with message-id and subject line Bug#963346: fixed in golang-github-openshift-api 4.0+git20190508.81d064c-4 has caused the Debian Bug report #963346, regarding golang-github-openshift-api: FTBFS: dh_auto_test: error: cd _build && go test

Bug#959579: adapta-gtk-theme: FTBFS: make[2]: *** [Makefile:1040: all] Error 1

Hello Sudip, Just a quick update, I spoke to Franciscarlos (he will reply back here soon) and he intends to keep the package, so your patch will be accepted, he just wants to confirm that the package is working fine with the latest version of gnome. Meanwhile, can you push your changes to the

Bug#962653: marked as done (davical build depends on rst2pdf that might not be in bullseye)

Your message dated Mon, 06 Jul 2020 09:48:35 + with message-id and subject line Bug#962653: fixed in davical 1.1.9.3-1.1 has caused the Debian Bug report #962653, regarding davical build depends on rst2pdf that might not be in bullseye to be marked as done. This means that you claim that the

Bug#962653: [DAViCal-devel] Bug#962653: davical: diff for NMU version 1.1.9.3-1.1

On Mon, Jul 06, 2020 at 08:34:12AM +0200, Florian Schlichting wrote: > On Sun, Jul 05, 2020 at 12:46:52PM +0300, Adrian Bunk wrote: > > I've prepared an NMU for davical (versioned as 1.1.9.3-1.1) and uploaded > > it to DELAYED/3. Please feel free to tell me if I should cancel it. > > ACK > >

Bug#964356: marked as done (libcoarrays-{mpich,openmpi}-dev: not co-installable due to usr/lib/x86_64-linux-gnu/libcaf_mpi.a)

Your message dated Mon, 06 Jul 2020 09:18:59 + with message-id and subject line Bug#964356: fixed in open-coarrays 2.9.0-2 has caused the Debian Bug report #964356, regarding libcoarrays-{mpich,openmpi}-dev: not co-installable due to usr/lib/x86_64-linux-gnu/libcaf_mpi.a to be marked as

Processed: affects 964242 javahelper

Processing commands for cont...@bugs.debian.org: > affects 964242 javahelper Bug #964242 [bsdmainutils] bsdmainutils: depends on non-existing version of bsdextrautils Added indication that 964242 affects javahelper > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Re: Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr

Processing control commands: > reopen -1 Bug #962553 {Done: Adrian Bunk } [src:gff2aplot] gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may

Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr

Control: reopen -1 On Mon, Jul 06, 2020 at 01:07:22AM +0200, Graham Inggs wrote: > Hi Adrian > > On Sun, 5 Jul 2020 at 19:02, Adrian Bunk wrote: > > This is #962550. > > Are you sure? > > The failing test was with ligclib1 0.11.8-1 from testing and gff2aplot > 2.0-13 from unstable. Right you

Bug#964242: bsdmainutils: depends on non-existing version of bsdextrautils

affects 964242 javahelper thanks This also affects javahelper which depends on bsdmainutils and breaks a lot of Java packages in Debian currently. Regards, Markus signature.asc Description: OpenPGP digital signature

Bug#962275: snort: Failed to start LSB

Dear Thorsten, Indeed I have found two issues in the Snort package related to this bug report: 1.- The location of the libraries in /etc/snort.conf is not correct for different architectures. I need to find a way to ammend this value when the package gets compiled (or find a way to locate this

Bug#925749: omit the problematic test to fix this bug

I have opened a merge request https://salsa.debian.org/med-team/liblemon/-/merge_requests/3 to fix this bug. I think it is acceptable to omit the lgf_reader_writer_test. This test deals with IO part of the library. and it had minor influence on the whole. This merge request can be successfully

Bug#946915: marked as done (espresso FTBFS on archs where it build in the past)

Your message dated Mon, 6 Jul 2020 10:56:36 +0300 with message-id <20200706075636.GA6674@localhost> and subject line Re: Bug#946915: espresso FTBFS on archs where it build in the past has caused the Debian Bug report #946915, regarding espresso FTBFS on archs where it build in the past to be

Processed: tagging 956680

Processing commands for cont...@bugs.debian.org: > tags 956680 + fixed-upstream Bug #956680 [src:xneur] xneur: Please migrate to enchant-2 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 956680:

Processed: tagging 964360

Processing commands for cont...@bugs.debian.org: > tags 964360 + bullseye sid Bug #964360 [libghc-doctemplates-doc] libghc-doctemplates-doc: depends on unavailable haddock-interface-33 Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: found 964366 in 0.9.18-1

Processing commands for cont...@bugs.debian.org: > found 964366 0.9.18-1 Bug #964366 [bashtop] bashtop: insecure use of /tmp Marked as found in versions bashtop/0.9.18-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 964366:

Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)【请注意，邮件由mity...@gmail.com代发】

Hi! Sorry for my late reply. I preload libGLX_mesa.so.0 , and then run the code on the arm machine is ok. I tried to debug it, and then I found something different. The parameter of __glXLookupVendorByName is NVIDIA instead of mesa, it will dlopen libGLX_nvidia.so.0, but my Graphics Card is

Bug#951059: marked as done (mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt)

Your message dated Mon, 06 Jul 2020 06:48:43 + with message-id and subject line Bug#951059: fixed in mariadb-10.3 1:10.3.23-1 has caused the Debian Bug report #951059, regarding mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt to be marked as done. This means that you

  1   2   >