Bug#1000986: Montage-wrapper does not play well with astropy 5.0

2021-12-01 Thread Ole Streicher
Package: python3-montage-wrapper Version: 0.9.9-4 Severity: serious The package fails in CI test with astropy 5.0. Since it is abandoned upstream, I do not intend to fix this, but will remove the package (unless someone else is going to take it over). The "montage" package now comes with its

Bug#1000753: marked as done (poliastro FTBFS: plugin flit failed with: Use [project] table for metadata or [tool.flit.metadata], not both)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Thu, 02 Dec 2021 07:18:39 + with message-id and subject line Bug#1000753: fixed in poliastro 0.15.2-4 has caused the Debian Bug report #1000753, regarding poliastro FTBFS: plugin flit failed with: Use [project] table for metadata or [tool.flit.metadata], not both to be

Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

2021-12-01 Thread Andreas Tille
Hi Robert, Am Wed, Dec 01, 2021 at 10:59:45PM -0800 schrieb Robert J. Hijmans: > On Tue, Nov 30, 2021 at 10:46 PM Andreas Tille wrote: > > > > raster 3-5.2 depends on terra; but it does not specify which version of > > > terra. I believe it needs to be terra 1.4-11 to not get this error. > > >

Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

2021-12-01 Thread Robert J. Hijmans
On Tue, Nov 30, 2021 at 10:46 PM Andreas Tille wrote: > Dear Robert, > > Am Tue, Nov 30, 2021 at 09:18:18PM -0800 schrieb Robert J. Hijmans: > > Dear Andreas, > > > > raster 3-5.2 depends on terra; but it does not specify which version of > > terra. I believe it needs to be terra 1.4-11 to not

Bug#995353: marked as done (ruby-protocol-http: autopkgtest regression on armhf and i386 (both 32 bits))

2021-12-01 Thread Debian Bug Tracking System
Your message dated Thu, 02 Dec 2021 07:58:28 +0100 with message-id <91d16169b8e7a83f8c38996328a24ee4bf52867f.ca...@debian.org> and subject line Fixed has caused the Debian Bug report #995353, regarding ruby-protocol-http: autopkgtest regression on armhf and i386 (both 32 bits) to be marked as

Bug#1000983: ocaml-mm FTBFS on !am64/arm64/riscv64

2021-12-01 Thread Stéphane Glondu
Le 02/12/2021 à 07:45, Adrian Bunk a écrit : > Source: ocaml-mm > Version: 0.7.2-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=ocaml-mm=0.7.2-1 > > ... > Supported external libraries: > - Alsa : true > - AO: true > - Mad : true >

Bug#1000983: ocaml-mm FTBFS on !am64/arm64/riscv64

2021-12-01 Thread Adrian Bunk
Source: ocaml-mm Version: 0.7.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=ocaml-mm=0.7.2-1 ... Supported external libraries: - Alsa : true - AO: true - Mad : true - OSS : false - Pulseaudio: true - SDL : true -

Processed: closing 1000359

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1000359 Bug #1000359 [src:python-biopython] FTBFS: test failure: External MBEDTLS version mismatch Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1000359:

Bug#1000812: pyrle: import fails on Python 3.10

2021-12-01 Thread Nilesh Patra
On Mon, 29 Nov 2021 20:35:40 +0100 Andreas Tille wrote: > Am Mon, Nov 29, 2021 at 11:36:33PM +0530 schrieb Nilesh Patra: > > I rebuilt with python3.10, and now error is this. > > Something wrong with pandas? > > As far as I understood we need to wait for pandas 1.3 to work > with Python3.10. I

Bug#999773: marked as done (ksh93u+m: missing Breaks+Replaces: ksh (<< 20210511))

2021-12-01 Thread Debian Bug Tracking System
Your message dated Thu, 2 Dec 2021 10:30:00 +0530 with message-id and subject line Experimental package has been removed has caused the Debian Bug report #999773, regarding ksh93u+m: missing Breaks+Replaces: ksh (<< 20210511) to be marked as done. This means that you claim that the problem has

Processed: fixed 984403 in 4.2.3-2

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 984403 4.2.3-2 Bug #984403 {Done: Stephen Kitt } [src:warzone2100] warzone2100: ftbfs with GCC-11 Marked as fixed in versions warzone2100/4.2.3-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 984403:

Processed: tagging 996052 ...

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 996052 + patch Bug #996052 [gnome-shell-extension-disconnect-wifi] gnome-shell-extension-disconnect-wifi: does not declare compatibility with GNOME Shell 41 Added tag(s) patch. > forwarded 996052

Processed: tagging 996052

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 996052 + fixed-upstream Bug #996052 [gnome-shell-extension-disconnect-wifi] gnome-shell-extension-disconnect-wifi: does not declare compatibility with GNOME Shell 41 Ignoring request to alter tags of bug #996052 to the same tags previously

Bug#999507: marked as done (rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed.)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:21:01 + with message-id and subject line Bug#999736: Removed package(s) from unstable has caused the Debian Bug report #999507, regarding rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed. to be

Bug#974606: marked as done (rust-tokio-process: unsatisfiable build-dependency)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:20:39 + with message-id and subject line Bug#999735: Removed package(s) from unstable has caused the Debian Bug report #974606, regarding rust-tokio-process: unsatisfiable build-dependency to be marked as done. This means that you claim that the problem

Bug#936535: marked as done (flup: Python2 removal in sid/bullseye)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:20:15 + with message-id and subject line Bug#999688: Removed package(s) from unstable has caused the Debian Bug report #936535, regarding flup: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#966797: marked as done (tumgreyspf: Unversioned Python removal in sid/bullseye)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:19:51 + with message-id and subject line Bug#999644: Removed package(s) from unstable has caused the Debian Bug report #927137, regarding tumgreyspf: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#938724: marked as done (tumgreyspf: Python2 removal in sid/bullseye)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:19:51 + with message-id and subject line Bug#999644: Removed package(s) from unstable has caused the Debian Bug report #927137, regarding tumgreyspf: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#927137: marked as done (src:tumgreyspf: Please port to python3 or remove)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:19:51 + with message-id and subject line Bug#999644: Removed package(s) from unstable has caused the Debian Bug report #927137, regarding src:tumgreyspf: Please port to python3 or remove to be marked as done. This means that you claim that the problem

Bug#997570: marked as done (golang-github-marten-seemann-qtls-go1-15: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/marten-seemann/qtls-go1-15 returned exit code 1)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:17:14 + with message-id and subject line Bug#999403: Removed package(s) from unstable has caused the Debian Bug report #996756, regarding golang-github-marten-seemann-qtls-go1-15: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4

Bug#996756: marked as done (golang-github-marten-seemann-qtls-go1-15: FTBFS with golang/1.17: panic: qtls.ClientHelloInfo doesn't match)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:17:14 + with message-id and subject line Bug#999403: Removed package(s) from unstable has caused the Debian Bug report #996756, regarding golang-github-marten-seemann-qtls-go1-15: FTBFS with golang/1.17: panic: qtls.ClientHelloInfo doesn't match to be

Bug#997626: marked as done (django-restricted-resource: FTBFS: TypeError: Abstract models cannot be instantiated.)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:16:07 + with message-id and subject line Bug#998900: Removed package(s) from unstable has caused the Debian Bug report #995465, regarding django-restricted-resource: FTBFS: TypeError: Abstract models cannot be instantiated. to be marked as done. This

Bug#995465: marked as done (django-restricted-resource: autopkgtest fails for python-django >= 3)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:16:07 + with message-id and subject line Bug#998900: Removed package(s) from unstable has caused the Debian Bug report #995465, regarding django-restricted-resource: autopkgtest fails for python-django >= 3 to be marked as done. This means that you

Bug#998723: marked as done (node-whatwg-fetch conflicts libjs-fetch)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:08:11 + with message-id and subject line Bug#998724: Removed package(s) from unstable has caused the Debian Bug report #998723, regarding node-whatwg-fetch conflicts libjs-fetch to be marked as done. This means that you claim that the problem has been

Bug#970186: marked as done (rust-rand-core-0.3: Unaligned memory access resulting in undefined behavior)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:08:46 + with message-id and subject line Bug#998735: Removed package(s) from unstable has caused the Debian Bug report #970186, regarding rust-rand-core-0.3: Unaligned memory access resulting in undefined behavior to be marked as done. This means that

Bug#915069: marked as done (libphp-predis: Useless in Debian, superseded by php-nrk-predis)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:06:47 + with message-id and subject line Bug#998717: Removed package(s) from unstable has caused the Debian Bug report #915069, regarding libphp-predis: Useless in Debian, superseded by php-nrk-predis to be marked as done. This means that you claim that

Bug#875184: marked as done ([sofa-framework] Future Qt4 removal from Buster)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:04:18 + with message-id and subject line Bug#998639: Removed package(s) from unstable has caused the Debian Bug report #875184, regarding [sofa-framework] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem

Bug#997290: marked as done (xfce4-sntray-plugin: FTBFS: client.vala:68.13-68.21: error: syntax error, no expression allowed between array brackets)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:03:57 + with message-id and subject line Bug#997290: fixed in xfce4-sntray-plugin 0.4.13.1-2 has caused the Debian Bug report #997290, regarding xfce4-sntray-plugin: FTBFS: client.vala:68.13-68.21: error: syntax error, no expression allowed between

Bug#991000: marked as done (bareos-database-common: fails to upgrade from buster: ERROR: invalid value for parameter "client_min_messages": "fatal")

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #991000, regarding bareos-database-common: fails to upgrade from buster: ERROR: invalid value for parameter "client_min_messages":

Bug#995837: marked as done (Should bareos be removed?)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #995837, regarding Should bareos be removed? to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#977708: marked as done (on purge not all files are removed)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #977708, regarding on purge not all files are removed to be marked as done. This means that you claim that the problem has been dealt

Bug#977707: marked as done (Install fails with mysql error 1005)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #977707, regarding Install fails with mysql error 1005 to be marked as done. This means that you claim that the problem has been

Bug#968957: marked as done (bareos: CVE-2020-11061)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #968957, regarding bareos: CVE-2020-11061 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#965985: marked as done (bareos: CVE-2020-4042)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #965985, regarding bareos: CVE-2020-4042 to be marked as done. This means that you claim that the problem has been dealt with. If

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

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:00:38 + with message-id and subject line Bug#1000902: Removed package(s) from unstable has caused the Debian Bug report #937927, regarding python-mode: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#937398: marked as done (pycalendar: Python2 removal in sid/bullseye)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:07 + with message-id and subject line Bug#1000904: Removed package(s) from unstable has caused the Debian Bug report #937398, regarding pycalendar: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#936185: marked as done (bareos: Python2 removal in sid/bullseye)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #936185, regarding bareos: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#922344: marked as done (bareos: autopkgtest regression)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #922344, regarding bareos: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt

Bug#884234: marked as done (bareos: Stable update fails to configure (no database version defined, FAILED to set Catalog MyCatalog dbdriver = postgresql))

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 23:01:50 + with message-id and subject line Bug#1000906: Removed package(s) from unstable has caused the Debian Bug report #884234, regarding bareos: Stable update fails to configure (no database version defined, FAILED to set Catalog MyCatalog dbdriver =

Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure

2021-12-01 Thread Thorsten Glaser
Michael Meskes dixit: >Hmm, not sure what I'm doing wrong. Using the same entries in my calendar file >I get: > >michael@feivel:~$ calendar Right, but do enable the cronjob. “calendar -a” runs as root. Or try sudo calendar -a which is basically the same then watch your mail. (You’ll also need

Bug#1000753: poliastro FTBFS: plugin flit failed with: Use [project] table for metadata or [tool.flit.metadata], not both

2021-12-01 Thread Scott Kitterman
On Wed, 01 Dec 2021 14:07:52 -0500 Scott Kitterman wrote: > On Sun, 28 Nov 2021 14:17:14 + "Rebecca N. Palmer" > wrote: > > Package: python3-poliastro > > Version: 0.15.2-3 > > Severity: serious > > > > Fails to build with the error > > > > E: pybuild pybuild:354: build: plugin flit

Bug#997290: marked as pending in xfce4-sntray-plugin

2021-12-01 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #997290 in xfce4-sntray-plugin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#997290 marked as pending in xfce4-sntray-plugin

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #997290 [src:xfce4-sntray-plugin] xfce4-sntray-plugin: FTBFS: client.vala:68.13-68.21: error: syntax error, no expression allowed between array brackets Added tag(s) pending. -- 997290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997290

Processed: minimac4 autopkgtest regression confirmed

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1000475 confirmed Bug #1000475 [src:minimac4] minimac4: autopkgtest regression: *** stack smashing detected ***: terminated Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000475:

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-12-01 Thread Joachim Reichel
Hi Ian, On 28.11.21 19:21, Ian Jackson wrote: Joachim Reichel (cppcheck maintainer): I'll upload a new version cppcheck with a workaround shortly Would you mind both prioritising this fix ? FTAOD it's not just cppcheck that is scheduled for autoremoval. Any package which transitively

Processed: Merge duplicates

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 997368 gnunet Bug #997368 [src:gnunet-fuse] FTBFS in sid Bug reassigned from package 'src:gnunet-fuse' to 'gnunet'. No longer marked as found in versions gnunet-fuse/0.13.0-2. Ignoring request to alter fixed versions of bug #997368 to

Processed: update bts with right meta info

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1000552 src:python-agate-excel 0.2.3-1 Bug #1000552 {Done: Håvard Flaget Aasen } [src:openpyxl, src:python-agate-excel] openpyxl breaks python-agate-excel autopkgtest Bug reassigned from package 'src:openpyxl, src:python-agate-excel'

Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure

2021-12-01 Thread Michael Meskes
[Sorry, I have missed this bug report, didn't make it into the correct mailbox locally it seems.] On Mon, Nov 01, 2021 at 12:02:48AM +, Thorsten Glaser wrote: > #define·ssh·Nov·01→ ssh > #include·"/root/.ssh/authorized_keys" Hmm, not sure what I'm doing wrong. Using the same entries in

Processed: Re: minimac4: autopkgtest regression: *** stack smashing detected ***: terminated

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - moreinfo Bug #1000475 [src:minimac4] minimac4: autopkgtest regression: *** stack smashing detected ***: terminated Removed tag(s) moreinfo. -- 1000475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000475 Debian Bug Tracking System Contact

Bug#1000972: ruby-jaeger-client: Depends on ruby-thrift:amd64 which isn't available on other architectures

2021-12-01 Thread Paul Gevers
Package: ruby-jaeger-client Version: 1.2.0-1 Severity: serious Justification: uninstallable ruby-jaeger-client is on my radar because it doesn't migrate for a long time. I was very puzzled by the output of britney: > ruby-jaeger-client/amd64 has unsatisfiable dependency > ruby-jaeger-client/arm64

Processed: Re: minimac4: autopkgtest regression: *** stack smashing detected ***: terminated

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #1000475 [src:minimac4] minimac4: autopkgtest regression: *** stack smashing detected ***: terminated Added tag(s) moreinfo. -- 1000475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000475 Debian Bug Tracking System Contact

Processed: Re: Bug#1000919: ldc: Please upgrade to llvm-toolchain-12 or 13

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1000919 [src:ldc] ldc: Please upgrade to llvm-toolchain-12 or 13 Severity set to 'serious' from 'important' > retitle -1 ldc: FTBFS with llvm-toolchain-13 Bug #1000919 [src:ldc] ldc: Please upgrade to llvm-toolchain-12 or 13 Changed Bug

Processed: Re: Bug#1000930: faust: Please upgrade to llvm-toolchain-12 or 13

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > found -1 2.33.1~ds0-1 Bug #1000930 [src:faust] faust: Please upgrade to llvm-toolchain-12 or 13 Marked as found in versions faust/2.33.1~ds0-1. > severity -1 serious Bug #1000930 [src:faust] faust: Please upgrade to llvm-toolchain-12 or 13 Severity set to 'serious'

Processed: Re: Bug#1000923: ghdl: Please upgrade to llvm-toolchain-12 or 13

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1000923 [src:ghdl] ghdl: Please upgrade to llvm-toolchain-12 or 13 Severity set to 'serious' from 'important' > retitle -1 ghdl: FTBFS with llvm-toolchain-13 Bug #1000923 [src:ghdl] ghdl: Please upgrade to llvm-toolchain-12 or 13 Changed Bug

Bug#1000753: poliastro FTBFS: plugin flit failed with: Use [project] table for metadata or [tool.flit.metadata], not both

2021-12-01 Thread Scott Kitterman
On Sun, 28 Nov 2021 14:17:14 + "Rebecca N. Palmer" wrote: > Package: python3-poliastro > Version: 0.15.2-3 > Severity: serious > > Fails to build with the error > > E: pybuild pybuild:354: build: plugin flit failed with: Use [project] > table for metadata or [tool.flit.metadata], not

Processed: tagging 996380

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 996380 + help Bug #996380 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 996297

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 996297 + help Bug #996297 [src:ruby-ice-nine] ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.end).to be_frozen Added tag(s) help. > thanks Stopping processing here. Please contact me if

Bug#998317: marked as done (PostgreSQL 14 transition)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 18:49:53 + with message-id and subject line Bug#998317: fixed in gavodachs 2.5+dfsg-1 has caused the Debian Bug report #998317, regarding PostgreSQL 14 transition to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1000958: /etc/aliases dosn't work since bullseye

2021-12-01 Thread Jörg Frings-Fürst
Hi Marc, Am Mittwoch, dem 01.12.2021 um 18:48 +0100 schrieb Marc Haber: > On Wed, Dec 01, 2021 at 05:44:32PM +0100, Jörg Frings-Fürst wrote: > > Here are the update-exim4.conf.conf: > > > > dc_eximconfig_configtype='satellite' > > That is the Debconf option "mail sent by smarthost; no local

Processed: Bug#996380 marked as pending in ruby-safe-yaml

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996380 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996380 Debian Bug Tracking System Contact

Bug#996380: marked as pending in ruby-safe-yaml

2021-12-01 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996380 in ruby-safe-yaml 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#1000958: /etc/aliases dosn't work since bullseye

2021-12-01 Thread Marc Haber
On Wed, Dec 01, 2021 at 05:44:32PM +0100, Jörg Frings-Fürst wrote: > Here are the update-exim4.conf.conf: > > dc_eximconfig_configtype='satellite' That is the Debconf option "mail sent by smarthost; no local mail". The behavior actually means "no local mail". Was that actually your intention? >

Bug#997357: marked as done (ruby-fakefs: FTBFS: ERROR: Test "ruby2.7" failed.)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 17:33:58 + with message-id and subject line Bug#997357: fixed in ruby-fakefs 1.2.0-2 has caused the Debian Bug report #997357, regarding ruby-fakefs: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you claim that the problem has

Processed: closing 997322

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 997322 Bug #997322 [src:ycmd] ycmd: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/usr/share/unicode/emoji/emoji-data.txt' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1000958: /etc/aliases dosn't work since bullseye

2021-12-01 Thread Jörg Frings-Fürst
Hello Marc, Am Mittwoch, dem 01.12.2021 um 15:58 +0100 schrieb Marc Haber: > On Wed, Dec 01, 2021 at 02:25:13PM +0100, Jörg Frings-Fürst wrote: > > here are my config and the logs: > > > > /etc/aliases: > > > > > > # /etc/aliases > > mailer-daemon: postmaster > > postmaster: root > > nobody:

Bug#978893: marked as done (ripperx: ftbfs with autoconf 2.70)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 16:04:47 + with message-id and subject line Bug#978893: fixed in ripperx 2.8.0-2.1 has caused the Debian Bug report #978893, regarding ripperx: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#994785: marked as done (python-ase: autopkgtest regression on arm64/ppc64el: TestSlab.test_vibration_on_surface)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 15:22:56 + with message-id and subject line Bug#994785: fixed in python-ase 3.22.1-1 has caused the Debian Bug report #994785, regarding python-ase: autopkgtest regression on arm64/ppc64el: TestSlab.test_vibration_on_surface to be marked as done. This

Bug#999626: [Maxima-discuss] maxima-emacs: fails to install with xemacs21

2021-12-01 Thread Camm Maguire
Greetings! Am uploading a fix for now. cl-lib for xemacs21 can be found in the mmm-mode package. Other change is that image-map needs to be nil if not bound. Quite a few byte-compilation warnings in both flavors, suppressed on install, but maintainers might want to look at cleaning these up.

Bug#1000467: marked as done (rpm, autopkgtest failure on armhf)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 15:05:54 + with message-id and subject line Bug#1000467: fixed in rpm 4.17.0+dfsg1-4 has caused the Debian Bug report #1000467, regarding rpm, autopkgtest failure on armhf to be marked as done. This means that you claim that the problem has been dealt

Bug#1000960: Wrong permissions after fresh install

2021-12-01 Thread Marc Haber
On Wed, Dec 01, 2021 at 01:36:52PM +, Jörg Frings-Fürst wrote: > /etc/exim4/passwd.client > 2021-12-01 09:37:02 1msM2w-kF-2M failed to expand "<; ${if > exists{/etc/exim4/passwd.client} > {${lookup{$host}nwildlsearch{/etc/exim4/passwd.client}{$host_address}}}{} }" > while checking a

Bug#1000958: /etc/aliases dosn't work since bullseye

2021-12-01 Thread Marc Haber
On Wed, Dec 01, 2021 at 02:25:13PM +0100, Jörg Frings-Fürst wrote: > here are my config and the logs: > > /etc/aliases: > > > # /etc/aliases > mailer-daemon: postmaster > postmaster: root > nobody: root > hostmaster: root > usenet: root > news: root > webmaster: root > www: root > ftp: root >

Processed: reassign 939419 to src:samba, fixed 939419 in 2:4.11.0+dfsg-1, fixed 939419 in 2:4.9.5+dfsg-5+deb10u2 ...

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 939419 src:samba 2:4.9.5+dfsg-5 Bug #939419 {Done: Salvatore Bonaccorso } [libparse-pidl-perl] libparse-pidl-perl: version ordering issue. Bug reassigned from package 'libparse-pidl-perl' to 'src:samba'. No longer marked as found in

Processed: reassign 1000735 to src:linux, tagging 974779, found 1000798 in 2.3.2+r586-7 ..., tagging 977403 ...

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1000735 src:linux Bug #1000735 [iwlwifi] iwlwifi: start the wifi, it makes a kernel opps Warning: Unknown package 'iwlwifi' Bug reassigned from package 'iwlwifi' to 'src:linux'. No longer marked as found in versions firmware-iwlwifi.

Bug#1000960: Wrong permissions after fresh install

2021-12-01 Thread Jörg Frings-Fürst
Package: exim4-daemon-light Version: 4.94.2-7 Severity: grave File: /usr/sbin/exim4 Hello, on a fresh install exim4 files has wrong permissions: /etc/exim4/passwd.client 2021-12-01 09:37:02 1msM2w-kF-2M failed to expand "<; ${if exists{/etc/exim4/passwd.client}

Bug#1000958: /etc/aliases dosn't work since bullseye

2021-12-01 Thread Jörg Frings-Fürst
Hello, here are my config and the logs: /etc/aliases: # /etc/aliases mailer-daemon: postmaster postmaster: root nobody: root hostmaster: root usenet: root news: root webmaster: root www: root ftp: root abuse: root noc: root security: root root: ser...@x.de logcheck: root

Bug#1000661: Missing b-dep on libbase64-ocaml-dev

2021-12-01 Thread Andreas Beckmann
Control: tag -1 sid bookworm Control: close -1 1:4.2.4-1 On Wed, 1 Dec 2021 16:09:41 +0800 Andy Li wrote: I've uploaded 1:4.2.4-1, which fixed the build problem regarding base64. So we can close this. Andreas

Processed: Re: Bug#1000661: Missing b-dep on libbase64-ocaml-dev

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 sid bookworm Bug #1000661 [haxe] Missing b-dep on libbase64-ocaml-dev Added tag(s) bookworm and sid. > close -1 1:4.2.4-1 Bug #1000661 [haxe] Missing b-dep on libbase64-ocaml-dev Marked as fixed in versions haxe/1:4.2.4-1. Bug #1000661 [haxe] Missing b-dep on

Bug#1000958: /etc/aliases dosn't work since bullseye

2021-12-01 Thread Jörg Frings-Fürst
Package: exim4-daemon-light Version: 4.94.2-7 Severity: critical File: /usr/sbin/exim4 Hello, on a new bullseye system /etc/aliases dosn't work. I send all files with the next mail. CU Jörg -- Package-specific info: Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57 Copyright (c) University

Bug#1000863: marked as done (php-predis: missing Breaks+Replaces: libphp-predis)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 12:33:37 + with message-id and subject line Bug#1000863: fixed in php-nrk-predis 1.1.9-5 has caused the Debian Bug report #1000863, regarding php-predis: missing Breaks+Replaces: libphp-predis to be marked as done. This means that you claim that the

Processed: limit source to php-nrk-predis, tagging 1000863

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source php-nrk-predis Limiting to bugs with field 'source' containing at least one of 'php-nrk-predis' Limit currently set to 'source':'php-nrk-predis' > tags 1000863 + pending Bug #1000863 [php-predis] php-predis: missing Breaks+Replaces:

Processed: severity of 998377 is important

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 998377 important Bug #998377 [src:mlv] mlv: FTBFS with new dash version due to bashism in configure.ac Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 998377:

Bug#1000955: libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend

2021-12-01 Thread Filippo Rusconi
Package: libkf5globalaccel-bin Version: 5.78.0-3 Severity: critical Tags: upstream Justification: breaks the whole system X-Debbugs-Cc: lopi...@debian.org Greetings, it is now a reproducible fact that my Plasma session goes awry in two different situations: 1. When I plug in a headphones+micro

Bug#994841: marked as done (sqlparse: CVE-2021-32839)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 11:03:48 + with message-id and subject line Bug#994841: fixed in sqlparse 0.4.2-1 has caused the Debian Bug report #994841, regarding sqlparse: CVE-2021-32839 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#998557: spice-gtk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "celt051"

2021-12-01 Thread Simon Chopin
Package: spice-gtk Version: 0.39-3 Followup-For: Bug #998557 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch X-Debbugs-Cc: simon.cho...@canonical.com Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/rules: remove

Processed: Re: spice-gtk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "celt051"

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #998557 [src:spice-gtk] spice-gtk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "celt051" Added tag(s) patch. -- 998557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998557 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1000953: c-blosc: FTBFS on mips64el

2021-12-01 Thread Bastian Germann
Source: c-blosc Severity: serious Version: 1.21.1+ds2-1 The build fails on mips64el with: 98% tests passed, 35 tests failed out of 1651 Total Test time (real) = 452.24 sec The following tests FAILED: 1 - test_api (Failed) 2 - test_bitshuffle_leftovers (Failed) 270

Bug#1000942: [Pkg-rust-maintainers] Bug#1000942: rust-zbus-macros - autopkgtest failure, makes reverse dependencies FTBFS.

2021-12-01 Thread Henry-Nicolas Tourneur
Package: rust-zbus-macros Version: 1.0.0-3 Severity: serious x-debbugs-cc: deb...@nilux.be The rust-zbus-macros autopkgtest is failing: error[E0432]: unresolved import `zbus` --> /tmp/tmp.2o6G5gYnNc/registry/zbus-1.0.0/src/object_server.rs:54:1 | 54 | #[dbus_interface(name =

Processed: tagging 1000255, tagging 1000732

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1000255 + sid bookworm Bug #1000255 {Done: Louis-Philippe Véronneau } [src:python-mpv] mpv: autopkgtest failures Added tag(s) sid and bookworm. > tags 1000732 + sid bookworm Bug #1000732 {Done: Håvard Flaget Aasen }

Bug#999799: marked as done (cffi breaks cl-plus-ssl autopkgtest on armhf and i386: OMPILE-FILE-ERROR while compiling #)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 08:34:17 + with message-id and subject line Bug#999799: fixed in cffi 1:0.24.1-2 has caused the Debian Bug report #999799, regarding cffi breaks cl-plus-ssl autopkgtest on armhf and i386: OMPILE-FILE-ERROR while compiling # to be marked as done. This

Bug#998486: marked as done (ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby3.0" failed.)

2021-12-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 Dec 2021 08:37:29 + with message-id and subject line Bug#998486: fixed in ruby-puma-worker-killer 0.3.1-3 has caused the Debian Bug report #998486, regarding ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you

Processed: 999531: forwarded upstream

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 999531 https://gitlab.com/ase/ase/-/issues/1010 Bug #999531 [src:python-ase] python-ase: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Processed: 994785: pending

2021-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 994785 ! Bug #994785 [src:python-ase] python-ase: autopkgtest regression on arm64/ppc64el: TestSlab.test_vibration_on_surface Owner recorded as Andrius Merkys . > tags 994785 + upstream fixed-upstream Bug #994785 [src:python-ase]

Bug#1000661: Missing b-dep on libbase64-ocaml-dev

2021-12-01 Thread Andy Li
Hi, On Fri, Nov 26, 2021 at 11:45 PM Julien Puydt wrote: > I was checking whether a recent dune would break any package, and my > test failed because Base64 was an unbound module -- it's a missing > build-dep on libbase64-ocaml-dev, so it should be pretty > straightforward to fix. I've uploaded

Bug#994785: marked as pending in python-ase

2021-12-01 Thread Andrius Merkys
Control: tag -1 pending Hello, Bug #994785 in python-ase reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#994785 marked as pending in python-ase

2021-12-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #994785 [src:python-ase] python-ase: autopkgtest regression on arm64/ppc64el: TestSlab.test_vibration_on_surface Added tag(s) pending. -- 994785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994785 Debian Bug Tracking System Contact