ports git repo frozen - anything important I missed?

SirDice said:
Summer holiday season?
Click to expand...
It is true that there are few committers in the Southern Hemisphere.
capt.png
captn.png
 
I remember that time when a ports committer made a random import with lots of build artifacts including a work/ directory - and an emacs *.core file :)
 
emacs.core is also mentioned in the 30th-anniversary.

FreeBSD 30th Anniversary Special Edition | FreeBSD Foundation

Table of Contents (Now with article PDFs) I'm Not From Yorkshire, I promise! How Time Flies: A Personal Timeline FreeBSD and the Early Unix Communities Early FreeBSD Ports Recollections: An Interview with David Greenman Lawrence Installing FreeBSD 1.0: 30 Years On FreeBSD at 30 Years: Its...
freebsdfoundation.org freebsdfoundation.org
 
cracauer@ said:
Somebody fatfingered something. This also caused the inability to `pkg update` on releases this week.
Click to expand...
yeah, happens a lot more than people care to admit..

Suffered this also on the past, bfg was of help to remove the blobs from the tree with minimum fuss (though it doesn't help people that had already pulled the affected repo).
As for the *.core file, that has to go on the .gitignore root file from the start of the repo. Maximum file size is a pain because you can only reliably block that server side (which github does but apparently cgit.freebsd did not).

Learning experiences all around ;)
 
jbo@ said:
A public statement which will also shed some light on for how much longer the freeze will be in place should be released soon™
Click to expand...
drhowarddrfine said:
Don't make it a big deal. Nothing came crashing down. Crackers aren't going to break into your server. You aren't even going to notice the problem beyond the freeze or this notice. It's a temporary fat finger that will be fixed by tomorrow or so.
Click to expand...

Phew, thanks to both of you for the clarification. I'll just sit tight and have some tea.
 
Somebody did a git add -A against a directory with a file they probably forgot to remove before committing and pushing. git show --name-status would have been a good pre-push check. Or git status prior to commit.

Haste makes waste.
 
cy@ said:
Somebody did a git add -A against a directory with a file they probably forgot to remove before committing and pushing. git show --name-status would have been a good pre-push check. Or git status prior to commit.

Haste makes waste.
Click to expand...
git add, git commit
Exactly; I have to get this commit done
Oh crap I've added all kinds of stuff.
Not unique to git (but maybe easier with git?)
It's happened before on lots of other projects with/without git, users need to take a step back and breath once or twice
 
mer said:
git add, git commit
Exactly; I have to get this commit done
Oh crap I've added all kinds of stuff.
Not unique to git (but maybe easier with git?)
It's happened before on lots of other projects with/without git, users need to take a step back and breath once or twice
Click to expand...
It's human beings being human. I've done this before. Even with non-computer related things. Totally understandable but also totally unforgivable. This can contribute to the medical condition called flat forehead syndrome.

Which reminds me, I need to go outside and turn the water off a hose under a tree.
 
cy@ said:
It's human beings being human. I've done this before. Even with non-computer related things. Totally understandable but also totally unforgivable. This can contribute to the medical condition called flat forehead syndrome.

Which reminds me, I need to go outside and turn the water off a hose under a tree.
Click to expand...
Are you sure?

:)

I may need to smack my head against my desk...
 
You must log in or register to reply here.
Back
Top