www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Erenkrantz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-518) CVS corruption in jakarta-tapestry
Date Mon, 22 Aug 2005 19:54:08 GMT
    [ http://issues.apache.org/jira/browse/INFRA-518?page=comments#action_12319640 ] 

Justin Erenkrantz commented on INFRA-518:
-----------------------------------------

The corruption appears to have happened on the 19th.  Our principal backups are only daily.

There may be a backup available from July (on brutus's firewire drive).  Please consult with
Sander Temme about seeing if there's anything useful on there.  There is also the possibility
of reconstructing the CVS history from the commit mail archives.  That last option would be
rather painstaking and not something I personally have time to do.

For now, I've deleted the two zero-length files:

./framework/src/descriptor/META-INF/tapestry.asset.xml,v
./framework/src/descriptor/META-INF/tapestry.services.xml,v

You can readd them.

> CVS corruption in jakarta-tapestry
> ----------------------------------
>
>          Key: INFRA-518
>          URL: http://issues.apache.org/jira/browse/INFRA-518
>      Project: Infrastructure
>         Type: Task
>   Components: CVS
>     Reporter: Howard M. Lewis Ship
>  Attachments: tapestry.asset.xml, tapestry.services.xml
>
> Looks like a commit went bad in some way.
> I attempted to do an update and there was a locking problem.
> I (foolishly?) went ahead and deleted the lock file:
> > cd /home/cvs/jakarta-tapestry/framework/src/descriptor/META-INF/
> > ls -lag
> total 296
> drwxrwxr-x  2 hlship      jakarta    512 Aug 19 07:11 #cvs.lock
> drwxrwxr-x  4 hlship      jakarta   1024 Aug 19 07:11 .
> drwxrwxr-x  3 hlship      jakarta    512 Aug 22 06:37 ..
> drwxrwxr-x  2 hlship      jakarta    512 Jun 24 11:54 Attic
> -r--r--r--  1 hlship      jakarta  31646 Aug 10 18:40 hivemodule.xml,v
> -r--r--r--  1 hlship      jakarta      0 Aug 19 07:11 tapestry.asset.xml,v
> -r--r--r--  1 hlship      jakarta  14896 Aug 10 18:40 tapestry.bindings.xml,v
> -r--r--r--  1 mindbridge  jakarta  10789 Aug 14 03:57 tapestry.coerce.xml,v
> -r--r--r--  1 mindbridge  jakarta   5723 Aug 12 15:22 tapestry.data.xml,v
> -r--r--r--  1 hlship      jakarta   7881 Aug 10 18:40 tapestry.describe.xml,v
> -r--r--r--  1 hlship      jakarta  30472 Aug 10 18:40 tapestry.enhance.xml,v
> -r--r--r--  1 hlship      jakarta   7459 Aug 10 18:40 tapestry.error.xml,v
> -r--r--r--  1 hlship      jakarta   2444 Aug 10 18:40 tapestry.form.translator.xml,v
> -r--r--r--  1 hlship      jakarta   3509 Aug 10 18:40 tapestry.form.validator.xml,v
> -r--r--r--  1 hlship      jakarta   3049 Aug 10 18:40 tapestry.form.xml,v
> -r--r--r--  1 hlship      jakarta  13001 Aug 10 18:40 tapestry.globals.xml,v
> -r--r--r--  1 hlship      jakarta   7297 Aug 10 18:40 tapestry.init.xml,v
> -r--r--r--  1 hlship      jakarta   2598 Aug 10 18:40 tapestry.listener.xml,v
> -r--r--r--  1 hlship      jakarta   4354 Aug 10 18:40 tapestry.markup.xml,v
> -r--r--r--  1 hlship      jakarta   3593 Aug 10 18:40 tapestry.monitor.xml,v
> -r--r--r--  1 hlship      jakarta   3460 Aug 10 18:40 tapestry.multipart.xml,v
> -r--r--r--  1 hlship      jakarta   5043 Aug 10 18:40 tapestry.ognl.xml,v
> -r--r--r--  1 hlship      jakarta  18692 Aug 10 18:40 tapestry.page.xml,v
> -r--r--r--  1 hlship      jakarta   9172 Aug 10 18:40 tapestry.parse.xml,v
> -r--r--r--  1 hlship      jakarta   9005 Aug 10 18:40 tapestry.persist.xml,v
> -r--r--r--  1 hlship      jakarta  16919 Aug 10 18:40 tapestry.props.xml,v
> -r--r--r--  1 hlship      jakarta  26176 Aug 10 18:40 tapestry.request.xml,v
> -r--r--r--  1 hlship      jakarta   4065 Aug 10 18:40 tapestry.script.xml,v
> -r--r--r--  1 hlship      jakarta      0 Aug 19 07:11 tapestry.services.xml,v
> -r--r--r--  1 hlship      jakarta  11908 Aug 10 18:40 tapestry.state.xml,v
> -r--r--r--  1 hlship      jakarta  13655 Aug 10 18:40 tapestry.url.xml,v
> -r--r--r--  1 hlship      jakarta   2805 Aug 10 18:40 tapestry.valid.xml,v
> > rm -rf #cvs.lock/
> However, it appears the damage was already done:
> Error: The following warnings were reported while performing the "cvs update" command.
>    Error: jakarta-tapestry: cvs update: `/home/cvs/jakarta-tapestry/framework/src/descriptor/META-INF/tapestry.asset.xml,v'
does not appear to be a valid rcs file
>    Error: jakarta-tapestry: cvs update: `/home/cvs/jakarta-tapestry/framework/src/descriptor/META-INF/tapestry.asset.xml,v'
does not appear to be a valid rcs file
>    Error: jakarta-tapestry: cvs update: `/home/cvs/jakarta-tapestry/framework/src/descriptor/META-INF/tapestry.services.xml,v'
does not appear to be a valid rcs file
>    Error: jakarta-tapestry: cvs update: `/home/cvs/jakarta-tapestry/framework/src/descriptor/META-INF/tapestry.services.xml,v'
does not appear to be a valid rcs file
> ***
> I'll attach the correct and current versions of the two files for safe keeping.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message