lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lynx-dev] Someone please fix these FSF mailing lists for good!


From: Thorsten Glaser
Subject: [Lynx-dev] Someone please fix these FSF mailing lists for good!
Date: Fri, 2 Mar 2007 05:01:19 +0000 (UTC)

Hi people,

please someone tell the US-American FSF to get IPv6!

Find attached below 2 mails:
• the original mail I wanted to send to this list
  (since it probably won't get through)
• the error report… clueless admins…

bye,
//mirabile
-- 
  "Using Lynx is like wearing a really good pair of shades: cuts out
   the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
                                         -- Henry Nelson, March 1999

---------- Forwarded message ----------
From: Thorsten Glaser <address@hidden>
Message-ID: <address@hidden>
To: address@hidden
Cc: Benny Siegert <address@hidden>
Date: Fri, 2 Mar 2007 00:44:58 +0000 (UTC)
Subject: Re: lynx2.8.7dev.2 distfile size/checksum mismatch

Thomas Dickey dixit:

>> I get the 3188012b file too. Seems as if the distfile changed,
>> but why? (NB: This is the nightmare of all porters and packagers.)
>
>I haven't touched it...

For reference: I managed to dig out the old .tar.gz, then uncompressed
both, hexdump'd them and put that through diff. Here the results:

--- old/lynx2.8.7dev.2.tar.hd   Fri Mar  2 00:20:48 2007
+++ new/lynx2.8.7dev.2.tar.hd   Fri Mar  2 00:20:51 2007
@@ -3,8 +3,8 @@
 *
 00000060  00 00 00 00 30 30 30 37 - 37 35 20 00 30 32 33 37  |....000775 .0237|
 00000070  31 31 20 00 30 32 33 33 - 37 34 20 00 30 30 30 30  |11 .023374 .0000|
-00000080  30 30 30 30 30 30 30 20 - 31 30 35 32 33 37 35 37  |0000000 10523757|
-00000090  37 30 30 20 30 31 32 37 - 30 37 00 20 35 00 00 00  |700 012707. 5...|
+00000080  30 30 30 30 30 30 30 20 - 31 30 35 32 35 37 34 33  |0000000 10525743|
+00000090  34 31 31 20 30 31 32 37 - 30 33 00 20 35 00 00 00  |411 012703. 5...|
 000000A0  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  |................|
 *
 00000100  00 75 73 74 61 72 00 30 - 30 64 69 63 6B 65 79 00  |.ustar.00dickey.|
@@ -284676,8 +284676,8 @@
 *
 0046F460  00 00 00 00 30 30 30 37 - 37 35 20 00 30 32 33 37  |....000775 .0237|
 0046F470  31 31 20 00 30 32 33 33 - 37 34 20 00 30 30 30 30  |11 .023374 .0000|
-0046F480  30 30 30 30 30 30 30 20 - 31 30 35 31 33 35 35 35  |0000000 10513555|
-0046F490  37 35 30 20 30 31 33 33 - 32 35 00 20 35 00 00 00  |750 013325. 5...|
+0046F480  30 30 30 30 30 30 30 20 - 31 30 35 32 35 37 34 33  |0000000 10525743|
+0046F490  34 30 31 20 30 31 33 33 - 32 30 00 20 35 00 00 00  |401 013320. 5...|
 0046F4A0  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  |................|
 *
 0046F500  00 75 73 74 61 72 00 30 - 30 64 69 63 6B 65 79 00  |.ustar.00dickey.|
@@ -510752,8 +510752,8 @@
 *
 007E7E60  00 00 00 00 30 30 30 37 - 37 35 20 00 30 32 33 37  |....000775 .0237|
 007E7E70  31 31 20 00 30 32 33 33 - 37 34 20 00 30 30 30 30  |11 .023374 .0000|
-007E7E80  30 30 30 30 30 30 30 20 - 31 30 35 32 33 37 35 37  |0000000 10523757|
-007E7E90  36 36 33 20 30 31 33 35 - 30 36 00 20 35 00 00 00  |663 013506. 5...|
+007E7E80  30 30 30 30 30 30 30 20 - 31 30 35 32 35 37 34 33  |0000000 10525743|
+007E7E90  34 30 31 20 30 31 33 34 - 37 31 00 20 35 00 00 00  |401 013471. 5...|
 007E7EA0  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  |................|
 *
 007E7F00  00 75 73 74 61 72 00 30 - 30 64 69 63 6B 65 79 00  |.ustar.00dickey.|

Seems like three timestamps changed. Looking at which…
* lynx2-8-7             10523757700 -> 10525743411
* lynx2-8-7/po          10513555750 -> 10525743401
* lynx2-8-7/src         10523757663 -> 10525743401

No, these can't be timestamps:
10523757700 = Sat Jun 27 18:01:17 UTC 2303

Eww, what's this then? If it were a cpio… well, let's
dig into the sources of the tar driver. Heh! These
are indeed mtimes. (I guess GNU tar's just broken.)

----

Now: why?

bye,
//mirabile
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.              -- Coywolf Qi Hunt
---------- Forwarded message ----------
From: Mail Delivery Subsystem <address@hidden>
Message-ID: <address@hidden>
X-Spam-Status: No, hits=0.000000 required=0.900000
To: address@hidden
Date: Fri, 2 Mar 2007 04:54:50 GMT
Subject: Warning: could not send message for past 4 hours

    **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Fri, 2 Mar 2007 00:45:06 GMT
from address@hidden [IPv6:2001:6f8:94d:4:2c0:9fff:fe1a:6a01]

   ----- Transcript of session follows -----
... while talking to mx10.gnu.org.:
>>> DATA
<<< 451-could not connect to odem.66h.42h.de 
[2001:6f8:94d:4:2c0:9fff:fe1a:6a01]: Address family not supported by protocol
<<< 451-Could not complete sender verify callout for <address@hidden>.
<<< 451-The mail server(s) for the domain may be temporarily unreachable, or
<<< 451-they may be permanently unreachable from this server. In the latter 
case,
<<< 451-you need to change the address or create an MX record for its domain
<<< 451-if it is supposed to be generally accessible from the Internet.
<<< 451 Talk to your mail administrator for details.
<address@hidden>... Deferred: 451-could not connect to odem.66h.42h.de 
[2001:6f8:94d:4:2c0:9fff:fe1a:6a01]: Address family not supported by protocol
<<< 503 valid RCPT command must precede DATA
... while talking to mx20.gnu.org.:
>>> DATA
<<< 451 Could not complete sender verify callout
<address@hidden>... Deferred: 451 Could not complete sender verify callout
<<< 503 valid RCPT command must precede DATA
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old




reply via email to

[Prev in Thread] Current Thread [Next in Thread]