Bug#1005497: marked as done (bpftrace: FTBFS: CheckIncludeFile.c:1:10: fatal error: sys/sdt.h: No such file or directory)

Your message dated Tue, 22 Feb 2022 07:33:47 + with message-id and subject line Bug#1005497: fixed in bpftrace 0.14.1-2 has caused the Debian Bug report #1005497, regarding bpftrace: FTBFS: CheckIncludeFile.c:1:10: fatal error: sys/sdt.h: No such file or directory to be marked as done. This

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 1002721 important Bug #1002721 [okular] okular: segfaults when trying to open a signed PDF Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1002721: https://bugs.de

Bug#1006131: rus-ispell: please stop build-depending on myspell-tools

Hello Agustin, On 21 Feb 2022, at 23:46, Agustin Martin wrote: >> Could you show me the difference? > Find attached diff. SInce flags are sorted differently by i2myspell > and ispellaff2myspell , I made some magic for easier check of result, > actually diffing sorted affix files. This is what le

Bug#1002721: okular: segfaults when trying to open a signed PDF

Control: 1002721 severity important thanks Hi Pablo, can you point to a PDF document available on the web that causes Okular to segfault for you such that I can try to reproduce it ? -- Med vänliga hälsningar Patrick Franz

Bug#1006258: rstudio crashes

Package: rstudio Version: 2022.02.0+443 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: l...@castermans.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upon crash a white s

Processed: limit source to git-remote-hg, tagging 1006038, tagging 826002

Processing commands for cont...@bugs.debian.org: > limit source git-remote-hg Limiting to bugs with field 'source' containing at least one of 'git-remote-hg' Limit currently set to 'source':'git-remote-hg' > tags 1006038 + pending Bug #1006038 [src:git-remote-hg] git-remote-hg: FTBFS: dh_auto_tes

Bug#971207: marked as done (rust-inotify-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 1)

Your message dated Mon, 21 Feb 2022 20:33:50 -0500 with message-id <20220222013350.esvnlz5h6ash2ser@localhost> and subject line Re: Bug#971207: rust-inotify-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 1 has caused the Debian Bug report #971207, regardi

Bug#1006039: pytest-xdist: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

On Sat, 19 Feb 2022, Lucas Nussbaum wrote: === FAILURES === _ test_internal_errors_propagate_to_controller _ pytester = def test_internal_errors_propagate_to_controller(pytester: pytest.Pyteste

Processed: Bug#1006141 marked as pending in supertuxkart

Processing control commands: > tag -1 pending Bug #1006141 [src:supertuxkart] supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}' Added tag(s) pending. -- 1006141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006141 Debian Bug Tracking

Bug#1006141: marked as pending in supertuxkart

Control: tag -1 pending Hello, Bug #1006141 in supertuxkart 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/games-team/supertuxkart/-/commit/ab93bba3a2a988c0c5a

Bug#1006196: marked as done (mozjs91: FTBFS on mipsel (eller): non262/regress/regress-303213.js: out of memory)

Your message dated Tue, 22 Feb 2022 00:19:26 + with message-id and subject line Bug#1006196: fixed in mozjs91 91.6.0-2 has caused the Debian Bug report #1006196, regarding mozjs91: FTBFS on mipsel (eller): non262/regress/regress-303213.js: out of memory to be marked as done. This means that

Bug#1006066: marked as done (hg-git: FTBFS: ERROR: test-hg-tags.t output changed)

Your message dated Mon, 21 Feb 2022 23:19:29 + with message-id and subject line Bug#1006066: fixed in hg-git 0.10.4-2 has caused the Debian Bug report #1006066, regarding hg-git: FTBFS: ERROR: test-hg-tags.t output changed to be marked as done. This means that you claim that the problem has b

Bug#1006066: marked as pending in hg-git

Control: tag -1 pending Hello, Bug #1006066 in hg-git 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/packages/hg-git/-/commit/4775ea6b0ec64190df8e3

Processed: Bug#1006066 marked as pending in hg-git

Processing control commands: > tag -1 pending Bug #1006066 [src:hg-git] hg-git: FTBFS: ERROR: test-hg-tags.t output changed Added tag(s) pending. -- 1006066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1006131: rus-ispell: please stop build-depending on myspell-tools

El lun, 21 feb 2022 a las 23:26, Mikhail Gusarov () escribió: > > Hello Agustin, > > On 21 Feb 2022, at 23:12, Agustin Martin wrote: > > I am thinking about using ispellaff2myspell --bylocale flag with > russian koi8-r locale set. This should only require an extra¡ > build-dep on locales-all and ch

Bug#1006131: rus-ispell: please stop build-depending on myspell-tools

Hello Agustin, On 21 Feb 2022, at 23:12, Agustin Martin wrote: > I am thinking about using ispellaff2myspell --bylocale flag with > russian koi8-r locale set. This should only require an extra¡ > build-dep on locales-all and change myspell-tools to hunspell-tools. I > am checking the result and o

Bug#1006131: rus-ispell: please stop build-depending on myspell-tools

El sáb, 19 feb 2022 a las 17:39, Mattia Rizzolo () escribió: > > Source: rus-ispell > Version: 0.99g5-27 > Severity: serious > > Dear maintainer, > > we plan to remove src:myspell really soon, and together with it also > the package "myspell-tools". > Your package still depends on it. Hi, thanks f

Processed: Bug#1006196 marked as pending in mozjs

Processing control commands: > tag -1 pending Bug #1006196 [src:mozjs91] mozjs91: FTBFS on mipsel (eller): non262/regress/regress-303213.js: out of memory Added tag(s) pending. -- 1006196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006196 Debian Bug Tracking System Contact ow...@bugs.de

Bug#1006196: marked as pending in mozjs

Control: tag -1 pending Hello, Bug #1006196 in mozjs 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/mozjs/-/commit/c946e40f44ce08286173a514400b458df

Bug#1005559: marked as done (gtranslator: FTBFS: ../data/meson.build:15:5: ERROR: Function does not take positional arguments.)

Your message dated Mon, 21 Feb 2022 21:34:25 + with message-id and subject line Bug#1005559: fixed in gtranslator 41.0-1 has caused the Debian Bug report #1005559, regarding gtranslator: FTBFS: ../data/meson.build:15:5: ERROR: Function does not take positional arguments. to be marked as done.

Processed: bug 1006009 is forwarded to https://bugs.chromium.org/p/webp/issues/detail?id=558, tagging 1006009

Processing commands for cont...@bugs.debian.org: > forwarded 1006009 https://bugs.chromium.org/p/webp/issues/detail?id=558 Bug #1006009 [libwebp7] qtimageformats-opensource-src: FTBFS on mipsel: test failure Set Bug forwarded-to-address to 'https://bugs.chromium.org/p/webp/issues/detail?id=558'.

Bug#961147: libcolor-calc-perl: broken by new libgraphics-colornames-perl

-=| intrigeri, 22.05.2020 08:47:25 +0200 |=- > Hi, > > Niko Tyni (2020-05-21): > > So IMO we should either to package Graphics::ColorNames::HTML even though > > it's deprecated, or drop Color::Calc from Debian. > > > libcolor-calc-perl has just one reverse dependency AFAICS: > > libcgi-applicatio

Processed: Bug#1005559 marked as pending in gtranslator

Processing control commands: > tag -1 pending Bug #1005559 [src:gtranslator] gtranslator: FTBFS: ../data/meson.build:15:5: ERROR: Function does not take positional arguments. Added tag(s) pending. -- 1005559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005559 Debian Bug Tracking System C

Bug#1005559: marked as pending in gtranslator

Control: tag -1 pending Hello, Bug #1005559 in gtranslator 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/gtranslator/-/commit/68aaa88141df731b576e8

Bug#1006009: qtimageformats-opensource-src: FTBFS on mipsel: test failure

On 2022-02-20 18:33:22, Dmitry Shachnev wrote: > Control: reassign -1 libwebp7 1.2.1-7 > Control: affects -1 src:qtimageformats-opensource-src > > Hi Sebastian and libwebp maintainers! > > On Fri, Feb 18, 2022 at 10:39:23PM +0100, Sebastian Ramacher wrote: > > Source: qtimageformats-opensource-sr

Bug#1003470: openimageio FTBFS: invalid preprocessing directive #errorDCMTK

Hi Jeremy! Il lun 21 feb 2022, 03:57 Jeremy Bicha ha scritto: > In Ubuntu, we fixed this issue by building with C++17. > > You can find a diff of the rules file at > https://launchpad.net/ubuntu/+source/openimageio/2.2.18.0+dfsg-1ubuntu >

Bug#1005947: marked as done (ignition-math: FTBFS on armel and mipsel)

Your message dated Mon, 21 Feb 2022 20:38:33 + with message-id and subject line Bug#1005947: fixed in ignition-math 6.10.0+ds3-3 has caused the Debian Bug report #1005947, regarding ignition-math: FTBFS on armel and mipsel to be marked as done. This means that you claim that the problem has b

Bug#1006219: new expat causes regressions in the python autopkg tests

On 2/21/22 21:31, Salvatore Bonaccorso wrote: > Control: forwarded -1 https://bugs.python.org/issue46811 > Control: affects -1 + src:expat > Control: clone -1 -2 -3 > Control: reassign -1 src:python3.10 3.10.2-1 > Control: reassign -2 src:python3.9 3.9.10-1 > Control: reassign -3 src:python2.7 2.7.

Processed: Re: Bug#1006219: new expat causes regressions in the python autopkg tests

Processing control commands: > forwarded -1 https://bugs.python.org/issue46811 Bug #1006219 [src:expat] new expat causes regressions in the python autopkg tests Set Bug forwarded-to-address to 'https://bugs.python.org/issue46811'. > affects -1 + src:expat Bug #1006219 [src:expat] new expat causes

Bug#1006219: new expat causes regressions in the python autopkg tests

Control: forwarded -1 https://bugs.python.org/issue46811 Control: affects -1 + src:expat Control: clone -1 -2 -3 Control: reassign -1 src:python3.10 3.10.2-1 Control: reassign -2 src:python3.9 3.9.10-1 Control: reassign -3 src:python2.7 2.7.18-12 Hi László, hi Matthias, On Mon, Feb 21, 2022 at 08

Bug#1006152: mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js

Control: severity -1 important On Mon, 21 Feb 2022 at 00:15:41 +, Simon McVittie wrote: > I'm testing a patch (basically just extending Marco's workaround to > apply to i386 too). If successful, I'll downgrade the severity of this bug > but leave it open. Looks like this worked. smcv

Processed: Re: Bug#1006152: mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js

Processing control commands: > severity -1 important Bug #1006152 [src:mozjs91] mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js Severity set to 'important' from 'serious' -- 1006152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006152 Debian Bug Tracking System C

Bug#1006219: new expat causes regressions in the python autopkg tests

Hi, On Mon, Feb 21, 2022 at 05:10:02PM +0100, László Böszörményi wrote: > Control: tags -1 +confirmed > > Hi Matthias, > > On Mon, Feb 21, 2022 at 2:57 PM Matthias Klose wrote: > > The new expat causes regressions in the python autopkg tests. I also see > > there > > is a new upstream 2.4.6. D

Bug#990201: CVE-2021-33622 (was: Re: Accepted singularity-container 3.9.5+ds1-1 (source) into experimental)

Hi again as well, On Tue, Feb 22, 2022 at 12:44:49AM +0530, Nilesh Patra wrote: > Hi again, > > On Mon, 21 Feb 2022 01:03:13 +0530 Nilesh Patra wrote: > > > So where has this issue bin fixed? > > > > But yes, you are right, even at Mitre metadata, I do not find any > > information > > about an

Bug#1005889: marked as done (dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test)

Your message dated Mon, 21 Feb 2022 19:33:50 + with message-id and subject line Bug#1005889: fixed in dbus 1.13.20-2 has caused the Debian Bug report #1005889, regarding dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test to be marked as done. This means that you

Bug#990201: CVE-2021-33622 (was: Re: Accepted singularity-container 3.9.5+ds1-1 (source) into experimental)

Hi again, On Mon, 21 Feb 2022 01:03:13 +0530 Nilesh Patra wrote: > > So where has this issue bin fixed? > > But yes, you are right, even at Mitre metadata, I do not find any information > about any patch for the bug; i.e. I do not see the "code" that fixes it, and > hence > I too am skeptical w

Bug#1005889: dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test

Hi Simon, On 21-02-2022 12:10, Simon McVittie wrote: Is there anything unusual about the ppc64el CI-runners compared with other architectures? (For example: lots of CPUs, few CPUs, lots of RAM, less RAM, lots of I/O bandwidth, running on tmpfs, using qemu, using lxc, running many tests in parall

Bug#1005250: marked as done (r-cran-rlang breaks r-cran-tidyselect autopkgtest: catch_cnd(vars_select(letters, starts_with("1"))) inherits from `'lifecycle_soft_deprecated'/'condition'` not `'characte

Your message dated Mon, 21 Feb 2022 18:22:58 + with message-id and subject line Bug#1005250: fixed in r-cran-tidyselect 1.1.2+dfsg-1 has caused the Debian Bug report #1005250, regarding r-cran-rlang breaks r-cran-tidyselect autopkgtest: catch_cnd(vars_select(letters, starts_with("1"))) inheri

Processed: reassign

Processing commands for cont...@bugs.debian.org: > reassign 1005250 r-cran-tidyselect 1.1.1+dfsg-1 Bug #1005250 [src:r-cran-rlang, src:r-cran-tidyselect] r-cran-rlang breaks r-cran-tidyselect autopkgtest: catch_cnd(vars_select(letters, starts_with("1"))) inherits from `'lifecycle_soft_deprecated

Bug#1006231: puppet: FTBFS with ruby 3.0: fileutils.rb:865:in `install': wrong number of arguments (given 3, expected 2) (ArgumentError)

Source: puppet Version: 6.16.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, puppet/experimental recently started to FTBFS. This seems to have been cuased by a recent change to a build dependency as a previous build attempt on Jan 12 was still successful. fakeroo

Bug#997637: marked as done (python-oauth: FTBFS: error in oauth setup command: use_2to3 is invalid.)

Your message dated Mon, 21 Feb 2022 17:43:58 + with message-id and subject line Bug#1006229: Removed package(s) from unstable has caused the Debian Bug report #997637, regarding python-oauth: FTBFS: error in oauth setup command: use_2to3 is invalid. to be marked as done. This means that you

Bug#1005653: (no subject)

maybe https://github.com/Nheko-Reborn/nheko/commit/b439e1fa41b26db5f1d0d16bd1da664338b435e7 fixes the bug, which is included in version 0.9.1 There is plans to package nheko 0.9.1 ?

Bug#1006024: marked as done (ignition-fuel-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)

Your message dated Mon, 21 Feb 2022 16:50:26 + with message-id and subject line Bug#1006024: fixed in ignition-fuel-tools 7.0.0+ds-3 has caused the Debian Bug report #1006024, regarding ignition-fuel-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose

Bug#1004299: marked as done (ruby-net-ssh: FTBFS in sid)

Your message dated Mon, 21 Feb 2022 16:20:48 + with message-id and subject line Bug#1004299: fixed in ruby-net-ssh 1:6.1.0-3 has caused the Debian Bug report #1004299, regarding ruby-net-ssh: FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1000230: marked as done (screenruler fails to start)

Your message dated Mon, 21 Feb 2022 16:21:02 + with message-id and subject line Bug#1000230: fixed in screenruler 1.0-2 has caused the Debian Bug report #1000230, regarding screenruler fails to start to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1006219: new expat causes regressions in the python autopkg tests

Control: tags -1 +confirmed Hi Matthias, On Mon, Feb 21, 2022 at 2:57 PM Matthias Klose wrote: > The new expat causes regressions in the python autopkg tests. I also see there > is a new upstream 2.4.6. Didn't check that yet. Basically 2.4.5-2 and 2.4.6 should be identical. I can package the la

Processed: Re: Bug#1006219: new expat causes regressions in the python autopkg tests

Processing control commands: > tags -1 +confirmed Bug #1006219 [src:expat] new expat causes regressions in the python autopkg tests Added tag(s) confirmed. -- 1006219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem

Bug#1004299: marked as pending in ruby-net-ssh

Control: tag -1 pending Hello, Bug #1004299 in ruby-net-ssh 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/ruby-net-ssh/-/commit/53d8aef71be98897919b

Processed: Bug#1004299 marked as pending in ruby-net-ssh

Processing control commands: > tag -1 pending Bug #1004299 [ruby-net-ssh] ruby-net-ssh: FTBFS in sid Added tag(s) pending. -- 1004299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1006220: marked as done (pytest & pyflake broken in unstable)

Your message dated Mon, 21 Feb 2022 15:42:41 + with message-id and subject line Bug#1006220: fixed in pycodestyle 2.8.0-2 has caused the Debian Bug report #1006220, regarding pytest & pyflake broken in unstable to be marked as done. This means that you claim that the problem has been dealt wi

Processed: Bug#1004556: fix doesn't seem to be sufficient

Processing commands for cont...@bugs.debian.org: > reopen 1004556 Bug #1004556 {Done: Alastair McKinstry } [libmpich-dev] libmpich-dev: The simplest MPI program compiled with mpich crashes 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared,

Bug#1006218: marked as done (csound-plugins: missing Breaks+Replaces: libcsound64-6.0 (<< 1:6.17))

Your message dated Mon, 21 Feb 2022 15:18:55 + with message-id and subject line Bug#1006218: fixed in csound-plugins 1.0.2~dfsg1-1 has caused the Debian Bug report #1006218, regarding csound-plugins: missing Breaks+Replaces: libcsound64-6.0 (<< 1:6.17) to be marked as done. This means that yo

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 1006220 pycodestyle 2.8.0-1 Bug #1006220 [src:python-flake8] pytest & pyflake broken in unstable Bug reassigned from package 'src:python-flake8' to 'pycodestyle'. No longer marked as found in versions python-flake8/4.0.1-1. Ignoring reque

Bug#1005889: marked as done (dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test)

Your message dated Mon, 21 Feb 2022 14:34:15 + with message-id and subject line Bug#1005889: fixed in dbus 1.12.20-4 has caused the Debian Bug report #1005889, regarding dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test to be marked as done. This means that you

Bug#1004556: fix doesn't seem to be sufficient

Dear maintainer, I've tried the same test with mpich 4.0-2 and still see the same behaviour. The issue doesn't seem fixed on my side. Is there anything else I should wait for beyond mpich/libmpich-dev? Best, Julien signature.asc Description: This is a digitally signed message part.

Bug#1005889: marked as pending in dbus

Control: tag -1 pending Hello, Bug #1005889 in dbus 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/utopia-team/dbus/-/commit/ef8ec838feeb2ea922d1ea40e93f15c2f2

Processed: Bug#1005889 marked as pending in dbus

Processing control commands: > tag -1 pending Bug #1005889 [src:dbus] dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test Added tag(s) pending. -- 1005889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005889 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#1006220: pytest & pyflake broken in unstable

Package: src:python-flake8 Version: 4.0.1-1 Severity: serious Tags: sid bookworm Seen in the last test rebuild, e.g.: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006032 if there are incompatible versions of flake and pytest, it should be expressed by Dependencies/Breaks in these packages.

Bug#1006214: [Pkg-javascript-devel] Bug#1006205: node-md5-hex: ships files already provided by node-blueimp-md5

Quoting Andreas Beckmann (2022-02-21 13:55:20) > node-blueimp-md5 was only recently uploaded to the archive. Therefore > node-md5-hex needs to stop bundling it and use the separately packaged > node-blueimp-md5 instead. > > node-blueimp-md5 needs Breaks+Replaces against node-md5-hex versions >

Bug#1006219: new expat causes regressions in the python autopkg tests

Package: src:expat Version: 2.4.5-2 Severity: serious Tags: sid bookworm The new expat causes regressions in the python autopkg tests. I also see there is a new upstream 2.4.6. Didn't check that yet. See https://tracker.debian.org/pkg/expat

Bug#1006218: csound-plugins: missing Breaks+Replaces: libcsound64-6.0 (<< 1:6.17)

Package: csound-plugins Version: 1.0.2~dfsg1-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails beca

Bug#1006205: marked as done (node-md5-hex: ships files already provided by node-blueimp-md5)

Your message dated Mon, 21 Feb 2022 13:34:09 + with message-id and subject line Bug#1006205: fixed in node-md5-hex 4.0.0-1 has caused the Debian Bug report #1006205, regarding node-md5-hex: ships files already provided by node-blueimp-md5 to be marked as done. This means that you claim that t

Processed: Bug#1006205 marked as pending in node-md5-hex

Processing control commands: > tag -1 pending Bug #1006205 [node-md5-hex] node-md5-hex: ships files already provided by node-blueimp-md5 Added tag(s) pending. -- 1006205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006205 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#1006205: marked as pending in node-md5-hex

Control: tag -1 pending Hello, Bug #1006205 in node-md5-hex 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-md5-hex/-/commit/cfb7ab60df234eceb04120

Bug#1006205: [Pkg-javascript-devel] Processed: reassign 1006205 to node-blueimp-md5

On 21/02/2022 14:00, Jonas Smedegaard wrote: Control: reassign 1006205 node-md5-hex Quoting Debian Bug Tracking System (2022-02-21 13:27:11) reassign 1006205 node-blueimp-md5 No, it is not a bug for node-blueimp-md5 to provide blueimp-md5! Oups sorry, I inverted debian/watch files

Processed: Re: [Pkg-javascript-devel] Processed: reassign 1006205 to node-blueimp-md5

Processing control commands: > reassign 1006205 node-md5-hex Bug #1006205 [node-md5-hex] node-md5-hex: ships files already provided by node-blueimp-md5 Ignoring request to reassign bug #1006205 to the same package -- 1006205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006205 Debian Bug

Bug#1006205: [Pkg-javascript-devel] Processed: reassign 1006205 to node-blueimp-md5

Control: reassign 1006205 node-md5-hex Quoting Debian Bug Tracking System (2022-02-21 13:27:11) > reassign 1006205 node-blueimp-md5 No, it is not a bug for node-blueimp-md5 to provide blueimp-md5! It is a bug in node-md5-hex to embed blueimp-md5 without coordination at bug#867290, causing waste

Processed: Re: node-md5-hex: ships files already provided by node-blueimp-md5

Processing control commands: > clone -1 -2 Bug #1006205 [node-blueimp-md5] node-md5-hex: ships files already provided by node-blueimp-md5 Bug 1006205 cloned as bug 1006214 > found -2 2.19.0~ds-2 Bug #1006214 [node-blueimp-md5] node-md5-hex: ships files already provided by node-blueimp-md5 Marked

Bug#1006205: node-md5-hex: ships files already provided by node-blueimp-md5

Followup-For: Bug #1006205 Control: clone -1 -2 Control: found -2 2.19.0~ds-2 Control: retitle -2 node-blueimp-md5: missing Breaks+Replaces: node-md5-hex (<< 3.0.1+~2.19.0-2~) Control: reassign -1 node-md5-hex 3.0.1+~2.19.0-1 node-blueimp-md5 was only recently uploaded to the archive. Therefore n

Bug#1004253: marked as done (broken for BIND in stable)

Your message dated Mon, 21 Feb 2022 13:47:00 +0100 with message-id and subject line Re: Bug#1004253: broken for BIND in stable has caused the Debian Bug report #1004253, regarding broken for BIND in stable to be marked as done. This means that you claim that the problem has been dealt with. If th

Processed: reassign 1006205 to node-blueimp-md5

Processing commands for cont...@bugs.debian.org: > reassign 1006205 node-blueimp-md5 Bug #1006205 [node-md5-hex] node-md5-hex: ships files already provided by node-blueimp-md5 Bug reassigned from package 'node-md5-hex' to 'node-blueimp-md5'. No longer marked as found in versions node-md5-hex/3.0.

Bug#1006172: [Pkg-electronics-devel] Bug#1006172: src:lepton-eda: fails to migrate to testing for too long: FTBFS on s390x

Hi Bdale, On 21-02-2022 05:01, Bdale Garbee wrote: Your package fails to build on s390x where it build successfully in the past. I've X-Debbugs-CC-ed the s390x porters to help you understand why only this architecture is affected. It's hard to imagine anyone actually trying to use lepton-eda o

Bug#1005889: dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test

On Wed, 16 Feb 2022 at 21:15:16 +0100, Paul Gevers wrote: > I looked at the results of the autopkgtest of you package on ppc64el because > it was showing up as a regression for the upload of glibc. I noticed that > the test regularly fails since the beginning of February this year. The > failure is

Bug#1006205: node-md5-hex: ships files already provided by node-blueimp-md5

Package: node-md5-hex Version: 3.0.1+~2.19.0-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 overwrit

Bug#1002445: ITA: shortuuid -- generates concise, unambiguous, URL-safe UUIDs for Python 3

A work in progress can be found at https://salsa.debian.org/python-team/packages/shortuuid If there are no objections, I'll upload this week.

Bug#1006204: pypy-pyparsing2: missing Breaks+Replaces: pypy-pyparsing (<< 2.4.7-3)

Package: pypy-pyparsing2 Version: 2.4.7-3 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 oth

Processed: Debian bugs: #1006116, #1005737, #1005817, #1005736

Processing commands for cont...@bugs.debian.org: > tags 1005736 + pending Bug #1005736 [sane-utils] sane-umax_pp(5) does not describe umax_pp command-line utility Added tag(s) pending. > tags 1005817 + pending Bug #1005817 [libsane1] Please recommend sane-airscan Added tag(s) pending. > tags 1005

Bug#1006044: marked as done (alembic: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)

Your message dated Mon, 21 Feb 2022 10:18:44 + with message-id and subject line Bug#1006044: fixed in alembic 1.7.6-1 has caused the Debian Bug report #1006044, regarding alembic: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 t

Bug#1006044: marked as pending in alembic

Control: tag -1 pending Hello, Bug #1006044 in alembic 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/packages/alembic/-/commit/da032d9238065e6b7a8

Bug#1006143: marked as done (kas: autopkgtest regression: ModuleNotFoundError: No module named 'snack')

Your message dated Mon, 21 Feb 2022 10:05:03 + with message-id and subject line Bug#1006143: fixed in kas 2.6.3-2 has caused the Debian Bug report #1006143, regarding kas: autopkgtest regression: ModuleNotFoundError: No module named 'snack' to be marked as done. This means that you claim tha

Processed: Bug#1006044 marked as pending in alembic

Processing control commands: > tag -1 pending Bug #1006044 [src:alembic] alembic: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. -- 1006044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006044 Debian Bu

Bug#1005230: Does chromium REALLY need fuse now?

Trent W. Buck wrote: > As at chromium 98.0.4758.102-1~deb11u1, > chromium works with xdg-desktop-portal, fuse, flatpak removed. As at chromium 98.0.4758.102-1~deb11u1, I can reproduce the original "Trace/breakpoint trap" in sway, without removing anything. i.e. I don't think xdg-desktop-portal he

Bug#998091: Please remove from Debian sid and experimental

Hi, libclc was merged into upstream llvm and is provided by llvm-toolchain-XX Debian packages (since llvm-toolchain-12 1:12.0.0-3). libclc Debian source package should be removed from sid and experimental (already removed from bookworm). Thanks.

Processed: 1004855 severity

Processing commands for cont...@bugs.debian.org: > severity 1004855 important Bug #1004855 [python3-ipykernel] python3-ipykernel: missing dependency on debugpy Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 100

Bug#1005404: marked as done (Kernel modules fail to build with Linux 5.16 onward)

Your message dated Mon, 21 Feb 2022 09:19:02 + with message-id and subject line Bug#1005404: fixed in openafs 1.8.8.1-1 has caused the Debian Bug report #1005404, regarding Kernel modules fail to build with Linux 5.16 onward to be marked as done. This means that you claim that the problem has

Processed: ITA: shortuuid -- generates concise, unambiguous, URL-safe UUIDs for Python3

Processing control commands: > affects -1 src:shortuuid Bug #1002445 [src:shortuuid] shortuuid: FTBFS: AssertionError: Requires Python v3.5 or above. Added indication that 1002445 affects src:shortuuid -- 1002445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002445 Debian Bug Tracking Sys

Bug#1002445: ITA: shortuuid -- generates concise, unambiguous, URL-safe UUIDs for Python3

Package: wnpp Control: affects -1 src:shortuuid X-Debbugs-Cc: team+pyt...@tracker.debian.org It seems, that the current maintainer of shortuuid is either not active anymore or just busy. Therefore, I like to move the package to the Python team, keeping the current maintainer as uploader.