Bug#1063252: marked as done (pristine-tar: Always set the -T parameter for xz)

Your message dated Wed, 28 Feb 2024 07:51:02 + with message-id and subject line Bug#1063252: fixed in pristine-tar 1.50+nmu1 has caused the Debian Bug report #1063252, regarding pristine-tar: Always set the -T parameter for xz to be marked as done. This means that you claim that the problem h

Bug#1060940: marked as done (libfreemarker-java: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25)

Your message dated Wed, 28 Feb 2024 07:10:08 + with message-id and subject line Bug#1060940: fixed in libfreemarker-java 2.3.32-2 has caused the Debian Bug report #1060940, regarding libfreemarker-java: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25 to be marked as don

Bug#1062043: marked as done (cegui-mk2: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 07:06:39 + with message-id and subject line Bug#1062043: fixed in cegui-mk2 0.8.7+git20220615-5.1 has caused the Debian Bug report #1062043, regarding cegui-mk2: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the

Bug#1062041: marked as done (cbflib: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 06:30:44 + with message-id and subject line Bug#1062041: fixed in cbflib 0.9.7+dfsg1-3.1 has caused the Debian Bug report #1062041, regarding cbflib: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has

Bug#1062042: marked as done (cddlib: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 06:30:52 + with message-id and subject line Bug#1062042: fixed in cddlib 094m-1.1 has caused the Debian Bug report #1062042, regarding cddlib: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been de

Bug#1062036: marked as done (cal3d: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 06:29:57 + with message-id and subject line Bug#1062036: fixed in cal3d 0.11.0-8.1 has caused the Debian Bug report #1062036, regarding cal3d: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been de

Bug#1062038: marked as done (canl-c: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 06:30:13 + with message-id and subject line Bug#1062038: fixed in canl-c 3.0.0-4.1 has caused the Debian Bug report #1062038, regarding canl-c: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been d

Bug#1062037: marked as done (camp: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 06:30:06 + with message-id and subject line Bug#1062037: fixed in camp 0.8.4-4.1 has caused the Debian Bug report #1062037, regarding camp: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt

Bug#1062035: marked as done (c-vtapi: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 06:29:50 + with message-id and subject line Bug#1062035: fixed in c-vtapi 0.0~git20230329.226eda8-1.1 has caused the Debian Bug report #1062035, regarding c-vtapi: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that th

Bug#1064909: marked as done (libbsd-dev: Many functions (possibly all?) aren't available)

Your message dated Wed, 28 Feb 2024 06:05:09 + with message-id and subject line Bug#1064909: fixed in libbsd 0.12.1-1 has caused the Debian Bug report #1064909, regarding libbsd-dev: Many functions (possibly all?) aren't available to be marked as done. This means that you claim that the probl

Bug#1062034: marked as done (c-icap: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:56:19 + with message-id and subject line Bug#1062034: fixed in c-icap 1:0.5.10-6.1 has caused the Debian Bug report #1062034, regarding c-icap: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has bee

Bug#1062033: marked as done (c-blosc2: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:56:09 + with message-id and subject line Bug#1062033: fixed in c-blosc2 2.13.1+ds-1.1 has caused the Debian Bug report #1062033, regarding c-blosc2: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem ha

Bug#1062031: marked as done (bullet: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:55:59 + with message-id and subject line Bug#1062031: fixed in bullet 3.24+dfsg-2.1 has caused the Debian Bug report #1062031, regarding bullet: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has be

Bug#1062030: marked as done (btrfs-progs: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:55:45 + with message-id and subject line Bug#1062030: fixed in btrfs-progs 6.6.3-1.1 has caused the Debian Bug report #1062030, regarding btrfs-progs: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem

Bug#1062028: marked as done (brial: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:55:32 + with message-id and subject line Bug#1062028: fixed in brial 1.2.12-1.1 has caused the Debian Bug report #1062028, regarding brial: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been de

Bug#1062027: marked as done (boost1.83: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:55:21 + with message-id and subject line Bug#1062027: fixed in boost1.83 1.83.0-2.1 has caused the Debian Bug report #1062027, regarding boost1.83: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has

Bug#982309: marked as done (Session-Interactive-Only: no is equivalent to Session-Interactive-Only: yes)

Your message dated Wed, 28 Feb 2024 05:31:34 + with message-id and subject line Bug#982309: fixed in pam 1.5.3-4 has caused the Debian Bug report #982309, regarding Session-Interactive-Only: no is equivalent to Session-Interactive-Only: yes to be marked as done. This means that you claim tha

Bug#646692: marked as done (pam_umask: umask in /etc/login.defs not respected cause libpam_umask is not configured)

Your message dated Wed, 28 Feb 2024 05:31:34 + with message-id and subject line Bug#583958: fixed in pam 1.5.3-4 has caused the Debian Bug report #583958, regarding pam_umask: umask in /etc/login.defs not respected cause libpam_umask is not configured to be marked as done. This means that yo

Bug#583958: marked as done (enable pam_umask usergroups by default)

Your message dated Wed, 28 Feb 2024 05:31:34 + with message-id and subject line Bug#583958: fixed in pam 1.5.3-4 has caused the Debian Bug report #583958, regarding enable pam_umask usergroups by default to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1062802: marked as done (libpam0t64: file loss during upgrade due to /usr-move DEP17)

Your message dated Wed, 28 Feb 2024 05:31:35 + with message-id and subject line Bug#1062802: fixed in pam 1.5.3-4 has caused the Debian Bug report #1062802, regarding libpam0t64: file loss during upgrade due to /usr-move DEP17 to be marked as done. This means that you claim that the problem h

Bug#1061097: marked as done (pam: CVE-2024-22365: pam_namespace: protect_dir(): use O_DIRECTORY to prevent local DoS situations)

Your message dated Wed, 28 Feb 2024 05:31:35 + with message-id and subject line Bug#1061097: fixed in pam 1.5.3-4 has caused the Debian Bug report #1061097, regarding pam: CVE-2024-22365: pam_namespace: protect_dir(): use O_DIRECTORY to prevent local DoS situations to be marked as done. This

Bug#1060160: marked as done (pam: install into /usr (DEP17 M2))

Your message dated Wed, 28 Feb 2024 05:31:34 + with message-id and subject line Bug#1060160: fixed in pam 1.5.3-4 has caused the Debian Bug report #1060160, regarding pam: install into /usr (DEP17 M2) to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1057775: marked as done ([INTL:sv] Swedish strings for pam debconf)

Your message dated Wed, 28 Feb 2024 05:31:34 + with message-id and subject line Bug#1057775: fixed in pam 1.5.3-4 has caused the Debian Bug report #1057775, regarding [INTL:sv] Swedish strings for pam debconf to be marked as done. This means that you claim that the problem has been dealt with

Bug#1062551: marked as done (fcml: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:26:26 + with message-id and subject line Bug#1062551: fixed in fcml 1.3.0-1.1 has caused the Debian Bug report #1062551, regarding fcml: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt

Bug#1062553: marked as done (fenics-basix: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:26:34 + with message-id and subject line Bug#1062553: fixed in fenics-basix 0.7.0-2.1 has caused the Debian Bug report #1062553, regarding fenics-basix: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the proble

Bug#1062550: marked as done (fcft: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:26:16 + with message-id and subject line Bug#1062550: fixed in fcft 3.1.8-1.1 has caused the Debian Bug report #1062550, regarding fcft: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt

Bug#1062548: marked as done (faust: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:26:07 + with message-id and subject line Bug#1062548: fixed in faust 2.70.3+ds-1.1 has caused the Debian Bug report #1062548, regarding faust: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1061979: marked as done (boost1.74: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 05:16:42 + with message-id and subject line Bug#1061979: fixed in boost1.74 1.74.0+ds1-23.1 has caused the Debian Bug report #1061979, regarding boost1.74: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the proble

Bug#1062546: marked as done (fastcdr: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:48:01 + with message-id and subject line Bug#1062546: fixed in fastcdr 1.1.0-1.1 has caused the Debian Bug report #1062546, regarding fastcdr: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1062547: marked as done (fastdds: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:48:20 + with message-id and subject line Bug#1062547: fixed in fastdds 2.11.2+ds-6.1 has caused the Debian Bug report #1062547, regarding fastdds: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has

Bug#1062544: marked as done (faifa: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:47:53 + with message-id and subject line Bug#1062544: fixed in faifa 0.2~svn82-3.1 has caused the Debian Bug report #1062544, regarding faifa: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1062537: marked as done (emerald: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:41:41 + with message-id and subject line Bug#1062537: fixed in emerald 0.8.18-4.1 has caused the Debian Bug report #1062537, regarding emerald: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has bee

Bug#1062536: marked as done (elk: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:41:32 + with message-id and subject line Bug#1062536: fixed in elk 3.99.8-4.3 has caused the Debian Bug report #1062536, regarding elk: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt

Bug#1062528: marked as done (eiskaltdcpp: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:41:22 + with message-id and subject line Bug#1062528: fixed in eiskaltdcpp 2.4.2-1.1 has caused the Debian Bug report #1062528, regarding eiskaltdcpp: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem

Bug#1062540: marked as done (event-dance: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:42:10 + with message-id and subject line Bug#1062540: fixed in event-dance 0.2.0-2.1 has caused the Debian Bug report #1062540, regarding event-dance: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem

Bug#1062539: marked as done (evemu: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:42:01 + with message-id and subject line Bug#1062539: fixed in evemu 2.7.0-3.1 has caused the Debian Bug report #1062539, regarding evemu: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Bug#1062538: marked as done (eos-sdk: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:41:52 + with message-id and subject line Bug#1062538: fixed in eos-sdk 0~git20230107+ds-5.1 has caused the Debian Bug report #1062538, regarding eos-sdk: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the probl

Bug#1061934: marked as done (boinc: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:32:26 + with message-id and subject line Bug#1061934: fixed in boinc 7.24.1+dfsg-2.1 has caused the Debian Bug report #1061934, regarding boinc: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has be

Bug#1061932: marked as done (blitz++: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 04:31:51 + with message-id and subject line Bug#1061932: fixed in blitz++ 1:1.0.2+ds-4.1 has caused the Debian Bug report #1061932, regarding blitz++: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has

Bug#1046520: marked as done (mozjs102: Fails to build source after successful build)

Your message dated Wed, 28 Feb 2024 04:03:09 + with message-id and subject line Bug#1046520: fixed in mozjs115 115.8.0-2 has caused the Debian Bug report #1046520, regarding mozjs102: Fails to build source after successful build to be marked as done. This means that you claim that the problem

Bug#1064172: marked as done (mozjs102: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:52:35 + with message-id and subject line Bug#1064172: fixed in mozjs102 102.15.1-2 has caused the Debian Bug report #1064172, regarding mozjs102: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has b

Bug#1057637: marked as done (mozjs102: Please enable jit default in LoongArch)

Your message dated Wed, 28 Feb 2024 03:52:35 + with message-id and subject line Bug#1057637: fixed in mozjs102 102.15.1-2 has caused the Debian Bug report #1057637, regarding mozjs102: Please enable jit default in LoongArch to be marked as done. This means that you claim that the problem has

Bug#1062526: marked as done (efivar: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:39:34 + with message-id and subject line Bug#1062526: fixed in efivar 38-3.1 has caused the Debian Bug report #1062526, regarding efivar: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been deal

Bug#1062523: marked as done (edge-addition-planarity-suite: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:39:24 + with message-id and subject line Bug#1062523: fixed in edge-addition-planarity-suite 3.0.2.0-2.1 has caused the Debian Bug report #1062523, regarding edge-addition-planarity-suite: NMU diff for 64-bit time_t transition to be marked as done. This

Bug#1062520: marked as done (ecl: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:39:06 + with message-id and subject line Bug#1062520: fixed in ecl 21.2.1+ds-4.1 has caused the Debian Bug report #1062520, regarding ecl: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Bug#1062522: marked as done (eclib: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:39:16 + with message-id and subject line Bug#1062522: fixed in eclib 20231212-1.1 has caused the Debian Bug report #1062522, regarding eclib: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1062515: marked as done (eb: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:38:51 + with message-id and subject line Bug#1062515: fixed in eb 4.4.3-14.1 has caused the Debian Bug report #1062515, regarding eb: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1062179: marked as done (gnome-bluetooth: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:39:54 + with message-id and subject line Bug#1062179: fixed in gnome-bluetooth 3.34.5-12 has caused the Debian Bug report #1062179, regarding gnome-bluetooth: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the

Bug#1061930: marked as done (belle-sip: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:36:21 + with message-id and subject line Bug#1061930: fixed in belle-sip 5.2.0+dfsg-3.1 has caused the Debian Bug report #1061930, regarding belle-sip: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem

Bug#1061929: marked as done (bamf: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:36:11 + with message-id and subject line Bug#1061929: fixed in bamf 0.5.6+repack-1.1 has caused the Debian Bug report #1061929, regarding bamf: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has bee

Bug#1061927: marked as done (avogadrolibs: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:36:02 + with message-id and subject line Bug#1061927: fixed in avogadrolibs 1.99.0-3.1 has caused the Debian Bug report #1061927, regarding avogadrolibs: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the probl

Bug#1061925: marked as done (audacious: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:35:29 + with message-id and subject line Bug#1061925: fixed in audacious 4.3.1-2.1 has caused the Debian Bug report #1061925, regarding audacious: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has

Bug#1061926: marked as done (audit: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:35:40 + with message-id and subject line Bug#1061926: fixed in audit 1:3.1.2-2.1 has caused the Debian Bug report #1061926, regarding audit: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been d

Bug#1061924: marked as done (atril: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:35:19 + with message-id and subject line Bug#1061924: fixed in atril 1.26.2-1.1 has caused the Debian Bug report #1061924, regarding atril: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been de

Bug#1062135: marked as done (glibmm2.4: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:17:46 + with message-id and subject line Bug#1062135: fixed in glibmm2.4 2.66.6-3 has caused the Debian Bug report #1062135, regarding glibmm2.4: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has b

Bug#1062541: marked as done (evince: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:16:25 + with message-id and subject line Bug#1062541: fixed in evince 45.0-2 has caused the Debian Bug report #1062541, regarding evince: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been deal

Bug#1062513: marked as done (dyssol: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:16:12 + with message-id and subject line Bug#1062513: fixed in dyssol 1.1.1+ds1-2.1 has caused the Debian Bug report #1062513, regarding dyssol: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has be

Bug#1062500: marked as done (duo-unix: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:15:58 + with message-id and subject line Bug#1062500: fixed in duo-unix 1.11.3-1.1 has caused the Debian Bug report #1062500, regarding duo-unix: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has b

Bug#1062391: marked as done (dt-utils: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:15:49 + with message-id and subject line Bug#1062391: fixed in dt-utils 2021.03.0+ds-2.1 has caused the Debian Bug report #1062391, regarding dt-utils: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem

Bug#1062389: marked as done (dsdp: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:15:41 + with message-id and subject line Bug#1062389: fixed in dsdp 5.8-10.1 has caused the Debian Bug report #1062389, regarding dsdp: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt

Bug#1062388: marked as done (dsdcc: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:15:33 + with message-id and subject line Bug#1062388: fixed in dsdcc 1.9.3-2.1 has caused the Debian Bug report #1062388, regarding dsdcc: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Bug#1062127: marked as done (glade: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:17:14 + with message-id and subject line Bug#1062127: fixed in glade 3.40.0-4 has caused the Debian Bug report #1062127, regarding glade: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been deal

Bug#1062387: marked as done (drogon: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:15:23 + with message-id and subject line Bug#1062387: fixed in drogon 1.8.7+ds-1.1 has caused the Debian Bug report #1062387, regarding drogon: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has bee

Bug#1062378: marked as done (dnswire: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:15:14 + with message-id and subject line Bug#1062378: fixed in dnswire 0.4.0-3.1 has caused the Debian Bug report #1062378, regarding dnswire: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1062377: marked as done (dmlc-core: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:15:05 + with message-id and subject line Bug#1062377: fixed in dmlc-core 0.5-1.1 has caused the Debian Bug report #1062377, regarding dmlc-core: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has be

Bug#1061923: marked as done (at-spi2-core: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:02:40 + with message-id and subject line Bug#1061923: fixed in at-spi2-core 2.50.0-1.1 has caused the Debian Bug report #1061923, regarding at-spi2-core: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the probl

Bug#1061922: marked as done (astrometry.net: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:02:30 + with message-id and subject line Bug#1061922: fixed in astrometry.net 0.93+dfsg-1.1 has caused the Debian Bug report #1061922, regarding astrometry.net: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that th

Bug#1061921: marked as done (asl: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:02:14 + with message-id and subject line Bug#1061921: fixed in asl 0.1.7-4.1 has caused the Debian Bug report #1061921, regarding asl: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt w

Bug#1061919: marked as done (arpack: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:02:04 + with message-id and subject line Bug#1061919: fixed in arpack 3.9.1-1.1 has caused the Debian Bug report #1061919, regarding arpack: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been d

Bug#1061918: marked as done (armnn: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 03:01:52 + with message-id and subject line Bug#1061918: fixed in armnn 23.08-4.1 has caused the Debian Bug report #1061918, regarding armnn: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Processed: closing 1015231

Processing commands for cont...@bugs.debian.org: > close 1015231 Bug #1015231 [wnpp] ITP: sphinx-theme-builder -- tool for authoring Sphinx themes with a simple (opinionated) workflow Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1015231: htt

Bug#1062331: marked as done (ding-libs: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:08:31 + with message-id and subject line Bug#1062331: fixed in ding-libs 0.6.2-2.1 has caused the Debian Bug report #1062331, regarding ding-libs: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has

Bug#1062332: marked as done (directfb: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:08:50 + with message-id and subject line Bug#1062332: fixed in directfb 1.7.7-11.1 has caused the Debian Bug report #1062332, regarding directfb: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has b

Bug#1062022: marked as done (dcmtk: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:08:22 + with message-id and subject line Bug#1062022: fixed in dcmtk 3.6.7-9.1 has caused the Debian Bug report #1062022, regarding dcmtk: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Bug#1062021: marked as done (dcap: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:08:00 + with message-id and subject line Bug#1062021: fixed in dcap 2.47.14-1.1 has caused the Debian Bug report #1062021, regarding dcap: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Bug#1062019: marked as done (davix: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:06:56 + with message-id and subject line Bug#1062019: fixed in davix 0.8.5-1.1 has caused the Debian Bug report #1062019, regarding davix: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Bug#1062020: marked as done (db5.3: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:07:51 + with message-id and subject line Bug#1062020: fixed in db5.3 5.3.28+dfsg2-4.1 has caused the Debian Bug report #1062020, regarding db5.3: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has b

Bug#1061898: marked as done (arm-compute-library: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:06:08 + with message-id and subject line Bug#1061898: fixed in arm-compute-library 23.08+dfsg-3.1 has caused the Debian Bug report #1061898, regarding arm-compute-library: NMU diff for 64-bit time_t transition to be marked as done. This means that you cl

Bug#1061897: marked as done (aribb24: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:05:47 + with message-id and subject line Bug#1061897: fixed in aribb24 1.0.3-2.1 has caused the Debian Bug report #1061897, regarding aribb24: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1061895: marked as done (apriltag: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:05:30 + with message-id and subject line Bug#1061895: fixed in apriltag 3.3.0-2.1 has caused the Debian Bug report #1061895, regarding apriltag: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has be

Bug#1061893: marked as done (apr-util: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:05:20 + with message-id and subject line Bug#1061893: fixed in apr-util 1.6.3-1.1 has caused the Debian Bug report #1061893, regarding apr-util: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has be

Bug#1061894: marked as done (apr: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:05:09 + with message-id and subject line Bug#1061894: fixed in apr 1.7.2-3.1 has caused the Debian Bug report #1061894, regarding apr: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt w

Bug#1061892: marked as done (apophenia: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:04:55 + with message-id and subject line Bug#1061892: fixed in apophenia 1.0+ds-8.1 has caused the Debian Bug report #1061892, regarding apophenia: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has

Bug#1061891: marked as done (apbs: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 02:04:46 + with message-id and subject line Bug#1061891: fixed in apbs 3.4.1-5.1 has caused the Debian Bug report #1061891, regarding apbs: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt

Bug#1062018: marked as done (dart: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:27:38 + with message-id and subject line Bug#1062018: fixed in dart 6.12.1+dfsg4-13.1 has caused the Debian Bug report #1062018, regarding dart: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has be

Bug#1062211: marked as done (android-platform-frameworks-native: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:27:02 + with message-id and subject line Bug#1062211: fixed in android-platform-frameworks-native 1:10.0.0+r36-1.1 has caused the Debian Bug report #1062211, regarding android-platform-frameworks-native: NMU diff for 64-bit time_t transition to be marke

Bug#1061890: marked as done (anthy: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:27:22 + with message-id and subject line Bug#1061890: fixed in anthy 1:0.4-2.1 has caused the Debian Bug report #1061890, regarding anthy: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Bug#1061889: marked as done (angelscript: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:27:12 + with message-id and subject line Bug#1061889: fixed in angelscript 2.35.1+ds-3.1 has caused the Debian Bug report #1061889, regarding angelscript: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the prob

Bug#1061887: marked as done (aml: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:26:45 + with message-id and subject line Bug#1061887: fixed in aml 0.3.0-1.1 has caused the Debian Bug report #1061887, regarding aml: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt w

Bug#1061990: marked as done (allegro4.4: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:09:41 + with message-id and subject line Bug#1061990: fixed in allegro4.4 2:4.4.3.1-4.1 has caused the Debian Bug report #1061990, regarding allegro4.4: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the proble

Bug#1061885: marked as done (allegro5: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:09:54 + with message-id and subject line Bug#1061885: fixed in allegro5 2:5.2.9.1+dfsg-1.1 has caused the Debian Bug report #1061885, regarding allegro5: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the probl

Bug#1061883: marked as done (alberta: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:09:28 + with message-id and subject line Bug#1061883: fixed in alberta 3.0.3-1.1 has caused the Debian Bug report #1061883, regarding alberta: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1061881: marked as done (akonadi-search: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 01:09:15 + with message-id and subject line Bug#1061881: fixed in akonadi-search 4:22.12.3-1.1 has caused the Debian Bug report #1061881, regarding akonadi-search: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that th

Bug#1061878: marked as done (agg: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 00:50:55 + with message-id and subject line Bug#1061878: fixed in agg 1:2.6.1-r134+dfsg1-2.1 has caused the Debian Bug report #1061878, regarding agg: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has

Bug#1061717: marked as done (4ti2: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 00:49:11 + with message-id and subject line Bug#1061717: fixed in 4ti2 1.6.10+ds-1.1 has caused the Debian Bug report #1061717, regarding 4ti2: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been d

Bug#1061873: marked as done (afflib: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 00:34:35 + with message-id and subject line Bug#1061873: fixed in afflib 3.7.20-1.1 has caused the Debian Bug report #1061873, regarding afflib: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1064118: marked as done (keychain: Suggests transitional package gnupg-agent instead of gpg-agent)

Your message dated Wed, 28 Feb 2024 00:35:35 + with message-id and subject line Bug#1064118: fixed in keychain 2.8.5-4 has caused the Debian Bug report #1064118, regarding keychain: Suggests transitional package gnupg-agent instead of gpg-agent to be marked as done. This means that you claim

Bug#1061872: marked as done (adolc: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 00:34:26 + with message-id and subject line Bug#1061872: fixed in adolc 2.7.2-6.1 has caused the Debian Bug report #1061872, regarding adolc: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dea

Bug#1061864: marked as done (actor-framework: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 00:34:06 + with message-id and subject line Bug#1061864: fixed in actor-framework 0.17.6-3.1 has caused the Debian Bug report #1061864, regarding actor-framework: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the

Bug#1061866: marked as done (adns: NMU diff for 64-bit time_t transition)

Your message dated Wed, 28 Feb 2024 00:34:16 + with message-id and subject line Bug#1061866: fixed in adns 1.6.0-2.1 has caused the Debian Bug report #1061866, regarding adns: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt

  1   2   >