EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch

[Zhiwei Zhu]

Hi,

I tried to install TurboGears-1.1.3 on my RedHat EL7 Beta server with yum install and got these error message:
Error: Package: TurboGears-1.1.3-8.el7.noarch (epel)
           Requires: python-webtest
Error: Package: python-cheetah-2.4.4-4.el7.x86_64 (epel)
           Requires: python-pygments
Error: Package: python-sqlobject-1.2.2-3.el7.noarch (epel)
           Requires: postgresql-python
Error: Package: python-genshi-0.7-3.el7.x86_64 (epel)
           Requires: python-babel >= 0.8
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles -nodigest

Is there anyone caring this or do we have any plan to fix this dependency issue?

Thank you in advance.

------------------------------
Best Regards
Jacky

[wargaming.net]
EgzO3mXGcK

This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg

[Christopher Meng]

I would suggest you using pip to install these packages.

First these packages in repo are old and may not match your need.

https://bugzilla.redhat.com/show_bug.cgi?id=852998

Second these packages are used for Fedora infrastructure apps, and since
the technology is moving forwardly, these packages may be retired.

Thanks.

[Zhiwei Zhu]

Hi Christopher,

Thanks for your quick response. I understand the situation and Turbogears-1.1.3 may be old.

I also tried Turbogears2 (which is TurboGears2-2.3.0) and got these errors:
Error: Package: python-transaction-1.4.1-1.el7.noarch (epel)
           Requires: python-zope-interface
Error: Package: python-zope-sqlalchemy-0.7.2-1.el7.noarch (epel)
           Requires: python-zope-interface
Error: Package: python-kajiki-0.3.5-1.el7.noarch (epel)
           Requires: babel
Error: Package: python-genshi-0.7-3.el7.x86_64 (epel)
           Requires: python-babel >= 0.8
Error: Package: python-repoze-who-2.1-1.el7.noarch (epel)
           Requires: python-zope-interface
Error: Package: TurboGears2-2.3.0-0.2.git6da6959.el7.noarch (epel)
           Requires: python-jinja2
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Do you have any suggestion for this one?
Thanks.

------------------------------
Best Regards
Jacky

From: [e-mail] [mailto:[e-mail]] On Behalf Of Christopher Meng
Sent: Friday, 14 March 2014 2:26 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch

I would suggest you using pip to install these packages.

First these packages in repo are old and may not match your need.

https://bugzilla.redhat.com/show_bug.cgi?id=852998

Second these packages are used for Fedora infrastructure apps, and since the technology is moving forwardly, these packages may be retired.

Thanks.
[wargaming.net]
EgzO3mXGcK

This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg

[Christopher Meng]

On Fri, Mar 14, 2014 at 11:40 AM, Zhiwei Zhu  wrote:
> Hi Christopher,
>
> Thanks for your quick response. I understand the situation and Turbogears-1.1.3 may be old.
>
> I also tried Turbogears2 (which is TurboGears2-2.3.0) and got these errors:
>
> Error: Package: python-transaction-1.4.1-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: python-zope-sqlalchemy-0.7.2-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: python-kajiki-0.3.5-1.el7.noarch (epel)
>        Requires: babel
>
> Error: Package: python-genshi-0.7-3.el7.x86_64 (epel)
>        Requires: python-babel >= 0.8
>
> Error: Package: python-repoze-who-2.1-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: TurboGears2-2.3.0-0.2.git6da6959.el7.noarch (epel)
>        Requires: python-jinja2
>
> You could try using --skip-broken to work around the problem
>
> You could try running: rpm -Va --nofiles --nodigest
>
> Do you have any suggestion for this one?
>
> Thanks.

For all packages which can be found from pypi, I'd recommend using pip
to install them.

I don't know the plan, maybe the missing packages will never get into EPEL7.

[Zhiwei Zhu]

Hi Christopher,

Got it. Thanks. Have a good day:)

------------------------------
Best Regards
Jacky

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Christopher Meng
Sent: Friday, 14 March 2014 2:47 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch

On Fri, Mar 14, 2014 at 11:40 AM, Zhiwei Zhu  wrote:
> Hi Christopher,
>
> Thanks for your quick response. I understand the situation and Turbogears-1.1.3 may be old.
>
> I also tried Turbogears2 (which is TurboGears2-2.3.0) and got these errors:
>
> Error: Package: python-transaction-1.4.1-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: python-zope-sqlalchemy-0.7.2-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: python-kajiki-0.3.5-1.el7.noarch (epel)
>        Requires: babel
>
> Error: Package: python-genshi-0.7-3.el7.x86_64 (epel)
>        Requires: python-babel >= 0.8
>
> Error: Package: python-repoze-who-2.1-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: TurboGears2-2.3.0-0.2.git6da6959.el7.noarch (epel)
>        Requires: python-jinja2
>
> You could try using --skip-broken to work around the problem
>
> You could try running: rpm -Va --nofiles --nodigest
>
> Do you have any suggestion for this one?
>
> Thanks.

For all packages which can be found from pypi, I'd recommend using pip to install them.

I don't know the plan, maybe the missing packages will never get into EPEL7.
_______________________________________________
epel-devel mailing list
[e-mail]
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
[wargaming.net]
EgzO3mXGcK
This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg

[Paul DeAudney]

When you use PIP make sure you also virtual-env for the application python
libraries and environment. This will allow you to install the PIP packages
into a isolated python environment for just that application and not impact
the 'system' python environment.

http://stackoverflow.com/questions/5844869/comprehensive-beginners-virtualen...

Alternatively you could package the python libraries to RPM yourself if you
have to deploy the same setup to many systems (at that point I assume you
would be using a tool like chef or puppet, so hand building RPMs might be
quicker than rolling out a virtual-env to all your servers).

On Thu, Mar 13, 2014 at 8:49 PM, Zhiwei Zhu  wrote:
> Hi Christopher,
>
> Got it. Thanks. Have a good day:)
>
> Best Regards
> Jacky
>
> -----Original Message-----
> From: [e-mail] [mailto:
> [e-mail]] On Behalf Of Christopher Meng
> Sent: Friday, 14 March 2014 2:47 PM
> To: EPEL Development List
> Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch
>
> On Fri, Mar 14, 2014 at 11:40 AM, Zhiwei Zhu  wrote:
> > Hi Christopher,
> >
> > Thanks for your quick response. I understand the situation and
>
> Turbogears-1.1.3 may be old.
> > I also tried Turbogears2 (which is TurboGears2-2.3.0) and got these
>
> errors:
> > Error: Package: python-transaction-1.4.1-1.el7.noarch (epel)
> >        Requires: python-zope-interface
> >
> > Error: Package: python-zope-sqlalchemy-0.7.2-1.el7.noarch (epel)
> >        Requires: python-zope-interface
> >
> > Error: Package: python-kajiki-0.3.5-1.el7.noarch (epel)
> >        Requires: babel
> >
> > Error: Package: python-genshi-0.7-3.el7.x86_64 (epel)
> >        Requires: python-babel >= 0.8
> >
> > Error: Package: python-repoze-who-2.1-1.el7.noarch (epel)
> >        Requires: python-zope-interface
> >
> > Error: Package: TurboGears2-2.3.0-0.2.git6da6959.el7.noarch (epel)
> >        Requires: python-jinja2
> >
> > You could try using --skip-broken to work around the problem
> >
> > You could try running: rpm -Va --nofiles --nodigest
> >
> > Do you have any suggestion for this one?
> >
> > Thanks.
>
> For all packages which can be found from pypi, I'd recommend using pip to
> install them.
>
> I don't know the plan, maybe the missing packages will never get into
> EPEL7.
> _______________________________________________
> epel-devel mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/epel-devel
> [wargaming.net]
> EgzO3mXGcK
> This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or
> PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient
> and, therefore, may not be retransmitted to any party outside of the
> recipient's organization without the prior written consent of the sender.
> If you have received this e-mail in error please notify the sender
> immediately by telephone or reply e-mail and destroy the original message
> without making a copy. Wargaming.net accepts no liability for any losses or
> damages resulting from infected e-mail transmissions and viruses in e-mail
> attachment. kgzO3mXGcg
> _______________________________________________
> epel-devel mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/epel-devel

[Zhiwei Zhu]

Hi Paul,

Thanks for sharing this. It seems there is no straightforward solution for this kind of issue.

It seems there is some kind of intersection between epel and pip. Take TurboGears for example. epel7 does provide the rpm of TurboGears but doesn't guarantee it could be installed (epel5 didn't have this issue, not sure for epel6). This is also applicable to TurboGears2 on epel7 which is supposed to be not old. Then I am not sure why we have TurboGears on epel7? I thought all the rpms on epel were supposed to be able to be installed, but I might be wrong.

I have just installed TurboGears using pip (current TurboGears on pip is version 1.5.x). Probably  we consider migrate our project to TurboGears 1.5.x or even TurboGears2.

------------------------------
Best Regards
Jacky

From: [e-mail] [mailto:[e-mail]] On Behalf Of Paul De Audney
Sent: Friday, 14 March 2014 3:59 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch

When you use PIP make sure you also virtual-env for the application python libraries and environment. This will allow you to install the PIP packages into a isolated python environment for just that application and not impact the 'system' python environment.

http://stackoverflow.com/questions/5844869/comprehensive-beginners-virtualen...
Alternatively you could package the python libraries to RPM yourself if you have to deploy the same setup to many systems (at that point I assume you would be using a tool like chef or puppet, so hand building RPMs might be quicker than rolling out a virtual-env to all your servers).

On Thu, Mar 13, 2014 at 8:49 PM, Zhiwei Zhu <[e-mail]> wrote:
Hi Christopher,

Got it. Thanks. Have a good day:)

------------------------------
Best Regards
Jacky

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Christopher Meng
Sent: Friday, 14 March 2014 2:47 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch
On Fri, Mar 14, 2014 at 11:40 AM, Zhiwei Zhu <[e-mail]> wrote:
> Hi Christopher,
>
> Thanks for your quick response. I understand the situation and Turbogears-1.1.3 may be old.
>
> I also tried Turbogears2 (which is TurboGears2-2.3.0) and got these errors:
>
> Error: Package: python-transaction-1.4.1-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: python-zope-sqlalchemy-0.7.2-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: python-kajiki-0.3.5-1.el7.noarch (epel)
>        Requires: babel
>
> Error: Package: python-genshi-0.7-3.el7.x86_64 (epel)
>        Requires: python-babel >= 0.8
>
> Error: Package: python-repoze-who-2.1-1.el7.noarch (epel)
>        Requires: python-zope-interface
>
> Error: Package: TurboGears2-2.3.0-0.2.git6da6959.el7.noarch (epel)
>        Requires: python-jinja2
>
> You could try using --skip-broken to work around the problem
>
> You could try running: rpm -Va --nofiles --nodigest
>
> Do you have any suggestion for this one?
>
> Thanks.

For all packages which can be found from pypi, I'd recommend using pip to install them.

I don't know the plan, maybe the missing packages will never get into EPEL7.
_______________________________________________
epel-devel mailing list
[e-mail]
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
[wargaming.nethttp://wargaming.net]
EgzO3mXGcK
This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg
_______________________________________________
epel-devel mailing list
[e-mail]
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

[Mathieu Bridon]

On Fri, 2014-03-14 at 05:55 +0000, Zhiwei Zhu wrote:
> It seems there is some kind of intersection between epel and pip. Take
> TurboGears for example. epel7 does provide the rpm of TurboGears but
> doesn’t guarantee it could be installed

I'm pretty sure repoclosure issues are considered bugs.

Most likely, you are seeing missing deps because EL 7 is not out yet,
and as such most stuff hasn't been built yet in EPEL properly.
> I thought all the rpms on epel were supposed to be able to be
> installed, but I might be wrong.

There is no point in providing an RPM which can't be installed, so it
can only be a bug, which can be resolved by either removing the
uninstallable rpm or building the missing dependencies.

Please, do report the bug.

[Toshio Kuratomi]

On Mar 13, 2014 10:57 PM, "Zhiwei Zhu"  wrote:
> Hi Paul,
>
> Thanks for sharing this. It seems there is no straightforward solution

for this kind of issue.
> It seems there is some kind of intersection between epel and pip. Take

TurboGears for example. epel7 does provide the rpm of TurboGears but
doesn’t guarantee it could be installed (epel5 didn’t have this issue, not
sure for epel6). This is also applicable to TurboGears2 on epel7 which is
supposed to be not old. Then I am not sure why we have TurboGears on epel7?
I thought all the rpms on epel were supposed to be able to be installed,
but I might be wrong.
> I have just installed TurboGears using pip (current TurboGears on pip is

version 1.5.x). Probably  we consider migrate our project to TurboGears
1.5.x or even TurboGears2.

I maintain tg1 (the turbogears package) in epel6.  I'm very interested in
not maintaining it for epel 7.  It's currently Been branched to the beta
epel 7 repo because it's a dependency of python-fedora which is needed to
get fedpkg working on epel 7.  Before epel 7 comes out of beta I need to
figure out with the rest of the fedora infrastructure team what to do about
that.  One option is that we'd drop the tg1 portions of python-fedora in
our epel 7 package and remove tg1.  If we think we can migrate or code away
from tg1 in a timely manner this is likely what I'll push for.

Someone else can, of course, pick up maintenance of the tg1 stack of they
need it.

-Toshio

[Zhiwei Zhu]

Hi Mathieu, Toshio,

I am really glad of receiving your responses.
I am clear about the situation now, though the final decision on tg1 hasn’t been made.

Tricky thing for us is that we may need to support both el5 and el7 (yeah, not el6 and el7), while the tg1 on epel5 is 1.0.9.
We have to consider carefully before making any decision.

Do you have any idea about tg2 on epel7? Because currently the dependency chain of it on epel7 is broken as well.

------------------------------
Best Regards
Jacky

From: [e-mail] [mailto:[e-mail]] On Behalf Of Toshio Kuratomi
Sent: Friday, 14 March 2014 5:16 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch

On Mar 13, 2014 10:57 PM, "Zhiwei Zhu" <[e-mail]> wrote:
> Hi Paul,
>
> Thanks for sharing this. It seems there is no straightforward solution for this kind of issue.
>
> It seems there is some kind of intersection between epel and pip. Take TurboGears for example. epel7 does provide the rpm of TurboGears but doesn’t guarantee it could be installed (epel5 didn’t have this issue, not sure for epel6). This is also applicable to TurboGears2 on epel7 which is supposed to be not old. Then I am not sure why we have TurboGears on epel7? I thought all the rpms on epel were supposed to be able to be installed, but I might be wrong.
>
> I have just installed TurboGears using pip (current TurboGears on pip is version 1.5.x). Probably  we consider migrate our project to TurboGears 1.5.x or even TurboGears2.

I maintain tg1 (the turbogears package) in epel6.  I'm very interested in not maintaining it for epel 7.  It's currently Been branched to the beta epel 7 repo because it's a dependency of python-fedora which is needed to get fedpkg working on epel 7.  Before epel 7 comes out of beta I need to figure out with the rest of the fedora infrastructure team what to do about that.  One option is that we'd drop the tg1 portions of python-fedora in our epel 7 package and remove tg1.  If we think we can migrate or code away from tg1 in a timely manner this is likely what I'll push for.

Someone else can, of course, pick up maintenance of the tg1 stack of they need it.

-Toshio

[wargaming.net]
EgzO3mXGcK

This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg

[Zhiwei Zhu]

Hi All,

Just an update for this thread. I apologize for this false alarm.
It turns out that the epel is fine and there is no dependency break for the TurboGears-1.1.3. The problem is only my environment.

I had problems of installing TurboGears-1.1.3 on my RHEL7 was just because the RHEL7 I was using was not registered to RedHat.
The packages required by TurboGears-1.1.3 but not available on EPEL7 are actually available on RedHat network.

I just switched my testing server to a registered RHEL7 and everything goes well.

Now I do hope that this TurboGears-1.1.3 will be maintained on epel even after Beta☺

------------------------------
Best Regards
Jacky

From: [e-mail] [mailto:[e-mail]] On Behalf Of Zhiwei Zhu
Sent: Friday, 14 March 2014 5:49 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch

Hi Mathieu, Toshio,

I am really glad of receiving your responses.
I am clear about the situation now, though the final decision on tg1 hasn’t been made.

Tricky thing for us is that we may need to support both el5 and el7 (yeah, not el6 and el7), while the tg1 on epel5 is 1.0.9.
We have to consider carefully before making any decision.

Do you have any idea about tg2 on epel7? Because currently the dependency chain of it on epel7 is broken as well.

------------------------------
Best Regards
Jacky

From: [e-mail] [mailto:[e-mail]] On Behalf Of Toshio Kuratomi
Sent: Friday, 14 March 2014 5:16 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch

On Mar 13, 2014 10:57 PM, "Zhiwei Zhu" <[e-mail]> wrote:
> Hi Paul,
>
> Thanks for sharing this. It seems there is no straightforward solution for this kind of issue.
>
> It seems there is some kind of intersection between epel and pip. Take TurboGears for example. epel7 does provide the rpm of TurboGears but doesn’t guarantee it could be installed (epel5 didn’t have this issue, not sure for epel6). This is also applicable to TurboGears2 on epel7 which is supposed to be not old. Then I am not sure why we have TurboGears on epel7? I thought all the rpms on epel were supposed to be able to be installed, but I might be wrong.
>
> I have just installed TurboGears using pip (current TurboGears on pip is version 1.5.x). Probably  we consider migrate our project to TurboGears 1.5.x or even TurboGears2.

I maintain tg1 (the turbogears package) in epel6.  I'm very interested in not maintaining it for epel 7.  It's currently Been branched to the beta epel 7 repo because it's a dependency of python-fedora which is needed to get fedpkg working on epel 7.  Before epel 7 comes out of beta I need to figure out with the rest of the fedora infrastructure team what to do about that.  One option is that we'd drop the tg1 portions of python-fedora in our epel 7 package and remove tg1.  If we think we can migrate or code away from tg1 in a timely manner this is likely what I'll push for.

Someone else can, of course, pick up maintenance of the tg1 stack of they need it.

-Toshio
[wargaming.net]
EgzO3mXGcK

This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 14 Mar 2014 11:25:36 +0800
Christopher Meng  wrote:
> I would suggest you using pip to install these packages.
>
> First these packages in repo are old and may not match your need.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=852998
>
> Second these packages are used for Fedora infrastructure apps, and
> since the technology is moving forwardly, these packages may be
> retired.
>
> Thanks.

Christopher,

Your advice is unhelpful and inappropriate. Please do not offer such
advice in Fedora channels again.

Clearly there is a bug and it needs fixed. are the deps showing as
broken on the nightly report? if so we need to get things fixed, afaik
I had all the Deps for TurboGears sorted right at the start. If you are
using an internal snapshot and things have been removed you are on your
own to get the deps, we can't deal with it until its broken in a public
release.

Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQIcBAEBAgAGBQJTK2K5AAoJEH7ltONmPFDRcacP/2TieTvpfFrQsEM/JKAMWnb9
> bqZV8ScPgKxJZwPXPZQ8vz/ZiCtclqtZfJMKMvv4Ll+B3uL6NmkI/NvjRY4eqHX2
> /1pvKvkPiaOqzU36sbtjqBKybCHTTapf0GjDXgqzYCQrQfhAv40NmbxfTk1rVF41
> C7Kls1vepLsAy6RtboJeef2mUmsbtymAqICjRWrl1Bc59WUzqFuW648g7aOPXS6t
> Bl4IZuqZu/5ZkP14hjyoV+VZM+6EQsEQIBr9EjTYxlvZ9pFVY6Sh5Bgb3rzrfWvZ
> WCAHKwaSmCphFwq8F0fAkp9Az22tcvERuGFyc7v3wchrq7Z4SnDLFAs56dIa4XzJ
> lM8BgF5cEQeX1Iim7lvRq58d4PfJpkuQDP1q/pdIO5mmVrNZ0bWPwhLitb4MmRAG
> R1bIGpPmzAq/jRTmkAzyodLw2S8WJaW1HoztXBY0ImH2MPGXJ5QcFYmPDevTgQOV
> QvkdeeQ/fcgk+8W0CPHuft2XYaqyd2iz0WzJUCK1GkiCult/G+9ilsVqCP6Y5KgJ
> f+yS/abNyytLy9+9UrTR61wv3xj5TZWr24dBJ7RF2O5r2pluWhWFFF4wsh9ePY4S
> vvThkbm5rEQ2k7HA+1jpqrwrT+Gis7Mv2eXjKHnBHV/HkKOKwbI7CVZS+sVA8Llx
> rebKB1muNVsgoVjc7bFd
> =VAYz
> -----END PGP SIGNATURE-----