DebConf23 registration and CfP are open

2023-06-12 Thread Daniel Lange 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

For DebConf23, we're pleased to announce opening of registration and call for 
proposal.

Registration and the Call for Proposals for DebConf23 are now open. The 24th 
edition of the Debian annual conference will be held from *September 10th to 
September 17th, 2023, in Infopark, Kochi, India.* The main conference will be 
preceded by DebCamp, which will take place from September 3rd to September 9th, 
2023.

The registration form can be accessed by creating an account on the [DebConf23 
website](https://debconf23.debconf.org/) and clicking on "register" in the 
profile section. The number of attendees is capped at 300 this year. All registrations 
will be reviewed by bursary team, and completing the registration form does not guarantee 
attendance.

As always, basic registration for DebConf is free of charge for attendees. If 
you are attending the conference in a professional capacity or as a 
representative of your company, we kindly ask that you consider registering in 
one of our paid categories to help cover the costs of organizing the conference 
and to support subsidizing other community members.

The last day to register with guaranteed swag is 5th August.

We also encourage eligible individuals to apply for a diversity bursary. 
Travel, food, and accommodation bursaries are available. More details can be 
found on the [bursary info 
page](https://debconf23.debconf.org/about/bursaries/).

The last day to apply for a bursary is 1st July. Applicants should receive 
feedback on their bursary application by 16th July.

The call for proposals for talks, discussions and other activities is also open. To 
submit a proposal you need to create an account on the website, and then use the 
"Submit Talk" button in the profile section. The last day to submit and have 
your proposal be considered for the main conference schedule, with video coverage 
guaranteed, is 13th August.

DebConf23 is also accepting sponsors. Interested companies and organizations 
may contact the DebConf team through spons...@debconf.org or visit the 
[DebConf23 website](https://debconf23.debconf.org/sponsors/become-a-sponsor/).

Cheers!
Sahil
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENXULj7bvlf8WuOvAZk8SOKqPE4oFAmSHcAwACgkQZk8SOKqP
E4q0VQ/+Py+iTo+PaRdcT9XTSST77HT/pc5HOxoSJIztUyxN0dH87mFtqQS3wdC6
aYHPUIEcWxDdnh7Qy2bMUYgiG1NE4qEouCafpRpD1kSd33L9FRlENyAJVKUedMUP
g83JQIq12f5xa4du7iH0zn7ubDX++7diUooib1lfHSlJdMQfcrgHijy04anIJQqW
x09ExS7bwFKk6CAbCz/7XLTsVFKl7iF7hnRqH5wIb+ri6iPcBLuaDBxX9dDFONHs
7sqnWJYub1+7GDkU91sFeeFflKOGVgfJ4H0nGWQrfdRC9rxWuh3mkjkpnI7sqnTQ
iT04qs/UiRKctr6RBmHaSAmy05LjvlNQ2VXCaibMCywt168Y9vH/YdkhI4pVJYWw
VklgkrUSAUbBQpRZ9XkmRQbIT1gOnhRNrrzefccKlyA0fCsAynY6OW+fmddURrOK
YXwX7NHgmEcLl/5wdnbQyvgaJj7OTrrxtrI8lhxQ71twAOij8ywjvwFSWBh9+iyR
SJj7IGYw8x9Hv2XDYU6M6fMtuNgMGYl+VRs4aXolnrpN6HL7AeOh4v4VvSBLASms
9S6HhfJZXhTsjOPYD3e92LlbSbfvpUGZq1O6ByJHybj1rp4Qt9AV183vXnoQxffd
4LMYuFKKlVW49UaX7zGuFXvqbpxt425H2aFlBFJed6sCuVi/PoY=
=WAWg
-END PGP SIGNATURE-

Reminder: DebConf20 registration, bursary status, Covid-19 survey results

2020-06-01 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

just a quick reminder:

The local team and the DebConf committee (DCC) need to decide next
Monday whether we keep DebConf20 as a physical conference for those
that will likely be able (and willing) to travel in August.

Please help us by registering if you want to attend at:

https://debconf20.debconf.org/register

by end of the week.

The bursary requests are closed for the moment as that deadline has
passed yesterday. So please register now if you do not need travel
sponsorship. Don't bother about food and accommodation at the moment.
For safety reasons alone, that would likely (have to) be provided.

The results of the survey we conducted in parallel are available at:

https://salsa.debian.org/debconf-team/public/data/dc20/-/tree/master/survey

24% of all people that wanted to join DebConf20 before the Corona
epidemic would still do so today and also recommend the in-person
conference. 59% prefer an online-only conference and 18% recommend to
cancel DebConf20.
79% of all respondents would be willing to join an online-only DebConf.
Please check the Salsa link above for more detailed results and analysis.
On a related note: Videos from the Online Mini-DC that took place last
weekend are available at:
https://ftp.acc.umu.se/pub/debian-meetings/2020/MiniDebConfOnline/

If you have any questions, feel free to drop by #debconf-team on IRC
and chat with us.

Kind regards,
Daniel
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENXULj7bvlf8WuOvAZk8SOKqPE4oFAl7VEfkACgkQZk8SOKqP
E4rjEw/+NmboQ+JxHIKRa7wQhKf8EkR6B+aCjv7rVaj430Yxzo5fcL0Ak1DqeXnk
xnCCv47HSY1PjgQA5cvkg1dUzatl1A4YMxTPmZtYQnnBrBbx6vEqP7UWIzwVpz6U
7Pc2MB8rN3Ljuo7+48x0ASxpyj/1Y5KzZjYOhrCO1GG2WRnFDU7eEtKD5FBaIN/1
owdwDPRQMCCUZ8gJAPVaAn6HSMsqKlJ6cnS4Xo4eogE4HSHIB6EQOrASnQj4HY2j
OOv/uPAwt0NfJy3U87aS3L8qe0crlehycXzVpqH2TZfNcFVgdR6txtMun+IvXvrf
CAkoEWqZdkvLPQlRITqNMKk247r/YW28msWGWg66OILu5vVgQU/Ctps/tw0JnUuh
AsUvbCnryu/P3LrdxrSzrNtZED5LsXBz+bDxQWRV+lSirRB3/iXSyHtb6wRE2neH
D9gJct9lnDXH0V3fOiZxN0PB43b8skHAAvhOg4CXmAAOniEruMw2gqQEC4/aPnBm
BH0N/pFqDpz89x5Ri3YmNjo9vgKhJMPTBpLUb/UyN1CGDMG6jmumz7mb9Hvv6VFl
5Q7uVyhNWOkd2n6v+1Jnb2XstEm6AwnIvBUxshflYmlsOj53GPuCzhyuk5hRFzfh
M2lB5STRW+vK85fQfSMwU88B9QpCZL00oblYRkLu9gaSMY04als=
=fHTP
-END PGP SIGNATURE-

Re: DebConf20 registration is now open (with caveats)

2020-05-23 Thread Daniel Lange 

Hi Enrico,

Am 23.05.20 um 18:41 schrieb Enrico Zini:

I'm perplexed by the deadline for the bursaries being earlier than the
date in which there'll be a decision about what the format of the
conference will be like.


That's because we need some time to evaluate bursary requests and if we 
give people approval too late, they will be unable to apply for Visa and 
get reasonable flights. So we'd exempt people that need a Visa for 
Israel inadvertently.


The bursary decisions are scheduled to be announced as soon as possible 
after an eventual "go ahead" decision for the physical conference and 
the availability of an approved conference budget.



The call for registration implies that one would be registering to a
similar format of conference as the previous years.


If you don't want to attend a physical conference, that is the right 
thing to do. We are currently only collecting registrations from people 
that are in the region or want to fly to Israel and estimate themselves 
that they will be likely be allowed to do so in August.



Can you however confirm that if on the 8th of June the format of the
conference will change into something that one would instead feel
motivated to attend, and such format would still requires expenses for
which one could use a bursary, then the bursaries deadline will be
extended?


An online format will be free of charge for people joining.

If a community member needs specific hardware to attend and cannot 
afford it themselves, there is the normal DPL reimbursement process 
available. This would apply to the prior Online Mini-DC (End of May) 
already before DebConf20 (End of August).


Kind regards,
Daniel

Re: @debian.org mail

2019-06-05 Thread Daniel Lange 

Am 04.06.19 um 17:51 schrieb Graham Inggs:

I would certainly make use of SMTP for sending @debian.org email. I 
can't see the advantage of IMAP over forwarding though, would you 
explain how you see it working, or who would use it? 


I wouldn't need IMAP either. But for those who are stuck with gmail, 
hotmail, gmx and the like Debian hosted IMAP servers would mean they 
also get a chance to _receive_ all Debian email. Email from @debian.org 
to these email domains is currently rejected outright (IPv6 & gmail, 
Tencent brands) or often ends up in /Spam (IPv4 & gmail, many other 
"free" email providers). We can assume with an updated SMTP setup that 
situation will improve significantly but probably not to a 100%. We run 
mailing lists without sender address rewrite and ARC isn't there yet. 
But if we run IMAP, too, we can simply ensure delivery today (and in the 
future).


So having a submission host (SMTP) and a matching SPF policy solves the 
sending side of the problem, Debian-hosted secure IMAP the receiving side.


Supporting ARC* will eventually help keep mailing lists and bugs.d.o 
functional (for non-Debian-hosted email aka our users) when "the big 
players" ratchet up their anti-spam measures further. But that's, by my 
very subjective personal estimate, another few years down the line.


I'd probably add Debian hosted webmail, too. It's trivial to add and 
some people seem to need it as they spend their day jobs behind very 
restrictive firewalls.


* see https://en.wikipedia.org/wiki/Authenticated_Received_Chain for an 
explanation. That also explains quite well why plain DKIM / DMARC is 
hard to implement without serious side-effects.

Re: @debian.org mail

2019-06-03 Thread Daniel Lange 

Am 03.06.19 um 22:32 schrieb Marco d'Itri:


On Jun 03, Daniel Lange  wrote:

> > -all would stop some forged emails, but we do not have forged email
> > issues.
> We do. 4% of this year's spam in my spam traps have originated as fake
> @debian.org. Unfortunately we even nicely relay them as we can't tell
This is not a meaningful figure unless you also figure out how much of
that spam could have been detected.

It is a data point to prove your "we do not have forged email issues" wrong.
How much of that spam we can prevent depends on which improvements we 
implement.


Cord kindly produced a few more data points tonight:

We have 39487 @gmail.com users subscribed to lists.d.o mailing lists.
9658 emails from lists.d.o have been bounced / denied by gmail.com in 
the last week.

Re: @debian.org mail

2019-06-03 Thread Daniel Lange 

Am 03.06.19 um 18:09 schrieb Marco d'Itri:


-all would stop some forged emails, but we do not have forged email
issues.
We do. 4% of this year's spam in my spam traps have originated as fake 
@debian.org. Unfortunately we even nicely relay them as we can't tell 
legitimate and fake Debian email apart ourselves.


My favorite ones are fake me sending real me emails with forged 
Microsoft Outlook Express 6.00.2900.5338 headers. 'Cause that's 
definitely my MUA of choice. I've also been chosen for the Google 
foundation trustee board which - allegedly - gets me a personal grant to 
spend however I wish. I'm still waiting for Google's check to arrive.


Back to topic:

Mailly's sender score has ditched to 65/100 during the last spam wave in 
early May and it took two weeks to recover to sane ratings.


We also fan out spam like 
 
(msgid-search works but it's just a boring example) which - funnily - 
gets us spam points at Google (cause we amplify that to ~ a hundred 
@gmail.com recipients).


As we are white-listed at dnswl.org and a few other places such fan out

1) is very useful for spammers and
2) makes our IP reputation suffer as in the May case cited above

As I said earlier, we're not the best netizens we can be and we should 
not facilitate for others spamming in our name.


I know you don't like SPF mx -all but that is what stops the above and 
makes @debian.org mail delivery reliable again. As we relay mailing 
lists via lists.d.o (bendel) we can easily have that continue rewriting 
senders without issues. It can have a separate SPF.


There are other options, too, incl. the one you listed. I'd go for ARC 
if we want to go beyond SPF. But that would be a 20 year leap in email 
tech. I like iterations, i.e. aim for some less ambitious goals first.
It's DSA's call what they prefer. I don't care which solution is chosen 
as long as we get one.
O.k., I'd prefer us to not sign up for Google hosted email or Exchange 
online. I think that part is even safe to assume rough consensus on.

Re: @debian.org mail

2019-06-03 Thread Daniel Lange 

Hi Sam,

Am 03.06.19 um 13:29 schrieb Sam Hartman:

1) You're asking all DDs to use this infrastructure you set up.


Currently everybody routes inbound mail via two Debian servers (as they 
are the only MXs for debian.org).


Everybody who needs to make sure they can reach @gmail.com / GApps users 
/ Microsoft hosted Exchange etc. need to send via these, too, cf. my 
initial email.


People vote with their feet. We're not really overrun by new 
contributors. We shouldn't afford the arrogance of "it is your problem 
if my email doesn't reach your inbox". Esp. if we can do better.


That said, I don't care when DDs use their private domains for Debian 
stuff. I'd be all for continuing them to do so.


For things like fundraising officially looking email addresses are 
important. That's why I care to keep these functional. More DDs funded 
to travel to DebConf is a more happy me. I'm also sure many @debian.org 
-> random upstream messages are never received. Because random upstream 
is a Google / Microsoft / Yahoo user or runs an email server with a 
strict anti-spam policy. We just had that case with the cfp@ email of 
our Hamburg Mini-DebConf rejecting @debian.org email because of "forged 
recipients" and bad IP reputation scores. QQ (Tencent) refused emails 
from Salsa. This is the biggest email hoster in China. I'd like more 
Chinese to be able to participate in Debian. I have many such examples.


Hence I'd like us to offer email services to project members. That's an 
offer. Not a requirement. If DDs use the Debian infra or continue using 
their current setup, all fine for me.
Yes, a proper SPF record may make things more difficult for people that 
run their own. But I - for example - run my own and route via Debian MX 
(just the Debian mail of course). So it can be done. I just wish not 
every DD had to, if they wouldn't want to. And possibly end up using 
GMail and make Jonathan and many Free as in Freedom advocates unhappy.



2) I'm not really sure I want the debian machines to get a copy of all
mail I send from my debian.org address.


In case anybody replies to your email, these machines get the gist of 
your communication anyways. And you send via AWS (Amazon). I personally 
trust DSA more.


To me emails are postcards. Everybody along the transport chain may 
enjoy the pictures. Of course I can sign or encrypt if I want the 
pictures to stay genuine or the back side text private.


There is currently a trend in the FLOSS ecosystem to try migrating off 
irc, email and email lists towards Discourse, Gitlab, Mattermost and 
other web based tools. I'm not a fan of that at all (siloing). But one 
of the reasons is lowering the technical entry barrier to participation. 
We should give at least the project members everything they need as 
readily available as possible. And email is really basic.


Kind regards,
Daniel

Re: @debian.org mail

2019-06-03 Thread Daniel Lange 

We (debian/DSA) do not provide email hosting. We provide email
forwarding.


DSA should re-evaluate that.

We run into more and more problems sending from @debian.org email 
addresses as the three big players in email ratchet up their anti-spam 
measures.


They are hosting a huge share of our users' email and the same for 
prospective contributors:



The default reply for missing wafer confirmation emails (the software 
running debconf19.debconf.org) and missing salsa password reset emails 
is "check your Spam folder". Debian.org doesn't have a SPF record so 
mail submitted from such Debian machines is a bit in a limbo.


We have more people registered for DebConf ("the Debian Developers' 
conference") with @gmail.com than @debian.org addresses.


Mail submitted from DD's private IPs frequently gets flagged as spam 
regardless of content by all three big players and - if submitted via 
IPv6 - refused directly by Google. Microsoft and Yahoo still run their 
MXs IPv4 only. But we can expect a similar policy once they add IPv6 
SMTPs at scale. And they won't warn us up-front.
The missing SPF record mentioned above means there is a lot of spam 
circulating with @debian.org fake senders and obviously our open 
submission policy on many mailing-lists and @debian.org technical 
addresses also fan out quite some spam. So we're not the best netizens 
we could be.


To do better, we should really offer SMTP submission/IMAP services for 
@debian.org as soon as possible and - after a grace period - publish a 
mx -all SPF record.


Google has added mailly and muffat to their internal 
has-no-proper-SPF-policy-whitelist (thank you!). This will obviously 
increase the problems for people not sending via Debian machines down 
the road.
Which is why a few people - including me - now route outbound via these 
Debian MX machines. That's a work-around for the technically inclined 
but won't really scale.


People have tried mending the gap by offering accounts on their personal 
infrastructure to fellow developers (and thanks for that Tollef and others).


We like people to use their @debian.org or @debconf.org email address 
when reaching out to sponsors and suppliers as this adds (perceived) 
credibility and (true) visibility. So we should make it easy for people 
to use those email addresses.


Just maintaining the status-quo of email-forwarding only seems past its 
useful life time.


Kind regards,
Daniel

P.S.: I have offered helping to run email services to DSA in the past.
I don't only complain. But DSA has the issue of them having to run 
committed infrastructure in the end. So if - for example - the Salsa 
team were not wanting to run salsa.debian.org anymore, DSA would end up 
having to add this to their work load. This is why DSA need to 
prioritize email regardless of who will set it up and run it initially.

Accepted cronic 3-2 (source all) into unstable

2018-05-06 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 May 2018 13:10:32 +0200
Source: cronic
Binary: cronic
Architecture: source all
Version: 3-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Lange <dla...@debian.org>
Changed-By: Daniel Lange <dla...@debian.org>
Description:
 cronic - Bash script for wrapping cron jobs to prevent excess email sendin
Changes:
 cronic (3-2) unstable; urgency=low
 .
   * Update policy to 4.1.4 (change vcs URLs, change URLs to https)
   * Update maintainer email
   * Update d/copyright and man page
Checksums-Sha1:
 fc231e1d7ecc46488b60bb44923ab4dab73f685b 1774 cronic_3-2.dsc
 49fb115a0450f56e76a9caf4cb530d7f298aa5be 5036 cronic_3-2.debian.tar.xz
 9f0b4ee504e467d67086558ea947d3f68efa22f7 6366 cronic_3-2_all.deb
 7088dbaf662a86b639f3abe56c0cab2679b22a7d 6170 cronic_3-2_amd64.buildinfo
Checksums-Sha256:
 aea537fe77cbf8eec21d1c3c13504a5254e650844f9a2cd01ef578a90bdbad52 1774 
cronic_3-2.dsc
 4eb7dca6c980749339a01e1ba5657f4a63db7ad56cd6f739be201c12a9c5b2ae 5036 
cronic_3-2.debian.tar.xz
 119ae92e144de96a785f12505f31e0a6762e40f011825be4732efc1052d6fc97 6366 
cronic_3-2_all.deb
 a55ad09b051fa1b5fa469e1786b138797161618da41cd80b6e89905550be8023 6170 
cronic_3-2_amd64.buildinfo
Files:
 a3f2379e5b84a5ecc4e40a45bd98ed01 1774 admin optional cronic_3-2.dsc
 a774e4278f49f1c5052bd3bb7bf44cbc 5036 admin optional cronic_3-2.debian.tar.xz
 5ccffb8c9488bd2f6e54e0004f1368e1 6366 admin optional cronic_3-2_all.deb
 e3d93c4198be4d5a86ad88817e1f5032 6170 admin optional cronic_3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEENXULj7bvlf8WuOvAZk8SOKqPE4oFAlrvABsSHGRsYW5nZUBk
ZWJpYW4ub3JnAAoJEGZPEjiqjxOK8VYP/3Z57Nb69Q8yqqGsK07PNR3DnR5bwXHg
Tq1b+v66XPB/s1vEmfkEonueo9hT9PEq+0dztgFeR8mQB5PN2p7OaiIZEv/gKV7i
f1Dk+EiUF/aOfKgAEZ85Jx2Bd/f7mVP624RpA2NdYgwUrHSvMDfO2uPPv7AzEgPr
zmGTXSHZSPy6gTQczORlRJlh4NlMTy6777bO8CPcNI2a6ZngtP18zlfABi0HIj5+
/+hNz64w35HIltCXXalQmfn9hIPay5bLn2rsroFigOFGdYff6rlP/bYU8CDp9aFX
KqjbmFTy8AESL8rm080nBUsPkz8OmfDmc3YIxGN321GitbTa2PNWV9ORB6DfgjEx
sDgDxBCwnMBitpMH5j48O6DUXZPceLejeMOVJv9RvsoqvqSfHv0XECS1WbEdiB8M
IC+P2vIkcR8Uf9QuIy2US+NNOsG67fIyOOsj7at2RWwJl0x8pVQouBsA8rEgxykg
7ttXZbmPAuxrkf/5XCOGtQRGzfC4tbq7jD020PZLxvXRsPZ8/PIoKqoDyqiUtv7M
EKpb0gIDxyk6y43CwhUMvqBHUfb3vRPk4I4JKLM2YpitUms62bcVmhAPSrag0g37
gsFY/1PVwp/juoz9mgCrgr5274O8zzGCJSUqxSJgtl44LHShGiKBKLek4Hrs/b3y
mjgac8Qwg9nJ
=y2CY
-END PGP SIGNATURE-

Accepted htop 2.2.0-1 (source amd64) into unstable

2018-04-26 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Apr 2018 21:10:00 +0200
Source: htop
Binary: htop
Architecture: source amd64
Version: 2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Lange <dla...@debian.org>
Changed-By: Daniel Lange <dla...@debian.org>
Description:
 htop   - interactive processes viewer
Changes:
 htop (2.2.0-1) unstable; urgency=medium
 .
   * New upstream release 2.2.0
   * Update uscan to v4 and add gpg verification of upstream tarball
   * Drop patches that were merged upstream
   * Remove OpenVZ patch that wasn't merged upstream
 (for now, upstream issue 464)
   * Add upstream issue 780 patch
   * Fix compile issue with regenerated header files (patch)
   * Update policy to 4.1.4 (no changes required)
Checksums-Sha1:
 341d9f5dee1063a0f4f8f52e4006524c3a8b3c99 2256 htop_2.2.0-1.dsc
 cf031894ea7fa2de914ec7ddeea19492f97e555d 291651 htop_2.2.0.orig.tar.gz
 558cb102a26a04b511f197905add39fe214eb20e 819 htop_2.2.0.orig.tar.gz.asc
 6158b758177010bb1e19625f912449adc975e32f 10780 htop_2.2.0-1.debian.tar.xz
 6c0958464ca240254dff280f629144db7ada9146 259206 htop-dbgsym_2.2.0-1_amd64.deb
 e73b12cc668674318cc0fbd20d3f90ded5cbc302 6716 htop_2.2.0-1_amd64.buildinfo
 98a7949207906a276d8c97f7c6e738b2eaadd27b 91606 htop_2.2.0-1_amd64.deb
Checksums-Sha256:
 577d474b213cc6abf6bfb7b3990ea05399b0df1fb485471c5aef1ca46d5265d4 2256 
htop_2.2.0-1.dsc
 becdd93eb41c949750ef2d923d6f7f6157c0d926ebd52d2472a45507eb791d13 291651 
htop_2.2.0.orig.tar.gz
 dcd37ff7c12ad4e61525d6a5661721201817f380a278c03ba71f8cc919a93361 819 
htop_2.2.0.orig.tar.gz.asc
 a8c544cce49d9cffbde300bbb96775b6d17eb7aff5076157390b1fde069942e3 10780 
htop_2.2.0-1.debian.tar.xz
 adf4f7221781ff786906ef7029b32a3a17389cf6780a8c699c6e6545674b528b 259206 
htop-dbgsym_2.2.0-1_amd64.deb
 5dd4c1c16531734a92477d939b972b98628b752b88031b5bc274c061bf297865 6716 
htop_2.2.0-1_amd64.buildinfo
 bdf2b735631bcb2a44e1949cf003521062358774d251be09091e79e983add953 91606 
htop_2.2.0-1_amd64.deb
Files:
 68c9ba6d6cc2ba78254de280e1b2ea3e 2256 utils optional htop_2.2.0-1.dsc
 f984359c3620f81f6f7027be3f63f89b 291651 utils optional htop_2.2.0.orig.tar.gz
 84cb0d7e913323d3ba02afd70a3bcad0 819 utils optional htop_2.2.0.orig.tar.gz.asc
 fa4e16326e1ca21ae7b4c4454ff1faad 10780 utils optional 
htop_2.2.0-1.debian.tar.xz
 19cffd42500b21fa36b4465e9d63c464 259206 debug optional 
htop-dbgsym_2.2.0-1_amd64.deb
 a0254c85c4f4722d7ace573e45708592 6716 utils optional 
htop_2.2.0-1_amd64.buildinfo
 43e1a04b87d35dfd6b37a042e39d8bb2 91606 utils optional htop_2.2.0-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEENXULj7bvlf8WuOvAZk8SOKqPE4oFAlriJJ4SHGRsYW5nZUBk
ZWJpYW4ub3JnAAoJEGZPEjiqjxOKHCQP/2T9zZDxAALpfuEIhACQu71InNM+uFMW
nkmsa5z0I5NtV8Gzg2iCqbQHTJZdCcUg1/J+MTP3gVvSEFYZQTP5M9Izk17t3TmW
j0ZVLvaEaQYFvlNSaY9xhb1j5u/FQUexjICrut3ka8z++H5s31e7qlraghZ8QxRc
uBdoRnANhZldcfA4/4hwlOIOR5JiY0JmPk3yCNZAkghHZiz5k/odOl6ZdpZilTBV
kVZP3G6I8c/re6YslqjKpSG0eE+ROg28GulDIwCrih8xHAoUdILxHkIXvGXozzty
b97G5rMnEgSwU8aXPhBREM1Ry2C+v4RMUF7uo6vESW4Um/YcFd2fr3xYN9dkGj6x
oszYmpZ5aC8h6H+8saG2P+1dryUgRiihVneGwmn0n3mukBZTZY0ZrGsEvM/erhiL
PPij74EFDrapqh60+0RQfzGVMi4tA7lz5rDwPVba2M8rJ9vyYoYWCbnIqKHUvsuK
yPiCbzRIhKgseIwuzWMDsp0vqOrpOmBP/q7VJqdMzHrN6f3uTPM/wjb4mUXkZmju
Ls32iqPWJn5sG0YkhKcdkjwMJSBIbWg6sHnn0rbJyq5yTJwDZ+Y0ulDQINkBwF6Q
g3oHk99Fa/QjbqeTWGFn84GfLfBrejSrM5H2PraneVsbyMyEIzCxV9FZSv4L3jF6
yCAcsngQH+43
=AhTC
-END PGP SIGNATURE-

Re: [Debconf-team] OCF.tw for Debian Trusted Organization

2017-02-21 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am 22.02.2017 um 04:30 schrieb Ying-Chun Liu (PaulLiu):
> I'd like to propose OCF.tw to be a Trusted Organization. And OCF.tw
> also have the interests to be in. But I don't know how to start. 
> We've both read 
> https://wiki.debian.org/Teams/DPL/TrustedOrganizationCriteria 
> OCF.tw strongly meets the criteria.
Please see the "acceptance" / "criteria" links under
https://wiki.debian.org/Teams/Auditor/Organizations
for examples on how to specify that OCF.tw meets the
requirements to be a potential Debian Trusted Organization (TO).

FTR: OCF.tw is the local legal entity that the DebConf18 team from
Hsinchu, Taiwan proposes to help manage the cash flow and contracts
for the conference.

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYrTHXAAoJEGZPEjiqjxOKMSIP/iQIUg+dDoomDMOCUEcG6plM
evuSuPxae/EdYWRqnjnicYJN4BKbScqB7oiWBpWmtZeXDgK8/s/sAK9XqJ5FIEm9
ynr4K1RJfh0qaIi+Zs2PLIFdcF2S5gZx3qhEoZgTN8yz+vCnuBmui10yB5Skvyw3
+8HecxmF77hrVW349ZoHuIyjXSLpkL4j7/N7RRf1skhY60NpwjhJbmjDZjvgVkaO
zpkqBPBOhrjWh2BYnUmcl1swKANI1+q/DmfVm4jmNm1PGYhy+/71BeMJvnpvcDH+
pjSph4eLMy0zxAi6QOcUSjO0acnrcKtrZkxPUFAueU6kQTE49fTcDWTXMcy6SKYp
QAJi2/a/C3lPGJ71jwVaRSeNJqkdD4bio67ZeHlbIFfKsUaTXPbe4rCdpWPiMiL+
aMD5H35yTuxJiH/nBGRlY4Mp6ReS41aqaVLwgmyhON0yXoRXfmFzHxf2eaF568uj
2nSza+cnoRUsAgpMffZFJrxMEQe55AyKpm/0Ef1nGQNH5qc3qgUyWA1sDGqs6tfx
2YVNeNZLoVr5s5ovifdl50LT1+9h6rVezo74ZXx72DQZ6xYI4ka0TKuKnbmep2AN
nyLU30g5FFzSZDjOKAXPmq9feyYC1RNjlO7mB/jUPkhbRGtS80C6KpQh3STVS+1x
F/ZzIwN6vuK9FBfpuY2F
=hlZI
-END PGP SIGNATURE-

Accepted metar 20061030.1-2.2 (source amd64) into unstable

2016-09-26 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 22 Aug 2016 16:25:57 +0200
Source: metar
Binary: metar
Architecture: source amd64
Version: 20061030.1-2.2
Distribution: unstable
Urgency: medium
Maintainer: Kees Leune <k...@leune.org>
Changed-By: Daniel Lange <dl@usrlocal.de>
Description:
 metar  - utility to download/decode METAR reports
Closes: 833655
Changes:
 metar (20061030.1-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Import patch for new METAR URL from Kees Leune. Closes: #833655
Checksums-Sha1:
 442ab54f7ac8a7e1bef54cd6fc8919320f247c95 1673 metar_20061030.1-2.2.dsc
 4bb50acdefe624be1e8d49dc938c95a9ca28f159 3032 
metar_20061030.1-2.2.debian.tar.xz
 12fe780e78da519bbfdb04d7b814d7698a1d4896 21896 
metar-dbgsym_20061030.1-2.2_amd64.deb
 e8e3a253dd06737a9b30680bb54098d4e807003c 16620 metar_20061030.1-2.2_amd64.deb
Checksums-Sha256:
 11ac92040b42cc82c595ae567bdd4f5fc15c332d3aae1fa35521469060a4245e 1673 
metar_20061030.1-2.2.dsc
 1917c0ead9b61c2156b7549baa68c4387317a7c4b0a4cb17c1770fb4230a13ac 3032 
metar_20061030.1-2.2.debian.tar.xz
 918221f3e96e59007c644bdeb3f0bad923346381c9b134bc6a6ad4200fd3fa26 21896 
metar-dbgsym_20061030.1-2.2_amd64.deb
 ec69ed88d682f7dbd1c4a6f8820fb42ef6e12ef1e8ada9ad8f409d6212f28d52 16620 
metar_20061030.1-2.2_amd64.deb
Files:
 b7e6e68ce2b5bbb3bb0e31a754c09db9 1673 utils optional metar_20061030.1-2.2.dsc
 a135bb2f0e8ac623ab5fd0904ec7a4e0 3032 utils optional 
metar_20061030.1-2.2.debian.tar.xz
 93445bdd8e4ffa9e5a1320d702258bcc 21896 debug extra 
metar-dbgsym_20061030.1-2.2_amd64.deb
 6005cd3b804005605732fb5587aa42f7 16620 utils optional 
metar_20061030.1-2.2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX6OEOAAoJED9JDeuHHvn6FaEQAJMEv06exoZbQqiVXJ7TTL7G
2MWOg069jGKHDKVC8CP6oKKDekPI22uwIFr8Zb0tWFhDo3C7dxgLBbuY1i/+0oV5
SbYXoAHOXTvmJhkkIfQkQMITi6y0m/LVW8U60rNQzunQMqrtyfrAbwncnxEq9l0w
q0tVcdGi8acsxEmIRm8NMjjIicpoh+RG3y6Dvq/OW4JnUxwxX+f6xG/SfTXpqL01
dfYJQ9AhsgvSH5WEyiwVeXdCIpu7JHV4FBbs44izM4UMTsmMbbMvdp5X56HfNLYg
IbukYEFPpa5AQYa71VAH0yGAM61B9o5ul+fPOtMywX+UZHggAw5ft4NCFGAws3Qh
gjU65lWqAMlGo1MInxdlNb7bzUB7aPmywrgi00038gSudz/CFM1h38VJgUnmksy7
CbFwAq2s/kOs9Wfk44Y4g6PKwJniBs94PYMrTkphEOElkjCvpAhW714Yiqs5wCRL
ZaA27S6L9UVJPPp8N5mGegiAnUsjG86NUl6kHx8tyx5MYz9rDN3wW+HVlRRwATXh
UEcexadXkupExVm2+TTc0qEVYM8frHZ+LG7L/FDn6hudjWALM83YFLuLGWURiGT1
AlwOdJ6JmD/GI8Abut6g9Gp8QvHkL535XrCjNNs8Fk+hvWgJ2qeXDOOxhxsEWZCI
TDJaWDI+dXxMCQr94m9M
=cB+u
-END PGP SIGNATURE-

Accepted htop 2.0.2-1 (source) into unstable

2016-07-25 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Jul 2016 19:46:17 +0200
Source: htop
Binary: htop
Architecture: source
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Lange <dl@usrlocal.de>
Changed-By: Daniel Lange <dl@usrlocal.de>
Description:
 htop   - interactive processes viewer
Closes: 821747 822963
Launchpad-Bugs-Fixed: 1589549
Changes:
 htop (2.0.2-1) unstable; urgency=medium
 .
   * Update to upstream version 2.0.2
 - Use SOURCE_DATE_EPOCH instead of current year in copyright message
   to make build reproducible. (Closes: #822963)
 - Fix build to detect the Hurd as a Linux platform. (Closes: #821747)
 - Fix crash when setting CPU affinity and -fPIE. (LP: #1589549)
   * Bump Standards to 3.9.8 (no changes required)
Checksums-Sha1:
 132df634a4f1d060d0e115ebf7bd457cce261f03 2003 htop_2.0.2-1.dsc
 201f793f13dce2448e36047079875b9bd5bba75a 476364 htop_2.0.2.orig.tar.gz
 db9ca29c70973b4dc76165686a718e1261471a7e 7916 htop_2.0.2-1.debian.tar.xz
Checksums-Sha256:
 8c1fa82357c164cfdb35922d137bfa68ec325f1b7802d69a65d8e814d3c25f4b 2003 
htop_2.0.2-1.dsc
 179be9dccb80cee0c5e1a1f58c8f72ce7b2328ede30fb71dcdf336539be2f487 476364 
htop_2.0.2.orig.tar.gz
 8d13c21c6228b811f5a8b12b8fbc6fb278f53995a3863c41e9e8dd1f268572a9 7916 
htop_2.0.2-1.debian.tar.xz
Files:
 687165d3de8ad349bcd1396f9c0c1a2c 2003 utils optional htop_2.0.2-1.dsc
 7d354d904bad591a931ad57e99fea84a 476364 utils optional htop_2.0.2.orig.tar.gz
 ccc6c1adaf020964926c00a6a85a3807 7916 utils optional htop_2.0.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXllYUAAoJEK/P7I5mnOHC1NAP/jcy1XACP8jv+oKvX+pVx3SC
sFZrBGeJOYUj7PAX3ZGfZxN59vRqKhMQKhDWWdWfdenfvnHquurx6KnNYaJznhqi
wCVrkd7voyNAY1a82iifTUFKcvYTF8Fsds71CEATZ6wJqqDxx6Wg5Vj4ZCjeDVRM
B4Z/8ykgA6BxDa+sSc0fXHkfQPdmGZhbo4Tvn2oEdmjJeJRu+Xlqe5yz22uolyH7
Ffl5BI/fSGL4pJG1p1F9FOvjTvzzWUV5RtGKqYV51hlbbeEBMDdStXTTlT6ftXSM
5stHpRKPx/TRcSNKuVhHA0ayikLFWQaX2Qh0mwkiMomrK6G0jqooKAaJfVK85AEg
iDOJuYasLMghs3lcU1VpEPW855+agFaWq0cake2ZQrY2czsEGVRVxmQvY+RS33NT
nqdPOWT4TQBV/hv+ZDMidBnDtXSMIxO4BgKzjJpm3eszvcd6WTsMy8y1Kb5P7naa
OJD4+LoiuRbifL6tP10tLZdGf06gShH1zEihxin8hRL48HCAQZurk9AFIJ02/G61
Os/Iu+57N2ttNertD7iaqjLjWnrvMFyZf6S4i3tL5Rgr0bBPBH35kZUaoqDZaQjj
JtV/hPJkgoDVMgJeotr+F22/wXrdkoaLyuIlsjQJ/5TDA1ZM2BZJmFo2WopJFDAQ
d1F6HQgHwfHDuni+ortG
=3bRO
-END PGP SIGNATURE-

Accepted htop 2.0.1-1 (source) into unstable

2016-04-14 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Apr 2016 10:25:45 +0200
Source: htop
Binary: htop
Architecture: source
Version: 2.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Lange <dl@usrlocal.de>
Changed-By: Daniel Lange <dl@usrlocal.de>
Description:
 htop   - interactive processes viewer
Closes: 749850 774930 783893 814401 817918
Changes:
 htop (2.0.1-1) unstable; urgency=medium
 .
   * New upstream release 2.0.1. (Closes: #814401, #783893, #774930)
   * Clean up patches from 1.0.3 -> 2.0.1
   * Update compat -> 9, rules -> debhelper/9
   * Update debian/copyright to copyright-format/1.0 (Closes: #749850)
   * Add lsof as suggested (Closes: #817918)
   * Change maintainership jackyf -> DLange, jackyf and ginggs will
 co-maintain. Jackyf: Thank you very much for 8 years of htop
 maintenance!
Checksums-Sha1:
 d8814b7c794b60f4870f605d757ff19eafdceb35 2003 htop_2.0.1-1.dsc
 ef9adab68b0218a16936c306f635e7fce227b7e6 477196 htop_2.0.1.orig.tar.gz
 31ef67ee715ea9ce10d44af4bc82e06dc3b9f4b8 8212 htop_2.0.1-1.debian.tar.xz
Checksums-Sha256:
 510b828916e1d0edf65a09b24878343d071d5e8d36838133c749c42d2242d16e 2003 
htop_2.0.1-1.dsc
 f410626dfaf6b70fdf73cd7bb33cae768869707028d847fed94a978e974f5666 477196 
htop_2.0.1.orig.tar.gz
 2acb433fe08b80c90468e7b943f1ab5bf09d89b8207ea4a9ae30156785c879b3 8212 
htop_2.0.1-1.debian.tar.xz
Files:
 6aafd805bba8e7a28deff7342f184166 2003 utils optional htop_2.0.1-1.dsc
 f75fe92b4defaa80d99109830f34b5e2 477196 utils optional htop_2.0.1.orig.tar.gz
 2e2a183ef385be8bc8795d7e6d30a6b4 8212 utils optional htop_2.0.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXD1a/AAoJEK/P7I5mnOHCSl4P/i4VFg/ojViORS/Guwymo98T
xIjdS/5otuzursixmoGvJLSrxK2t7VRXHrEOxuh04j+sxrT3OQyt8hZmF3HdfOff
sS6zG/AkKp2F74S2/xggQWCnFpm7OZPEIfHbedZB6q1bujrp/U/losY/xJvMfL/x
bsuI9rigHUcW7ixm/LDiO2JCJbc1z4yNfHZuBpM1M/6sea6Amn/E14h7ycgcRaLx
hnhB8Rq3CivOFe9XU8WVTPfKjUfXFRbCYYjV2gLcC9sECOP8NAzW4BZpHlb/WW44
FUwcTbGMCbSPDYWJGzWctIfHN/XJnfFq0ejXVpDU/x5C6jmYN9qq0rSbZOw4pCKI
4OgqHjZRUCX95C0wjJmdkf/8cJwZcOne2CL6vXZOhgJItrKrbu2A44cWAPaAIRmL
pAQ4xleZpD5V/c6Ub1gQhfgbHi8kzyN/FKpXpIC+r9zk5cLKlKkYKre/1S5MLH2K
fvZzRhUaYqDW6aJVAl06th1lWQJ3TZaBMRMSxHl1mBy3sQ3coREyS+uHxOnDRm8E
HoZA2sHhW2WudOcSBDc21hNg/6RuLT7/ubBnKoc1EufyLOceKuNJdboUgcUEj1rT
IvcXU1jgX3SrjLTSYFCk0V33LND5yseS3aPOP2kkBTuWRmpx70F7XxTfwIjMqVcU
nuQMilkz051vlxrNNuju
=g/KU
-END PGP SIGNATURE-

Accepted cronic 3-1 (source) into unstable

2016-04-11 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 10 Apr 2016 10:59:36 +0200
Source: cronic
Binary: cronic
Architecture: source
Version: 3-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Lange <dl@usrlocal.de>
Changed-By: Daniel Lange <dl@usrlocal.de>
Description:
 cronic - Bash script for wrapping cron jobs to prevent excess email sendin
Closes: 820331
Changes:
 cronic (3-1) unstable; urgency=medium
 .
   * Updated from upstream. (Closes: #820331)
   * Update manual to v3.
   * Update policy to 3.9.8 (no changes required).
Checksums-Sha1:
 101351e9e034906f78c1691dbb93e304858f731b 1761 cronic_3-1.dsc
 ebc01c07bfdeabc8df1c619bb85ecff9eebf6274 648 cronic_3.orig.tar.xz
 961fd6a6ba1d619f7306488ae969f24695933907 4976 cronic_3-1.debian.tar.xz
Checksums-Sha256:
 17cdb43e5106232d01389182e5fe7b0f1c9398071f41d1ffe0e4d9b2031ba761 1761 
cronic_3-1.dsc
 9327fe6712b947329478dcb7d86da6463872ed1bcfc9fe4c178ff3cb6cc388a9 648 
cronic_3.orig.tar.xz
 7e06810dbc0fd43ee51d5baf476c4eed2cfa6919a3c892bda22332e261badf8c 4976 
cronic_3-1.debian.tar.xz
Files:
 dbf3ccdaa7b7e93189c6f3bbac4f7ab7 1761 admin optional cronic_3-1.dsc
 4fca21d4efef3488151dc83773c3c66a 648 admin optional cronic_3.orig.tar.xz
 f0b01b02f6c7ff295d99c73dd64cf5aa 4976 admin optional cronic_3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXC2AuAAoJEK/P7I5mnOHCHXkP/jMk4OQmKjaLjDcJbRULYvZE
Zey3CsQbP/gPLWAqVS3d8VLK7M2PagWFnFT7un6FKgNDoFYRbKfLFSbYHRUAd5LB
DcebHdrLzPfaUzQ+3GLPTdG69uYX6lURSa7jLztF7Ze7kvHeQN6TB6vbugbLMPZF
4UDsQYwPf6FO2KyPnSTzmflq71oRPTPSYwcsb38VuQ3X9pENp1J/pfsSStKLK7T+
hCpzs9w2rJqjzoKayPOxG0caXdhM4YROGewBYvU2h/NgoY90ijcyGDPmLL9HC+us
cVO3q8gXcomzHvV5ALLru/ZAT3jBDkjfHnbkqJ9Rlsqc4KGZmG2ylPZH5QMRheZS
bUg3hm2KuuUR1t4RYr/Ict7CWLXqiecGWqKesbtgRhAYKf/+wQ4G7k4EUHWvA2tt
5xc11VyRHypoo1le5wHuDGItPF/rXQDj61SwwpF4uU1EB1O9hJkMFXi/H9XqiXmD
A8qrq4v6mwRRO1OXwHkK2qj+MoZ2yVAABFeaip//tS+q79f71ghLAONx/E29vWKO
0vzoswZirivzap0G/3jqJWDHUagsaKLdTOJvC7Diot09RGvD4FSV4fXDjP3cLByj
gHbm7nOiz9rs9P4P2BPYyJWUVAip1XhL3+OWXUMNQR8hSHRqj9LkO0ilGCrLsVyq
I6Z9cdqKleDYWAw0sz3V
=Gntq
-END PGP SIGNATURE-

Accepted cronic 2-1 (source all) into unstable, unstable

2016-03-23 Thread Daniel Lange 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 Mar 2016 13:15:20 +0100
Source: cronic
Binary: cronic
Architecture: source all
Version: 2-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Lange <dl@usrlocal.de>
Changed-By: Daniel Lange <dl@usrlocal.de>
Description:
 cronic - Bash script for wrapping cron jobs to prevent excess email sendin
Closes: 711017
Changes:
 cronic (2-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #711017)
Checksums-Sha1:
 d115f1a1e0684736fc218cbe741b5ddad7bbbf80 1763 cronic_2-1.dsc
 8e56de81263b2eb9959d7b9d42a4465e1f6eadbe 636 cronic_2.orig.tar.xz
 cbd88cdf61441a44c7f8c56a0cc2c78c5e3fa98d 4876 cronic_2-1.debian.tar.xz
 cc8e84cff3a3cbaef2fc8156a86b8e71b2303a72 6090 cronic_2-1_all.deb
Checksums-Sha256:
 161a191dca132d7684715e93d16ddf6a9bb35fe0f96dfb48ab4d5d74affeacf7 1763 
cronic_2-1.dsc
 b427c24301f3be991a9669828aa4ce9820ac993dec1f6cd9f153c851f55094ae 636 
cronic_2.orig.tar.xz
 8c4e00ab451de1def02dbc9da40ebbcefc7eb6d6ca5f89bdf8d1acf508ca2ea7 4876 
cronic_2-1.debian.tar.xz
 1ca6a2c2e7fbac88441d501b47d54cb67a870f4164b5a441dc2cd5f3376a1e46 6090 
cronic_2-1_all.deb
Files:
 fc165375e79be132e00d67b7da33d948 1763 admin optional cronic_2-1.dsc
 f6f7210e511d8c38eb10ad2ccd9c4b21 636 admin optional cronic_2.orig.tar.xz
 d663ea93d20cdf19f5c86294e4b8468b 4876 admin optional cronic_2-1.debian.tar.xz
 9ba6114a1c9be4b4bd0f27268d247efd 6090 admin optional cronic_2-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJW8TYIAAoJEK/P7I5mnOHCqAsP/38XJ8NI3FDxwU8ZaLy6MNGh
Aa6nM2Joi37KsZxNX2WYMy0GXbi0MIa56KABKpSUSFd9lYVQQC3YD+Klr883Lsx6
tX7Roct/iuQcrF5etbnD80P6MJ/y9Yq7BJOUv3grxX4tyjsFi0xezCwnKVOYJL7L
nrCdW0Ut6tsVTSRnQpDPmTzQMJG1IZZubrpp5AMUH5lIxDSogSqtdj1MtwRjIwCL
253pq/z+axpNhSH+S6rneYUATCD8V9YdTz2Vee2IQhldt85n0otJvidtDXTeC+wm
DOCpIKYFa5o2LvPY7SROf/78ZU2Luhj8HTXvgYhLmTgO0HbljaMN6M06fQvP31W+
iXsTqzhRuN1VA3Ilu03lpzoOqwIIqUvIuyVDY2lJgstOqVBxC6/Obk2X2mAa7Qe4
656D7UJtNmXw19OxWDg+E5Jw3Qkqdo2gSUB1wkV/gI0Ox7+lQpWbEgZP377sADqq
7Shf09b6slTmFkoOzUWaW+5bMgsC4Z6BkewmrtWv49en8Bf7USKWQy7DwGO5/DSu
XD05/h7mLZcHwhW2qc1xEmDevOOJq45VB/UXD/BecKM3aeumt48VNkIvik0eMfHP
k8w890XwPUmw0dWPRaA9/LGmk1uJxsgT/CjQf4nUXmuhfWYJOr/UzxkGHKv/8hpU
RsuYa/3rekTVp9I0adtI
=yql6
-END PGP SIGNATURE-