setting up the component architecture overwrites $GNUPGHOME due to gpghandler isolating itself
Bug #227586 reported by
Michael Hudson-Doyle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Observe:
>>> from canonical.
>>> import os
>>> os.environ.
>>> execute_
>>> os.environ.
'/tmp/gpg-L49Hue'
This does not seem like a feature.
This is because canonical.
tags: | added: tech-debt |
Changed in launchpad-foundations: | |
status: | Incomplete → Invalid |
Changed in launchpad-foundations: | |
importance: | Undecided → Low |
Changed in launchpad-foundations: | |
assignee: | Celso Providelo (cprov) → nobody |
visibility: | private → public |
summary: |
- setting up the component architecture overwrites $GNUPGHOME + setting up the component architecture overwrites $GNUPGHOME due to + gpghandler isolating itself |
To post a comment you must log in.
Hi Michael, the GNUPGHOME is set on initialization because it needs to point to a special configuration file prepared for LP needs (for instance, it uses auto-key-retrieve option). So, it is indeed a feature, although, I admit it's not explicitly documented in any of the related tests. So, if it's only about documentation, feel free to edit the description and tag the bug appropriately.