Bug#1053653: marked as done (samba-libs:armhf: libndr-samba.so invalid elf header)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sun, 8 Oct 2023 07:41:19 +0300 with message-id <564cdb70-f978-4a12-b3a1-cb09d05e3...@tls.msk.ru> and subject line Re: Bug#1053653: samba-libs:armhf: libndr-samba.so invalid elf header has caused the Debian Bug report #1053653, regarding samba-libs:armhf: libndr-samba.so invalid

Bug#959972: marked as done (nextcloud-desktop: Please provide a backport for buster)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Oct 2023 03:49:10 +0200 with message-id <2519464.mS5XxJoxeo@tuxin> and subject line Re: Bug#959972: nextcloud-desktop: Please provide a backport for buster has caused the Debian Bug report #959972, regarding nextcloud-desktop: Please provide a backport for buster to be m

Processed: forcemerge 972152 971614

2023-10-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 972152 971614 Bug #972152 {Done: Hefee } [nextcloud-desktop] nextcloud-desktop: segfault with libQt5Core.so.5.11.3 after resuming from hibernate Bug #971614 [nextcloud-desktop] /usr/bin/nextcloud: General protection fault with libQT5

Bug#972152: marked as done (nextcloud-desktop: segfault with libQt5Core.so.5.11.3 after resuming from hibernate)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Oct 2023 03:23:58 +0200 with message-id <2091005.R3dchmCGeU@tuxin> and subject line Re: Bug#972152: nextcloud-desktop: segfault with libQt5Core.so.5.11.3 after resuming from hibernate has caused the Debian Bug report #972152, regarding nextcloud-desktop: segfault with li

Bug#996924: marked as done (nextcloud-desktop: deletes dirs on the server although they're still here locally)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Oct 2023 02:22:11 +0200 with message-id <3309717.CA4L6bvzst@tuxin> and subject line Re: Bug#996924: nextcloud-desktop: deletes dirs on the server although they're still here locally has caused the Debian Bug report #996924, regarding nextcloud-desktop: deletes dirs on th

Bug#985989: marked as done (nextcloud-desktop: segmentation fault when trying to open settings)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Oct 2023 02:18:20 +0200 with message-id <5594270.zFmEUVrfbZ@tuxin> and subject line Re: Bug#985989: nextcloud-desktop: segmentation fault when trying to open settings has caused the Debian Bug report #985989, regarding nextcloud-desktop: segmentation fault when trying to

Bug#980543: marked as done (nextcloud-desktop: nextcloud started to create huge log files in 1min intervals)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Oct 2023 01:40:27 +0200 with message-id <56765244.G3UXOvhOfr@tuxin> and subject line Re: Bug#980543: nextcloud-desktop: nextcloud started to create huge log files in 1min intervals has caused the Debian Bug report #980543, regarding nextcloud-desktop: nextcloud started t

Bug#511461: marked as done (O: lprng -- lpr/lpd printer spooling system)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 23:06:35 + with message-id and subject line Bug#511461: fixed in lprng 3.8.B-7 has caused the Debian Bug report #511461, regarding O: lprng -- lpr/lpd printer spooling system to be marked as done. This means that you claim that the problem has been dealt wi

Bug#998004: marked as done (/usr/sbin/lpinfo: lpinfo: -U does not work despite saying so in the help)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#998004: fixed in cups 2.4.7-1 has caused the Debian Bug report #998004, regarding /usr/sbin/lpinfo: lpinfo: -U does not work despite saying so in the help to be marked as done. This means that you claim that

Bug#971625: marked as done (libcups2-dev: please include a cups.pc for pkg-config)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#971625: fixed in cups 2.4.7-1 has caused the Debian Bug report #971625, regarding libcups2-dev: please include a cups.pc for pkg-config to be marked as done. This means that you claim that the problem has been

Bug#954974: marked as done (apparmor.d/usr.sbin.cupsd -- please add an #include dropin for cups-pdf)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#954974: fixed in cups 2.4.7-1 has caused the Debian Bug report #954974, regarding apparmor.d/usr.sbin.cupsd -- please add an #include dropin for cups-pdf to be marked as done. This means that you claim that t

Bug#1052419: marked as done (cups-daemon: NEWS.Debian is only tech-gibberish)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1052419: fixed in cups 2.4.7-1 has caused the Debian Bug report #1052419, regarding cups-daemon: NEWS.Debian is only tech-gibberish to be marked as done. This means that you claim that the problem has been dea

Bug#1043470: marked as done (cups: current d/watch no longer works)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1043470: fixed in cups 2.4.7-1 has caused the Debian Bug report #1043470, regarding cups: current d/watch no longer works to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1041466: marked as done (printer-driver-gutenprint: Canon MG3500: CMYK mode is not working anymore)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1043331: fixed in cups 2.4.7-1 has caused the Debian Bug report #1043331, regarding printer-driver-gutenprint: Canon MG3500: CMYK mode is not working anymore to be marked as done. This means that you claim th

Bug#1043331: marked as done (cups: no color printing (black/white works; ppd file used))

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1043331: fixed in cups 2.4.7-1 has caused the Debian Bug report #1043331, regarding cups: no color printing (black/white works; ppd file used) to be marked as done. This means that you claim that the problem h

Bug#1039983: marked as done (CMYK capable printer does not print in colour)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1043331: fixed in cups 2.4.7-1 has caused the Debian Bug report #1043331, regarding CMYK capable printer does not print in colour to be marked as done. This means that you claim that the problem has been dealt

Bug#1043331: marked as done (cups: no color printing (black/white works; ppd file used))

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1041466: fixed in cups 2.4.7-1 has caused the Debian Bug report #1041466, regarding cups: no color printing (black/white works; ppd file used) to be marked as done. This means that you claim that the problem h

Bug#1039983: marked as done (CMYK capable printer does not print in colour)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1041466: fixed in cups 2.4.7-1 has caused the Debian Bug report #1041466, regarding CMYK capable printer does not print in colour to be marked as done. This means that you claim that the problem has been dealt

Bug#1041466: marked as done (printer-driver-gutenprint: Canon MG3500: CMYK mode is not working anymore)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1041466: fixed in cups 2.4.7-1 has caused the Debian Bug report #1041466, regarding printer-driver-gutenprint: Canon MG3500: CMYK mode is not working anymore to be marked as done. This means that you claim th

Bug#1043331: marked as done (cups: no color printing (black/white works; ppd file used))

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1039983: fixed in cups 2.4.7-1 has caused the Debian Bug report #1039983, regarding cups: no color printing (black/white works; ppd file used) to be marked as done. This means that you claim that the problem h

Bug#1041466: marked as done (printer-driver-gutenprint: Canon MG3500: CMYK mode is not working anymore)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1039983: fixed in cups 2.4.7-1 has caused the Debian Bug report #1039983, regarding printer-driver-gutenprint: Canon MG3500: CMYK mode is not working anymore to be marked as done. This means that you claim th

Bug#1039983: marked as done (CMYK capable printer does not print in colour)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1039983: fixed in cups 2.4.7-1 has caused the Debian Bug report #1039983, regarding CMYK capable printer does not print in colour to be marked as done. This means that you claim that the problem has been dealt

Bug#1009146: marked as done (cups Segmentation fault)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1009147: fixed in cups 2.4.7-1 has caused the Debian Bug report #1009147, regarding cups Segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1009147: marked as done ()

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1009147: fixed in cups 2.4.7-1 has caused the Debian Bug report #1009147, regarding to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#1009147: marked as done ()

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1009146: fixed in cups 2.4.7-1 has caused the Debian Bug report #1009146, regarding to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#1009146: marked as done (cups Segmentation fault)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1009146: fixed in cups 2.4.7-1 has caused the Debian Bug report #1009146, regarding cups Segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1008053: marked as done (cups-client: lpoptions as root doesn't update /etc/cups/lpoptions)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 22:34:43 + with message-id and subject line Bug#1008053: fixed in cups 2.4.7-1 has caused the Debian Bug report #1008053, regarding cups-client: lpoptions as root doesn't update /etc/cups/lpoptions to be marked as done. This means that you claim that the pr

Bug#986740: marked as done (RM: forked-daapd -- ROM; RC-buggy; needs many Vue.js packages for full features)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:13 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #986740, regarding RM: forked-daapd -- ROM; RC-buggy; needs many Vue.js packages for full features to be marked as done. This means th

Bug#982034: marked as done (forked-daapd: autopkgtest regression in testing: Job for forked-daapd.service failed.)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #982034, regarding forked-daapd: autopkgtest regression in testing: Job for forked-daapd.service failed. to be marked as done. This me

Bug#962450: marked as done (forked-daapd: Please document (Description: or README.Debian) why the web UI is disabled)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #962450, regarding forked-daapd: Please document (Description: or README.Debian) why the web UI is disabled to be marked as done. This

Bug#960425: marked as done (RM: arcanist-clang-format-linter -- ROM; orphaned, dead upstream, no users)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:43 + with message-id and subject line Bug#960425: Removed package(s) from unstable has caused the Debian Bug report #960425, regarding RM: arcanist-clang-format-linter -- ROM; orphaned, dead upstream, no users to be marked as done. This means that yo

Bug#957758: marked as done (restbed: ftbfs with GCC-10)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:54:50 + with message-id and subject line Bug#1053534: Removed package(s) from unstable has caused the Debian Bug report #957758, regarding restbed: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#892376: marked as done (forked-daapd: iPhone Remote kills forked-daapd)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #892376, regarding forked-daapd: iPhone Remote kills forked-daapd to be marked as done. This means that you claim that the problem has

Bug#703162: marked as done (forked-daapd: Segfaults on remote connect)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #703162, regarding forked-daapd: Segfaults on remote connect to be marked as done. This means that you claim that the problem has been

Bug#880569: marked as done (forked-daapd: segfaults on start up (converting old format db))

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #880569, regarding forked-daapd: segfaults on start up (converting old format db) to be marked as done. This means that you claim that

Bug#662125: marked as done (forked-daapd: scans whole DB on startup which takes ages)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #662125, regarding forked-daapd: scans whole DB on startup which takes ages to be marked as done. This means that you claim that the pr

Bug#1053534: marked as done (RM: restbed -- RoQA; unmaintained, RC-buggy, no rdeps)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:54:46 + with message-id and subject line Bug#1053534: Removed package(s) from unstable has caused the Debian Bug report #1053534, regarding RM: restbed -- RoQA; unmaintained, RC-buggy, no rdeps to be marked as done. This means that you claim that the pro

Bug#1031173: marked as done (arcanist-clang-format-linter: prevents arcanist tool from working (PHP Fatal error: Uncaught Error))

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:47 + with message-id and subject line Bug#960425: Removed package(s) from unstable has caused the Debian Bug report #1031173, regarding arcanist-clang-format-linter: prevents arcanist tool from working (PHP Fatal error: Uncaught Error) to be marked as

Bug#1004626: marked as done (forked-daapd: FTBFS with ffmpeg 5.0)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #1004626, regarding forked-daapd: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#1053376: marked as done (RM: lttnganalyses -- ROM; obsolete, dead upstream)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:52:28 + with message-id and subject line Bug#1053376: Removed package(s) from unstable has caused the Debian Bug report #1053376, regarding RM: lttnganalyses -- ROM; obsolete, dead upstream to be marked as done. This means that you claim that the problem

Bug#1052768: marked as done (lttnganalyses: FTBFS: AssertionError: '20:57:08.123456789' != '16:57:08.123456789')

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:52:31 + with message-id and subject line Bug#1053376: Removed package(s) from unstable has caused the Debian Bug report #1052768, regarding lttnganalyses: FTBFS: AssertionError: '20:57:08.123456789' != '16:57:08.123456789' to be marked as done. This mea

Bug#1053321: marked as done (RM: google-android-platform-33-upsidedowncakeprivacysandbox-installer -- ROM; NVIU)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:50:50 + with message-id and subject line Bug#1053321: Removed package(s) from unstable has caused the Debian Bug report #1053321, regarding RM: google-android-platform-33-upsidedowncakeprivacysandbox-installer -- ROM; NVIU to be marked as done. This mea

Bug#1053315: marked as done (RM: firmware-tomu -- RoM; RC-buggy; abandoned upstream)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:46:59 + with message-id and subject line Bug#1053315: Removed package(s) from unstable has caused the Debian Bug report #1053315, regarding RM: firmware-tomu -- RoM; RC-buggy; abandoned upstream to be marked as done. This means that you claim that the pr

Bug#1052836: marked as done (firmware-tomu: FTBFS: unsatisfiable build-dependencies: libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), gcc-arm-none-eabi (= 15:12.2.rel1-1))

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:47:02 + with message-id and subject line Bug#1053315: Removed package(s) from unstable has caused the Debian Bug report #1052836, regarding firmware-tomu: FTBFS: unsatisfiable build-dependencies: libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), gcc-arm

Bug#858958: marked as done (morse-simulator-doc: broken symlink: /usr/share/doc/morse/html/_static/underscore.js -> ../../../../javascript/jquery/underscore.js)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:46:22 + with message-id and subject line Bug#1053299: Removed package(s) from unstable has caused the Debian Bug report #858958, regarding morse-simulator-doc: broken symlink: /usr/share/doc/morse/html/_static/underscore.js -> ../../../../javascript/jqu

Bug#1053299: marked as done (RM: morse-simulator -- ROM; unmaintained upstream)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:46:17 + with message-id and subject line Bug#1053299: Removed package(s) from unstable has caused the Debian Bug report #1053299, regarding RM: morse-simulator -- ROM; unmaintained upstream to be marked as done. This means that you claim that the problem

Bug#1053268: marked as done (RM: pgaudit-1.7 -- ROM; superseded by pgaudit-16)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:44:39 + with message-id and subject line Bug#1053268: Removed package(s) from unstable has caused the Debian Bug report #1053268, regarding RM: pgaudit-1.7 -- ROM; superseded by pgaudit-16 to be marked as done. This means that you claim that the problem

Bug#1052960: marked as done (pgaudit-1.7: FTBFS: make: *** [debian/rules:10: clean] Error 1)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:44:43 + with message-id and subject line Bug#1053268: Removed package(s) from unstable has caused the Debian Bug report #1052960, regarding pgaudit-1.7: FTBFS: make: *** [debian/rules:10: clean] Error 1 to be marked as done. This means that you claim tha

Bug#1040101: marked as done (morse-simulator: deprecation of Python libraries asyncore and asynchat)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:46:22 + with message-id and subject line Bug#1053299: Removed package(s) from unstable has caused the Debian Bug report #1040101, regarding morse-simulator: deprecation of Python libraries asyncore and asynchat to be marked as done. This means that you c

Bug#1040288: marked as done (python3-morse-simulator: SyntaxWarning during package installation)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:46:22 + with message-id and subject line Bug#1053299: Removed package(s) from unstable has caused the Debian Bug report #1040288, regarding python3-morse-simulator: SyntaxWarning during package installation to be marked as done. This means that you claim

Bug#1035264: marked as done (morse-simulator: please add autopkgtests (to add coverage for python3-numpy))

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:46:22 + with message-id and subject line Bug#1053299: Removed package(s) from unstable has caused the Debian Bug report #1035264, regarding morse-simulator: please add autopkgtests (to add coverage for python3-numpy) to be marked as done. This means tha

Bug#910033: marked as done (bless-0.6.0-5 - Unexpected exit of the program when exporting to a file)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:38:55 + with message-id and subject line Bug#1053152: Removed package(s) from unstable has caused the Debian Bug report #910033, regarding bless-0.6.0-5 - Unexpected exit of the program when exporting to a file to be marked as done. This means that you

Bug#978046: marked as done (bless: ignore/reload nonresponsive unless scrolled to top)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:38:55 + with message-id and subject line Bug#1053152: Removed package(s) from unstable has caused the Debian Bug report #978046, regarding bless: ignore/reload nonresponsive unless scrolled to top to be marked as done. This means that you claim that the

Bug#792585: marked as done (bless default UI can only shows 17 bytes or more per row when 'Conversion Table' is visible)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:38:55 + with message-id and subject line Bug#1053152: Removed package(s) from unstable has caused the Debian Bug report #792585, regarding bless default UI can only shows 17 bytes or more per row when 'Conversion Table' is visible to be marked as done.

Bug#647024: marked as done (bless: assertion failure when saving an empty file)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:38:55 + with message-id and subject line Bug#1053152: Removed package(s) from unstable has caused the Debian Bug report #647024, regarding bless: assertion failure when saving an empty file to be marked as done. This means that you claim that the problem

Bug#1052876: marked as done (bless: FTBFS: ../tests/meson.build:5:4: ERROR: Problem encountered: nunit not found, cannot build tests. You can disable with -Dtests=false)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:38:55 + with message-id and subject line Bug#1053152: Removed package(s) from unstable has caused the Debian Bug report #1052876, regarding bless: FTBFS: ../tests/meson.build:5:4: ERROR: Problem encountered: nunit not found, cannot build tests. You can d

Bug#1053152: marked as done (RM: bless -- RoQA; RC-buggy; unmaintained)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:38:49 + with message-id and subject line Bug#1053152: Removed package(s) from unstable has caused the Debian Bug report #1053152, regarding RM: bless -- RoQA; RC-buggy; unmaintained to be marked as done. This means that you claim that the problem has bee

Bug#967492: marked as done (gtkglextmm: depends on deprecated GTK 2)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:37:07 + with message-id and subject line Bug#1052987: Removed package(s) from unstable has caused the Debian Bug report #967492, regarding gtkglextmm: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been d

Bug#1043275: marked as done (bless: Build-Depends on deprecated libgtk2.0-cil-dev)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:38:55 + with message-id and subject line Bug#1053152: Removed package(s) from unstable has caused the Debian Bug report #1043275, regarding bless: Build-Depends on deprecated libgtk2.0-cil-dev to be marked as done. This means that you claim that the prob

Bug#525228: marked as done (libgtkglextmm-x11-1.2-0: glwindow->create_cairo_context() segfaults)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:37:07 + with message-id and subject line Bug#1052987: Removed package(s) from unstable has caused the Debian Bug report #525228, regarding libgtkglextmm-x11-1.2-0: glwindow->create_cairo_context() segfaults to be marked as done. This means that you claim

Bug#1053093: marked as done (RM: mpdcron -- ROM; Dead upstream)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:37:59 + with message-id and subject line Bug#1053093: Removed package(s) from unstable has caused the Debian Bug report #1053093, regarding RM: mpdcron -- ROM; Dead upstream to be marked as done. This means that you claim that the problem has been dealt

Bug#1048354: marked as done (mpdcron: Fails to build source after successful build)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:38:02 + with message-id and subject line Bug#1053093: Removed package(s) from unstable has caused the Debian Bug report #1048354, regarding mpdcron: Fails to build source after successful build to be marked as done. This means that you claim that the pro

Bug#1052987: marked as done (RM: gtkglextmm -- RoQA; dead upstream; depends on gtk2)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:37:03 + with message-id and subject line Bug#1052987: Removed package(s) from unstable has caused the Debian Bug report #1052987, regarding RM: gtkglextmm -- RoQA; dead upstream; depends on gtk2 to be marked as done. This means that you claim that the pr

Bug#1052709: marked as done (RM: bzr-upload -- ROM; transitional package)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:35:49 + with message-id and subject line Bug#1052709: Removed package(s) from unstable has caused the Debian Bug report #1052709, regarding RM: bzr-upload -- ROM; transitional package to be marked as done. This means that you claim that the problem has b

Bug#981890: marked as done (ITA: apt-listchanges -- package change history)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#981890: fixed in apt-listchanges 4.0 has caused the Debian Bug report #981890, regarding ITA: apt-listchanges -- package change history to be marked as done. This means that you claim that the problem has been

Bug#967493: marked as done (gtkguitune: depends on deprecated GTK 2)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:35:22 + with message-id and subject line Bug#1052608: Removed package(s) from unstable has caused the Debian Bug report #967493, regarding gtkguitune: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been d

Bug#967817: marked as done (xbindkeys-config: depends on deprecated GTK 2)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #967817, regarding xbindkeys-config: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has

Bug#926554: marked as done (xbindkeys-config: segfault upon "Get key")

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #926554, regarding xbindkeys-config: segfault upon "Get key" to be marked as done. This means that you claim that the problem has been

Bug#880142: marked as done (Please leave blank lines around header)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#880142: fixed in apt-listchanges 4.0 has caused the Debian Bug report #880142, regarding Please leave blank lines around header to be marked as done. This means that you claim that the problem has been dealt w

Bug#772473: marked as done (xbindkeys-config: CVE-2014-9513: Insecure use of temporary files)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #772473, regarding xbindkeys-config: CVE-2014-9513: Insecure use of temporary files to be marked as done. This means that you claim th

Bug#760918: marked as done (apt-listchanges: does not show backdated NEWS entries)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#760918: fixed in apt-listchanges 4.0 has caused the Debian Bug report #760918, regarding apt-listchanges: does not show backdated NEWS entries to be marked as done. This means that you claim that the problem h

Bug#748631: marked as done (apt-listchanges should put separate version numbers in seen DB for each binary package)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#748631: fixed in apt-listchanges 4.0 has caused the Debian Bug report #748631, regarding apt-listchanges should put separate version numbers in seen DB for each binary package to be marked as done. This means

Bug#650369: marked as done (xbindkeys-config: Cannot close Manual and About windows from Help menu)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #650369, regarding xbindkeys-config: Cannot close Manual and About windows from Help menu to be marked as done. This means that you cl

Bug#516565: marked as done (xbindkeys-config make a segfault when the file ~/.xbindkeysrc doesn't exist)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #516565, regarding xbindkeys-config make a segfault when the file ~/.xbindkeysrc doesn't exist to be marked as done. This means that

Bug#514865: marked as done (apt-listchanges: GTK+ window should not steal focus, and only appear if there is anything to show)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#514865: fixed in apt-listchanges 4.0 has caused the Debian Bug report #514865, regarding apt-listchanges: GTK+ window should not steal focus, and only appear if there is anything to show to be marked as done.

Bug#478188: marked as done (apt-listchanges: Please provide option to set all installed packages as seen)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#478188: fixed in apt-listchanges 4.0 has caused the Debian Bug report #478188, regarding apt-listchanges: Please provide option to set all installed packages as seen to be marked as done. This means that you

Bug#507105: marked as done (xbindkeys-config: buffer overflow when handling environmental variables)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #507105, regarding xbindkeys-config: buffer overflow when handling environmental variables to be marked as done. This means that you

Bug#977422: marked as done (News entry is not shown on upgrades)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#383803: fixed in apt-listchanges 4.0 has caused the Debian Bug report #383803, regarding News entry is not shown on upgrades to be marked as done. This means that you claim that the problem has been dealt with

Bug#760099: marked as done (apt-listchanges: Incorrectly assumes that binary packages from the same source share NEWS files)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#383803: fixed in apt-listchanges 4.0 has caused the Debian Bug report #383803, regarding apt-listchanges: Incorrectly assumes that binary packages from the same source share NEWS files to be marked as done. T

Bug#383803: marked as done (apt-listchanges: mishandles different NEWS.Debian files in different binary packages built from the same source)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#383803: fixed in apt-listchanges 4.0 has caused the Debian Bug report #383803, regarding apt-listchanges: mishandles different NEWS.Debian files in different binary packages built from the same source to be ma

Bug#213178: marked as done (xbindkeys-config segfaults on a specific entry)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #213178, regarding xbindkeys-config segfaults on a specific entry to be marked as done. This means that you claim that the problem has

Bug#268630: marked as done (segfault if no vanilla config found)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #268630, regarding segfault if no vanilla config found to be marked as done. This means that you claim that the problem has been dealt

Bug#1052986: marked as done (apt-listchanges: When a source package is renamed, the entire old changelog is re-displayed)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:08 + with message-id and subject line Bug#1052986: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1052986, regarding apt-listchanges: When a source package is renamed, the entire old changelog is re-displayed to be marked as done. Thi

Bug#1052608: marked as done (RM: gtkguitune -- ROM; Dead upstream)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:35:19 + with message-id and subject line Bug#1052608: Removed package(s) from unstable has caused the Debian Bug report #1052608, regarding RM: gtkguitune -- ROM; Dead upstream to be marked as done. This means that you claim that the problem has been dea

Bug#1052569: marked as done (apt-listchanges: --filter option can't possibly work)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:08 + with message-id and subject line Bug#1052569: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1052569, regarding apt-listchanges: --filter option can't possibly work to be marked as done. This means that you claim that the problem

Bug#1052515: marked as done (RM: vocproc -- ROM (team); unmaintained; depends on gtk2)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:52 + with message-id and subject line Bug#1052515: Removed package(s) from unstable has caused the Debian Bug report #1052515, regarding RM: vocproc -- ROM (team); unmaintained; depends on gtk2 to be marked as done. This means that you claim that the

Bug#1052477: marked as done (RM: xbindkeys-config -- RoQA; orphaned; dead upstream; depends on gtk2)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:23 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #1052477, regarding RM: xbindkeys-config -- RoQA; orphaned; dead upstream; depends on gtk2 to be marked as done. This means that you c

Bug#1052456: marked as done (RM: python-igraph [s390x] -- ROM; unsatisfiable Buil-Depends-Arch: libigraph-dev: libplfit-dev)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:02 + with message-id and subject line Bug#1052456: Removed package(s) from unstable has caused the Debian Bug report #1052456, regarding RM: python-igraph [s390x] -- ROM; unsatisfiable Buil-Depends-Arch: libigraph-dev: libplfit-dev to be marked as don

Bug#1052323: marked as done (RM: biojava5-live -- ROM; superseded by biojava6-live)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:33:40 + with message-id and subject line Bug#1052323: Removed package(s) from unstable has caused the Debian Bug report #1052323, regarding RM: biojava5-live -- ROM; superseded by biojava6-live to be marked as done. This means that you claim that the pro

Bug#1049891: marked as done (O: xbindkeys-config -- gtk program for configuring Xbindkeys)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:31 + with message-id and subject line Bug#1052477: Removed package(s) from unstable has caused the Debian Bug report #1049891, regarding O: xbindkeys-config -- gtk program for configuring Xbindkeys to be marked as done. This means that you claim that

Bug#1041800: marked as done (vocproc: depends on unmaintained gtkmm2.4, and indirectly on GTK 2)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:56 + with message-id and subject line Bug#1052515: Removed package(s) from unstable has caused the Debian Bug report #1041800, regarding vocproc: depends on unmaintained gtkmm2.4, and indirectly on GTK 2 to be marked as done. This means that you claim

Bug#1034241: marked as done ([INTL:ro] Romanian debconf templates translation of apt-listchanges)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:08 + with message-id and subject line Bug#1034241: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1034241, regarding [INTL:ro] Romanian debconf templates translation of apt-listchanges to be marked as done. This means that you claim th

Bug#1034197: marked as done ([INTL:ro] Translation of "apt-listchanges" to Romanian)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:08 + with message-id and subject line Bug#1034197: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1034197, regarding [INTL:ro] Translation of "apt-listchanges" to Romanian to be marked as done. This means that you claim that the proble

Bug#1033903: marked as done (apt-listchanges: [INTL:nl] Dutch translation for the apt-listchanges package's documentation)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:08 + with message-id and subject line Bug#1033903: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1033903, regarding apt-listchanges: [INTL:nl] Dutch translation for the apt-listchanges package's documentation to be marked as done. Th

Bug#1028474: marked as done (apt-listchanges: text frontend should flush stdout before prompting for confirmation)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:08 + with message-id and subject line Bug#1028474: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1028474, regarding apt-listchanges: text frontend should flush stdout before prompting for confirmation to be marked as done. This means

Bug#1023084: marked as done (apt-listchanges: Unable to retrieve changelog for package linux-headers-amd64; 'apt-get changelog' failed with: E: Version '6.0.5+1' for 'linux-headers-amd64' was not foun

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#1023084: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1023084, regarding apt-listchanges: Unable to retrieve changelog for package linux-headers-amd64; 'apt-get changelog' failed with: E: Ver

Bug#1020858: marked as done (apt-listchanges: Please consider line breaking)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#1020858: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1020858, regarding apt-listchanges: Please consider line breaking to be marked as done. This means that you claim that the problem has be

Bug#1052296: marked as done (RM: php-psr-log-test -- ROM; Already packaged under another name)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:33:13 + with message-id and subject line Bug#1052296: Removed package(s) from unstable has caused the Debian Bug report #1052296, regarding RM: php-psr-log-test -- ROM; Already packaged under another name to be marked as done. This means that you claim t

Bug#1052295: marked as done (RM: xmlrpc-light -- RoQA; dead upstream; low popcon; FTBFS with OCaml 4.14.1)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:32:46 + with message-id and subject line Bug#1052295: Removed package(s) from unstable has caused the Debian Bug report #1052295, regarding RM: xmlrpc-light -- RoQA; dead upstream; low popcon; FTBFS with OCaml 4.14.1 to be marked as done. This means tha

Bug#1052237: marked as done (FTBFS with OCaml 4.14.1)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:32:50 + with message-id and subject line Bug#1052295: Removed package(s) from unstable has caused the Debian Bug report #1052237, regarding FTBFS with OCaml 4.14.1 to be marked as done. This means that you claim that the problem has been dealt with. If t

  1   2   3   4   5   >