Metadata revisions for elocrypt-2.1.0

Package maintainers and Hackage trustees are allowed to edit certain bits of package metadata after a release, without uploading a new tarball. Note that the tarball itself is never changed, just the metadata that is stored separately. For more information about metadata revisions, please refer to the Hackage Metadata Revisions FAQ.

No. Time User SHA256
-r1 (elocrypt-2.1.0-r1) 2019-12-16T02:00:04Z sgillespie 2bf49f367186e82b36c434f5304063f5443a0f9e8e00b83636ba5ee62bc39111
  • Changed source-repository from

    source-repository this
        type:     git
        location: https://github.com/sgillespie/elocrypt.git
        tag:      v2.0.1
    
    to
    source-repository this
        type:     git
        location: https://github.com/sgillespie/elocrypt.git
        tag:      v2.1.0
    

-r0 (elocrypt-2.1.0-r0) 2019-12-16T01:42:29Z sgillespie 0b8a27513bfdb11263d165639a6d52ed5b48e67f89ca7e8f173d90279a28a44d