eclipsedarcs-develop — Development discussion

Re: [eclipsedarcs-develop] Push All operation refactoring + Send All Fix.

[<rad...@gm...>]

2007/3/20, Leif Frenzel <lei...@go...>:
> Hi Radek,
>
>
> > What I was thinking while implementing this page was to have
> > repository attached with given project. This is not supported by
> > RepositoryLocationManager as far as I understand it. Moreover I'm not
> > sure does it make much sense to have repos for projects only.
> >
> > What do you think? Should we care and support such a feature or do we
> > use global repo locations everywhere? If we support it then I think
> > IDarcsRepository should have link to Projects (if attached to one) and
> > RepositoryLocationManager should have the ability to search repos for
> > given project. Right? I don't think that is very hard to do...
> I think having repos globally simplifies things.
>
> Also, I think to associate them is very easy. Every project has a repository
> provider attached to it, if it is shared with Darcs. From that, it can be
> determined to which repo a project belongs (that is for instance what the
> [Right-click project] > Darcs repo > Browse action does. It checks with
> which repo the project is shared, and then opens that repo in the Darcs
> Browsing perspective (or creates it there, if it is not yet there). That's a
> feature I use quite often, btw. ;-)

Yes, but this is one (project) to one (repo) mapping (Correct me if
I'm talking rubbish). What I was thinking was one (project) to many
(repos) mapping.
Let's say I change my code, and from time to time I push to my own
branch. Now I want to create patch against (or push to or whatever)
main repository - I would have to have two repositories attached to
one project.

But anyway, I agree to use global list. It is not an issue for me.

> > Also, what do we do with pop-up menu for project? I think that we
> > should either move everything to "Darcs Repository" or back to "Team"
> > menu. I don't think we should keep it mixed like it is right now for
> > 0.4 release which is coming soon I think. :D Will you take a look at
> > it?
> Yes, I'll try it out again. My suspicion is, however, that there is a bug in
> the menu handling in Eclipse. I have found it not possible to have submenus
> under 'Team'. If that is actually so, there might be a chance that it will
> be fixed in Eclipse 3.3, however.

Great!


  Cheers,
  Radek.

Re: [eclipsedarcs-develop] Push All operation refactoring + Send All Fix.

[<rad...@gm...>]

Hi Leif,

> :-) Here's what I did: I run a runtime-workbench with some repo that has a
> few patches. I created a second local repo in a folder. Then I went to the
> project properties page, selected 'Darcs', and added a new repo location, by
> just entering something like 'C:\temp\blarepo'. That gave me the yellow
> warning icon, and the push operation didn't work, so I inferred I had done
> something wrong with the location. I played around a bit, and finally
> entering a URI worked.

Ahh.. This one. I totally forgot about it. It is however flawed and I
will probably remove it.
What I was thinking while implementing this page was to have
repository attached with given project. This is not supported by
RepositoryLocationManager as far as I understand it. Moreover I'm not
sure does it make much sense to have repos for projects only.

What do you think? Should we care and support such a feature or do we
use global repo locations everywhere? If we support it then I think
IDarcsRepository should have link to Projects (if attached to one) and
 RepositoryLocationManager should have the ability to search repos for
given project. Right? I don't think that is very hard to do...

Also, what do we do with pop-up menu for project? I think that we
should either move everything to "Darcs Repository" or back to "Team"
menu. I don't think we should keep it mixed like it is right now for
0.4 release which is coming soon I think. :D Will you take a look at
it?

Cheers!
  Radek.

Re: [eclipsedarcs-develop] Ssh repositories support

[<rad...@gm...>]

MjAwNy8zLzE5LCBSYWRvc8WCYXcgR3J6YW5rYSA8cmFkb3NsYXdnQGdtYWlsLmNvbT46Cj4gSGks
Cj4gICBJIGhhdmUgYWRkZWQgc3VwcG9ydCBmb3IgU1NIIHJlcG9zaXRvcmllcyBpbiBEYXJjcyBQ
ZXJzcGVjdGl2ZS4KPiBGZXRjaGluZyBDaGFuZ2VzIHdvcmtzIG9uIHdpbmRvd3MsIG9ubHkgaWYg
eW91IHVzZSBsYXRlc3QgZGFyY3MKPiAxLjAuOXJjMiAhISBUaGF0IGlzIGJlY2F1c2UgZWFybGll
ciB2ZXJzaW9ucyBzcGl0cyBzb21lIG91dHB1dCB0bwo+IGVycm9yIGNoYW5uZWwuIDovCgpBbm90
aGVyIG5vdGUgaXM6IHlvdSBoYXZlIHRvIGhhdmUgcGFzc3dvcmRsZXNzIHNzaCBhY2Nlc3MgY29u
ZmlndXJlZApvciBlbHNlIGl0IHdpbGwgaGFuZyEgSSBkb24ndCBrbm93IHdoYXQgdG8gZG8gd2l0
aCBpdC4KCkNoZWVycywKICBSYWRlay4K

[eclipsedarcs-develop] Ssh repositories support

[<rad...@gm...>]

Hi,
  I have added support for SSH repositories in Darcs Perspective.
Fetching Changes works on windows, only if you use latest darcs
1.0.9rc2 !! That is because earlier versions spits some output to
error channel. :/

Attached file is zip archive.

Also, I've made this a little bit hasty so some testing is required.

Cheers,
  Radek.

-- 
Galeria/Gallery: http://zdjecia.zuzia.homelinux.net/
Codeside: http://codeside.org/

Re: [eclipsedarcs-develop] Fix for Flyspray #11

[<rad...@gm...>]

2007/3/18, Leif Frenzel <lei...@go...>:
>
> > Doesn't that mean that we should not worry about it at all? We don't
> > need to put any text at the end of the file. Or do we?
> We had to, at that time at least. (I'm so lazy, I don't hink I would have
> added that line if it had worked without ;-).
>
>
> > Time showed that putting there anything may in future result in
> > another changed comment. This is temp file, completly under our
> > command without user interaction with it, darcs accept it and
> > correctly parse it without any termination text.
> I'm absolutely not opposed to that, if it works :-)
>
> Cool, so I'll run a few checks on that too, and push it through.


I forgot to add that someone (presumably you :) ) should check this
long comment fix on windows as I am checking it only on Linux right
now.

Re: [eclipsedarcs-develop] Fix for Flyspray #11

[<rad...@gm...>]

2007/3/18, Leif Frenzel <lei...@go...>:
>
> >
> >
> > >
> > > > The ***DARCS*** Line is explicitly added in
> > > > RecordOperation.prepareLogFile () method. I was about to remove it
> > > > anyway as I thought this was some kind of debug.
> >
> > If I remember correcty, it was deliberate. I was mimicking the thing that
> Darcs does when it calls an external editor for the long comment. But it
> seems that this works now different, or strictly speaking, they use now
> '***END OF DESCRIPTION***' instead of '***DARCS***'.
> >
> > Hm, I suspect that was a change between some earlier Darcs version and
> 1.0.8.
> >
> > But that would mean that we have to change our code to '***END OF
> DESCRIPTION***' and declare explicitely that Darcs 1.0.8 should be used with
> EclipseDarcs, right?
> Hm, I verified, with Darcs 1.0.2 it's '***DARCS***'. It's '***END OF
> DESCRIPTION***' with Darcs 1.0.5RC1, I haven't checked the versions in
> between.
>
> Wow, it's always a bit frightening how time flies ;-)
>
> So this means we don't have to worry. We should be able to simply use
> '***END OF DESCRIPTION***'.

Doesn't that mean that we should not worry about it at all? We don't
need to put any text at the end of the file. Or do we?

Time showed that putting there anything may in future result in
another changed comment. This is temp file, completly under our
command without user interaction with it, darcs accept it and
correctly parse it without any termination text.

Cheers!
  Radek.

Re: [eclipsedarcs-develop] Fix for Flyspray #11

[<rad...@gm...>]

Hi

> The ***DARCS*** Line is explicitly added in
> RecordOperation.prepareLogFile() method. I was about to remove it
> anyway as I thought this was some kind of debug.

Here comes the patch.

Thanks,
  Radek.

Re: [eclipsedarcs-develop] Fix for Flyspray #11

[<rad...@gm...>]

2007/3/18, Leif Frenzel <lei...@go...>:
> On 3/18/07, Leif Frenzel <lei...@go...> wrote:
> >
> >
> > > It turns out it is because usage of quote (") characters in darcs
> > > invocation. If I use
> > >
> > > createNameValueParam( PARAM_LOGFILE, logFile.toString() ) ;
> > >
> > > instead of
> > >
> > > createNameQuotedValueParam( PARAM_LOGFILE, logFile.toString() ) ;
> > >
> > > everything works ok. Any ideas why? Is it safe to substitute it? Anyone?
> >
> > I'd say so. But I will do some safety checks.
> Hm, looks good to me.
>
>
> >
> >
> > Btw: there is some other thing that I noticed: if one does a record with a
> long comment, at least under Windows, and one does _not_ do a line break at
> the end, the comment gets screwed up in the Darcs changes output. I'll have
> a look at that and perhaps get it fixed at the same time :-)
> Strange enough, this happens also if one _does_ enter a line break. Any long
> comment gets a '***DARCS***' appended. E.g.
>
> [snip]
> C:\temp\junk\edws\test>darcs changes --last=3
> Sun Mar 18 11:18:07 Westeurop[_\e4_]ische Normalzeit 2007  Leif Frenzel
> <lfr...@in...>
>   * 1174213086703
>
> Sun Mar 18 11:16:57 Westeurop[_\e4_]ische Normalzeit 2007  Leif Frenzel <
> lfr...@in...>
>   * 1174213013109
>   a
>   ***DARCS***
>
> Sun Mar 18 11:16:07 Westeurop[_\e4_]ische Normalzeit 2007  Leif Frenzel <
> lfr...@in...>
>   * test
>   test long comment
>
>   ***DARCS***
> [snap]
>
> This has not happened earlier, so it must have sneaked in somewhere in the
> past. Do you see the same effect on Linux?
>

The ***DARCS*** Line is explicitly added in
RecordOperation.prepareLogFile() method. I was about to remove it
anyway as I thought this was some kind of debug.

Cheers!
  Radek.

-- 
Galeria/Gallery: http://zdjecia.zuzia.homelinux.net/
Codeside: http://codeside.org/

Re: [eclipsedarcs-develop] Fix for Flyspray #11

[<rad...@gm...>]

Hi,

> > So I assume this different kind of magic.
> >
> > Invocation from command line gives:
> >
> > $ darcs record
> --repodir=/home/radekg/private/runtime-EclipseApplication/TestProject
> > --all --patch-name=Name with space --skip-long-comment aaaaaaa.java
> >
> > Recording changes in "aaaaaaa.java":
> >
> > Non existent files or directories: "space" "with"
> Strange. So this actually has to do with the difference between the
> invocation from the shell and the invocation from the Java process.
>
> I would have to check this, but don't we call Runtime.exec() with a string
> array instead of just one single string? That would also explain why 'Name
> with space' is treated as a single string and not parsed into different
> arguments, if we assume that our array looks like this:
>
> [ ..., "--all", "--patch-name=Name with space", "--skip-long-comment", ... ]

Bingo this time. :)

Cheers,
  Radek.

Re: [eclipsedarcs-develop] Fix for Flyspray #11

[<rad...@gm...>]

> > darcs record
> --repodir=/home/radekg/private/runtime-EclipseApplication/TestProject
> > --all --patch-name=Name with space --skip-long-comment aaaaaaa.java
> >
> > and it worked. So it seems quotes are not necsessary.
> Perfect timing - as it happens, I have just written up a basic tutorial on
> handling command line options in Haskell. (Will post it to my blog during
> the next few hours.) So I don't know for sure, but I have an idea why this
> works.
>
> The getOpts mechanism in Haskell (which is presumably used by Darcs)
> recognizes options when they start, as usual, with a single or double dash.
> It may well be that the entire part between --patch-name and
> --skip-long-comment is just recognized as a single string and passed to the
> program as argument to --patch-name. The mechanism can know this because
> there is a defined option (namely, --skip-long-comment) after it, so it is
> known where the string ends. If, on the other hand, --patch-name were the
> last argument, then it would look as if only the first word, i.e. 'Name' is
> an argument to --patch-name, and the rest are individual other options.

That would be perfect explanation except it does not work from command
line. :) So I assume this different kind of magic.

Invocation from command line gives:

$ darcs record --repodir=/home/radekg/private/runtime-EclipseApplication/TestProject
--all --patch-name=Name with space --skip-long-comment aaaaaaa.java

Recording changes in "aaaaaaa.java":

Non existent files or directories: "space" "with"

Cheers!
  Radek.

Re: [eclipsedarcs-develop] Push All operation refactoring + Send All Fix.

[<rad...@gm...>]

2007/3/17, Leif Frenzel <lei...@go...>:
> Hi Radek,
>
> this looks cool already :-) I'm having a few troubles under Windows, mostly
> related to file paths etc. I think I will try to fix them myself and send
> you a patch so that you can verify they don't break anything under Linux ;-)
>
> Here are a few more suggestions:
>
> - I think it generally hard to see what one has to enter for a repo location
> (seems it must be a valid URI, but I only figured that out because I saw the
> stacktraces when something went wrong ;-). So I think it would be good if we
> could re-use the repo selection dialog from the browser perspective, where
> the user can browse to a folder and it is converted to a URI in the
> background.

To which dialog window are you refering? I don't recall any, where
user can enter his own repository address

I was about to refine Push/Pull/Send Dialog to allow user to write
address of custom repository and refactor them as they seem to share
much in common.

However, there is a problem with validating indeed. One option is like
you suggested but I don't know how to solve ssh address validation.
IIRC URI for ssh is too complicated to request from user. Ideally I
would like to be able to specify repo address as darcs expects.

> - There is a yellow warning icon for an invalid repo location. Maybe we
> should have some warning message also that gives a bit more info? (E.g.
> 'blablabla is not a valid repo location' or 'blablabla does not exist' or
> something like that)

Are you sure you checked plugin with my patches? I think this icon and
validation is no more. If I missed something then please point me to
it. (I know I am sometimes absent minded)

> - Very minor: on the push-all dialog, I think I would actually prefer if the
> text says 'darcs --all' instead of 'darcs -a'. That would be easier to
> understand to users who don't know the command line interface, because it is
> more speaking.

Yes, agreed.

> I think also that it will help if there is a possibility to copy the repo
> URI from an existing location (in the repo browser). That's not very
> difficult to do. (I'm thinking of something like the Properties dialog that
> the CVS browsing perspective has on CVS repo locations, plus perhaps a
> similar 'Copy to clipboard' action as they do have.) I think I can do that
> in the next days, which will probably also be a good warm-up exercise for
> me, to get oriented about the code base again :-)

What I am working right now on is specifying custom repo location in
Push/Pull and Send dialogs. This will make Eclipsedarcs complete
replacement for command line for me. :)

Next thing there will be small feature either in darcs or in
Eclipsedarcs - to create compressed output from send command. This
shouldn't be complicated. And would be very helpful for me.

Cheers,
  Radek.

[eclipsedarcs-develop] Fix for Flyspray #11

[<rad...@gm...>]

Hi,
  I will rewrite what I have written in bug comment:

It turns out it is because usage of quote (") characters in darcs
invocation. If I use

createNameValueParam( PARAM_LOGFILE, logFile.toString() ) ;

instead of

createNameQuotedValueParam( PARAM_LOGFILE, logFile.toString() ) ;

everything works ok. Any ideas why? Is it safe to substitute it? Anyone?

Moreover I was surprised that record worked if patch short name
contained space. i.e. darcs invocation looked like this:

darcs record --repodir=/home/radekg/private/runtime-EclipseApplication/TestProject
--all --patch-name=Name with space --skip-long-comment aaaaaaa.java

and it worked. So it seems quotes are not necsessary.

I am attaching patch.

Cheers!
  Radek.

-- 
Galeria/Gallery: http://zdjecia.zuzia.homelinux.net/
Codeside: http://codeside.org/

Re: [eclipsedarcs-develop] Push All operation refactoring + Send All Fix.

[Leif F. <lei...@go...>]

SGkgUmFkZWssCgp0aGlzIGxvb2tzIGNvb2wgYWxyZWFkeSA6LSkgSSdtIGhhdmluZyBhIGZldyB0
cm91YmxlcyB1bmRlciBXaW5kb3dzLCBtb3N0bHkKcmVsYXRlZCB0byBmaWxlIHBhdGhzIGV0Yy4g
SSB0aGluayBJIHdpbGwgdHJ5IHRvIGZpeCB0aGVtIG15c2VsZiBhbmQgc2VuZAp5b3UgYSBwYXRj
aCBzbyB0aGF0IHlvdSBjYW4gdmVyaWZ5IHRoZXkgZG9uJ3QgYnJlYWsgYW55dGhpbmcgdW5kZXIg
TGludXggOy0pCgpIZXJlIGFyZSBhIGZldyBtb3JlIHN1Z2dlc3Rpb25zOgoKLSBJIHRoaW5rIGl0
IGdlbmVyYWxseSBoYXJkIHRvIHNlZSB3aGF0IG9uZSBoYXMgdG8gZW50ZXIgZm9yIGEgcmVwbyBs
b2NhdGlvbgooc2VlbXMgaXQgbXVzdCBiZSBhIHZhbGlkIFVSSSwgYnV0IEkgb25seSBmaWd1cmVk
IHRoYXQgb3V0IGJlY2F1c2UgSSBzYXcgdGhlCnN0YWNrdHJhY2VzIHdoZW4gc29tZXRoaW5nIHdl
bnQgd3JvbmcgOy0pLiBTbyBJIHRoaW5rIGl0IHdvdWxkIGJlIGdvb2QgaWYgd2UKY291bGQgcmUt
dXNlIHRoZSByZXBvIHNlbGVjdGlvbiBkaWFsb2cgZnJvbSB0aGUgYnJvd3NlciBwZXJzcGVjdGl2
ZSwgd2hlcmUKdGhlIHVzZXIgY2FuIGJyb3dzZSB0byBhIGZvbGRlciBhbmQgaXQgaXMgY29udmVy
dGVkIHRvIGEgVVJJIGluIHRoZQpiYWNrZ3JvdW5kLgoKLSBUaGVyZSBpcyBhIHllbGxvdyB3YXJu
aW5nIGljb24gZm9yIGFuIGludmFsaWQgcmVwbyBsb2NhdGlvbi4gTWF5YmUgd2UKc2hvdWxkIGhh
dmUgc29tZSB3YXJuaW5nIG1lc3NhZ2UgYWxzbyB0aGF0IGdpdmVzIGEgYml0IG1vcmUgaW5mbz8g
KEUuZy4KJ2JsYWJsYWJsYSBpcyBub3QgYSB2YWxpZCByZXBvIGxvY2F0aW9uJyBvciAnYmxhYmxh
YmxhIGRvZXMgbm90IGV4aXN0JyBvcgpzb21ldGhpbmcgbGlrZSB0aGF0KQoKLSBWZXJ5IG1pbm9y
OiBvbiB0aGUgcHVzaC1hbGwgZGlhbG9nLCBJIHRoaW5rIEkgd291bGQgYWN0dWFsbHkgcHJlZmVy
IGlmIHRoZQp0ZXh0IHNheXMgJ2RhcmNzIC0tYWxsJyBpbnN0ZWFkIG9mICdkYXJjcyAtYScuIFRo
YXQgd291bGQgYmUgZWFzaWVyIHRvCnVuZGVyc3RhbmQgdG8gdXNlcnMgd2hvIGRvbid0IGtub3cg
dGhlIGNvbW1hbmQgbGluZSBpbnRlcmZhY2UsIGJlY2F1c2UgaXQgaXMKbW9yZSBzcGVha2luZy4K
CkkgdGhpbmsgYWxzbyB0aGF0IGl0IHdpbGwgaGVscCBpZiB0aGVyZSBpcyBhIHBvc3NpYmlsaXR5
IHRvIGNvcHkgdGhlIHJlcG8KVVJJIGZyb20gYW4gZXhpc3RpbmcgbG9jYXRpb24gKGluIHRoZSBy
ZXBvIGJyb3dzZXIpLiBUaGF0J3Mgbm90IHZlcnkKZGlmZmljdWx0IHRvIGRvLiAoSSdtIHRoaW5r
aW5nIG9mIHNvbWV0aGluZyBsaWtlIHRoZSBQcm9wZXJ0aWVzIGRpYWxvZyB0aGF0CnRoZSBDVlMg
YnJvd3NpbmcgcGVyc3BlY3RpdmUgaGFzIG9uIENWUyByZXBvIGxvY2F0aW9ucywgcGx1cyBwZXJo
YXBzIGEKc2ltaWxhciAnQ29weSB0byBjbGlwYm9hcmQnIGFjdGlvbiBhcyB0aGV5IGRvIGhhdmUu
KSBJIHRoaW5rIEkgY2FuIGRvIHRoYXQKaW4gdGhlIG5leHQgZGF5cywgd2hpY2ggd2lsbCBwcm9i
YWJseSBhbHNvIGJlIGEgZ29vZCB3YXJtLXVwIGV4ZXJjaXNlIGZvcgptZSwgdG8gZ2V0IG9yaWVu
dGVkIGFib3V0IHRoZSBjb2RlIGJhc2UgYWdhaW4gOi0pCgpUaGFua3MgJiYgY2lhbywKTGVpZgoK
T24gMy8xNC8wNywgUmFkb3OzYXcgR3J6YW5rYSA8cmFkb3NsYXdnQGdtYWlsLmNvbT4gd3JvdGU6
Cj4KPiBIaSwKPiAgIGhlcmUgY29tZXMgcGF0Y2hlcyBmb3IgUHVzaCBBbGwgb3BlcmF0aW9uLiBJ
dCB3b3JrcyBub3cgKGlmIHlvdQo+IHNlbGVjdCAibGFzdCByZXBvc2l0b3J5Li4uIikuCj4KPiBB
bHNvIHRoZXJlIGlzIHRyaXZpYWwgZXJyb3IgaW4gdmFsaWRhdGluZyBTZW5kQWxsIERpYWxvZyB3
aGljaAo+IGJhc2ljYWxseSBwcmV2ZW50ZWQgaXQgZnJvbSB3b3JraW5nLgo+Cj4gQXR0YWNoZWQg
ZmlsZSBpcyB6aXAgZmlsZS4KPgo+IFdlZCBNYXIgMTQgMTQ6MTk6NDkgW19cOGNfXXJvZGtvd29l
dXJvcGVqc2tpIGN6YXMgc3RhbmQuIDIwMDcKPiBSYWRvc2xhdyBHcnphbmthIDxyYWRvc2xhd2dA
Z21haWwuY29tPgo+ICAgKiBUcml2aWFsIGVycm9yIGluIHZhbGlkYXRpbmcgU2VuZCBBbGwgRGlh
bG9nLgo+Cj4gV2VkIE1hciAxNCAxNDoxNToxOSBbX1w4Y19dcm9ka293b2V1cm9wZWpza2kgY3ph
cyBzdGFuZC4gMjAwNwo+IFJhZG9zbGF3IEdyemFua2EgPHJhZG9zbGF3Z0BnbWFpbC5jb20+Cj4g
ICAqIFB1bGwgQWxsIERpYWxvZyBmaXguCj4KPiBXZWQgTWFyIDE0IDE0OjE1OjAxIFtfXDhjX11y
b2Rrb3dvZXVyb3BlanNraSBjemFzIHN0YW5kLiAyMDA3Cj4gUmFkb3NsYXcgR3J6YW5rYSA8cmFk
b3NsYXdnQGdtYWlsLmNvbT4KPiAgICogUHVzaCBBbGwgRGlhbG9nIHJlZmFjdG9yaW5nLgo+Cj4g
V2VkIE1hciAxNCAxNDoxNDoyMCBbX1w4Y19dcm9ka293b2V1cm9wZWpza2kgY3phcyBzdGFuZC4g
MjAwNwo+IFJhZG9zbGF3IEdyemFua2EgPHJhZG9zbGF3Z0BnbWFpbC5jb20+Cj4gICAqIFB1c2gg
QWxsIE9wZXJhdGlvbiByZWZhY3RvcmluZyB0byBlbXBsb3kgKkluZm8gbW9kZWwuCj4KPgo+IENo
ZWVycywKPiAgIFJhZGVrLgo+Cj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+IFRha2UgU3VydmV5cy4gRWFy
biBDYXNoLiBJbmZsdWVuY2UgdGhlIEZ1dHVyZSBvZiBJVAo+IEpvaW4gU291cmNlRm9yZ2UubmV0
J3MgVGVjaHNheSBwYW5lbCBhbmQgeW91J2xsIGdldCB0aGUgY2hhbmNlIHRvIHNoYXJlCj4geW91
cgo+IG9waW5pb25zIG9uIElUICYgYnVzaW5lc3MgdG9waWNzIHRocm91Z2ggYnJpZWYgc3VydmV5
cy1hbmQgZWFybiBjYXNoCj4gaHR0cDovL3d3dy50ZWNoc2F5LmNvbS9kZWZhdWx0LnBocD9wYWdl
PWpvaW4ucGhwJnA9c291cmNlZm9yZ2UmQ0lEPURFVkRFVgo+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gZWNsaXBzZWRhcmNzLWRldmVsb3AgbWFpbGlu
ZyBsaXN0Cj4gZWNsaXBzZWRhcmNzLWRldmVsb3BAbGlzdHMuc291cmNlZm9yZ2UubmV0Cj4gaHR0
cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vZWNsaXBzZWRhcmNzLWRl
dmVsb3AKPgo+Cj4KCgotLSAKTGVpZiBGcmVuemVsCmh0dHA6Ly9sZWlmZnJlbnplbC5kZQpodHRw
Oi8vY29oYXRvZS5ibG9nc3BvdC5jb20K

Re: [eclipsedarcs-develop] Release of version 0.2.4

[Marius K. <am...@gm...>]

aGkgcGVvcGxlcywKCmRvbid0IHN3ZWFyIG1lIGFueW9uZSBidXQsCmhhdmUgeW91IHRyaWVkIGJh
emFhcj8KaHR0cDovL2JhemFhci12Y3Mub3JnCkkgbG92ZSBpdCwgYW5kIGl0IGlzIGFsc28gZGlz
dHJpYnV0ZWQgYW5kIHN1cHBvcnRzIHlvdXIgd2VpcmQgd29ya2Zsb3cKcHJldHR5IG5pY2VseS4K
CnJlZ2FyZHMKTWFyaXVzCgoKT24gMy85LzA3LCBSYWRvc7NhdyBHcnphbmthIDxyYWRvc2xhd2dA
Z21haWwuY29tPiB3cm90ZToKPgo+IEhpLAo+Cj4gPiBCdXQgaW4gZ2VuZXJhbCwgSSdkIHNheSB0
aGF0IERhcmNzIGlzIHF1aXRlIHdlbGwgc3VpdGVkIGZvciB1c2UuIChBbmQgd2UKPiA+IHNob3Vs
ZCBrZWVwIGluIG1pbmQgdGhhdCB0aGVyZSBhcmUgcHJvYmxlbXMgd2l0aCBDVlMgb3IgU1ZOIG9y
IHdoYXRldmVyCj4gPiBvdGhlciBzeXN0ZW1zLCB0b28gOi0pCj4KPiBNeSBtYWluIG1vdGl2YXRp
b24gYmVoaW5kIHN3aXRjaGluZyBWQ1MgZnJvbSBTVk4gdG8gRGFyY3MgaXMKPiBicmFuY2hpbmcu
IFdlIGhhdmUgcXVpdGUgY29tcGxpY2F0ZWQgd29yayBtb2RlbC4gVGhlcmUgYXJlIHR3byB0ZWFt
cwo+IHRoYXQgZG9lcyBhIHdvcmsgb24gb25lIGNvZGUgYmFzZSB3aGljaCBhcmUgYnJhbmNoZWQg
YW5kIHN5bmNocm9uaXplZAo+IG9uY2UgaW4gYSB3aGlsZS4gQWxzbyB0aGVyZSBpcyAicHJvZHVj
dGlvbiIgYnJhbmNoLiBOb3csIG1lcmdpbmcKPiBjaGFuZ2VzIGJldHdlZW4gdGVhbXMgYW5kIHRo
ZW4gdXBsb2FkaW5nIHNlbGVjdGVkIHBhdGNoZXMgdG8gdGhlCj4gcHJvZHVjdGlvbiBjb2RlIHdp
dGggU1ZOIGlzIE5JR0hUTUFSRS4gTm8gaGVscCBmcm9tIHRoZSBzeXN0ZW0KPiB3aGF0c29ldmVy
LiBBbHNvIHRoaXMgcmVwb3NpdG9yeSBpcyBwcmV0dHkgbGFyZ2UuCj4KPiBFaXRoZXIgd2Ugc3dp
dGNoIFZDUyBvciB3b3JrIG1vZGVsLgo+Cj4gVGhhbmtzIGFnYWluLAo+IFJhZGVrLgo+Cj4gLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCgoKCi0tIAoKCgpJIGNvZGUg
dGhlcmVmb3JlIEkgYW0uCg==

Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs repo

[Kauker, H. <Hub...@tr...>]

Leif,

 

for the record only: when that 404 message came, nothing was killed or
interrupted.

And indeed, I am on Windows.

Must be one of those "rough" edges.

 

Just an idea:  --exact-version might produce a readable OS identifier, too?

 

Hubert

 

 

Also simple "darcs get" went past patch 37 this morning.
Killed it myself at patch 100 or so, since my patience was up.

Anyway, a rather strange message:
libcurl: HTTP error (404?).

What puzzles me is the question mark. 
Obviously libcurl or some other module higher up was doing some guesswork.
Under normal conditions a 404 error and a timeout, say, should be easy to
tell apart. Right?

 

Indeed. I'd have to speculate what happens here. I would guess, from the
message, that it comes from libcurl. But as you said, libcurl should be able
to be more specific. So either the message comes actually from the code that
calls it (called it, was interrupted by the kill, didn't know what the
problem was, and wrote that message as if on behalf of libcurl), or
(assuming you're on Windows) this has to do with the version of libcurl that
was linked in (cygwin?, ...). Generally, Darcs seems to have a few rough
edges on Windows, there are several things that don't really run smoothly. 

 

 

Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs repo

[<rad...@gm...>]

Hi,

>
> > Furtunatly 'darcs repair' fixed the state (by giving no explanation
> either).
> >
> > That is why I have started to learn Haskell. ;)
> Good luck :-) Haskell is definitely fun to learn, even if the Darcs code is
> probably a bit ambitious to start with ;-)

Oh no, I am not starting with darcs (however I have copy of repository
at hand ;) ). Anyway I am really impressed with Haskell, and I am
doing much progress in no time ;) . I see a lot of application of
Haskell in my projects however I would like to embed it in other
languages (mainly Java, C# and, which may be a lot harder, Delphi) but
I can't find many resources on that. I've looked at "cahatoe" project
you've mentioned but I still can't figure out the concept of embedding
used there. Any hints?

Cheers!
  Radek.

Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs repo

[Leif F. <lei...@go...>]

>
>
> Right, but that is no question for eclipsedarcs mailing list. ;) But
> to share the opinion, darcs doesn't do good job informing about
> abnormal situation. For example, yesterday I've run darcs check. The
> output was something like
>
> $ darcs check
>   The repository is inconsistent!
>   Nothing!
>
> Now go figure. ;)

Yes, I've seen something like that also.

'Nothing' is one of the possible values of the 'Maybe' data type in Haskell.
(Given some type a, the two possible values are 'Just a' or 'Nothing'.) So
for instance, if you have a function that collects problems in a repo, you
might get nothing back from that function, or just a list of error messages.
In you case, it seems, there was nothing ;-) There seem to have been
problems still, but none of them with detail messages. At any rate, that is
what I think has gone on in your case. I have had sometimes the situation
where darcs check would give a list of changes in diff format instead of
just saying 'Nothing'. These changes were what was inconsistent.

At any rate, I totally agree of course that this is not something that a
user would have to know. The message would probably better be something like
'No further details available. Please run darcs repair.' Or something like
that :-)


Furtunatly 'darcs repair' fixed the state (by giving no explanation either).
>
> That is why I have started to learn Haskell. ;)

Good luck :-) Haskell is definitely fun to learn, even if the Darcs code is
probably a bit ambitious to start with ;-)

Thanks && ciao,
Leif



Cheers,
>   Radek.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> eclipsedarcs-develop mailing list
> ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipsedarcs-develop
>



-- 
Leif Frenzel
http://leiffrenzel.de
http://cohatoe.blogspot.com

Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs repo

[Leif F. <lei...@go...>]

Hi Hubert,

Thanks a lot,
>
> darcs get --partial --verbose http://...
>
> works all right.
> Very fast - I am impressed.


:-)


Also simple "darcs get" went past patch 37 this morning.
> Killed it myself at patch 100 or so, since my patience was up.
>
> Anyway, a rather strange message:
> libcurl: HTTP error (404?).
>
> What puzzles me is the question mark.
> Obviously libcurl or some other module higher up was doing some guesswork=
.
> Under normal conditions a 404 error and a timeout, say, should be easy to
> tell apart. Right?

Indeed. I'd have to speculate what happens here. I would guess, from the
message, that it comes from libcurl. But as you said, libcurl should be abl=
e
to be more specific. So either the message comes actually from the code tha=
t
calls it (called it, was interrupted by the kill, didn't know what the
problem was, and wrote that message as if on behalf of libcurl), or
(assuming you're on Windows) this has to do with the version of libcurl tha=
t
was linked in (cygwin?, ...). Generally, Darcs seems to have a few rough
edges on Windows, there are several things that don't really run smoothly.

Thanks && ciao,
Leif

Thanks again,
> Hubert
>
>
>
> > -----Urspr=FCngliche Nachricht-----
> > Von: ecl...@li...
> > [mailto:ecl...@li...] Im Auftrag
> von
> > Radoslaw Grzanka
> > Gesendet: Donnerstag, 15. M=E4rz 2007 14:22
> > An: ecl...@li...
> > Betreff: Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs
> > repo
> >
> > 2007/3/15, Kauker, Hubert <Hub...@tr...>:
> > > Hello...
> > >
> > > Did a darcs get from the command line.
> > > Got the following failure:
> > >
> > > Copying patch 37 of 332:
> > > 20060509235042-159cd-d8ceb161114b978ceb5df057ecb83bd0a5
> > > 48097b.gz
> > >
> >
> > I have managed to get the repo from sf.net today with no problem.
> > However, earlier this morning I had problems with transfers from
> > sf.net. Maybe it was related? Anyway, simply try again.
> >
> > Also, try with --partial. Much faster.
> >
> > Cheers,
> >   Radek.
> >
> >
> -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your
> > opinions on IT & business topics through brief surveys-and earn cash
> >
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> > _______________________________________________
> > eclipsedarcs-develop mailing list
> > ecl...@li...
> > https://lists.sourceforge.net/lists/listinfo/eclipsedarcs-develop
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> eclipsedarcs-develop mailing list
> ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipsedarcs-develop
>



--=20
Leif Frenzel
http://leiffrenzel.de
http://cohatoe.blogspot.com

[eclipsedarcs-develop] Fwd: Push All operation refactoring + Send All Fix.

[Leif F. <lei...@go...>]

cnJyZ2ggLi4uIGFnYWluIHRvIHRoZSB3cm9uZyBtYWlsIGFkZHJlc3MgOy0pCgpTb3JyeSAmJiBj
aWFvLApMZWlmCgotLS0tLS0tLS0tIEZvcndhcmRlZCBtZXNzYWdlIC0tLS0tLS0tLS0KRnJvbTog
TGVpZiBGcmVuemVsIDxsZWlmZnJlbnplbEBnb29nbGVtYWlsLmNvbT4KRGF0ZTogTWFyIDE2LCAy
MDA3IDg6MTYgQU0KU3ViamVjdDogUmU6IFtlY2xpcHNlZGFyY3MtZGV2ZWxvcF0gUHVzaCBBbGwg
b3BlcmF0aW9uIHJlZmFjdG9yaW5nICsgU2VuZApBbGwgRml4LgpUbzogUmFkb3P5YXcgR3J6YW5r
YSA8cmFkb3NsYXdnQGdtYWlsLmNvbT4KCkp1cHAsIG5vdyBpdCB3ZW50IHRocm91Z2ggOi0pCgpU
aGFua3MgJiYgY2lhbywKTGVpZgoKT24gMy8xNi8wNywgUmFkb3P5YXcgR3J6YW5rYSA8cmFkb3Ns
YXdnQGdtYWlsLmNvbSA+IHdyb3RlOgoKPiAyMDA3LzMvMTYsIExlaWYgRnJlbnplbCA8IGxlaWZm
cmVuemVsQGdvb2dsZW1haWwuY29tPjoKPiA+IEhpIFJhZGVrLAo+ID4KPiA+IFRoYW5rcyA6LSkg
SSdtIGhvd2V2ZXIgbm90IGFibGUgdG8gYXBwbHkgdGhpcyBsYXN0IG9uZS4gSSBnZXQKPiA+Cj4g
PiBbc25pcF0KPiA+IEM6XHdvcmtzcGFjZXNcZWNsaXBzZWRhcmNzPmRhcmNzIGFwcGx5IC0taW50
ZXJhY3RpdmUKPiA+IHB1c2hhbGwucGF0Y2gKPiA+IGRhcmNzOiBDYW5ub3QgYXBwbHkgdGhpcyBw
YXRjaCBidW5kbGUsIHNpbmNlIHdlJ3JlIG1pc3Npbmc6Cj4gPiBUaHUgTWFyICA4IDExOjI5OjEy
IFdlc3RldXJvcPVpc2NoZSBOb3JtYWx6ZWl0IDIwMDcgIFJhZG9zbGF3IEdyemFua2EKPiA+IDwg
cmFkb3NsYXdnQGdtYWlsLmNvbT4KPiA+ICAgKiBGaXggZm9yIGJ1dCAjOCAoQWRkIG9wZXJhdGlv
bikKPiA+ICAgVGhlIGFkZCBvcGVyYXRpb24gaXMgbm93IGRpc2FibGVkIGluIGV2ZXJ5IGNhc2Ug
d2hlcmUgaXQgd291bGQgbm90IGFkZAo+ID4gYW55dGhpbmcgdG8gdGhlIHJlcG9zaXRvcnkuCj4g
PiAgICoqKkRBUkNTKioqCj4gPiBbc25hcF0KPgo+IEkgdGhvdWdodCBJJ3ZlIHNlbnQgdGhpcyAt
IGFwcGFyZW50bHkgSSBqdXN0IG1hcmtlZCBpdCBkb25lIG9mCj4gZmx5c3ByYXkuLiBBbnl3YXks
IGhlcmUgYXJlIGFsbCB0aGUgcGF0Y2hlcyBhZ2FpbnN0Cj4gaHR0cDovL2VjbGlwc2VkYXJjcy5z
Zi5uZXQvcmVwbwo+Cj4gVGhhbmtzLAo+ICAgUmFkZWsuCj4KPiAtLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCj4g
VGFrZSBTdXJ2ZXlzLiBFYXJuIENhc2guIEluZmx1ZW5jZSB0aGUgRnV0dXJlIG9mIElUCj4gSm9p
biBTb3VyY2VGb3JnZS5uZXQncyBUZWNoc2F5IHBhbmVsIGFuZCB5b3UnbGwgZ2V0IHRoZSBjaGFu
Y2UgdG8gc2hhcmUKPiB5b3VyCj4gb3BpbmlvbnMgb24gSVQgJiBidXNpbmVzcyB0b3BpY3MgdGhy
b3VnaCBicmllZiBzdXJ2ZXlzLWFuZCBlYXJuIGNhc2gKPiBodHRwOi8vd3d3LnRlY2hzYXkuY29t
L2RlZmF1bHQucGhwP3BhZ2U9am9pbi5waHAmcD1zb3VyY2Vmb3JnZSZDSUQ9REVWREVWCj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBlY2xpcHNlZGFy
Y3MtZGV2ZWxvcCBtYWlsaW5nIGxpc3QKPiBlY2xpcHNlZGFyY3MtZGV2ZWxvcEBsaXN0cy5zb3Vy
Y2Vmb3JnZS5uZXQKPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5m
by9lY2xpcHNlZGFyY3MtZGV2ZWxvcAo+Cj4KPgoKCi0tIApMZWlmIEZyZW56ZWwKaHR0cDovL2xl
aWZmcmVuemVsLmRlCmh0dHA6Ly9jb2hhdG9lLmJsb2dzcG90LmNvbQoKCi0tIApMZWlmIEZyZW56
ZWwKaHR0cDovL2xlaWZmcmVuemVsLmRlCmh0dHA6Ly9jb2hhdG9lLmJsb2dzcG90LmNvbQo=

Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs repo

[<rad...@gm...>]

2007/3/16, Kauker, Hubert <Hub...@tr...>:
> Thanks a lot,
>
> darcs get --partial --verbose http://...
>
> works all right.
> Very fast - I am impressed.
>
> Also simple "darcs get" went past patch 37 this morning.
> Killed it myself at patch 100 or so, since my patience was up.
>
> Anyway, a rather strange message:
> libcurl: HTTP error (404?).
>
> What puzzles me is the question mark.
> Obviously libcurl or some other module higher up was doing some guesswork.
> Under normal conditions a 404 error and a timeout, say, should be easy to
> tell apart. Right?

Right, but that is no question for eclipsedarcs mailing list. ;) But
to share the opinion, darcs doesn't do good job informing about
abnormal situation. For example, yesterday I've run darcs check. The
output was something like

$ darcs check
  The repository is inconsistent!
  Nothing!

Now go figure. ;)

Furtunatly 'darcs repair' fixed the state (by giving no explanation either).

That is why I have started to learn Haskell. ;)

Cheers,
  Radek.

Re: [eclipsedarcs-develop] Push All operation refactoring + Send All Fix.

[<rad...@gm...>]

MjAwNy8zLzE2LCBMZWlmIEZyZW56ZWwgPGxlaWZmcmVuemVsQGdvb2dsZW1haWwuY29tPjoKPiBI
aSBSYWRlaywKPgo+IFRoYW5rcyA6LSkgSSdtIGhvd2V2ZXIgbm90IGFibGUgdG8gYXBwbHkgdGhp
cyBsYXN0IG9uZS4gSSBnZXQKPgo+IFtzbmlwXQo+IEM6XHdvcmtzcGFjZXNcZWNsaXBzZWRhcmNz
PmRhcmNzIGFwcGx5IC0taW50ZXJhY3RpdmUKPiBwdXNoYWxsLnBhdGNoCj4gZGFyY3M6IENhbm5v
dCBhcHBseSB0aGlzIHBhdGNoIGJ1bmRsZSwgc2luY2Ugd2UncmUgbWlzc2luZzoKPiBUaHUgTWFy
ICA4IDExOjI5OjEyIFdlc3RldXJvcMO1aXNjaGUgTm9ybWFsemVpdCAyMDA3ICBSYWRvc2xhdyBH
cnphbmthCj4gPHJhZG9zbGF3Z0BnbWFpbC5jb20+Cj4gICAqIEZpeCBmb3IgYnV0ICM4IChBZGQg
b3BlcmF0aW9uKQo+ICAgVGhlIGFkZCBvcGVyYXRpb24gaXMgbm93IGRpc2FibGVkIGluIGV2ZXJ5
IGNhc2Ugd2hlcmUgaXQgd291bGQgbm90IGFkZAo+IGFueXRoaW5nIHRvIHRoZSByZXBvc2l0b3J5
Lgo+ICAgKioqREFSQ1MqKioKPiBbc25hcF0KCkkgdGhvdWdodCBJJ3ZlIHNlbnQgdGhpcyAtIGFw
cGFyZW50bHkgSSBqdXN0IG1hcmtlZCBpdCBkb25lIG9mCmZseXNwcmF5Li4gQW55d2F5LCBoZXJl
IGFyZSBhbGwgdGhlIHBhdGNoZXMgYWdhaW5zdApodHRwOi8vZWNsaXBzZWRhcmNzLnNmLm5ldC9y
ZXBvCgpUaGFua3MsCiAgUmFkZWsuCg==

Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs repo

[Kauker, H. <Hub...@tr...>]

Thanks a lot,

darcs get --partial --verbose http://...

works all right.
Very fast - I am impressed.

Also simple "darcs get" went past patch 37 this morning.
Killed it myself at patch 100 or so, since my patience was up.

Anyway, a rather strange message:=20
libcurl: HTTP error (404?).

What puzzles me is the question mark.=20
Obviously libcurl or some other module higher up was doing some =
guesswork.
Under normal conditions a 404 error and a timeout, say, should be easy =
to
tell apart. Right?

Thanks again,
Hubert



> -----Urspr=FCngliche Nachricht-----
> Von: ecl...@li...
> [mailto:ecl...@li...] Im =
Auftrag von
> Radoslaw Grzanka
> Gesendet: Donnerstag, 15. M=E4rz 2007 14:22
> An: ecl...@li...
> Betreff: Re: [eclipsedarcs-develop] darcs get failure from =
eclipsedarcs
> repo
>=20
> 2007/3/15, Kauker, Hubert <Hub...@tr...>:
> > Hello...
> >
> > Did a darcs get from the command line.
> > Got the following failure:
> >
> > Copying patch 37 of 332:
> > 20060509235042-159cd-d8ceb161114b978ceb5df057ecb83bd0a5
> > 48097b.gz
> >
>=20
> I have managed to get the repo from sf.net today with no problem.
> However, earlier this morning I had problems with transfers from
> sf.net. Maybe it was related? Anyway, simply try again.
>=20
> Also, try with --partial. Much faster.
>=20
> Cheers,
>   Radek.
>=20
> =
------------------------------------------------------------------------=
-
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =
share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> eclipsedarcs-develop mailing list
> ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipsedarcs-develop

[eclipsedarcs-develop] Changelog on wiki

[Leif F. <lei...@go...>]

Hi all,

I have uploaded the actual changelog file from the 0.3 version to the wiki.
The link is now no longer broken :-)

If there is any other shortcoming on the project page, as always, please let
us know :-)

Thanks && ciao,
Leif

-- 
Leif Frenzel
http://leiffrenzel.de
http://cohatoe.blogspot.com

Re: [eclipsedarcs-develop] Push All operation refactoring + Send All Fix.

[Leif F. <lei...@go...>]

SGkgUmFkZWssCgpUaGFua3MgOi0pIEknbSBob3dldmVyIG5vdCBhYmxlIHRvIGFwcGx5IHRoaXMg
bGFzdCBvbmUuIEkgZ2V0Cgpbc25pcF0KQzpcd29ya3NwYWNlc1xlY2xpcHNlZGFyY3M+ZGFyY3Mg
YXBwbHkgLS1pbnRlcmFjdGl2ZSBwdXNoYWxsLnBhdGNoCmRhcmNzOiBDYW5ub3QgYXBwbHkgdGhp
cyBwYXRjaCBidW5kbGUsIHNpbmNlIHdlJ3JlIG1pc3Npbmc6ClRodSBNYXIgIDggMTE6Mjk6MTIg
V2VzdGV1cm9w9WlzY2hlIE5vcm1hbHplaXQgMjAwNyAgUmFkb3NsYXcgR3J6YW5rYSA8CnJhZG9z
bGF3Z0BnbWFpbC5jb20+CiAgKiBGaXggZm9yIGJ1dCAjOCAoQWRkIG9wZXJhdGlvbikKICBUaGUg
YWRkIG9wZXJhdGlvbiBpcyBub3cgZGlzYWJsZWQgaW4gZXZlcnkgY2FzZSB3aGVyZSBpdCB3b3Vs
ZCBub3QgYWRkCmFueXRoaW5nIHRvIHRoZSByZXBvc2l0b3J5LgogICoqKkRBUkNTKioqCltzbmFw
XQoKSXQgc2VlbXMgdGhlcmUgaXMgYSBwYXRjaCBtaXNzaW5nIGluIHRoZSBidW5kbGUsIG9yIGVs
c2UgZGlkIEkgbWlzcwpzb21ldGhpbmc/CgpUaGFua3MgJiYgY2lhbywKTGVpZgoKT24gMy8xNC8w
NywgUmFkb3P5YXcgR3J6YW5rYSA8cmFkb3NsYXdnQGdtYWlsLmNvbT4gd3JvdGU6Cj4KPiBIaSwK
PiAgIGhlcmUgY29tZXMgcGF0Y2hlcyBmb3IgUHVzaCBBbGwgb3BlcmF0aW9uLiBJdCB3b3JrcyBu
b3cgKGlmIHlvdQo+IHNlbGVjdCAibGFzdCByZXBvc2l0b3J5Li4uIikuCj4KPiBBbHNvIHRoZXJl
IGlzIHRyaXZpYWwgZXJyb3IgaW4gdmFsaWRhdGluZyBTZW5kQWxsIERpYWxvZyB3aGljaAo+IGJh
c2ljYWxseSBwcmV2ZW50ZWQgaXQgZnJvbSB3b3JraW5nLgo+Cj4gQXR0YWNoZWQgZmlsZSBpcyB6
aXAgZmlsZS4KPgo+IFdlZCBNYXIgMTQgMTQ6MTk6NDkgW19cOGNfXXJvZGtvd29ldXJvcGVqc2tp
IGN6YXMgc3RhbmQuIDIwMDcKPiBSYWRvc2xhdyBHcnphbmthIDxyYWRvc2xhd2dAZ21haWwuY29t
Pgo+ICAgKiBUcml2aWFsIGVycm9yIGluIHZhbGlkYXRpbmcgU2VuZCBBbGwgRGlhbG9nLgo+Cj4g
V2VkIE1hciAxNCAxNDoxNToxOSBbX1w4Y19dcm9ka293b2V1cm9wZWpza2kgY3phcyBzdGFuZC4g
MjAwNwo+IFJhZG9zbGF3IEdyemFua2EgPHJhZG9zbGF3Z0BnbWFpbC5jb20+Cj4gICAqIFB1bGwg
QWxsIERpYWxvZyBmaXguCj4KPiBXZWQgTWFyIDE0IDE0OjE1OjAxIFtfXDhjX11yb2Rrb3dvZXVy
b3BlanNraSBjemFzIHN0YW5kLiAyMDA3Cj4gUmFkb3NsYXcgR3J6YW5rYSA8cmFkb3NsYXdnQGdt
YWlsLmNvbT4KPiAgICogUHVzaCBBbGwgRGlhbG9nIHJlZmFjdG9yaW5nLgo+Cj4gV2VkIE1hciAx
NCAxNDoxNDoyMCBbX1w4Y19dcm9ka293b2V1cm9wZWpza2kgY3phcyBzdGFuZC4gMjAwNwo+IFJh
ZG9zbGF3IEdyemFua2EgPHJhZG9zbGF3Z0BnbWFpbC5jb20+Cj4gICAqIFB1c2ggQWxsIE9wZXJh
dGlvbiByZWZhY3RvcmluZyB0byBlbXBsb3kgKkluZm8gbW9kZWwuCj4KPgo+IENoZWVycywKPiAg
IFJhZGVrLgo+Cj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+IFRha2UgU3VydmV5cy4gRWFybiBDYXNoLiBJ
bmZsdWVuY2UgdGhlIEZ1dHVyZSBvZiBJVAo+IEpvaW4gU291cmNlRm9yZ2UubmV0J3MgVGVjaHNh
eSBwYW5lbCBhbmQgeW91J2xsIGdldCB0aGUgY2hhbmNlIHRvIHNoYXJlCj4geW91cgo+IG9waW5p
b25zIG9uIElUICYgYnVzaW5lc3MgdG9waWNzIHRocm91Z2ggYnJpZWYgc3VydmV5cy1hbmQgZWFy
biBjYXNoCj4gaHR0cDovL3d3dy50ZWNoc2F5LmNvbS9kZWZhdWx0LnBocD9wYWdlPWpvaW4ucGhw
JnA9c291cmNlZm9yZ2UmQ0lEPURFVkRFVgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fCj4gZWNsaXBzZWRhcmNzLWRldmVsb3AgbWFpbGluZyBsaXN0Cj4g
ZWNsaXBzZWRhcmNzLWRldmVsb3BAbGlzdHMuc291cmNlZm9yZ2UubmV0Cj4gaHR0cHM6Ly9saXN0
cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vZWNsaXBzZWRhcmNzLWRldmVsb3AKPgo+
Cj4KCgotLSAKTGVpZiBGcmVuemVsCmh0dHA6Ly9sZWlmZnJlbnplbC5kZQpodHRwOi8vY29oYXRv
ZS5ibG9nc3BvdC5jb20K

Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs repo

[<rad...@gm...>]

2007/3/15, Kauker, Hubert <Hub...@tr...>:
> Hello...
>
> Did a darcs get from the command line.
> Got the following failure:
>
> Copying patch 37 of 332:
> 20060509235042-159cd-d8ceb161114b978ceb5df057ecb83bd0a5
> 48097b.gz
>

I have managed to get the repo from sf.net today with no problem.
However, earlier this morning I had problems with transfers from
sf.net. Maybe it was related? Anyway, simply try again.

Also, try with --partial. Much faster.

Cheers,
  Radek.