Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Important Notice #21

Closed
ghost opened this issue Nov 12, 2018 · 9 comments
Closed

Important Notice #21

ghost opened this issue Nov 12, 2018 · 9 comments
Assignees

Comments

@ghost
Copy link

ghost commented Nov 12, 2018

See DobyTang/LazyLibrarian#1666

@homerr
Copy link
Member

homerr commented Nov 12, 2018

Thanks, we'll update this to pull in from their new GitLab home

@homerr homerr self-assigned this Nov 12, 2018
@DavidFW1960
Copy link

When will this change request be implemented?

@Epod
Copy link

Epod commented Dec 4, 2018

@DavidFW1960 & @homerr - I just did a pull request that fixes this issue. Hopefully it gets approved :)

@DavidFW1960
Copy link

Hi @Epod great.... I reported an issue to them that has been fixed now however of course until the repo location is updated and the repo is pulled I can't access it.

@ghost
Copy link
Author

ghost commented Dec 7, 2018

@homerr please review PR, LL is currently broken!

@DavidFW1960
Copy link

this has still not been addressed in latest image. can the pr be merged?

@homerr
Copy link
Member

homerr commented Dec 11, 2018

New PR opened for this, just doing final QA on how the container handles upgrading before it goes live. #24

@homerr
Copy link
Member

homerr commented Dec 12, 2018

All done, pull the latest image and you'll be up to date.

@homerr homerr closed this as completed Dec 12, 2018
@DavidFW1960
Copy link

Nice job!!! and the bug I had is now gone as well. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants