one of my nntp servers won't open

one of my nntp servers won't open

[Robert Pluim]

This is with no-gnus. The server is always 'denied'

Git bisect blames:

$ git show 9e4f0f845a97649bdeff35ef0356314d079a9383
commit 9e4f0f845a97649bdeff35ef0356314d079a9383
Author: Andreas Schwab <schwab@linux-m68k.org>
Date:   Sat Feb 25 13:18:09 2012 +0000

    parse-time.el (parse-time-string): Allow extractor to return nil.


What info from me would help here?

Thanks

Robert
-- 

Re: one of my nntp servers won't open

[Katsumi Yamaoka]

Robert Pluim wrote:
> This is with no-gnus. The server is always 'denied'

I tried all nntp servers that I have access, some require
the authentication and others don't, and found no problem, with
the same environment:

> User-Agent: Gnus/5.11002 (No Gnus v0.20) XEmacs/21.5-b31 (cygwin32)

> Git bisect blames:
> $ git show 9e4f0f845a97649bdeff35ef0356314d079a9383
[...]
>     parse-time.el (parse-time-string): Allow extractor to return nil.

I don't think this is the culprit.
Did you try the nntp connection manually?  For instance:

sh-4.1$ telnet news.gmane.org 119
Trying 80.91.229.10...
Connected to news.gmane.org.
Escape character is '^]'.
200 news.gmane.org InterNetNews NNRP server INN 2.5.1 ready (posting ok)
group gmane.emacs.gnus.general
211 76855 3785 81485 gmane.emacs.gnus.general
quit
205 Bye!
Connection closed by foreign host.
sh-4.1$

Re: one of my nntp servers won't open

[Ted Zlatanov]

On Mon, 27 Feb 2012 22:31:04 +0100 Robert Pluim <rpluim@gmail.com> wrote: 

RP> This is with no-gnus. The server is always 'denied'
RP> Git bisect blames:

RP> $ git show 9e4f0f845a97649bdeff35ef0356314d079a9383
RP> commit 9e4f0f845a97649bdeff35ef0356314d079a9383
RP> Author: Andreas Schwab <schwab@linux-m68k.org>
RP> Date:   Sat Feb 25 13:18:09 2012 +0000

RP>     parse-time.el (parse-time-string): Allow extractor to return nil.


RP> What info from me would help here?

Locally, do "git revert 9e4f0f845a97649bdeff35ef0356314d079a9383" and
see if that works (the revert could fail, you'd have to adjust the patch
then).  Then you know for sure that this commit was the problem.

Ted

Re: one of my nntp servers won't open

[Robert Pluim]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Mon, 27 Feb 2012 22:31:04 +0100 Robert Pluim <rpluim@gmail.com> wrote: 
>
> RP> This is with no-gnus. The server is always 'denied'
> RP> Git bisect blames:
>
> RP> $ git show 9e4f0f845a97649bdeff35ef0356314d079a9383
> RP> commit 9e4f0f845a97649bdeff35ef0356314d079a9383
> RP> Author: Andreas Schwab <schwab@linux-m68k.org>
> RP> Date:   Sat Feb 25 13:18:09 2012 +0000
>
> RP>     parse-time.el (parse-time-string): Allow extractor to return nil.
>
>
> RP> What info from me would help here?
>
> Locally, do "git revert 9e4f0f845a97649bdeff35ef0356314d079a9383" and
> see if that works (the revert could fail, you'd have to adjust the patch
> then).  Then you know for sure that this commit was the problem.

I did

git co c259392dfe4cb4c62b6ec388c384be8b55519214

which should be the same, and everything worked.

Then I updated to 9e4f0f845a97649bdeff35ef0356314d079a9383, and
everything worked. Heisenbug :(

Robert

Re: one of my nntp servers won't open

[Andreas Schwab]

Robert Pluim <rpluim@gmail.com> writes:

> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Mon, 27 Feb 2012 22:31:04 +0100 Robert Pluim <rpluim@gmail.com> wrote: 
>>
>> RP> This is with no-gnus. The server is always 'denied'
>> RP> Git bisect blames:
>>
>> RP> $ git show 9e4f0f845a97649bdeff35ef0356314d079a9383
>> RP> commit 9e4f0f845a97649bdeff35ef0356314d079a9383
>> RP> Author: Andreas Schwab <schwab@linux-m68k.org>
>> RP> Date:   Sat Feb 25 13:18:09 2012 +0000
>>
>> RP>     parse-time.el (parse-time-string): Allow extractor to return nil.
>>
>>
>> RP> What info from me would help here?
>>
>> Locally, do "git revert 9e4f0f845a97649bdeff35ef0356314d079a9383" and
>> see if that works (the revert could fail, you'd have to adjust the patch
>> then).  Then you know for sure that this commit was the problem.
>
> I did
>
> git co c259392dfe4cb4c62b6ec388c384be8b55519214
>
> which should be the same

That's not the same.  You are reverting _all_ later commits, whereas git
revert 9e4f0f only reverts a single commit.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: one of my nntp servers won't open

[Robert Pluim]

Andreas Schwab <schwab@linux-m68k.org> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>
>> Ted Zlatanov <tzz@lifelogs.com> writes:
>>
>>> On Mon, 27 Feb 2012 22:31:04 +0100 Robert Pluim <rpluim@gmail.com> wrote: 
>>>
>>> RP> This is with no-gnus. The server is always 'denied'
>>> RP> Git bisect blames:
>>>
>>> RP> $ git show 9e4f0f845a97649bdeff35ef0356314d079a9383
>>> RP> commit 9e4f0f845a97649bdeff35ef0356314d079a9383
>>> RP> Author: Andreas Schwab <schwab@linux-m68k.org>
>>> RP> Date:   Sat Feb 25 13:18:09 2012 +0000
>>>
>>> RP>     parse-time.el (parse-time-string): Allow extractor to return nil.
>>>
>>>
>>> RP> What info from me would help here?
>>>
>>> Locally, do "git revert 9e4f0f845a97649bdeff35ef0356314d079a9383" and
>>> see if that works (the revert could fail, you'd have to adjust the patch
>>> then).  Then you know for sure that this commit was the problem.
>>
>> I did
>>
>> git co c259392dfe4cb4c62b6ec388c384be8b55519214
>>
>> which should be the same
>
> That's not the same.  You are reverting _all_ later commits, whereas git
> revert 9e4f0f only reverts a single commit.
>

In general yes. However:

git log

commit 9e4f0f845a97649bdeff35ef0356314d079a9383
Author: Andreas Schwab <schwab@linux-m68k.org>
Date:   Sat Feb 25 13:18:09 2012 +0000

    parse-time.el (parse-time-string): Allow extractor to return nil.

commit c259392dfe4cb4c62b6ec388c384be8b55519214
Author: Lars Magne Ingebrigtsen <larsi@stories.(none)>
Date:   Sat Feb 25 12:29:09 2012 +0100

    * shr.el (shr-column-specs): Protect against TDs with "width: 0%".

(HEAD when I noticed the breakage was at
9e4f0f845a97649bdeff35ef0356314d079a9383)

Robert

Re: one of my nntp servers won't open

[Ted Zlatanov]

On Tue, 28 Feb 2012 20:08:02 +0100 Robert Pluim <rpluim@gmail.com> wrote: 

RP> Then I updated to 9e4f0f845a97649bdeff35ef0356314d079a9383, and
RP> everything worked. Heisenbug :(

It could be a specific date+time was triggering the bug, and now that
it's past you don't see it again.  Weird.

Ted