okay. but to reconfirm, am i to run it in only the erpnext directory?
UPDATE: Upgrade completed successfully but only frappe upgraded to v12. erpnext is still on v11
can anyone point out what would be the latest moment when to run the …
switch-to-branch [version]
… command when your instance is on the master branch currently?
not 100% sure if that is still relevant but from switching branches from staging to master las time , but as far as I remember …
switch-to-branch [branch] --upgrade
… would be the ideal command of choice.
Okay, sorry if I am getting too detailed. 
git config remote.upstream.fetch “+refs/heads/(star):refs/remotes/upstream/(star)” from erpnext and then
from frappe-bench directory
bench switch-to-branch version-12 --upgrade
bench update --patch
Hope that helps.
Thanks
Jay
2 Likes
I figured i’d need to do that so i already did. But when i try to migrate i get this error:
frappe.exceptions.DoesNotExistError: DocType Item Manufacturer not found
I essentially gave up, setup a new v12 instance and restored backup and everything is fine. i have tried direct upgrade all day and it doesn’t work
Please clarify if:
production systems which were on master need to change either to version-11 or version-12 and both still are valid versions.
very confusing from the start. Here below:
"Repository Changes
The branches on the ERPNext & Frappe repositories are being renamed as follows:
Old Name New Name
develop version-12
master version-11
hotfix version-11-hotfix
Note: The master branch has been deprecated as of today i.e. 22 July, 2019.
Following are the new branches created:
develop: Version 13
version-12-hotfix: Staging area for version 12 fixes
Please note, all your open PRs have to be rebased to the new branch."
Please also note that there are systems on production.
I think i’m more or less there - but I have been stuck all day yesterday and now today on the rollup build taking forever or not happening at all…
/home/frappe/frappe-bench$ sudo bench update --build
Backing up sites...
INFO:bench.utils:bench build
yarn run v1.17.3
$ FRAPPE_ENV=production node rollup/build.js
Production mode
✔ Built js/moment-bundle.min.js
✔ Built js/libs.min.js
Building frappe assets...
✔ Built js/dialog.min.js
✔ Built js/modules.min.js
✔ Built js/social.min.js
Any ideas on how long this should take or how I can speed it up? Previously on v11 it took a while but would eventually build. Now it’s not going at all…
Thanks!
Whoa!!! This is awesome… I almost feel like a kid in a candy store 
Did this ship with the DB API as planned? Didn’t see anything about that in the release notes
Cheers!
I’m up and running! Needed to increase my VM on GCloud as my ram was too low. Now it seems to be working smoothly. Thanks
1 Like
As of now.
~/frappe-bench/apps/erpnext$ git branch -a
- develop
remotes/upstream/HEAD → upstream/develop
remotes/upstream/clarkejj-patch-1
remotes/upstream/develop
remotes/upstream/fix_bom_include_exploded_item
remotes/upstream/hotfix
remotes/upstream/hr_dashboard
remotes/upstream/master
remotes/upstream/revert-16950-fix-issue-credit
remotes/upstream/staging
remotes/upstream/v10.x.x
remotes/upstream/v12
remotes/upstream/v4.x.x
remotes/upstream/v5.x.x
remotes/upstream/v6.x.x
remotes/upstream/v7.0.x
remotes/upstream/v7.x.x
remotes/upstream/v8.x.x
remotes/upstream/v9.x.x
~/frappe-bench$ bench switch-to-branch v12 erpnext
Switching for erpnext
INFO:bench.utils:git config --unset-all remote.upstream.fetch
INFO:bench.utils:git config --add remote.upstream.fetch ‘+refs/heads/:refs/remotes/upstream/’
INFO:bench.utils:git fetch upstream --unshallow
remote: Enumerating objects: 1, done.
remote: Counting objects: 100% (1/1), done.
remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0
Unpacking objects: 100% (1/1), done.
INFO:bench.utils:git checkout v12
Branch v12 set up to track remote branch v12 from upstream.
Switched to a new branch ‘v12’
INFO:bench.utils:git merge upstream/v12
Already up-to-date.
Successfully switched branches for:
erpnext
Switched to v12
Please run bench update --patch to be safe from any differences in database schema
Hi
v11 running in VM box
Trying to upgrade to V12
when i run this
frappe@ubuntu:~/frappe-bench$ git config remote.upstream.fetch “+refs/heads/:refs/remotes/upstream/”
i get error
fatal : not in a git directory
how to resolve this
regards
Hemanth
Hi Kirishnan,
Check this link out. That should resolve your issue. Hopefully. The software behind this forum replaces some of the characters, that’s the problem.
Thanks
Jay
Sir
Thanks for the reply
this command
git config remote.upstream.fetch “+refs/heads/:refs/remotes/upstream/”
iam running @ frappe@ubuntu:~/frappe-bench$
should i change the directory to git
if so how
how to execute this command
“What do you see if you go to frappe-bench/apps/erpnext and do a git status?”
should i change the directory from frappe@ubuntu:~/frappe-bench$ to ?
Thanks and regards
Hemanth
1 Like
You need to run that from the frappe-bench/apps/erpnext folder and you have to replace in your command line “ with " and ” with ".
plus you need to add a star (the multiplication key *) after heads/ and upstream/
If that doesn’t go through run the same command with git config --replace-all …
Hope this helps.
Thanks
Jay
1 Like
Sir
Thanks for the reply
I tried as mentioned…but no results
this is what i get
tried with git config --replace-all
no results
thanks and regards
Hemanth
1 Like
There won’t be any results in that screen. Now go back to frappe-bench folder and run
bench switch-to-branch version-12 --upgrade
bench update --patch
And if the DocType Item Manufacturer not found shows up:
bench run-patch erpnext.patches.v12_0.make_item_manufacturer
if you have multiple sites you will have to do that for each. The default site will go through when you run it the first time, but for the others you will have to use the command
bench --site sitename run-patch erpnext.patches.v12_0.make_item_manufacturer
Hope that helps
Thanks
Jay
2 Likes