"undefined" charm owner in Preview sidebar #245

Closed
ursinha opened this Issue Apr 8, 2016 · 4 comments

Comments

Projects
None yet
4 participants

ursinha commented Apr 8, 2016

A new version of landscape-server charm was uploaded to the store yesterday, and as can be seen at https://jujucharms.com/landscape-server/trusty/14, the owner of the charm in the Preview sidepanel says "undefined" (which amusingly links to an existing user in launchpad):
preview-undefined

Previous version (https://jujucharms.com/landscape-server/trusty/13) displays the right owner, landscape-charmers.

ursinha commented Apr 8, 2016

bac pointed that landscape-server is not the only one with this problem: https://jujucharms.com/u/juju-gui-charmers/juju-gui/trusty/53. At the top it says "by charmers", it is the "card" at the bottom right that displays the problem.

Member

anthonydillon commented Apr 8, 2016

This has been fixed in the latest release of Juju cards (1.2.0). This has
been committed to the jujucharms code base and will be live with the next
release of jujucharms.

On Fri, 8 Apr 2016, 21:07 Ursula Junque (Ursinha), notifications@github.com
wrote:

bac pointed that landscape-server is not the only one with this problem:
https://jujucharms.com/u/juju-gui-charmers/juju-gui/trusty/53. At the top
it says "by charmers", it is the "card" at the bottom right that displays
the problem.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#245 (comment)

@urosj urosj added the fix-committed label Apr 14, 2016

@urosj urosj added this to the 0.1.44 milestone Apr 14, 2016

johnsca commented Apr 18, 2016

We have been able to work around this for the big data charms by setting the bzr-owner under extra-info:

charm set cs:~bigdata-charmers/apache-hadoop-namenode bzr-owner=bigdata-charmers

But, clearly, this is not ideal and I'm looking forward to the proper fix.

Member

anthonydillon commented May 19, 2016

This has gone live. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment