Bug#1009040: marked as done (esys-particle: build-depends on removed libltdl7-dev)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Tue, 26 Apr 2022 05:18:47 + with message-id and subject line Bug#1009040: fixed in esys-particle 2.3.5+dfsg2-5 has caused the Debian Bug report #1009040, regarding esys-particle: build-depends on removed libltdl7-dev to be marked as done. This means that you claim that the

Processed: Re: calibre: FTBFS on mips64el

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1010185 calibre/5.41.0+dfsg-2~exp1 Bug #1010185 {Done: Nicholas D Steeves } [src:calibre] calibre: FTBFS on mips64el Marked as fixed in versions calibre/5.41.0+dfsg-2~exp1. > End of message, stopping processing here. Please contact me if

Bug#1009208: ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array

2022-04-25 Thread duck
Quack, Indeed, I failed to see it was assigned to both, thanks for the fix. \_o< -- Marc Dequènes

Bug#1010185: marked as done (calibre: FTBFS on mips64el)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Tue, 26 Apr 2022 01:03:49 + with message-id and subject line Bug#1010185: fixed in calibre 5.41.0+dfsg-2 has caused the Debian Bug report #1010185, regarding calibre: FTBFS on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1010192: ModuleNotFoundError: No module named 'qrtools'

2022-04-25 Thread Christoph Anton Mitterer
Package: qtqr Version: 2.1~bzr46-2 Severity: grave Justification: renders package unusable Hey. On a fresh install of the package: $ qtqr Traceback (most recent call last): File "/usr/bin/qtqr", line 15, in from qrtools import QR ModuleNotFoundError: No module named 'qrtools' Thanks,

Bug#1009426: marked as done (xkcdpass: FTBFS: test case raises “TypeError: … missing 1 required positional argument: 'self'”)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Tue, 26 Apr 2022 00:23:43 + with message-id and subject line Bug#1009426: fixed in xkcdpass 1.19.3+dfsg1-2 has caused the Debian Bug report #1009426, regarding xkcdpass: FTBFS: test case raises “TypeError: … missing 1 required positional argument: 'self'” to be marked as

Bug#1010189: fs-uae-launcher is broken in Sid

2022-04-25 Thread John Paul Adrian Glaubitz
Control: severity -1 normal Control: forcemerge 1010048 -1 Hello! On 4/26/22 00:44, Miguel A. Vallejo wrote: > FS-UAE-Launcher in Debian Sid is now broken. It opens with a totally > corrupted window and the terminal outputs a ton of errors. fs-uae-launcher is not part of Debian unstable. It's

Processed: Re: Bug#1010189: fs-uae-launcher is broken in Sid

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1010189 [fs-uae-launcher] fs-uae-launcher is broken in Sid Severity set to 'normal' from 'grave' > forcemerge 1010048 -1 Bug #1010048 [fs-uae-launcher] fs-uae-launcher: GUI is corrupted. Bug #1010189 [fs-uae-launcher] fs-uae-launcher is

Processed: tagging 957366

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 957366 + ftbfs Bug #957366 [src:intercal] intercal: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957366

Bug#1010189: fs-uae-launcher is broken in Sid

2022-04-25 Thread Miguel A. Vallejo
Package: fs-uae-launcher Version: 3.0.5+dfsg-1 Severity: grave FS-UAE-Launcher in Debian Sid is now broken. It opens with a totally corrupted window and the terminal outputs a ton of errors. I suspect the problem is now that PYQT5 does not accept floats anymore. I also noticed the available

Bug#1007744: dovecot: FTBFS on ppc64el

2022-04-25 Thread Noah Meyerhans
On Mon, Apr 25, 2022 at 12:15:40PM +0300, Timo Sirainen wrote: > >> It looks like the ppc64el build was retried and succeeded. > >> > >> Maybe the timeouts should be increased for slow build systems, similar > >> what upstream did for running under valgrind with commit 2d12409a > >> ("lib-smtp:

Processed: Re: Should zorp be removed?

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1008285 normal Bug #1008285 [src:zorp] Should zorp be removed? Severity set to 'normal' from 'serious' > reassign 1008285 ftp.debian.org Bug #1008285 [src:zorp] Should zorp be removed? Bug reassigned from package 'src:zorp' to

Bug#995838: [htcondor-debian] Bug#995838: Should condor be removed?

2022-04-25 Thread Moritz Mühlenhoff
Am Fri, Oct 29, 2021 at 01:36:27PM + schrieb Tim Theisen: > I plan to upload a new version this weekend. Did you make progress with updating condor? Cheers, Moritz

Bug#1008285: Should zorp be removed?

2022-04-25 Thread Moritz Mühlenhoff
severity 1008285 normal reassign 1008285 ftp.debian.org retitle 1008285 RM: -- RoM; Depends on Python 2 thanks Am Fri, Mar 25, 2022 at 11:30:26PM +0100 schrieb Moritz Muehlenhoff: > Source: zorp > Version: 7.0.1~alpha2-3 > Severity: serious > > Your package came up as a candidate for removal

Processed: Re: Should postnews be removed?

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1008272 normal Bug #1008272 [src:postnews] Should postnews be removed? Severity set to 'normal' from 'serious' > reassign 1008272 ftp.debian.org Bug #1008272 [src:postnews] Should postnews be removed? Bug reassigned from package

Bug#1008272: Should postnews be removed?

2022-04-25 Thread Moritz Mühlenhoff
severity 1008272 normal reassign 1008272 ftp.debian.org retitle 1008272 RM: -- RoM; depends on Python 2, unmaintained thanks Am Fri, Mar 25, 2022 at 08:57:50PM +0100 schrieb Moritz Muehlenhoff: > Source: postnews > Version: 0.7-1 > Severity: serious > > Your package came up as a candidate for

Bug#1010176: marked as done (node-send: Depends: node-statuses (< 2) but 2.0.1+~2.0.0-3 is to be installed)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 20:49:10 + with message-id and subject line Bug#1010176: fixed in node-send 0.18.0+~cs1.19.1-2 has caused the Debian Bug report #1010176, regarding node-send: Depends: node-statuses (< 2) but 2.0.1+~2.0.0-3 is to be installed to be marked as done. This

Processed: properly close to avoid theano autorm

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1007890 python3-nbclient Bug #1007890 {Done: Gordon Ball } [python3-nbclient,src:theano] FTBFS: No module named 'ipython_genutils' Bug reassigned from package 'python3-nbclient,src:theano' to 'python3-nbclient'. No longer marked as

Bug#1010176: marked as pending in node-send

2022-04-25 Thread Yadd
Control: tag -1 pending Hello, Bug #1010176 in node-send 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#1010176 marked as pending in node-send

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1010176 [node-send] node-send: Depends: node-statuses (< 2) but 2.0.1+~2.0.0-3 is to be installed Added tag(s) pending. -- 1010176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010176 Debian Bug Tracking System Contact

Bug#1010185: calibre: FTBFS on mips64el

2022-04-25 Thread Sebastian Ramacher
Source: calibre Version: 5.41.0+dfsg-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org calibre FTBFS on mips64el: test_zeroconf (calibre.test_build.BuildTest) ... ok [0.0 s]

Bug#989409: nss-pam-ldapd's autopkgtest fails with OpenLDAP 2.5

2022-04-25 Thread Salvatore Bonaccorso
Hi Arthur, On Fri, Feb 18, 2022 at 07:11:24PM -0800, Ryan Tandy wrote: > Hi Arthur, > > sorry for the long delayed followup. > > On Sun, Nov 14, 2021 at 04:20:03PM +0100, Arthur de Jong wrote: > > > However the test_pamcmds script fails with the new version. The login > > > with the correct

Bug#1008558: marked as done (gnome-shell-extension-tiling-assistant: does not declare compatibility with GNOME Shell 42)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 19:23:20 + with message-id and subject line Bug#1008558: fixed in gnome-shell-extension-tiling-assistant 32-2 has caused the Debian Bug report #1008558, regarding gnome-shell-extension-tiling-assistant: does not declare compatibility with GNOME Shell 42

Bug#1010177: r8168-dkms: dkms build failed on kernel 5.17

2022-04-25 Thread Alexey Morsov
Package: r8168-dkms Version: 8.049.02-1 Severity: grave Tags: ftbfs Justification: renders package unusable Dear Maintainer, * What led up to the situation? update linux-image to 5.17 * What exactly did you do (or not do) that was effective (or ineffective)? apt full-upgrade *

Bug#1010176: node-send: Depends: node-statuses (< 2) but 2.0.1+~2.0.0-3 is to be installed

2022-04-25 Thread Adrian Bunk
Package: node-send Version: 0.18.0+~cs1.19.1-1 Severity: serious The following packages have unmet dependencies: node-send : Depends: node-statuses (< 2) but 2.0.1+~2.0.0-3 is to be installed

Processed: Re: mutt: license conflict with libsasl2

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #999672 [mutt] mutt: license conflict with libsasl2 Added tag(s) patch. > severity -1 serious Bug #999672 [mutt] mutt: license conflict with libsasl2 Severity set to 'serious' from 'important' -- 999672:

Bug#1010172: marked as done (macaulay2: autopkgtest regression)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 18:41:55 + with message-id and subject line Bug#1010172: fixed in macaulay2 1.19.1+ds-8 has caused the Debian Bug report #1010172, regarding macaulay2: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt

Bug#1009188: ipp-usb

2022-04-25 Thread alain
found this : https://github.com/OpenPrinting/ipp-usb tried to compile it from source but didn't managed . the package does not exists in experimental (only stable and sid) . installed the golang package but didn't succed to compile ipp-usb . friendly , respectfully , alain .

Processed: Re: Should sandsifter be removed?

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1008274 normal Bug #1008274 [src:sandsifter] Should sandsifter be removed? Severity set to 'normal' from 'serious' > reassign 1008274 ftp.debian.org Bug #1008274 [src:sandsifter] Should sandsifter be removed? Bug reassigned from package

Bug#1008274: Should sandsifter be removed?

2022-04-25 Thread Moritz Mühlenhoff
severity 1008274 normal reassign 1008274 ftp.debian.org retitle 1008274 RM: -- RoM; depends on Python 2, unmaintained thanks Am Fri, Mar 25, 2022 at 08:59:21PM +0100 schrieb Moritz Muehlenhoff: > Source: sandsifter > Version: 1.04-1 > Severity: serious > > Your package came up as a candidate

Bug#1008271: Should arriero be removed?

2022-04-25 Thread Moritz Mühlenhoff
severity 1008271 normal reassign 1008271 ftp.debian.org retitle 1008271 RM: arriero -- RoQA; depends on Python 2, unmaintained thanks Am Fri, Mar 25, 2022 at 08:57:10PM +0100 schrieb Moritz Muehlenhoff: > Source: arriero > Version: 0.6-1 > Severity: serious > > Your package came up as a

Processed: Re: Should arriero be removed?

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1008271 normal Bug #1008271 [src:arriero] Should arriero be removed? Severity set to 'normal' from 'serious' > reassign 1008271 ftp.debian.org Bug #1008271 [src:arriero] Should arriero be removed? Bug reassigned from package

Bug#1000919: marked as done (ldc: FTBFS with llvm-toolchain-13)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 18:00:15 + with message-id and subject line Bug#1000919: fixed in ldc 1:1.29.0-1 has caused the Debian Bug report #1000919, regarding ldc: FTBFS with llvm-toolchain-13 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: [bts-link] source package pipewire

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package pipewire > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#1010172: macaulay2: autopkgtest regression

2022-04-25 Thread Sebastian Ramacher
Source: macaulay2 Version: 1.19.1+ds-7 Severity: serious Since the last upload, autopkgtests fail on all architectures: stdio:1:1:(3): error: test(s) #267, 268, 269 of package Core failed. cd /tmp/M2-2816-0/1-rundir/; GC_MAXIMUM_HEAP_SIZE=400M "/usr/bin/M2-binary" --int --no-randomize

Bug#1009416: marked as done (fungw: FTBFS: perl.h:736:25: error: expected expression before ‘do’)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 17:18:59 + with message-id and subject line Bug#1009416: fixed in fungw 1.2.1-1 has caused the Debian Bug report #1009416, regarding fungw: FTBFS: perl.h:736:25: error: expected expression before ‘do’ to be marked as done. This means that you claim that

Bug#1010161: marked as done (x11-xkb-utils-udeb: broken setxkbmap within the installer)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 17:05:43 + with message-id and subject line Bug#1010161: fixed in x11-xkb-utils 7.7+7 has caused the Debian Bug report #1010161, regarding x11-xkb-utils-udeb: broken setxkbmap within the installer to be marked as done. This means that you claim that the

Bug#1010170: FTBFS: lisp/net/tramp-archive-tests.log contains unexpected results

2022-04-25 Thread Vincent Lefevre
Source: emacs Version: 1:27.1+1-3.1 Severity: serious Tags: ftbfs When rebuilding emacs: SUMMARY OF TEST RESULTS --- Files examined: 267 Ran 3883 tests, 3832 results as expected, 1 unexpected, 50 skipped 1 files contained unexpected results: lisp/net/tramp-archive-tests.log

Bug#1009188: [OpenPrinting/ipp-usb] ipp-usb is not ready for this device (Issue #48)

2022-04-25 Thread alain
Le 25/04/2022 à 17:33, alain a écrit : Le 25/04/2022 à 16:10, alain a écrit : uninstalled apparmor and reboot . system-config-printer  do not work better and do not recognize my printer . with the 0.9.20-1 ipp-usb package , it seems not to work better than with the stable one (ok for

Bug#1010166: webkit2gtk: 2.36.1-1 apparent regression seen in devhelp autopkgtest

2022-04-25 Thread Jeremy Bicha
Source: webkit2gtk Version: 2.36.1-1 Severity: serious The new release of webkit2gtk won't migrate to Testing because of an autopkgtest regression in devhelp. I'm filing this bug to make sure that the maintainer notices the issue. https://ci.debian.net/packages/d/devhelp/testing/amd64/ Test

Bug#1009685: marked as done (opm-grid: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.10.so')

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 15:34:35 + with message-id and subject line Bug#1009685: fixed in opm-grid 2021.10-5 has caused the Debian Bug report #1009685, regarding opm-grid: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.10.so' to be marked as

Bug#1010164: fails autopkgtest against Octave 7

2022-04-25 Thread Sébastien Villemot
Package: octave-bart Version: 0.7.00-2 Severity: serious Tags: patch Control: block 1009865 by -1 Dear Maintainer, The autopkgtest for octave-bart fails against octave 7.1.0-2 recently uploaded to unstable. See: https://ci.debian.net/data/autopkgtest/testing/amd64/b/bart/21135046/log.gz The

Processed: fails autopkgtest against Octave 7

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > block 1009865 by -1 Bug #1009865 [release.debian.org] transition: octave 1009865 was not blocked by any bugs. 1009865 was not blocking any bugs. Added blocking bug(s) of 1009865: 1010164 -- 1009865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009865

Bug#1010161: x11-xkb-utils-udeb: broken setxkbmap within the installer

2022-04-25 Thread Cyril Brulebois
Julien Cristau (2022-04-25): > Control: tag -1 upstream patch > Control: forwarded -1 > https://gitlab.freedesktop.org/xorg/app/setxkbmap/-/merge_requests/4 > > On Mon, Apr 25, 2022 at 03:44:59PM +0200, Cyril Brulebois wrote: > > And thanks again for the quick turnaround for the libxrandr2 udeb

Bug#1009685: marked as done (opm-grid: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.10.so')

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 14:35:49 + with message-id and subject line Bug#1009685: fixed in opm-grid 2021.10-4 has caused the Debian Bug report #1009685, regarding opm-grid: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.10.so' to be marked as

Processed: Re: Bug#1010161: x11-xkb-utils-udeb: broken setxkbmap within the installer

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 upstream patch Bug #1010161 [x11-xkb-utils-udeb] x11-xkb-utils-udeb: broken setxkbmap within the installer Added tag(s) patch and upstream. > forwarded -1 > https://gitlab.freedesktop.org/xorg/app/setxkbmap/-/merge_requests/4 Bug #1010161

Bug#1010161: x11-xkb-utils-udeb: broken setxkbmap within the installer

2022-04-25 Thread Julien Cristau
Control: tag -1 upstream patch Control: forwarded -1 https://gitlab.freedesktop.org/xorg/app/setxkbmap/-/merge_requests/4 On Mon, Apr 25, 2022 at 03:44:59PM +0200, Cyril Brulebois wrote: > And thanks again for the quick turnaround for the libxrandr2 udeb > addition. The next issue is

Bug#1010161: x11-xkb-utils-udeb: broken setxkbmap within the installer

2022-04-25 Thread Cyril Brulebois
Package: x11-xkb-utils-udeb Version: 7.7+6+b1 Severity: serious Tags: d-i Justification: breaks graphical installer X-Debbugs-Cc: debian-b...@lists.debian.org Hi X people, And thanks again for the quick turnaround for the libxrandr2 udeb addition. The next issue is is_xwayland() erroring out at

Processed: Re: emacs-gtk: tries to read a config file from another user's home dir

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42827 Bug #1010152 [emacs-gtk] emacs-gtk: tries to read a config file from another user's home dir Set Bug forwarded-to-address to 'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42827'. -- 1010152:

Bug#1010152: emacs-gtk: tries to read a config file from another user's home dir

2022-04-25 Thread Vincent Lefevre
Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42827 On 2022-04-25 15:37:08 +0200, Vincent Lefevre wrote: > This is also fixed in upstream's 27.2. 2020-08-17 Robert Pluim Fix bug with ~/Emacs file not being read at init * src/xrdb.c (get_user_app): Put

Bug#1010152: emacs-gtk: tries to read a config file from another user's home dir

2022-04-25 Thread Vincent Lefevre
On 2022-04-25 15:23:43 +0200, Vincent Lefevre wrote: > I can reproduce the issue with upstream's 27.1 version: > > 11openat(AT_FDCWD, "/home/vlefevrePOSIX/Emacs", O_RDONLY) = -1 ENOENT (No > such file or directory) > 11openat(AT_FDCWD, "/home/vlefevreEmacs", O_RDONLY) = -1 ENOENT (No

Processed: Re: emacs-gtk: tries to read a config file from another user's home dir

2022-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1010152 upstream fixed-upstream Bug #1010152 [emacs-gtk] emacs-gtk: tries to read a config file from another user's home dir Added tag(s) fixed-upstream and upstream. > End of message, stopping processing here. Please contact me if you

Bug#1010152: emacs-gtk: tries to read a config file from another user's home dir

2022-04-25 Thread Vincent Lefevre
Control: tags upstream fixed-upstream I can reproduce the issue with upstream's 27.1 version: 11openat(AT_FDCWD, "/home/vlefevrePOSIX/Emacs", O_RDONLY) = -1 ENOENT (No such file or directory) 11openat(AT_FDCWD, "/home/vlefevreEmacs", O_RDONLY) = -1 ENOENT (No such file or directory)

Bug#1008653: marked as done (backintime-qt broken in sid after python upgrade)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 12:33:47 + with message-id and subject line Bug#1008653: fixed in backintime 1.3.2-0.1 has caused the Debian Bug report #1008653, regarding backintime-qt broken in sid after python upgrade to be marked as done. This means that you claim that the problem

Bug#1010152: emacs-gtk: tries to read a config file from another user's home dir

2022-04-25 Thread Vincent Lefevre
Due to this issue, I reported the bug from but another machine (I should have unset DISPLAY, instead). So here are some corrections. On 2022-04-25 14:26:29 +0200, Vincent Lefevre wrote: > Package: emacs-gtk > Version: 1:27.1+1-3.1+b1 Actually 1:27.1+1-3.1 > -- System Information: The actual

Bug#1008653: backintime-qt broken in sid after python upgrade

2022-04-25 Thread Bastian Germann
On Sun, 24 Apr 2022 22:17:17 +0200 Fabio Fantoni wrote: I also prepared an NMU upload on mentors and open RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009834 I sponsored this. NMU debdiff is attached.diff -Nru backintime-1.2.1/CHANGES backintime-1.3.2/CHANGES ---

Bug#1010152: emacs-gtk: tries to read a config file from another user's home dir

2022-04-25 Thread Vincent Lefevre
Package: emacs-gtk Version: 1:27.1+1-3.1+b1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team After wondering why Emacs was hanging on startup after a reinstallation of machines with Debian 11 at my lab, I looked at the strace output (strace -o

Bug#1010118: marked as done (qtwebkit-opensource-src FTBFS with ICU 71.1)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 11:34:05 + with message-id and subject line Bug#1010118: fixed in qtwebkit-opensource-src 5.212.0~alpha4-16 has caused the Debian Bug report #1010118, regarding qtwebkit-opensource-src FTBFS with ICU 71.1 to be marked as done. This means that you claim

Bug#1009939: marked as pending in sip6

2022-04-25 Thread Dmitry Shachnev
Control: tag -1 pending Hello, Bug #1009939 in sip6 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#1009939 marked as pending in sip6

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009939 [src:sip6] sip6: AttributeError: 'YaccProduction' object has no attribute 'parser_manager' Added tag(s) pending. -- 1009939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009939 Debian Bug Tracking System Contact

Processed: Re: ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:ruby-faker 1.9.1-3 Bug #1009208 {Done: Marc Dequènes (duck) } [src:ruby-i18n, src:ruby-faker] ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array Bug reassigned from package 'src:ruby-i18n, src:ruby-faker' to

Bug#1009208: ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array

2022-04-25 Thread Paul Gevers
Control: reassign -1 src:ruby-faker 1.9.1-3 Control: fixed -1 2.20.0-1 Control: affects -1 src:ruby-i18n On Mon, 25 Apr 2022 17:34:12 +0900 =?UTF-8?Q?Marc_Dequ=C3=A8nes_=28duck=29?= wrote: Version: 2.20.0-1 As this bug was assigned to two sources, the bts didn't know which package this

Bug#1009039: marked as done (dico: build-depends on removed libltdl7-dev)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 09:33:48 + with message-id and subject line Bug#1009039: fixed in dico 2.11-1 has caused the Debian Bug report #1009039, regarding dico: build-depends on removed libltdl7-dev to be marked as done. This means that you claim that the problem has been dealt

Bug#1009188: Bug#1008997: cups: impossible to print on hp envy 5536 from sid

2022-04-25 Thread alain
1) set ipp-usb from stable version to sid version 2) reading /var/log/ipp-usb/ alain@sid:/var/log/ipp-usb$ ls 03f0-c311-CN595530XD06BX-HP-ENVY-5530-series.log 03f0-c311-CN595530XD06BX-HP-ENVY-5530-series.log.0.gz 03f0-c311-CN595530XD06BX-HP-ENVY-5530-series.log.1.gz

Bug#1007744: dovecot: FTBFS on ppc64el

2022-04-25 Thread Timo Sirainen
On 17. Apr 2022, at 5.43, Noah Meyerhans wrote: > > On Wed, Apr 13, 2022 at 09:33:58PM +0200, Christian Göttsche wrote: >> It looks like the ppc64el build was retried and succeeded. >> >> Maybe the timeouts should be increased for slow build systems, similar >> what upstream did for running

Processed: courier-unicode: Build-Depends not available in testing

2022-04-25 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1003933 Bug #1010145 [src:courier-unicode] courier-unicode: Build-Depends not available in testing 1010145 was not blocked by any bugs. 1010145 was not blocking any bugs. Added blocking bug(s) of 1010145: 1003933 -- 1010145:

Bug#1010145: courier-unicode: Build-Depends not available in testing

2022-04-25 Thread Paul Gevers
Source: courier-unicode Version: 2.1.2-2 Severity: serious Tags: ftbfs Justification: ftbfs User: trei...@debian.org Usertags: edos-uninstallable Control: block -1 by 1003933 Dear maintainer, Your package Build-Depends on w3c-sgml-lib which has an RC bug for a while now. The package has been

Bug#1009208: marked as done (ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 17:34:12 +0900 with message-id <9c50ebc27d18cf22b2ebea967682c...@duckcorp.org> and subject line Re: ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array has caused the Debian Bug report #1009208, regarding ruby-i18n breaks ruby-faker

Bug#1004870: python-xarray: autopkgtest regression on s390x

2022-04-25 Thread Rajendra Kharat1
Hi Graham, We have identified the RCA of the problem that reported last month related to python-xarray. The problem was in pandas library where handling of big endian arch was not available in below file. pandas/_libs/tslibs/conversion.pyx +225 By the time we identify this issue and fix

Bug#1010117: marked as done (librostlab: binary-all FTBFS)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 08:33:51 + with message-id and subject line Bug#1010117: fixed in librostlab 1.0.20-12 has caused the Debian Bug report #1010117, regarding librostlab: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1010070: marked as done (python3-fuse: several bindings broken on Python 3.10)

2022-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2022 07:04:14 + with message-id and subject line Bug#1010070: fixed in python-fuse 2:1.0.5-1 has caused the Debian Bug report #1010070, regarding python3-fuse: several bindings broken on Python 3.10 to be marked as done. This means that you claim that the

Bug#1010140: aqsis: FTBFS on arm{el,hf}

2022-04-25 Thread Sebastian Ramacher
Source: aqsis Version: 1.8.2+git20210815-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org aqsis FTBFS on armel and armhf: [ 34%] Building CXX object

Bug#1008776: intel-media-va-driver: Segmentation fault with gstreamer based applications

2022-04-25 Thread Sebastian Ramacher
Hi Kai On 2022-04-06 17:27:46 +1000, Kai Weber wrote: > * Sebastian Ramacher : > > > That could be another case of the driver expecting to have a kernel > > available which in fact is disabled in the open source build. If > > 22.3.1+dfsg1-1 doesn't fix the issue for you, please let my know your