[Slackbuilds-users] supervisor issues

[Miguel De Anda]

i'm trying to setup supervisord and i ran into a few issues i thought
i'd share. i'm configuring it in a docker container where i installed
all slackware packages using the following Dockerfile:



========================

FROM vbatts/slackware
MAINTAINER Miguel miguel at thedeanda.com

RUN echo "BATCH=on" >> /etc/slackpkg/slackpkg.conf
RUN echo "DEFAULT_ANSWER=y" >> /etc/slackpkg/slackpkg.conf
RUN echo "http://mylocalmirror/slackware64-14.1/" > /etc/slackpkg/mirrors
RUN echo "kdei" >> /etc/slackpkg/blacklist

RUN slackpkg update
RUN slackpkg reinstall *
RUN slackpkg install-new

RUN slackpkg install a/*
RUN slackpkg install ap/*
RUN slackpkg install d/*
RUN slackpkg install l/*
RUN slackpkg install n/*
RUN slackpkg install t/*
RUN slackpkg install tcl/*
RUN slackpkg install x/*
RUN slackpkg install xap/*
RUN slackpkg install y/*

========================

then i ran it and installed pysetuptools and supervisor:



========================

root at ea5f05b08549:/# upgradepkg --install-new *.t?z

+==============================================================================
| Installing new package ./pysetuptools-18.0.1-x86_64-1_SBo.tgz
+==============================================================================

Verifying package pysetuptools-18.0.1-x86_64-1_SBo.tgz.
Installing package pysetuptools-18.0.1-x86_64-1_SBo.tgz:
PACKAGE DESCRIPTION:
# pysetuptools (a collection of enhancements to Python distutils)
#
# Easily build, install, upgrade, and uninstall Python packages!
#
# Setuptools is a fully-featured, actively-maintained, and stable
# library designed to facilitate packaging Python projects, where
# packaging includes Python package and module definitions,
# distribution package metadata, test hooks, project installation,
# platform-specific details, and Python 3 support.
#
Package pysetuptools-18.0.1-x86_64-1_SBo.tgz installed.


+==============================================================================
| Installing new package ./supervisor-3.1.1-x86_64-2_SBo.tgz
+==============================================================================

Verifying package supervisor-3.1.1-x86_64-2_SBo.tgz.
Installing package supervisor-3.1.1-x86_64-2_SBo.tgz:
PACKAGE DESCRIPTION:
# supervisor (A system for controlling process state under UNIX)
#
# Supervisor is a client/server system that allows its users to
# monitor and control a number of processes on UNIX-like operating
# systems.
#
# It shares some of the same goals of programs like launchd,
# daemontools, and runit.
#
# Homepage: http://supervisord.org/
#
Executing install script for supervisor-3.1.1-x86_64-2_SBo.tgz.
Package supervisor-3.1.1-x86_64-2_SBo.tgz installed.

========================

when i try to launch supervisor, i get:



========================

root at ea5f05b08549:/# supervisord
Traceback (most recent call last):
  File "/usr/bin/supervisord", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 3084, in <module>
    @_call_aside
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 3070, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 3097, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 651, in _build_master
    ws.require(__requires__)
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 952, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 839, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'meld3>=0.6.5' distribution
was not found and is required by supervisor
root at ea5f05b08549:/#


========================

if i install pip and run pip install supervisor it works so i'm not
sure if i'm doing something wrong. i believe i had a similar issue
when i tried setting up supervisor natively on the host instance.

-m