Solved xorg upgrading, problems with some dependencies

P

pierre

Hi
I am upgrading xorg-server. Some dependencies, python libraries failed to build, so I downloaded the tarballs and installed them manually with python setup.py install
Please have a look to my previous post
https://forums.freebsd.org/threads/devel-py-jinja2-buid-failed.49196/
these libraries are installed in
/usr/local/lib/python2.7/site-packages/jinja2
/usr/local/lib/python2.7/site-packages/markupsafe
/usr/local/lib/python2.7/site-packages/babel
I assume it's fine.
Now, running portmaster -r xorg-server again, these packages still required,
Code: 
....
Install devel/py-Jinja2
Install textproc/py-MarkupSafe
....
then the process will stop

I have probably to register the installation of Jinja2, markupsafe, babel!
But How to proceed?
Thanks!
 
Manually installing dependencies defeats the purpose of the package database. The database is more than a list of just which packages are installed. Each includes a list of all the files it installed, and checksums to test whether a file has been modified. It would be best to go back and find out what the problem was with those ports, then install them.
 
That what I thought, but it's because I couldn't solve it that I did this way.
I will uninstall the 3 python libraries, if I can and go back.
The outputs will remains the same.
What could be the meaning of
Code: 
error: option --single-version-externally-managed not recognized
?
 
What do you have in your environment? Those packages compile fine for me on 10.1-RELEASE. On top of that the ports have not been updated for a while. If there were issues building the ports they likely would have been resolved since your November thread. Can you show what is in your make.conf and describe anything unique about your environment that could prevent them from compiling?
 
junovitch said:
What do you have in your environment? Those packages compile fine for me on 10.1-RELEASE. On top of that the ports have not been updated for a while. If there were issues building the ports they likely would have been resolved since your November thread. Can you show what is in your make.conf and describe anything unique about your environment that could prevent them from compiling?
Click to expand...
I have updated the ports 3 days ago and planned a complete upgrade. but it's take such a time, so I decided to start with xorg-server. (from 1.12 to 1.14). I am facing the same problem that I gave up in november.
/etc/make.conf
Code: 
DEFAULT_VERSIONS+=ruby=1.9
env
Code: 
HOST=cotuit.conodor.local
DISPLAY=:0.0
WINDOWID=31457312
SHELL=/bin/csh
SESSION_MANAGER=local/cotuit.conodor.local:/tmp/.ICE-unix/933
MACHTYPE=x86_64
BLOCKSIZE=K
EDITOR=vi
COLORTERM=mate-terminal
OSTYPE=FreeBSD
GROUP=pierre
DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-UDBRrJRsb3,guid=280776d3a50824c3fedea4ea54d7f2fb
VENDOR=amd
HOME=/root
LANG=fr_FR.UTF-8
LOGNAME=pierre
TERM=xterm
PAGER=more
MAIL=/var/mail/pierre
MATE_DESKTOP_SESSION_ID=this-is-deprecated
SHLVL=3
XAUTHORITY=/home/pierre/.Xauthority
PWD=/home/pierre
MM_CHARSET=UTF-8
WINDOWPATH=9
USER=pierre
CLICOLOR=true
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
HOSTTYPE=FreeBSD
 
How far behind are you on updates? The only 'single-version' line I found was in the devel/py-setuptools27 package. Does /usr/ports/UPDATING entry 20140307 apply?

less -p 20140307 /usr/ports/UPDATING
Code: 
20140307:
  AFFECTS: users of devel/py-setuptools dependent ports
  AUTHOR: sunpoet@FreeBSD.org

  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
 
devel/py-setuptools27 is installed, not devel/py-setuptools.
I tried to run
portmaster -r py\*setuptools
and the output is similar
Code: 
===>  Staging for py27-tkinter-2.7.9_5
===>  Generating temporary packing list
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
  or: setup.py --help [cmd1 cmd2 ...]
  or: setup.py --help-commands
  or: setup.py cmd --help

error: option --single-version-externally-managed not recognized
*** Error code 1

Stop.
make: stopped in /usr/ports/x11-toolkits/py-tkinter

===>>> make stage failed for x11-toolkits/py-tkinter
===>>> Aborting update

===>>> Update for py27-tkinter-2.7.8_5 failed
===>>> Aborting update ....
 
I own another FreeBSD machine (let us call it 2), py-Babel, py-Jinja2, py-markupsafe have been installed properly on.
With the main machine, I launched a test in a py-xxxx source directory, I ran setup.py --help-commands, it output a part of previous error messages:
Code: 
/usr/local/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'entry_points'
  warnings.warn(msg)
/usr/local/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'zip_safe'
  warnings.warn(msg)
/usr/local/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'install_requires'
.
On the machine 2, the same test didn't output any error/warnings message. At this step, I think I will not be able to build any py libraries.
 
Your Python version might be outdated?

If python -V shows a lesser version than 2.7.9 you have to work on this.

grep python /etc/make.conf should have an output like this:
Code: 
DEFAULT_VERSIONS=python=2.7 python2=2.7 perl=perl5.18
 
My Python version is 2.7.9.
Is it mandatory to have a make.conf? I created one to keep the previous version of Ruby. I erased it today after upgrading to Ruby 2.0.
 
You don't need an /etc/make.conf. It's only for changing the defaults.

Here is what I would do:
1. Make a list of packages you asked to be installed. You should probably check it too.
pkg query -e '%a = 0' %o > /tmp/my_packages
2. Delete all the Python packages
pkg delete -x "py27|python"
3. Delete any junk that might have been installed by installing Python stuff outside the package system.
rm -r /usr/local/lib/python2.7
4. Install all your packages back, this syntax is sh(1) compatible.
for package in `cat /tmp/my_packages`; do pkg install -y $package; done
 
You must log in or register to reply here.
Back
Top