How to update from v10 to V11

[root13F]

Switch branches in V11 [ cannot import name Database issue]

i installed ERPNext V11 and when i run bench switch-to-master it told Switched to master Please run `bench update --patch` to be safe from any differences in database schema but when i run it it gives me this error Backing up sites... Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/opt/frappe/newe…

[fnrfarid]

Hi @root13F, I’m facing the same issue. The versions are:

Installed Apps
ERPNext: v10.1.64 (master)
Frappe Framework: v11.0.3-beta.14 () (staging)

This is my test instance. It was Frappe v10 before. I switched the branch and stuff. I mean, I don’t see any changes ; I think , I need ERPNext v11 for updated features. How can I achieve that?

I’m also willing to start from scratch.

Thanks in advance.

[root13F]

@fnrfarid

ERPNext: v10.1.64 (master)
Frappe Framework: v11.0.3-beta.14 () (staging)

First it has been recommended that both your apps should be on the same branch i.e. master or staging. Also, one thing to note is v11 features have not yet been merged into master. SO to try them out you’ll have to switch to staging branch.

I recommend that If you are testing v11 then make a new site and try those changes there in your development server or PC. Then try bench switch-to-branch staging and bench update --patch to get it done.

[fnrfarid]

@root13F

Then try bench switch-to-branch staging and bench update --patch to get it done.

@root13F I’m trying to switch to staging branch; while switching ERPNext, it shows “Branch staging does not exist in Upstream for erpnext”

I’m following this

Master branch : v10
Staging branch : v11

If you want to switch to v11, goto your bench and run

Switch to staging branch
bench switch-to-branch staging frappe
bench switch-to-branch staging erpnext

Setup requirements
bench setup requirements

Migrate site
bench --site site-name migrate

Restart supervisor.
bench restart

Getting “Branch staging does not exist in Upstream for erpnext” in the 2nd step.

[fnrfarid]

@chdecultot

Hi,

The staging branch does exist on Github, and the problem with the command “switch-to-*” comes from your git configuration file for ERPNext:

Make sure it fetches all branches on upstream and not only develop or master.

Here is an example of an app already switched to staging:

@chdecultot How do I make sure to fetch all branches on upstream?

I can switch Frappe to staging but for ERPNext it says, doesn’t exist on upstream!

[snv]

Hi,

Refer to my solution here:

[Sept-2018] [Important] Develop Branch is now Version 12

In case you can’t fetch the staging branch, execute this command from the app’s directory: git config remote.upstream.fetch "+refs/heads/*:refs/remotes/upstream/*" This will configure git to fetch all branches from upstream. Then run git fetch upstream to fetch staging branch.

[fnrfarid]

Thanks @snv. I already did. Using the Staging now; testing. Getting errors after saving stuffs.

Hopefully a master version will be released soon.

Thanks again.

[chdecultot]

Hi @fnrfarid,
@snv solution is the correct one.
If it’s still not working check the .git/config file directly in the erpnext folder.

If correctly configured (like in @snv post) you should be able to make a git fetch and fetch the staging branch.

It’s strictly a git issue, so maybe you can find some help by making some git tutorials or looking in Google in reference to the error generated by the git command.

Good luck!

[chdecultot]

Sorry didn’t see your last message

Maybe you can post your issues with the staging branch?
You may not be the only one facing these issues.

[vrms]

@chdecultot

Make sure it fetches all branches on upstream and not only develop or master.

as shown by @snv here

[kt2152]

getting the following error

any solution

[Muzzy]

Change the line in git .config file as shown in post 19 of this thread. The text after fetch =
Then try again to migrate ERPNext

[kt2152]

tried it
made changes to erpnext git config file

but still giving me same error while trying to switch branch

[Muzzy]

You need to edit it as below.

fetch = +refs/heads/:refs/remotes/upstream/
Ensure the characters are correct. Save the file and then use

bench switch-to-branch staging erpnext

use bench switch-to-branch staging frappe (if your frappe is still on Master)

bench setup requirements

bench --site site-name migrate

bench restart

Frappe and ERPNext should both be on Staging. Had the same issue till I fixed the config file. Since then now more problems. ignore npm if it throws any error.

[kt2152]

This is the entire config file

still no luck ,
can you share your config file please , it will help out a lot ,

thanks

[Muzzy]

core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote “upstream”]
url = GitHub - frappe/erpnext: Free and Open Source Enterprise Resource Planning (ERP)
fetch = +refs/heads/:refs/remotes/upstream/
[branch “master”]
remote = upstream
merge = refs/heads/master
[remote “origin”]
fetch = refs/heads/:refs/remotes/origin/
[branch “staging”]
remote = upstream
merge = refs/heads/staging

Installed Apps
ERPNext: v11.0.3-beta.24 () (staging)
Frappe Framework: v11.0.3-beta.29 () (staging)

Just realized that for some reason the * go missing in the code. So heres the picture of the code that should be there.

[clarkej]

FWIW this may help to compare Switch branches in V11 [ cannot import name Database issue] - #14 by clarkej

[Manjunath_Sajjan]

I followed your procedure, not able to set erpnext to staging from master.

[abidomar]

it’s very difficult for the layperson to manage this… I’m sticking with Version 10 until a proper upgrade path exists.

[root13F]

you should wait till the v11 actually comes to master. however you can try it on a test instance. and by instance I don’t mean a different server altogether. It can either be a different frappe-something folder (its called a bench instance) or on a different pc