-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update python to 2.7.18 #3648
Update python to 2.7.18 #3648
Conversation
@hgy59 Thanks. In case of Python, I am not only interested in package own-upgrade but also in effect on dependent applications. I will do some testing |
It would be very helpful if we had some makefile targets like "all-python" or "all-python3" to build python2.7 or python3 with all packages depending on it. |
@hgy59 I agree... A basic "grep" may do the trick... By the way, compilation success is far not enough, according to current troubles with stuck 3.6 upgrade. |
...and |
I already have logic to find the things with DEPENDS -tracking (it showed me the build load for an OpenSSL change recently that I backed away from)
I only track build dependencies, not install-dependencies, so it would be logic at a different level but I can mimic the same for a test-matrix of some kind.
… On Mar 4, 2019, at 13:32, hgy59 ***@***.***> wrote:
It would be very helpful if we had some makefile targets like "all-python" or "all-python3" to build python2.7 or python3 with all packages depending on it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
working on verification of the build for packages depending on python 2.7 EDIT: current states and WIP see PR description current packages states:
TODO:
@Safihre do we still need the package |
Feel free to remove @ymartin59 I think it can be completely removed from SynoCommunity, also from the website etc. |
Any updates here? :) |
Maybe we should get this out now :) |
@Safihre I am working on it. As it has so much dependencies, it takes some time to build and verify. For python2, all packages that depend on python2 and all packaes depending on python modules, it takes more than 36 hours for me to build (results in ~ 220 spk files). And the (really) final python2 version is in sight (2.7.18 release candidate early April, 2020, 2.7.18 mid-April, 2020). |
Any help to use Travis to do the building? But I guess we have some time if we wait untill 2.7.18. |
@Safihre thanks for the offer, but now it is more a matter of testing than building the packages. |
@hgy59 @Safihre At the moment, I focus on Python 3 and moving applications to Python 3. I really wonder if it is worth the effort to build and publish Python 2.7 and all other dependent applications - that may probably break after Python 2 update... |
@hgy59 Do not put effort on maintaining applications that now have Python 3 support. (Firefox Sync Server does not have yet). |
not for ffsync (as you are working on it, and future update changed to rust). |
@hgy59 I am (almost) over with ffsync, I will have a look at Subliminal. |
…tire fix saltpad homepage use latest version of wheel that works with python 2 fix linking to rt lib update itools - update dependencies - fix ppc-archs - fix configure for linking to rt library in cross/usbmuxd fix usage of DSM_APP_NAME in spk makefiles retire oscam package (close SynoCommunity#2636) Fix pyload/tesseract-ocr for ppc853x-5.2
- fix DSM 6 compatibility - create certificate by installer (paths used by app for certificate creation does not work on dsm 6)
- update domoticz and migrate to python3 - archs not supported anymore: $(ARM5_ARCHES) powerpc ppc824x ppc853x ppc854x - update app icon
- use compiled bcrypt dependency - enable arch qoriq (unsupported are: powerpc ppc824x ppc853x ppc854x)
- fix duplicity wheels (missing modules requirements.txt) - update librsync - update duply
- add compression to cross/librsync - older versions of rdiff-backup fail to build with updated cross/librsync
- remove definition of LOG_FILE to use generic one - mylar: use subfolder for data to avoid conflicts with log files - fix couchpotatoserver - fix couchpotatoserver-custom - fix headphones - fix headphones-custom - fix lazylibrarian - fix mylar - fix nzbmegasearch - fix plexpy-custom - fix sabnzbd
- fix salt-api dependencies and add port - update salt-master to version 2015.5.11 (may be the last supported version by saltpad) - update salt-master dependencies (salt-api needs CherryPy < 12) - use branch saltpad_v1 as this is the latest python app - update dependencies to use current Flask - reduce icons to 512x512 pixel
- fix deluge start-stop-status - adjust deluge dependencies and add hi3535 to unsupported archs - archs not supported anymore: 88f6281 powerpc ppc824x ppc853x ppc854x hi3535 - use src/requirements.txt for wheels and use explicit versions - fix boost PLIST - fix watch folder configuration - configure autoadd plugin and activate on demand - update python module cryptography to 2.9.2 - add python module rencode 1.0.6 - deluge depends on rencode and latest python - fix python dependency - configure geoip data (still not working) - add wheels of rencode and PyHamcrest
- update pyload to 0.4.20 - fix DSM 6 service installation (use generic service approach where possible) - fix pyload.conf - fix host ip (use 0.0.0.0 instead of ::) and remove IPv6 patch since config does not work with "::" - remove obsolete patches - install config to var instead of etc folder for generic update handling - set user name and group for permissions in pyload.conf - fix cross compile js - js compiled for intel archs (x86_64, i386), does still not work for pyload - pyload JS engine test fails for intel archs as calling `js -e "print(23+19)"` returns "out of memory" instead of "42" - add diyspk/js (helpful for testing cross compiled js engine) - remove SPK_COMMANDS (not working with SERVICE_SETUP)
- use full device name for shares of mounted devices - fix service user privilege - need root for mount/umount and add/remove udev rules - update itools dependencies - update libplist and libusbmuxd to official releases - suppress call of configure in autogen.sh (libplist, libusbmuxd, usbmuxd, libimobiledevice) - use var folder for access-log and lock files - use package log (not install log) for service_prestart and service_poststop - log unexpected errors of mount/umount in error.log
- fix dsmappname configuration - fix quotes in spk description - make gateone icon square - popt: fix download url - sabnzbd/Makefile: use spksrc.install-resoruces.mk for package download - minio/src/wizard/install_uifile: fix html of link to permission management - haproxy/Makefile: use requirements.txt for wheels
- itools: remove obsolete install_target - flexget: revert update - rdiff-backup: generic installer
@ymartin59 I updated the commit messages (except the |
Build Check List before storm-publish:
|
@ymartin59 I would leave out |
@@ -16,7 +16,7 @@ | |||
"daemon_port": 58846, | |||
"torrentfiles_location": "@download_dir@", | |||
"max_active_limit": 8, | |||
"geoip_db_location": "/usr/local/deluge/share/GeoIP/GeoIP.dat", | |||
"geoip_db_location": "/usr/share/geoip/GeoIP.dat", |
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.
@hgy59 Notice I do not find that file on DSM 6.1 system, it is only available on DSM 6.2
Motivation: Update python to 2.7.18 (the last 2.x version)
Checklist
all-supported
completed successfullyupgrade and new installation verified with x64-6.1
Updates an fixes of dependent packages
Validated dependent packages
Remarks
BOOST_LIBRARIES
are built. The dependency on cross/python is removed from cross/boost/Makefile to avoid conflicts with cross/python3. To build cross/boost with python(2) bindings, the dependency on cross/python must now precede cross/boost. With this dynamic dependency, it is possible for packages (like updated domoticz) to depend on python3 and boost (boost python3 bindings not yet required/implemented).js -e "print(23+19)"
fails without of memory
.