Bug 21836 - update request: nagstamon
Summary: update request: nagstamon
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA6-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2017-10-11 22:45 CEST by Guillaume Rousse
Modified: 2018-01-07 23:54 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Guillaume Rousse 2017-10-11 22:45:57 CEST
The nagstamon package shipped in mageia 6 lacks some runtimes dependencies on external python modules. As a consequence, it doesn't run without installing them manually:
[guillaume@netchaiev ~]$ nagstamon 
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/Nagstamon/Config.py", line 606, in KeyringAvailable
    import secretstorage
ImportError: No module named 'secretstorage'
Traceback (most recent call last):
  File "/usr/bin/nagstamon", line 60, in <module>
    from Nagstamon.QUI import (APP,
  File "/usr/lib/python3.5/site-packages/Nagstamon/QUI/__init__.py", line 23, in <module>
    from PyQt5.QtWidgets import *
ImportError: No module named 'PyQt5'

The nagstamon-2.0.1-1.1.mga6 release, from mageia 6 core/updates_testing, fix the issue.
Comment 1 Herman Viaene 2017-10-21 16:26:54 CEST
MGA6-32 on Asus A6000VM MATE
No installation issues.
I can start nagstamon, get dialogue to create new server or ignore or exit. Choosing create new server gives a setup dialogue, so I stopped there as the problem of runtime dependencies seems to be solved.

CC: (none) => herman.viaene
Whiteboard: (none) => MGA6-32-OK

Comment 2 Lewis Smith 2017-10-27 13:05:11 CEST
Testing M6/64 under LXDE.

BEFORE the update, installed: nagstamon-2.0.1-1.mga6
which pulled in just a couple of extra python3 pkgs.

$ nagstamon
[Errno 2] No such file or directory: '/home/lewis/.nagstamon/nagstamon.pid'
Traceback (most recent call last):
  File "/usr/bin/nagstamon", line 60, in <module>
    from Nagstamon.QUI import (APP,
  File "/usr/lib/python3.5/site-packages/Nagstamon/QUI/__init__.py", line 23, in <module>
    from PyQt5.QtWidgets import *
ImportError: No module named 'PyQt5'
------------------------------------
AFTER the update, which pulled in additonally these python pkgs:
- python3-qt5-core-5.6-8.mga6.x86_64
- python3-qt5-multimedia-5.6-8.mga6.x86_64
- python3-qt5-network-5.6-8.mga6.x86_64
- python3-qt5-svg-5.6-8.mga6.x86_64
- python3-qt5-widgets-5.6-8.mga6.x86_64
- python3-sip-4.18.1-1.mga6.x86_64
nagstamon-2.0.1-1.1.mga6

However,
 $ nagstamon
gave the same error as previously. Will logout & retry.

CC: (none) => lewyssmith

Comment 3 Lewis Smith 2017-10-27 13:13:45 CEST
M6/64 continued, AFTER the update.
On re-logging in, same problem. All pkgs are as noted above at the end of in comment 2.

 $ nagstamon
 [Errno 2] No such file or directory: '/home/lewis/.nagstamon/nagstamon.pid'
 ...
 ImportError: No module named 'PyQt5.QtGui'

Since this worked in comment 1 32-bit, am asking for feedback.

Keywords: (none) => feedback

Comment 4 Guillaume Rousse 2017-10-27 18:30:24 CEST
The difference you experienced between your two different testing environments isn't caused by their architecture, but with their initial state. If you happen to have needed dependencies already installed, for whatever reason, the problem won't appear. Just get rid of python3-qt5-core, for instance, to see it surfacing again.

Now, it seems I forgot another python dependency in 1.1.mga6, python3-qt5-gui, explaining the failure in the second case. I just submitted 1.2.mga6 with this additional dependency added.
David Walser 2018-01-03 15:25:17 CET

Keywords: feedback => (none)
Whiteboard: MGA6-32-OK => (none)

Comment 5 Guillaume Rousse 2018-01-06 12:08:19 CET
So ? The problem was just a missing dependency, that should be quite easy to check, and close the issue.
Comment 6 Lewis Smith 2018-01-07 17:03:24 CET
M6/64
(In reply to Guillaume Rousse from comment #5)
> So ? The problem was just a missing dependency, that should be quite easy to
> check, and close the issue.
Point taken! Sorry this got left so long.

Testing this empirically, using urpmq -i for the package version, and urpmq -d for its dependancies.

BEFORE the update (core release): nagstamon-2.0.1-1.mga6
[list of 47 dependancies, of which 10 python*]:
python
python2-rpm-macros
python3
python3-beautifulsoup4
python3-pip
python3-pkg-resources
python3-psutil
python3-rpm-macros
python3-setuptools
python-rpm-macros

AFTER the update (core updates testing): nagstamon-2.0.1-1.2.mga6
[list of 342 dependancies of which 24 python*]
I suspect this huge list of dependancies is the result of the extra included python3 pkgs..
These are the extra 14 python* ones introduced by the update:
python3-cairo
python3-chardet
python3-dbus
python3-gobject3
python3-qt5-core
python3-qt5-gui        [see C4]
python3-qt5-multimedia
python3-qt5-network
python3-qt5-svg
python3-qt5-widgets
python3-requests
python3-sip
python3-six
python3-urllib3

Just to try it now...nagstamon-2.0.1-1.2.mga6
 $ nagstamon
 [Errno 2] No such file or directory: '/home/lewis/.nagstamon/nagstamon.pid'
 QLayout: Attempting to add QLayout "" to StatusWindow "", which already has a layout

which popped up the New Server dialogue when asked to, so that looks OK. Like Herman's C2 test.

Particularly, the previous error:
"Traceback (most recent call last):
  File "/usr/bin/nagstamon", line 60, in <module>
    from Nagstamon.QUI import (APP,
  File "/usr/lib/python3.5/site-packages/Nagstamon/QUI/__init__.py", line 23, in <module>
    from PyQt5.QtWidgets import *
 ImportError: No module named 'PyQt5'"
is gone. Update now good, OKing & validating under our new policy.

Will make up the advisory from comments 0 & 4.

Keywords: (none) => validated_update
Whiteboard: (none) => MGA6-64-OK
CC: (none) => sysadmin-bugs

Lewis Smith 2018-01-07 17:14:35 CET

Keywords: (none) => advisory

Comment 7 Mageia Robot 2018-01-07 23:54:15 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2018-0011.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.