Bug#1059556: marked as done (gauche: add loongarch64 support)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Wed, 03 Apr 2024 05:34:43 + with message-id and subject line Bug#1059556: fixed in gauche 0.9.14-4 has caused the Debian Bug report #1059556, regarding gauche: add loongarch64 support to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1065859: marked as done (flowblade: Please drop dependencies on python3-distutils)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Wed, 03 Apr 2024 03:49:24 + with message-id and subject line Bug#1065859: fixed in flowblade 2.14.0.1-1 has caused the Debian Bug report #1065859, regarding flowblade: Please drop dependencies on python3-distutils to be marked as done. This means that you claim that the pro

Bug#1032725: marked as done (please drop transitional package liblz4-tool from src:lz4)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Wed, 03 Apr 2024 03:04:22 + with message-id and subject line Bug#1032725: fixed in lz4 1.9.4-2 has caused the Debian Bug report #1032725, regarding please drop transitional package liblz4-tool from src:lz4 to be marked as done. This means that you claim that the problem has

Bug#1046472: marked as done (lz4: Fails to build source after successful build)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Wed, 03 Apr 2024 03:04:22 + with message-id and subject line Bug#1046472: fixed in lz4 1.9.4-2 has caused the Debian Bug report #1046472, regarding lz4: Fails to build source after successful build to be marked as done. This means that you claim that the problem has been de

Bug#1068205: marked as done (gauche: FTBFS on arm{el,hf}: "list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) == 0x7)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Wed, 03 Apr 2024 00:19:22 + with message-id and subject line Bug#1068205: fixed in gauche 0.9.14-3 has caused the Debian Bug report #1068205, regarding gauche: FTBFS on arm{el,hf}: "list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) ==

Processed: ITP: wtmpdb -- Y2038 safe wtmp implementation

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1068289 Bug #1068289 [wnpp] ITP: wtmpdb -- Y2038 safe wtmp implementation Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1068289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068289 D

Processed: Merge duplicates

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1067360 src:flint Bug #1067360 [src:macaulay2] macaulay2: FTBFS: make[3]: *** [../Makefile.library:235: /<>/M2/BUILD/tarfiles/normaliz-3.9.2.tar.gz] Error 1 Bug reassigned from package 'src:macaulay2' to 'src:flint'. No longer marked as

Bug#1066289: marked as done (clipit: FTBFS: main.c:1080:9: error: implicit declaration of function ‘umask’ [-Werror=implicit-function-declaration])

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 22:49:05 + with message-id and subject line Bug#1066289: fixed in clipit 1.4.5+git20210313-2 has caused the Debian Bug report #1066289, regarding clipit: FTBFS: main.c:1080:9: error: implicit declaration of function ‘umask’ [-Werror=implicit-function-declar

Bug#1056893: marked as done (uvloop: ftbfs with cython 3.0.x)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 22:22:27 + with message-id and subject line Bug#1056893: fixed in uvloop 0.19.0+ds1-2.1 has caused the Debian Bug report #1056893, regarding uvloop: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with

Processed: closing 1067286

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # was a bug in flint > close 1067286 Bug #1067286 [src:msolve] msolve: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/msolve/usr/bin/msolve) Marked Bug as done > thanks Stop

Bug#1019738: marked as done (searchandrescue: FTBFS on riscv64: add library search path)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 22:06:29 + with message-id and subject line Bug#1019738: fixed in searchandrescue 1.5.0+dfsg-0.2 has caused the Debian Bug report #1019738, regarding searchandrescue: FTBFS on riscv64: add library search path to be marked as done. This means that you claim

Bug#1064217: marked as done (bitlbee: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 22:04:22 + with message-id and subject line Bug#1064217: fixed in bitlbee 3.6-1.4 has caused the Debian Bug report #1064217, regarding bitlbee: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the problem h

Bug#1007440: marked as done (bfbtester: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 21:50:09 + with message-id and subject line Bug#1007440: fixed in bfbtester 2.0.1-7.3 has caused the Debian Bug report #1007440, regarding bfbtester: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the pro

Processed: closing 1060078

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1060078 1.7.0-1 Bug #1060078 [davfs2] newer (from 2022) release is available 1.7.0 There is no source info for the package 'davfs2' at version '1.7.0-1' with architecture '' Unable to make a source version for version '1.7.0-1' Marked as fi

Bug#1007045: marked as done (libmad: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 21:24:53 + with message-id and subject line Bug#1007045: fixed in libmad 0.15.1b-10.2 has caused the Debian Bug report #1007045, regarding libmad: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the proble

Bug#1064728: marked as done (davfs2: FTBFS: configure: error: could not find neon)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 21:19:21 + with message-id and subject line Bug#1064728: fixed in davfs2 1.7.0-1 has caused the Debian Bug report #1064728, regarding davfs2: FTBFS: configure: error: could not find neon to be marked as done. This means that you claim that the problem has b

Bug#994187: marked as done (squidguard: Squidguard cannot access DATADIR as a symlink)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 21:11:09 + with message-id and subject line Bug#994187: fixed in squidguard 1.6.0-5 has caused the Debian Bug report #994187, regarding squidguard: Squidguard cannot access DATADIR as a symlink to be marked as done. This means that you claim that the proble

Bug#1066439: marked as done (squidguard: FTBFS: ././conftest.c:17:(.text.startup+0xb): undefined reference to `yywrap')

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 21:11:09 + with message-id and subject line Bug#1066439: fixed in squidguard 1.6.0-5 has caused the Debian Bug report #1066439, regarding squidguard: FTBFS: ././conftest.c:17:(.text.startup+0xb): undefined reference to `yywrap' to be marked as done. This m

Bug#1054900: marked as done (libunity: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 21:08:21 + with message-id and subject line Bug#1054900: fixed in libunity 7.1.4+19.04.20190319-6.1 has caused the Debian Bug report #1054900, regarding libunity: please consider upgrading to 3.0 source format to be marked as done. This means that you claim

Bug#1037202: marked as done (libunity9: Multi-Arch: same, but not co-installable)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 21:08:21 + with message-id and subject line Bug#1037202: fixed in libunity 7.1.4+19.04.20190319-6.1 has caused the Debian Bug report #1037202, regarding libunity9: Multi-Arch: same, but not co-installable to be marked as done. This means that you claim that

Bug#1063596: marked as done (flint: FTBFS on amd64: test segfault)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 2 Apr 2024 21:00:12 + with message-id <87jzlfqy3t@piedmont.edu> and subject line Re: flint: FTBFS on amd64: test segfault has caused the Debian Bug report #1063596, regarding flint: FTBFS on amd64: test segfault to be marked as done. This means that you claim that t

Processed: RFS: python-redmine/2.5.0-1 -- Python library for the Redmine RESTful API (Python 3)

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1067859 Bug #1067859 [sponsorship-requests] RFS: python-redmine/2.5.0-1 -- Python library for the Redmine RESTful API (Python 3) Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1067859: htt

Bug#1067674: marked as done (library package (arch any) depending on a "common" package with too strict version constraint)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 20:37:07 + with message-id and subject line Bug#1067674: fixed in folks 0.15.9-2 has caused the Debian Bug report #1067674, regarding library package (arch any) depending on a "common" package with too strict version constraint to be marked as done. This m

Bug#1067849: marked as done (util-linux: CVE-2024-28085: wall: escape sequence injection)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 20:33:09 + with message-id and subject line Bug#1067849: fixed in util-linux 2.36.1-8+deb11u2 has caused the Debian Bug report #1067849, regarding util-linux: CVE-2024-28085: wall: escape sequence injection to be marked as done. This means that you claim th

Bug#1067115: marked as done (gross: CVE-2023-52159)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 20:32:32 + with message-id and subject line Bug#1067115: fixed in gross 1.0.2-4.1~deb11u1 has caused the Debian Bug report #1067115, regarding gross: CVE-2023-52159 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1018572: marked as done (python-redmine: build-depends on python3-nose or uses it for autopkgtest)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 19:50:54 + with message-id and subject line Bug#1018572: fixed in python-redmine 2.5.0-1 has caused the Debian Bug report #1018572, regarding python-redmine: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you

Bug#1068216: marked as done (aqemu, dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 19:49:13 + with message-id and subject line Bug#1068216: fixed in aqemu 0.9.2-4 has caused the Debian Bug report #1068216, regarding aqemu, dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means that you claim that the

Bug#1022105: marked as done (pentaho-reporting-flow-engine: ships patches but doesn't apply them)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 19:21:31 + with message-id and subject line Bug#1022105: fixed in pentaho-reporting-flow-engine 0.9.4-5.2 has caused the Debian Bug report #1022105, regarding pentaho-reporting-flow-engine: ships patches but doesn't apply them to be marked as done. This mea

Bug#1007086: marked as done (pentaho-reporting-flow-engine: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 19:21:31 + with message-id and subject line Bug#1007086: fixed in pentaho-reporting-flow-engine 0.9.4-5.2 has caused the Debian Bug report #1007086, regarding pentaho-reporting-flow-engine: please consider upgrading to 3.0 source format to be marked as done

Bug#1065305: marked as done (brewtarget: switch to boost 1.83)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 19:19:14 + with message-id and subject line Bug#1065305: fixed in brewtarget 3.0.11-1 has caused the Debian Bug report #1065305, regarding brewtarget: switch to boost 1.83 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1007672: marked as done (poe.app: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 19:06:57 + with message-id and subject line Bug#1007672: fixed in poe.app 0.5.1-6.1 has caused the Debian Bug report #1007672, regarding poe.app: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the problem

Bug#1068213: marked as done (gnome-remote-desktop: hard-coded dependency on pre-t64 library)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 18:04:25 + with message-id and subject line Bug#1068213: fixed in gnome-remote-desktop 44.2-8 has caused the Debian Bug report #1068213, regarding gnome-remote-desktop: hard-coded dependency on pre-t64 library to be marked as done. This means that you claim

Bug#1058745: marked as done (debvm enables accel=kvm:tcg on ppc64el despite not available/working)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 2 Apr 2024 20:02:59 +0200 with message-id <20240402180259.ga2231...@subdivi.de> and subject line Re: Bug#1058745: debvm enables accel=kvm:tcg on ppc64el despite not available/working has caused the Debian Bug report #1058745, regarding debvm enables accel=kvm:tcg on ppc64el

Bug#1068166: marked as done (manpages-dev: Fails to upgrade due to file conflict)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 16:50:01 + with message-id and subject line Bug#1068166: fixed in manpages 6.7-2 has caused the Debian Bug report #1068166, regarding manpages-dev: Fails to upgrade due to file conflict to be marked as done. This means that you claim that the problem has be

Bug#1068167: marked as done (manpages-dev: Update to 6.7-1 fails)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 16:50:01 + with message-id and subject line Bug#1068166: fixed in manpages 6.7-2 has caused the Debian Bug report #1068166, regarding manpages-dev: Update to 6.7-1 fails to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1066194: marked as done (nstreams: FTBFS: parse_tcpdump.c:262:50: error: implicit declaration of function ‘int2proto’ [-Werror=implicit-function-declaration])

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 16:34:58 + with message-id and subject line Bug#1066194: fixed in nstreams 1.0.4-1.1 has caused the Debian Bug report #1066194, regarding nstreams: FTBFS: parse_tcpdump.c:262:50: error: implicit declaration of function ‘int2proto’ [-Werror=implicit-function

Bug#939158: marked as done (nstreams FTCBFS: uses the build architecture compiler)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 16:34:58 + with message-id and subject line Bug#939158: fixed in nstreams 1.0.4-1.1 has caused the Debian Bug report #939158, regarding nstreams FTCBFS: uses the build architecture compiler to be marked as done. This means that you claim that the problem ha

Bug#1007384: marked as done (nstreams: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 16:34:58 + with message-id and subject line Bug#1007384: fixed in nstreams 1.0.4-1.1 has caused the Debian Bug report #1007384, regarding nstreams: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the probl

Bug#1068243: marked as done (bsdgames: fails to configure)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 16:19:37 + with message-id and subject line Bug#1068243: fixed in bsdgames 2.17-32 has caused the Debian Bug report #1068243, regarding bsdgames: fails to configure to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1067378: marked as done (python-docs-theme: FTBFS: make: *** [debian/rules:4: build] Error 25)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 16:07:18 + with message-id and subject line Bug#1067378: fixed in python-docs-theme 2024.3-1 has caused the Debian Bug report #1067378, regarding python-docs-theme: FTBFS: make: *** [debian/rules:4: build] Error 25 to be marked as done. This means that you

Bug#1067076: marked as done (x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:53:44 + with message-id and subject line Bug#1067076: fixed in x11vnc 0.9.16-10 has caused the Debian Bug report #1067076, regarding x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’ to be marked as done

Bug#1064489: marked as done (python-packaging: please remove obsolete package python3-six from the build dependency)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:53:01 + with message-id and subject line Bug#1064489: fixed in python-packaging 24.0-1 has caused the Debian Bug report #1064489, regarding python-packaging: please remove obsolete package python3-six from the build dependency to be marked as done. This

Bug#1007576: marked as done (psgml: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:34:59 + with message-id and subject line Bug#1007576: fixed in psgml 1.4.0-12.1 has caused the Debian Bug report #1007576, regarding psgml: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the problem ha

Bug#1068222: marked as done (libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:34:12 + with message-id and subject line Bug#1068222: fixed in appmenu-gtk-module 0.7.6-3 has caused the Debian Bug report #1068222, regarding libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. Th

Bug#1067391: marked as done (bitlbee-facebook: redundant dependency on libglib2.0-0)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:34:22 + with message-id and subject line Bug#1067391: fixed in bitlbee-facebook 1.2.2-3 has caused the Debian Bug report #1067391, regarding bitlbee-facebook: redundant dependency on libglib2.0-0 to be marked as done. This means that you claim that the p

Bug#1064028: marked as done (libpython3.12-dev: non-C90 headerfile code breaks -Werror=declaration-after-statement)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:22:15 + with message-id and subject line Bug#1064028: fixed in python3.12 3.12.2-5 has caused the Debian Bug report #1064028, regarding libpython3.12-dev: non-C90 headerfile code breaks -Werror=declaration-after-statement to be marked as done. This mean

Bug#1063905: marked as done (mksh: add /usr/bin/mksh{,-static} to /etc/shells)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:20:57 + with message-id and subject line Bug#1063905: fixed in mksh 59c-35 has caused the Debian Bug report #1063905, regarding mksh: add /usr/bin/mksh{,-static} to /etc/shells to be marked as done. This means that you claim that the problem has been dea

Bug#1068240: marked as done (nauty: autopkgtest regression in testing)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:05:06 + with message-id and subject line Bug#1068240: fixed in nauty 2.8.8+ds-3 has caused the Debian Bug report #1068240, regarding nauty: autopkgtest regression in testing to be marked as done. This means that you claim that the problem has been dealt

Bug#1019738: marked as done (searchandrescue: FTBFS on riscv64: add library search path)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:05:25 + with message-id and subject line Bug#1019738: fixed in searchandrescue 1.5.0+dfsg-0.1 has caused the Debian Bug report #1019738, regarding searchandrescue: FTBFS on riscv64: add library search path to be marked as done. This means that you claim

Bug#1007284: marked as done (searchandrescue: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 15:05:25 + with message-id and subject line Bug#1007284: fixed in searchandrescue 1.5.0+dfsg-0.1 has caused the Debian Bug report #1007284, regarding searchandrescue: please consider upgrading to 3.0 source format to be marked as done. This means that you c

Bug#1065438: marked as done (O: gnu-which -- Utility to show the full path of commands)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 14:34:09 + with message-id and subject line Bug#1065438: fixed in gnu-which 2.21+dfsg-5 has caused the Debian Bug report #1065438, regarding O: gnu-which -- Utility to show the full path of commands to be marked as done. This means that you claim that the p

Bug#1064905: marked as done (Why is cyrus_sasl_config_path ignored in bookworm and older releases? The README.Debian.gz only states "For policy reasons: a. SASL configuration goes in /etc/postfix/sasl

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 10:14:18 -0400 with message-id <2479856.1ts7lmlHNH@localhost> and subject line Re: Why is cyrus_sasl_config_path ignored in bookworm and older releases? The README.Debian.gz only states "For policy reasons: a. SASL configuration goes in /etc/postfix/sasl" but d

Processed: your mail

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1067226 1068140 Bug #1067226 {Done: Doug Torrance } [src:flint] flint: libflint needs soversion bump to 19 Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /l

Bug#1063773: marked as done (postfix-mysql upgrade add dynamicmaps.cf after postfix restart)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 13:34:58 + with message-id and subject line Bug#1063772: fixed in postfix 3.9.0-2 has caused the Debian Bug report #1063772, regarding postfix-mysql upgrade add dynamicmaps.cf after postfix restart to be marked as done. This means that you claim that the pr

Bug#1067483: marked as done (postfix: please make the build reproducible)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 13:34:58 + with message-id and subject line Bug#1067483: fixed in postfix 3.9.0-2 has caused the Debian Bug report #1067483, regarding postfix: please make the build reproducible to be marked as done. This means that you claim that the problem has been deal

Bug#1063772: marked as done (postfix-mysql upgrade add map in dynamicmaps.cf after postfix restart)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 13:34:58 + with message-id and subject line Bug#1063772: fixed in postfix 3.9.0-2 has caused the Debian Bug report #1063772, regarding postfix-mysql upgrade add map in dynamicmaps.cf after postfix restart to be marked as done. This means that you claim that

Bug#1007663: marked as done (searchandrescue-data: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 13:04:22 + with message-id and subject line Bug#1007663: fixed in searchandrescue-data 1.3.0-1.2 has caused the Debian Bug report #1007663, regarding searchandrescue-data: please consider upgrading to 3.0 source format to be marked as done. This means that

Bug#1007624: marked as done (imaprowl: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 12:34:26 + with message-id and subject line Bug#1007624: fixed in imaprowl 1.2.1-1.3 has caused the Debian Bug report #1007624, regarding imaprowl: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the probl

Processed: closing 1067339

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1067339 Bug #1067339 [src:deal.ii] deal.ii: FTBFS: unsatisfiable build-dependencies Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1067339: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#1068181: marked as done (asunder: Asunder package calls wavpack version not present (5.6.0-1+b1). 5.7.0-1 in repo. Cannot install.)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 2 Apr 2024 13:06:52 +0100 with message-id <0a304c2f-99a8-479f-86fc-bb63e2e98...@pblackman.plus.com> and subject line Re: Bug#1068181: asunder: Asunder package calls wavpack version not present (5.6.0-1+b1). 5.7.0-1 in repo. Cannot install. has caused the Debian Bug report #

Bug#999881: marked as done (stone FTCBFS: does not pass cross tools to make)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 12:05:01 + with message-id and subject line Bug#999881: fixed in stone 2.4-1.1 has caused the Debian Bug report #999881, regarding stone FTCBFS: does not pass cross tools to make to be marked as done. This means that you claim that the problem has been deal

Bug#626252: marked as done (stone: POP->APOP conversion is disabled despite of the package description)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 12:05:01 + with message-id and subject line Bug#626252: fixed in stone 2.4-1.1 has caused the Debian Bug report #626252, regarding stone: POP->APOP conversion is disabled despite of the package description to be marked as done. This means that you claim th

Bug#403401: marked as done (stone: FTBFS on GNU/Hurd)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 12:05:01 + with message-id and subject line Bug#403401: fixed in stone 2.4-1.1 has caused the Debian Bug report #403401, regarding stone: FTBFS on GNU/Hurd to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1007330: marked as done (stone: please consider upgrading to 3.0 source format)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 12:05:01 + with message-id and subject line Bug#1007330: fixed in stone 2.4-1.1 has caused the Debian Bug report #1007330, regarding stone: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the problem has b

Bug#1068228: marked as done (libreoffice-core: fails to open any documents (ods/odt) after latest upgrades, missing components)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 13:54:06 +0200 with message-id and subject line Re: Bug#1068228: libreoffice-core: fails to open any documents (ods/odt) after latest upgrades, missing components has caused the Debian Bug report #1068228, regarding libreoffice-core: fails to open any documents

Bug#1066638: marked as done (ukui-screensaver: FTBFS: kylin-network-interface.c:199:5: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declarati

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 11:55:00 + with message-id and subject line Bug#1066638: fixed in ukui-screensaver 3.0.3.3-1 has caused the Debian Bug report #1066638, regarding ukui-screensaver: FTBFS: kylin-network-interface.c:199:5: error: implicit declaration of function ‘asprintf’; d

Bug#1067987: marked as done (pyopencl: Please replace python3-appdirs dependency with platformdirs)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 11:19:42 + with message-id and subject line Bug#1067987: fixed in pyopencl 2024.1-1 has caused the Debian Bug report #1067987, regarding pyopencl: Please replace python3-appdirs dependency with platformdirs to be marked as done. This means that you claim th

Bug#1065865: marked as done (gdal: Please drop dependencies on python3-distutils)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 11:19:32 + with message-id and subject line Bug#1065865: fixed in gdal 3.8.5~rc1+dfsg-1~exp1 has caused the Debian Bug report #1065865, regarding gdal: Please drop dependencies on python3-distutils to be marked as done. This means that you claim that the pr

Bug#1068067: marked as done (fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed)))

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 11:04:20 + with message-id and subject line Bug#1068067: fixed in fpzip 1.3.0-4 has caused the Debian Bug report #1068067, regarding fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed)) to be marked as done. This means that you cl

Bug#1067778: marked as done (retroarch ftbfs in unstable)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 10:35:41 + with message-id and subject line Bug#1064681: fixed in retroarch 1.18.0+dfsg-1 has caused the Debian Bug report #1064681, regarding retroarch ftbfs in unstable to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1064681: marked as done (retroarch: FTBFS: glslang is disabled and forced to build with SPIRV-Cross support.)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 10:35:41 + with message-id and subject line Bug#1064681: fixed in retroarch 1.18.0+dfsg-1 has caused the Debian Bug report #1064681, regarding retroarch: FTBFS: glslang is disabled and forced to build with SPIRV-Cross support. to be marked as done. This me

Bug#1055857: marked as done (transition: opm-common)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 2 Apr 2024 10:04:51 +0200 with message-id and subject line transition: opm-common not needed anymore has caused the Debian Bug report #1055857, regarding transition: opm-common to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1054486: marked as done (sogo: installs sogo.service twice once dh_installsystemd installs to /usr)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 10:20:52 +0200 with message-id and subject line Fixed in 5.9.1-1 has caused the Debian Bug report #1054486, regarding sogo: installs sogo.service twice once dh_installsystemd installs to /usr to be marked as done. This means that you claim that the problem has

Processed: closing 1055288

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1055288 Bug #1055288 [wnpp] ITP: gnome-video-trimmer -- Simple GUI application for lossless cutting of video files Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1055288: https://bugs.de

Bug#1068175: marked as done (Fix dracut 059 producing broken unified kernel images with systemd 254)

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 2 Apr 2024 10:13:42 +0200 with message-id <26123.48694.628752.825...@cs.uni-koeln.de> and subject line Re: Bug#1068175: Fix dracut 059 producing broken unified kernel images with systemd 254 has caused the Debian Bug report #1068175, regarding Fix dracut 059 producing broke

Bug#1066555: marked as done (kylin-nm: FTBFS: src/kylin-network-interface.c:197:5: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])

2024-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2024 07:34:12 + with message-id and subject line Bug#1066555: fixed in kylin-nm 3.0.3.1-1 has caused the Debian Bug report #1066555, regarding kylin-nm: FTBFS: src/kylin-network-interface.c:197:5: error: implicit declaration of function ‘asprintf’; did you mean