Bug#963761: [Pkg-javascript-devel] Bug#963761: Bug#963761: Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

2020-07-11 Thread merkys
On 2020-07-11 11:00, Jonas Smedegaard wrote: > Reason I suspect upstream-only tracking is wrong is that also Debian > changes can change ABI - either deliberately or accidentally. Most > notibly by adding/changing patches, but possibly also through changes to > build-dependencies. Agree. > I

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-07-11 Thread Johannes Schauer
Hi, I put Jessica and Ralf in CC because they are the solver experts. :) On Wed, 8 Jul 2020 18:27:54 +0200 Adam Borowski wrote: > This problem can't possibly be caused by elogind. A package may cause a > problem only if: > 1. some of its code is actually run (preinst, postinst, payload), or >

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-07-11 Thread Jessica Clarke
On 11 Jul 2020, at 23:47, Johannes Schauer wrote: > > Hi, > > I put Jessica and Ralf in CC because they are the solver experts. :) > > On Wed, 8 Jul 2020 18:27:54 +0200 Adam Borowski wrote: >> This problem can't possibly be caused by elogind. A package may cause a >> problem only if: >> 1.

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-07-11 Thread Johannes Schauer
Control: tag -1 + patch Hi Jessica, Quoting Jessica Clarke (2020-07-12 00:54:53) > Is this not the bug I fixed a while ago and you committed upstream > recently[1]? There hasn't been a dose3 upload to Debian yet with that fixed. > > Jess > > [1] >

Processed: Re: Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-07-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #964026 [apt-cudf] libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies) Added tag(s) patch. -- 964026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964026 Debian Bug Tracking System Contact

Bug#964879: [request-tracker-maintainers] Bug#964879: request-tracker4: FTBFS: broken by libgnupg-interface-perl

2020-07-11 Thread Andrew Ruthven
Hmmm, this is likely a bug in libgnupg-interface-perl v1.00. It should be able to work with both gpg v1 and v2.4, and certainly as I was reviewing the packaging for v1.00 it certainly tries to. Our RT v4.4.4 packages are forcing the use of gpg v1. I'll have a look at libgnupg-interface-perl

Bug#964849: "Invalid data found when processing input" got when using ffmpeg

2020-07-11 Thread Jonas Smedegaard
Quoting gulfstream (2020-07-11 05:10:41) > When I use ffmpeg to process any media file, it can not run > successfully, and an error message is got, such as, > > $ ffmpeg -i 5.m2ts > ffmpeg version 1.1.1 Copyright (c) 2000-2013 the FFmpeg developers > built on Jan 28 2013 09:43:45 with gcc

Bug#964334:

2020-07-11 Thread Marco De Donno
Same issue here on Debian 10.4 stable. What surprised me is that this went through up to stable (via the security updates). On 11.07.20 14:03, steve simmons wrote: > I have a similar looking issue. > > I updated Chromium, and since then, every few minutes there is crash. > Happens more often if

Bug#964815: it looks like dprof2calltree cannot be distributed with a GPL-2 work

2020-07-11 Thread Florian Weimer
* Nicholas D. Steeves: > Hi, > > Adrian Bunk writes: > >> On Fri, Jul 10, 2020 at 07:48:31PM -0400, Nicholas D Steeves wrote: >> >>> it would still not be DFSG-free, because it >>> fails the "desert island test" for snail mail. Were OmniTI Computer >>> Consulting would accept email, it would

Bug#964866: When upgrade from Stretch to Buster my development environment stop working and Arm (sama5d3) never mount his root on NFS

2020-07-11 Thread Dan Smolik
Package: nfs-kernel-server Version: 1:1.3.4-2.5 Severity: critical Tags: upstream I have using development environment for ARM (sama5d3) with root on NFS. Arm donwload kernel and DTB boots and mount root exported by my computer with Debian Buster. I works perfect with Ddebian Stretch but stop

Bug#964815: it looks like dprof2calltree cannot be distributed with a GPL-2 work

2020-07-11 Thread Francesco Poli
On Fri, 10 Jul 2020 18:33:32 -0400 Nicholas D Steeves wrote: [...] > Adrian Bunk writes: > > > On Fri, Jul 10, 2020 at 03:38:57PM -0400, Nicholas D Steeves wrote: > >>... > >> * Neither name of the company nor the names of its contributors may be > >> used to endorse or promote products

Bug#964640: marked as done (patsy: FTBFS: RuntimeError: Non Expected warning in `/<>/doc/spline-regression.rst` line 205)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 15:06:41 + with message-id and subject line Bug#964640: fixed in patsy 0.5.1-2 has caused the Debian Bug report #964640, regarding patsy: FTBFS: RuntimeError: Non Expected warning in `/<>/doc/spline-regression.rst` line 205 to be marked as done. This

Bug#964750: marked as done (hypercorn build-dependencies unsatisfiable in testing.)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 13:20:47 + with message-id and subject line Bug#964750: fixed in hypercorn 0.10.1-1 has caused the Debian Bug report #964750, regarding hypercorn build-dependencies unsatisfiable in testing. to be marked as done. This means that you claim that the problem

Processed: your mail

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 964246 + pending Bug #964246 [src:freetype] freetype: please test compile/link/run in autopkgtest Added tag(s) pending. > tags 964774 + pending Bug #964774 [src:freetype] freetype: libfreetype6-udeb should not depend on non-udeb libbrotli1

Processed: Re: Bug#964682: icu: FTBFS: dh_auto_test: error: cd source && make -j4 check VERBOSE=1 returned exit code 2

2020-07-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +confirmed Bug #964682 [src:icu] icu: FTBFS: dh_auto_test: error: cd source && make -j4 check VERBOSE=1 returned exit code 2 Added tag(s) confirmed. -- 964682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964682 Debian Bug Tracking System Contact

Bug#964682: icu: FTBFS: dh_auto_test: error: cd source && make -j4 check VERBOSE=1 returned exit code 2

2020-07-11 Thread GCS
Control: tags -1 +confirmed Hi, I'm looking for advice here on what would be the best move. On Thu, Jul 9, 2020 at 1:36 PM Lucas Nussbaum wrote: > Source: icu > Version: 67.1-2 > Severity: serious > Justification: FTBFS on amd64 > During a rebuild of all packages in sid, your package failed

Bug#964870: snapd: FTBFS: FAIL: squashfs_test.go:130: SquashfsTestSuite.TestInstallSimpleNoCp

2020-07-11 Thread Reinhard Tartler
Package: snapd Version: 2.44.1-2 Severity: serious While trying to rebuild the package, I noticed that one of the tests in the testsuite fails: === RUN Test -- FAIL: squashfs_test.go:130:

Bug#964815: marked as done (it looks like dprof2calltree cannot be distributed with a GPL-2 work)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 18:04:12 +0300 with message-id <20200711150412.GA23784@localhost> and subject line Re: Bug#964815: it looks like dprof2calltree cannot be distributed with a GPL-2 work has caused the Debian Bug report #964815, regarding it looks like dprof2calltree cannot be

Processed: found 964871 in 1.30.0+dfsg1-9

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 964871 1.30.0+dfsg1-9 Bug #964871 [rkt] rkt: FTBFS: make[2]: *** No rule to make target 'stage1/usr_from_coreoskvmhostsrcfly/usr_from_coreoskvmhostsrcfly.mk'. Stop. Marked as found in versions rkt/1.30.0+dfsg1-9. > thanks Stopping

Processed: your mail

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 963548 - moreinfo Bug #963548 [chromium] Received signal 11 SEGV_MAPERR Bug #964334 [chromium] segfault repeatedly Bug #964362 [chromium] chromium crash frequently, SEGV_MAPERR Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s)

Processed: found 964842 in 0.6.1.1-1

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 964842 0.6.1.1-1 Bug #964842 [src:haskell-yesod-auth-oauth2] haskell-yesod-auth-oauth2: BD-Uninstallable Marked as found in versions haskell-yesod-auth-oauth2/0.6.1.1-1. > thanks Stopping processing here. Please contact me if you need

Bug#963761: [Pkg-javascript-devel] Bug#963761: Bug#963761: Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

2020-07-11 Thread Jonas Smedegaard
Quoting Andrius Merkys (2020-07-10 11:52:40) > On 2020-07-10 12:38, Jonas Smedegaard wrote: > > I suspect you are wrong about relaxing lower bounds to only upstream > > part. > > I got this idea from the way the issue was fixed in node-expat [1]. > Could you explain why you think this is a bad

Bug#964630: marked as done (python-googleapi: FTBFS: ModuleNotFoundError: No module named 'uritemplate')

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 11:07:50 + with message-id and subject line Bug#964630: fixed in python-googleapi 1.7.11-4 has caused the Debian Bug report #964630, regarding python-googleapi: FTBFS: ModuleNotFoundError: No module named 'uritemplate' to be marked as done. This means

Bug#964384: marked as done (ulfius: FTBFS with recent libmicrohttpd)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 11:48:56 + with message-id and subject line Bug#964384: fixed in ulfius 2.6.8-1 has caused the Debian Bug report #964384, regarding ulfius: FTBFS with recent libmicrohttpd to be marked as done. This means that you claim that the problem has been dealt

Processed: notfound 964871 in 1.30.0+dfsg-7

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 964871 1.30.0+dfsg-7 Bug #964871 [rkt] rkt: FTBFS: make[2]: *** No rule to make target 'stage1/usr_from_coreoskvmhostsrcfly/usr_from_coreoskvmhostsrcfly.mk'. Stop. No longer marked as found in versions rkt/1.30.0+dfsg-7. > thanks

Bug#964849: 回复:Bug#964849: "Invalid data found when processing input" got when using ffmpeg

2020-07-11 Thread Jonas Smedegaard
Quoting 王钢林 (2020-07-11 09:01:33) > I am glad to receive your reply. But the ffmpeg was installed from debian > source by apt-get without any other ffmpeg version was installed. Please provide the output of each of these commands: echo $PATH which ffmpeg ffmpeg - Jonas -- * Jonas

Bug#963063: marked as done (nodejs breaks node-diff autopkgtest: Failed test: 41)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 08:35:50 + with message-id and subject line Bug#963063: fixed in node-diff 1.4.0~dfsg-4 has caused the Debian Bug report #963063, regarding nodejs breaks node-diff autopkgtest: Failed test: 41 to be marked as done. This means that you claim that the

Bug#964849: marked as done ("Invalid data found when processing input" got when using ffmpeg)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 13:01:11 +0200 with message-id <159446527199.2363368.904455430359268...@auryn.jones.dk> and subject line Re: Re: 回复:Bug#964849: "Invalid data found when processing input" got when using ffmpeg has caused the Debian Bug report #964849, regarding "Invalid data

Bug#964334:

2020-07-11 Thread steve simmons
I have a similar looking issue. I updated Chromium, and since then, every few minutes there is crash. Happens more often if I have about 10 tabs open (I usually open a folder of bookmarks) I am using version: Version 83.0.4103.116 (Developer Build) built on Debian 10.4, running on Debian 10.4

Processed: found 964841 in 0.15-2

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 964841 0.15-2 Bug #964841 [src:haskell-servant-server] haskell-servant-server: BD-Uninstallable Marked as found in versions haskell-servant-server/0.15-2. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#936875: marked as done (libieee1284: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 10:18:49 + with message-id and subject line Bug#936875: fixed in libieee1284 0.2.11-14 has caused the Debian Bug report #936875, regarding libieee1284: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#961849: marked as done (mariadb-10.3: CVE-2020-2814 CVE-2020-2812 CVE-2020-2760 CVE-2020-2752)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 11:47:11 + with message-id and subject line Bug#961849: fixed in mariadb-10.3 1:10.3.23-0+deb10u1 has caused the Debian Bug report #961849, regarding mariadb-10.3: CVE-2020-2814 CVE-2020-2812 CVE-2020-2760 CVE-2020-2752 to be marked as done. This means

Bug#961889: marked as done (src:gnutls28: Fails building chains with expired intermediate regardless of trust store)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 11:47:10 + with message-id and subject line Bug#961889: fixed in gnutls28 3.6.7-4+deb10u5 has caused the Debian Bug report #961889, regarding src:gnutls28: Fails building chains with expired intermediate regardless of trust store to be marked as done.

Processed: Bug#963063 marked as pending in node-diff

2020-07-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963063 [src:nodejs, src:node-diff] nodejs breaks node-diff autopkgtest: Failed test: 41 Added tag(s) pending. -- 963063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963063 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#963063: marked as pending in node-diff

2020-07-11 Thread Gianfranco Costamagna
Control: tag -1 pending Hello, Bug #963063 in node-diff 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#938841: marked as done (xchat: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 09:34:07 + with message-id and subject line Bug#938841: fixed in xchat 2.8.8-21 has caused the Debian Bug report #938841, regarding xchat: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#964849: Re: 回复:Bug#964849: "Invalid data found when processing input" got when using ffmpeg

2020-07-11 Thread wglxy
Thanks for your suggest. I got the reason which another software was installed with another ffmpeg, and set PATH point to it. Now I solved it. Thank you again! Best regards, Gulfstream > -原始邮件- > 发件人: "Jonas Smedegaard" > 发送时间: 2020-07-11 15:11:54 (星期六) > 收件人:

Bug#963478: marked as done (libgnustep-gui0.28: Missing sentinel in +[NSPDFImageRep imagePasteboardTypes] crashes applications)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 11:04:01 + with message-id and subject line Bug#963478: fixed in gnustep-gui 0.28.0-3 has caused the Debian Bug report #963478, regarding libgnustep-gui0.28: Missing sentinel in +[NSPDFImageRep imagePasteboardTypes] crashes applications to be marked as

Bug#938764: marked as done (util-vserver: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 18:32:36 + with message-id and subject line Bug#963775: Removed package(s) from unstable has caused the Debian Bug report #938764, regarding util-vserver: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#964866: Acknowledgement (When upgrade from Stretch to Buster my development environment stop working and Arm (sama5d3) never mount his root on NFS) - Solved

2020-07-11 Thread Daniel Smolik
Dear maintainer, please close the bug I found a solution. It looks like that Root on NFS require NFSv2. But on Buster is disabled. To enable it add to /etc/default/nfs-kernel-server RPCNFSDOPTS="-V 2" and restart  /etc/init.d/nfs-kernel-server . Regards             Dan -- Mydatex s

Bug#964056: marked as done (Should ksh93 be removed?)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 18:39:40 + with message-id and subject line Bug#963858: Removed package(s) from unstable has caused the Debian Bug report #964056, regarding Should ksh93 be removed? to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#964034: marked as done (ksh93: CVE-2019-14868)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 18:39:40 + with message-id and subject line Bug#963858: Removed package(s) from unstable has caused the Debian Bug report #964034, regarding ksh93: CVE-2019-14868 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#964884: gplaycli does not seem to be suitable for stable releases

2020-07-11 Thread Adrian Bunk
Package: gplaycli Severity: serious gplaycli in buster was broken by Google API changes (#950112) and already removed (#958231). This does not give confidence that the package in bullseye can be kept working for the during the time bullseye is supported.

Bug#937490: marked as done (pynifti: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 18:59:42 + with message-id and subject line Bug#964030: Removed package(s) from unstable has caused the Debian Bug report #937490, regarding pynifti: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#938057: marked as done (python-pychart: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 19:00:56 + with message-id and subject line Bug#964049: Removed package(s) from unstable has caused the Debian Bug report #938057, regarding python-pychart: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#937645: marked as done (python-cjson: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 19:03:44 + with message-id and subject line Bug#964051: Removed package(s) from unstable has caused the Debian Bug report #937645, regarding python-cjson: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938315: marked as done (qpid-qmf: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 19:04:22 + with message-id and subject line Bug#964052: Removed package(s) from unstable has caused the Debian Bug report #938315, regarding qpid-qmf: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#964886: src:paramiko: fails to migrate to testing for too long: unresolved RC bug

2020-07-11 Thread Paul Gevers
Source: paramiko Version: 2.6.0-2 Severity: serious Control: close -1 2.7.1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 960899 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are

Processed: src:paramiko: fails to migrate to testing for too long: unresolved RC bug

2020-07-11 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.7.1-1 Bug #964886 [src:paramiko] src:paramiko: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions paramiko/2.7.1-1. Bug #964886 [src:paramiko] src:paramiko: fails to migrate to testing for too long: unresolved RC bug

Bug#964888: src:python-cobra: fails to migrate to testing for too long: FTBFS on s390x

2020-07-11 Thread Paul Gevers
Source: python-cobra Version: 0.14.2-2 Severity: serious Control: close -1 0.18.0-3 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 961224 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are

Processed: src:python-cobra: fails to migrate to testing for too long: FTBFS on s390x

2020-07-11 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.18.0-3 Bug #964888 [src:python-cobra] src:python-cobra: fails to migrate to testing for too long: FTBFS on s390x Marked as fixed in versions python-cobra/0.18.0-3. Bug #964888 [src:python-cobra] src:python-cobra: fails to migrate to testing for too

Bug#937378: marked as done (purity-ng: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 19:22:26 + with message-id and subject line Bug#964396: Removed package(s) from unstable has caused the Debian Bug report #937378, regarding purity-ng: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#945545: marked as done (xpp FTBFS: error: invalid use of incomplete type 'ipp_t')

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 19:27:54 + with message-id and subject line Bug#964481: Removed package(s) from unstable has caused the Debian Bug report #945545, regarding xpp FTBFS: error: invalid use of incomplete type 'ipp_t' to be marked as done. This means that you claim that the

Bug#964899: FTBFS: test suites fails with 1 failures, 8 errors

2020-07-11 Thread Antonio Terceiro
Source: ruby-net-dns Severity: serious Tags: ftbfs Justification: fails to build from source ruby-new-dns currently fails to build from source in unstable. Several tests fail like this: Error: Minitest::Result#test_should_return_state_without_exception: NoMethodError: undefined method `split'

Bug#924221: marked as done (syslinux-themes-debian-{squeeze,wheezy}: syslinux-common has changed the filesystem layout)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 19:45:30 + with message-id and subject line Bug#964487: Removed package(s) from unstable has caused the Debian Bug report #924221, regarding syslinux-themes-debian-{squeeze,wheezy}: syslinux-common has changed the filesystem layout to be marked as done.

Processed: your mail

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 963548 964287 964817 964451 964760 Bug #963548 [chromium] Received signal 11 SEGV_MAPERR Bug #964334 [chromium] segfault repeatedly Bug #964362 [chromium] chromium crash frequently, SEGV_MAPERR Bug #964287 [chromium] chromium: crashes

Processed: Re: Bug#936805: kodi: Python2 removal in sid/bullseye

2020-07-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 confirmed upstream Bug #936805 [src:kodi] kodi: Python2 removal in sid/bullseye Added tag(s) confirmed and upstream. -- 936805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#964451: marked as done (chromium (83.0.4103.116-1~deb10u2) constantly crashes and slow)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 16:04:34 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-3 has caused the Debian Bug report #963548, regarding chromium (83.0.4103.116-1~deb10u2) constantly crashes and slow to be marked as done. This means that you claim

Bug#964287: marked as done (chromium: crashes after page interaction due to a double free)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 16:04:34 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-3 has caused the Debian Bug report #963548, regarding chromium: crashes after page interaction due to a double free to be marked as done. This means that you claim that

Bug#964817: marked as done (chromium 83.0.4103.116-1~deb10u2 crashes frequently)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 16:04:34 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-3 has caused the Debian Bug report #963548, regarding chromium 83.0.4103.116-1~deb10u2 crashes frequently to be marked as done. This means that you claim that the

Bug#963548: marked as done (Received signal 11 SEGV_MAPERR)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 16:04:34 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-3 has caused the Debian Bug report #963548, regarding Received signal 11 SEGV_MAPERR to be marked as done. This means that you claim that the problem has been dealt

Bug#964334: marked as done (segfault repeatedly)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 16:04:34 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-3 has caused the Debian Bug report #963548, regarding segfault repeatedly to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#964760: marked as done (chromium: Chromium 83.0.4103.116-2 crash : SEGV_MAPERR)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 16:04:34 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-3 has caused the Debian Bug report #963548, regarding chromium: Chromium 83.0.4103.116-2 crash : SEGV_MAPERR to be marked as done. This means that you claim that the

Processed: affects 964878

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 964878 msva-perl src:mod-gnutls Bug #964878 [libgnupg-interface-perl] libgnupg-interface-perl: breaks monkeysphere-validation-agent Added indication that 964878 affects msva-perl and src:mod-gnutls > thanks Stopping processing here.

Bug#964880: npm: test failures in ppc64el and s390x

2020-07-11 Thread Gianfranco Costamagna
Source: npm Version: 6.14.6+ds-1 Severity: serious Hello, looks like one test is failing on ppc64el and s390x. Could you please have a look? this on s390x

Bug#937519: marked as done (RM: pyrex -- RoQA; dead upstream; no rdeps; blocking py2 removal)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 17:56:18 + with message-id and subject line Bug#937519: Removed package(s) from unstable has caused the Debian Bug report #937519, regarding RM: pyrex -- RoQA; dead upstream; no rdeps; blocking py2 removal to be marked as done. This means that you claim

Bug#964120: marked as done (not compatible with current Gajim, no more upstream support)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 17:59:46 + with message-id and subject line Bug#963604: Removed package(s) from unstable has caused the Debian Bug report #964120, regarding not compatible with current Gajim, no more upstream support to be marked as done. This means that you claim that

Bug#942999: marked as done (doxypy: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 17:59:13 + with message-id and subject line Bug#963572: Removed package(s) from unstable has caused the Debian Bug report #942999, regarding doxypy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#936805: kodi: Python2 removal in sid/bullseye

2020-07-11 Thread Bálint Réczey
Control: tags -1 confirmed upstream Hi, Vasyl Gello ezt írta (időpont: 2020. júl. 5., V, 18:42): > > Hi Nicholas! > > I joined Debian to package Kodi 19.0 and full archive of binary addons and I > already made a > significant progress on the way: > > 1. The build dependencies for kodi not

Processed: Bug is also in buster

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 962218 Bug #962218 {Done: Andreas Metzler } [src:gnutls28] gnutls28: build fails on IPv6-only buildds Unarchived Bug 962218 > found 962218 3.6.7-4 Bug #962218 {Done: Andreas Metzler } [src:gnutls28] gnutls28: build fails on IPv6-only

Bug#964362: marked as done (chromium crash frequently, SEGV_MAPERR)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 16:04:34 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-3 has caused the Debian Bug report #963548, regarding chromium crash frequently, SEGV_MAPERR to be marked as done. This means that you claim that the problem has been

Bug#964879: request-tracker4: FTBFS: broken by libgnupg-interface-perl

2020-07-11 Thread Niko Tyni
Source: request-tracker4 Version: 4.4.4-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: libgnupg-interface-p...@packages.debian.org This package fails its test suite with libgnupg-interface-perl_1.00-1, which recently entered sid. Many (but not all) of the test suite failures seem to be about

Bug#964878: libgnupg-interface-perl: breaks monkeysphere-validation-agent

2020-07-11 Thread Niko Tyni
Package: libgnupg-interface-perl Version: 1.00-1 Severity: serious Affects: msva-perl, src:mod-gnutls X-Debbugs-Cc: msva-p...@packages.debian.org, mod-gnu...@packages.debian.org The new version of libgnupg-interface-perl breaks /usr/bin/monkeysphere-validation-agent in msva-perl_0.9.2-1. This

Bug#964880: [Pkg-javascript-devel] Bug#964880: npm: test failures in ppc64el and s390x

2020-07-11 Thread Xavier
Control: forcemerge -1 964854 Control: forwarded 964854 https://github.com/npm/cli/issues/1455 Le 11/07/2020 à 19:54, Gianfranco Costamagna a écrit : > Source: npm > Version: 6.14.6+ds-1 > Severity: serious > > Hello, looks like one test is failing on ppc64el and s390x. > Could you please have a

Processed: adjust meta data such that it doesn't block dpkg anymore

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 964475 src:apt 2.1.6 Bug #964475 {Done: Julian Andres Klode } [src:dpkg, src:apt] dpkg breaks apt autopkgtest: dpkg: error: unknown option --foreign-architecture Bug reassigned from package 'src:dpkg, src:apt' to 'src:apt'. No longer

Processed: Re: [Pkg-javascript-devel] Bug#964880: npm: test failures in ppc64el and s390x

2020-07-11 Thread Debian Bug Tracking System
Processing control commands: > forcemerge -1 964854 Bug #964880 [src:npm] npm: test failures in ppc64el and s390x Bug #964880 [src:npm] npm: test failures in ppc64el and s390x Marked as found in versions npm/6.14.5+ds-1. Bug #964854 [src:npm] npm: autopkgtests failures on s390x Severity set to

Bug#964581: marked as done (angelscript: binary-all FTBFS)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 19:48:32 + with message-id and subject line Bug#964581: fixed in angelscript 2.34.0+ds-3.1 has caused the Debian Bug report #964581, regarding angelscript: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt

Bug#964902: libio-socket-ip-perl: AI_ADDRCONFIG breaks many test suites on IPv6-only hosts

2020-07-11 Thread Niko Tyni
Package: libio-socket-ip-perl Version: 0.39-2 Severity: serious Tags: patch ipv6 This is a follow-up for #962047 "fails to build on IPv6-only buildds". The background here is that a while ago new official build daemons were added that only have IPv6 connectivity, and this exposed a new class of

Bug#962047: Bug#962318: libmojolicious-perl: build fails on IPv6-only buildds

2020-07-11 Thread Niko Tyni
On Mon, Jun 15, 2020 at 09:41:18PM +0300, Niko Tyni wrote: > On Fri, Jun 12, 2020 at 06:58:15PM +0300, Niko Tyni wrote: > > > I have not had the tuits yet for looking at IO::Socket::IP properly. > > It seems to me that it could look at the address and pass AI_NUMERICHOST > > to getaddrinfo(3) if

Bug#964616: marked as done (maint-guide: FTBFS: build-dependency not installable: libopencc2-data)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 20:45:54 + with message-id and subject line Bug#964616: fixed in maint-guide 1.2.45 has caused the Debian Bug report #964616, regarding maint-guide: FTBFS: build-dependency not installable: libopencc2-data to be marked as done. This means that you claim

Bug#964819: rsyncd fails to access some directories

2020-07-11 Thread Samuel Henrique
Hello Winfried, Thank you for reporting this issue, Could you please check if the same issue happens with rsync 3.2.2-2 ? This package is currently in unstable and it will reach testing in about 24 hours. Alternatively, you can do the following to test: comment out (or remove) the following

Bug#964819: rsyncd fails to access some directories

2020-07-11 Thread Samuel Henrique
> Could you please check if the same issue happens with rsync 3.2.2-2 ? > This package is currently in unstable and it will reach testing in > about 24 hours. I just noticed that 3.2.2-1 is on testing already, this is the first package version to contain the fix, please update your system and

Bug#945680: marked as done (opensvc: Python2 removal in sid/bullseye)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 21:33:34 + with message-id and subject line Bug#964831: Removed package(s) from unstable has caused the Debian Bug report #945680, regarding opensvc: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#872208: marked as done (opensvc: fdisk dependency needed)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 21:33:34 + with message-id and subject line Bug#964831: Removed package(s) from unstable has caused the Debian Bug report #872208, regarding opensvc: fdisk dependency needed to be marked as done. This means that you claim that the problem has been dealt

Processed: py2removal bugs severity updates - 2020-07-11 21:34:23.705586+00:00

2020-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See