Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moduleset error horror #14

Closed
totaam opened this issue Dec 30, 2016 · 6 comments
Closed

moduleset error horror #14

totaam opened this issue Dec 30, 2016 · 6 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Dec 30, 2016

Issue migrated from trac ticket # 1392

component: packaging | priority: critical | resolution: worksforme | keywords: osx

2016-12-30 06:03:43: antoine created the issue


It started with some updates from trunk that should be applied to v1.0.x (see #13):

  • 14657: libpng
  • 14658 + r14661: mpfr
  • 14659: opus (+14662 which is buggy)
  • 14663: switch all moduleset links to "tags/v1.0.x"

jhbuild was then failing with the totally unhelpful:

jhbuild update: failed to parse /Users/osx/Source/jhbuild/modulesets/http:/xpra.org/svn/Xpra/tags/v1.0.x/osx/jhbuild/xpra.modules: \
  [Errno 2] No such file or directory: \
  u'/Users/osx/Source/jhbuild/modulesets/http:/xpra.org/svn/Xpra/tags/v1.0.x/osx/jhbuild/xpra.modules'

So 14664 moved "xpra.modules" to "modulesets-stable", which allowed me to continue (after downloading it into "~/Source/jhbuild/modulesets" by hand).
This uncovered an error in the 14662 changeset, fixed in 14665.
14666 moved "xpra.modules" back to where it was (a URL link) but unfortunately it still fails with the same error.
Whatever the problem is, it's really not obvious to me.

@totaam
Copy link
Collaborator Author

totaam commented Jan 23, 2017

2017-01-23 10:04:17: antoine changed owner from antoine to smo

@totaam
Copy link
Collaborator Author

totaam commented Jan 23, 2017

2017-01-23 10:04:17: antoine commented


@smo: please advise on which updates from trunk (#1404) are applicable to the 1.x branch.
Then I'll give this another go, copying the module files by hand if needed.

@totaam
Copy link
Collaborator Author

totaam commented Jan 24, 2017

2017-01-24 20:21:05: smo commented


Okay I've updated the other ticket.

@totaam
Copy link
Collaborator Author

totaam commented Jan 26, 2017

Rebuild from scratch with the updates from Xpra-org/xpra#1404#comment:9 worked OK.
Closing.

@totaam totaam closed this as completed Jan 26, 2017
@totaam
Copy link
Collaborator Author

totaam commented Mar 25, 2017

Hit it again after r15394 which had some small mistakes in it:

Tried moving things around (r15397), no help.
Then digging into the jhbuild code in ~/Source/jhbuild/jhbuild//moduleset.py, I find that they're swallowing the exception details (PITA), so I replaced the exception code with this:

def _parse_module_set(config, uri):
    try:
        filename = httpcache.load(uri, nonetwork=config.nonetwork, age=0)
    except Exception as e:
        raise FatalError(_('could not download %s: %s') % (uri, e))
    filename = os.path.normpath(filename)
    try:
        document = xml.dom.minidom.parse(filename)
    except IOError as e:
        import traceback
        traceback.print_stack()
        #raise FatalError(_('failed to parse %s: %s') % (filename, e))
        raise
    except xml.parsers.expat.ExpatError as e:
        #raise FatalError(_('failed to parse %s: %s') % (uri, e))
        import traceback
        traceback.print_stack()
        raise

And got the details needed instead of the utterly useless original exception message. Immediately found the problem, fixed in r15398. (could also have been found by opening the file with a validating XML parser)
Why on earth isn't this the default??

@totaam
Copy link
Collaborator Author

totaam commented Aug 12, 2019

Similar hidden error in jhbuild: #7#comment:1

@totaam totaam transferred this issue from Xpra-org/xpra Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant