| Summary: | golang-libcrypto and golang-googlecode-go-crypto are the same | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jybz <j.biernacki+mga> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | lewyssmith |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | golang-libcrypto-0.20131031-8.mga7.src.rpm, golang-googlecode-go-crypto | CVE: | |
| Status comment: | |||
|
Description
Jybz
2020-04-01 10:13:42 CEST
> I found this two packages :
> golang-libcrypto
> golang-googlecode-go-crypto
Did you really? Although both golang-libcrypto and golang-googlecode-go-crypto are listed as SRPMs, I can only find golang-libcrypto as a *package*. So we do not seem to offer the Google variant.
Given that you say the Google one has disappeared anyway, why bother with it? Just use golang-libcrypto.Status:
NEW =>
RESOLVED |