Processed: RFS: yascreen/1.92-1~exp1 -- Yet Another Screen Library - development files

2023-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1028035 Bug #1028035 [sponsorship-requests] RFS: yascreen/1.92-1~exp1 -- Yet Another Screen Library - development files Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1028035: https://bugs

Bug#995544: marked as done (Updating the dh-lua Uploaders list)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 07:35:04 + with message-id and subject line Bug#995544: fixed in dh-lua 29 has caused the Debian Bug report #995544, regarding Updating the dh-lua Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1024721: marked as done (dh-lua: stop using libtool-bin)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 07:35:04 + with message-id and subject line Bug#1024721: fixed in dh-lua 29 has caused the Debian Bug report #1024721, regarding dh-lua: stop using libtool-bin to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1027621: marked as done (mkdocstrings-python-handlers: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 07:19:57 + with message-id and subject line Bug#1027621: fixed in mkdocstrings-python-handlers 0.8.3-1 has caused the Debian Bug report #1027621, regarding mkdocstrings-python-handlers: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.

Processed: src:raku-json-class: fails to migrate to testing for too long: unresolved RC bug

2023-01-05 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.0.19-1 Bug #1028038 [src:raku-json-class] src:raku-json-class: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions raku-json-class/0.0.19-1. Bug #1028038 [src:raku-json-class] src:raku-json-class: fails to migrate to t

Bug#1024883: marked as done (Reconsider versioned dependencies of libpinyin-data)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 6 Jan 2023 07:16:34 +0100 with message-id and subject line Re: Bug#1024883: Reconsider versioned dependencies of libpinyin-data has caused the Debian Bug report #1024883, regarding Reconsider versioned dependencies of libpinyin-data to be marked as done. This means that y

Bug#1025696: marked as done (bzip3: The version that the CLI tools and manpages report is "UNKNOWN".)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 06:19:20 + with message-id and subject line Bug#1025696: fixed in bzip3 1.2.1-2 has caused the Debian Bug report #1025696, regarding bzip3: The version that the CLI tools and manpages report is "UNKNOWN". to be marked as done. This means that you claim tha

Bug#1027285: marked as done (matplotlib: axes3d.quiver() fails when providing args to Line3DCollection)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 05:20:06 + with message-id and subject line Bug#1027285: fixed in matplotlib 3.6.2-4 has caused the Debian Bug report #1027285, regarding matplotlib: axes3d.quiver() fails when providing args to Line3DCollection to be marked as done. This means that you cl

Bug#1027049: marked as done (python-matplotlib-data: missing copyright file)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 05:20:06 + with message-id and subject line Bug#1027049: fixed in matplotlib 3.6.2-4 has caused the Debian Bug report #1027049, regarding python-matplotlib-data: missing copyright file to be marked as done. This means that you claim that the problem has bee

Bug#1024488: marked as done (kaddressbook: Unused build-dependency on libgpgmepp-dev?)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 05:14:33 +0100 with message-id <4770519.GXAFRqVoOG@treadstone-71> and subject line has caused the Debian Bug report #1024488, regarding kaddressbook: Unused build-dependency on libgpgmepp-dev? to be marked as done. This means that you claim that the problem has

Bug#1023039: marked as done (python-xmlsec: FTBFS with xmlsec1 1.2.35)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 02:46:33 + with message-id and subject line Bug#1023039: fixed in python-xmlsec 1.3.13-1 has caused the Debian Bug report #1023039, regarding python-xmlsec: FTBFS with xmlsec1 1.2.35 to be marked as done. This means that you claim that the problem has been

Bug#1023496: marked as done (target-factory: FTBFS with protobuf 3.21)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 00:51:21 + with message-id and subject line Bug#1023496: fixed in target-factory 2.5-8 has caused the Debian Bug report #1023496, regarding target-factory: FTBFS with protobuf 3.21 to be marked as done. This means that you claim that the problem has been de

Bug#893678: marked as done (gesftpserver: drop unused Build-Depends: python-paramiko)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 6 Jan 2023 01:43:16 +0100 with message-id <8c44374a-4e2b-7e06-a22f-d13ec357e...@debian.org> and subject line Re: gesftpserver: diff for NMU version 1~ds-1.1 has caused the Debian Bug report #893678, regarding gesftpserver: drop unused Build-Depends: python-paramiko to be mar

Bug#1021209: marked as done (pyqt6: Create python3-pyqt6.qtpdf)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2023 00:00:19 + with message-id and subject line Bug#1021209: fixed in pyqt6 6.4.0-2 has caused the Debian Bug report #1021209, regarding pyqt6: Create python3-pyqt6.qtpdf to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1024036: marked as done (nipy FTBFS with Python 3.11 as supported version)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 23:35:23 + with message-id and subject line Bug#1024036: fixed in nipy 0.5.0-5 has caused the Debian Bug report #1024036, regarding nipy FTBFS with Python 3.11 as supported version to be marked as done. This means that you claim that the problem has been de

Bug#1027171: marked as done (mplcursors: autopkgtest fail with matplotlib/3.6.2)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:38:50 + with message-id and subject line Bug#1027171: fixed in mplcursors 0.5.2-1 has caused the Debian Bug report #1027171, regarding mplcursors: autopkgtest fail with matplotlib/3.6.2 to be marked as done. This means that you claim that the problem has

Bug#1027839: marked as done (createrepo-c FTBFS with Python 3.11 as default version)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:35:06 + with message-id and subject line Bug#1027839: fixed in createrepo-c 0.17.3-2 has caused the Debian Bug report #1027839, regarding createrepo-c FTBFS with Python 3.11 as default version to be marked as done. This means that you claim that the prob

Bug#1026967: marked as done (llvm: broken-symlink /usr/share/man/man1/llvm-reduce.1.gz -> llvm-reduce-14.1.gz)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:37:55 + with message-id and subject line Bug#1026967: fixed in llvm-defaults 0.55.4 has caused the Debian Bug report #1026967, regarding llvm: broken-symlink /usr/share/man/man1/llvm-reduce.1.gz -> llvm-reduce-14.1.gz to be marked as done. This means th

Bug#995499: marked as done (O: lua-apr -- Apache Portable Runtime library for the Lua language)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:24:18 + with message-id and subject line Bug#1027998: Removed package(s) from unstable has caused the Debian Bug report #995499, regarding O: lua-apr -- Apache Portable Runtime library for the Lua language to be marked as done. This means that you claim

Bug#935271: marked as done (lua-apr: FTBFS on all architectures)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:24:18 + with message-id and subject line Bug#1027998: Removed package(s) from unstable has caused the Debian Bug report #935271, regarding lua-apr: FTBFS on all architectures to be marked as done. This means that you claim that the problem has been dealt

Bug#895562: marked as done (RM: libgnomecanvasmm2.6 -- RoQA; unmaintained upstream; no rdeps)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:25:20 + with message-id and subject line Bug#895562: Removed package(s) from unstable has caused the Debian Bug report #895562, regarding RM: libgnomecanvasmm2.6 -- RoQA; unmaintained upstream; no rdeps to be marked as done. This means that you claim tha

Bug#1028000: marked as done (RM: kalendar [armel ppc64el s390x alpha hppa m68k riscv64 sh4] -- ROM; ANAIS)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:24:45 + with message-id and subject line Bug#1028000: Removed package(s) from unstable has caused the Debian Bug report #1028000, regarding RM: kalendar [armel ppc64el s390x alpha hppa m68k riscv64 sh4] -- ROM; ANAIS to be marked as done. This means tha

Bug#1027998: marked as done (RM: lua-apr -- RoQA; dead upstream; FTBFS with recent lua/apr)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:24:14 + with message-id and subject line Bug#1027998: Removed package(s) from unstable has caused the Debian Bug report #1027998, regarding RM: lua-apr -- RoQA; dead upstream; FTBFS with recent lua/apr to be marked as done. This means that you claim that

Bug#1027661: marked as done (python-griffe: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:11:03 + with message-id and subject line Bug#1027661: fixed in python-griffe 0.25.3-1 has caused the Debian Bug report #1027661, regarding python-griffe: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/di

Bug#1024528: marked as done (python3-refurb: Throws syntax error in postinst, but upgrade completes anyways)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:11:13 + with message-id and subject line Bug#1024528: fixed in python-refurb 1.9.1-1 has caused the Debian Bug report #1024528, regarding python3-refurb: Throws syntax error in postinst, but upgrade completes anyways to be marked as done. This means tha

Bug#805864: marked as done (procmail: procmail.org homepage gone)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:10:44 + with message-id and subject line Bug#805864: fixed in procmail 3.24-1 has caused the Debian Bug report #805864, regarding procmail: procmail.org homepage gone to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1006633: marked as done (procmail is unmaintained upstream)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:10:44 + with message-id and subject line Bug#1006633: fixed in procmail 3.24-1 has caused the Debian Bug report #1006633, regarding procmail is unmaintained upstream to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1006653: marked as done (procmail-dbgsym)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 22:10:44 + with message-id and subject line Bug#1006653: fixed in procmail 3.24-1 has caused the Debian Bug report #1006653, regarding procmail-dbgsym to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#1027997: marked as done (linux-image-6.0.0-6-amd64: netfilter (nft) tproxy broken on 6.0.0 kernel)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 5 Jan 2023 23:01:59 +0100 with message-id and subject line Re: Bug#1027997: linux-image-6.0.0-6-amd64: netfilter (nft) tproxy broken on 6.0.0 kernel has caused the Debian Bug report #1027997, regarding linux-image-6.0.0-6-amd64: netfilter (nft) tproxy broken on 6.0.0 kern

Bug#983363: marked as done (unattended-upgrades: autopkg test failure only on qemu testbed)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 21:56:45 + with message-id and subject line Bug#983363: fixed in unattended-upgrades 2.9.1+nmu3 has caused the Debian Bug report #983363, regarding unattended-upgrades: autopkg test failure only on qemu testbed to be marked as done. This means that you clai

Bug#1012226: marked as done (unattended-upgrades: flaky autopkgtest: kernel-patterns seems to regularly get confused)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 21:56:45 + with message-id and subject line Bug#1012226: fixed in unattended-upgrades 2.9.1+nmu3 has caused the Debian Bug report #1012226, regarding unattended-upgrades: flaky autopkgtest: kernel-patterns seems to regularly get confused to be marked as don

Bug#1003473: marked as done (php-horde-lz4: fails to build with php8.1)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 21:27:43 + with message-id and subject line Bug#1003473: fixed in php-horde-lz4 1.0.10-9 has caused the Debian Bug report #1003473, regarding php-horde-lz4: fails to build with php8.1 to be marked as done. This means that you claim that the problem has been

Bug#1015212: marked as done (pelican-themes can install the notmyidea theme but cannot remove it)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 20:52:00 + with message-id and subject line Bug#1015212: fixed in pelican 4.8.0+dfsg-1 has caused the Debian Bug report #1015212, regarding pelican-themes can install the notmyidea theme but cannot remove it to be marked as done. This means that you claim t

Bug#1012540: marked as done (pelican: The contents of man of "pelican" and "pelican-plugins" seem to be wrong.)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 20:52:00 + with message-id and subject line Bug#1012540: fixed in pelican 4.8.0+dfsg-1 has caused the Debian Bug report #1012540, regarding pelican: The contents of man of "pelican" and "pelican-plugins" seem to be wrong. to be marked as done. This means t

Processed: closing 1028001

2023-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # contains all three commits > close 1028001 1:2.5.4-1~exp1 Bug #1028001 [nfs-common] nfs-common: in a kerberized nfs setup, rpc gssd get ABRT'ed from time to time Marked as fixed in versions nfs-utils/1:2.5.4-1~exp1. Bug #1028001 [nfs-common] nf

Bug#919636: marked as done (pelican: "make publish" with Atom feed yields "CRITICAL: TypeError: not all arguments converted during string formatting")

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 5 Jan 2023 12:08:52 -0800 with message-id and subject line Re: pelican: "make publish" with Atom feed yields "CRITICAL: TypeError: not all arguments converted during string formatting" has caused the Debian Bug report #919636, regarding pelican: "make publish" with Atom f

Bug#1027511: marked as done (mkdocstrings: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 19:53:01 + with message-id and subject line Bug#1027511: fixed in mkdocstrings 0.19.1-1 has caused the Debian Bug report #1027511, regarding mkdocstrings: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist

Bug#1027523: marked as done (autoimport: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 5 Jan 2023 19:08:13 + with message-id <20230105190813.4bkyoo5to7qhj...@4angle.com> and subject line Fixed in pdm-pep517 version 1.0.6+ds1-2 has caused the Debian Bug report #1027523, regarding autoimport: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'pack

Bug#1027798: marked as done (LXCFS: not updating entries in /proc on arm64)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 5 Jan 2023 20:18:51 +0100 with message-id <6a48e0a5-6359-1e0a-031a-d2844a38b...@myiq.de> and subject line Finished has caused the Debian Bug report #1027798, regarding LXCFS: not updating entries in /proc on arm64 to be marked as done. This means that you claim that the pro

Bug#1027246: marked as done (tiledb-py: autopkgtest fail with numpy/1.24.1)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 19:31:07 + with message-id and subject line Bug#1027246: fixed in tiledb-py 0.19.1-1 has caused the Debian Bug report #1027246, regarding tiledb-py: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has been

Bug#1027909: marked as done (golang-github-libgit2-git2go: FTBFS in bookworm (undeclared build-dependency on tzdata))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 19:22:42 + with message-id and subject line Bug#1027909: fixed in golang-github-libgit2-git2go 34.0.0-3 has caused the Debian Bug report #1027909, regarding golang-github-libgit2-git2go: FTBFS in bookworm (undeclared build-dependency on tzdata) to be marked

Processed: closing 1026331

2023-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1026331 Bug #1026331 [src:lintian-brush] lintian-brush: autopkgtest regression: test_matches_package_version Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1026331: https://bugs.debian.o

Bug#1025898: marked as done (ITP: hippotat -- IP-over-HTTP client and server)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 19:03:47 + with message-id and subject line Bug#1025898: fixed in hippotat 1.1.3 has caused the Debian Bug report #1025898, regarding ITP: hippotat -- IP-over-HTTP client and server to be marked as done. This means that you claim that the problem has been d

Bug#1026633: marked as done (grig: FTBFS: rig-daemon.c:2286: undefined reference to `rig_get_split')

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 18:50:26 + with message-id and subject line Bug#1026633: fixed in grig 0.9.0-1 has caused the Debian Bug report #1026633, regarding grig: FTBFS: rig-daemon.c:2286: undefined reference to `rig_get_split' to be marked as done. This means that you claim that t

Bug#1016791: marked as done (kivy: New upstream release available)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 18:51:31 + with message-id and subject line Bug#1016791: fixed in kivy 2.1.0-1 has caused the Debian Bug report #1016791, regarding kivy: New upstream release available to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1013046: marked as done (systemc: ftbfs with GCC-12 (symbol changes))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 18:10:29 + with message-id and subject line Bug#1013046: fixed in systemc 2.3.4-1 has caused the Debian Bug report #1013046, regarding systemc: ftbfs with GCC-12 (symbol changes) to be marked as done. This means that you claim that the problem has been deal

Bug#901291: marked as done (RFA: pynliner -- CSS-to-inline-styles conversion tool for HTML - Python 2.x)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 18:09:59 + with message-id and subject line Bug#901291: fixed in pynliner 0.8.0-5 has caused the Debian Bug report #901291, regarding RFA: pynliner -- CSS-to-inline-styles conversion tool for HTML - Python 2.x to be marked as done. This means that you clai

Bug#1023918: marked as done (ziproxy: license conflict with libsasl2)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 17:09:34 + with message-id and subject line Bug#1023918: fixed in ziproxy 3.3.2-6 has caused the Debian Bug report #1023918, regarding ziproxy: license conflict with libsasl2 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1026296: marked as done (unifrac-tools: Incorrect Homepage link)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 17:08:50 + with message-id and subject line Bug#1026296: fixed in unifrac-tools 1.2-1 has caused the Debian Bug report #1026296, regarding unifrac-tools: Incorrect Homepage link to be marked as done. This means that you claim that the problem has been dealt

Bug#1007054: marked as done (lxqt-metapackages: please consider upgrading to 3.0 source format)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 17:07:22 + with message-id and subject line Bug#1007054: fixed in lxqt-metapackages 31 has caused the Debian Bug report #1007054, regarding lxqt-metapackages: please consider upgrading to 3.0 source format to be marked as done. This means that you claim tha

Bug#1025467: marked as done (glusterfs: test suite failure: xfs filesystem too small)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 16:35:06 + with message-id and subject line Bug#1025467: fixed in glusterfs 10.3-3 has caused the Debian Bug report #1025467, regarding glusterfs: test suite failure: xfs filesystem too small to be marked as done. This means that you claim that the problem

Bug#974617: marked as done (nomacs 3.16 is available upstream)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 6 Jan 2023 00:26:11 +0800 with message-id and subject line new nomacs release has caused the Debian Bug report #974617, regarding nomacs 3.16 is available upstream to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1024576: marked as done (librepo: FTBFS against libgpgme-dev >= 1.18.0-2)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 16:22:06 + with message-id and subject line Bug#1024576: fixed in librepo 1.14.5-1 has caused the Debian Bug report #1024576, regarding librepo: FTBFS against libgpgme-dev >= 1.18.0-2 to be marked as done. This means that you claim that the problem has been

Bug#1027372: marked as done (golang-github-teambition-rrule-go: FTBFS in bullseye (missing build-depends on tzdata))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 16:04:21 + with message-id and subject line Bug#1027372: fixed in golang-github-teambition-rrule-go 1.8.1-1 has caused the Debian Bug report #1027372, regarding golang-github-teambition-rrule-go: FTBFS in bullseye (missing build-depends on tzdata) to be mar

Processed: closing 983805

2023-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 983805 Bug #983805 [wnpp] ITA: ucspi-unix -- UNIX-domain socket client-server command-line tools Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 983805: https://bugs.debian.org/cgi-bin/bu

Bug#983804: marked as done (ITA: ucspi-tcp -- command-line tools for building TCP client-server applications)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 15:35:10 + with message-id and subject line Bug#983804: fixed in ucspi-unix 1.0-2 has caused the Debian Bug report #983804, regarding ITA: ucspi-tcp -- command-line tools for building TCP client-server applications to be marked as done. This means that you

Bug#991774: marked as done (ucspi-unix FTBFS on architectures without dietlibc)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 15:35:10 + with message-id and subject line Bug#991774: fixed in ucspi-unix 1.0-2 has caused the Debian Bug report #991774, regarding ucspi-unix FTBFS on architectures without dietlibc to be marked as done. This means that you claim that the problem has bee

Bug#1027910: marked as done (golang-github-rickb777-date: FTBFS in bookworm (undeclared build-dependency on tzdata))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 15:34:10 + with message-id and subject line Bug#1027910: fixed in golang-github-rickb777-date 1.20.1-1 has caused the Debian Bug report #1027910, regarding golang-github-rickb777-date: FTBFS in bookworm (undeclared build-dependency on tzdata) to be marked a

Bug#1025640: marked as done (python-dbusmock: autopkgtest depends on transitional policykit-1 package)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 14:55:01 + with message-id and subject line Bug#1025640: fixed in python-dbusmock 0.28.7-1 has caused the Debian Bug report #1025640, regarding python-dbusmock: autopkgtest depends on transitional policykit-1 package to be marked as done. This means that y

Bug#975326: marked as done (dash: inconsistency between ulimit -r and ulimit -a)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:35:08 + with message-id and subject line Bug#975326: fixed in dash 0.5.12-2 has caused the Debian Bug report #975326, regarding dash: inconsistency between ulimit -r and ulimit -a to be marked as done. This means that you claim that the problem has been

Bug#975325: marked as done (dash(1) man page: ulimit documentation is inconsistent and out-of-date)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:35:08 + with message-id and subject line Bug#975325: fixed in dash 0.5.12-2 has caused the Debian Bug report #975325, regarding dash(1) man page: ulimit documentation is inconsistent and out-of-date to be marked as done. This means that you claim that th

Bug#819829: marked as done (dash: "hash: Illegal option -v")

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:35:08 + with message-id and subject line Bug#819829: fixed in dash 0.5.12-2 has caused the Debian Bug report #819829, regarding dash: "hash: Illegal option -v" to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#869206: marked as done (dash: man dash doesn't describe "false" and other builtins)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:35:08 + with message-id and subject line Bug#558607: fixed in dash 0.5.12-2 has caused the Debian Bug report #558607, regarding dash: man dash doesn't describe "false" and other builtins to be marked as done. This means that you claim that the problem ha

Bug#558607: marked as done (dash: jobs builtin is missing in manpage)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:35:08 + with message-id and subject line Bug#558607: fixed in dash 0.5.12-2 has caused the Debian Bug report #558607, regarding dash: jobs builtin is missing in manpage to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1024635: marked as done (dash: segfaults during runtime when executing a script with invalid syntax)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:35:08 + with message-id and subject line Bug#1024635: fixed in dash 0.5.12-2 has caused the Debian Bug report #1024635, regarding dash: segfaults during runtime when executing a script with invalid syntax to be marked as done. This means that you claim

Bug#396821: marked as done (dash 0.5.2-5 manpage doesn't document its builtin 'kill' command)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:35:08 + with message-id and subject line Bug#558607: fixed in dash 0.5.12-2 has caused the Debian Bug report #558607, regarding dash 0.5.2-5 manpage doesn't document its builtin 'kill' command to be marked as done. This means that you claim that the prob

Bug#1017531: marked as done (dash: for/while/if suppress errors from redirections with -e, POSIX violation)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:35:08 + with message-id and subject line Bug#1017531: fixed in dash 0.5.12-2 has caused the Debian Bug report #1017531, regarding dash: for/while/if suppress errors from redirections with -e, POSIX violation to be marked as done. This means that you cla

Bug#1027103: marked as done (virtualbox-ext-pack: Hash mismatch Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 5 Jan 2023 14:27:05 +0100 with message-id <794152eb-6a6b-cd48-e719-ae03c640a...@debian.org> and subject line Re: virtualbox-ext-pack: Hash mismatch Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack has caused the Debian Bug report #1027103, regarding virtualbox-ext-pa

Bug#975326: marked as done (dash: inconsistency between ulimit -r and ulimit -a)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:19:14 + with message-id and subject line Bug#975326: fixed in dash 0.5.12-1 has caused the Debian Bug report #975326, regarding dash: inconsistency between ulimit -r and ulimit -a to be marked as done. This means that you claim that the problem has been

Bug#850202: marked as done (dash: test with multiple conditions cannot handle variable whose expanded value is same as an operator)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:19:14 + with message-id and subject line Bug#850202: fixed in dash 0.5.12-1 has caused the Debian Bug report #850202, regarding dash: test with multiple conditions cannot handle variable whose expanded value is same as an operator to be marked as done.

Bug#1024635: marked as done (dash: segfaults during runtime when executing a script with invalid syntax)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:19:14 + with message-id and subject line Bug#1024635: fixed in dash 0.5.12-1 has caused the Debian Bug report #1024635, regarding dash: segfaults during runtime when executing a script with invalid syntax to be marked as done. This means that you claim

Bug#869206: marked as done (dash: man dash doesn't describe "false" and other builtins)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:19:13 + with message-id and subject line Bug#558607: fixed in dash 0.5.12-1 has caused the Debian Bug report #558607, regarding dash: man dash doesn't describe "false" and other builtins to be marked as done. This means that you claim that the problem ha

Bug#819829: marked as done (dash: "hash: Illegal option -v")

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:19:13 + with message-id and subject line Bug#819829: fixed in dash 0.5.12-1 has caused the Debian Bug report #819829, regarding dash: "hash: Illegal option -v" to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#396821: marked as done (dash 0.5.2-5 manpage doesn't document its builtin 'kill' command)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:19:13 + with message-id and subject line Bug#558607: fixed in dash 0.5.12-1 has caused the Debian Bug report #558607, regarding dash 0.5.2-5 manpage doesn't document its builtin 'kill' command to be marked as done. This means that you claim that the prob

Bug#558607: marked as done (dash: jobs builtin is missing in manpage)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:19:13 + with message-id and subject line Bug#558607: fixed in dash 0.5.12-1 has caused the Debian Bug report #558607, regarding dash: jobs builtin is missing in manpage to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1017531: marked as done (dash: for/while/if suppress errors from redirections with -e, POSIX violation)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 13:19:14 + with message-id and subject line Bug#1017531: fixed in dash 0.5.12-1 has caused the Debian Bug report #1017531, regarding dash: for/while/if suppress errors from redirections with -e, POSIX violation to be marked as done. This means that you cla

Processed: reassign and close

2023-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1026570 dask.distributed 2022.02.0+ds.1-2 Bug #1026570 [src:python-streamz] python-streamz: FTBFS: ValueError: I/O operation on closed file. Bug reassigned from package 'src:python-streamz' to 'dask.distributed'. No longer marked as foun

Bug#1027379: marked as done (nfdump: FTBFS in bullseye (missing build-depends on tzdata))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 11:52:01 + with message-id and subject line Bug#1027379: fixed in nfdump 1.7.1-2 has caused the Debian Bug report #1027379, regarding nfdump: FTBFS in bullseye (missing build-depends on tzdata) to be marked as done. This means that you claim that the proble

Bug#1027966: marked as done (building of cross-toolchain-base broken, wrong assumption of dpkg-buildinfo)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 11:49:38 + with message-id and subject line Bug#1027966: fixed in dpkg 1.21.17 has caused the Debian Bug report #1027966, regarding building of cross-toolchain-base broken, wrong assumption of dpkg-buildinfo to be marked as done. This means that you claim

Bug#1027716: marked as done (dpkg: consider trimming changelog.gz)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 11:49:38 + with message-id and subject line Bug#1027716: fixed in dpkg 1.21.17 has caused the Debian Bug report #1027716, regarding dpkg: consider trimming changelog.gz to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1026407: marked as done (nvidia-support: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 11:30:09 + with message-id and subject line Bug#1026407: fixed in nvidia-support 20220217+2 has caused the Debian Bug report #1026407, regarding nvidia-support: [INTL:pt_BR] Brazilian Portuguese debconf templates translation to be marked as done. This mean

Bug#608073: marked as done (/usr/lib/dri/i965_dri.so: segfaults in run_vp (?))

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 5 Jan 2023 12:11:50 +0100 with message-id and subject line /usr/lib/dri/i965_dri.so: segfaults in run_vp (?) has caused the Debian Bug report #608073, regarding /usr/lib/dri/i965_dri.so: segfaults in run_vp (?) to be marked as done. This means that you claim that the prob

Bug#972947: marked as done (login not visible with classic theme)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 10:35:40 + with message-id and subject line Bug#972947: fixed in cacti 1.2.23+ds1-1 has caused the Debian Bug report #972947, regarding login not visible with classic theme to be marked as done. This means that you claim that the problem has been dealt with

Bug#1026392: marked as done (transition: gnat-12)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 5 Jan 2023 11:00:48 +0100 with message-id and subject line Re: Bug#1026392: transition: gnat-12 status update has caused the Debian Bug report #1026392, regarding transition: gnat-12 to be marked as done. This means that you claim that the problem has been dealt with. If t

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

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 09:31:21 + with message-id and subject line Bug#1027582: fixed in python-docx 0.8.11+dfsg1-4 has caused the Debian Bug report #1027582, regarding python-docx: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returne

Bug#1027955: marked as done (samba cannot be installed/upgraded)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 5 Jan 2023 11:54:02 +0300 with message-id <2744429e-3115-79a3-e955-08403933d...@msgid.tls.msk.ru> and subject line Re:Bug#1027955: samba cannot be installed/upgraded has caused the Debian Bug report #1027955, regarding samba cannot be installed/upgraded to be marked as done.

Bug#1027845: marked as done (kdevelop-python: Plugin crashes on encountering Python code)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 08:43:11 + with message-id and subject line Bug#1027845: fixed in kdevelop-python 22.12.0-3 has caused the Debian Bug report #1027845, regarding kdevelop-python: Plugin crashes on encountering Python code to be marked as done. This means that you claim that

Bug#1026084: marked as done (iraf: IRAF package creates wrong application menu)

2023-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2023 08:42:20 + with message-id and subject line Bug#1026084: fixed in iraf 2.17-4 has caused the Debian Bug report #1026084, regarding iraf: IRAF package creates wrong application menu to be marked as done. This means that you claim that the problem has been de