Bug 26411 - golang-libcrypto and golang-googlecode-go-crypto are the same
Summary: golang-libcrypto and golang-googlecode-go-crypto are the same
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-01 10:13 CEST by Jybz
Modified: 2020-04-01 21:12 CEST (History)
1 user (show)

See Also:
Source RPM: golang-libcrypto-0.20131031-8.mga7.src.rpm, golang-googlecode-go-crypto
CVE:
Status comment:


Attachments

Description Jybz 2020-04-01 10:13:42 CEST
Hello !

In order to build IPFS, I'm building more or less 200 packages.

I'm also looking on dependencies already build in Mageia.

I found this two packages :
 golang-libcrypto
 golang-googlecode-go-crypto

on the svn :
> http://svnweb.mageia.org/packages/updates/7/golang-googlecode-go-crypto/current/SPECS/golang-googlecode-go-crypto.spec?view=markup
> http://svnweb.mageia.org/packages/updates/7/golang-libcrypto/current/SPECS/golang-libcrypto.spec?view=markup

And I'm pretty certain that there are the same.
> Summary:        Supplementary Go cryptography libraries
> Summary:        supplementary Go cryptography libraries

Moreover, one seem to be obsolet :
> %define prerelease 6478cc9340cb
> Source0:        http://crypto.go.googlecode.com/archive/%{prerelease}.zip
Following the link :
http://crypto.go.googlecode.com/archive/6478cc9340cb.zip
> 404 not found

I'm still hesitating between writing a third spec from my pattern, or reusing one of them.
Comment 1 Lewis Smith 2020-04-01 21:12:30 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
CC: (none) => lewyssmith
Source RPM: golang-libcrypto golang-googlecode-go-crypto => golang-libcrypto-0.20131031-8.mga7.src.rpm, golang-googlecode-go-crypto
Resolution: (none) => INVALID


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