Bug#1068424: marked as done (populations - still depends on old libqt5gui5 after binnmu)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 06:50:12 + with message-id and subject line Bug#1068424: fixed in populations 1.2.33+svn0120106+dfsg-6ubuntu3 has caused the Debian Bug report #1068424, regarding populations - still depends on old libqt5gui5 after binnmu to be marked as done. This means t

Bug#1067572: marked as done (rust-parsec-tool: Testsuite fails with openssl 3.2)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 05:19:03 + with message-id and subject line Bug#1067572: fixed in rust-parsec-tool 0.7.0-4 has caused the Debian Bug report #1067572, regarding rust-parsec-tool: Testsuite fails with openssl 3.2 to be marked as done. This means that you claim that the probl

Bug#1067352: marked as done (mtail: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 04:34:40 + with message-id and subject line Bug#1067352: fixed in mtail 3.0.0~rc54+git0ff5-1 has caused the Debian Bug report #1067352, regarding mtail: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25 to be marked as done. This means

Bug#1032628: marked as done (please drop transitional package libapache2-mod-proxy-uwsgi from src:apache2)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 04:34:28 + with message-id and subject line Bug#1032628: fixed in apache2 2.4.59-1 has caused the Debian Bug report #1032628, regarding please drop transitional package libapache2-mod-proxy-uwsgi from src:apache2 to be marked as done. This means that you c

Bug#1054564: marked as done (apache2: mod_proxy_connect insecure default server-wide AllowCONNECT value)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 04:34:28 + with message-id and subject line Bug#1054564: fixed in apache2 2.4.59-1 has caused the Debian Bug report #1054564, regarding apache2: mod_proxy_connect insecure default server-wide AllowCONNECT value to be marked as done. This means that you cla

Bug#1049548: marked as done (node-graphql: Fails to build binary packages again after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 04:04:10 + with message-id and subject line Bug#1049548: fixed in node-graphql 16.8.1-2 has caused the Debian Bug report #1049548, regarding node-graphql: Fails to build binary packages again after successful build to be marked as done. This means that you

Bug#1061860: marked as done (xapers fails its autopkg tests with Python 3.12)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 04:04:55 + with message-id and subject line Bug#1061860: fixed in xapers 0.9.0-3 has caused the Debian Bug report #1061860, regarding xapers fails its autopkg tests with Python 3.12 to be marked as done. This means that you claim that the problem has been d

Bug#1046929: marked as done (node-graphql: Fails to build source after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 04:04:09 + with message-id and subject line Bug#1046929: fixed in node-graphql 16.8.1-2 has caused the Debian Bug report #1046929, regarding node-graphql: Fails to build source after successful build to be marked as done. This means that you claim that the

Bug#1066511: marked as done (photopc: FTBFS: fnames.c:118:21: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 02:36:37 + with message-id and subject line Bug#1066511: fixed in photopc 3.07-3 has caused the Debian Bug report #1066511, regarding photopc: FTBFS: fnames.c:118:21: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration] t

Bug#1066387: marked as done (gkermit: FTBFS: gkermit.c:350:7: error: implicit declaration of function ‘sleep’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 02:34:31 + with message-id and subject line Bug#1066387: fixed in gkermit 2.01-4 has caused the Debian Bug report #1066387, regarding gkermit: FTBFS: gkermit.c:350:7: error: implicit declaration of function ‘sleep’ [-Werror=implicit-function-declaration] to

Bug#925358: marked as done (qemu-user-static: mis-emulates something to do with process/signal handling (m68k, s390x, …))

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 5 Apr 2024 02:23:01 + (UTC) with message-id and subject line Re: Bug#925358: qemu-user-static: mis-emulates something to do with process/signal handling (m68k, s390x, …) has caused the Debian Bug report #925358, regarding qemu-user-static: mis-emulates something to do

Bug#1068311: marked as done (tcp-wrappers: Can anything be done to avoid the libnsl dependency?)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 01:49:14 + with message-id and subject line Bug#1068311: fixed in tcp-wrappers 7.6.q-33 has caused the Debian Bug report #1068311, regarding tcp-wrappers: Can anything be done to avoid the libnsl dependency? to be marked as done. This means that you claim t

Bug#1066614: marked as done (splitvt: FTBFS: vt100.c:146:16: error: implicit declaration of function ‘check_attr’; did you mean ‘set_attr’? [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 01:35:07 + with message-id and subject line Bug#1066614: fixed in splitvt 1.6.6-16 has caused the Debian Bug report #1066614, regarding splitvt: FTBFS: vt100.c:146:16: error: implicit declaration of function ‘check_attr’; did you mean ‘set_attr’? [-Werror=

Bug#1068420: marked as done (pidgin-gnome-keyring - still depends on old libpurple after binnmu)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 01:05:59 + with message-id and subject line Bug#1068420: fixed in pidgin-gnome-keyring 2.0-3 has caused the Debian Bug report #1068420, regarding pidgin-gnome-keyring - still depends on old libpurple after binnmu to be marked as done. This means that you cl

Bug#667930: marked as done (epm: CPPFLAGS hardening flags missing)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 00:49:31 + with message-id and subject line Bug#667930: fixed in epm 4.2-12 has caused the Debian Bug report #667930, regarding epm: CPPFLAGS hardening flags missing to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1066241: marked as done (epm: FTBFS: mantohtml.c:230:27: error: implicit declaration of function ‘tolower’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 00:49:31 + with message-id and subject line Bug#1066241: fixed in epm 4.2-12 has caused the Debian Bug report #1066241, regarding epm: FTBFS: mantohtml.c:230:27: error: implicit declaration of function ‘tolower’ [-Werror=implicit-function-declaration] to be

Bug#1044273: marked as done (epm: Fails to build source after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 00:49:31 + with message-id and subject line Bug#1044273: fixed in epm 4.2-12 has caused the Debian Bug report #1044273, regarding epm: Fails to build source after successful build to be marked as done. This means that you claim that the problem has been dea

Bug#1047100: marked as done (wily: Fails to build source after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 23:51:05 + with message-id and subject line Bug#1047100: fixed in wily 0.13.42-2 has caused the Debian Bug report #1047100, regarding wily: Fails to build source after successful build to be marked as done. This means that you claim that the problem has bee

Bug#1066343: marked as done (wily: FTBFS: getrect.c:27:17: error: implicit declaration of function ‘sleep’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 23:51:05 + with message-id and subject line Bug#1066343: fixed in wily 0.13.42-2 has caused the Debian Bug report #1066343, regarding wily: FTBFS: getrect.c:27:17: error: implicit declaration of function ‘sleep’ [-Werror=implicit-function-declaration] to be

Bug#1067561: marked as done (FTBFS: Error: symbol `open64' is already defined)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 23:04:55 + with message-id and subject line Bug#1067561: fixed in lightdm 1.32.0-5~exp1 has caused the Debian Bug report #1067561, regarding FTBFS: Error: symbol `open64' is already defined to be marked as done. This means that you claim that the problem ha

Bug#1066866: marked as done (railway-gtk: FTBFS on i386 "type annotations needed")

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 23:05:52 + with message-id and subject line Bug#1066866: fixed in railway-gtk 2.4.0-2 has caused the Debian Bug report #1066866, regarding railway-gtk: FTBFS on i386 "type annotations needed" to be marked as done. This means that you claim that the problem

Bug#1007664: marked as done (lpr: please consider upgrading to 3.0 source format)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 22:52:00 + with message-id and subject line Bug#1007664: fixed in lpr 1:2008.05.17.3+nmu2 has caused the Debian Bug report #1007664, regarding lpr: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the probl

Bug#1066108: marked as done (intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575 CVE-2023-22655 CVE-2023-28746)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 22:47:12 + with message-id and subject line Bug#1066108: fixed in intel-microcode 3.20240312.1~deb12u1 has caused the Debian Bug report #1066108, regarding intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575 CVE-2023-22655 CVE-2023-28746 to be mar

Bug#1060407: marked as done (Multiple security issues)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 22:47:08 + with message-id and subject line Bug#1060407: fixed in gtkwave 3.3.118-0.1~deb12u1 has caused the Debian Bug report #1060407, regarding Multiple security issues to be marked as done. This means that you claim that the problem has been dealt with.

Bug#977940: marked as done (logtools FTCBFS: does not pass --host to configure)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 22:22:46 + with message-id and subject line Bug#977940: fixed in logtools 0.13e+nmu3 has caused the Debian Bug report #977940, regarding logtools FTCBFS: does not pass --host to configure to be marked as done. This means that you claim that the problem has

Bug#1007513: marked as done (logtools: please consider upgrading to 3.0 source format)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 22:22:46 + with message-id and subject line Bug#1007513: fixed in logtools 0.13e+nmu3 has caused the Debian Bug report #1007513, regarding logtools: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the prob

Bug#1066521: marked as done (weplab: FTBFS: analpfile.c:105:21: error: implicit declaration of function ‘GetPacketBssid’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 22:06:11 + with message-id and subject line Bug#1066521: fixed in weplab 0.1.5-7 has caused the Debian Bug report #1066521, regarding weplab: FTBFS: analpfile.c:105:21: error: implicit declaration of function ‘GetPacketBssid’ [-Werror=implicit-function-decl

Bug#1067461: marked as done (libvirt: CVE-2024-2494)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 21:51:16 + with message-id and subject line Bug#1067461: fixed in libvirt 10.2.0-1 has caused the Debian Bug report #1067461, regarding libvirt: CVE-2024-2494 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#1007071: marked as done (lockfile-progs: please consider upgrading to 3.0 source format)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 21:51:23 + with message-id and subject line Bug#1007071: fixed in lockfile-progs 0.1.19+nmu1 has caused the Debian Bug report #1007071, regarding lockfile-progs: please consider upgrading to 3.0 source format to be marked as done. This means that you claim

Bug#1068400: marked as done (lomiri-filemanager-app dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 21:34:42 + with message-id and subject line Bug#1068400: fixed in lomiri-filemanager-app 1.0.4+dfsg-2 has caused the Debian Bug report #1068400, regarding lomiri-filemanager-app dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as do

Bug#1068399: marked as done (lomiri-system-settings - uninstallable on armel, armhf and mips64el due to depends/build-depends cycles.)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 21:34:51 + with message-id and subject line Bug#1068399: fixed in lomiri-system-settings-security-privacy 1.0.2-3 has caused the Debian Bug report #1068399, regarding lomiri-system-settings - uninstallable on armel, armhf and mips64el due to depends/build-

Bug#1007318: marked as done (keyboards-rg: please consider upgrading to 3.0 source format)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 21:34:10 + with message-id and subject line Bug#1007318: fixed in keyboards-rg 0.3+nmu2 has caused the Debian Bug report #1007318, regarding keyboards-rg: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that th

Bug#1066116: marked as done (libssl3: 3.1.4-2 NEWS entry seems incorrect)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 21:21:26 + with message-id and subject line Bug#1066116: fixed in openssl 3.2.1-3 has caused the Debian Bug report #1066116, regarding libssl3: 3.1.4-2 NEWS entry seems incorrect to be marked as done. This means that you claim that the problem has been deal

Bug#1007497: marked as done (ifupdown-extra: please consider upgrading to 3.0 source format)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 21:04:11 + with message-id and subject line Bug#1007497: fixed in ifupdown-extra 0.33+nmu2 has caused the Debian Bug report #1007497, regarding ifupdown-extra: please consider upgrading to 3.0 source format to be marked as done. This means that you claim th

Bug#1066352: marked as done (tla: FTBFS: cmd-apply-delta.c:307:3: error: implicit declaration of function ‘arch_merge3’; did you mean ‘arch_cmd_get’? [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 20:49:22 + with message-id and subject line Bug#1066352: fixed in tla 1.3.5+dfsg1-3 has caused the Debian Bug report #1066352, regarding tla: FTBFS: cmd-apply-delta.c:307:3: error: implicit declaration of function ‘arch_merge3’; did you mean ‘arch_cmd_get’?

Bug#1046988: marked as done (tla: Fails to build source after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 20:49:22 + with message-id and subject line Bug#1046988: fixed in tla 1.3.5+dfsg1-3 has caused the Debian Bug report #1046988, regarding tla: Fails to build source after successful build to be marked as done. This means that you claim that the problem has b

Bug#1042967: marked as done (nheko crashes on first launch in arm64 (librem 5))

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 20:35:09 + with message-id and subject line Bug#1042967: fixed in nheko 0.11.3+~0.9.2+~1.0.0+~0.3.0-2 has caused the Debian Bug report #1042967, regarding nheko crashes on first launch in arm64 (librem 5) to be marked as done. This means that you claim that

Bug#715806: marked as done ([hp-ppd] refers to removed package linuxprinting.org-ppds in extended description)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 20:34:39 + with message-id and subject line Bug#715806: fixed in hp-ppd 0.9+nmu2 has caused the Debian Bug report #715806, regarding [hp-ppd] refers to removed package linuxprinting.org-ppds in extended description to be marked as done. This means that you

Bug#1007683: marked as done (fortunes-bg: please consider upgrading to 3.0 source format)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 20:34:14 + with message-id and subject line Bug#1007683: fixed in fortunes-bg 1.4+nmu1 has caused the Debian Bug report #1007683, regarding fortunes-bg: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the

Bug#1007459: marked as done (hp-ppd: please consider upgrading to 3.0 source format)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 20:34:39 + with message-id and subject line Bug#1007459: fixed in hp-ppd 0.9+nmu2 has caused the Debian Bug report #1007459, regarding hp-ppd: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the problem ha

Bug#1064593: marked as done (debian-policy: missing static resources for www.debian.org policy page)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 19:51:23 + with message-id <660f04bbdfb33_1408bb94c-...@godard.mail> and subject line Bug#1064593 fixed in www.debian.org has caused the Debian Bug report #1064593, regarding debian-policy: missing static resources for www.debian.org policy page to be marked

Bug#1007066: marked as done (dh-buildinfo: please consider upgrading to 3.0 source format)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 19:34:06 + with message-id and subject line Bug#1007066: fixed in dh-buildinfo 0.11+nmu3 has caused the Debian Bug report #1007066, regarding dh-buildinfo: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that t

Bug#1068345: marked as done (trixie-pu: package chromium/123.0.6312.105-1~deb13u1)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 4 Apr 2024 21:29:46 +0200 with message-id and subject line Re: trixie-pu: package chromium/123.0.6312.105-1~deb13u1 has caused the Debian Bug report #1068345, regarding trixie-pu: package chromium/123.0.6312.105-1~deb13u1 to be marked as done. This means that you claim tha

Bug#985218: marked as done (package-supports-alternative-init-but-no-init.d-script is outdated)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 4 Apr 2024 22:06:55 +0300 with message-id and subject line Re: Bug#985218: package-supports-alternative-init-but-no-init.d-script is outdated has caused the Debian Bug report #985218, regarding package-supports-alternative-init-but-no-init.d-script is outdated to be marked

Bug#1065897: marked as done (link-grammar: Please drop dependencies on python3-distutils)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 18:00:17 + with message-id and subject line Bug#1065897: fixed in link-grammar 5.12.4~dfsg-1 has caused the Debian Bug report #1065897, regarding link-grammar: Please drop dependencies on python3-distutils to be marked as done. This means that you claim tha

Bug#1062748: marked as done (link-grammar: NMU diff for 64-bit time_t transition)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 18:00:17 + with message-id and subject line Bug#1062748: fixed in link-grammar 5.12.4~dfsg-1 has caused the Debian Bug report #1062748, regarding link-grammar: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the pr

Bug#1047439: marked as done (link-grammar: Fails to build source after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 18:00:17 + with message-id and subject line Bug#1047439: fixed in link-grammar 5.12.4~dfsg-1 has caused the Debian Bug report #1047439, regarding link-grammar: Fails to build source after successful build to be marked as done. This means that you claim that

Processed: RFS: libtypec/0.4-4 [RFP] -- Development files for an interface for USB-C port management

2024-04-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1041327 Bug #1041327 [sponsorship-requests] RFS: libtypec/0.4-4 [RFP] -- Development files for an interface for USB-C port management Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1041327

Bug#1068341: marked as done (bioawk: FTBFS randomly due to Makefile bug: cp: cannot create regular file 'ytab.c': File exists)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 17:34:05 + with message-id and subject line Bug#1068341: fixed in bioawk 1.0-5 has caused the Debian Bug report #1068341, regarding bioawk: FTBFS randomly due to Makefile bug: cp: cannot create regular file 'ytab.c': File exists to be marked as done. This

Bug#1066426: marked as done (xshisen: FTBFS: main.C:149:71: error: ‘rand’ was not declared in this scope)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 17:20:57 + with message-id and subject line Bug#1066426: fixed in xshisen 1:1.51-8 has caused the Debian Bug report #1066426, regarding xshisen: FTBFS: main.C:149:71: error: ‘rand’ was not declared in this scope to be marked as done. This means that you cl

Bug#1003064: marked as done (xshisen: cannot show the personal score)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 17:20:57 + with message-id and subject line Bug#1003064: fixed in xshisen 1:1.51-8 has caused the Debian Bug report #1003064, regarding xshisen: cannot show the personal score to be marked as done. This means that you claim that the problem has been dealt w

Bug#1066617: marked as done (xfrisk: FTBFS: aiStubs.c:88:45: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 16:51:53 + with message-id and subject line Bug#1066617: fixed in xfrisk 1.2-9 has caused the Debian Bug report #1066617, regarding xfrisk: FTBFS: aiStubs.c:88:45: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration] to be

Bug#1066550: marked as done (xscavenger: FTBFS: sound.c:158:9: error: implicit declaration of function ‘doall’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 16:35:17 + with message-id and subject line Bug#1066550: fixed in xscavenger 1.4.5-6 has caused the Debian Bug report #1066550, regarding xscavenger: FTBFS: sound.c:158:9: error: implicit declaration of function ‘doall’ [-Werror=implicit-function-declaratio

Processed: closing 837205

2024-04-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 837205 Bug #837205 [python-ofxclient] python-ofxclient: beautifulsoup warning Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 837205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8372

Bug#900194: marked as done (bluemon FTCBFS: fails finding dbus-1.pc with the build architecture pkg-config)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 16:19:02 + with message-id and subject line Bug#900194: fixed in bluemon 1.4-9 has caused the Debian Bug report #900194, regarding bluemon FTCBFS: fails finding dbus-1.pc with the build architecture pkg-config to be marked as done. This means that you clai

Bug#1066509: marked as done (dmitry: FTBFS: src/file.c:4:20: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 16:19:44 + with message-id and subject line Bug#1066509: fixed in dmitry 1.3a-3 has caused the Debian Bug report #1066509, regarding dmitry: FTBFS: src/file.c:4:20: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration] to

Bug#1066330: marked as done (bluemon: FTBFS: bluemon-query.c:46:15: error: implicit declaration of function ‘strncmp’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 16:19:02 + with message-id and subject line Bug#1066330: fixed in bluemon 1.4-9 has caused the Debian Bug report #1066330, regarding bluemon: FTBFS: bluemon-query.c:46:15: error: implicit declaration of function ‘strncmp’ [-Werror=implicit-function-declarat

Processed: your mail

2024-04-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1067300 src:flint Bug #1067300 [src:pynormaliz] pynormaliz: FTBFS: ImportError: libflint.so.18: cannot open shared object file: No such file or directory Bug reassigned from package 'src:pynormaliz' to 'src:flint'. No longer marked as fo

Bug#1066408: marked as done (ncl: FTBFS: ld: cannot find -lncarg_c: No such file or directory)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 15:36:17 + with message-id and subject line Bug#1066408: fixed in ncl 6.6.2.dfsg.1-5 has caused the Debian Bug report #1066408, regarding ncl: FTBFS: ld: cannot find -lncarg_c: No such file or directory to be marked as done. This means that you claim that t

Bug#1021499: marked as done (fim: --slideshow=5 is buggy. doesn't show first picture, and 'q' doesn't quit)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 4 Apr 2024 15:25:34 + with message-id <20240404152534.GA22517@localhost> and subject line Re: Bug#1021499: fim: --slideshow=5 is buggy. doesn't show first picture, and 'q' doesn't quit has caused the Debian Bug report #1021499, regarding fim: --slideshow=5 is buggy. do

Bug#1066637: marked as done (cronolog: FTBFS: cronoutils.c:673:36: error: implicit declaration of function ‘strptime’; did you mean ‘strftime’? [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 15:34:03 + with message-id and subject line Bug#1066637: fixed in cronolog 1.6.2+rpk-4 has caused the Debian Bug report #1066637, regarding cronolog: FTBFS: cronoutils.c:673:36: error: implicit declaration of function ‘strptime’; did you mean ‘strftime’? [

Bug#1032978: marked as done (sshpass: new upstream version)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 15:20:57 + with message-id and subject line Bug#1032978: fixed in sshpass 1.10-0.1 has caused the Debian Bug report #1032978, regarding sshpass: new upstream version to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1066270: marked as done (convlit: FTBFS: litsections.c:332:14: error: implicit declaration of function ‘LZXinit’; did you mean ‘lzxd_init’? [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 14:34:20 + with message-id and subject line Bug#1066270: fixed in convlit 1.8-5 has caused the Debian Bug report #1066270, regarding convlit: FTBFS: litsections.c:332:14: error: implicit declaration of function ‘LZXinit’; did you mean ‘lzxd_init’? [-Werror

Bug#1046185: marked as done (snacc: Fails to build source after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 14:37:21 + with message-id and subject line Bug#1046185: fixed in snacc 1.3.1-10 has caused the Debian Bug report #1046185, regarding snacc: Fails to build source after successful build to be marked as done. This means that you claim that the problem has be

Bug#1066242: marked as done (snacc: FTBFS: parse-asn1.c:2716:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 14:37:21 + with message-id and subject line Bug#1066242: fixed in snacc 1.3.1-10 has caused the Debian Bug report #1066242, regarding snacc: FTBFS: parse-asn1.c:2716:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration]

Bug#1065981: marked as done (snacc: FTBFS on arm{el,hf}: parse-asn1.c:2716:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration])

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 14:37:21 + with message-id and subject line Bug#1065981: fixed in snacc 1.3.1-10 has caused the Debian Bug report #1065981, regarding snacc: FTBFS on arm{el,hf}: parse-asn1.c:2716:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-functio

Bug#1015664: marked as done (snacc: ftbfs with LTO (link time optimization) enabled)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 14:37:21 + with message-id and subject line Bug#1015664: fixed in snacc 1.3.1-10 has caused the Debian Bug report #1015664, regarding snacc: ftbfs with LTO (link time optimization) enabled to be marked as done. This means that you claim that the problem has

Bug#899328: marked as done (Updating the viruskiller Uploaders list)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:50:47 + with message-id and subject line Bug#899328: fixed in viruskiller 1.03-1+dfsg1-3 has caused the Debian Bug report #899328, regarding Updating the viruskiller Uploaders list to be marked as done. This means that you claim that the problem has been

Bug#1067365: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067373: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067343: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067357: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067351: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067338: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067336: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067328: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067322: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067314: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067307: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067302: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067280: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067261: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067279: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1067256: marked as done (gir-rust-code-generator: update for time_t changes)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:34:41 + with message-id and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2 has caused the Debian Bug report #1067256, regarding gir-rust-code-generator: update for time_t changes to be marked as done. This means that you claim that t

Bug#1064610: marked as done (python-fabio: please remove dependency on python3-six)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:19:20 + with message-id and subject line Bug#1064610: fixed in python-fabio 2023.10.0-1~exp1 has caused the Debian Bug report #1064610, regarding python-fabio: please remove dependency on python3-six to be marked as done. This means that you claim that t

Bug#1047799: marked as done (python-fabio: Fails to build source after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:19:20 + with message-id and subject line Bug#1047799: fixed in python-fabio 2023.10.0-1~exp1 has caused the Debian Bug report #1047799, regarding python-fabio: Fails to build source after successful build to be marked as done. This means that you claim t

Bug#1018820: marked as done (fabio-viewer: crash during file opening)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:19:20 + with message-id and subject line Bug#1018820: fixed in python-fabio 2023.10.0-1~exp1 has caused the Debian Bug report #1018820, regarding fabio-viewer: crash during file opening to be marked as done. This means that you claim that the problem has

Bug#1065089: marked as done (ITP: libwww-telegram-botapi-perl -- module of Telegram Bot API in Perl)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 12:00:10 + with message-id and subject line Bug#1065089: fixed in libwww-telegram-botapi-perl 0.12-1 has caused the Debian Bug report #1065089, regarding ITP: libwww-telegram-botapi-perl -- module of Telegram Bot API in Perl to be marked as done. This means

Bug#1067633: marked as done (RM: hdmi2usb-fx2-firmware -- ROM; FTBFS, unmaintained upstream, supporting old hardware)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 11:57:39 + with message-id and subject line Bug#1067633: Removed package(s) from unstable has caused the Debian Bug report #1067633, regarding RM: hdmi2usb-fx2-firmware -- ROM; FTBFS, unmaintained upstream, supporting old hardware to be marked as done. Thi

Bug#1067331: marked as done (hdmi2usb-fx2-firmware: FTBFS: sdcpp: fatal error: cannot execute 'cc1': execvp: No such file or directory)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 11:57:43 + with message-id and subject line Bug#1067633: Removed package(s) from unstable has caused the Debian Bug report #1067331, regarding hdmi2usb-fx2-firmware: FTBFS: sdcpp: fatal error: cannot execute 'cc1': execvp: No such file or directory to be ma

Bug#1067166: marked as done (RM: jellyfish [armel armhf hppa i386] -- ROM; scientific software & upstream doesn't suppport 32-bit systems)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 11:56:48 + with message-id and subject line Bug#1067166: Removed package(s) from unstable has caused the Debian Bug report #1067166, regarding RM: jellyfish [armel armhf hppa i386] -- ROM; scientific software & upstream doesn't suppport 32-bit systems to be

Bug#1068218: marked as done (RM: chipmunk/experimental -- ROM; cruft from the 64-bit time_t transition)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 11:53:25 + with message-id and subject line Bug#1068218: Removed package(s) from experimental has caused the Debian Bug report #1068218, regarding RM: chipmunk/experimental -- ROM; cruft from the 64-bit time_t transition to be marked as done. This means th

Bug#1067740: marked as done (RM: kylin-process-manager/experimental -- RoQA; superseeded by unstable; undeclared file conflict)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 11:52:01 + with message-id and subject line Bug#1067740: Removed package(s) from experimental has caused the Debian Bug report #1067740, regarding RM: kylin-process-manager/experimental -- RoQA; superseeded by unstable; undeclared file conflict to be marked

Bug#1068090: marked as done (Update Build-Depends for the time64 library renames)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 11:49:47 + with message-id and subject line Bug#1068090: fixed in tetzle 2.2.3-1.1 has caused the Debian Bug report #1068090, regarding Update Build-Depends for the time64 library renames to be marked as done. This means that you claim that the problem has

Bug#1068381: marked as done (openapi-specification: please include examples in Debian package)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 11:34:30 + with message-id and subject line Bug#1068381: fixed in openapi-specification 3.1.0-2 has caused the Debian Bug report #1068381, regarding openapi-specification: please include examples in Debian package to be marked as done. This means that you c

Bug#1067138: marked as done (RM: spirv-llvm-translator-18/experimental -- RoM; NVIU; version in sid had a soname bump)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 4 Apr 2024 13:18:00 +0200 with message-id <3952da39-4915-add3-7ed6-a469f9693...@debian.org> and subject line Re: RM: spirv-llvm-translator-18/experimental -- RoM; NVIU; version in sid had a soname bump has caused the Debian Bug report #1067138, regarding RM: spirv-llvm-tran

Bug#1068075: marked as done (Update Build-Depends for the time64 library renames)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 09:21:55 + with message-id and subject line Bug#1068075: fixed in tanglet 1.6.5-2 has caused the Debian Bug report #1068075, regarding Update Build-Depends for the time64 library renames to be marked as done. This means that you claim that the problem has b

Bug#1067292: marked as done (prometheus-sql-exporter: FTBFS: make: *** [debian/rules:4: build] Error 25)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 09:06:27 + with message-id and subject line Bug#1067292: fixed in prometheus-sql-exporter 0.4.5-2 has caused the Debian Bug report #1067292, regarding prometheus-sql-exporter: FTBFS: make: *** [debian/rules:4: build] Error 25 to be marked as done. This mea

Bug#1068351: marked as done (libhdf4: Update to latest upstream version)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 08:37:28 + with message-id and subject line Bug#1068351: fixed in libhdf4 4.3.0-1~exp1 has caused the Debian Bug report #1068351, regarding libhdf4: Update to latest upstream version to be marked as done. This means that you claim that the problem has been

Bug#1068211: marked as done (pmix: FTBFS on 32 bit architectures: configure: WARNING: PMIx does not support 32 bit builds.)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 08:38:11 + with message-id and subject line Bug#1068211: fixed in pmix 5.0.2-2 has caused the Debian Bug report #1068211, regarding pmix: FTBFS on 32 bit architectures: configure: WARNING: PMIx does not support 32 bit builds. to be marked as done. This mea

  1   2   >