Bug#938073: fssync marked for autoremoval due to python-pylibacl?

2020-03-17 Thread Julien Muchembled
With this bug fixed, fssync has just been marked for autoremoval because it would depend (transitively) on python-pylibacl. I don't understand why. fssync only depends on python3-pylibacl.

Processed: Transition started, raising severity

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #951656 [src:r-cran-lwgeom] r-cran-lwgeom: FTBFS with PROJ 7.0.0 (ERROR: lazy loading failed for package 'lwgeom') Severity set to 'serious' from 'important' -- 951656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951656 Debian Bug Tra

Processed: Transition started, raising severity

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #951655 [src:r-cran-sf] r-cran-sf: FTBFS with PROJ 7.0.0 (configure: error: proj_api.h not found in standard or given locations.) Severity set to 'serious' from 'important' -- 951655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951655

Bug#938622: tahoe-lafs: Python2 removal in sid/bullseye

2020-03-17 Thread Vasudev Kamath
Sorry for the delayed response here. I let the package to fall of from testing as upstream does not yet any support for building python3. Though currently there is some work going on for supporting python3 in upstream, I'm not sure of ETA of the procedure. Will reintroduce the package once upstr

Bug#953942: marked as done (RM: jack -- RoQA; python2-only; no new upstream code since 2005; better alternatives exist; blocking py2removal effort)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:48:51 + with message-id and subject line Bug#953942: Removed package(s) from unstable has caused the Debian Bug report #953942, regarding RM: jack -- RoQA; python2-only; no new upstream code since 2005; better alternatives exist; blocking py2removal effo

Bug#953610: marked as done (RM: spambayes -- RoQA; python2-only; no progress in python3 port upstream; no rdeps; low popcon; blocks other python2 removal activities)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:48:15 + with message-id and subject line Bug#953610: Removed package(s) from unstable has caused the Debian Bug report #953610, regarding RM: spambayes -- RoQA; python2-only; no progress in python3 port upstream; no rdeps; low popcon; blocks other python

Bug#950290: marked as done (bley: Port to use publicsuffix2, missing depends)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:47:52 + with message-id and subject line Bug#953609: Removed package(s) from unstable has caused the Debian Bug report #950290, regarding bley: Port to use publicsuffix2, missing depends to be marked as done. This means that you claim that the problem ha

Bug#953609: marked as done (RM: bley -- RoQA; python2-only; no rdeps; extremely low popcon; no release since 2014; RC-buggy)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:47:42 + with message-id and subject line Bug#953609: Removed package(s) from unstable has caused the Debian Bug report #953609, regarding RM: bley -- RoQA; python2-only; no rdeps; extremely low popcon; no release since 2014; RC-buggy to be marked as done

Bug#936216: marked as done (bley: Python2 removal in sid/bullseye)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:47:52 + with message-id and subject line Bug#953609: Removed package(s) from unstable has caused the Debian Bug report #936216, regarding bley: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#937712: marked as done (Should not be released with bullsye: Python2 removal in sid/bullseye)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:49:25 + with message-id and subject line Bug#952500: Removed package(s) from unstable has caused the Debian Bug report #937712, regarding Should not be released with bullsye: Python2 removal in sid/bullseye to be marked as done. This means that you claim

Bug#938522: marked as done (spambayes: Python2 removal in sid/bullseye)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:48:27 + with message-id and subject line Bug#953610: Removed package(s) from unstable has caused the Debian Bug report #938522, regarding spambayes: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#927100: marked as done (bley: Please port to python3)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:47:52 + with message-id and subject line Bug#953609: Removed package(s) from unstable has caused the Debian Bug report #927100, regarding bley: Please port to python3 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#950081: marked as done (vim-tlib: modifies shipped file: /usr/share/vim/addons/doc/tags)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 02:43:19 + with message-id and subject line Bug#950081: fixed in vim-tlib 1.27-3 has caused the Debian Bug report #950081, regarding vim-tlib: modifies shipped file: /usr/share/vim/addons/doc/tags to be marked as done. This means that you claim that the pro

Bug#954187: marked as done (vault: FTBFS with iam_handle.go:9:2: cannot find package "google.golang.org/api/gensupport")

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 01:19:47 + with message-id and subject line Bug#954187: fixed in vault 1.0.2+dfsg2-4 has caused the Debian Bug report #954187, regarding vault: FTBFS with iam_handle.go:9:2: cannot find package "google.golang.org/api/gensupport" to be marked as done. This

Bug#954190: dh-runit: FTBFS on armhf due to shake testsuite failure

2020-03-17 Thread Lorenzo Puliti
Package: dh-runit Version: 2.8.15 Severity: serious Tags: ftbfs Justification: fails to build from source According to build logs dh-runit FTBFS, but only on armhf. This is because the testsuite exits nonzero. I can reproduce the error in the log [1] inside an armhf chroot (created with debootstra

Bug#952083: marked as done (pry: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@str_output.string).not_to match(/SyntaxError/))

2020-03-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Mar 2020 00:49:17 + with message-id and subject line Bug#952083: fixed in pry 0.12.2-2 has caused the Debian Bug report #952083, regarding pry: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@str_output.string).not_to match(/SyntaxError/) to be mark

Processed: Bug#954187 marked as pending in vault

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #954187 [src:vault] vault: FTBFS with iam_handle.go:9:2: cannot find package "google.golang.org/api/gensupport" Added tag(s) pending. -- 954187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954187 Debian Bug Tracking System Contact ow...@bu

Bug#954187: marked as pending in vault

2020-03-17 Thread Dmitry Smirnov
Control: tag -1 pending Hello, Bug #954187 in vault reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/vault/-/commit/8a6566304a2116a71ca2c7a294d0

Processed: Bug#952083 marked as pending in pry

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #952083 [src:pry] pry: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@str_output.string).not_to match(/SyntaxError/) Added tag(s) pending. -- 952083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952083 Debian Bug Tracking

Bug#952083: marked as pending in pry

2020-03-17 Thread Lucas Kanashiro
Control: tag -1 pending Hello, Bug #952083 in pry reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/pry/-/commit/81f79754a50877b47840f6c4e581854f29521fa

Bug#954114: marked as done (wine-development: build-dependencies unsatisfiable.)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 23:51:30 + with message-id and subject line Bug#954114: fixed in wine-development 5.3-1 has caused the Debian Bug report #954114, regarding wine-development: build-dependencies unsatisfiable. to be marked as done. This means that you claim that the problem

Bug#954189: acmetool: Buster acmetool stops working in June 1, 2020

2020-03-17 Thread Pali Rohár
Package: acmetool Version: 0.0.62-3+b11 Severity: grave Hello! I'm using Debian Buster 10.3 on servers with acmetool for updating Let's encrypt certificates and I got following email from letsencrypt: According to our records, the software client you're using to get Let's Encrypt TLS/SSL

Bug#951934: marked as done (autoradio: FTBFS: ImportError: cannot import name 'permalink' from 'django.db.models' (/usr/lib/python3/dist-packages/django/db/models/__init__.py))

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 23:19:18 + with message-id and subject line Bug#951934: fixed in autoradio 3.4-1 has caused the Debian Bug report #951934, regarding autoradio: FTBFS: ImportError: cannot import name 'permalink' from 'django.db.models' (/usr/lib/python3/dist-packages/django

Bug#954187: vault: FTBFS with iam_handle.go:9:2: cannot find package "google.golang.org/api/gensupport"

2020-03-17 Thread Andreas Beckmann
Source: vault Version: 1.0.2+dfsg2-3 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, vault recently started to FTBFS (IIRC it was building fine shortly after the upload happened). This error may contain a clue: src/github.com/hashicorp/vault/vendor/github.com/hashico

Bug#953540: [Aspectc-developers] Fwd: Bug#953540: aspectc++: FTBFS on armel

2020-03-17 Thread Reinhard Tartler
Control: forwarded -1 aspectc-develop...@aspectc.org Hi Adrian, Olaf, the upstream developer, has a question regarding your patch to aspectc++. Would you mind having a look and ideally sharing your reply to everyone? Thank you! -rt On 3/17/20 11:05 AM, Olaf Spinczyk wrote: > Hi Reinhard! > > D

Processed: Re: [Aspectc-developers] Fwd: Bug#953540: aspectc++: FTBFS on armel

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 aspectc-develop...@aspectc.org Bug #953540 [src:aspectc++] aspectc++: FTBFS on armel Set Bug forwarded-to-address to 'aspectc-develop...@aspectc.org'. -- 953540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953540 Debian Bug Tracking System Contac

Bug#952097: marked as done (spice-gtk: FTBFS: spice-widget-egl.c:29:10: fatal error: libdrm/drm_fourcc.h: No such file or directory)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 22:06:04 + with message-id and subject line Bug#952097: fixed in spice-gtk 0.37-2 has caused the Debian Bug report #952097, regarding spice-gtk: FTBFS: spice-widget-egl.c:29:10: fatal error: libdrm/drm_fourcc.h: No such file or directory to be marked as don

Bug#954180: pillow-python2: has failing autopkgtests for python3

2020-03-17 Thread Ivo De Decker
package: pillow-python2 version: 6.2.1-3 severity: serious Hi, The autopkgtests for pillow-python2 fail with "selftest-py3 FAIL non-zero exit status 1" I suspect the python 3 tests need to be removed (as the rest of the python3 packaging is in src:pillow). Note that pillow-python2 curre

Bug#952309: marked as done (cysignals: FTBFS: help2man: can't get `--help' info from /<>/debian/adhoc/wrappers/cysignals-CSI)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 20:36:26 + with message-id and subject line Bug#952309: fixed in cysignals 1.10.2+ds-4 has caused the Debian Bug report #952309, regarding cysignals: FTBFS: help2man: can't get `--help' info from /<>/debian/adhoc/wrappers/cysignals-CSI to be marked as done.

Processed: Re: Bug#954158: tightvncserver output a blank screen with gray color under gnome

2020-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 954158 + moreinfo Bug #954158 [tightvncserver] tightvncserver output a blank screen with gray color under gnome Added tag(s) moreinfo. > severity 954158 minor Bug #954158 [tightvncserver] tightvncserver output a blank screen with gray color

Bug#954158: tightvncserver output a blank screen with gray color under gnome

2020-03-17 Thread Ola Lundqvist
tags 954158 + moreinfo severity 954158 minor thanks Hi Have you checked your vnc startup script in ~/.vnc/xstartup or alternatively the startup script in ~/.vncstartup This is the set of commands used to start the window manager and other stuff. When reading the manual I can see that this is no

Processed: py2removal bugs severity updates - 2020-03-17 20:28:21.500259+00:00

2020-03-17 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 https://lists.debian.org/debian-devel-an

Bug#954174: login broken for usernames starting with a number (badname)

2020-03-17 Thread Michael Biebl
Package: systemd Version: 245-2 Severity: serious Forwarded: https://github.com/systemd/systemd/issues/15141 Usernames that contain a number (or digit) as first character are rejected by v245: https://github.com/systemd/systemd/blob/v245/src/basic/user-util.c#L710 This will lead to login failures

Bug#950568: marked as done (node-copy-webpack-plugin FTBFS: test failures)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 19:04:26 + with message-id and subject line Bug#950568: fixed in node-copy-webpack-plugin 4.3.0-7 has caused the Debian Bug report #950568, regarding node-copy-webpack-plugin FTBFS: test failures to be marked as done. This means that you claim that the prob

Bug#952375: marked as done (node-jsonld: FTBFS: Module not found: Error: Can't resolve 'rdf-canonize' in '/<>/lib')

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 18:19:32 + with message-id and subject line Bug#952375: fixed in node-jsonld 1.6.2-3 has caused the Debian Bug report #952375, regarding node-jsonld: FTBFS: Module not found: Error: Can't resolve 'rdf-canonize' in '/<>/lib' to be marked as done. This means

Processed: Bug#952375 marked as pending in node-jsonld

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #952375 [src:node-jsonld] node-jsonld: FTBFS: Module not found: Error: Can't resolve 'rdf-canonize' in '/<>/lib' Added tag(s) pending. -- 952375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952375 Debian Bug Tracking System Contact ow...@b

Bug#952375: marked as pending in node-jsonld

2020-03-17 Thread Jonas Smedegaard
Control: tag -1 pending Hello, Bug #952375 in node-jsonld reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jsonld/-/commit/554246f2fa6f907909c53383a

Bug#952374: marked as done (node-rdf-canonize: FTBFS: Module not found: Error: Can't resolve 'babel-runtime/core-js/get-iterator' in '/<>/lib')

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 18:04:35 + with message-id and subject line Bug#952374: fixed in node-rdf-canonize 1.1.0-1 has caused the Debian Bug report #952374, regarding node-rdf-canonize: FTBFS: Module not found: Error: Can't resolve 'babel-runtime/core-js/get-iterator' in '/<>/lib'

Processed: Bug#952374 marked as pending in node-rdf-canonize

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #952374 [src:node-rdf-canonize] node-rdf-canonize: FTBFS: Module not found: Error: Can't resolve 'babel-runtime/core-js/get-iterator' in '/<>/lib' Added tag(s) pending. -- 952374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952374 Debian

Bug#952374: marked as pending in node-rdf-canonize

2020-03-17 Thread Jonas Smedegaard
Control: tag -1 pending Hello, Bug #952374 in node-rdf-canonize reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rdf-canonize/-/commit/45ed73ffd2628

Processed: Re: runit - default installation wants to remove systemd

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 runit - default installation can force init switch Bug #953875 [src:runit] runit - default installation wants to remove systemd Changed Bug title to 'runit - default installation can force init switch' from 'runit - default installation wants to remove sy

Bug#953875: runit - default installation wants to remove systemd

2020-03-17 Thread Lorenzo
Control: retitle -1 runit - default installation can force init switch Control: tag -1 moreinfo Hi, Bastian Blank: > An installation attempt on a default system (with recommends enabled) of > runit wants to replace the installed init: thanks for reporting this, however I can't reproduce. I'm tes

Bug#952152: marked as done (node-immutable-tuple: FTBFS: build-dependency not installable: node-rollup-plugin-buble)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 18:38:42 +0100 with message-id <085fe77d-bcf5-c02c-0a4f-f37497e91...@debian.org> and subject line Fixed by buble* updates has caused the Debian Bug report #952152, regarding node-immutable-tuple: FTBFS: build-dependency not installable: node-rollup-plugin-buble

Bug#925816: marked as done (qxw: ftbfs with GCC-9)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 17:34:08 + with message-id and subject line Bug#925816: fixed in qxw 20140331-1.1 has caused the Debian Bug report #925816, regarding qxw: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread Holger Wansing
Hi, Am Dienstag, 17. März 2020 schrieb Steve McIntyre: > On Tue, Mar 17, 2020 at 12:06:45PM +, Steve McIntyre wrote: > > > >I can see from your log that you're just using ext4 for the new > >system, and you're booting in BIOS mode. Any other disks attached to > >the system? > > > >Testing at t

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

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 16:50:21 + with message-id and subject line Bug#938107: fixed in python-pyxattr 0.6.1-2 has caused the Debian Bug report #938107, regarding python-pyxattr: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

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

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 16:50:13 + with message-id and subject line Bug#938073: fixed in python-pylibacl 0.5.4-2 has caused the Debian Bug report #938073, regarding python-pylibacl: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Processed: reassign 953609 to ftp.debian.org ..., reassign 953610 to ftp.debian.org ..., tagging 952500

2020-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 953609 ftp.debian.org Bug #953609 [bley] bley: should this package be removed? Bug reassigned from package 'bley' to 'ftp.debian.org'. No longer marked as found in versions bley/2.0.0-2. Ignoring request to alter fixed versions of bug #95

Bug#953739: marked as done (aac-tactics: FTBFS in sid)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 16:19:15 + with message-id and subject line Bug#953739: fixed in aac-tactics 8.11.0-1 has caused the Debian Bug report #953739, regarding aac-tactics: FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#952309: cysignals: FTBFS: help2man: can't get `--help' info from /<>/debian/adhoc/wrappers/cysignals-CSI

2020-03-17 Thread Tobias Hansen
The reason for this is that src/scripts/cysignals-CSI calls python which is not installed. The script has to be ported to python3. Best, Tobias On 2/23/20 2:37 PM, Lucas Nussbaum wrote: > Source: cysignals > Version: 1.10.2+ds-3 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullsey

Processed: py2removal bugs severity updates - 2020-03-17 15:35:30.330726+00:00

2020-03-17 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 https://lists.debian.org/debian-devel-an

Bug#951975: marked as done (fava: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 16:29:48 +0100 with message-id and subject line This bug is fixed has caused the Debian Bug report #951975, regarding fava: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13 to be marked as done. This means that y

Bug#954158: tightvncserver output a blank screen with gray color under gnome

2020-03-17 Thread gulfstream
Package: tightvncserver Version: 1:1.3.9-9.1 Severity: grave Hello, I want to use tightvnc under the gnome desktop, but only a blank screen was got in the client. Nothing is on the screen except a cursor. What is the matter? Would you please resolve it? Thank you very much! Best regards, Gu

Bug#954095: marked as done (gimp: fatal error: Segmentation fault on startup)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 15:20:46 + with message-id and subject line Bug#953880: fixed in gimp 2.10.14-3 has caused the Debian Bug report #953880, regarding gimp: fatal error: Segmentation fault on startup to be marked as done. This means that you claim that the problem has been de

Bug#953880: marked as done (gimp: fatal error: Segmentation fault on startup)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 15:20:46 + with message-id and subject line Bug#953880: fixed in gimp 2.10.14-3 has caused the Debian Bug report #953880, regarding gimp: fatal error: Segmentation fault on startup to be marked as done. This means that you claim that the problem has been de

Bug#942618: marked as done (vilistextum: Maintainer email address not working)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 15:21:57 + with message-id and subject line Bug#942618: fixed in vilistextum 2.6.9-1.2 has caused the Debian Bug report #942618, regarding vilistextum: Maintainer email address not working to be marked as done. This means that you claim that the problem has

Bug#950147: sagemath ftbfs with python 3.8

2020-03-17 Thread Tobias Hansen
Control: block -1 by 953633 We have a patch for this but I'm waiting for a fix of a bug in pari that causes test failures and a test timeout. Best, Tobias On Wed, 29 Jan 2020 17:46:47 +0100 Tobias Hansen wrote: > It does if applied first. But ok, the ipython 7 patch needed some small > change

Processed: Re: Bug#950147: sagemath ftbfs with python 3.8

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 953633 Bug #950147 [src:sagemath] sagemath ftbfs with python 3.8 950147 was not blocked by any bugs. 950147 was not blocking any bugs. Added blocking bug(s) of 950147: 953633 -- 950147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950147 Debian Bug

Bug#950154: marked as done (apertium-eo-ca FTBFS with apertium 3.6.1)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 15:04:10 + with message-id and subject line Bug#950154: fixed in apertium-eo-ca 1:0.9.1~r60655-4 has caused the Debian Bug report #950154, regarding apertium-eo-ca FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem ha

Bug#954033: marked as done (pdfarranger: The package should depend on python3-gi-cairo. Otherwise the application will not render pages.)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 14:49:39 + with message-id and subject line Bug#954033: fixed in pdfarranger 1.4.2-1 has caused the Debian Bug report #954033, regarding pdfarranger: The package should depend on python3-gi-cairo. Otherwise the application will not render pages. to be marke

Bug#953880: marked as pending in gimp

2020-03-17 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #953880 in gimp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gimp/-/commit/26eed4e96e753f0b12f37d54df1351225b59

Processed: Bug#953880 marked as pending in gimp

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #953880 [gimp] gimp: fatal error: Segmentation fault on startup Bug #954095 [gimp] gimp: fatal error: Segmentation fault on startup Added tag(s) pending. Added tag(s) pending. -- 953880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953880 95

Bug#954147: src:dateparser: Requires a package outside of Main

2020-03-17 Thread Antoine Beaupré
On 2020-03-17 09:14:03, Scott Kitterman wrote: > Package: src:dateparser > Version: 0.7.2-1 > Severity: serious > Justification: Policy 2.2.1 > > This package uses python pip to download and install packages from outside the > Debian archive to run autopkgtests. Main is required to be self-contain

Processed: tagging 954079, notfound 954100 in 3.0.4, found 954100 in 3.0.4-1, found 954134 in 20200314

2020-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 954079 + sid bullseye Bug #954079 [magic-wormhole] magic-wormhole: Fails to send with a type error Added tag(s) bullseye and sid. > notfound 954100 3.0.4 Bug #954100 [src:gdcm] Error: A deprecated csdestruct_derived typemap was found for vtk

Processed: Bug#954033 marked as pending in pdfarranger

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #954033 [pdfarranger] pdfarranger: The package should depend on python3-gi-cairo. Otherwise the application will not render pages. Added tag(s) pending. -- 954033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954033 Debian Bug Tracking Syst

Bug#954033: marked as pending in pdfarranger

2020-03-17 Thread Tobias Quathamer
Control: tag -1 pending Hello, Bug #954033 in pdfarranger reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/applications/pdfarranger/-/commit/5930995b

Bug#954154: src:salt: Requires a package outside of Main

2020-03-17 Thread Scott Kitterman
Package: src:salt Version: 3000+dfsg1-3 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ [1]

Bug#954033: Fixed in new upload

2020-03-17 Thread Dr. Tobias Quathamer
Hi Jacob, thanks for filing this bug, it slipped through my testing. A new package is on its way to unstable. Regards, Tobias signature.asc Description: OpenPGP digital signature

Bug#932659: node: modules are not getting detected in a fresh sid chroot environment

2020-03-17 Thread Josh de Kock
Hi, This still occurs for me. I have a armhf chroot of Sid. It seems to be using a node path relative to the current directory (as far as I can tell). These paths should probably be /usr prefixed (and not relative to cwd), but I wouldn't know where to begin fixing this. See my tests below: roo

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread Steve McIntyre
On Tue, Mar 17, 2020 at 12:06:45PM +, Steve McIntyre wrote: > >I can see from your log that you're just using ext4 for the new >system, and you're booting in BIOS mode. Any other disks attached to >the system? > >Testing at the weekend didn't show any problems for me or Andy. I'm >doing an expl

Bug#954153: src:python-virtualenv: Please drop python-virtualenv tests

2020-03-17 Thread Scott Kitterman
Package: src:python-virtualenv Version: 15.1.0+ds-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) This is really an autopkgtest failure bug, but I think ftbfs is the closest tag we have. Please drop the autopkgtests for python-virtual

Bug#954151: src:logbook: Requires a package outside of Main

2020-03-17 Thread Scott Kitterman
Package: src:logbook Version: 1.5.3-2 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ [1] i

Bug#954150: src:ffc: Requires a package outside of Main

2020-03-17 Thread Scott Kitterman
Package: src:ffc Version: 2019.1.0.post0-2 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ

Bug#954148: src:doit: Requires a package outside of Main

2020-03-17 Thread Scott Kitterman
Package: src:doit Version: 0.31.1-3.2 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ [1] i

Bug#954147: src:dateparser: Requires a package outside of Main

2020-03-17 Thread Scott Kitterman
Package: src:dateparser Version: 0.7.2-1 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ [1

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread Holger Wansing
Hi, Am Dienstag, 17. März 2020 schrieb Steve McIntyre: > >Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown > >filesystem. > > I can see from your log that you're just using ext4 for the new > system, and you're booting in BIOS mode. Any other disks attached to > the sys

Bug#953832: cannot allocate memory in static TLS block

2020-03-17 Thread Andreas Tille
Hi Faidon, On Tue, Mar 17, 2020 at 01:29:59PM +0200, Faidon Liambotis wrote: > Hi Andreas, > > Thanks for reaching out. It sounds like this is already reported as > #951704 (Cc'ed now). OK. > I'll need to give this a closer look, but I hope I > can have an update within the next couple of weeks

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread Steve McIntyre
Hi Holger, On Tue, Mar 17, 2020 at 11:13:27AM +0100, Holger Wansing wrote: > >Holger Wansing wrote: >> > >> > I will sent installation logs shortly. >> >> Logs attached. > >The relevant part seems to be: ... >Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size >Mar 16

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread John Paul Adrian Glaubitz
On 3/17/20 12:49 PM, Holger Wansing wrote: > However: > >> Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown >> filesystem. > [...] >> Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size >> Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted >

Bug#953832: cannot allocate memory in static TLS block

2020-03-17 Thread Faidon Liambotis
Hi Andreas, Thanks for reaching out. It sounds like this is already reported as #951704 (Cc'ed now). I'll need to give this a closer look, but I hope I can have an update within the next couple of weeks. Does this work? Thanks! Faidon On Sun, Mar 15, 2020 at 10:33:20AM +0100, Andreas Tille wrote

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread Holger Wansing
Hi, Am Dienstag, 17. März 2020 schrieb John Paul Adrian Glaubitz: > On 3/17/20 11:05 AM, Holger Wansing wrote: > > Logs attached. > > grub-installer did not report any problems: > > Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda' > Mar 16 09:55:41 grub-installer: info: grub-i

Bug#951778: marked as done (libva2: NULL vtable when querying nvidia render device)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 11:19:21 + with message-id and subject line Bug#951778: fixed in libva 2.7.0~pre1-1 has caused the Debian Bug report #951778, regarding libva2: NULL vtable when querying nvidia render device to be marked as done. This means that you claim that the problem h

Processed: Re: gimp: segmentation fault on startup

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 953880 954095 Bug #953880 [gimp] gimp: segmentation fault on startup Bug #954095 [gimp] [gimp] GIMP fails to boot, with a segmentation fault Merged 953880 954095 > retitle -1 gimp: fatal error: Segmentation fault on startup Bug #953880 [gimp] gimp: segment

Bug#953880: gimp: segmentation fault on startup

2020-03-17 Thread Thorsten Glaser
Package: gimp Version: 2.10.14-2+b1 Followup-For: Bug #953880 Control: forcemerge 953880 954095 Control: retitle -1 gimp: fatal error: Segmentation fault on startup (gimp:19053): GLib-GObject-CRITICAL **: 12:14:27.292: g_param_spec_internal: assertion 'is_valid_property_name (name)' failed gimp:

Processed: Re: Bug#953540: aspectc++: FTBFS on armel

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #953540 [src:aspectc++] aspectc++: FTBFS on armel Added tag(s) patch. -- 953540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#953540: aspectc++: FTBFS on armel

2020-03-17 Thread Adrian Bunk
Control: tags -1 patch On Tue, Mar 10, 2020 at 11:12:16AM +, Ivo De Decker wrote: > package: src:aspectc++ > version: 1:2.2+git20200229-1 > severity: serious > tags: ftbfs > > Hi, > > The latest upload of aspectc++ to unstable fails on armel: > > https://buildd.debian.org/status/package.php

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread John Paul Adrian Glaubitz
On 3/17/20 11:05 AM, Holger Wansing wrote: > Logs attached. grub-installer did not report any problems: Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda' Mar 16 09:55:41 grub-installer: info: grub-install does not support --no-floppy Mar 16 09:55:41 grub-installer: info: Running

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread Holger Wansing
Hi, Holger Wansing wrote: > > > > I will sent installation logs shortly. > > Logs attached. The relevant part seems to be: Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda' Mar 16 09:55:41 grub-installer: info: grub-install does not support --no-floppy Mar 16 09:55:41 grub-

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread Holger Wansing
Holger Wansing wrote: > > I will sent installation logs shortly. Logs attached. -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 installer.tar.gz Description: application/gzip

Processed: Re: Bug#954129: gucharmap: build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed

2020-03-17 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + fixed-upstream Bug #954129 [src:gucharmap] gucharmap: build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed Added tag(s) fixed-upstream. -- 954129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954129 Debian Bug Tracking System Conta

Bug#954129: gucharmap: build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed

2020-03-17 Thread Simon McVittie
Control: tags -1 + fixed-upstream On Tue, 17 Mar 2020 at 11:48:16 +0200, Adrian Bunk wrote: > The following packages have unmet dependencies: > builddeps:gucharmap : Depends: unicode-data (< 12.2) but 13.0.0-2 is to be > installed gucharmap needs to be upgraded in lockstep with unicode-data. Th

Bug#954133: python-acme build depends on python3-idna (< 2.8) but 2.8-1 is to be installed

2020-03-17 Thread Adrian Bunk
Source: python-acme Version: 1.1.0-1 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:python-acme : Depends: python3-idna (< 2.8) but 2.8-1 is to be installed

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-17 Thread Holger Wansing
Package: debian-installer Severity: grave While testing the alpha2 netinst image on a spare Thinkpad, I found that grub cannot be installed successfully (and rebooting into the new installation fails as well). This was ok in alpha1. This might look like an grub-installer issue, however there wer

Bug#954132: wine build depends on unicode-data (< 13) but 13.0.0-2 is to be installed

2020-03-17 Thread Adrian Bunk
Source: wine Version: 5.0-3 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:wine : Depends: unicode-data (< 13) but 13.0.0-2 is to be installed

Bug#953958: Bug#953562: libcrypt1 should ship file in /usr, breaks is useless

2020-03-17 Thread Markus Steinko
On Tue, 17 Mar 2020 10:26:17 +0100 Markus Steinko wrote: > Dear maintainer, > > downgrading a system from bullseye to buster (via apt-pinning) was kind > of impossible (due to removal of libcrypt.so.1 and unresolved > dependencies of libc-bin and libc6, I think)  when I was facing the bug > for t

Processed: tagging 954114

2020-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 954114 + ftbfs Bug #954114 [src:wine-development] wine-development: build-dependencies unsatisfiable. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 954114: https://bugs.debian.org/cgi-b

Bug#954130: libxmlada build depends on unicode-data (< 13~) but 13.0.0-2 is to be installed

2020-03-17 Thread Adrian Bunk
Source: libxmlada Version: 19-2 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:libxmlada : Depends: unicode-data (< 13~) but 13.0.0-2 is to be installed

Bug#954131: utf8proc build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed

2020-03-17 Thread Adrian Bunk
Source: utf8proc Version: 2.4.0-2 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:utf8proc : Depends: unicode-data (< 12.2) but 13.0.0-2 is to be installed

Bug#954129: gucharmap: build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed

2020-03-17 Thread Adrian Bunk
Source: gucharmap Version: 1:12.0.1-2 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:gucharmap : Depends: unicode-data (< 12.2) but 13.0.0-2 is to be installed

Bug#953958: Bug#953562: libcrypt1 should ship file in /usr, breaks is useless

2020-03-17 Thread Markus Steinko
Dear maintainer, downgrading a system from bullseye to buster (via apt-pinning) was kind of impossible (due to removal of libcrypt1.so and unresolved dependencies of libc-bin and libc6, I think)  when I was facing the bug for the first time and I not being logged in as root within an active t

  1   2   >