Your message dated Sat, 17 Dec 2022 22:10:00 -0500
with message-id
and subject line Re: Bug#1025771: python3-matplotlib: package delivers
jquery-1.7.1 whith XSS Vulnerability known from CVE-2012-6708
has caused the Debian Bug report #1025771,
regarding python3-matplotlib: package delivers jquery
Processing commands for cont...@bugs.debian.org:
> forcemerge 1020018 1025733
Bug #1020018 {Done: Nicolas Boulenguez } [src:libxmlada]
libxmlada: FTBFS: unsatisfiable build-dependency: unicode-data (< 15~) but
15.0.0-1 is to be installed
Bug #1025733 [src:libxmlada] libxmlada: unsatisfiable buil
Your message dated Sat, 17 Dec 2022 23:18:25 +0100
with message-id
and subject line Re: Bug#1026289: surf: The app opens, only displays a blank
page
has caused the Debian Bug report #1026289,
regarding surf: The app opens, only displays a blank page
to be marked as done.
This means that you clai
Processing commands for cont...@bugs.debian.org:
> forwarded 1025326 https://gitlab.freedesktop.org/mesa/mesa/-/issues/7819
Bug #1025326 [libgl1-mesa-dri] tigervnc-standalone-server: Upgrade of
libgl1-mesa-dri to 22.3.0 breaks Xvnc
Set Bug forwarded-to-address to
'https://gitlab.freedesktop.org/
Your message dated Sat, 17 Dec 2022 20:10:52 +
with message-id <7aa6ad5ad06a51bf99c646cea95a9009fb677df2.ca...@gmail.com>
and subject line Re: [deluge] crashes on load
has caused the Debian Bug report #1026240,
regarding [deluge] crashes on load
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> reassign 1025326 mesa 22.3.0-1
Bug #1025326 [tigervnc-standalone-server] tigervnc-standalone-server: Upgrade
of libgl1-mesa-dri to 22.3.0 breaks Xvnc
Bug reassigned from package 'tigervnc-standalone-server' to 'mesa'.
No longer marked as found in
Processing commands for cont...@bugs.debian.org:
> close 975596
Bug #975596 [python3-paramiko] dput-ng: traceback with ssh-upload when
python3-gssapi is installed
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
975596: https://bugs.debian.org/c
Your message dated Sat, 17 Dec 2022 14:00:37 -0500
with message-id
and subject line Re: Further information
has caused the Debian Bug report #896056,
regarding python-paramiko: SSH key login fails since 2.0.0
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Sat, 17 Dec 2022 19:26:16 +0100
with message-id
and subject line Re: Bug#1025531: transition: elpi 1.16.8-1
has caused the Debian Bug report #1025531,
regarding transition: elpi 1.16.8-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Processing control commands:
> close -1 1.13.8+dfsg-1
Bug #1026285 [src:ruby-nokogiri] src:ruby-nokogiri: fails to migrate to testing
for too long: FTBFS on some arch
Marked as fixed in versions ruby-nokogiri/1.13.8+dfsg-1.
Bug #1026285 [src:ruby-nokogiri] src:ruby-nokogiri: fails to migrate to t
Your message dated Sat, 17 Dec 2022 18:52:11 +0100
with message-id <7fa5687d-42dc-7ec4-d8dc-3d91cef39...@debian.org>
and subject line Close Bug #964882
has caused the Debian Bug report #964882,
regarding ITP: templating-maven-plugin -- Copying files to an output directory
to be marked as done.
Thi
Processing control commands:
> close -1 43.2-1
Bug #1026279 [src:mutter] src:mutter: fails to migrate to testing for too long:
autopkgtest regression and FTBFS on armhf
Marked as fixed in versions mutter/43.2-1.
Bug #1026279 [src:mutter] src:mutter: fails to migrate to testing for too long:
auto
Your message dated Sat, 17 Dec 2022 16:48:25 +
with message-id
and subject line Bug#1025706: fixed in squashfuse 0.1.105-1
has caused the Debian Bug report #1025706,
regarding squashfuse: link against fuse3
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 17 Dec 2022 15:51:28 +
with message-id
and subject line Bug#1026257: fixed in node-zx 7.1.1+~cs6.7.23-2
has caused the Debian Bug report #1026257,
regarding FTBFS: more network tests in node-zx
to be marked as done.
This means that you claim that the problem has been d
Your message dated Sat, 17 Dec 2022 15:51:10 +
with message-id
and subject line Bug#1026252: fixed in lintian-brush 0.145
has caused the Debian Bug report #1026252,
regarding lintian-brush: Do not "fix" "uses-debhelper-compat-file" for
non-stable debhelper compat levels
to be marked as done.
Your message dated Sat, 17 Dec 2022 15:51:10 +
with message-id
and subject line Bug#1026052: fixed in lintian-brush 0.145
has caused the Debian Bug report #1026052,
regarding lintian-brush: fixer unused-build-dependency-on-cdbs fails if there
is no Build-Depends
to be marked as done.
This me
Your message dated Sat, 17 Dec 2022 15:26:39 +
with message-id
and subject line Bug#1026202: Removed package(s) from unstable
has caused the Debian Bug report #999713,
regarding ruby-omniauth-cas3: FTBFS with ruby-omniauth 2.0.x: ERROR: Test
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygem
Your message dated Sat, 17 Dec 2022 15:26:35 +
with message-id
and subject line Bug#1026202: Removed package(s) from unstable
has caused the Debian Bug report #1026202,
regarding RM: ruby-omniauth-cas3 -- ROM; upstream inactive
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 17 Dec 2022 15:25:38 +
with message-id
and subject line Bug#1026203: Removed package(s) from unstable
has caused the Debian Bug report #999712,
regarding ruby-omniauth-azure-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR:
Test "ruby2.7" failed:
/usr/lib/ruby/vendor_rub
Your message dated Sat, 17 Dec 2022 15:25:35 +
with message-id
and subject line Bug#1026203: Removed package(s) from unstable
has caused the Debian Bug report #1026203,
regarding RM: ruby-omniauth-azure-oauth2 -- ROM; upstream inactive
to be marked as done.
This means that you claim that the
Your message dated Sat, 17 Dec 2022 15:23:36 +
with message-id
and subject line Bug#1026135: Removed package(s) from unstable
has caused the Debian Bug report #999723,
regarding ruby-omniauth-remote-user: FTBFS with ruby-omniauth 2.0.x: ERROR:
Test "ruby2.7" failed:
/usr/lib/ruby/vendor_ruby
Your message dated Sat, 17 Dec 2022 15:23:36 +
with message-id
and subject line Bug#1026135: Removed package(s) from unstable
has caused the Debian Bug report #959557,
regarding ruby-omniauth-remote-user: FTBFS: ERROR: Test "ruby2.7" failed:
NoMethodError: undefined method `strip' for nil:Nil
Your message dated Sat, 17 Dec 2022 15:23:32 +
with message-id
and subject line Bug#1026135: Removed package(s) from unstable
has caused the Debian Bug report #1026135,
regarding RM: ruby-omniauth-remote-user -- ROM; upstream inactive
to be marked as done.
This means that you claim that the p
Your message dated Sat, 17 Dec 2022 15:22:06 +
with message-id
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #982774,
regarding haskell-uri: Wrong homepage + new version
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 17 Dec 2022 15:22:02 +
with message-id
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #1026157,
regarding RM: haskell-uri -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Sat, 17 Dec 2022 15:20:45 +
with message-id
and subject line Bug#1026156: Removed package(s) from unstable
has caused the Debian Bug report #1026156,
regarding RM: haskell-thyme -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 17 Dec 2022 15:22:06 +
with message-id
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #1018030,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:20:10 +
with message-id
and subject line Bug#1026154: Removed package(s) from unstable
has caused the Debian Bug report #1026154,
regarding RM: haskell-text-format -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 17 Dec 2022 15:20:49 +
with message-id
and subject line Bug#1026156: Removed package(s) from unstable
has caused the Debian Bug report #1022920,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:20:49 +
with message-id
and subject line Bug#1026156: Removed package(s) from unstable
has caused the Debian Bug report #1021574,
regarding haskell-thyme FTBFS: Couldn't match type
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 17 Dec 2022 15:20:15 +
with message-id
and subject line Bug#1026154: Removed package(s) from unstable
has caused the Debian Bug report #1022918,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:22:06 +
with message-id
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #1017253,
regarding haskell-uri: FTBFS: hlibrary.setup: Encountered missing or private
dependencies: parsec >=3.0 && <=3.1.11
to be ma
Your message dated Sat, 17 Dec 2022 15:20:15 +
with message-id
and subject line Bug#1026154: Removed package(s) from unstable
has caused the Debian Bug report #1014001,
regarding haskell-text-format FTBFS: hlibrary.setup: Encountered missing or
private dependencies: base >=4.3 && <4.15
to be
Your message dated Sat, 17 Dec 2022 15:17:10 +
with message-id
and subject line Bug#1026152: Removed package(s) from unstable
has caused the Debian Bug report #837766,
regarding wrapped list in long description
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Sat, 17 Dec 2022 15:17:45 +
with message-id
and subject line Bug#1026153: Removed package(s) from unstable
has caused the Debian Bug report #1026153,
regarding RM: haskell-test-framework-th-prime -- ROM; obsolete
to be marked as done.
This means that you claim that the prob
Your message dated Sat, 17 Dec 2022 15:17:06 +
with message-id
and subject line Bug#1026152: Removed package(s) from unstable
has caused the Debian Bug report #1026152,
regarding RM: haskell-relational-schemas -- ROM; obsolete
to be marked as done.
This means that you claim that the problem h
Your message dated Sat, 17 Dec 2022 15:17:49 +
with message-id
and subject line Bug#1026153: Removed package(s) from unstable
has caused the Debian Bug report #1022913,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:17:10 +
with message-id
and subject line Bug#1026152: Removed package(s) from unstable
has caused the Debian Bug report #1022196,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:17:49 +
with message-id
and subject line Bug#1026153: Removed package(s) from unstable
has caused the Debian Bug report #1015288,
regarding haskell-test-framework-th-prime FTBFS: Couldn't match expected type
‘Maybe Exp’ with actual type ‘Exp’
to be marke
Your message dated Sat, 17 Dec 2022 15:16:05 +
with message-id
and subject line Bug#1026151: Removed package(s) from unstable
has caused the Debian Bug report #1026151,
regarding RM: haskell-relational-query-hdbc -- ROM; obsolete
to be marked as done.
This means that you claim that the proble
Your message dated Sat, 17 Dec 2022 15:15:10 +
with message-id
and subject line Bug#1026149: Removed package(s) from unstable
has caused the Debian Bug report #1026149,
regarding RM: haskell-relational-record -- ROM; obsolete
to be marked as done.
This means that you claim that the problem ha
Your message dated Sat, 17 Dec 2022 15:15:42 +
with message-id
and subject line Bug#1026150: Removed package(s) from unstable
has caused the Debian Bug report #1022191,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:15:38 +
with message-id
and subject line Bug#1026150: Removed package(s) from unstable
has caused the Debian Bug report #1026150,
regarding RM: haskell-persistable-types-hdbc-pg -- ROM; obsolete
to be marked as done.
This means that you claim that the pr
Your message dated Sat, 17 Dec 2022 15:15:14 +
with message-id
and subject line Bug#1026149: Removed package(s) from unstable
has caused the Debian Bug report #1022195,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:16:09 +
with message-id
and subject line Bug#1026151: Removed package(s) from unstable
has caused the Debian Bug report #1022194,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:14:11 +
with message-id
and subject line Bug#1026148: Removed package(s) from unstable
has caused the Debian Bug report #1026148,
regarding RM: haskell-pipes-zlib -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 17 Dec 2022 15:12:54 +
with message-id
and subject line Bug#1026147: Removed package(s) from unstable
has caused the Debian Bug report #1026147,
regarding RM: haskell-monad-unlift -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has bee
Your message dated Sat, 17 Dec 2022 15:12:58 +
with message-id
and subject line Bug#1026147: Removed package(s) from unstable
has caused the Debian Bug report #1022906,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:14:15 +
with message-id
and subject line Bug#1026148: Removed package(s) from unstable
has caused the Debian Bug report #103,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:14:15 +
with message-id
and subject line Bug#1026148: Removed package(s) from unstable
has caused the Debian Bug report #1015280,
regarding haskell-pipes-zlib FTBFS: error: Couldn't match type
to be marked as done.
This means that you claim that the prob
Your message dated Sat, 17 Dec 2022 15:12:58 +
with message-id
and subject line Bug#1026147: Removed package(s) from unstable
has caused the Debian Bug report #1013996,
regarding haskell-monad-unlift FTBFS: error: Couldn't match type
to be marked as done.
This means that you claim that the pr
Your message dated Sat, 17 Dec 2022 15:11:52 +
with message-id
and subject line Bug#1026146: Removed package(s) from unstable
has caused the Debian Bug report #1026146,
regarding RM: haskell-maths -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 17 Dec 2022 15:11:56 +
with message-id
and subject line Bug#1026146: Removed package(s) from unstable
has caused the Debian Bug report #1022905,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:11:56 +
with message-id
and subject line Bug#1026146: Removed package(s) from unstable
has caused the Debian Bug report #1013795,
regarding haskell-maths FTBFS: error: Bang pattern in expression context: !j
to be marked as done.
This means that you claim
Your message dated Sat, 17 Dec 2022 15:10:34 +
with message-id
and subject line Bug#1026144: Removed package(s) from unstable
has caused the Debian Bug report #982490,
regarding haskell-hsh: Wrong homepage
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Sat, 17 Dec 2022 15:11:28 +
with message-id
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #982489,
regarding haskell-hashmap: Wrong homepage
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Sat, 17 Dec 2022 15:11:24 +
with message-id
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #1026145,
regarding RM: haskell-hashmap -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Sat, 17 Dec 2022 15:10:30 +
with message-id
and subject line Bug#1026144: Removed package(s) from unstable
has caused the Debian Bug report #1026144,
regarding RM: haskell-hsh -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Sat, 17 Dec 2022 15:08:37 +
with message-id
and subject line Bug#1026141: Removed package(s) from unstable
has caused the Debian Bug report #1017242,
regarding haskell-descriptive: FTBFS: • Couldn't match expected type ‘Key’ with
actual type ‘Text’ • In the second argument
Your message dated Sat, 17 Dec 2022 15:09:59 +
with message-id
and subject line Bug#1026143: Removed package(s) from unstable
has caused the Debian Bug report #1026143,
regarding RM: haskell-ghc-mtl -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Sat, 17 Dec 2022 15:09:29 +
with message-id
and subject line Bug#1026142: Removed package(s) from unstable
has caused the Debian Bug report #1026142,
regarding RM: haskell-djinn-ghc -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been d
Your message dated Sat, 17 Dec 2022 15:08:34 +
with message-id
and subject line Bug#1026141: Removed package(s) from unstable
has caused the Debian Bug report #1026141,
regarding RM: haskell-descriptive -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 17 Dec 2022 15:10:04 +
with message-id
and subject line Bug#1026143: Removed package(s) from unstable
has caused the Debian Bug report #1022901,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:08:37 +
with message-id
and subject line Bug#1026141: Removed package(s) from unstable
has caused the Debian Bug report #1021070,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:09:33 +
with message-id
and subject line Bug#1026142: Removed package(s) from unstable
has caused the Debian Bug report #1022053,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:11:28 +
with message-id
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #1020252,
regarding libghc-hashmap-doc: Depends: haddock-interface-35 but it is not
installable
to be marked as done.
This means that
Your message dated Sat, 17 Dec 2022 15:11:28 +
with message-id
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #1020782,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:10:34 +
with message-id
and subject line Bug#1026144: Removed package(s) from unstable
has caused the Debian Bug report #1018051,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:10:04 +
with message-id
and subject line Bug#1026143: Removed package(s) from unstable
has caused the Debian Bug report #1014021,
regarding haskell-ghc-mtl FTBFS: error: Could not find module
to be marked as done.
This means that you claim that the probl
Your message dated Sat, 17 Dec 2022 15:09:33 +
with message-id
and subject line Bug#1026142: Removed package(s) from unstable
has caused the Debian Bug report #1014002,
regarding haskell-djinn-ghc FTBFS: error: Could not find module
to be marked as done.
This means that you claim that the pro
Your message dated Sat, 17 Dec 2022 15:07:55 +
with message-id
and subject line Bug#1026140: Removed package(s) from unstable
has caused the Debian Bug report #1017011,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:07:55 +
with message-id
and subject line Bug#1026140: Removed package(s) from unstable
has caused the Debian Bug report #1017207,
regarding haskell-binary-tagged: FTBFS: unsatisfiable build-dependencies:
libghc-aeson-dev (< 1.5), libghc-base16-bytestring
Your message dated Sat, 17 Dec 2022 16:05:43 +0100
with message-id <875yea5auw@43-1.org>
and subject line Re: RM: recipe-scrapers -- ROM; Upstream switched to
scrape-schema-recipe
has caused the Debian Bug report #1026208,
regarding RM: recipe-scrapers -- ROM; Upstream switched to scrape-schem
Your message dated Sat, 17 Dec 2022 15:07:51 +
with message-id
and subject line Bug#1026140: Removed package(s) from unstable
has caused the Debian Bug report #1026140,
regarding RM: haskell-binary-tagged -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has be
Your message dated Sat, 17 Dec 2022 14:42:29 +
with message-id
and subject line Bug#1025588: fixed in osmnx 1.2.3+ds-1
has caused the Debian Bug report #1025588,
regarding osmnx: FTBFS with Shapely 2.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Sat, 17 Dec 2022 14:43:18 +
with message-id
and subject line Bug#1025526: fixed in rust-nix 0.26.1-2
has caused the Debian Bug report #1025526,
regarding rust-nix: please upgrade to v0.26.1
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Sat, 17 Dec 2022 14:54:14 +0100
with message-id
and subject line Re: Bug#1025832: transition: libkeduvocdocument
has caused the Debian Bug report #1025832,
regarding transition: libkeduvocdocument
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Sat, 17 Dec 2022 14:44:40 +0100 (CET)
with message-id
and subject line
has caused the Debian Bug report #1025944,
regarding rust-castaway: please upgrasde to v0.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it i
Your message dated Sat, 17 Dec 2022 14:44:43 +0100
with message-id
and subject line Re: Bug#1025768: transition: snapd-glib 1.63
has caused the Debian Bug report #1025768,
regarding transition: snapd-glib 1.63
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Processing commands for cont...@bugs.debian.org:
> reassign 1023911 swig
Bug #1023911 [src:xdmf] xdmf FTBFS with SWIG 4.1.0
Bug reassigned from package 'src:xdmf' to 'swig'.
No longer marked as found in versions xdmf/3.0+git20190531-11.
Ignoring request to alter fixed versions of bug #1023911 to t
Processing commands for cont...@bugs.debian.org:
> close 1023353
Bug #1023353 [php-faker] [php-faker] Failing tests with PHP 8.2
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1023353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023353
D
Your message dated Sat, 17 Dec 2022 13:16:51 +
with message-id
and subject line re: rust-siphasher: please update to v0.3.9
has caused the Debian Bug report #1022546,
regarding rust-siphasher: please update to v0.3.9
to be marked as done.
This means that you claim that the problem has been de
Your message dated Sat, 17 Dec 2022 13:13:09 +
with message-id <9dbac8b0-0617-2d30-409f-0e3569d77...@p10link.net>
and subject line re: rust-rustyline: please upgrade to v9
has caused the Debian Bug report #1022198,
regarding rust-rustyline: please upgrade to v9
to be marked as done.
This means
Your message dated Sat, 17 Dec 2022 12:22:32 +
with message-id
and subject line Bug#1026155: fixed in python-trio 0.22.0-0.1
has caused the Debian Bug report #1026155,
regarding python3-trio: MultiError implementation conflicts with
BaseExceptionGroup backport in Python 3.10
to be marked as d
Your message dated Sat, 17 Dec 2022 11:20:46 +
with message-id
and subject line Bug#1024555: fixed in swig 4.1.0-0.2
has caused the Debian Bug report #1024555,
regarding xdmf FTBFS with SWIG 4.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 17 Dec 2022 11:18:56 +
with message-id
and subject line Bug#1024304: fixed in rust-cargo-outdated 0.11.1-1
has caused the Debian Bug report #1024304,
regarding rust-cargo-outdated - build-depends on obsolete version of rust-cargo.
to be marked as done.
This means that
Your message dated Sat, 17 Dec 2022 11:06:27 +
with message-id
and subject line Bug#1025840: fixed in deepin-log-viewer 5.9.7+ds1-2
has caused the Debian Bug report #1025840,
regarding deepin-log-viewer: build-depends on dropped virtual package
to be marked as done.
This means that you claim
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025774,
regarding bullseye-pu: package evolution/3.38.3-1+deb1
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025766,
regarding bullseye-pu: package
golang-github-go-chef-
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025764,
regarding bullseye-pu: package isoquery/3.2.4-1+deb11u
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025758,
regarding bullseye-pu: package efitools/1.9.2-2~deb11u
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025756,
regarding bullseye-pu: package nvidia-graphics-drivers
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025755,
regarding bullseye-pu: package dovecot-fts-xapian/1.4.
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025750,
regarding bullseye-pu: package
nvidia-graphics-driver
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025754,
regarding bullseye-pu: package containerd/1.4.13~ds1-1
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025716,
regarding bullseye-pu: package mutt/2.0.5-4.1+deb11u2
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025710,
regarding bullseye-pu: package awstats/7.8-2+deb11u1
t
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025700,
regarding bullseye-pu: package virglrenderer/0.8.2-5+d
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025646,
regarding bullseye-pu: package libapache2-mod-auth-mel
Your message dated Sat, 17 Dec 2022 10:57:10 +
with message-id
<03e9b90cf2f149b9e2835590c9ec0ccb048b744d.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 11.6
has caused the Debian Bug report #1025652,
regarding bullseye-pu: package
nvidia-graphics-driver
1 - 100 of 153 matches
Mail list logo
