Please see also bug 15481 Websockify is missing a require on python-pkg-resources. eg. $ novnc_server Warning: could not find self.pem Starting webserver and WebSockets proxy on port 6080 Traceback (most recent call last): File "/usr/bin/websockify", line 5, in <module> from pkg_resources import load_entry_point ImportError: No module named pkg_resources Failed to start WebSockets proxy Fixed by installing python-pkg-resources Reproducible: Steps to Reproduce:
Tidying bug report...
Keywords: (none) => Junior_jobHardware: i586 => AllSource RPM: (none) => websockify
Freeze push requested for Cauldron.
Advisory: ---------------------------------------- The websockify program requires the pkg_resources Python module, but the websockify package didn't require the package that contains this module. This has now been corrected. ---------------------------------------- Updated packages in core/updates_testing: ---------------------------------------- python-websockify-0.5.1-3.1.mga4 websockify-0.5.1-3.1.mga4 python3-websockify-0.5.1-3.1.mga4 from python-websockify-0.5.1-3.1.mga4.src.rpm
Keywords: Junior_job => (none)Assignee: bugsquad => qa-bugs
Testing complete mga4 64 Before ------ # urpmq --requires python-websockify | grep pkg --requires behaviour changed, use --requires-recursive to get the old behaviour After ----- # urpmq --requires python-websockify --media Testing | grep pkg --requires behaviour changed, use --requires-recursive to get the old behaviour python-websockify: python-pkg-resources
Whiteboard: (none) => mga4-64-ok
In fact, the require is added to the python-websockify package but /usr/bin/websockify is provided by the websockify package, which itself has no requires. So this looks to add the require to the wrong one. Adding feedback marker.
Whiteboard: mga4-64-ok => feedback
D'oh, the SRPM name confused me. Thanks for catching that. I just fixed it in SVN and asked for another freeze push in Cauldron.
python-websockify-0.5.1-3.1.mga4 has now been submitted (also the same fix is in Cauldron).
Whiteboard: feedback => (none)
Once madb will have synced, an easy way to check is to use the RPMs page from the update candidate list. The diff links will show every change. We should see only added requires. http://mageia.madb.org/tools/listRpmsForQaBug/bugnum/15622/application/0
CC: (none) => stormi
Testing complete mga4 64 Verified the altered require and tested with novnc as comment 0
Whiteboard: (none) => has_procedure mga4-64-ok
Advisory uploaded.
Whiteboard: has_procedure mga4-64-ok => has_procedure advisory mga4-64-ok
Testing complete mga4 32 Validating. Please push to 4 updates Thanks
Keywords: (none) => validated_updateWhiteboard: has_procedure advisory mga4-64-ok => has_procedure advisory mga4-64-ok mga4-32-okCC: (none) => sysadmin-bugs
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0039.html
Status: NEW => RESOLVEDResolution: (none) => FIXED