Bug#1019420: marked as done (xfce4-pulseaudio-plugin volume icon flickers)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Sat, 01 Oct 2022 04:22:14 + with message-id and subject line Bug#1019420: fixed in xfce4-pulseaudio-plugin 0.4.5-1 has caused the Debian Bug report #1019420, regarding xfce4-pulseaudio-plugin volume icon flickers to be marked as done. This means that you claim that the

Bug#1021015: marked as done (tinyproxy: CVE-2022-40468)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Sat, 01 Oct 2022 02:36:02 + with message-id and subject line Bug#1021015: fixed in tinyproxy 1.11.1-2 has caused the Debian Bug report #1021015, regarding tinyproxy: CVE-2022-40468 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#990004: marked as done (support aliases by default or manual for suite names)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Sat, 1 Oct 2022 01:53:21 +0200 with message-id and subject line Re: support aliases by default or manual for suite names has caused the Debian Bug report #990004, regarding support aliases by default or manual for suite names to be marked as done. This means that you claim

Bug#978703: marked as done (gives strange error messages on outdated images)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Sat, 1 Oct 2022 01:50:23 +0200 with message-id and subject line Re: Bug#978703: gives strange error messages on outdated images has caused the Debian Bug report #978703, regarding gives strange error messages on outdated images to be marked as done. This means that you claim

Bug#1008422: marked as done (jupyter-notebook: FTBFS: Module not found: Error: Can't resolve './../../../buffer' in '/<>/node_modules/postcss/lib')

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 23:51:01 + with message-id and subject line Bug#1008422: fixed in jupyter-notebook 6.4.12-2 has caused the Debian Bug report #1008422, regarding jupyter-notebook: FTBFS: Module not found: Error: Can't resolve './../../../buffer' in

Processed: your mail

2022-09-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1013005 Bug #1013005 [src:onednn] onednn: ftbfs with GCC-12 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1013005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013005 Debian Bug

Bug#1014317: marked as done (ITP: yarsync -- file synchronization and backup tool)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 23:10:09 + with message-id and subject line Bug#1014317: fixed in yarsync 0.1.1+deb-1 has caused the Debian Bug report #1014317, regarding ITP: yarsync -- file synchronization and backup tool to be marked as done. This means that you claim that the problem

Bug#1020967: marked as done (New upstream version 5.1.2)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 22:25:00 + with message-id and subject line Bug#1020967: fixed in nuspell 5.1.2-1 has caused the Debian Bug report #1020967, regarding New upstream version 5.1.2 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#997252: marked as done (qt-gstreamer: FTBFS: gatomic.h:113:19: error: argument 2 of ‘__atomic_load’ must not be a pointer to a ‘volatile’ type)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 22:25:08 + with message-id and subject line Bug#997252: fixed in qt-gstreamer 1.2.0-5.2 has caused the Debian Bug report #997252, regarding qt-gstreamer: FTBFS: gatomic.h:113:19: error: argument 2 of ‘__atomic_load’ must not be a pointer to a ‘volatile’

Bug#906882: marked as done (libqt5gstreamer-dev: pkg-config fails unless libgstreamer-plugins-base1.0-dev is also installed)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 22:25:08 + with message-id and subject line Bug#906882: fixed in qt-gstreamer 1.2.0-5.2 has caused the Debian Bug report #906882, regarding libqt5gstreamer-dev: pkg-config fails unless libgstreamer-plugins-base1.0-dev is also installed to be marked as

Bug#1021029: marked as done (src:rust-resource-proof: fails to migrate to testing for too long: autopkgtest regression)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 22:25:17 + with message-id and subject line Bug#1021029: fixed in rust-resource-proof 1.0.39-3 has caused the Debian Bug report #1021029, regarding src:rust-resource-proof: fails to migrate to testing for too long: autopkgtest regression to be marked as

Bug#1016254: marked as done (lomiri-url-dispatcher: FTBFS: overlay-tracker-mir.cpp:95:45: error: variable ‘std::array urls’ has initializer but incomplete type)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 22:24:47 + with message-id and subject line Bug#1016254: fixed in lomiri-url-dispatcher 0.1.0-8 has caused the Debian Bug report #1016254, regarding lomiri-url-dispatcher: FTBFS: overlay-tracker-mir.cpp:95:45: error: variable ‘std::array urls’ has

Bug#1015783: marked as done (Please update jupyter-notebook to 6.4.12)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 20:39:42 + with message-id and subject line Bug#1015783: fixed in jupyter-notebook 6.4.12-1 has caused the Debian Bug report #1015783, regarding Please update jupyter-notebook to 6.4.12 to be marked as done. This means that you claim that the problem has

Bug#1014771: marked as done (jupyter-notebook: CVE-2022-24758)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 20:39:42 + with message-id and subject line Bug#1014771: fixed in jupyter-notebook 6.4.12-1 has caused the Debian Bug report #1014771, regarding jupyter-notebook: CVE-2022-24758 to be marked as done. This means that you claim that the problem has been

Bug#1013272: marked as done (jupyter-notebook: CVE-2022-29238)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 20:39:42 + with message-id and subject line Bug#1013272: fixed in jupyter-notebook 6.4.12-1 has caused the Debian Bug report #1013272, regarding jupyter-notebook: CVE-2022-29238 to be marked as done. This means that you claim that the problem has been

Bug#1007960: marked as done (RFP: pedidos de empacotamento)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 22:29:45 +0200 with message-id <20220930202945.gfg3k4q4bzl2c...@jwilk.net> and subject line Re: Bug#1007960: RFP: signal-desktop has caused the Debian Bug report #1007960, regarding RFP: pedidos de empacotamento to be marked as done. This means that you claim

Bug#1018777: marked as done (pari-nflistdata: Unhandled data compression by dh_compress)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 19:43:54 +0200 with message-id and subject line Re: Bug#1018777: pari-nflistdata: Unhandled data compression by dh_compress has caused the Debian Bug report #1018777, regarding pari-nflistdata: Unhandled data compression by dh_compress to be marked as done.

Bug#1017220: marked as done (camitk: FTBFS: unsatisfiable build-dependencies)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 19:50:36 + with message-id and subject line Bug#1017220: fixed in camitk 5.0.2-4 has caused the Debian Bug report #1017220, regarding camitk: FTBFS: unsatisfiable build-dependencies to be marked as done. This means that you claim that the problem has been

Bug#1013040: marked as done (sleef: ftbfs with GCC-12)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 19:34:17 + with message-id and subject line Bug#1013040: fixed in sleef 3.5.1-2 has caused the Debian Bug report #1013040, regarding sleef: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#840266: marked as done (no CHANGES file)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 20:36:06 +0200 with message-id <87tu4ok8vd@hands.com> and subject line text in question no longer present in manual has caused the Debian Bug report #840266, regarding no CHANGES file to be marked as done. This means that you claim that the problem has been

Bug#564260: marked as done (perltidy (-pbp) desalign hashes in given-when construct)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 20:18:00 +0200 with message-id <87zgegk9pj@hands.com> and subject line fixed since 20220613-1 (or probably before that) has caused the Debian Bug report #564260, regarding perltidy (-pbp) desalign hashes in given-when construct to be marked as done. This

Bug#475930: marked as done (attempted to not indent an non-long line)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 20:08:19 +0200 with message-id <8735c8loq4@hands.com> and subject line fixed in 20220613-1 (if not before) has caused the Debian Bug report #475930, regarding attempted to not indent an non-long line to be marked as done. This means that you claim that the

Bug#916681: marked as done (Perl::Tidy: tries to access file "SCALAR(0x...)" in cwd)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 19:57:16 +0200 with message-id <875yh4lp8j@hands.com> and subject line no longer reproducible has caused the Debian Bug report #916681, regarding Perl::Tidy: tries to access file "SCALAR(0x...)" in cwd to be marked as done. This means that you claim that

Processed: src:rust-resource-proof: fails to migrate to testing for too long: autopkgtest regression

2022-09-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.39-2 Bug #1021029 [src:rust-resource-proof] src:rust-resource-proof: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions rust-resource-proof/1.0.39-2. Bug #1021029 [src:rust-resource-proof]

Bug#528898: marked as done (please add info-dir-section to your info files)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 18:57:42 +0200 with message-id and subject line Re: please add info-dir-section to your info files has caused the Debian Bug report #528898, regarding please add info-dir-section to your info files to be marked as done. This means that you claim that the

Bug#1020282: marked as done (openmotor: git build fail when $HOME is not writable)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 10:25:27 -0600 (MDT) with message-id <20220930162527.189db24e0...@rover.gag.com> and subject line fixed in latest upload has caused the Debian Bug report #1020282, regarding openmotor: git build fail when $HOME is not writable to be marked as done. This means

Bug#1021009: marked as done (Unindent the .pc files for pkgconf compatibility)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 16:37:01 + with message-id and subject line Bug#1021009: fixed in glslang 11.11.0-2 has caused the Debian Bug report #1021009, regarding Unindent the .pc files for pkgconf compatibility to be marked as done. This means that you claim that the problem has

Bug#916679: marked as done (broken Perl::Tidy man page)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 18:12:08 +0200 with message-id <878rm0lu3r@hands.com> and subject line perltidy: fixed since 20200110-1 has caused the Debian Bug report #916679, regarding broken Perl::Tidy man page to be marked as done. This means that you claim that the problem has been

Bug#922406: marked as done (man Perl::Tidy disaster)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 17:58:30 +0200 with message-id <87bkqwluqh@hands.com> and subject line perltidy: fixed since 20200110-1 has caused the Debian Bug report #922406, regarding man Perl::Tidy disaster to be marked as done. This means that you claim that the problem has been

Bug#949490: marked as done (raptor2: FTBFS with libxml2 not shipping xml2-config)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 16:08:47 + with message-id and subject line Bug#949490: fixed in raptor2 2.0.15-3 has caused the Debian Bug report #949490, regarding raptor2: FTBFS with libxml2 not shipping xml2-config to be marked as done. This means that you claim that the problem has

Bug#1016922: marked as done (pkgconf doesn’t handle indented .pc files)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 16:08:14 + with message-id and subject line Bug#1016922: fixed in pkgconf 1.8.0-6 has caused the Debian Bug report #1016922, regarding pkgconf doesn’t handle indented .pc files to be marked as done. This means that you claim that the problem has been dealt

Bug#1021014: marked as done (snakeyaml: CVE-2022-38752)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 15:38:07 + with message-id and subject line Bug#1021014: fixed in snakeyaml 1.33-1 has caused the Debian Bug report #1021014, regarding snakeyaml: CVE-2022-38752 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1020951: marked as done (RFS: raptor2/2.0.15-3 [QA] -- Raptor 2 RDF syntax library)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 17:36:17 +0200 with message-id and subject line Re: RFS: raptor2/2.0.15-3 [QA] -- Raptor 2 RDF syntax library has caused the Debian Bug report #1020951, regarding RFS: raptor2/2.0.15-3 [QA] -- Raptor 2 RDF syntax library to be marked as done. This means that

Bug#1020630: marked as done (diffoscope: cbfstool is finally available in Debian)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 15:34:45 + with message-id and subject line Bug#1020630: fixed in diffoscope 223 has caused the Debian Bug report #1020630, regarding diffoscope: cbfstool is finally available in Debian to be marked as done. This means that you claim that the problem has

Processed: notfound 1020301 in 1:10.3.36-0+deb10u, found 1020301 in 1:10.3.36-0+deb10u1, closing 1020301

2022-09-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # typo in version > notfound 1020301 1:10.3.36-0+deb10u Bug #1020301 [mariadb-server-10.3] mariadb-server-10.3: postinst called with unknown argument 'triggered' There is no source info for the package 'mariadb-server-10.3' at version

Bug#1018076: marked as done (mini-transition: gjs built against mozjs102)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 16:22:11 +0100 with message-id and subject line Re: Bug#1018076: mini-transition: gjs built against mozjs102 has caused the Debian Bug report #1018076, regarding mini-transition: gjs built against mozjs102 to be marked as done. This means that you claim that

Bug#1020971: marked as done (usrmerge: Fails to install on Windows Subsystem for Linux (WSL) 1.0)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 16:15:42 +0100 with message-id <1016eb1a2c286573e6cb97c3fe77fb3571e43d30.ca...@debian.org> and subject line Re: Bug#1020971: usrmerge: Fails to install on Windows Subsystem for Linux (WSL) 1.0 has caused the Debian Bug report #1020971, regarding usrmerge: Fails

Bug#1020813: marked as done (bible-kjv: reproducible-builds: differing buildid in various binaries)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 15:04:05 + with message-id and subject line Bug#1020813: fixed in bible-kjv 4.38 has caused the Debian Bug report #1020813, regarding bible-kjv: reproducible-builds: differing buildid in various binaries to be marked as done. This means that you claim that

Bug#994089: marked as done (ITP: node-rollup-plugin-strip -- Rollup plugin to remove debugger statements and functions)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 15:00:13 + with message-id and subject line Bug#994089: fixed in node-rollup-plugin-strip 2.1.0+ds-1 has caused the Debian Bug report #994089, regarding ITP: node-rollup-plugin-strip -- Rollup plugin to remove debugger statements and functions to be marked

Bug#1019546: marked as done (ITP: emacs-pass-mode -- major mode for password-store)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 15:00:12 + with message-id and subject line Bug#1019546: fixed in emacs-pass-mode 2.0-1 has caused the Debian Bug report #1019546, regarding ITP: emacs-pass-mode -- major mode for password-store to be marked as done. This means that you claim that the

Bug#1019208: marked as done (ITP: viagee -- support for Gmail as the preferred email application in GNOME)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 15:00:14 + with message-id and subject line Bug#1019208: fixed in viagee 3.0-1 has caused the Debian Bug report #1019208, regarding ITP: viagee -- support for Gmail as the preferred email application in GNOME to be marked as done. This means that you

Bug#1019507: marked as done (ITP: libquazip1-qt6 -- Qt/C++ wrapper over minizip - Version 1 (Qt6))

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 15:00:13 + with message-id and subject line Bug#1019507: fixed in libquazip1-qt6 1.3-1 has caused the Debian Bug report #1019507, regarding ITP: libquazip1-qt6 -- Qt/C++ wrapper over minizip - Version 1 (Qt6) to be marked as done. This means that you claim

Bug#1009142: marked as done (ITP: org-appear -- auto-toggle visibility of org mode elements)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 15:00:14 + with message-id and subject line Bug#1009142: fixed in org-appear 0.3.0-1 has caused the Debian Bug report #1009142, regarding ITP: org-appear -- auto-toggle visibility of org mode elements to be marked as done. This means that you claim that

Bug#1020012: marked as done (python-fluids: FTBFS: ModuleNotFoundError: No module named 'setuptools')

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 14:43:10 + with message-id and subject line Bug#1020012: fixed in python-fluids 1.0.22-2 has caused the Debian Bug report #1020012, regarding python-fluids: FTBFS: ModuleNotFoundError: No module named 'setuptools' to be marked as done. This means that you

Bug#529152: marked as done (vflib3: please upgrade your watch file)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 14:44:01 + with message-id and subject line Bug#529152: fixed in vflib3 3.7.2+dfsg-0.1 has caused the Debian Bug report #529152, regarding vflib3: please upgrade your watch file to be marked as done. This means that you claim that the problem has been

Bug#449781: marked as done (vflib3: debian/watch fails to report upstream's version)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 14:44:01 + with message-id and subject line Bug#449781: fixed in vflib3 3.7.2+dfsg-0.1 has caused the Debian Bug report #449781, regarding vflib3: debian/watch fails to report upstream's version to be marked as done. This means that you claim that the

Bug#515724: marked as done (vflib3: incorrect upstream URL in copyright file)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 14:44:01 + with message-id and subject line Bug#515724: fixed in vflib3 3.7.2+dfsg-0.1 has caused the Debian Bug report #515724, regarding vflib3: incorrect upstream URL in copyright file to be marked as done. This means that you claim that the problem has

Bug#1020903: marked as done (pipewire-pulse: Is the conflict with pulseaudio necessary?)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 13:39:45 + with message-id and subject line Bug#1020903: fixed in pipewire 0.3.59-1 has caused the Debian Bug report #1020903, regarding pipewire-pulse: Is the conflict with pulseaudio necessary? to be marked as done. This means that you claim that the

Bug#1020330: marked as done (pipewire-pulse: Conflict with pulseaudio is badly resolved by apt full-upgrade)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 13:39:45 + with message-id and subject line Bug#1020330: fixed in pipewire 0.3.59-1 has caused the Debian Bug report #1020330, regarding pipewire-pulse: Conflict with pulseaudio is badly resolved by apt full-upgrade to be marked as done. This means that

Bug#1017286: marked as done (fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 'master_ufo/Inter.designspace': Generating fonts from Designspace failed: fonts contains incompatible glyphs:

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 13:37:04 + with message-id and subject line Bug#1017286: fixed in fonts-inter 4.0~beta1+ds-1 has caused the Debian Bug report #1017286, regarding fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 'master_ufo/Inter.designspace': Generating fonts

Bug#1020171: marked as done (paredit-everywhere: FTBFS: make: *** [debian/rules:7: binary] Error 25)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 12:20:10 + with message-id and subject line Bug#1020171: fixed in paredit-everywhere 0.4git10-1 has caused the Debian Bug report #1020171, regarding paredit-everywhere: FTBFS: make: *** [debian/rules:7: binary] Error 25 to be marked as done. This means

Bug#1012988: marked as done (librg-blast-parser-perl: ftbfs with GCC-12)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 11:04:40 + with message-id and subject line Bug#1012988: fixed in librg-blast-parser-perl 0.03-9 has caused the Debian Bug report #1012988, regarding librg-blast-parser-perl: ftbfs with GCC-12 to be marked as done. This means that you claim that the

Processed: closing 1017401

2022-09-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1017401 3.4.1.0-3 Bug #1017401 [src:haskell-cabal-install] haskell-cabal-install: FTBFS in bookworm: Depends: libghc-resolv-dev (>= 0.1.1) but it is not installable Ignoring request to alter fixed versions of bug #1017401 to the same

Processed: closing 1017227

2022-09-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1017227 1.1.2.0-2 Bug #1017227 [src:haskell-snap-server] haskell-snap-server: FTBFS: unsatisfiable build-dependency: libghc-attoparsec-dev (< 0.14) but 0.14.4-2 is to be installed Marked as fixed in versions haskell-snap-server/1.1.2.0-2.

Bug#1020991: marked as done (php-twig: CVE-2022-39261)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 10:20:48 + with message-id and subject line Bug#1020991: fixed in php-twig 3.4.3-1 has caused the Debian Bug report #1020991, regarding php-twig: CVE-2022-39261 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: reassign 1019685 to node-rollup-plugin-node-resolve, found 1019685 in 14.0.0+ds-1 ...

2022-09-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1019685 node-rollup-plugin-node-resolve Bug #1019685 {Done: Yadd } [src:node-babel7] node-babel7: FTBFS in sid Bug reassigned from package 'src:node-babel7' to 'node-rollup-plugin-node-resolve'. No longer marked as found in versions

Bug#976269: marked as done ([20201202] mirror.intergrid.com.au: sync-frequency, ftpsync-version)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 10:16:40 + with message-id <6336c2089c161_2528496010...@godard.mail> and subject line Bug#976269 fixed in mirrors has caused the Debian Bug report #976269, regarding [20201202] mirror.intergrid.com.au: sync-frequency, ftpsync-version to be marked as done.

Bug#1014797: marked as done (FTBFS: test failures with new libgd3)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 09:49:09 + with message-id and subject line Bug#1014797: fixed in gbrowse 2.56+dfsg-11 has caused the Debian Bug report #1014797, regarding FTBFS: test failures with new libgd3 to be marked as done. This means that you claim that the problem has been dealt

Processed: closing 1017215

2022-09-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1017215 0.19.6-2 Bug #1017215 [src:haskell-shake] libghc-shake-dev and libghc-shake-data both ship /usr/lib/haskell-packages/extra-packages/shake-0.19.6 Marked as fixed in versions haskell-shake/0.19.6-2. Bug #1017215 [src:haskell-shake]

Bug#1019390: marked as done (o2: autopkgtest regression on i386 and s390x: Assertion `arg->v.vf[i] == 123.456F + i' failed.)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 09:18:57 + with message-id and subject line Bug#1019390: fixed in o2 1.1~ds-2 has caused the Debian Bug report #1019390, regarding o2: autopkgtest regression on i386 and s390x: Assertion `arg->v.vf[i] == 123.456F + i' failed. to be marked as done. This

Processed: closing 1020993

2022-09-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1020993 3.3.21-3 Bug #1020993 [src:haskell-warp] haskell-warp: FTBFS on mipsel: E: Build killed with signal TERM after 150 minutes of inactivity The source 'haskell-warp' and version '3.3.21-3' do not appear to match any binary packages

Bug#1015328: marked as done (ruby-netcdf: FTBFS: ERROR: Test "ruby3.1" failed.)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 07:50:15 + with message-id and subject line Bug#1015328: fixed in ruby-netcdf 0.8.0-3 has caused the Debian Bug report #1015328, regarding ruby-netcdf: FTBFS: ERROR: Test "ruby3.1" failed. to be marked as done. This means that you claim that the problem

Bug#1006818: marked as done (intermediary files embed arch-specific path)

2022-09-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Sep 2022 06:35:00 + with message-id and subject line Bug#1006818: fixed in eye 22.0203.1955~ds-2 has caused the Debian Bug report #1006818, regarding intermediary files embed arch-specific path to be marked as done. This means that you claim that the problem has