Bug#974983: marked as done (TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType')

2020-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Nov 2020 07:48:18 + with message-id and subject line Bug#974983: fixed in apt-listchanges 3.22+nmu2 has caused the Debian Bug report #974983, regarding TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' to be marked as done.

Bug#975020: marked as done (version mismatch between package and manifest.json)

2020-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Nov 2020 07:33:21 + with message-id and subject line Bug#975020: fixed in dav4tbsync 1.23-1 has caused the Debian Bug report #975020, regarding version mismatch between package and manifest.json to be marked as done. This means that you claim that the problem has

Bug#975012: dplfin: FTBFS: 69% tests passed, 15 tests failed out of 49

2020-11-17 Thread Anton Gladky
Hi Sebastian, Thanks for your bug report. I am preparing a transition to boost 1.74 and tested my minimal changes to fix #974948. It worked locally. Anyway I have reverted the fix for #974948 and it did not help. So the reason is somewhere else. Sorry for the inconvenience. Best regards Anton

Processed: affects 975009

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 975009 - node-grunt-webpack Bug #975009 [node-schema-utils] node-schema-utils breaking change Removed indication that 975009 affects node-grunt-webpack > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: affects 975009

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 975009 - node-react Bug #975009 [node-schema-utils] node-schema-utils breaking change Removed indication that 975009 affects node-react > thanks Stopping processing here. Please contact me if you need assistance. -- 975009:

Processed: affects 975009

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 975009 - node-abab Bug #975009 [node-schema-utils] node-schema-utils breaking change Removed indication that 975009 affects node-abab > thanks Stopping processing here. Please contact me if you need assistance. -- 975009:

Processed: affects 975009

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 975009 - node-xterm Bug #975009 [node-schema-utils] node-schema-utils breaking change Removed indication that 975009 affects node-xterm > thanks Stopping processing here. Please contact me if you need assistance. -- 975009:

Processed: cp2k: test failure on armhf and i386 with libint2

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #948909 [src:cp2k] cp2k: test failure on armhf and i386 with libint2 Severity set to 'important' from 'serious' -- 948909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948909 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#948909: cp2k: test failure on armhf and i386 with libint2

2020-11-17 Thread Graham Inggs
Control: severity -1 important Downgrading severity since the autopkgtests are now passing [1][2] and no longer blocking migration. [1] https://ci.debian.net/packages/c/cp2k/testing/armhf/ [2] https://ci.debian.net/packages/c/cp2k/testing/i386/

Bug#974950: vim-scripts: missing vim-addon-manager registry file

2020-11-17 Thread James McCoy
On Tue, Nov 17, 2020 at 02:43:55PM -0300, Antonio Terceiro wrote: > On Mon, Nov 16, 2020 at 07:04:26PM -0500, James McCoy wrote: > > On Mon, Nov 16, 2020 at 08:41:57PM -0300, Antonio Terceiro wrote: > > > The new vim-scripts breaks existing usage with vim-addon-manager. > > > > > > It is missing

Bug#973459: uim: FAIL: test-composer.scm

2020-11-17 Thread dai
On Tue, Nov 17, 2020 at 09:11:54AM +0900, Takatsugu Nokubi wrote: > I need the test2/test-suite.log file, so I had tried to reproduce it > on abel twice, but > I couldn't get the error, just succeeded. > > Can I get the test2/test-suite.log file from anywhere? test2/test-suite.log is printed in

Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Francesco Poli
Control: tag -1 - moreinfo On Tue, 17 Nov 2020 20:36:50 +0100 Axel Beckert wrote: [...] > Francesco Poli wrote: [...] > > [notify-osd](https://packages.debian.org/sid/amd64/notify-osd/filelist) > > does not seem to. > > Indeed, thanks! > > > On the other hand, > >

Processed: Re: Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - moreinfo Bug #974949 [systray-mdstat] systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown Removed tag(s) moreinfo. -- 974949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974949 Debian Bug Tracking System Contact

Processed: tagging 922405, tagging 964873, found 966714 in 3.6.14-2, tagging 968965, tagging 887649

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 922405 + upstream Bug #922405 [pocl] pocl : FTBFS on sid - testsuite has failed on ppc64el arch Added tag(s) upstream. > tags 964873 + experimental Bug #964873 [src:consul] consul: FTBFS:

Processed: Re: libjbig0: invalid ELF header when loading libjbig.so.0

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo unreproducible Bug #974754 [libjbig0] libjbig0: invalid ELF header when loading libjbig.so.0 Added tag(s) moreinfo and unreproducible. -- 974754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974754 Debian Bug Tracking System Contact

Bug#974754: libjbig0: invalid ELF header when loading libjbig.so.0

2020-11-17 Thread Andreas Beckmann
Control: tag -1 moreinfo unreproducible On Sat, 14 Nov 2020 10:41:26 -0700 Ryan Beethe wrote: > I use libjbig indirectly through the php-gd package. When running php > from the command line, I get the following error: > > PHP Warning: PHP Startup: Unable to load dynamic library 'gd.so' >

Bug#975020: version mismatch between package and manifest.json

2020-11-17 Thread Martin
Package: webext-dav4tbsync Version: 1.21-1 Severity: grave Justification: makes the package in question unusable by most or all users Dear Mechthilde, many thanks for maintaining the tbsync packages! Very much appreciated, especially the support of Debian 10 (buster). The zip file

Processed: reassign 975010 to dash, forcibly merging 974705 975010

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 975010 dash Bug #975010 [src:systemd] src:systemd: autopkgtest regression in testing: timedated test times out Bug reassigned from package 'src:systemd' to 'dash'. No longer marked as found in versions systemd/246.6-2. Ignoring request

Bug#957120: marked as done (darksnow: ftbfs with GCC-10)

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 22:18:45 + with message-id and subject line Bug#957120: fixed in darksnow 0.7.1-3 has caused the Debian Bug report #957120, regarding darksnow: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#954542: marked as done (haproxy: FTBFS: AttributeError: module 'cgi' has no attribute 'escape')

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 22:56:26 +0100 with message-id <80e0e3a1-a2ac-8c8a-d252-a2165d9d2...@debian.org> and subject line Re: fixed 954542 in 2.0.13-2 has caused the Debian Bug report #954542, regarding haproxy: FTBFS: AttributeError: module 'cgi' has no attribute 'escape' to be marked

Bug#975012: dplfin: FTBFS: 69% tests passed, 15 tests failed out of 49

2020-11-17 Thread Sebastian Ramacher
Source: dolfin Version: 2019.2.0~git20200629.946dbd3-6 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org With the last upload to fix #974947, dolfin now FTBFS everywhere: | 69% tests passed, 15 tests

Bug#975006: marked as done (libgnatcoll-db-bin: missing Breaks+Replaces: libgnatcoll-sqlite-bin)

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 21:33:44 + with message-id and subject line Bug#975006: fixed in libgnatcoll-db 21.0.0-3 has caused the Debian Bug report #975006, regarding libgnatcoll-db-bin: missing Breaks+Replaces: libgnatcoll-sqlite-bin to be marked as done. This means that you claim

Processed: unblock 968912 with 974058

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unblock 968912 with 974058 Bug #968912 [release.debian.org] transition: perl 5.32 968912 was blocked by: 974021 974143 961152 974134 961157 974063 972275 964902 974055 961155 973010 960863 972274 961208 974704 974574 974061 974170 974058 961154

Processed: retitle 975009 to node-schema-utils breaking change

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 975009 node-schema-utils breaking change Bug #975009 [node-schema-utils] node-schema-utils breacking change Changed Bug title to 'node-schema-utils breaking change' from 'node-schema-utils breacking change'. > thanks Stopping processing

Bug#975010: src:systemd: autopkgtest regression in testing: timedated test times out

2020-11-17 Thread Paul Gevers
Source: systemd Version: 246.6-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression timesout Dear maintainer(s), Recently (somewhere this week) the autopkgtest of systemd started to fail in testing on all architectures we run it on

Processed: found 975009 in 3.0.0-1, notfound 975009 in 2.6.6-1

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 975009 3.0.0-1 Bug #975009 [node-schema-utils] node-schema-utils breacking change Marked as found in versions node-schema-utils/3.0.0-1. > notfound 975009 2.6.6-1 Bug #975009 [node-schema-utils] node-schema-utils breacking change No longer

Processed: tagging 975009

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 975009 + experimental Bug #975009 [node-schema-utils] node-schema-utils breacking change Added tag(s) experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 975009:

Processed: tagging 975009

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 975009 + ftbfs Bug #975009 [node-schema-utils] node-schema-utils breacking change Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 975009:

Processed: affects 975009

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 975009 node-abab node-babel-loader node-cache-loader > node-caniuse-lite node-compression-webpack-plugin node-css-loader > node-extract-text-webpack-plugin node-file-loader node-grunt-webpack > node-mini-css-extract-plugin

Bug#975009: node-schema-utils breacking change

2020-11-17 Thread Xavier Guimard
Package: node-schema-utils Version: 2.6.6-1 Severity: serious node-schema-utils API changed: `require("schema-utils")` becomes `require("schema-utils").validate`

Bug#975006: libgnatcoll-db-bin: missing Breaks+Replaces: libgnatcoll-sqlite-bin

2020-11-17 Thread Andreas Beckmann
Package: libgnatcoll-db-bin Version: 21.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because

Processed: python3-paraview: ships vtk modules which are also packaged by python3-vtk9 in experimental

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + python3-vtk9 Bug #975004 [python3-paraview] python3-paraview: ships vtk modules which are also packaged by python3-vtk9 in experimental Added indication that 975004 affects python3-vtk9 -- 975004:

Bug#975004: python3-paraview: ships vtk modules which are also packaged by python3-vtk9 in experimental

2020-11-17 Thread Andreas Beckmann
Package: python3-paraview Version: 5.7.0-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + python3-vtk9 Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files.

Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Axel Beckert
Control: tag -1 + moreinfo Hi Francesco, (Hint: The reason for the moreinfo tag is near the end of the mail.) Francesco Poli wrote: > > So despite it's name "notification-daemon" looking like being the most > > generic one of all of them, it looks to me as if it does not to > > provide that

Processed: Re: Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + moreinfo Bug #974949 [systray-mdstat] systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown Added tag(s) moreinfo. -- 974949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974949 Debian Bug Tracking System Contact

Bug#974073: Info received (gcc-10: arm64 internal compiler error: canonical types differ for identical types)

2020-11-17 Thread Wookey
So this is the failing command from the build: g++ -c -o /home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o -MMD -MT /home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o -MF

Bug#973472: fetchmail: Fails to connect using SSL

2020-11-17 Thread GCS
On Wed, Nov 11, 2020 at 9:23 PM Kurt Roeckx wrote: > On Tue, Nov 10, 2020 at 08:54:22PM +0100, László Böszörményi (GCS) wrote: > > Thanks for possibly the best solution. Meanwhile OpenSSL 1.1.1h-1 > > migrated to testing; closing this bug report. > > That is not a fix. Fetchmail should not be

Processed: desproxy: diff for NMU version 0.1.0~pre3-10.1

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tags 957128 + patch Bug #957128 [src:desproxy] desproxy: ftbfs with GCC-10 Added tag(s) patch. > tags 957128 + pending Bug #957128 [src:desproxy] desproxy: ftbfs with GCC-10 Added tag(s) pending. -- 957128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957128

Bug#957128: desproxy: diff for NMU version 0.1.0~pre3-10.1

2020-11-17 Thread Sudip Mukherjee
Control: tags 957128 + patch Control: tags 957128 + pending -- Dear maintainer, I've prepared an NMU for desproxy (versioned as 0.1.0~pre3-10.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru desproxy-0.1.0~pre3/debian/changelog

Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Francesco Poli
On Tue, 17 Nov 2020 16:38:42 +0100 Axel Beckert wrote: [...] > Francesco Poli wrote: [...] > > Package notification-daemon does not seem to ship any *.service file: > > > > $ dpkg -L notification-daemon | grep -i service > > But other notification daemons seem to do. > > So despite it's name

Bug#974918: libnotcurses2,libnotcurses++2: missing Breaks+Replaces: libnotcurses1/libnotcurses++1 (>= 2)

2020-11-17 Thread Nick Black
> That would have been sufficient for the file conflict, but I assumed > that the forgotten soname bump makes lib*1 (>= 2) not neccessarily > broken, but at least undesired versions. makes sense. thanks for the explanation, and thanks once again for the bug report and your well-known vigilance!

Bug#972481: marked as done (ruby-pygments.rb: FTBFS, tests failure (due to new pygments))

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 16:48:50 + with message-id and subject line Bug#972481: fixed in ruby-pygments.rb 1.2.1-2 has caused the Debian Bug report #972481, regarding ruby-pygments.rb: FTBFS, tests failure (due to new pygments) to be marked as done. This means that you claim that

Processed: Bug#972481 marked as pending in ruby-pygments.rb

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #972481 [src:ruby-pygments.rb] ruby-pygments.rb: FTBFS, tests failure (due to new pygments) Added tag(s) pending. -- 972481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972481 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#972481: marked as pending in ruby-pygments.rb

2020-11-17 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #972481 in ruby-pygments.rb reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Re: Bug#974915 closed by Debian FTP Masters (reply to Roger Shimizu ) (Bug#974915: fixed in golang-github-cheekybits-genny 1.0.0-6)

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.0.0-6 Bug #974915 {Done: Roger Shimizu } [genny] genny: missing Breaks+Replaces: golang-github-cheekybits-genny-dev (<< 1.0.0-4) Marked as found in versions golang-github-cheekybits-genny/1.0.0-6; no longer marked as fixed in versions

Bug#974915: closed by Debian FTP Masters (reply to Roger Shimizu ) (Bug#974915: fixed in golang-github-cheekybits-genny 1.0.0-6)

2020-11-17 Thread Andreas Beckmann
Control: found -1 1.0.0-6 On 11/16/20 6:51 PM, Debian Bug Tracking System wrote: > - Add Breaks+Replaces: golang-github-cheekybits-genny-dev (<< 1.0.0-4) Unfortunately the B+R ended up in the golang-github-cheekybits-genny-dev package (as a superfluous self-relation), while they need to be

Bug#974918: libnotcurses2,libnotcurses++2: missing Breaks+Replaces: libnotcurses1/libnotcurses++1 (>= 2)

2020-11-17 Thread Andreas Beckmann
On 11/17/20 5:32 AM, Nick Black wrote: > the version constraints could have been tightened to (>= 2.0.4), > but I didn't see this as adding particularly much value. Thanks That would have been sufficient for the file conflict, but I assumed that the forgotten soname bump makes lib*1 (>= 2) not

Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Axel Beckert
Hi Francesco, Francesco Poli wrote: > > > I have notification-daemon installed on my system: > > > > That's strange. > > > > Can you send me the output of this command on the system where this > > happened? > > > > $ fgrep org.freedesktop.Notifications /usr/share/dbus-1/services/*.service > >

Bug#974873: postgresql-rum: autopkgtest failure

2020-11-17 Thread Christoph Berg
Re: Sebastian Ramacher > postgresql-rum is currently unable to migrate due to autopkgtest > regressions on arm64 and ppc64el: > | +FATAL: failed to load summary > "/usr/lib/postgresql/13/lib/bitcode/rum.index.bc": Invalid summary version 9. > Version should be in the range [1-8]. Hi, this is

Bug#974983: TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'

2020-11-17 Thread Jochen Sprickerhof
Package: apt-listchanges Version: 3.22+nmu1 Severity: grave Tags: patch Justification: renders package unusable Hi, got this with the latest version: Traceback (most recent call last): File "/usr/bin/apt-listchanges", line 323, in main(config) File "/usr/bin/apt-listchanges", line 115,

Bug#974430: marked as done (plasma-workspace-wayland: Undefined symbols: Need rebuild ?)

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 14:34:25 + with message-id and subject line Bug#974430: fixed in plasma-workspace 4:5.19.5-5 has caused the Debian Bug report #974430, regarding plasma-workspace-wayland: Undefined symbols: Need rebuild ? to be marked as done. This means that you claim

Processed: Re: Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - moreinfo Bug #974949 [systray-mdstat] systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown Removed tag(s) moreinfo. -- 974949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974949 Debian Bug Tracking System Contact

Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Francesco Poli
Control: tag -1 - moreinfo On Tue, 17 Nov 2020 12:58:17 +0100 Axel Beckert wrote: [...] > Francesco Poli wrote: [...] > > I have notification-daemon installed on my system: > > That's strange. > > Can you send me the output of this command on the system where this > happened? > > $ fgrep

Bug#939477: marked as done (incomplete copyright file, and copyright file includes null characters)

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 13:48:23 + with message-id and subject line Bug#939477: fixed in emscripten 2.0.8~dfsg1-8 has caused the Debian Bug report #939477, regarding incomplete copyright file, and copyright file includes null characters to be marked as done. This means that you

Processed: unarchiving 940939, reassign 940966 to src:kirigami2, forcibly merging 940939 940966 ...

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 940939 Bug #940939 {Done: Maximiliano Curia } [src:kirigami2] plasma-discover: After KDE Frameworks 5.62 update plasma-discover doesn't start Unarchived Bug 940939 > reassign 940966 src:kirigami2 Bug #940966

Bug#974093: marked as done (ruby-httparty breaks ruby-gitlab autopkgtest: Gitlab::Client.create_merge_request_discussion posts the correct resource)

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 12:33:29 + with message-id and subject line Bug#974093: fixed in ruby-httparty 0.18.1-2 has caused the Debian Bug report #974093, regarding ruby-httparty breaks ruby-gitlab autopkgtest: Gitlab::Client.create_merge_request_discussion posts the correct

Processed: src:fonts-urw-base35: fails to migrate to testing for too long: Depends on version of ghostscript that's not migrating

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > close -1 20200910-1 Bug #974970 [src:fonts-urw-base35] src:fonts-urw-base35: fails to migrate to testing for too long: Depends on version of ghostscript that's not migrating Marked as fixed in versions fonts-urw-base35/20200910-1. Bug #974970 [src:fonts-urw-base35]

Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Axel Beckert
Control: tag -1 + moreinfo Hi Francesco, Francesco Poli wrote: > > > > $ org.freedesktop.DBus.Error.ServiceUnknown: The name > > > > org.freedesktop.Notifications was not provided by any .service files > > > > Seems to be a missing dependency on notification-daemon. > > I have

Processed: Re: Bug#974949: systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + moreinfo Bug #974949 [systray-mdstat] systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown Added tag(s) moreinfo. -- 974949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974949 Debian Bug Tracking System Contact

Bug#974939: machine does not boot

2020-11-17 Thread Ben Hutchings
Control: tag -1 moreinfo Control: severity -1 important On Mon, 2020-11-16 at 19:41 +, Toni wrote: > Package: src:linux > Version: 4.19.152-1 > Severity: critical > > > Hi, > > with the two latest kernels, linux-image-4.19.0-12-amd64 and > linux-image-4.19.0-11-amd64, my machine does not

Processed: Re: Bug#974939: machine does not boot

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #974939 [src:linux] machine does not boot Bug #971535 [src:linux] this package makes my laptop almost unbootable Added tag(s) moreinfo. Added tag(s) moreinfo. > severity -1 important Bug #974939 [src:linux] machine does not boot Bug #971535

Processed: maintenance

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 971535 critical Bug #971535 [src:linux] this package makes my laptop almost unbootable Severity set to 'critical' from 'important' > merge 974939 971535 Bug #974939 [src:linux] machine does not boot Bug #974939 [src:linux] machine does

Processed (with 1 error): maintenance

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 974939 971535 Bug #974939 [src:linux] machine does not boot Unable to merge bugs because: severity of #971535 is 'important' not 'critical' Failed to merge 974939: Did not alter merged bugs. > thanks Stopping processing here. Please

Bug#972041: not a showstopper

2020-11-17 Thread Hans-Christoph Steiner
Control: severity -1 normal I don't think packages should be kicked of testing for this issue since things are working. We will update as needed if the ABI in question changes in future updates.

Processed: not a showstopper

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #972041 [src:android-platform-external-libunwind] android-platform-external-libunwind uses an internal interface of p7zip-full Severity set to 'normal' from 'serious' -- 972041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972041

Bug#973405: marked as done (fakeroot on amd64 stopped supporting armel, armhf and mipsel chroots)

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 09:18:23 + with message-id and subject line Bug#973405: fixed in fakeroot 1.25.3-1.1 has caused the Debian Bug report #973405, regarding fakeroot on amd64 stopped supporting armel, armhf and mipsel chroots to be marked as done. This means that you claim

Processed: Bug#974093 marked as pending in ruby-httparty

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974093 [src:ruby-httparty, src:ruby-gitlab] ruby-httparty breaks ruby-gitlab autopkgtest: Gitlab::Client.create_merge_request_discussion posts the correct resource Added tag(s) pending. -- 974093:

Bug#974093: marked as pending in ruby-httparty

2020-11-17 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #974093 in ruby-httparty 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#973468: marked as done (gnome-shell-extension-multi-monitors: Broken by GNOME 3.38)

2020-11-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Nov 2020 08:48:45 + with message-id and subject line Bug#973468: fixed in gnome-shell-extension-multi-monitors 22-1 has caused the Debian Bug report #973468, regarding gnome-shell-extension-multi-monitors: Broken by GNOME 3.38 to be marked as done. This means that

Processed: bug 974093 is forwarded to https://github.com/NARKOZ/gitlab/issues/591

2020-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 974093 https://github.com/NARKOZ/gitlab/issues/591 Bug #974093 [src:ruby-httparty, src:ruby-gitlab] ruby-httparty breaks ruby-gitlab autopkgtest: Gitlab::Client.create_merge_request_discussion posts the correct resource Set Bug

Bug#974563: corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654

2020-11-17 Thread Markus Koschany
Control: severity -1 normal Am Montag, den 16.11.2020, 09:22 -0300 schrieb Alejandro Taboada: > Hi Markus, > > Sorry for the delay. With this patch works when is applied only to 1 node. > The services restart and the arm resources are up. > The problem appears again when I install the patch on a

Processed: Re: Bug#974563: corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654

2020-11-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #974563 [pacemaker] corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654 Severity set to 'normal' from 'grave' -- 974563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974563 Debian Bug