Bug#1067872: marked as done (transition: netcdf)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Mon, 1 Apr 2024 06:23:29 +0200 with message-id and subject line Re: Bug#1067872: transition: netcdf has caused the Debian Bug report #1067872, regarding transition: netcdf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1059532: marked as done (abseil:riscv64: uses privileged rdcycle instruction)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Mon, 01 Apr 2024 01:34:23 + with message-id and subject line Bug#1059532: fixed in abseil 20230802.1-3 has caused the Debian Bug report #1059532, regarding abseil:riscv64: uses privileged rdcycle instruction to be marked as done. This means that you claim that the problem

Bug#1021794: marked as done (libipc-run-perl: delay after child exit)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Mon, 01 Apr 2024 01:05:33 + with message-id and subject line Bug#1021794: fixed in libipc-run-perl 20231003.0-2 has caused the Debian Bug report #1021794, regarding libipc-run-perl: delay after child exit to be marked as done. This means that you claim that the problem has

Processed: Merge duplicates

2024-03-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1068160 haskell-haskell-gi Bug #1068160 [src:haskell-gi-glib] haskell-gi-glib: FTBFS on mips64el: couldn't find API description for GLib.time_t Bug reassigned from package 'src:haskell-gi-glib' to 'haskell-haskell-gi'. No longer marked

Bug#1067968: marked as done (defcon: Please replace python3-appdirs build-dependency with platformdirs)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 23:35:47 + with message-id and subject line Bug#1067968: fixed in defcon 0.10.3-2 has caused the Debian Bug report #1067968, regarding defcon: Please replace python3-appdirs build-dependency with platformdirs to be marked as done. This means that you

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

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:52:04 + with message-id and subject line Bug#1068062: fixed in workrave 1.10.52-2 has caused the Debian Bug report #1068062, regarding Update Build-Depends for the time64 library renames to be marked as done. This means that you claim that the problem

Bug#1066314: marked as done (regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration])

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:51:36 + with message-id and subject line Bug#1066314: fixed in regina-rexx 3.9.5+dfsg1-0.1 has caused the Debian Bug report #1066314, regarding regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean

Bug#1027405: marked as done (regina-rexx FTCBFS: builds for the build architecture)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:51:36 + with message-id and subject line Bug#1027405: fixed in regina-rexx 3.9.5+dfsg1-0.1 has caused the Debian Bug report #1027405, regarding regina-rexx FTCBFS: builds for the build architecture to be marked as done. This means that you claim that

Bug#1052115: marked as done (workrave-gnome: needs update for GNOME Shell 46)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:52:04 + with message-id and subject line Bug#1052115: fixed in workrave 1.10.52-2 has caused the Debian Bug report #1052115, regarding workrave-gnome: needs update for GNOME Shell 46 to be marked as done. This means that you claim that the problem has

Processed: Re: opari2: please make the build reproducible

2024-03-31 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.0.7-2 Bug #1026877 [src:opari2] opari2: please make the build reproducible Marked as fixed in versions opari2/2.0.7-2. Bug #1026877 [src:opari2] opari2: please make the build reproducible Marked Bug as done -- 1026877:

Bug#964789: marked as done (ITA: zatacka -- arcade multiplayer game like nibbles)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#964789: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #964789, regarding ITA: zatacka -- arcade multiplayer game like nibbles to be marked as done. This means that you claim that the problem has

Bug#904633: marked as done (newer upstream/forked version available)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#904633: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #904633, regarding newer upstream/forked version available to be marked as done. This means that you claim that the problem has been dealt

Bug#908572: marked as done (zatacka: Crashes with segmentation fault on changing settings)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#908572: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #908572, regarding zatacka: Crashes with segmentation fault on changing settings to be marked as done. This means that you claim that the

Bug#908387: marked as done (zatacka: Crashes with segmentation fault on launch)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#908387: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #908387, regarding zatacka: Crashes with segmentation fault on launch to be marked as done. This means that you claim that the problem has

Bug#738090: marked as done (zatacka: please provide icon for desktop file)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#738090: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #738090, regarding zatacka: please provide icon for desktop file to be marked as done. This means that you claim that the problem has been

Bug#626767: marked as done (zatacka: window manager close button does not work)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#626767: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #626767, regarding zatacka: window manager close button does not work to be marked as done. This means that you claim that the problem has

Bug#1067626: marked as done (FTBFS: fopen_fails test failed)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 22:09:52 + with message-id and subject line Bug#1067626: fixed in pacemaker 2.1.7-1 has caused the Debian Bug report #1067626, regarding FTBFS: fopen_fails test failed to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1066722: marked as done (xracer: FTBFS: spatscal.c:102:17: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 21:44:30 + with message-id and subject line Bug#1066722: fixed in xracer 0.96.9.1-12 has caused the Debian Bug report #1066722, regarding xracer: FTBFS: spatscal.c:102:17: error: implicit declaration of function ‘exit’

Bug#1057910: marked as done (apticron: use systemd.pc to place systemd system units)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 21:34:27 + with message-id and subject line Bug#1057910: fixed in apticron 1.2.9 has caused the Debian Bug report #1057910, regarding apticron: use systemd.pc to place systemd system units to be marked as done. This means that you claim that the problem

Bug#1066527: marked as done (xsystem35: FTBFS: sactcg.c:211:27: error: implicit declaration of function ‘sjis2euc’ [-Werror=implicit-function-declaration])

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 21:10:35 + with message-id and subject line Bug#1066527: fixed in xsystem35 1.7.3-pre5-11 has caused the Debian Bug report #1066527, regarding xsystem35: FTBFS: sactcg.c:211:27: error: implicit declaration of function ‘sjis2euc’

Bug#1065514: marked as done (qpdfview FTCBFS: fails running lrelease and runs the build arch qmake6)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 21:10:21 + with message-id and subject line Bug#1065514: fixed in qpdfview 0.5.0+ds-5 has caused the Debian Bug report #1065514, regarding qpdfview FTCBFS: fails running lrelease and runs the build arch qmake6 to be marked as done. This means that you

Bug#1064677: marked as done (puppetdb: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 21:10:09 + with message-id and subject line Bug#1064677: fixed in puppetdb 8.4.1-1 has caused the Debian Bug report #1064677, regarding puppetdb: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 to be marked as done. This means that

Bug#1057678: marked as done (puppetdb: FTBFS with default Java 21 due to the FIPS clause in project.clj)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 21:10:09 + with message-id and subject line Bug#1057678: fixed in puppetdb 8.4.1-1 has caused the Debian Bug report #1057678, regarding puppetdb: FTBFS with default Java 21 due to the FIPS clause in project.clj to be marked as done. This means that you

Bug#1068151: marked as done (Pre-installed vendors list contains broken links)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 20:47:56 + (UTC) with message-id <9489a182-e124-46da-bf5c-b209aae47...@me.com> and subject line has caused the Debian Bug report #1068151, regarding Pre-installed vendors list contains broken links to be marked as done. This means that you claim that the

Bug#1067649: marked as done (Verification page is not accessible from the homepage)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 20:06:55 + with message-id and subject line Re: Bug#1067649: Verification page is not accessible from the homepage has caused the Debian Bug report #1067649, regarding Verification page is not accessible from the homepage to be marked as done. This means

Bug#1067121: marked as done (supysonic: flaky autopkgtest including times out)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 19:51:56 + with message-id and subject line Bug#1067121: fixed in supysonic 0.7.6+ds-4 has caused the Debian Bug report #1067121, regarding supysonic: flaky autopkgtest including times out to be marked as done. This means that you claim that the problem

Bug#1067947: marked as done (golang-github-stvp-tempredis: please make the build reproducible)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 19:20:17 + with message-id and subject line Bug#1067947: fixed in golang-github-stvp-tempredis 0.0~git20231107.8a695b6-2 has caused the Debian Bug report #1067947, regarding golang-github-stvp-tempredis: please make the build reproducible to be marked as

Processed: your mail

2024-03-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1001981 Bug #1001981 [onioncircuits] onioncircuits: Doesn't start: Permission denied: '/usr/local/lib/python3.9/dist-packages/usb-0.0.83.dev0.dist-info' Marked Bug as done > tags 1001981 + unreproducible Bug #1001981 {Done: Sascha

Processed: your mail

2024-03-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 901144 Bug #901144 [onioncircuits] onioncircuits: Fails to display information on Tor Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 901144:

Bug#900015: marked as done (libmbedtls-dev: add pkg-config support)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 18:34:33 + with message-id and subject line Bug#900015: fixed in mbedtls 2.28.8-1 has caused the Debian Bug report #900015, regarding libmbedtls-dev: add pkg-config support to be marked as done. This means that you claim that the problem has been dealt

Bug#1066594: marked as done (octave-iso2mesh: FTBFS: nl_single_file.c:2505:26: error: implicit declaration of function ‘lsame_’ [-Werror=implicit-function-declaration])

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 17:41:47 + with message-id and subject line Bug#1066594: fixed in octave-iso2mesh 1.9.6+ds-10 has caused the Debian Bug report #1066594, regarding octave-iso2mesh: FTBFS: nl_single_file.c:2505:26: error: implicit declaration of function ‘lsame_’

Bug#1055321: marked as done (pipx: shell completions are not installed)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 17:08:45 + with message-id and subject line Bug#1055321: fixed in python-pipx 1.5.0-1 has caused the Debian Bug report #1055321, regarding pipx: shell completions are not installed to be marked as done. This means that you claim that the problem has been

Bug#1067879: marked as done (mp3check: suggests dead-upstream mpg321 instead of mpg123)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 17:06:48 + with message-id and subject line Bug#1067879: fixed in mp3check 0.8.7-5 has caused the Debian Bug report #1067879, regarding mp3check: suggests dead-upstream mpg321 instead of mpg123 to be marked as done. This means that you claim that the

Bug#1067880: marked as done (normalize-audio: suggests dead-upstream mpg321 instead of mpg123)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 17:06:57 + with message-id and subject line Bug#1067880: fixed in normalize-audio 0.7.7-18 has caused the Debian Bug report #1067880, regarding normalize-audio: suggests dead-upstream mpg321 instead of mpg123 to be marked as done. This means that you claim

Bug#1063989: marked as done (xonsh: autopkgtest regression with pytest 8)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 16:53:52 + with message-id and subject line Bug#1063989: fixed in xonsh 0.15.1+dfsg-1 has caused the Debian Bug report #1063989, regarding xonsh: autopkgtest regression with pytest 8 to be marked as done. This means that you claim that the problem has been

Bug#1049381: marked as done (pipx: manpage shows as generate_man.py)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 12:11:17 -0400 with message-id <3zgkm6diinxqzw2a6l4eb44kqj5en7u4nrt4gbxnr2sxcbclg6@gy6iejrvtxc7> and subject line Re: Bug#1049381: pipx: manpage shows as generate_man.py has caused the Debian Bug report #1049381, regarding pipx: manpage shows as generate_man.py

Bug#1068102: marked as done (FileNotFoundError in process_manpages())

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 15:49:34 + with message-id and subject line Bug#1068102: fixed in debputy 0.1.24 has caused the Debian Bug report #1068102, regarding FileNotFoundError in process_manpages() to be marked as done. This means that you claim that the problem has been dealt

Processed: closing 1067304

2024-03-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # this was a transient issues > close 1067304 Bug #1067304 [src:gmsh] gmsh: FTBFS: unsatisfiable build-dependencies Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1067304:

Bug#1067985: marked as done (nmu: libevent_2.1.12-stable-8.1)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 16:55:31 +0200 with message-id and subject line Re: Bug#1067985: nmu: libevent_2.1.12-stable-8.1 has caused the Debian Bug report #1067985, regarding nmu: libevent_2.1.12-stable-8.1 to be marked as done. This means that you claim that the problem has been

Bug#1068128: marked as done (nmu: opencolorio_2.1.3+dfsg-1.1)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 16:55:14 +0200 with message-id and subject line Re: Bug#1068128: nmu: opencolorio_2.1.3+dfsg-1.1 has caused the Debian Bug report #1068128, regarding nmu: opencolorio_2.1.3+dfsg-1.1 to be marked as done. This means that you claim that the problem has been

Bug#1067494: marked as done (obs-studio: FTBFS on time64_t archs)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 13:39:07 + with message-id and subject line Bug#1067494: fixed in obs-studio 30.0.2+dfsg-3 has caused the Debian Bug report #1067494, regarding obs-studio: FTBFS on time64_t archs to be marked as done. This means that you claim that the problem has been

Processed: RFS: graphviz-dot-mode/0.4.2+git20230325.8ff793b-1 [Team] -- Emacs mode for the dot-language used by graphviz

2024-03-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1067933 Bug #1067933 [sponsorship-requests] RFS: graphviz-dot-mode/0.4.2+git20230325.8ff793b-1 [Team] -- Emacs mode for the dot-language used by graphviz Marked Bug as done > stop Stopping processing here. Please contact me if you need

Bug#1067942: marked as done (Depends on pre-t64 libglib2.0-0)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 12:50:08 + with message-id and subject line Bug#1067942: fixed in ibus 1.5.29-2 has caused the Debian Bug report #1067942, regarding Depends on pre-t64 libglib2.0-0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1068121: marked as done (python-fusepy: hard-coded dependencies on pre-t64 libraries)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 11:47:36 + with message-id and subject line Bug#1068121: fixed in python-fusepy 3.0.1-5 has caused the Debian Bug report #1068121, regarding python-fusepy: hard-coded dependencies on pre-t64 libraries to be marked as done. This means that you claim that

Bug#1067243: marked as done (openssh: please build without -fzero-call-used-regs=used on m68k)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 11:47:29 + with message-id and subject line Bug#1067243: fixed in openssh 1:9.7p1-3 has caused the Debian Bug report #1067243, regarding openssh: please build without -fzero-call-used-regs=used on m68k to be marked as done. This means that you claim that

Bug#1056861: marked as done (python-llfuse: ftbfs with cython 3.0.x)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 11:08:51 + with message-id and subject line Bug#1056861: fixed in python-llfuse 1.4.1+dfsg-3 has caused the Debian Bug report #1056861, regarding python-llfuse: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has

Bug#1062404: marked as done (orthanc-python: flaky autopkgtest: Test failed with)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 11:06:09 + with message-id and subject line Bug#1062404: fixed in orthanc-python 4.1+ds-3 has caused the Debian Bug report #1062404, regarding orthanc-python: flaky autopkgtest: Test failed with to be marked as done. This means that you claim that the

Bug#1039701: marked as done (libsigrok4: Built-in driver list is empty when compiled with LTO)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 11:42:33 +0100 with message-id and subject line Re: [Pkg-electronics-devel] Bug#1039701: libsigrok4: Built-in driver list is empty when compiled with LTO has caused the Debian Bug report #1039701, regarding libsigrok4: Built-in driver list is empty when

Bug#1066964: marked as done (ITA: newlib -- C library and math library for)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 11:02:51 + with message-id and subject line Bug#1066964: fixed in newlib 4.4.0.20231231-3 has caused the Debian Bug report #1066964, regarding ITA: newlib -- C library and math library for to be marked as done. This means that you claim that the problem

Bug#1018413: marked as done (mom: build-depends on python3-nose or uses it for autopkgtest)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:58:05 + with message-id and subject line Bug#1018413: fixed in mom 0.6.4-0.1 has caused the Debian Bug report #1018413, regarding mom: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim that the

Bug#1068105: marked as done (drop the Python3-Version attribute)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:56:31 + with message-id and subject line Bug#1068105: fixed in libsbml 5.20.2+dfsg-3 has caused the Debian Bug report #1068105, regarding drop the Python3-Version attribute to be marked as done. This means that you claim that the problem has been dealt

Bug#1014781: marked as done (momd crashing due to error in HypervisorInterfaces/libvirtInterface.py)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:58:05 + with message-id and subject line Bug#1014781: fixed in mom 0.6.4-0.1 has caused the Debian Bug report #1014781, regarding momd crashing due to error in HypervisorInterfaces/libvirtInterface.py to be marked as done. This means that you claim that

Bug#1068047: marked as done (Suspicious commit merged in 2021 from account responsible for xz backdoor)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:46:58 + with message-id and subject line Bug#1068047: fixed in libarchive 3.7.2-2 has caused the Debian Bug report #1068047, regarding Suspicious commit merged in 2021 from account responsible for xz backdoor to be marked as done. This means that you

Bug#1067904: marked as done ($frontend-$version-for-host: versioned dependency too strict)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:42:46 + with message-id and subject line Bug#1067904: fixed in gcc-14 14-20240330-1 has caused the Debian Bug report #1067904, regarding $frontend-$version-for-host: versioned dependency too strict to be marked as done. This means that you claim that

Bug#1067272: marked as done (haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:43:57 + with message-id and subject line Bug#1067272: fixed in haskell-haskell-gi 0.26.7-4 has caused the Debian Bug report #1067272, regarding haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1 to

Bug#1031125: marked as done (ell FTBFS on hppa b/c of missing LFS suppport)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:39:00 + with message-id and subject line Bug#1031125: fixed in ell 0.64-1 has caused the Debian Bug report #1031125, regarding ell FTBFS on hppa b/c of missing LFS suppport to be marked as done. This means that you claim that the problem has been dealt

Bug#1068043: marked as done (BinNMU 1.11-1+b1 depends on both, libmspack0 and libmspack0t64, and is hence uninstallable (at least on armhf))

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:36:56 + with message-id and subject line Bug#1068043: fixed in cabextract 1.11-2 has caused the Debian Bug report #1068043, regarding BinNMU 1.11-1+b1 depends on both, libmspack0 and libmspack0t64, and is hence uninstallable (at least on armhf) to be

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

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 10:37:09 + with message-id and subject line Bug#1067919: fixed in calindori 24.02.1-1 has caused the Debian Bug report #1067919, regarding Update Build-Depends for the time64 library renames to be marked as done. This means that you claim that the problem

Bug#1068069: marked as done (nmu: juce_7.0.5+ds-1)

2024-03-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Mar 2024 11:39:22 +0200 with message-id and subject line Re: Bug#1068069: nmu: juce_7.0.5+ds-1 has caused the Debian Bug report #1068069, regarding nmu: juce_7.0.5+ds-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not