[HACKERS] [URGENT] v6.4.1 was a mis-package...

Started by The Hermit Hackerabout 27 years ago3 messages
#1The Hermit Hacker
scrappy@hub.org

Due to an error on my part, I mistakenly packaged up the -CURRENT source
tree as being v6.4.1, vs the actual v6.4.1 source tree...

This has *just* been fixed as of two minutes ago...

For those running production environments, *please* download this new
package and rebuild :(

Sorry for the inconvience that this is going to cause most ppl...

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

#2Sascha Schumann
sas@schell.de
In reply to: The Hermit Hacker (#1)
Re: [HACKERS] [URGENT] v6.4.1 was a mis-package...

On Thu, 24 Dec 1998, The Hermit Hacker wrote:

Due to an error on my part, I mistakenly packaged up the -CURRENT source
tree as being v6.4.1, vs the actual v6.4.1 source tree...

This has *just* been fixed as of two minutes ago...

For those running production environments, *please* download this new
package and rebuild :(

Are there any big flaws in it which could result in data loss? I ran some
updates just yesterday with the what-I-thought-would-be 6.4.1.

Regards,

Sascha Schumann |
Consultant | finger sas@schell.de
| for PGP public key

#3Bruce Momjian
maillist@candle.pha.pa.us
In reply to: Sascha Schumann (#2)
Re: [HACKERS] [URGENT] v6.4.1 was a mis-package...

On Thu, 24 Dec 1998, The Hermit Hacker wrote:

Due to an error on my part, I mistakenly packaged up the -CURRENT source
tree as being v6.4.1, vs the actual v6.4.1 source tree...

This has *just* been fixed as of two minutes ago...

For those running production environments, *please* download this new
package and rebuild :(

Are there any big flaws in it which could result in data loss? I ran some
updates just yesterday with the what-I-thought-would-be 6.4.1.

Good question. We have some new stuff in 6.5 tree, and none of it
tested. The only thing that I think could be a problem is Vadim's
changes to the structure of the row headers. This could majorly break
things internally.

The big problem is that the data rows were created with a different
format than the backend expected. At least that is my conclusion based
on what Vadim had done.

A dump/restore should may fix any breakage, but you may have to restore
and re-run the updates.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026