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

Upgrade to Drupal 8.2 #416

Merged
merged 3 commits into from
Nov 16, 2016
Merged

Upgrade to Drupal 8.2 #416

merged 3 commits into from
Nov 16, 2016

Conversation

dannylamb
Copy link
Contributor

Addresses #392

The REST UI module made a release TODAY that works with 8.2. We're back in business with no yaml.

@whikloj
Copy link
Member

whikloj commented Nov 10, 2016

vagrant up

@whikloj
Copy link
Member

whikloj commented Nov 10, 2016

Possibly unrelated, but tried to add a new Fedora Resource and got a website error. Apache log says

[Thu Nov 10 19:21:35.494767 2016] [:error] [pid 28029] [client 10.0.2.2:57649] Uncaught PHP Exception Symfony\\Component\\Routing\\Exception\\RouteNotFoundException: "Route "entity.fedora_resource.version_history" does not exist." at /var/www/html/drupal/core/lib/Drupal/Core/Routing/RouteProvider.php line 187, referer: http://localhost:8000/admin/structure/fedora_resource/add/rdf_source

@dannylamb
Copy link
Contributor Author

not unrelated... other work sneaking through. let me pull my version stuff out of it. sry... bad form with git on my part.

@ruebot
Copy link
Member

ruebot commented Nov 10, 2016

Don't be @ruebot 😄

@dannylamb
Copy link
Contributor Author

hrm... looks fine on my install. and the revision stuff isn't there or in the commit. i was paranoid because i totally added that route in other work, but i sliced it out properly. i'm going to blast what i've got and re-vagrant up to double check. tabula rasa.

@dannylamb
Copy link
Contributor Author

screenshot from 2016-11-14 09-57-42

:(

Fresh install didn't reproduce? Can anyone try?

@whikloj Shall we start the vbox/vagrant version dance? Vbox 5.0.24_Ubuntu / Vagrant 1.8.1 on Ubuntu 16.04

@ruebot
Copy link
Member

ruebot commented Nov 14, 2016

I'll give it a shot.

vagrant up

@ruebot
Copy link
Member

ruebot commented Nov 14, 2016

screenshot from 2016-11-14 09-36-32

Looks good on my end.

$ vagrant -v      
Vagrant 1.8.4

VirtualBox Graphical User Interface Version 5.0.14_Ubuntu r105127

@whikloj
Copy link
Member

whikloj commented Nov 14, 2016

My islandora submodule is different and I can't get it to go back to normal. Death to submodules.

@dannylamb
Copy link
Contributor Author

I made sure I had everything pushed up, and then I clobbered my directory and re-cloned. I don't trust the submodules either.

@DiegoPino
Copy link
Contributor

I did a fresh install and could not reproduce the error this pull fixes, so i think we have deployment async problems (deployment version vectors??). So if anyone can confirm this is working then i'm fine.

@ruebot
Copy link
Member

ruebot commented Nov 14, 2016

@dannylamb that's what I did to. Removed the dir in modules, cloned, removed content I had existing, uninstalled, checked out branch, installed.

@ruebot
Copy link
Member

ruebot commented Nov 15, 2016

Shall I create a separate ticket to remove the use of submodules from the vagrant install process? I'm happy to take that on.

@dannylamb
Copy link
Contributor Author

Yes. I think at this point we should consider pulling install out into its own repo, as well. It's confusing to bundle it with this, which I guess is just for releases, really.

@dannylamb
Copy link
Contributor Author

Is someone ok merging this?

@ruebot
Copy link
Member

ruebot commented Nov 15, 2016

I can merge it now. Any objections @Islandora-CLAW/committers?

@dannylamb
Copy link
Contributor Author

Merged with upstream to get rid of a conflict. Good to go now.

@ruebot ruebot merged commit 0d96627 into Islandora:master Nov 16, 2016
@dannylamb
Copy link
Contributor Author

Thx @ruebot

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

Successfully merging this pull request may close these issues.

4 participants