#151: AssertionError tailorizing openssl CVS history
---------------------+------------------------------------------------------
  Reporter:  zooko   |       Owner:  lele      
      Type:  defect  |      Status:  reopened  
  Priority:  major   |   Milestone:  VersionOne
 Component:  cvs     |     Version:  0.9       
Resolution:          |    Keywords:            
---------------------+------------------------------------------------------
Changes (by zooko):

  * status:  closed => reopened
  * resolution:  worksforme =>


Comment:

 I reran it, and this time it ended with:

 {{{
 22:41:25 [I] Changeset #99
 22:41:25 [I] Changeset "1998-12-30 22:58:33 by rse"
 22:41:25 [I] Log message: Cleanup of doc/ directory: The old/obsolete
 SSLeay files are now assembled
 together in a ssleay.txt file.
 22:41:25 [I] /Users/wonwinmcbrootles/playground/openssl/tailored $ cvs -f
 -d [EMAIL PROTECTED]:/openssl-cvs -q update -d -P -r 1.1
 doc/README doc/ssleay.txt
 22:41:33 [W] [Status 1]
 22:41:33 [W] /Users/wonwinmcbrootles/playground/openssl/tailored $ cvs -f
 -d [EMAIL PROTECTED]:/openssl-cvs -q update -d -P -r 1.1
 doc/README doc/ssleay.txt returned status 1, retrying in 2 seconds...
 22:41:34 [I] /Users/wonwinmcbrootles/playground/openssl/tailored $ cvs -f
 -d [EMAIL PROTECTED]:/openssl-cvs -q update -d -P -r 1.1
 doc/README doc/ssleay.txt
 22:41:37 [W] [Status 1]
 22:41:37 [W] /Users/wonwinmcbrootles/playground/openssl/tailored $ cvs -f
 -d [EMAIL PROTECTED]:/openssl-cvs -q update -d -P -r 1.1
 doc/README doc/ssleay.txt returned status 1, retrying in 4 seconds...
 22:41:39 [I] /Users/wonwinmcbrootles/playground/openssl/tailored $ cvs -f
 -d [EMAIL PROTECTED]:/openssl-cvs -q update -d -P -r 1.1
 doc/README doc/ssleay.txt
 22:41:43 [W] [Status 1]
 22:41:43 [W] /Users/wonwinmcbrootles/playground/openssl/tailored $ cvs -f
 -d [EMAIL PROTECTED]:/openssl-cvs -q update -d -P -r 1.1
 doc/README doc/ssleay.txt returned status 1, retrying in 8 seconds...
 22:41:46 [I] /Users/wonwinmcbrootles/playground/openssl/tailored $ cvs -f
 -d [EMAIL PROTECTED]:/openssl-cvs -q update -d -P -r 1.1
 doc/README doc/ssleay.txt
 22:41:49 [W] [Status 1]
 22:41:49 [C] Couldn't apply changeset
 22:41:51 [C] Upstream change application failed
 Traceback (most recent call last):
   File "/usr/local/bin/tailor", line 8, in <module>
     load_entry_point('tailor==0.9.32', 'console_scripts', 'tailor')()
   File "/usr/local/stow/python-release25-maint-2008-05-15/lib/python2.5
 /site-packages/tailor-0.9.32-py2.5.egg/vcpx/tailor.py", line 342, in main
     tailorizer()
   File "/usr/local/stow/python-release25-maint-2008-05-15/lib/python2.5
 /site-packages/tailor-0.9.32-py2.5.egg/vcpx/tailor.py", line 147, in
 __call__
     self.update()
   File "/usr/local/stow/python-release25-maint-2008-05-15/lib/python2.5
 /site-packages/tailor-0.9.32-py2.5.egg/vcpx/tailor.py", line 111, in
 update
     applyable=self._applyable, applied=self._applied)
   File "/usr/local/stow/python-release25-maint-2008-05-15/lib/python2.5
 /site-packages/tailor-0.9.32-py2.5.egg/vcpx/dualwd.py", line 97, in
 applyPendingChangesets
     applied=applied)
   File "/usr/local/stow/python-release25-maint-2008-05-15/lib/python2.5
 /site-packages/tailor-0.9.32-py2.5.egg/vcpx/source.py", line 113, in
 applyPendingChangesets
     res = self._applyChangeset(c)
   File "/usr/local/stow/python-release25-maint-2008-05-15/lib/python2.5
 /site-packages/tailor-0.9.32-py2.5.egg/vcpx/repository/cvsps.py", line
 373, in _applyChangeset
     cvsup.exit_status))
 vcpx.source.ChangesetApplicationFailure:
 /Users/wonwinmcbrootles/playground/openssl/tailored $ cvs -f -d
 [EMAIL PROTECTED]:/openssl-cvs -q update -d -P -r 1.1 doc/README
 doc/ssleay.txt returned status 1

 real    44m25.880s
 user    2m59.802s
 sys     1m51.117s
 }}}

-- 
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/151#comment:4>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor

Reply via email to