Bug#1003578: marked as done (hash-slinger: Unnecessary dependency on python3-ipaddr)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Thu, 24 Feb 2022 07:03:39 + with message-id and subject line Bug#1003578: fixed in hash-slinger 3.1-1.1 has caused the Debian Bug report #1003578, regarding hash-slinger: Unnecessary dependency on python3-ipaddr to be marked as done. This means that you claim that the

Bug#1005912: hydrogen: autopkgtest regression on arm64 and ppc64el: H2Core::Instrument::dequeue(): Assertion `__queued > 0' failed.

2022-02-23 Thread Nicholas D Steeves
Hi Paul, Debian CI team, and Denis, Paul and Debian CI team, do you know if a dummy alsa driver (and dummy sequencer driver) can be enabled on DebCI systems? This would make the testbed more comparable to a real system and increase the value of the tests for multimedia packages. If not, please

Bug#1006312: marked as done (appstream-compose: missing Breaks+Replaces: appstream (<< 0.15.2))

2022-02-23 Thread Debian Bug Tracking System
Your message dated Thu, 24 Feb 2022 04:18:49 + with message-id and subject line Bug#1006312: fixed in appstream 0.15.2-2 has caused the Debian Bug report #1006312, regarding appstream-compose: missing Breaks+Replaces: appstream (<< 0.15.2) to be marked as done. This means that you claim that

Bug#1006073: marked as done (xine-lib-1.2: FTBFS: dh_missing: error: missing files, aborting)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Thu, 24 Feb 2022 03:06:10 + with message-id and subject line Bug#1006073: fixed in xine-lib-1.2 1.2.11-2 has caused the Debian Bug report #1006073, regarding xine-lib-1.2: FTBFS: dh_missing: error: missing files, aborting to be marked as done. This means that you claim

Bug#1005426: marked as done (ruby-jwt: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: raise JWT::RequiredDependencyError, "You currently have OpenSSL #{OpenSSL::VERSION}. PS support require

2022-02-23 Thread Debian Bug Tracking System
Your message dated Thu, 24 Feb 2022 01:50:01 + with message-id and subject line Bug#1005426: fixed in ruby-jwt 2.3.0-1 has caused the Debian Bug report #1005426, regarding ruby-jwt: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: raise JWT::RequiredDependencyError, "You currently

Bug#1006352: bsfiltger: "Cannot load such file -- sdbm (LoadError)"

2022-02-23 Thread YABUKI Yukiharu
Package: bsfilter Version: 1:1.0.19-2.1 Severity: grave Justification: renders package unusable Dear Maintainer, Due to ruby transition, ruby could not load sdbm module. I use bsfilter which classifies spam mail. ``` $ bsfilter :85:in `require': cannot load such file -- sdbm (LoadError) Did

Bug#1003012: Fixing #1003012 in bullseye (was: Re: Bug#1003012: closed by Salvatore Bonaccorso (Re: Accepted bash 5.1-6 (source) into unstable))

2022-02-23 Thread Daniel Qian
Is new version bullseye released? I encountered the same issue. On Sat, 8 Jan 2022 08:52:28 +0100 Salvatore Bonaccorso wrote: > Hi Frank, > > On Sat, Jan 08, 2022 at 12:27:35AM +0100, Frank Heckenbach wrote: > > Thanks for the quick fix! > > Just in avoidance of doubt, thanks goes to Matthias, I

Bug#1005426: marked as pending in ruby-jwt

2022-02-23 Thread Antonio Terceiro
Control: tag -1 pending Hello, Bug #1005426 in ruby-jwt 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#1005426 marked as pending in ruby-jwt

2022-02-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005426 [src:ruby-jwt] ruby-jwt: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: raise JWT::RequiredDependencyError, "You currently have OpenSSL #{OpenSSL::VERSION}. PS support requires >= 2.1" Added tag(s) pending. -- 1005426:

Bug#1006063: marked as done (ri-li: FTBFS: Impossible d'initialiser SDL:Couldn't open X11 display)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Thu, 24 Feb 2022 01:22:41 + with message-id and subject line Bug#1006063: fixed in ri-li 2.0.1+ds2-1 has caused the Debian Bug report #1006063, regarding ri-li: FTBFS: Impossible d'initialiser SDL:Couldn't open X11 display to be marked as done. This means that you claim

Processed: Re: Bug#1006348: lintian: Tag improbable-bug-number-in-closes condition considers 7-digit bug numbers improbable

2022-02-23 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1003272 Bug #1006348 [lintian] lintian: Tag improbable-bug-number-in-closes condition considers 7-digit bug numbers improbable 1006348 was not blocked by any bugs. 1006348 was not blocking any bugs. Added blocking bug(s) of 1006348: 1003272 and 1003353

Bug#1006350: pidgin: crashes when typing past visible number of lines

2022-02-23 Thread Phil Dibowitz
Package: pidgin Version: 2.14.8-2 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, It seems 2.14.6 introduced a bug where Pidgin crashes when the user types somethign longer than the visible number of lines - not always, but often. This has been reported

Bug#1006141: marked as done (supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}')

2022-02-23 Thread Debian Bug Tracking System
Your message dated Thu, 24 Feb 2022 00:05:29 + with message-id and subject line Bug#1006141: fixed in supertuxkart 1.3+dfsg1-3 has caused the Debian Bug report #1006141, regarding supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}' to be

Bug#1006043: closing 1006043

2022-02-23 Thread Cédric Boutillier
close 1006043 fixed 1006043 ruby-rqrcode-core/0.2.0-1 thanks This bug has been fixed with the upload of a new upstream version 0.2.0. I am therefore closing the bug.

Processed: closing 1006043

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1006043 Bug #1006043 [src:ruby-rqrcode-core] ruby-rqrcode-core: FTBFS: ERROR: Error installing /tmp/d20220218-241350-fqxx8g/rqrcode_core-0.1.2.gem: rqrcode_core-0.1.2 requires Ruby version ~> 2.3. The current ruby version is 3.0.2.107.

Bug#1006042: Processed: fixed 1006042 in 0.2.0-1

2022-02-23 Thread Cédric Boutillier
Dear Sandro Quoting Sandro Tosi (2022-02-23 18:14:41) > are you sure this is correct? rich never had a 0.2.0-1 upload Sorry, I messed up when copying with my big fingers another bug number. Thank you for noticing, and apologies for the noise. Best wishes, Cédric signature.asc Description:

Processed: notfixed 1006042 in 0.2.0-1

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 1006042 0.2.0-1 Bug #1006042 [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 The source 'rich' and version '0.2.0-1' do not appear to match any binary

Processed: reopening 1006042

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1006042 Bug #1006042 {Done: Cédric Boutillier } [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 'reopen' may be inappropriate when a bug has been closed

Bug#1005737: marked as done (Purging sane-utils deletes the scanner group, created by libsane1)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 22:35:56 + with message-id and subject line Bug#1005737: fixed in sane-backends 1.1.1-3 has caused the Debian Bug report #1005737, regarding Purging sane-utils deletes the scanner group, created by libsane1 to be marked as done. This means that you claim

Bug#1005653: marked as done (nheko: FTBFS: fails to build CMakeFiles/nheko.dir/src/voip/WebRTCSession.cpp.o)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 15:58:15 -0500 with message-id <87a6ehi9lk@svladcjelli.uhoreg.ca> and subject line Re: Bug#1005653: nheko: FTBFS: fails to build CMakeFiles/nheko.dir/src/voip/WebRTCSession.cpp.o has caused the Debian Bug report #1005653, regarding nheko: FTBFS: fails to

Bug#1006308: closed by Debian FTP Masters (reply to Mark Hindley ) (Bug#1006308: fixed in seatd 0.6.4-1)

2022-02-23 Thread Salvatore Bonaccorso
Hi Mark, Sorry was away for the whole day: On Wed, Feb 23, 2022 at 09:22:11AM +, Mark Hindley wrote: > Salvatore, > > On Wed, Feb 23, 2022 at 10:14:59AM +0100, Salvatore Bonaccorso wrote: > > Thanks for the quick fix! > > > > Note there is a typo in the CVE, should have been CVE-2022-25643.

Processed (with 2 errors): Re: adwaita-icon-theme: many missing icons

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1005997 serious Bug #1005997 [adwaita-icon-theme] adwaita-icon-theme: many missing icons Severity set to 'serious' from 'important' > forwarded 1005997 Unknown command or malformed arguments to command. >

Bug#1006336: trinityrnaseq: autopkgtest regression in testing: segmentation fault

2022-02-23 Thread Paul Gevers
Source: trinityrnaseq Version: 2.13.2+dfsg-3 Severity: serious Dear maintainer, Somewhere around the end of January 2022, the autopkgtest of you package started to fail on amd64. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/t/trinityrnaseq/19291359/log.gz All commands completed

Bug#1005311: This bug also affects experimental version 510.47.03-1

2022-02-23 Thread Christian Weeks
This bug also affects experimental version 510.47.03-1 - it looks like the dependencies need updating on the experimental driver as well.

Bug#1005478: marked as done (thermald: FTBFS: src/thd_engine_adaptive.cpp:1002:54: error: ‘gboolean up_client_get_lid_is_closed(UpClient*)’ is deprecated [-Werror=deprecated-declarations])

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 19:04:21 + with message-id and subject line Bug#1005478: fixed in thermald 2.4.7-2 has caused the Debian Bug report #1005478, regarding thermald: FTBFS: src/thd_engine_adaptive.cpp:1002:54: error: ‘gboolean up_client_get_lid_is_closed(UpClient*)’ is

Bug#1005604: marked as done (iptux: FTBFS: ../share/applications/meson.build:2:5: ERROR: Function does not take positional arguments.)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 18:49:22 + with message-id and subject line Bug#1005604: fixed in iptux 0.8.3+git20211122-1 has caused the Debian Bug report #1005604, regarding iptux: FTBFS: ../share/applications/meson.build:2:5: ERROR: Function does not take positional arguments. to be

Processed: Re: Bug#1006333: biboumi: fail to start after libexpat1 update

2022-02-23 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:expat Bug #1006333 [biboumi] biboumi: fail to start after libexpat1 update Bug reassigned from package 'biboumi' to 'src:expat'. No longer marked as found in versions biboumi/8.3-1. Ignoring request to alter fixed versions of bug #1006333 to the same

Bug#1006333: biboumi: fail to start after libexpat1 update

2022-02-23 Thread Jonas Smedegaard
Control: reassign -1 src:expat Control: found -1 2.2.6-2+deb10u3 Control: affects -1 biboumi Quoting Slavko (2022-02-23 18:57:49) > Package: biboumi > Severity: serious > Version: 8.3-1+b1 > > After security upgrade of libexpat library, the biboumi refused to > start with error: > >

Processed: bug 1006330 is forwarded to https://github.com/mitogen-hq/mitogen/issues/906, tagging 1006330

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1006330 https://github.com/mitogen-hq/mitogen/issues/906 Bug #1006330 [ansible-mitogen] broken by python3-distro 1.7.0-1 Set Bug forwarded-to-address to 'https://github.com/mitogen-hq/mitogen/issues/906'. > tags 1006330 + upstream Bug

Bug#1006330: broken by python3-distro 1.7.0-1

2022-02-23 Thread Marco d'Itri
Package: ansible-mitogen Version: 0.3.1-2 Severity: grave Tags: upstream Works with 1.6.0-2, is totally broken with 1.7.0-1. [mux 685121] 14:38:50.354759 D mitogen: PkgutilMethod(): loading 'ansible.module_utils.distro' using <_frozen_importlib_external.SourceFileLoader object at

Processed: fixed 1006042 in 0.2.0-1

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1006042 0.2.0-1 Bug #1006042 {Done: Cédric Boutillier } [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 The source 'rich' and version '0.2.0-1' do not appear

Processed: closing 1006042

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1006042 Bug #1006042 [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Bug#1005810: epiphany-browser: crash on session_tab_free at ../src/ephy-session.c:605

2022-02-23 Thread Alberto Garcia
Control: tags -1 patch fixed-upstream Control: forwarded -1 https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/954 On Tue, Feb 15, 2022 at 04:29:52PM +0200, Andres Gomez wrote: > After talking with the main WebKitGtk developer and maintainer, > he pointed that the cause of the crash

Processed: Re: Bug#1005810: epiphany-browser: crash on session_tab_free at ../src/ephy-session.c:605

2022-02-23 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch fixed-upstream Bug #1005810 [epiphany-browser] epiphany-browser: crash on session_tab_free at ../src/ephy-session.c:605 Added tag(s) fixed-upstream and patch. > forwarded -1 https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/954 Bug #1005810

Processed: bug 1006029 is forwarded to https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/176

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1006029 > https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/176 Bug #1006029 [adwaita-icon-theme] gtk+3.0: FTBFS: dh_auto_test: error: cd debian/build/deb && make -j8 check VERBOSE=1 -k check -j1 returned exit code 2 Set Bug

Bug#1006289: marisa's autopkgtest regressed since rebuild for ruby3.0 as default

2022-02-23 Thread Antonio Terceiro
On Wed, Feb 23, 2022 at 02:44:05AM -0500, Boyuan Yang wrote: > X-Debbugs-CC: kanash...@debian.org terce...@debian.org gunna...@debian.org > > Hi all, > > (see bottom) > > 在 2022-02-22星期二的 22:05 +0100,Paul Gevers写道: > > Source: marisa > > Version: 0.2.6-8 > > Severity: serious > > X-Debbugs-Cc:

Bug#1004556: libmpich-dev: The simplest MPI program compiled with mpich crashes

2022-02-23 Thread Drew Parsons
On 2022-02-22 19:49, Alastair McKinstry wrote: I can disable pmix support in mpich. Thanks Alastair. My tests are now passing with mpich 4.0-3 Pmix is working fine in openmpi, so it’s an mpich/pmix issue of some sort (or maybe ch4) "Working fine" might not be quite the word for it.

Bug#1004849: nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814

2022-02-23 Thread Andreas Beckmann
On 23/02/2022 13.10, Vincent Lefevre wrote: Bug 1004847 against src:nvidia-graphics-drivers was cloned as 1004849, which got reassigned to src:nvidia-graphics-drivers-legacy-390xx, but is 390xx affected? It is not listed on https://nvidia.custhelp.com/app/answers/detail/a_id/5312 Only

Bug#1005920: closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1005920: fixed in coq-doc 8.15.0-3)

2022-02-23 Thread Andreas Beckmann
With all these B-D added, the build fails for me now with Running[3870]: (cd _build/default/doc && /usr/bin/env sphinx-build -q -W -b html sphinx refman-html) Command [3870] exited with code 2: $ (cd _build/default/doc && /usr/bin/env sphinx-build -q -W -b html sphinx refman-html) Warning,

Bug#1004849: nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814

2022-02-23 Thread Vincent Lefevre
On 2022-02-02 11:47:50 +0100, Andreas Beckmann wrote: > https://nvidia.custhelp.com/app/answers/detail/a_id/5312 > > CVE‑2022‑21813NVIDIA GPU Display Driver for Linux contains a > vulnerability in the kernel driver, where improper handling of > insufficient permissions or privileges may

Bug#1006014: marked as done (FTBFS: void value not ignored as it ought to be)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 11:34:08 + with message-id and subject line Bug#1006014: fixed in bind-dyndb-ldap 11.9-5 has caused the Debian Bug report #1006014, regarding FTBFS: void value not ignored as it ought to be to be marked as done. This means that you claim that the problem

Bug#1004729: marked as done (bind9-dyndb-ldap: fails to load dyndb-ldap backend)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 11:34:08 + with message-id and subject line Bug#1004729: fixed in bind-dyndb-ldap 11.9-5 has caused the Debian Bug report #1004729, regarding bind9-dyndb-ldap: fails to load dyndb-ldap backend to be marked as done. This means that you claim that the

Bug#891224: occurs in bullseye release

2022-02-23 Thread Moritz Schlarb
Oh wow, okay, yes... Sorry. I'm probably just to tired for anything... That issue looks familiar and in my Git Repo for libapache2-mod-auth-openidc I even have a tag called debian/2.4.9.4-1, so I probably already nearly solved this but apparently did not release... Sorry about that! I'll

Bug#891224: occurs in bullseye release

2022-02-23 Thread Hamish Moffatt
Hi Moritz, Even after a full restart (systemctl restart apache2), it still causes a segfault on every "apache2ctl graceful". vagrant up (debian/bullseye64) sudo -i apt update apt install apache2; apt install libapache2-mod-auth-openidc systemctl restart apache2 apache2ctl graceful

Bug#891224: occurs in bullseye release

2022-02-23 Thread Hamish Moffatt
It's listed as fixed in the upstream release notes for 2.4.9.2: https://github.com/zmartzone/mod_auth_openidc/releases/tag/v2.4.9.2 Regards Hamish On 23/2/22 20:57, Hamish Moffatt wrote: Hi Moritz, Even after a full restart (systemctl restart apache2), it still causes a segfault on

Bug#1006214: marked as done (node-blueimp-md5: missing Breaks+Replaces: node-md5-hex (<< 3.0.1+~2.19.0-2~))

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 11:02:14 +0100 with message-id <164561053431.2636895.13903813753663682...@auryn.jones.dk> and subject line Re: [Pkg-javascript-devel] Bug#1006214: Bug#1006205: node-md5-hex: ships files already provided by node-blueimp-md5 has caused the Debian Bug report

Processed: tagging 891224

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 891224 - moreinfo pending Bug #891224 {Done: Moritz Schlarb } [libapache2-mod-auth-openidc] Just enabling the module makes apache children segfault Removed tag(s) pending and moreinfo. > thanks Stopping processing here. Please contact me

Bug#891224: occurs in bullseye release

2022-02-23 Thread Moritz Schlarb
Dear Hamish, sorry, I didn't think all the way through what you were writing. Actually, enabling (and probably disabling) modules in Apache2 always requires a restart of the main daemon process - so performing a graceful restart/reload is simply not supported here (you are experiencing the

Processed: Re: Bug#904742 closed by Martin (jp: name conflict of /usr/bin/jp with sat-xmpp-jp)

2022-02-23 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.1.3-2 Bug #904742 {Done: Martin } [jp] jp: name conflict of /usr/bin/jp with sat-xmpp-jp Bug #954443 {Done: Martin } [jp] jp: name conflict of /usr/bin/jp with sat-xmpp-jp Marked as found in versions jp/0.1.3-2 and reopened. Marked as found in versions

Bug#904742: closed by Martin (jp: name conflict of /usr/bin/jp with sat-xmpp-jp)

2022-02-23 Thread Andreas Beckmann
Control: found -1 0.1.3-2 On 22/02/2022 15.21, Debian Bug Tracking System wrote: The program jp (package sat-xmpp-jp) has been renamed to libervia-cli (package libervia-cli). Problem solved. Not completely. Now jp needs to add Breaks+Replaces: sat-xmpp-jp (<< 0.8.0-1) to ensure smooth

Bug#1005311: forcing dependency is not enough, at least for optirun

2022-02-23 Thread Aniol Martí
On Mon, 14 Feb 2022 20:31:33 +0100 Gianluigi Tiesi wrote: optirun glxinfo optirun glxinfo [ 1566.529702] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Unable to locate/open config directory: "/etc/bumblebee/xorg.conf.d" [ 1566.529735] [ERROR]Aborting because fallback start is

Bug#1006312: appstream-compose: missing Breaks+Replaces: appstream (<< 0.15.2)

2022-02-23 Thread Andreas Beckmann
Package: appstream-compose Version: 0.15.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite

Bug#891224: occurs in bullseye release

2022-02-23 Thread Moritz Schlarb
Dear Hamish, can you please send us more information on your setup? E.g. the output of: apache2ctl -M and dpkg -l *apache* Thanks, Moritz On 17.01.22 00:55, Hamish Moffatt wrote: I'm seeing this in bullseye with a brand new apache install. Every graceful restart (apache2ctl graceful) causes

Bug#1006308: closed by Debian FTP Masters (reply to Mark Hindley ) (Bug#1006308: fixed in seatd 0.6.4-1)

2022-02-23 Thread Mark Hindley
Salvatore, On Wed, Feb 23, 2022 at 10:14:59AM +0100, Salvatore Bonaccorso wrote: > Thanks for the quick fix! > > Note there is a typo in the CVE, should have been CVE-2022-25643. Evidently too quick! Thanks for pointing it out. Would you prefer a new upload to fix it now or wait for the next

Bug#1006308: closed by Debian FTP Masters (reply to Mark Hindley ) (Bug#1006308: fixed in seatd 0.6.4-1)

2022-02-23 Thread Salvatore Bonaccorso
Hi Mark, On Wed, Feb 23, 2022 at 09:09:05AM +, Debian Bug Tracking System wrote: > Format: 1.8 > Date: Wed, 23 Feb 2022 08:09:56 + > Source: seatd > Architecture: source > Version: 0.6.4-1 > Distribution: unstable > Urgency: high > Maintainer: Mark Hindley > Changed-By: Mark Hindley >

Bug#1006308: marked as done (seatd-launch: CVE-2022-25643)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 09:06:32 + with message-id and subject line Bug#1006308: fixed in seatd 0.6.4-1 has caused the Debian Bug report #1006308, regarding seatd-launch: CVE-2022-25643 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1002445: marked as done (shortuuid: FTBFS: AssertionError: Requires Python v3.5 or above.)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 08:49:29 + with message-id and subject line Bug#1002445: fixed in shortuuid 1.0.8-1 has caused the Debian Bug report #1002445, regarding shortuuid: FTBFS: AssertionError: Requires Python v3.5 or above. to be marked as done. This means that you claim that

Bug#1006289: marked as done (marisa's autopkgtest regressed since rebuild for ruby3.0 as default)

2022-02-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Feb 2022 08:34:49 + with message-id and subject line Bug#1006289: fixed in marisa 0.2.6-9 has caused the Debian Bug report #1006289, regarding marisa's autopkgtest regressed since rebuild for ruby3.0 as default to be marked as done. This means that you claim that

Processed: bug #997338: forwarded to upstream PR

2022-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 997338 https://github.com/yasm/yasm/pull/178 Bug #997338 [src:yasm] yasm: FTBFS: configure: error: Standard (ANSI/ISO C89) header files are required. Set Bug forwarded-to-address to 'https://github.com/yasm/yasm/pull/178'. > --

Bug#1002445: About shortuuid (was: FTBFS: AssertionError...)

2022-02-23 Thread Martin
On 2022-02-23 12:30, Kouhei Maeda wrote: > I'm sorry. No need to by sorry - we're all volunteers :-) > Please go ahead. Thank you, will do!