Opened 10 years ago

Closed 9 years ago

#1193 closed defect (invalid)

[invalid] Can't apply patches under VMware

Reported by: jvoight Owned by: cwitty
Priority: minor Milestone: sage-2.10.4
Component: misc Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:


When I attempt to apply a patch under VMware, I get an error:

    ret = _runcommand(ui, options, cmd, d)
  File "/usr/local/sage/local/lib/python2.5/mercurial/", line 401, in
    return checkargs()
  File "/usr/local/sage/local/lib/python2.5/mercurial/", line 357, in
    return cmdfunc()
  File "/usr/local/sage/local/lib/python2.5/mercurial/", line 340, in
    d = lambda: func(ui, repo, *args, **cmdoptions)
  File "/usr/local/sage/local/lib/python2.5/mercurial/", line 2691, i
n unbundle
    modheads = repo.addchangegroup(gen, 'unbundle', 'bundle:', + fname)
  File "/usr/local/sage/local/lib/python2.5/mercurial/", line 1849, 
in addchangegroup
    if cl.addgroup(chunkiter, csmap, trp, 1) is None:
  File "/usr/local/sage/local/lib/python2.5/mercurial/", line 1201, in
    ifh, dfh)
  File "/usr/local/sage/local/lib/python2.5/mercurial/", line 1026, in
    ptext = self.revision(self.node(prev))
  File "/usr/local/sage/local/lib/python2.5/mercurial/", line 948, in r
    text = mdiff.patches(text, bins)
mpatch.mpatchError: invalid patch

This occurred most recently when I applied Yi's latest DSage patch, but it occurs even when I make a patch recording a trivial modification to a file.

(Shouldn't there be a "mercurial" component in the drop-down below?)

Change History (5)

comment:1 Changed 10 years ago by mabshoff

  • Milestone set to sage-2.8.13

comment:2 Changed 9 years ago by mabshoff

  • Summary changed from Can't apply patches under VMware to [probably invalid] Can't apply patches under VMware

I believe this is a permission issue, so not really a bug on our end.



comment:3 Changed 9 years ago by was

The error message suggests corruption of the patch file itself.

comment:4 Changed 9 years ago by rlm

  • Milestone changed from sage-2.11 to sage-2.10.4

comment:5 Changed 9 years ago by jvoight

  • Resolution set to invalid
  • Status changed from new to closed
  • Summary changed from [probably invalid] Can't apply patches under VMware to [invalid] Can't apply patches under VMware

Whatever was causing the problem so very long ago is no longer--I checked and can now apply patches. JV

Note: See TracTickets for help on using tickets.