Bug 1685701 - pius Python libraries installed in root directory
Summary: pius Python libraries installed in root directory
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pius
Version: 29
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Praveen Kumar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-05 20:38 UTC by Cleber Rosa
Modified: 2019-11-27 18:16 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-27 18:16:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Cleber Rosa 2019-03-05 20:38:46 UTC
Description of problem:

What seems to be a packaging problem is putting the Python libraries in the root directory, instead of within the Python site-packages library path.  This both pollutes the root directory, and prevents the "pius" to even start (failing to import the libraries).

Version-Release number of selected component (if applicable):

pius-2.2.4-4.fc29.noarch

How reproducible:

Always

Steps to Reproduce:

1. $ dnf install pius
2. $ pius 
3. $ rpm -ql pius | grep libpius

Actual results:

1. $ dnf install pius
2. $ pius 
Traceback (most recent call last):
  File "/usr/bin/pius", line 22, in <module>
    from libpius import signer as psigner
ImportError: No module named libpius
3. rpm -ql pius | grep libpius
/libpius
/libpius/__init__.py
/libpius/constants.py
/libpius/exceptions.py
/libpius/mailer.py
/libpius/signer.py
/libpius/state.py
/libpius/util.py
/libpius/wotsap.py

Expected results:

1. /libpius to be installed in `rpm -E '%{python2_sitelib}'`
2. pius command to work


Additional info:

Comment 1 Eric Blake 2019-03-05 21:12:23 UTC
I tried to work around it with:
$ PYTHONPATH=/:$PYTHONPATH pius -s $mykey -m $myemail -H $mysmtp -e $recipientkey

but that in turn failed:

Signing all UIDs on key XXXXX
  There is 1 UID on this key to sign
  UID 1 (XXX): signedTraceback (most recent call last):
  File "/usr/bin/pius", line 342, in <module>
    main()
  File "/usr/bin/pius", line 326, in main
    if signer.sign_all_uids(key, retval):
  File "/libpius/signer.py", line 788, in sign_all_uids
    self.encrypt_signed_uid(key, uid['file'])
  File "/libpius/signer.py", line 444, in encrypt_signed_uid
    raise EncryptionUnknownError(line)
libpius.exceptions.EncryptionUnknownError: [GNUPG:] ENCRYPTION_COMPLIANCE_MODE 23

I've been missing the functionality of pius since F28, per bug 1507152, and this new packaging bug doesn't seem to impact that the older bug is still unfixed :(

Comment 2 Ben Cotton 2019-10-31 19:51:29 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Eric Blake 2019-11-01 12:23:33 UTC
The broken installation at /libpius appears to be resolved in 2.2.4-5

Comment 4 Ben Cotton 2019-11-27 18:16:00 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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