Crash trying to recreate own libraries after update

Issue #43 resolved
Guan Yang
created an issue
  1. Updated to 0.7.2.

  2. Open an existing project. Razen complains about my own guanix/lib-avr library being missing.

  3. I quit and and go to /Applications/ and did a hg clone of my library.

  4. Now I open the library because I want to change the part.

  5. Make a change and save.

  6. Select Upload Changes (to server).

  7. Crash as attached.

Is it possible to have my own libraries outside the Razen application folder so I don’t have to do work to use them every time I update?

Comments (11)

  1. Razen repo owner

    library_path and project_path in the general config file should allow you to move the libraries and project directories to an external location

  2. Razen repo owner

    Ah ok, so when you clone a library with hg it sets the remote url to the source of the clone (even if the source had its own remote url). So the remote of your newly cloned library is the old library, not the bitbucket repo. Will fix this, though need to think more about handling of remote urls.

  3. Guan Yang reporter

    Sorry, I've only used Git before, not Mercurial. Is there a fix for this? Can I change the remote url? I compared .hg/hgrc in the built in razen/lib-avr library with mine, and they look very similar. Built in:

    default =


    default = ssh://
    username = guanix <>
  4. Razen repo owner

    Another thought after rereading your original comment - is your library not automatically downloaded when you open a project that depends on it? That's what should happen.

  5. Guan Yang reporter

    It did this time! But I am pretty sure that didn’t work the first time. Hm.

    You can close this if you like or keep it open for the ssh problem. It's no longer an issue to me :-)

  6. Guan Yang reporter

    As far as I can tell, it is using plain http, and not https, when Razen downloaded the library automatically. Is my username and password sent over the wire unencrypted?

  7. Razen repo owner

    Ah, ok, it does https everywhere except the library clone (which I'll fix) :) But that doesn't use a username/password (so doesn't support private repos yet).

  8. Log in to comment