WHOA!!! Screw up on my part: how do I undo this (Re: [Python-checkins] CVS: black - Imported sources)
I was playing with a different SourceForge project and I screwed up my CVSROOT (used Python's instead). Sorry SOrry! How do I undo this cleanly? I could 'cvs remove' the README.txt file but that would still leave the top-level 'black/' turd right? Do the SourceForge admin guys have to manually kill the 'black' directory in the repository? or-failing-that-can-my--pet-project-make-it-into-python-2.0-<weak-smile>-ly yours, Trent On Wed, Sep 27, 2000 at 12:06:06AM -0700, Trent Mick wrote:
Update of /cvsroot/python/black In directory slayer.i.sourceforge.net:/tmp/cvs-serv20977
Log Message: first import into CVS
Status:
Vendor Tag: vendor Release Tags: start
N black/README.txt
No conflicts created by this import
***** Bogus filespec: - ***** Bogus filespec: Imported ***** Bogus filespec: sources
_______________________________________________ Python-checkins mailing list Python-checkins@python.org http://www.python.org/mailman/listinfo/python-checkins
-- Trent Mick TrentM@ActiveState.com
Trent Mick writes:
I was playing with a different SourceForge project and I screwed up my CVSROOT (used Python's instead). Sorry SOrry!
Well, you blew it. Don't worry, we'll have you kicked off SourceForge in no time! ;) Well, maybe not. I've submitted a support request to fix this: http://sourceforge.net/support/?func=detailsupport&support_id=106112&group_id=1 -Fred -- Fred L. Drake, Jr. <fdrake at beopen.com> BeOpen PythonLabs Team Member
On Thu, Sep 28, 2000 at 10:25:00PM -0400, Fred L. Drake, Jr. wrote:
Trent Mick writes:
I was playing with a different SourceForge project and I screwed up my CVSROOT (used Python's instead). Sorry SOrry!
Well, you blew it. Don't worry, we'll have you kicked off SourceForge in no time! ;) Well, maybe not. I've submitted a support request to fix this:
http://sourceforge.net/support/?func=detailsupport&support_id=106112&group_id=1
Thank you Fred! Trent -- Trent Mick TrentM@ActiveState.com
"TM" == Trent Mick <trentm@ActiveState.com> writes:
TM> I was playing with a different SourceForge project and I TM> screwed up my CVSROOT (used Python's instead). Sorry SOrry! TM> How do I undo this cleanly? I could 'cvs remove' the TM> README.txt file but that would still leave the top-level TM> 'black/' turd right? Do the SourceForge admin guys have to TM> manually kill the 'black' directory in the repository? One a directory's been added, it's nearly impossible to cleanly delete it from CVS. If it's infected people's working directories, you're really screwed, because even if the SF admins remove it from the repository, it'll be a pain to clean up on the client side. Probably best thing to do is make sure you "cvs rm" everything in the directory and then just let "cvs up -P" remove the empty directory. Everybody /is/ using -P (and -d) right? :) -Barry
On Fri, Sep 29, 2000 at 02:06:33AM -0400, Barry A. Warsaw wrote:
"TM" == Trent Mick <trentm@ActiveState.com> writes:
TM> I was playing with a different SourceForge project and I TM> screwed up my CVSROOT (used Python's instead). Sorry SOrry!
TM> How do I undo this cleanly? I could 'cvs remove' the TM> README.txt file but that would still leave the top-level TM> 'black/' turd right? Do the SourceForge admin guys have to TM> manually kill the 'black' directory in the repository?
One a directory's been added, it's nearly impossible to cleanly delete it from CVS. If it's infected people's working directories, you're really screwed, because even if the SF admins remove it from the repository, it'll be a pain to clean up on the client side.
Hopefully no client machines were infected. People would have to 'cvs co black' with the Python CVSROOT. I presume people are only doing either 'cvs co python'or 'cvs co distutils'. ...or is there some sort of 'cvs co *' type invocation that people could and were using?
Probably best thing to do is make sure you "cvs rm" everything in the directory and then just let "cvs up -P" remove the empty directory. Everybody /is/ using -P (and -d) right? :)
I didn't know about -P, but I will use it now. For reference for others: -P Prune (remove) directories that are empty after being updated, on checkout, or update. Normally, an empty directory (one that is void of revision-con trolled files) is left alone. Specifying -P will cause these directories to be silently removed from your checked-out sources. This does not remove the directory from the repository, only from your checked out copy. Note that this option is implied by the -r or -D options of checkout and export. Trent -- Trent Mick TrentM@ActiveState.com
"TM" == Trent Mick <trentm@ActiveState.com> writes:
TM> Hopefully no client machines were infected. People would have TM> to 'cvs co black' with the Python CVSROOT. I presume people TM> are only doing either 'cvs co python'or 'cvs co TM> distutils'. ...or is there some sort of 'cvs co *' type TM> invocation that people could and were using? In fact, I usually only "co -d python python/dist/src" :) But if you do a "cvs up -d" at the top-level, I think you'll get the new directory. Don't know how many people that'll affect, but if you're going to wax that the directory, the soon the better! -Barry
Barry A. Warsaw writes:
One a directory's been added, it's nearly impossible to cleanly delete it from CVS. If it's infected people's working directories, you're really screwed, because even if the SF admins remove it from the repository, it'll be a pain to clean up on the client side.
In general, yes, but since the directory was a separate module (in CVS terms, "product" in SF terms), there's no way for it to have been picked up by clients automatically. -Fred -- Fred L. Drake, Jr. <fdrake at beopen.com> BeOpen PythonLabs Team Member
participants (3)
-
bwarsaw＠beopen.com -
Fred L. Drake, Jr. -
Trent Mick