At 2:14 Uhr +0200 11.05.1998, Greg A. Woods wrote:
>[ On Sun, May 10, 1998 at 08:38:31 (-0600), Jim Bernard wrote: ]
>> Subject: BEWARE: sup just deleted entire pkgsrc tree
>>
>>   Does anybody have any clue why sup just deleted my entire pkgsrc tree.
>> On two systems.  No changes to the local sup configurations in months, and
>> no changes to the local operating systems in more than a week.  Sup runs
>> have been normal on a daily basis "forever".  Yes, I've got it configured
>> with the "delete" option---always have.
>
>yup, mine too.
>
>That's why I'd never do anything live in a sup mirror.

Still, this misses the point.

Early this month, sup erased the gnu tree just to re-load it afterwards.
Warned by this thread, i could intervene just in time to keep it from
erasing pkgsrc yesterday. I copied the subtree, let sup do its thing and
found it installs a link to "../packages/pkgsrc" from its base dir (that
would be /usr for the default configuration). I have my sup dir on an amd
mounted disk under "/vol/sup-netbsd", and the attempt to set said link
failed miserably.

FYI, I am living behind the wrong end of a 14k4 ppp link, and the "best"
local call rate of the German Telekom is ~2 DM/hr. The mentioned "gnu"
delete cost me 15-20 DM.

So, a few questions remain open:

o  Why wasn't there any announcement of the deletes like there was at the
beginning of the year? That's what "netbsd-announce" is for!

o  What was this bogus "pkgsrc" manoeuvre actually trying to do in the
first place?

o  Could the responsible person please stand up and apologize (and spend me
a pizza if he happens to live near Heidelberg ;) ?

	hauke


--
"It's never straight up and down"     (DEVO)