[prev in list] [next in list] [prev in thread] [next in thread] 

List:       darcs-devel
Subject:    [darcs-devel] [issue1855] Unhelpful message pushing to unrelated
From:       Eric Kow <bugs () darcs ! net>
Date:       2010-05-31 14:13:17
Message-ID: 1275315197.26.0.326933254095.issue1855 () darcs ! net
[Download RAW message or body]


Eric Kow <kowey@darcs.net> added the comment:

Thanks, for the report, Simon.  I can reproduce this trying to pull from
the nofib repo into the ghc one.  (Unfortunately, when I try to push,
something weirder happens

As I understand it, this was resolved in issue1039 which implemented a
simple check for relatedness (two repositories are considered related if
they have some patches in common).

For instance: if you do
  darcs get --lazy http://darcs.net darcs
  darcs get --lazy http://code.haskell.org/darcs-benchmark
  cd darcs
  darcs push ../darcs-benchmark

What you see is this confirmation prompt:

  Repositories seem to be unrelated. Proceed? [yn]

OK, so why does this not work for the ghc/nofib case?  Unfortunately,
this is one of those situations where Darcs has been fooled by a
conversion from CVS into thinking that the two repos have patches in
common (see issue1026).

An example of these patches is:

The GHC repo
------------
Thu Apr 28 10:46:25 BST 2005  simonmar
  * [project @ 2005-04-28 09:46:25 by simonmar]
  Run each nofib program multiple times, tunable by the $(NoFibRuns)
  variable.  nofib-analyse already knows how to average the times from
  multiple runs.

    M ./mk/config.mk.in +3

The nofib repo
--------------
Thu Apr 28 10:46:25 BST 2005  simonmar
  * [project @ 2005-04-28 09:46:25 by simonmar]
  Run each nofib program multiple times, tunable by the $(NoFibRuns)
  variable.  nofib-analyse already knows how to average the times from
  multiple runs.

    M ./mk/boilerplate.mk -1
    M ./mk/target.mk -5 +10

Different patches, same name... hence the bug in get_extra.

That said, I'd also like to report that with David's NewSet work (as
adapted by Petr), the work that darcs needs to do to determine if there
are patches in common seems to succeed (Darcs asks you if you'd like to
push/pull some 20K or 400 patches respectively).  That's not necessarily
a good thing (due to false positives in patch identity).

But in any case, I think we've pretty much reached a point where we can
do no more to help.  Sorry!

----------
nosy: +kowey
priority:  -> bug
status: unknown -> duplicate
superseder: +wish: detect seemingly unrelated repositories, wish: improved advice for \
                bug in get_extra commuting patch (2.x)
title: Unhelpful meessage -> Unhelpful message pushing to unrelated repo

__________________________________
Darcs bug tracker <bugs@darcs.net>
<http://bugs.darcs.net/issue1855>
__________________________________
_______________________________________________
darcs-devel mailing list (AUTOMATIC POSTINGS ONLY PLEASE!)
darcs-devel@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-devel


[prev in list] [next in list] [prev in thread] [next in thread]