Repository from GitHub using the following command: Open a terminal or command prompt and clone the PyBitmessage The Bitmessage wiki should provide a list of necessaryĭependencies for your operating system. Here is a step-by-step guide to compiling and running PyBitmessage:įirst, make sure you have all the required dependencies installed on On Sun, Jul 30, 2023, 1:19 AM botdigit-admin wrote: For the most current information, always refer to the official Bitmessage wiki or the project's repository on GitHub. Keep in mind that my knowledge is based on information available up until September 2021, and the Bitmessage project may have undergone changes or updates since then. Alternatively, you might find pre-compiled binaries or package managers that simplify the installation process for your specific operating system. Please note that these instructions are for compiling and running PyBitmessage from source. Running as a daemon is useful for having Bitmessage run continuously without a graphical user interface. If you want to run Bitmessage as a daemon (in the background), you should check the Bitmessage wiki for specific instructions on how to do that. You can edit this file using a text editor to make necessary changes. The configuration file is usually located in the "keys.dat" file within the PyBitmessage directory. If you don't understand what git merge does, please don't use it either.Depending on your needs, you may want to adjust the configuration settings. If you're not doing any changes to the code, please don't use git merge. On second thought, you probably do need FETCH_HEAD after all.Īlso, i wont mind if i lose any changes since i didnt make any changes to any code, the only changes i dont want to lose are my settings/configs. Git reset -hard without FETCH_HEAD would do just fine. Please don't do that if you don't understand what it does.īecause this is not a BM issue but a git issue. unless of course you did a git merge in the past. ![]() These are the files it was conflicting with when i do git pull: There shouldn't be any problem doing a git pull. My main concern is updating bitmessage Portable from 0.6.1 to 0.6.2 using git pull. But it turns out that that's not the problem you're having. Setting XDG_CONFIG_HOME is an alternative to portable mode, when for some reason you can't have config in the same directory as the source. ![]() I only run in portable mode so i dont need to change this right XDG_CONFIG_HOME? So please pay attention when I'm telling you not to use git merge. Im not a professional and am still kinda new to BM. Please confirm if the above git reset command does the job of updating BM portable mode correctly without losing any settings or without breaking the code? Git stash does not work for me and prefer not to use it. Is this the correct way to do a git pull in portable mode or is there a SIMPLER method?Īlso forgive me if i didnt see, but i have been looking all over the BM wiki to try and find documentation which describes what to actually do step by step if GIT PULL does not work and there is nothing. The only thing i tried now which seemed to work was: git reset -hard FETCH_HEADĪnd then git pull and then it seemed like it updated the files very quickly, i started BM and i saw that my settings were there and version went to 0.6.2. Please, commit your changes or stash them before you can merge. Puppypackage/pybitmessage-0.3.5.pet.specs Error: Your local changes to the following files would be overwritten by merge:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |