I want to upgrade React Native Debugger from version 0.10.0 to version 0.10.2, but clicking to upgrade when the program itself prompts me isn't working because (as they indicate on their page), there's a bug that prevents this upgrade. People have suggested "manually" upgrading or using brew cask reinstall react-native-debugger. The latter doesn't work, so I was wondering how you go about manually upgrading a package like this?
You can go to the release page https://github.com/jhen0409/react-native-debugger/releases/tag/v0.10.2 and download the appropriate .dmg file (for MacOS) from there. Afterwards you can just install it like any regular .dmg.
Related
I use Windows Application Packaging Project to generate MSIXBUNDLE for my WPF app.
App installed failed with error message: Windows cannot install package xxxxxx_3.8.3.0_neutral~_hijkl because a different package xxxxxxx_3.8.2.0_neutral~_abcde r with the same name is already installed. Remove package xxxxxx_3.8.2.0_neutral~_abcde before installing. (0x80073cf3)
I think the reason is that I signed the new package (3.8,3) with a new EV code signing certificate. Does WAP tool support option to uninstall previous package? Under the project property tab "Debug" ->"Start option", there is a check box for "Uninstall and then re-install my package. All information about the application state is deleted". But enable it does not seem to do the job.
Thanks,
"Uninstall and then re-install my package. All information about the application state is deleted"
I think this option is useful only for debugging purposes. It sounds like an option to remove a previous copy of the package (that has the same version and product name). So, this does not help with removing older versions.
For MSIX packages, you don't top configure anything specific in the package to trigger the removal of a previous version, as you used to do with an MSI. This is handled automatically by the OS.
But the OS needs to somehow understand which package to remove and I suspect the digital certificate is part of that check. Just manually remove the old version, install the new one, and then build a test version (3.8.4) to confirm if the different certificate was the problem.
I am trying to run AppEngine Standard Environment inside PyCharm.
The problem is when I include Google App Engine SDK as part of External Libraries, but it contains multiple version of old libraries that somehow has higher priority than the library I have in my env folder.
Specifically, it is loading jinja2-2.6 which doesn't work for Python 3, even though I have jinja2-2.11.3 in my env/lib.
Pycharm does have a bit of issues with its library system as many users have reported before. To Adjust the version of your libraries in PyCharm you must access the interpreter options relating your python interpreter for your current project, you can access this option by searching in the menu Settings/Preferences or by pressing Ctrl+Alt+S
In this dialog you can view the packages available and their current running versions. You can update the version by clicking on the ▲ symbol next to the version. if you have trouble upgrading to a specific version you may need then you can alway remove a package by clicking on the "-" on the right hand side after clicking on the package you wish to remove. After removing the package you can add a new one by clicking on the "+" button right on top of the "-" button. Here you can search for the package you need and before installing a package, you can check the specific version checkbox to search for the version you require in the dropdown menu next to it.
This link contains images for what i'm explaining here.
Remember that these packages are taken directly from the pip so if you have errors using the interface you can always try to manually edit the packages (also described in the link).
To upgrade a specific package using pip for python3 you can use the following command:
pip3 install --upgrade PackageName
I need to deploy and launch 2sxc module source code locally on my pc. Which release version is stable and has correct references? I tried it with version 11.05.00, but didn't succeed so far.
What problems did you find, and which version of DNN are you using?
I have 2sxc 11.4.0 running in a DNN 9.7.2 installation. No problems.
Looking at GitHub, I see 11.07.01 for LTS and a couple of "minor bugfix" releases following it. It looks like I should consider updating ...
Basically almost all releases are stable - and we recommend LTS releases.
I don't understand what you mean with correct references - could you elaborate?
Using JBoss Studio and importing sample jboss-forge-html5-archetype. When you click next; shows that plugin AngularJS Eclipse needs to be installed. When I try Download and Install it fails. It says it is already installed.
Has anyone seen this issue before? Where does JBoss Studio keep it's log files? Where does JBOss Studio list it's plugins? How do you un-install a plugin?
Thanks!
Log files are stored the same way as plain Eclipse does. Check in your ~/devstudio/ folder for .log files, or check your workspace's folder for a .log file. Or check the Error Log view while running Devstudio.
To list installed plugins / features, from within Devstudio,select Help > About. You can also uninstall features (not plugins) from that dialog.
If a feature needed by a quick start is already installed then you shouldn't need to reinstall it... But maybe you need to update it?
What version of Devstudio are you running? Which OS & version? Which JDK vendor & version?
I am trying to bring a package to an earlier version using opkg running this --force-downgrade opkg command, but it seems it doesn't behave like it should. Did this option work for anybody so far? And if so, how shoud I use it?
It seems to me that once you installed the latest version of a package you are stuck with it and can't get to another version without removing the package and installing it again.
I assume you have an earlier version of the ipk on the system and your are trying to call "opkg install --force-downgrade"?