charm-tools from the juju/stable ppa is not installable on trusty

[vilagithub]

On a fresh trusty host, with the ppa:juju/stable https://launchpad.net/~juju/+archive/ubuntu/stable/

apt-get install charm-tools fails with:

The following packages have unmet dependencies:
charm-tools : Depends: python-libcharmstore (>= 0.0.3) but it is not installable

The last libcharmstore upload for trusty https://launchpadlibrarian.net/295590003/buildlog_ubuntu-trusty-i386.libcharmstore_0.0.6-0ubuntu1~ubuntu14.04.1~ppa2_BUILDING.txt.gz failed with:

make[1]: /bin/nosetests: Command not found

[chuckbutler]

@vilagithub - if you're not opposed to trying something new, charm + charm-tools have refocused under snaps. Snapd is now installable on Trusty, and you can test this path which should have you running the latest and greatest of the developer tooling in a nice auto-refreshing fashion under snaps

sudo apt-get install -y snapd 
sudo apt purge charm charm-tools (respectively)
sudo snap install charm --classic

If you encounter any issues here we'd love to hear the feedback on how this went for you and if this resolved your issue with the current apt-package. I do believe the deb is a few releases behind the snap package, and efforts have been doubled on focusing on the snap path as charm-tools is a fast moving project.

[vilagithub]

That doesn't seem to work inside an lxd container which is where I need it :-/

$ sudo snap install charm --classic
error: cannot communicate with server: Post http://localhost/v2/snaps/charm: dial unix /run/snapd-snap.socket: connect: no such file or directory

[nskaggs]

@vilagithub install squashfuse in the container first; it should work.

Also see https://bugs.launchpad.net/snappy/+bug/1611078.

EDIT -- Ohh right, you are on trusty.

[shawn111]

Hello,

I run charm(snap) on trusty, but got below issue.
It only happened on trusty, but good on xenial.
I didn't test charm(snap) in container.

$ charm build
Traceback (most recent call last):
File "/snap/charm/11/bin/charm-build", line 7, in
from charmtools.build.builder import main
File "/snap/charm/11/lib/python2.7/site-packages/charmtools/build/init.py", line 6, in
from builder import (
File "/snap/charm/11/lib/python2.7/site-packages/charmtools/build/builder.py", line 16, in
from charmtools import (utils, repofinder, proof)
File "/snap/charm/11/lib/python2.7/site-packages/charmtools/proof.py", line 23, in
from charms import Charm
File "/snap/charm/11/lib/python2.7/site-packages/charmtools/charms.py", line 13, in
from launchpadlib.launchpad import Launchpad
File "/snap/charm/11/lib/python2.7/site-packages/launchpadlib/launchpad.py", line 33, in
from httplib2 import proxy_info_from_environment
File "/snap/charm/11/lib/python2.7/site-packages/httplib2/init.py", line 930, in
class HTTPSConnectionWithTimeout(httplib.HTTPSConnection):
AttributeError: 'module' object has no attribute 'HTTPSConnection'

[vilagithub]

According to https://bugs.launchpad.net/snappy/+bug/1628289/comments/18 using the charm snap in a trusty container is a no-go.

Is there a way to un-break trusty support in the https://launchpad.net/~juju/+archive/ubuntu/stable/ ppa while we migrate to xenial/snaps in the various affected environments ?

[chuckbutler]

cc @marcoceppi on this issue. It looks like despite our best efforts we have an orphaned package.

[arosales]

The other issue this brings up is Travis testing is also failing as they only offer Trusty buids, aiui Travis doesn't include Xenial testing atm.

[johnsca]

@arosales is correct that Travis doesn't support Xenial. We also ran in to an issue trying to use the snap in Travis, so we're completely blocked on this now for getting passing Travis builds.

[vilagithub]

For the record, https://launchpad.net/~ubuntuone/+archive/ubuntu/charm-tools now has trusty versions working for charm-tools and libcharmstore so we're out of trouble until we migrate to either xenial or the snap.

[marcoceppi]

An update python-libcharmstore is now in the stable ppa (thanks @vilagithub)