• Diese Seite verwendet Cookies. Indem du diese Website weiterhin nutzt, erklärst du dich mit der Verwendung von Cookies einverstanden. Erfahre mehr

Workaroud für Konflikt py-setuptools, pip lässt sich nicht installieren

Themenstarter #1
Ich habe in einem FreeBSD iocage nextcloud auf FreeNAS installiert, aber das letsencrypt Zertifikat lässt sich nicht automatisch aktualisieren.

Code:
root@nextcloud:/usr/ports/devel/py-pip # acme.sh --issue -d my.example.com --standalone --httpport 8675 --reloadcmd "/root/deploy-freenas/deploy_freenas.py" --debug --renew --test
Code:
root@nextcloud:~/deploy-freenas # /root/deploy-freenas/deploy_freenas.py

Traceback (most recent call last):

  File "/root/deploy-freenas/deploy_freenas.py", line 22, in <module>

    import requests

ModuleNotFoundError: No module named 'requests'
py-requests sollte ich per pip install nachinstallieren, allerdings gibt es Probleme wegen eines Konflikts mit py-setuptools py27 vs. py36.

Code:
root@nextcloud:/usr/ports/devel/py-setuptools # freebsd-version
11.2-RELEASE-p9

root@nextcloud:/usr/ports/devel/py-setuptools # make FLAVOR=py36 install clean BATCH=yes FORCE=yes
===>  Installing for py36-setuptools-41.2.0
===>  Checking if py36-setuptools is already installed
===>   Registering installation for py36-setuptools-41.2.0
[nextcloud] Installing py36-setuptools-41.2.0...
pkg-static: py36-setuptools-41.2.0 conflicts with py27-setuptools-40.8.0 (installs files into the same place).  Problematic file: /usr/local/bin/easy_install
*** Error code 70

Stop.
make: stopped in /usr/ports/devel/py-setuptools

root@nextcloud:/usr/ports/devel/py-setuptools # cd /usr/ports/devel/py-pip/ && make FLAVOR=py36 install clean BATCH=yes FORCE=yes
===>   py36-pip-19.1.1 depends on package: py36-pypa-docs-theme>=g20180622 - not found
===>   py36-pypa-docs-theme-g20180622 depends on package: py36-setuptools>0 - not found
===>  Installing for py36-setuptools-41.2.0
===>  Checking if py36-setuptools is already installed
===>   Registering installation for py36-setuptools-41.2.0 as automatic
[nextcloud] Installing py36-setuptools-41.2.0...
pkg-static: py36-setuptools-41.2.0 conflicts with py27-setuptools-40.8.0 (installs files into the same place).  Problematic file: /usr/local/bin/easy_install
*** Error code 70

Stop.
make[2]: stopped in /usr/ports/devel/py-setuptools
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/textproc/py-pypa-docs-theme
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/py-pip
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226634

Gibt es einen Workaround? So ganz verstehe ich die Diskussion im Bug-Report nicht.

Vielleicht mittels
DEFAULT_VERSIONS=python=3.6
in /etc/make.conf? (Nicht vorhanden)

https://www.freshports.org/devel/py-setuptools/
 
Themenstarter #2
Ich habe nun den head des deploy_freenas.py (letsencrypt)scripts versuchsweise auf python2.7 angepasst.

a) In der Hoffnung, dass alle zu importierenden Module bereits vorhanden sind
b) Dass sie sonst mit pip nachzuinstallieren sind.

Pip war allerdings noch nicht installiert, und es fehlte zwar nicht request, aber dafür configparser.
Code:
root@nextcloud:~/deploy-freenas # ./deploy_freenas.py
Traceback (most recent call last):
  File "./deploy_freenas.py", line 25, in <module>
    import configparser
ImportError: No module named configparser
root@nextcloud:~/deploy-freenas # python2.7
Python 2.7.15 (default, Feb  6 2019, 23:39:04)
[GCC 4.2.1 Compatible FreeBSD Clang 6.0.0 (tags/RELEASE_600/final 326565)] on freebsd11
Type "help", "copyright", "credits" or "license" for more information.
>>> pip
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'pip' is not defined
>>>


Nun, ohne pip, erst mal versuchen es nachzuinstallieren mit FLAVOR=py27.
Code:
root@nextcloud:~/deploy-freenas # cd /usr/ports/devel/py-pip/ && make FLAVOR=py27 install clean BATCH=yes FORCE=yes
===>  License MIT accepted by the user
===>   py27-pip-19.1.1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by py27-pip-19.1.1 for building
===>  Extracting for py27-pip-19.1.1
=> SHA256 Checksum OK for pip/setuptools-41.0.1-py2.py3-none-any.whl.
=> SHA256 Checksum OK for pip/wheel-0.33.4-py2.py3-none-any.whl.
=> SHA256 Checksum OK for pip/pypa-pip-19.1.1_GH0.tar.gz.
===>  Patching for py27-pip-19.1.1
===>  Applying FreeBSD patches for py27-pip-19.1.1
===>   py27-pip-19.1.1 depends on package: py27-pypa-docs-theme>=g20180622 - not found
===>  License PSFL accepted by the user
===>   py27-pypa-docs-theme-g20180622 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by py27-pypa-docs-theme-g20180622 for building
===>  Extracting for py27-pypa-docs-theme-g20180622
=> SHA256 Checksum OK for pypa-pypa-docs-theme-g20180622-d2e63fb_GH0.tar.gz.
===>  Patching for py27-pypa-docs-theme-g20180622
===>   py27-pypa-docs-theme-g20180622 depends on package: py27-setuptools>0 - found
===>   py27-pypa-docs-theme-g20180622 depends on file: /usr/local/bin/python2.7 - found
===>  Configuring for py27-pypa-docs-theme-g20180622
running config
===>  Building for py27-pypa-docs-theme-g20180622
running build
running build_py
creating build
creating build/lib
creating build/lib/pypa_theme
copying pypa_theme/__init__.py -> build/lib/pypa_theme
running egg_info
creating pypa_docs_theme.egg-info
writing pypa_docs_theme.egg-info/PKG-INFO
writing top-level names to pypa_docs_theme.egg-info/top_level.txt
writing dependency_links to pypa_docs_theme.egg-info/dependency_links.txt
writing entry points to pypa_docs_theme.egg-info/entry_points.txt
writing manifest file 'pypa_docs_theme.egg-info/SOURCES.txt'
reading manifest file 'pypa_docs_theme.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'pypa_docs_theme.egg-info/SOURCES.txt'
copying pypa_theme/localtoc.html -> build/lib/pypa_theme
copying pypa_theme/theme.conf -> build/lib/pypa_theme
creating build/lib/pypa_theme/static
copying pypa_theme/static/pypa.css -> build/lib/pypa_theme/static
===>  Staging for py27-pypa-docs-theme-g20180622

[...]

===> Creating unique files: Move MAN files needing SUFFIX
===> Creating unique files: Move files needing SUFFIX
Move: bin/pip --> bin/pip-2.7
====> Compressing man pages (compress-man)
===>  Installing for py27-pip-19.1.1
===>  Checking if py27-pip is already installed
===>   Registering installation for py27-pip-19.1.1
[nextcloud] Installing py27-pip-19.1.1...
pip MUST ONLY be used:

* With the --user flag, OR
* To install or manage Python packages in virtual environments

Failure to follow this warning can and will result in an inconsistent
system-wide Python environment (LOCALBASE/lib/pythonX.Y/site-packages) and
cause errors.

Avoid using pip as root unless you know what you're doing.

===>  Cleaning for py27-pypa-docs-theme-g20180622
===>  Cleaning for py27-python-docs-theme-2018.2
===>  Cleaning for py27-pip-19.1.1
root@nextcloud:/usr/ports/devel/py-pip #


Könnte mir bitte nun jemand erklären, was das nun konkret, am Besten anhand eines cmd-line Beispieles, bedeutet? Wie verwende ich nun pip, ohne die Systemumgebung inkonsistent zu machen? Was muss ich dabei beachten?
pip MUST ONLY be used:

* With the --user flag, OR
* To install or manage Python packages in virtual environments


Failure to follow this warning can and will result in an inconsistent
system-wide Python environment

Avoid using pip as root unless you know what you're doing.
Ich habe das hier gefunden, benötige aber ein paar Hinweise.

a) ist mein iocage FreeBSD auf freenas, indem ich 11.2 installiert habe um eine nextcloud Instanz in einem Jail nutzen zu können ein "virtual environment"? Funktioniert dort pip --user nicht?

b) Ich bin mir gerade unsicher, da ich wohl bislang alles als root mache, ob z.B. ein nextcloud user besteht.


Code:
root@nextcloud:/usr/ports/devel/py-pip # users
root
root@nextcloud:/usr/ports/devel/py-pip # id
uid=0(root) gid=0(wheel) groups=0(wheel),5(operator)
root@nextcloud:/usr/ports/devel/py-pip # groups
wheel operator

root@nextcloud:/usr/ports/devel/py-pip # less /etc/group
# $FreeBSD: releng/11.2/etc/group 294896 2016-01-27 06:28:56Z araujo $
#
wheel:*:0:root
daemon:*:1:
kmem:*:2:
sys:*:3:
tty:*:4:
operator:*:5:root
mail:*:6:
bin:*:7:
news:*:8:
man:*:9:
games:*:13:
ftp:*:14:
staff:*:20:
sshd:*:22:
smmsp:*:25:
mailnull:*:26:
guest:*:31:
video:*:44:
bind:*:53:
unbound:*:59:
proxy:*:62:
authpf:*:63:
_pflogd:*:64:
_dhcp:*:65:
uucp:*:66:
dialer:*:68:
network:*:69:
audit:*:77:
www:*:80:
_ypldap:*:160:
hast:*:845:
nogroup:*:65533:
nobody:*:65534:
_tss:*:601:
messagebus:*:556:
avahi:*:558:
cups:*:193:
mysql:*:88:
git_daemon:*:964:
(END)
 
Zuletzt bearbeitet:

Esjott

Kellerkind
#3
Warum nimmst du nicht *einfach* python 3.6? Ist doch mittlerweile default:

Code:
Revision 498529 - (view) (download) (annotate) - [select for diffs]
Modified Wed Apr 10 05:47:26 2019 UTC (5 months ago) by antoine
File length: 4443 byte(s)
Diff to previous 497421
Switch default version of python to 3.6

PR:        234633
With hat:    portmgr
Differential Revision:    https://reviews.freebsd.org/D18743
 
Themenstarter #4
Sorry, kapier ich nicht.


Code:
root@nextcloud:/usr/ports/devel/py-pip # which python
/usr/local/bin/python
root@nextcloud:/usr/ports/devel/py-pip # ls -l /usr/local/bin/python
lrwxr-xr-x  1 root  wheel  24 Sep  8 23:09 /usr/local/bin/python -> /usr/local/bin/python3.6
Das heißt, python36 ist zwar schon installiert, aber offenbar manuel verlinkt, da eher python27 Systemstandard zu sein scheint, wenn man als Maßstab die installierten Pakerte betrachtet: https://pastebin.com/U9CUxyNL
 
Zuletzt bearbeitet:

Esjott

Kellerkind
#6
Scheint komplett durcheinander zu sein dein setup. Du bist auf freenas in einer jail, richtig? schmeiss mal alles was python ist, raus, installier 3.6 und das, was du an py36-foo brauchst, neu. Wenn letzteres nicht klappt, handarbeit in /usr/local (oder setz gleich ne neue jail auf, geht auch ohne iocage im handumdrehen)
 
Themenstarter #7
Keine Ahnung. Was passiert dann mit dem installierten nextcloud?

Ich würde trotzdem gerne mal wissen, was diese Warnung impliziert:

* With the --user flag, OR
* To install or manage Python packages in virtual environments


Außerdem wie „schmeiße ich das heraus“? Wie kann ich erkennen, was per pkg und was per ports installiert wurde?

Gibt es da nicht Abhängigkeiten, die man beachten müsste und neu gelinkt auf python36 kompilieren müsste? (siehe bug #226634)

Siehe auch hier: https://piano2nd.smb.net/PukiWiki/index.php?py2.7 py3.6


Antoine Brodin
2018-05-28 20:00:05 UTC
(In reply to Serge from comment #4)
So you installed samba47 and py27-setuptools with an empty make.conf (hence DEFAULT_VERSIONS=python=2.7) and later installed py36-iocage with make.conf having DEFAULT_VERSIONS=python=3.6 ?

I think this is not supported, DEFAULT_VERSIONS should be constant on 1 host.
Serge 2018-05-29 22:18:37 UTC
Hi Antoine,

I have been trying to understand what is going on, and it looks like I was able to clear things up. I am putting it here in case someone else runs into this problem.

It turns out, that you were actually right about changing DEFAULT_VERSIONS. What happened is py27-setuptools were built on my system with DEFAULT_VERSIONS=python=2.7 and then I set it to DEFAULT_VERSIONS+= python=3.6. So the problem was in the way py27-setuptools was built. When I manually removed it and rebuilt with DEFAULT_VERSIONS+= python=3.6, it became possible to have both py27 and py36 flavours at the same time.

So, you have set me on the right track and I think the flavour system works as intended.

Thank you.
Comment 9 Antoine Brodin
2019-01-04 09:51:54 UTC

Conclusion was "the flavour system works as intended"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226634



2014-03-07Affects: users of devel/py-setuptools dependent ports
Author: sunpoet@FreeBSD.org
Reason:
devel/py-setuptools is being used for every python ports (if USE_PYDISTUTILS
defined) since r336553. Due to PKGORIGIN limitation, we cannot build one
python port with python27 and the other with python33 since they require
different setuptools versions which have same PKGORIGIN. With the addition
of py-setuptools{27,32,33}, we could now have py27-foo and py33-bar coexist
in one system.

Note that this is only a short-term solution. It does not help if you need
coexistence of one port with different python versions, e.g. py27-foo and
py33-foo.

Please rebuild all ports that depend on devel/py-setuptools and use
devel/py-setuptools{27,32,33} instead.

XX represents python version (27, 32 or 33) in the following steps.

pkgng users:

# pkg set -o devel/py-setuptools:devel/py-setuptoolsXX

portmaster users:

# portmaster -o devel/py-setuptoolsXX devel/py-setuptools
# portmaster -r py\*setuptools

portupgrade users:

# portupgrade -o devel/py-setuptoolsXX -f devel/py-setuptools
# portupgrade -fr devel/py-setuptools
https://www.freshports.org/devel/py-setuptools/



(nabble) FreeBSDfreebsd-ports | Python conflict on RPI2
Tatsuki Makino | Reply | Threaded | More

Apr 16, 2019; 4:26am Re: Python conflict on RPI2

72 posts
In reply to this post by Tatsuki Makino
correction

Tatsuki Makino wrote on 2019/04/13 11:07:
>
> py27-cython and py27-sphinx are also cause.
> Probably, pkg query -e %\#r\ =\ 0 -g %n py27-\* ports/packages can be
> deleted in advance.
>

Code:
pkg query -e %n\ ~\ py27-\*\ \&\&\ %\#r\ =\ 0 %n
The previous mail command dredges all py27-* :)
http://freebsd.1045724.x6.nabble.com/Python-conflict-on-RPI2-td6324932.html
 
Zuletzt bearbeitet:
Themenstarter #9
Ja, könnte eventuell sein, da ich nicht besonders vertraut mit freeBSD bin. Ich füge gleich mal history | grep pkg oder so ein.

Okay, das Skript /root/deploy-freenas/deploy_freenas.py könnte auch unter python27 funktionieren.

root@nextcloud:/usr/ports/devel/py-pip # python

Python 3.6.8 (default, Feb 6 2019, 23:39:15)

[GCC 4.2.1 Compatible FreeBSD Clang 6.0.0 (tags/RELEASE_600/final 326565)] on freebsd11

Type "help", "copyright", "credits" or "license" for more information.

>>> pip install --upgrade pip

File "<stdin>", line 1

pip install --upgrade pip

^

SyntaxError: invalid syntax

>>>

root@nextcloud:/usr/ports/devel/py-pip # python2.7

Python 2.7.15 (default, Feb 6 2019, 23:39:04)

[GCC 4.2.1 Compatible FreeBSD Clang 6.0.0 (tags/RELEASE_600/final 326565)] on freebsd11

Type "help", "copyright", "credits" or "license" for more information.

>>> pip install --upgrade pip

File "<stdin>", line 1

pip install --upgrade pip

^

SyntaxError: invalid syntax

>>>

root@nextcloud:/usr/ports/devel/py-pip # which pip-2.7

/usr/local/bin/pip-2.7

root@nextcloud:/usr/ports/devel/py-pip # ln -s /usr/local/bin/pip-2.7 /usr/local/bin/pip

ln: /usr/local/bin/pip: File exists

root@nextcloud:/usr/ports/devel/py-pip # pip --version

pip: Command not found.

root@nextcloud:/usr/ports/devel/py-pip # ls -l /usr/local/bin/pip

lrwxr-xr-x 1 root wheel 22 Sep 8 23:29 /usr/local/bin/pip -> /usr/local/bin/pip-3.6

root@nextcloud:/usr/ports/devel/py-pip # python

Python 3.6.8 (default, Feb 6 2019, 23:39:15)

[GCC 4.2.1 Compatible FreeBSD Clang 6.0.0 (tags/RELEASE_600/final 326565)] on freebsd11

Type "help", "copyright", "credits" or "license" for more information.

>>> pip --version

Traceback (most recent call last):

File "<stdin>", line 1, in <module>

NameError: name 'pip' is not defined

>>>

root@nextcloud:/usr/ports/devel/py-pip # pip --version

pip: Command not found.

root@nextcloud:/usr/ports/devel/py-pip # /usr/local/bin/pip --version

/usr/local/bin/pip: Command not found.

root@nextcloud:/usr/ports/devel/py-pip # ls -l /usr/local/bin/pip-3.6

ls: /usr/local/bin/pip-3.6: No such file or directory

root@nextcloud:/usr/ports/devel/py-pip # ls -l /usr/local/bin/pip*

lrwxr-xr-x 1 root wheel 22 Sep 8 23:29 /usr/local/bin/pip -> /usr/local/bin/pip-3.6

-rwxr-xr-x 1 root wheel 373 Sep 9 12:04 /usr/local/bin/pip-2.7

root@nextcloud:/usr/ports/devel/py-pip # rm /usr/local/bin/pip

root@nextcloud:/usr/ports/devel/py-pip # ln -s /usr/local/bin/pip-2.7 /usr/local/bin/pip

root@nextcloud:/usr/ports/devel/py-pip # pip --version

pip 19.1.1 from /usr/local/lib/python2.7/site-packages/pip (python 2.7)

root@nextcloud:/usr/ports/devel/py-pip # pip install --upgrade pip

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.

Collecting pip

Downloading https://files.pythonhosted.org/pack...d8e6514e675a1/pip-19.2.3-py2.py3-none-any.whl (1.4MB)

|################################| 1.4MB 3.2MB/s

Installing collected packages: pip

Found existing installation: pip 19.1.1

Uninstalling pip-19.1.1:

Successfully uninstalled pip-19.1.1

Successfully installed pip-19.2.3

root@nextcloud:/usr/ports/devel/py-pip # cd /root

root@nextcloud:~ # ls

.acme.sh .cshrc .k5login .login .profile .rnd dbname dbuser occ.sh

.cache .history .lesshst .mysql_history .python_history .ssh dbpassword deploy-freenas post_install.sh

root@nextcloud:~ # ./deploy-freenas/deploy_freenas.py

Traceback (most recent call last):

File "./deploy-freenas/deploy_freenas.py", line 25, in <module>

import configparser

ImportError: No module named configparser

root@nextcloud:~ # pip install configparser --user

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support

Collecting configparser

Downloading https://files.pythonhosted.org/pack...15c14/configparser-4.0.1-py2.py3-none-any.whl

Installing collected packages: configparser

Successfully installed configparser-4.0.1

root@nextcloud:~ # ./deploy-freenas/deploy_freenas.py

Error importing certificate!

<Response [404]>

root@nextcloud:~ #

Hier kann ich vielleicht mit Stuck Deploying Certs using scripts for HTTPS und Let's Encrypt with FreeNAS 11.1 and later 0.3 weiter machen.

Jedenfalls vielen Dank, Esjott! Bezüglich --user flag bei pip install und virtual environments bleiben zwar noch Fragen offen, aber vielleicht kann ich mir das bald selbst beantworten.


history | grep pkg

Code:
   817  22:24   pkg update -f
   846  23:41   pkg install py36-pip
   848  23:51   pkg set -o devel/py-setuptools:devel/py36-setuptools-41.2.0
   850  23:53   pkg install py36-pip
   851  23:53   pkg install py-pip
   862  0:01    pkg set -o devel/py-setuptools:devel/py-setuptools27
   865  0:02    pkg set -o devel/py-setuptools:devel/py27-setuptools-40.8.0
   919  18:12   pkg info
   925  18:20   pkg version -l "<"
 
Zuletzt bearbeitet:
Themenstarter #10
Wahrscheinlich hatte ich ein nextcloud jail howto verwendet, dass auf python27 basierte und auf ports aufbaute.
pkg set -o hatte ich wahrscheinlich schon im Rahmen des Konflikts verwendet und später zurückgesetzt, inklusive zuvor gescheiterte Versuche py36-pip oder py-pip per pkg zu installieren. Später die Abfrage nach allen installierten Paketen. Diese sind aber wohl per ports installiert.

Ich denke, Du hast Recht, und python27 und python36 sollten nicht parallel installiert sein. Das führt zu dem Konflikt mit py-setuptools, wenn man py-pip installieren möchte, da /usr/local/bin/easy_install bereits vorhanden ist.

Ach ja, alles zurückändern auf python27

Code:
root@nextcloud:~ # ls -l /usr/local/bin/python
lrwxr-xr-x  1 root  wheel  24 Sep  8 23:09 /usr/local/bin/python -> /usr/local/bin/python3.6
root@nextcloud:~ # rm /usr/local/bin/python
root@nextcloud:~ # ln /usr/local/bin/python2.7 /usr/local/bin/python
root@nextcloud:~ # rm /usr/local/bin/python
root@nextcloud:~ # ln -s /usr/local/bin/python2.7 /usr/local/bin/python
root@nextcloud:~ # ls -l /usr/local/bin/python
lrwxr-xr-x  1 root  wheel  24 Sep  9 23:31 /usr/local/bin/python -> /usr/local/bin/python2.7
 
Zuletzt bearbeitet:
#11
Spätestens beim nächsten update fliegt dir das wieder um die Ohren, wenn pkg python 3.6 updaten will, genau dann hast du wieder das gleiche Problem.

Die sauberste Lösung ist immer noch python zu deinstallieren und mit allem auf 3.6 zu gehen. Ich würde dabei keine ports verwenden und alles per pkg installieren, nur um konsistenz der versionen zu behalten (per default ist bei pkg das quarterly repo ausgewählt, die ports aber sind tagesaktuell, kann schon für kopfzerbrechen reichen)
Das script auf python 2.7 zu backporten, naja, 2.7 ist outdated.

Versuche doch erstmal mit deiner jail auf einen nachvollziehbaren stand zu kommen - pkg delete python3.6 zeigt dir ja, was alles gelöscht wird, nextcloud sollte davon nicht betroffen sein (keine Abhängigkeit). Ab da könnte man weiter machen, alles was py27-foo im namen hat als py36-foo nachinstallieren, ohne pkg und ports zu mischen. So würde ich vorgehen (und keine scripts benutzen, die irgendwas für einen machen, lieber damit auseinander setzen, wie das unter FreeBSD geht, statt linuxism mit der Brechstange reinzuwürgen :rolleyes:)

Gibt es einen bestimmten Grund für das obscure script? Ich mein, letsencrypt inkl nginx plugin ist als pkg verfügbar (py36-certbot und py36-certbot-nginx wenn ich mich recht erinnere)
 
Themenstarter #12
Ich vermutete bereits, dass nur python3.6 einfach so installiert war, wegen einem tutorial oder so, um pip zu installieren, ka.
Code:
   846  23:41   pkg install py36-pip
   848  23:51   pkg set -o devel/py-setuptools:devel/py36-setuptools-41.2.0
   850  23:53   pkg install py36-pip

Code:
root@nextcloud:~/deploy-freenas # pkg delete python3.6
Updating database digests format: 100%
No packages matched for pattern 'python3.6'

Checking integrity... done (0 conflicting)
1 packages requested for removal: 0 locked, 1 missing


root@nextcloud:~/deploy-freenas # pkg delete python36
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 8 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
        python36-3.6.8
        gobject-introspection-1.56.1,1
        avahi-app-0.7_2
        cups-2.2.10
        ghostscript9-agpl-base-9.26
        ImageMagick6-nox11-6.9.10.22,1
        php71-pecl-imagick-3.4.3_3
        nextcloud-php71-15.0.4

Number of packages to be removed: 8

The operation will free 351 MiB.

Proceed with deinstalling packages? [y/N]: n
root@nextcloud:~/deploy-freenas #
Das Skript soll das letsencrypt renew per nginx für nextcloud@freenas übernehmen.
/root/deploy-freenas/deploy_freenas.py

Let's Encrypt with FreeNAS 11.1 and later 0.3
Integrating Let’s Encrypt TLS Certificates with FreeNAS

FreeNAS has long had the ability to use HTTPS for the web GUI, but that has usually meant dealing with self-signed certificates and the associated headaches, or paying for a commercial certificate. With the launch of Let’s Encrypt in December 2015, trusted TLS certificates became available at no cost. However, their short lifetime, as well as the requirement to use other software tools to issue them, has caused some challenges in integrating them into the FreeNAS web GUI.

With the release of FreeNAS 11.1, the FreeNAS API now has all the hooks needed for a script to automate deployment of a certificate. This resource will describe two methods for obtaining a certificate for your FreeNAS box. It will also describe how to automate deployment of the certificate. The goal is that the certificate will be issued (and renewed) and deployed automatically, and you won’t need to manually deal with it ever again.
https://www.ixsystems.com/community/resources/lets-encrypt-with-freenas-11-1-and-later.82/

Daher nutze ich auch acme.sh für Let's Encrypt Zertifikate.