Libraries not syncing

#1

Hi all.
Do I need to register as a contributor to get access to all of this new awesome stuff you are all publishing? Maybe I'm missing something obvious, but I don't see half of this stuff on github either ?
I tried "Sync libraries" of course, but I get an error message:
""
Sync Successful : factory (1.0.10,anon)
Sync (pull) FAILED : community (1.0.10,anon)
org.eclipse.jgit.api.errors.NoHeadException: Pull on repository without HEAD currently not supported
org.eclipse.jgit.api.errors.NoHeadException: Pull on repository without HEAD currently not supported
""
plus a lot more......
I realize that the new stuff should be included in the next release, but I just cant wait :wink:
Thanks!

#2

no you don't need to be registered

go to preferences, and do 'reset libraries'

usually the above happen if you alter the community library, which if you are not a contributor you should consider 'read only'

#3

You probably need to select the 1.0.10 branch on github if you're browsing new patches there. :slight_smile:

#4

Yes!
I will be getting no sleep tonight :dizzy_face:
Thanks a loti

#5

Sorry, but I also found this matter really confusing. Finally sorted, but...Whew!

#6

generally, users do not need to go to github.com (or particular branches) to use Axoloti, it can all be done within the Axoloti app.

in fact, Id prefer users without git experience do not go there as it will lead to 'confusion', just browse using the filesystem locally - lets keep it simple.

(the only 'requirement' to go to github.com is to register as a user if you are going to be a contributor, but registering is the only thing needed to be done... some have accidentally forked the repo)

as I said to the OP, the reason for the git error, was due to editing content in the libraries, which essentially except for 'your contributor area' in the community library you should consider 'read-only'.

if you get into a weird state like the recommended path will be to reset the libraries, this is for two reasons
- we don't distribute tools needed to fix it in other ways
- I dont have the time to explain how to deal with git, which can be a complex beast.

in a future release, i hope to extend the current implementation such that the above issue are avoided, and if encountered is dealt with. but again, automatically, so the user does not have to be concerned with how its implemented. (as you may appreciate, making something simple for the end-user tends to mean the complexity is borne by the developer :wink: )

of course, I recognise we also need a proper patch browser and also access to version history is useful, they are on my 'wish' list too.

the only thing to bear in mind, is don't change anything in the libraries outside 'your area', future version will overwrite it (and this is already the case for the factory objects.)

EDIT : moved to helpdesk, the community library section is just for how to use, and contribution post.
(it needs to be kept 'minimal' so its easier to navigate)

#7

Indeed, I just pointed out the branch as they were nosing about on github anyway. :slight_smile:

#8

yeah, I know, no issue - its no secret this is all hosted on github :slight_smile:

I just wanted it to be clear to new users, visiting github.com, is not a needed/recommended part of the workflow.
this is going to be important when we get this out as an 'official' release, and so many more users will start using, and then potentially searching the forum, if they have issues.

#9

'Check for updates' was giving me null response while I was running on 1.0.9. It was only by reading hellcore's post and going to github for a look that I found 1.0.10. Probably there is another way I was supposed to know about it and get it installed, but that's how I got there... All's well that ends well. Thanks for all assistance!

#10

hmm sounds like a bug, but seems to be ok, in 1.0.10

we always post on the forum about new releases, and this includes a link to the software

a full list is always available here:

https://github.com/axoloti/axoloti/releases

(note: software releases are contained in a different repo to the community library, and are not routinely branched)

#11

Hahaha! "Nosing about" on the web is actually second on my list of preferred learning styles. "Trying stuff until it breaks" is first, and "asking questions" is way down the list. :confused:

The issue in my case was that I had indeed messed around with the libraries so they refused to sync. I had been making copies of some community patches and objects, and working on them inside the same folder. Resetting libraries did the trick. I now keep all my own work in a separate axoloti "objects/patches" folder structure over in "home/Documents", which I have added to the axoloti library locations in the preferences. No mess in my main axoloti file structure, and it works great!
By the way, thanks for the great forum guys. Very helpful!

#12

I only meant "nosing" in an inquisitive fashion. :slight_smile:

#13

thats actually what the one in Documents/axoloti is for, documents/axoloti/objects , documents/axoloti/patches (aka home library) is the users 'personal' library, we wont touch this (or any other library that is of type 'local') during sync.
hmm, perhaps I should have called it 'personal' or 'user' to make that a bit clearer :slight_smile:

note: the reason its there (rather than say documents/axoloti/user/objects,patches) is priory to libraries, we had been suggesting this location for users objects and patches, so made sense to use this to ease migration.

#14

But the "personal" folder structure generated on install on my system is inside "/home/axoloti" not "home/Documents/axoloti"...?
I created the same folder structure over in /Documents, and then changed the library reference for "home" in the axoloti preferences. Seems to work fine.
This is on Ubuntu 14.04 LTS, fresh download and install of axoloti 1.0.10 today, because I accidentally nuked my entire Ubuntu partition yesterday. Aah, nothing like a fresh start :confounded:

#15

sorry, a bit of confusion on my part as i was not aware what platform you were running on.
(windows and OS X have the axoloti home inside the documents folder)

yes on linux, its ~/axoloti and yes ~/axoloti/objects, patches were where i assumed users would put personal files.
I use ubuntu as well, but I wasn't sure how common ~/Documents is on other distros ... and even with ubuntu, as I tend to use linux for low level and dev stuff - Ive never seen ~/Documents used by anything :slight_smile:

so thought ~/axoloti was 'a safer bet' .... I guess we could look for a ~/Documents folder, and if it exists place the axoloti folder in there, it would be more consistent with windows and OSX.

anyway, you can put libraries where you like, generally we don't care about their locations... the only thing we refer to is the ID, and then only for factory/community where we have some logic to ensure users dont overwrite things and objects are placed in the right place in the community library.

Ouch no fun :frowning:
one thing you might want to consider is creating your own repo on either bitbucket or github, that way you can sync your own personal patches/objects there for 'backup' purposes, this is what I do.
(I prefer bitbucket for 'private' stuff, as its free to host private repos, whereas github (last time i checked) charges for private repos, only public are free)

anyway, have fun... happy patching

#16

I'm also having trouble with the community library. It contains a few really useful synths, but I can't find stuff from users such as Sirsicsick, who seems to be posting regularly. I've tried syncing the library, but all this stuff still isn't there. Does anyone have any suggestions?

#17

Which version do you have installed? Only the latest version will sync the latest additions to the community library. Could you post the related log messages from the main window?

#18

this might be obvious, but just to be clear, you only see the patches that contributors share in the library menu. all objects are in the object window (double click on an empty space in a patch) and you can search them from there...

#19

Thanks to both of you for getting back to me. Yes, it is obvious now that I know! I think I've figured it out now.