darcs

Issue 2542 No patch gets created after sending a bundle

Title No patch gets created after sending a bundle
Priority Status unknown
Milestone Resolved in
Superseder Nosy List bf
Assigned To
Topics

Created on 2017-08-07.14:35:32 by bf, last changed 2017-08-07.14:45:24 by gh.

Messages
msg19509 (view) Author: bf Date: 2017-08-07.14:35:29
The bug tracker does not generate a new patch entry when I send a
bundle. Sending says it is successful:

franksen@tiber: ...src/darcs/clean > darcs send
Creating patch to "http://darcs.net/screened"...
Patch bundle will  be sent to: patches@darcs.net
patch bb6b39ea7dd2852cab5ea5a88713492a8892c78a
Author: Ben Franksen <benjamin.franksen@helmholtz-berlin.de>
Date:   Fri Jul 28 13:44:54 CEST 2017
  * remove matchAPatchread and replace its use with matchAPatch
  
  matchAPatchread did exactly the same thing as matchAPatch and had an ugly
  name, too.
Shall I send this patch? (1/3)  [ynW...], or ? for more options: n
patch 6c5d5b7ec2ce1cf805e489d02279412c739ed2a4
Author: Ben Franksen <ben.franksen@online.de>
Date:   Thu Apr 27 18:38:13 CEST 2017
  * plugging memory leak in annotate
Shall I send this patch? (2/3)  [ynW...], or ? for more options: y
patch 5ab1a2344812c29660ef4c6a6267f3a55a637d9f
Author: Ben Franksen <ben.franksen@online.de>
Date:   Fri Apr 28 16:55:39 CEST 2017
  * improve efficiency of annotate
  
  The patch index makes finding the relevant patches quite efficient,
but when
  a patch contains many hunks, the previous implementation took a very long
  time to finish. This was because it naively applied every hunk and
then used
  diff to see which lines were changed.
  
  The new implementation directly observes the effect of patches on the
  Annotated structure using the new Annotate patch interface (type class).
  This also makes attribution of lines to patches more accurate, since the
  result no longer depends on the diff algorithm that annotate used
  internally.
Shall I send this patch? (3/3)  [ynW...], or ? for more options: y
Do you want to Send these patches? [Yglqk...], or ? for more options: y
Minimizing context, to send with full context hit ctrl-C...

You need a passphrase to unlock the secret key for
user: "Ben Franksen <ben.franksen@online.de>"
4096-bit RSA key, ID E7B29005, created 2012-03-06


You need a passphrase to unlock the secret key for
user: "Ben Franksen <ben.franksen@online.de>"
4096-bit RSA key, ID E7B29005, created 2012-03-06

gpg: encrypted with 4096-bit RSA key, ID E7B29005, created 2012-03-06
      "Ben Franksen <ben.franksen@online.de>"
Successfully sent patch bundle to: patches@darcs.net and cc'ed
benjamin.franksen@helmholtz-berlin.de.
msg19510 (view) Author: gh Date: 2017-08-07.14:45:23
Hi Ben,

I also realized this was happening a couple of weeks ago.

Until this is fixed (I think Ganesh knows how but he does not have a
lot of time), let us manually create patch entries on the bug
tracker...


I just realized that also replying by mail to this issue did no longer
work... let us try and use more IRC.

Guillaume
History
Date User Action Args
2017-08-07 14:35:32bfcreate
2017-08-07 14:45:24ghsetmessages: + msg19510