Opened 12 years ago

Closed 12 years ago

#6757 closed defect (invalid)

libgcrypt in Sage is GPL 3

Reported by: drkirkby Owned by: somebody
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: cryptography Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

Sage has libgcrypt version 1.4.3 in spkg/standard.

But:

http://directory.fsf.org/project/libgcrypt/

clearly shows:

1.4.3

The file SPKG.txt says:

License

  • LGPL V2.1 or later (1.4 release)

Change History (4)

comment:1 Changed 12 years ago by wdj

See also http://trac.sagemath.org/sage_trac/ticket/1627 When I download libcrypt-1.4.4 from http://www.gnupg.org/download/index.en.html#libgcrypt the COPYING file indicates GPLv2 and the COPYING.LIB file indicates LGPLv2.1.

I don't see 1.4.3 there.

comment:2 Changed 12 years ago by drkirkby

The name of the .spkg file in Sage 4.1.1 is libgcrypt-1.4.3.p1.spkg I've made a libgcrypt-1.4.3.p2.spkg

drkirkby@smudge:[~/sage/suncc/sage-4.1.1/spkg/standard] $ ls -ld libgcrypt* 
-rw-r--r--   1 drkirkby other    2036701 Jul 31 22:45 libgcrypt-1.4.3.p1.spkg
-rw-r--r--   1 drkirkby other    2115840 Aug 16 12:34 libgcrypt-1.4.3.p2.spkg
drkirkby@smudge:[~/sage/suncc/sage-4.1.1/spkg/standard] $ pwd
/export/home/drkirkby/sage/suncc/sage-4.1.1/spkg/standard
drkirkby@smudge:[~/sage/suncc/sage-4.1.1/spkg/standard] $


comment:3 Changed 12 years ago by drkirkby

I guess we should go by the COPYING file. The website and the actual code disagree. I assume the code is more authorative.

I suspect this should be closed in that case.

comment:4 Changed 12 years ago by mvngu

  • Milestone changed from sage-4.1.2 to sage-duplicate/invalid/wontfix
  • Resolution set to invalid
  • Status changed from new to closed

I think the file COPYING in the source tarball is the authority here. So close this ticket as invalid.

Note: See TracTickets for help on using tickets.