edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
Cc: Karl Dahlke <eklhad@comcast.net>, edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Curl library error
Date: Mon, 29 Jan 2018 18:37:53 +0100	[thread overview]
Message-ID: <20180129173753.GA19481@nautica> (raw)
In-Reply-To: <alpine.DEB.2.21.1801291123540.4266@debian.pulsar.com>

Chuck Hallenbeck wrote on Mon, Jan 29, 2018:
> If I decide to backtrack, it makes sense to do  so stepping backward a
> day at a time until I can once more access that site.  But what would
> that tell us?

If you're up for it, git has a 'bisect' command where it goes halfway in
history everytime and you tell it if the commit works or doesn't work.
(If required you can also tell it "this commit doesn't work for a
different reason and I cannot test", which will give you another commit
close-ish to test again)

That will tell you precisely which commit changed the behavior and we
can look into it.


But first, please make sure going back to some old version like the
commit Karl pointed at makes it work again -- I tried on a slightly
outdated archlinux (last upgrade is two weeks old) and it works just
fine, so your problem could be due to some system upgrade instead.
Or, since you're pointing at the https version, it could be a TLS
problem.... But we should get that too in that case, it is odd.

-- 
Dominique

  reply	other threads:[~2018-01-29 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 12:09 Chuck Hallenbeck
2018-01-29 14:06 ` Karl Dahlke
2018-01-29 15:19   ` Chuck Hallenbeck
2018-01-29 15:27   ` Chuck Hallenbeck
2018-01-29 16:03 ` Karl Dahlke
2018-01-29 16:53   ` Chuck Hallenbeck
2018-01-29 17:37     ` Dominique Martinet [this message]
     [not found] ` <alpine.DEB.2.21.1802010449280.1929@debian.pulsar.com>
2018-02-01 18:08   ` Karl Dahlke

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=20180129173753.GA19481@nautica \
    --to=asmadeus@codewreck.org \
    --cc=chuckhallenbeck@gmail.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).