SABnzbd Forums

nutski wrote:Seems to be gone which is very strange, i cloned it over the weekend so if anyone wants it grab from https://github.com/Nutski/LazyLibrarian

i used this one
https://github.com/itsmegb/LazyLibrarian

luzer wrote:

nutski wrote:Seems to be gone which is very strange, i cloned it over the weekend so if anyone wants it grab from https://github.com/Nutski/LazyLibrarian

i used this one
https://github.com/itsmegb/LazyLibrarian

That's out of date by a fair whack.

Hey guys, it's unfortunate that LibrarianMike deleted the main repo. I'm going to keep working on this branch to improve its features (in my free time). The updates I make will go into this repository https://github.com/herman-rogers/LazyLibrarian-1 (same version as Nutski and special thanks to Nutski for grabbing the last changes) and if anyone wants to chip in on issues/enhancements or with coding please feel free to!

It is a shame he deleted the repo as he had done some great work on updating it, i'm glad i cloned the repo when i did!

so librarianmike quit the project and deleted his repo?

keim wrote:so librarianmike quit the project and deleted his repo?

Really don't know unfortunately, all we know is the repo is gone

Is there an easy way to modify my existing install to pull updates from one of these other github repos?

It appears that he has quit the project or maybe he just deleted his account and is coming back soon. In any case I'll just keep working on it. There's a new update that allows for books to be added to the list while the database is fetching books. https://github.com/herman-rogers/LazyLibrarian-1 is the current link.

^ to update you copy just do the following:

git remote add --track master upstream git://github.com/upstreamname/projectname.git

git fetch upstream

git merge upstream/master

if you already have an upstream then:

git rm upstream

That should do it.

Can you give an example of how to switch it to yours? I tried that but I must have done it wrong as my copy still tries to update from LibrarianMike's version from the GUI.

_edraven_ wrote:Can you give an example of how to switch it to yours? I tried that but I must have done it wrong as my copy still tries to update from LibrarianMike's version from the GUI.

The code needs a little update to point to the correct GIT repo, i've made the changes and submitted a pull request, if herman-rogers thinks it looks at and pulls it in then if you follow his instructions it will update then auto update should work again after that, i hope

Cool thanks Nutski, I merged the pull request and it should update. Let me know if its working this way or not it should work but only through manual updating it through Github. I know before LibrarianMike left that there was a problem with the updating feature so I think I might work on that as well so updates can occur through the GUI rather than through command line prompts.

Also, if you're still having problems just delete LazyLibrarian and re clone my repository (I had a lot of problems because I was synced directly with LibrarianMikes repo). Then try updating the stream to see if that helps.

(This might delete your library/authors so be careful!!)

No probs, i'm not great at coding but can understand enough to make changes here and there, i've just allowed mine to update and its now pulled to the latest revision on your GIT, real test will be when you make your next change but so far it seems to work well, thanks for pulling it through.

The easiest way for most people will be to download the current version from GIT and then use the built in update from then on, if you KEEP config.ini and also lazylibrarian.db but remove all other files, download the latest version from https://github.com/herman-rogers/LazyLibrarian-1 and copy all these files into your normal directory structure, this should maintain your settings and database and then continue on as normal.

did this. get
Could not get commits behind from github

I'm sorry what exactly did you try? I know if you attempt to update the program using its built in update feature that it won't work, I think that whole part of the program needs to be worked on really. Did you try just a normal git pull?