| Summary: | trinity-keyring should not depend on gnupg | ||
|---|---|---|---|
| Product: | TDE | Reporter: | mgb-trinity |
| Component: | debian | Assignee: | Slávek Banko <slavek.banko> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugwatch, mgb-trinity, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 3161 | ||
|
Description
mgb-trinity
2020-10-31 11:09:09 CDT
Thanks, now I've looked at it in more detail and I see it. We need gnupg at the time of building the package - so build-deps, but no longer needed for the binary package. I'll make an adjustment in the packaging. About the bugzilla - that's fine. Here it will take some time before the website change is ready, as discussed in the ML, before the TGW integration is ready for reporting bugs from applications, and before the bugs from the bugzilla are migrated to issues in the TGW... Until then, we'll have to watch both. This is obviously not a high priority bug but when you get round to it you might want to look at the postinst, prerm, and postrm of debian-archive-keyring and see if trinity-keyring should have something similar. (In reply to mgb-trinity from comment #2) > This is obviously not a high priority bug but when you get round to it you > might want to look at the postinst, prerm, and postrm of > debian-archive-keyring and see if trinity-keyring should have something > similar. Yes, that's not a big priority. But at the same time it is a simple fix, so it will be useful when it can be resolved and closed. See pull-request https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging/pulls/69 Pull request has been merged, updated packages are available in PSB and PTB repositories. |