551329 - After updating to newest version cuddlefish stopped to create XPI

Status: RESOLVED WORKSFORME

(Add-on SDK Graveyard :: General, enhancement, P1)

Description

[Piotr Zalewa [:zalun]]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.2 (KHTML, like Gecko) Chrome/5.0.342.1 Safari/533.2
Build Identifier: hg clone http://hg.mozilla.org/labs/jetpack-sdk/

Except of changing the jetpak-sdk nothing was changed - the same setup is working on http://flightdeck.zalewa.info/
After updating on my system I started to receive following error:

Traceback (most recent call last):
  File "/home/zalun/Projects/FlightDeck/flightdeckenv/bin/cfx", line 6, in <module>
    cuddlefish.run()
  File "/home/zalun/Projects/FlightDeck/flightdeckenv/lib/python2.6/site-packages/cuddlefish/__init__.py", line 292, in run
    pkg_cfg = packaging.build_config(env_root, target_cfg)
  File "/home/zalun/Projects/FlightDeck/flightdeckenv/lib/python2.6/site-packages/cuddlefish/packaging.py", line 136, in build_config
    pkgconfig = get_config_in_dir(path)
  File "/home/zalun/Projects/FlightDeck/flightdeckenv/lib/python2.6/site-packages/cuddlefish/packaging.py", line 86, in get_config_in_dir
    path))
cuddlefish.packaging.MalformedPackageError: package.json not found in "/home/zalun/Projects/FlightDeck/flightdeckenv/packages/packages"

/home/zalun/Projects/FlightDeck/flightdeckenv/lib/python2.6/site-packages/cuddlefish is just a link to the cuddlefish within the jetpack-sdk/python-lib
/home/zalun/Projects/FlightDeck/flightdeckenv/packages is a link to jetpack-sdk/packages

Reproducible: Always



Expected Results:  
XPI should be created

Comment 1

[Atul Varma [:atul]]

Unfortunately, from the traceback alone I can't figure out what's going on. Steps to reproduce this error from a fresh checkout would be really helpful; barring that, the exact commandline and CUDDLEFISH_ROOT environment variable would be helpful, as well as the current working directory.

Also, which version of the jetpack-sdk repo were you at before you pulled the new version?

Comment 2

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

Sounds somewhat similar to Dolske's problem in bug 549776 (completely different problems, but it was also an issue with symlinks)

Comment 3

[Atul Varma [:atul]]

Yeah, but since that issue's fixed, I'm not sure what's going on here... :(

Comment 4

[Daniel Buchner [:dbuc]]

I think Piotr is going to try something with his implementation and get back to this thread with the result - cross your fingers, this may be solved!

Comment 5

[Piotr Zalewa [:zalun]]

Yes - Now in my local installation I've got one rotating link, it may be I've broken it while solving the issue, but I'll have to check.

Comment 6

[Myk Melez [:myk] [@mykmelez]]

Piotr: it's unclear from your last comment... are you still experiencing this problem, and have you found a workaround?

Comment 7

[Atul Varma [:atul]]

Piotr's response in bug 550082 comment 5 seems to imply that he found a workaround, since I assume he couldn't have tested the FD addon without having resolved this bug.

Will reopen this bug if this proves not to be the case.

Comment 8

[Myk Melez [:myk] [@mykmelez]]

The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".