Bug#995903: marked as done (chromium: Download manager, bookmark manager and extension manager is not showing when on there tab)

Your message dated Sun, 19 Feb 2023 00:45:27 -0500 with message-id and subject line Re: Bug#995903: chromium: Download manager, bookmark manager and extension manager is not showing when on there tab has caused the Debian Bug report #995903, regarding chromium: Download manager, bookmark manager

Bug#1029369: marked as done (tpm2-tss: CVE-2023-22745)

Your message dated Sun, 19 Feb 2023 05:04:00 + with message-id and subject line Bug#1029369: fixed in tpm2-tss 3.2.1-3 has caused the Debian Bug report #1029369, regarding tpm2-tss: CVE-2023-22745 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1031427: marked as done (libomemo-c-dev: No version in pkgconf)

Your message dated Sun, 19 Feb 2023 01:50:23 + with message-id and subject line Bug#1031427: fixed in libomemo-c 0.5.0-4 has caused the Debian Bug report #1031427, regarding libomemo-c-dev: No version in pkgconf to be marked as done. This means that you claim that the problem has been dealt

Bug#1031051: marked as done (librust-rustls-dev depends on librust-ring-dev which is missing on mips, ppc*, s390x, riscv, sparc64, c32)

Your message dated Sun, 19 Feb 2023 01:26:16 + with message-id <21c0d351-0082-19dc-9469-4f892d44c...@debian.org> and subject line re: librust-rustls-dev depends on librust-ring-dev which is missing on mips, ppc*, s390x, riscv, sparc64, c32 has caused the Debian Bug report #1031051, regarding

Bug#998193: marked as done (gitlab: dpkg --configure gitlab fails with NoMethodError: undefined method `build' for debian bullseye)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #998193, regarding gitlab: dpkg --configure gitlab fails with NoMethodError: undefined method `build' for debian bullseye to be

Bug#995073: marked as done (gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2".)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #995073, regarding gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2". to be marked as done.

Bug#995906: marked as done (gitlab: Upgrading buster to bullseye needs some more gitlab-apt-pin-preferences adjustments)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #995906, regarding gitlab: Upgrading buster to bullseye needs some more gitlab-apt-pin-preferences adjustments to be marked as done.

Bug#992075: marked as done (gitlab: download button for 2fa recovery codes does not work (coping works))

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #992075, regarding gitlab: download button for 2fa recovery codes does not work (coping works) to be marked as done. This means that

Bug#991744: marked as done (gitlab-workhorse: contains non-free image testdata/image.svg)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #991744, regarding gitlab-workhorse: contains non-free image testdata/image.svg to be marked as done. This means that you claim that

Bug#989791: marked as done (gitlab: Some views broken by Rails 6.0.3.7 upgrade)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #989791, regarding gitlab: Some views broken by Rails 6.0.3.7 upgrade to be marked as done. This means that you claim that the

Bug#983924: marked as done (GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0))

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #983924, regarding GitLab 13.7.7: ERROR in1:0 Module parse failed: Unexpected character '' (1:0) to be marked as done. This

Bug#990103: marked as done (gitlab: Conflicting dependencies on google-protobuf prevent package configuration during update)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #990103, regarding gitlab: Conflicting dependencies on google-protobuf prevent package configuration during update to be marked as

Bug#988108: marked as done (gitlab: Repeated issues resolving dependencies on upgrade)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #988108, regarding gitlab: Repeated issues resolving dependencies on upgrade to be marked as done. This means that you claim that the

Bug#984828: marked as done (gitlab: code tree not rendered (circling circle instead))

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #984828, regarding gitlab: code tree not rendered (circling circle instead) to be marked as done. This means that you claim that the

Bug#982903: marked as done (gitlab: Internal error caused by missing gitaly-git2go binary)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #982903, regarding gitlab: Internal error caused by missing gitaly-git2go binary to be marked as done. This means that you claim that

Bug#981777: marked as done (gitlab: Install error in pdfjs-dist/build/pdf.js - module parse error)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #981777, regarding gitlab: Install error in pdfjs-dist/build/pdf.js - module parse error to be marked as done. This means that you

Bug#981776: marked as done (gitlab: Install error in pdfjs-dist/build/pdf.js - module parse error)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #981776, regarding gitlab: Install error in pdfjs-dist/build/pdf.js - module parse error to be marked as done. This means that you

Bug#977751: marked as done (gitlab: node-css-loader 4.x transition)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #977751, regarding gitlab: node-css-loader 4.x transition to be marked as done. This means that you claim that the problem has been

Bug#964218: marked as done (node-yarnpkg: autopkgtest fails with node-uuid 8.2 from experimental - "Cannot read property 'v4' of undefined")

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #964218, regarding node-yarnpkg: autopkgtest fails with node-uuid 8.2 from experimental - "Cannot read property 'v4' of undefined" to

Bug#975493: marked as done (gitlab: Gitlab install script not working)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #975493, regarding gitlab: Gitlab install script not working to be marked as done. This means that you claim that the problem has

Bug#977636: marked as done (gitlab: Package upgrade hangs indefinitely and consumes all CPU/memory)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #977636, regarding gitlab: Package upgrade hangs indefinitely and consumes all CPU/memory to be marked as done. This means that you

Bug#976879: marked as done (gitlab: Missing dependency on "file" (being used in postinst script))

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #976879, regarding gitlab: Missing dependency on "file" (being used in postinst script) to be marked as done. This means that you

Bug#972754: marked as done (gitlab: Uploading images to issues fails due to missing dependency on libimage-exiftool-perl)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #972754, regarding gitlab: Uploading images to issues fails due to missing dependency on libimage-exiftool-perl to be marked as done.

Bug#968286: marked as done (gitlab: adding log rotation)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #968286, regarding gitlab: adding log rotation to be marked as done. This means that you claim that the problem has been dealt with.

Bug#964193: marked as done (gitlab: 500 Errrors at log in because of missing setting in gitlab.yml)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #964193, regarding gitlab: 500 Errrors at log in because of missing setting in gitlab.yml to be marked as done. This means that you

Bug#958445: marked as done (gitlab: 500 error on two-factor auth page)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #958445, regarding gitlab: 500 error on two-factor auth page to be marked as done. This means that you claim that the problem has

Bug#955332: marked as done (gitlab : Gitlab systemdless / apache2)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #955332, regarding gitlab : Gitlab systemdless / apache2 to be marked as done. This means that you claim that the problem has been

Bug#940709: marked as done (Possible improvements to gitlab init script)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #940709, regarding Possible improvements to gitlab init script to be marked as done. This means that you claim that the problem has

Bug#930404: marked as done ([Meta] move gitlab back to main from contrib)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #930404, regarding [Meta] move gitlab back to main from contrib to be marked as done. This means that you claim that the problem has

Bug#915050: marked as done (Keep out of testing)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #915050, regarding Keep out of testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#914159: marked as done (gitlab: Problem with GPG Keys)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #914159, regarding gitlab: Problem with GPG Keys to be marked as done. This means that you claim that the problem has been dealt

Bug#909630: marked as done (gitlab: no sysvinit scripts installed or available)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #909630, regarding gitlab: no sysvinit scripts installed or available to be marked as done. This means that you claim that the

Bug#901338: marked as done (gitlab: dependency on postgresql-contrib pulls in postgresql server)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #901338, regarding gitlab: dependency on postgresql-contrib pulls in postgresql server to be marked as done. This means that you

Bug#909840: marked as done (gitlab: not suitable for stable Debian releases)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #909840, regarding gitlab: not suitable for stable Debian releases to be marked as done. This means that you claim that the problem

Bug#901379: marked as done (gitlab: postinst script should not call psql if database is not managed by dbconfig-common)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #901379, regarding gitlab: postinst script should not call psql if database is not managed by dbconfig-common to be marked as done.

Bug#897444: marked as done (Gitlab: Change repository path does not work)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #897444, regarding Gitlab: Change repository path does not work to be marked as done. This means that you claim that the problem has

Bug#890399: marked as done (gitlab: override.conf in /etc/systemd/system/gitlab-*.service.d is not overwriten)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #890399, regarding gitlab: override.conf in /etc/systemd/system/gitlab-*.service.d is not overwriten to be marked as done. This

Bug#886657: marked as done (gitlab postinst failing when 'apt-get install' or 'reconfigure' when CWD not accessible to gitlab user)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #886657, regarding gitlab postinst failing when 'apt-get install' or 'reconfigure' when CWD not accessible to gitlab user to be

Bug#895648: marked as done ([gitlab] Add keyword that allows the inclusion of external YAML files)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #895648, regarding [gitlab] Add keyword that allows the inclusion of external YAML files to be marked as done. This means that you

Bug#893450: marked as done (gitlab: fresh install have no root account, default root password does not work)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #893450, regarding gitlab: fresh install have no root account, default root password does not work to be marked as done. This means

Bug#865105: marked as done (gitlab: leaves stale systemd service symlinks after purge)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #865105, regarding gitlab: leaves stale systemd service symlinks after purge to be marked as done. This means that you claim that the

Bug#862159: marked as done (gitlab: config.yml.example is not there)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #862159, regarding gitlab: config.yml.example is not there to be marked as done. This means that you claim that the problem has been

Bug#852787: marked as done (gitlab: systemd configuration for sidekiq tears down gitlab service)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #852787, regarding gitlab: systemd configuration for sidekiq tears down gitlab service to be marked as done. This means that you

Bug#851648: marked as done (gitlab-workhorse not logging to file on systemd)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #851648, regarding gitlab-workhorse not logging to file on systemd to be marked as done. This means that you claim that the problem

Bug#848872: marked as done (gitlab: please document how to operate Debian gitlab behind an ssl terminating reverse proxy)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #848872, regarding gitlab: please document how to operate Debian gitlab behind an ssl terminating reverse proxy to be marked as done.

Bug#846180: marked as done (gitlab not restarted after redis-server upgrade)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #846180, regarding gitlab not restarted after redis-server upgrade to be marked as done. This means that you claim that the problem

Bug#847421: marked as done (gitlab should precompile assets itself if relevant dependencies change)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #847421, regarding gitlab should precompile assets itself if relevant dependencies change to be marked as done. This means that you

Bug#839702: marked as done (gitlab: logrotate not working?)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #839702, regarding gitlab: logrotate not working? to be marked as done. This means that you claim that the problem has been dealt

Bug#846179: marked as done (gitlab: Use notify on ready under systemd instead of hack with sleep + check commandline)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #846179, regarding gitlab: Use notify on ready under systemd instead of hack with sleep + check commandline to be marked as done.

Bug#820065: marked as done (gitlab: please adapt the postinst output for Debian)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #820065, regarding gitlab: please adapt the postinst output for Debian to be marked as done. This means that you claim that the

Bug#836551: marked as done (gitlab: short gpg key used in script)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #836551, regarding gitlab: short gpg key used in script to be marked as done. This means that you claim that the problem has been

Bug#831448: marked as done (gitlab: fails to install database)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #831448, regarding gitlab: fails to install database to be marked as done. This means that you claim that the problem has been dealt

Bug#820564: marked as done (gitlab: CI tests broken)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #820564, regarding gitlab: CI tests broken to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1031573: marked as done (RM: jthread -- ROM; abandoned upstream, unmaintained)

Your message dated Sun, 19 Feb 2023 01:04:42 + with message-id and subject line Bug#1031573: Removed package(s) from unstable has caused the Debian Bug report #1031573, regarding RM: jthread -- ROM; abandoned upstream, unmaintained to be marked as done. This means that you claim that the

Bug#1031551: marked as done (RM: cawbird -- ROM; unusable due to changes in Twitter policies and abandoned by the upstream developer)

Your message dated Sun, 19 Feb 2023 01:04:10 + with message-id and subject line Bug#1031551: Removed package(s) from unstable has caused the Debian Bug report #1031551, regarding RM: cawbird -- ROM; unusable due to changes in Twitter policies and abandoned by the upstream developer to be

Bug#1031253: marked as done (jthread: FTBFS (dh_install: error: missing files, aborting))

Your message dated Sun, 19 Feb 2023 01:04:45 + with message-id and subject line Bug#1031573: Removed package(s) from unstable has caused the Debian Bug report #1031253, regarding jthread: FTBFS (dh_install: error: missing files, aborting) to be marked as done. This means that you claim that

Bug#1031519: marked as done (RM: gitlab -- ROM; Remove gitlab from unstable (keep the version in experimental))

Your message dated Sun, 19 Feb 2023 01:02:30 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1031519, regarding RM: gitlab -- ROM; Remove gitlab from unstable (keep the version in experimental) to be marked as done. This

Bug#1025001: marked as done (gitlab: Some UI elements, including buttons, are replaced with "undefined")

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1025001, regarding gitlab: Some UI elements, including buttons, are replaced with "undefined" to be marked as done. This means that

Bug#1029623: marked as done (gitlab: Services are not restarted in case of a missing database server during startup)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1029623, regarding gitlab: Services are not restarted in case of a missing database server during startup to be marked as done.

Bug#1024631: marked as done (gitlab: preinst: invalid number 9.1)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1024631, regarding gitlab: preinst: invalid number 9.1 to be marked as done. This means that you claim that the problem has been

Bug#1024627: marked as done (gitlab: Fails to install)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1024627, regarding gitlab: Fails to install to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1024143: marked as done (gitlab: postinst fails silently within rake-tasks, if /var/lib/gitlab/.cache/yarn/v6 does not exist)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1024143, regarding gitlab: postinst fails silently within rake-tasks, if /var/lib/gitlab/.cache/yarn/v6 does not exist to be marked

Bug#1023291: marked as done (gitlab-sidekiq spamming logs after upgrade to gitlab 15.4.2)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1023291, regarding gitlab-sidekiq spamming logs after upgrade to gitlab 15.4.2 to be marked as done. This means that you claim that

Bug#1022875: marked as done (gitlab: JavaScript not working: Uncaught TypeError renders UI mostly unusable)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1022875, regarding gitlab: JavaScript not working: Uncaught TypeError renders UI mostly unusable to be marked as done. This means

Bug#1019731: marked as done (gitlab: failed to fetch comments in merge requests (500 Internal Server Error))

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1019731, regarding gitlab: failed to fetch comments in merge requests (500 Internal Server Error) to be marked as done. This means

Bug#1018034: marked as done (gitlab: Content editor in Wiki breaks JavaScript)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1018034, regarding gitlab: Content editor in Wiki breaks JavaScript to be marked as done. This means that you claim that the problem

Bug#1019403: marked as done (gitlab: failed to fetch comments in issue (500 Internal Server Error))

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1019403, regarding gitlab: failed to fetch comments in issue (500 Internal Server Error) to be marked as done. This means that you

Bug#1016551: marked as done (cawbird: Switch to librest 1.0 and libsoup3)

Your message dated Sun, 19 Feb 2023 01:04:13 + with message-id and subject line Bug#1031551: Removed package(s) from unstable has caused the Debian Bug report #1016551, regarding cawbird: Switch to librest 1.0 and libsoup3 to be marked as done. This means that you claim that the problem has

Bug#1015302: marked as done (Upgrading 14.10.5 to 15.0.4 aborts on db:migrate)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1015301, regarding Upgrading 14.10.5 to 15.0.4 aborts on db:migrate to be marked as done. This means that you claim that the problem

Bug#1015301: marked as done (gitlab: Upgrade to 15.0.4 fails because BackgroundMigrations could not finalize)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1015301, regarding gitlab: Upgrade to 15.0.4 fails because BackgroundMigrations could not finalize to be marked as done. This means

Bug#1012504: marked as done (cawbird: doesn't migrate because of autopkgtests failure)

Your message dated Sun, 19 Feb 2023 01:04:13 + with message-id and subject line Bug#1031551: Removed package(s) from unstable has caused the Debian Bug report #1012504, regarding cawbird: doesn't migrate because of autopkgtests failure to be marked as done. This means that you claim that the

Bug#1009942: marked as done (gitlab: textEncoding is not defined)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1009942, regarding gitlab: textEncoding is not defined to be marked as done. This means that you claim that the problem has been

Bug#1009954: marked as done (gitlab: Cannot install experimental or unstable version due to ruby-omniauth dependency)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1009954, regarding gitlab: Cannot install experimental or unstable version due to ruby-omniauth dependency to be marked as done.

Bug#1005178: marked as done (gitlab/experimental: binary-any FTBFS)

Your message dated Sun, 19 Feb 2023 01:03:08 + with message-id and subject line Bug#1031519: Removed package(s) from unstable has caused the Debian Bug report #1005178, regarding gitlab/experimental: binary-any FTBFS to be marked as done. This means that you claim that the problem has been

Bug#984294: marked as done (photoflow: ftbfs with GCC-11)

Your message dated Sun, 19 Feb 2023 00:59:16 + with message-id and subject line Bug#1031202: Removed package(s) from unstable has caused the Debian Bug report #984294, regarding photoflow: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#947523: marked as done (gconf-editor: build-depends on deprecated gnome-doc-utils)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #947523, regarding gconf-editor: build-depends on deprecated gnome-doc-utils to be marked as done. This means that you claim that the

Bug#997548: marked as done (golang-github-alangpierce-go-forceexport: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/alangpierce/go-forceexport returned exit code 1)

Your message dated Sun, 19 Feb 2023 01:00:38 + with message-id and subject line Bug#1031263: Removed package(s) from unstable has caused the Debian Bug report #997548, regarding golang-github-alangpierce-go-forceexport: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4

Bug#894056: marked as done (gconf-editor: only useful for gconf which is being removed from Debian)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #894056, regarding gconf-editor: only useful for gconf which is being removed from Debian to be marked as done. This means that you

Bug#829951: marked as done (gconf-editor: Uses deprecated gnome-common macros/variables)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #829951, regarding gconf-editor: Uses deprecated gnome-common macros/variables to be marked as done. This means that you claim that

Bug#661577: marked as done (gconf-editor: Program received signal SIGSEGV, Segmentation fault.)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #661577, regarding gconf-editor: Program received signal SIGSEGV, Segmentation fault. to be marked as done. This means that you claim

Bug#661183: marked as done (gconf-editor: Moving via arrowkeys in tree)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #661183, regarding gconf-editor: Moving via arrowkeys in tree to be marked as done. This means that you claim that the problem has

Bug#650766: marked as done (gconf-editor: inconsistent layout of context help)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #650766, regarding gconf-editor: inconsistent layout of context help to be marked as done. This means that you claim that the problem

Bug#645304: marked as done (gconf-editor: search box should keep previous search term)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #645304, regarding gconf-editor: search box should keep previous search term to be marked as done. This means that you claim that the

Bug#614991: marked as done (german translation: parameter wrong)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #614991, regarding german translation: parameter wrong to be marked as done. This means that you claim that the problem has been

Bug#528987: marked as done (gconf-editor: I suggest a wording change in the description, please.)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #528987, regarding gconf-editor: I suggest a wording change in the description, please. to be marked as done. This means that you

Bug#476904: marked as done (gconf-editor: please add context menu options to main menu also)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #476904, regarding gconf-editor: please add context menu options to main menu also to be marked as done. This means that you claim

Bug#1031263: marked as done (RM: golang-github-alangpierce-go-forceexport -- RoQA; Not working since Go1.17, upstream seems abandoned)

Your message dated Sun, 19 Feb 2023 01:00:34 + with message-id and subject line Bug#1031263: Removed package(s) from unstable has caused the Debian Bug report #1031263, regarding RM: golang-github-alangpierce-go-forceexport -- RoQA; Not working since Go1.17, upstream seems abandoned to be

Bug#465687: marked as done (gconf-editor: Please support multiple user configuration sources)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #465687, regarding gconf-editor: Please support multiple user configuration sources to be marked as done. This means that you claim

Bug#179299: marked as done (gconf-editor: Forgets layout when closed)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #179299, regarding gconf-editor: Forgets layout when closed to be marked as done. This means that you claim that the problem has been

Bug#1031397: marked as done (RM: python-omemo-backend-signal -- ROM; obsolete, unmaintained)

Your message dated Sun, 19 Feb 2023 01:01:17 + with message-id and subject line Bug#1031397: Removed package(s) from unstable has caused the Debian Bug report #1031397, regarding RM: python-omemo-backend-signal -- ROM; obsolete, unmaintained to be marked as done. This means that you claim

Bug#1031242: marked as done (RM: django-hvad -- ROM; abandoned upstream ; unmaintained; EOL upstream)

Your message dated Sun, 19 Feb 2023 00:59:46 + with message-id and subject line Bug#1031242: Removed package(s) from unstable has caused the Debian Bug report #1031242, regarding RM: django-hvad -- ROM; abandoned upstream ; unmaintained; EOL upstream to be marked as done. This means that

Bug#1031202: marked as done (RM: photoflow -- ROM; appears dead upstream, FTBFS)

Your message dated Sun, 19 Feb 2023 00:59:12 + with message-id and subject line Bug#1031202: Removed package(s) from unstable has caused the Debian Bug report #1031202, regarding RM: photoflow -- ROM; appears dead upstream, FTBFS to be marked as done. This means that you claim that the

Bug#1031172: marked as done (RM: gconf-editor -- ROM; not in bullseye or bookworm, obsolete)

Your message dated Sun, 19 Feb 2023 00:58:21 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #1031172, regarding RM: gconf-editor -- ROM; not in bullseye or bookworm, obsolete to be marked as done. This means that you claim

Bug#1026622: marked as done (python-omemo-backend-signal: FTBFS: ModuleNotFoundError: No module named 'omemo.backends')

Your message dated Sun, 19 Feb 2023 01:01:21 + with message-id and subject line Bug#1031397: Removed package(s) from unstable has caused the Debian Bug report #1026622, regarding python-omemo-backend-signal: FTBFS: ModuleNotFoundError: No module named 'omemo.backends' to be marked as done.

Bug#1018898: marked as done (gconf-editor: Intent to request removal from Debian)

Your message dated Sun, 19 Feb 2023 00:58:31 + with message-id and subject line Bug#1031172: Removed package(s) from unstable has caused the Debian Bug report #1018898, regarding gconf-editor: Intent to request removal from Debian to be marked as done. This means that you claim that the

Bug#1031302: marked as done (devscripts FTBFS with black 23.1.0)

Your message dated Sun, 19 Feb 2023 00:35:20 + with message-id and subject line Bug#1031302: fixed in devscripts 2.23.2 has caused the Debian Bug report #1031302, regarding devscripts FTBFS with black 23.1.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#1031487: marked as done (devscripts: FTBFS: AssertionError: black found code that needs reformatting:)

Your message dated Sun, 19 Feb 2023 00:35:20 + with message-id and subject line Bug#1031302: fixed in devscripts 2.23.2 has caused the Debian Bug report #1031302, regarding devscripts: FTBFS: AssertionError: black found code that needs reformatting: to be marked as done. This means that you

Bug#1031549: marked as done (debchange man page: uneven indentation in option list)

Your message dated Sun, 19 Feb 2023 00:35:20 + with message-id and subject line Bug#1031549: fixed in devscripts 2.23.2 has caused the Debian Bug report #1031549, regarding debchange man page: uneven indentation in option list to be marked as done. This means that you claim that the problem

Bug#1030141: marked as done (build-rdeps man page: undocumented -q)

Your message dated Sun, 19 Feb 2023 00:35:20 + with message-id and subject line Bug#1030141: fixed in devscripts 2.23.2 has caused the Debian Bug report #1030141, regarding build-rdeps man page: undocumented -q to be marked as done. This means that you claim that the problem has been dealt

Bug#1031583: marked as done (rust-sequoia-sq: FTBFS in testing: build-dependency not installable: librust-rpassword-5+default-dev)

Your message dated Sun, 19 Feb 2023 00:15:30 + with message-id <814857f1-2f1d-620d-32a8-8c7bda0ae...@debian.org> and subject line re: rust-sequoia-sq: FTBFS in testing: build-dependency not installable: librust-rpassword-5+default-dev has caused the Debian Bug report #1031583, regarding

  1   2   >