Update to 0.5.0 fails with "pg_config executable not found"

[sticilface]

Saw you rolled the update into 0.5.0. Trying to update through the GUI...

Updating, please wait.
Collecting https://github.com/malnvenshorn/OctoPrint-FilamentManager/archive/0.5.0.zip
Downloading https://github.com/malnvenshorn/OctoPrint-FilamentManager/archive/0.5.0.zip (235kB)
Requirement already satisfied: OctoPrint in /home/pi/oprint/lib/python2.7/site-packages/OctoPrint-1.3.6-py2.7.egg (from OctoPrint-FilamentManager==0.5.0)
Requirement already satisfied: backports.csv<1.1,>=1.0.5 in /home/pi/oprint/lib/python2.7/site-packages (from OctoPrint-FilamentManager==0.5.0)
Collecting SQLAlchemy<1.2,>=1.1.15 (from OctoPrint-FilamentManager==0.5.0)
Using cached SQLAlchemy-1.1.15.tar.gz
Collecting psycopg2<2.8,>=2.7.3 (from OctoPrint-FilamentManager==0.5.0)
Using cached psycopg2-2.7.3.2.tar.gz
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-YWr_EX/psycopg2/
Complete output from command python setup.py egg_info:
running egg_info
creating pip-egg-info/psycopg2.egg-info
writing pip-egg-info/psycopg2.egg-info/PKG-INFO
writing top-level names to pip-egg-info/psycopg2.egg-info/top_level.txt
writing dependency_links to pip-egg-info/psycopg2.egg-info/dependency_links.txt
writing manifest file 'pip-egg-info/psycopg2.egg-info/SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
Error: pg_config executable not found.
Please add the directory containing pg_config to the PATH
or specify the full executable path with the option:
python setup.py build_ext --pg-config /path/to/pg_config build ...
or with the pg_config option in 'setup.cfg'.
----------------------------------------
The update did not finish successfully. Please consult the log for details.

any clues?

[ghost]

Hi @sticilface,

It looks like there is some information missing in your ticket that will be needed in order to reproduce and fix the problem at hand. Please take a look at the Issue Template, which will tell you exactly what your ticket has to contain in order to be processable.

If you did not intend to report a bug but have a question or want to request a feature add a "[Question]" respectively "[Request]" prefix to the title.

I'm marking this one now as an incomplete ticket. Please understand that if you do not provide that information within the next two weeks (until 2017-12-26 15:15) I'll close this ticket so it doesn't clutter the bug tracker.

Best regards,
~ Your FriendlyGithubBot

PS: I'm just an automated script, not a human being.

[Angelinsky7]

What were you doing?
Updating with GUI

What did you expect to happen?
To update without issue

What happened instead?
same as @sticilface post

Link to octoprint.log
irrelevant

Link to gcode file
irrelevant

Link to contents of Javascript console in the browser
irrelevant

Further information
none

[malnvenshorn]

Try apt-get install libpq5 on raspbian/debian or respectively pacman -Sy postgresql-libs if you're running arch linux.

[Angelinsky7]

Hi,
Sadly, after updating, upgrading, installing libpq5 and rebooting the error is still there

[Angelinsky7]

apt-get remove libpq5
apt-get install libpq-dev

did the trick...
it's sad that those libs aren't installed automatically with the gui...

[malnvenshorn]

Added the required dependencies to the README and the release notes.

[Turtletrumpet]

Thanks for this great plugin!

[malnvenshorn]

it's sad that those libs aren't installed automatically with the gui...

Sadly I cannot ship this with the release. There exists a libpq-dev python package but it needs to be installed with the same version as PostgreSQL and I cannot predict the PostgreSQL version provided by your distribution. If someone knows a solution please tell me.

[Angelinsky7]

did you

apt-get update
apt-get dist-upgrade -y
apt-get upgrade -y

before ??

[malnvenshorn]

@Angelinsky7 Are you referring to me? I've no debian (based) distribution running.

[Angelinsky7]

@malnvenshorn no sorry i received a mail from that thread but it didn't appear here... (???)
so i answered here before noticing that it was a direct question....

[Angelinsky7]

@malnvenshorn thanks anyway for your help :-)

[bryanhunwardsen]

Not sure what the library is being leveraged for, thought Id add that a great deal many people run octoprint off of raspian/octopi, not many will be able to trace error here or manually fix as detailed. Would suggest finding alternate implementation removing this dependency(I have 20+ plugins installed and another 15-20 that i tried and uninstalled for various reasons) none of which was not manageable through the gui. This is such a great plugin, I only wish it to be useable by all! In the meantime, Id humbly suggest explicitly capturing this error and tailing the failure with a verbose human log statement that points directly to the readme and the issue detailed in a simple format to it is easilly understood and recoverable by perople who may not be comfortable in github or at an ssh terminal. regards, hope you can find a long term solution to support ui only management.

[malnvenshorn]

The library is required because the Python module for the PostgreSQL support uses the libpq client library. I totally agree with you that this is not the ideal situation now.

I cannot capture this error because it appears during the installation process (at least I don't know how), but even if it were possible I don't think it would make a difference. The amount of tickets showed that many people don't read the output or the log files.

I removed the psycopg2 module, required for the PostgreSQL support, from the dependencies for the plugin version. This shifts the "issue" only to the people who are using PostgreSQL as their database. They have to install this module manually.