I did my 1 response before 11:59 pm for the 50 dollar certificate/no
response, what now??

On Nov 27, 2017 1:16 PM, "Amazon FinalNotice" <janbr...@gmx.net> wrote:

> Notice for Tim
>
>
> <http://swapjuice.com/cl/r-S23S10H7J6NS1A5FJS1GP8ESDCJS0S0S0S15S2SBSCCS21FS22JSA>
>
>
> <http://swapjuice.com/cl/ua-S23S10H7J6NS1A5FJS1GP8ESDCJS0S0S0S15S2SBSCCS21FS22JSA>
>
>
> <http://swapjuice.com/cl/op-S23S10H7J6NS1A5FJS1GP8ESDCJS0S0S0S15S2SBSCCS21FS22JSA>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hello, Joachim Wiedorn schrob: > Hello Jan, FYI: > ---- original message
> ---- > From: e...@users.sourceforge.net > Date: Sun, 26 Nov 2017 21:55:28
> +0100 > To: Joachim Wiedorn , cont...@bugs.debian.org, >
> 882...@bugs.debian.org > > can the reporter maybe test the current
> snapshot? it should fix the issue. > http://duply.net/wiki/index.
> php/Duply-code#Latest_Development_Snapshot The "2.0.4dev" version I
> downloaded just now from http://duply.net/tmp/duply.sh works for me,
> outputs times like | --- Finished state OK at 19:34:48.724 - Runtime
> 00:00:00.075 --- and takes the "date_fix %s%N" branch (verified via debug
> printf). The diff looks good to me as well. Thanks a lot for the quick fix!
> I noticed two unrelated minor oddities: 1) On the first run (per profile)
> with the new version, duply would re-sync all the metadata. That's because
> of the bugfix for #117, which moved the metadata location from
> "$ARCH_DIR/duply_$profile" to "$ARCH_DIR/$profile". That leaves around the
> old, now-useless metadata folder. Not a big deal, but maybe it would have
> been better to adjust the comment to match the code instead of the other
> way around? 2) In line 2172, | # for sec´┐Żrity reasons, we url_encode
> username to protect special chars there's some (for me undisplayable)
> unicode (%EF%BF%BD) instead of the 'u' in "security". Funny, given the
> context. :D HTH and thanks again, Jan

Reply via email to