-
Notifications
You must be signed in to change notification settings - Fork 403
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
Sync master and develop after 2.0 release #979
Conversation
Hotfix: Make RFID reader service working again
hotfix: installer shall use master
Use mopidy 2.2 also on master
Pin mopidy-iris to last version working with python 2
* Make master py3 compatible * Use py3 * Make py3 compatible * Make py3 compatible * Make py3 compatible * Make py3 compatible * Make py3 compatible * Make py3 compatible * Make py3 compatible * Make py3 compatible * Make py3 compatible
* use always python 3 for RegisterDevice.py
Make master py3 compatible
File name on ˋmasterˋ is still with underscores
Hotfix: installation of py packages now for python 3
delay shutdown if apt update/upgrade is running
# Conflicts: # .github/workflows/pythonpackage.yml # misc/sampleconfigs/phoniebox-rotary-encoder.service.stretch-default.sample # scripts/MFRC522.py # scripts/Reader.py.experimental # scripts/Reader.py.kkmoonRFIDreader # scripts/daemon_rfid_reader.py # scripts/installscripts/buster-install-default.sh # scripts/installscripts/stretch-install-default.sh # scripts/installscripts/stretch-install-spotify.sh # scripts/playout_controls.sh # scripts/python-phoniebox/PhonieboxConfigChanger.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Readme has only the actual release date I added yesterday.
The service file has just whitespace changes.
@MiczFlor, could you review also? From my point of view there are no changes back to develop.
Hi @s-martin
But I am not sure if that is necessary at the moment. With this merge you synced master issues back into develop? |
master is in sync with develop, i.e. develop contains all changes from develop and master. We can continue working on develop and when the next release is ready we can merge again develop to master. As long as we don't apply any hotfixes to master we don't need to merge master to develop. I don't think we need to delete and rename the branches. |
No description provided.