Your message dated Tue, 09 Nov 2021 13:34:28 +0000
with message-id <[email protected]>
and subject line Bug#996139: fixed in ruby-bluefeather 0.41-6
has caused the Debian Bug report #996139,
regarding ruby-bluefeather: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
NoMethodError:
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
996139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996139
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-bluefeather
Version: 0.41-5.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: [email protected]
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-bluefeather was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> NoMethodError:
> undefined method `escape' for URI:Module
> # ./lib/bluefeather.rb:2016:in `escape_to_header_id'
> # ./lib/bluefeather.rb:1641:in `block in transform_headers'
> # ./lib/bluefeather.rb:1588:in `gsub'
> # ./lib/bluefeather.rb:1588:in `transform_headers'
> # ./lib/bluefeather.rb:732:in `apply_block_transforms'
> # ./lib/bluefeather.rb:546:in `parse_text'
> # ./lib/bluefeather.rb:583:in `parse_text_with_render_state'
> # ./spec/header-id.rb:42:in `block (2 levels) in <top (required)>'
>
> Deprecation Warnings:
>
> --------------------------------------------------------------------------------
> CUIMatcher::WriteToStderr implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/cui.rb:25:in `block (2 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> CUIMatcher::WriteToStderr implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/cui.rb:32:in `block (2 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> CUIMatcher::WriteToStderr implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/cui.rb:38:in `block (2 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> Too many similar deprecation messages reported, disregarding further reports.
> Pass `--deprecation-out` or set `config.deprecation_stream` to a file for
> full output.
>
> --------------------------------------------------------------------------------
> CUIMatcher::WriteToStdout implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/cui.rb:24:in `block (2 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> CUIMatcher::WriteToStdout implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/cui.rb:31:in `block (2 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> CUIMatcher::WriteToStdout implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/cui.rb:37:in `block (2 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> Too many similar deprecation messages reported, disregarding further reports.
> Pass `--deprecation-out` or set `config.deprecation_stream` to a file for
> full output.
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/auto-link.rb:58:in `block (5 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/auto-link.rb:59:in `block (5 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:100:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:101:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:116:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:117:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:132:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:196:in `block (3 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:19:in `block (3 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:248:in `block (3 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:36:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/header-id.rb:19:in `block (3 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/header-id.rb:31:in `block (3 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/dl.rb:97:in `block (3 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/dl.rb:132:in `block (3 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/encoding.rb:32:in `block (3 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> Too many similar deprecation messages reported, disregarding further reports.
> Pass `--deprecation-out` or set `config.deprecation_stream` to a file for
> full output.
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElement implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/toc.rb:34:in `block (4 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/auto-link.rb:28:in `block (5 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/auto-link.rb:29:in `block (5 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/auto-link.rb:86:in `block (5 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/auto-link.rb:87:in `block (5 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:115:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:131:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:165:in `block (2 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:18:in `block (3 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:195:in `block (3 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:221:in `block (3 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:247:in `block (3 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:35:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:46:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:47:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/code-block.rb:99:in `block (4 levels) in
> <top (required)>')
> --------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/dl.rb:88:in `block (3 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/dl.rb:89:in `block (3 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/dl.rb:122:in `block (3 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> Too many similar deprecation messages reported, disregarding further reports.
> Pass `--deprecation-out` or set `config.deprecation_stream` to a file for
> full output.
>
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/dl.rb:19:in `block (4 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/dl.rb:20:in `block (4 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> --------------------------------------------------------------------------------
> NokogiriMatcher::HaveElements implements a legacy RSpec matcher
> protocol. For the current protocol you should expose the failure messages
> via the `failure_message` and `failure_message_when_negated` methods.
> (Used from /<<PKGBUILDDIR>>/spec/dl.rb:21:in `block (4 levels) in <top
> (required)>')
> --------------------------------------------------------------------------------
> Too many similar deprecation messages reported, disregarding further reports.
> Pass `--deprecation-out` or set `config.deprecation_stream` to a file for
> full output.
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from /<<PKGBUILDDIR>>/spec/auto-link.rb:28:in
> `block (5 levels) in <top (required)>'.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 77 deprecation warnings total
>
> Finished in 0.26209 seconds (files took 0.31774 seconds to load)
> 184 examples, 1 failure, 2 pending
>
> Failed examples:
>
> rspec ./spec/header-id.rb:70 # Auto Generated Header ID: escape: pattern
> matched
>
> /usr/bin/ruby3.0 -Ku
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern spec/\*.rb failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-bluefeather/ruby-bluefeather_0.41-5.1+rebuild1633375808_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-bluefeather
Source-Version: 0.41-6
Done: Daniel Leidert <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ruby-bluefeather, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert <[email protected]> (supplier of updated ruby-bluefeather
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 09 Nov 2021 13:58:33 +0100
Source: ruby-bluefeather
Architecture: source
Version: 0.41-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<[email protected]>
Changed-By: Daniel Leidert <[email protected]>
Closes: 996139
Changes:
ruby-bluefeather (0.41-6) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Bump debhelper from old 11 to 13.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright (Copyright): Add team.
* d/rules: Use gem installation layout.
* d/patches/fix_uri_escape_deprecation.patch: Add patch.
- Work around deprecation of URI.escape to fix FTBFS (closes: #996139).
* d/patches/series: Enable new patch.
Checksums-Sha1:
cac1e8fc378de3a1b300b7285c234ee516b58436 2089 ruby-bluefeather_0.41-6.dsc
635a1abbfc38e3aa6b585802a26a151b30ee2abb 6596
ruby-bluefeather_0.41-6.debian.tar.xz
341f88f62f613150ad53cbff4a96df4c116164ce 9452
ruby-bluefeather_0.41-6_amd64.buildinfo
Checksums-Sha256:
fdd855f02c88828ce162cdef3470c8c913b012e74e480b2cbff1fe1fad3e1c97 2089
ruby-bluefeather_0.41-6.dsc
7aca7a9ff5bd9d1748bd0868afe80c29595367d349da28e1769dca86198bb0e8 6596
ruby-bluefeather_0.41-6.debian.tar.xz
3c4730e87ef302afdd72052a5b839be9a6acc2ef336559637cfcb8e26e7d068d 9452
ruby-bluefeather_0.41-6_amd64.buildinfo
Files:
7badf6a79e1bd232228b11d6068586d8 2089 ruby optional ruby-bluefeather_0.41-6.dsc
79dec5e47713f9af3c60e580169bf862 6596 ruby optional
ruby-bluefeather_0.41-6.debian.tar.xz
87dff31f08a0bfe0b165e05e3cf76766 9452 ruby optional
ruby-bluefeather_0.41-6_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGKc4EACgkQS80FZ8KW
0F2WFBAAqiygdt7mTJVnDZG6u3LKp8IBQvBc+eUdyJcXJlpkmvDGLyI4EF0pp5gp
ThiUEjOa+RC/SSrXHCk4yk8YFh0Wlfkc0O+laSVNBPDt5cNIH9UM1uhYRp2lfoKB
JNFGs7C9Ak4cMyZTh/lTYyPh8Wr+ktMT2zW75Yf6SnuM1S2uurd3xJni4LVggGwc
Sr+YztS+F8ifdQAAkhtAsmN7y4kAGrwxNQIDGBIcuZuxBvL2bWgm4BVdB9hCO0Pe
G8XKkGt6oUxiyffisVAnVvLmXNmwCh7FpGZCoqI9Asb2wdEC+5IHDj3ZcwcCbeTa
PYbYOBCb1iX9o5DMvgY7qesT9xmBNfvkW/7zBqtN0py0ANpQFhhnmNh3raVjceJQ
eyu96exeddXMhWyux9cLXj+1z71eIdeGP3J71cX+jGXiBjJsBYzN3T2rYEdPbGAs
KTh41irIiOQptCVx0WG6ZfdZsC7QVXlxatn3l5B0nKWAyJ0CmiqCAkJhbfERsqdb
eHhYLACNNp2MbuU51OU7mcoWJVV5328ltczFhRIY2iIkfMuuJg31fqwmDRWP3zqw
I+ryK0o8rhwBMCDhATToXq2uJWMuF2ykjU2aWiYPIHjUuRIZQp1LLX0UMwg2TpIY
6A+/7m5GOu3Pk6jRFHUDRXAFobWx7YdX2d4SXoDSmJatSznx9TI=
=rqVl
-----END PGP SIGNATURE-----
--- End Message ---
