Re: pkg problems
Francesco Steno <[email protected]> Wed, 17 Sep 2014 11:07:14 +0200
| Newsgroups | gmane.os.freebsd.italian.aiuto |
|---|---|
| Message-ID | <[email protected]> |
Il giorno 17/set/2014, alle ore 10:51, Cristiano Deana <[email protected]> ha scritto: > 2014-09-17 10:41 GMT+02:00 Francesco Steno <[email protected]>: > >>>> Da quel che ho imparato, quando passi a pkg, DEVI dimenticarti i comandi >>>> vecchi (quelli con _ per capirci). E DEVI segnalare nel make.conf che >>>> stai utilizzando pkg con la direttiva WITH_PKGNG=yes. Altrimenti >>>> utilizzando un po' di comandi pkg e un po' pkg_"vecchio" si genera solo >>>> ca..no. >>>> Utilizza questa tabellina https://wiki.freebsd.org/PkgPrimer > >> io però ho una domanda … in questo modo non andrei poi a lavorare con i binary package ? >> (ammesso che io risolva il problema … ovviamente …) … > > se usi pkg per installare/upgradare allora userai i binari, se usi i > ports (o portupgrade ad esempio) userai i ports e sono tutti > compatibili e felici. > Se "interroghi" solo, ad esempio `pkg info', lui lavora sul db comune > dei pkg/ports installati. ok, resta sempre il dilemma del perché non mi aggiorna i ports, ===>>> The following actions will be taken if you choose to proceed: Re-install db48-4.8.30.0_2 Upgrade cmake-2.8.12.1_4 to cmake-3.0.1_1 Install textproc/py-sphinx Install devel/py-Jinja2 Install devel/py-babel Install devel/py-pytz Install textproc/py-docutils Install textproc/py-pygments Upgrade mod_php55-5.5.15_1 to mod_php55-5.5.16 Upgrade phpMyAdmin-4.2.7.1 to phpMyAdmin-4.2.8.1 Upgrade ruby-1.9.3.547,1 to ruby-1.9.3.547_3,1 ===>>> Proceed? y/n [y] [snip] ===> Cleaning for py27-pytz-2014.4,1 ===> License MIT accepted by the user ===> py27-pytz-2014.4,1 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by py27-pytz-2014.4,1 for building ===> Extracting for py27-pytz-2014.4,1 => SHA256 Checksum OK for pytz-2014.4.tar.bz2. ===> Patching for py27-pytz-2014.4,1 ===> py27-pytz-2014.4,1 depends on package: py27-setuptools27>0 - found ===> py27-pytz-2014.4,1 depends on file: /usr/local/bin/python2.7 - found ===> Configuring for py27-pytz-2014.4,1 Traceback (most recent call last): File "<string>", line 1, in <module> File "setup.py", line 5, in <module> import pytz, sys, os, os.path File "pytz/__init__.py", line 37, in <module> from pytz.lazy import LazyDict, LazyList, LazySet File "pytz/lazy.py", line 1, in <module> from threading import RLock File "/usr/local/lib/python2.7/threading.py", line 6, in <module> import thread ImportError: No module named thread *** [do-configure] Error code 1 Stop in /usr/ports/devel/py-pytz. ===>>> make build failed for devel/py-pytz ===>>> Aborting update ===>>> Update for devel/py-pytz failed ===>>> Aborting update ===>>> Update for devel/py-babel failed ===>>> Aborting update ===>>> Update for devel/py-Jinja2 failed ===>>> Aborting update ===>>> Update for textproc/py-sphinx failed ===>>> Aborting update ===>>> Update for devel/cmake failed ===>>> Aborting update ===>>> The following actions were performed: Re-installation of db48-4.8.30.0_2 ===>>> You can restart from the point of failure with this command line: portmaster <flags> devel/cmake textproc/py-sphinx devel/py-Jinja2 devel/py-babel devel/py-pytz textproc/py-docutils textproc/py-pygments www/mod_php55 databases/phpmyadmin lang/ruby19 sono proprio nella ca__a … questo è un ambiente che poi devo portare in produzione …. … _______________________________________________ Aiuto mailing list [email protected] http://mailman.gufi.org/mailman/listinfo/aiuto
signature.asc
(application/pgp-signature, 203 B)
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlQZT1AACgkQmhAtHzlzwgOCIQCeJB85aohobpH9cZxjt20wStCs jpoAn0PjQE4rRtK8EXJuAs2jE2Jo2n5D =yNBF -----END PGP SIGNATURE-----