From: chad <yandros@gmail.com>
To: bruce.connor.am@gmail.com
Cc: 20809@debbugs.gnu.org
Subject: bug#20809: 25.0.50; package-list-packages never finishes async update if cert bad
Date: Sun, 14 Jun 2015 15:52:29 -0700 [thread overview]
Message-ID: <F06D3F22-7953-43FB-826A-E8CEB582A2C7@gmail.com> (raw)
In-Reply-To: <CAAdUY-Lt0p30KR5UkEmxS+XZbW3UMX-hEFwvSVcBZKb-+t_Zag@mail.gmail.com>
> On 14 Jun 2015, at 14:52, Artur Malabarba <bruce.connor.am@gmail.com> wrote:
>
> I pushed a change which should handle this, but I can't test it
> because I don't get the "connection cannot be secured" message even if
> I follow your recipe (which is weird, since visiting marmalade on the
> browser clearly shows the certificate is still bad).
>
> Let me know if it works for you.
I just rebuilt, and it seems to be working. It’s a bit hard to tell
if the other sources are all updating correctly, because the
timestamps on the other sources aren’t updating to the current date
- I *believe* because there arent any new packages since their last
updates. The list updates quickly, and “U" gives me the expected
"nothing to update" response.
; ls -alR archives/*/archive-contents
-rw-r--r-- 1 yandros staff 11670 Jun 13 20:56 archives/Tom/archive-contents
-rw-r--r-- 1 yandros staff 21278 Jun 14 15:45 archives/gnu/archive-contents
-rw-r--r-- 1 yandros staff 113127 Jun 13 16:18 archives/marmalade/archive-contents
-rw-r--r-- 1 yandros staff 159677 Jun 13 20:56 archives/melpa-stable/archive-contents
Thanks!
~Chad
next prev parent reply other threads:[~2015-06-14 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 4:03 bug#20809: 25.0.50; package-list-packages never finishes async update if cert bad chad
2015-06-14 10:55 ` Artur Malabarba
2015-06-14 17:50 ` chad
2015-06-14 21:52 ` Artur Malabarba
2015-06-14 22:52 ` chad [this message]
2015-06-15 8:50 ` Artur Malabarba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F06D3F22-7953-43FB-826A-E8CEB582A2C7@gmail.com \
--to=yandros@gmail.com \
--cc=20809@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.