This is an automated email from the git hooks/post-receive script.

gregoa pushed a change to annotated tag upstream/2.12
in repository libcpan-checksums-perl.

        at  1b90ecb   (tag)
   tagging  4d49dc0e22de7926f2d43078795a0fe89bd4aae0 (commit)
  replaces  upstream/2.10
 tagged by  gregor herrmann
        on  Fri Jul 1 16:51:47 2016 +0200

- Log -----------------------------------------------------------------
Upstream version 2.12

Andreas Koenig (10):
      ready to release 2.09
      switching from svn to git and release testing
      Version 2.10; no functional change
      bump the Module::Signature version that decides whether to test or not to 
test
      Extend checksums with those for uncompressed files also to .tgz and .tbz
      Make Changes file ready for release 2.11
      never let t/00signature.t actually fail
      Release gears: shorten the release target in the Makefile
      Fix recalc being too lazy
      Ready to release 2.12

Petr Písař (1):
      Try to connect to pool.sks-keyservers.net

gregor herrmann (1):
      Imported Upstream version 2.12

k (95):
      initial import
      Starting to use SVN
      more SVN preparations
      remove |Makefile
      remove other runtime files
      Rev property!
      applied a patch by Steve Peters to support sha256
      want to sign the distro
      refactored the new function add_digests out of the long loop
      add support for bzip2
      Oops, checked in all the RCS directories
      tests rewrote comment in CHECKSUMS file
      Property set for release after_12
      just silencing svn
      removing automatic files
      oops, there was a chmod still
      Property set for release after_16
      oh my god, how many unneeded files did I check in???
      is this the last RCS relict?
      Property set for release after_19
      last change of the reference file
      Property set for release after_21
      sort the keys
      the latest CHECKSUMS file after sorting
      Property set for release after_24
      Touching the Makefile.PL caused irritating behaviour, will try without; 
we can add 1 instead of 1.1 now to the VERSION because we reach at greater than 
1.018 which was the last release
      we had an updatedir.t~ in the CHECKSUMS file, removed now
      Property set for release after_27
      finally I discovered how version_diff was intended to work initially: 
after a forced checkin the make must die because it still only knows about the 
old version
      Property set for release after_29
      rename ChangeLog to ChangeLog.svn: do not like to set expectations to the 
other format
      Property set for release after_31
      blah
      dependencies; GMT
      add release target to Makefile
      svn complains after make test that the CHECKSUMS file is not checked in; 
is svn right about that?
      Property set for release after_36
      new dist_test target
      Property set for release after_38
      adding Chagelog.svn
      witch testscript to use Test::More
      add the standard pot.t
      blah
      add a Todo file
      blah
      better error handling during updatedir
      prepare next release
      Property set for release after_47
      blah
      guarantee atomicity: concurrent writes are consistent
      blah
      add a license to the manpage
      thanks to pod coverage found a few missing things in the docu
      add some more of my usual makefile.pl voodoo
      refactoring updatedir without functional change: separate the generation 
of the directory reference
      more refactoring without functional change: rename variable cksum to 
old_ddump and split out _read_old_ddump
      more refactoring without functional change: rename variable cksum to 
old_ddump and split out _read_old_ddump
      allow the reuse of a previously calculated md5 when the sha256 already 
matches
      allow reuse of old -un{gz,bz2} checksum if the plain one has already 
proven file is unchanged
      just test metadata, autogenerated
      Property set for release after_60
      make 5.005 compatible
      prepare release
      Property set for release after_63
      eliminate forward slashes from test
      automatic side effect of last testrun
      prepare for a move of the file Checksums.pm to lib/CPAN
      actually mv the file Checksums.pm to lib/CPAN
      ready for the next release
      prepare a new release
      prepare a new release
      prepare a new release
      prepare a new release
      prepare a new release
      prepare a new release
      autogen
      add missing binmode() for Windows (courtesy Elliot Shank)
      prepare a release
      prepare a release
      call binmode as a function not a method
      up some version numbers on rereqs just to be on the safe side
      prepare next release
      prepare next release
      whitespace
      ready for the next release
      ready for another relase
      remove a test that relies on the number of blocks a file occupies
      add MYMETA.yml to MANIFEST.SKIP
      prepare release 2.06
      prepare release 2.06
      prepare release 2.06
      skip the signature test under more bad circumstances
      ready for 2.07
      survive newest toolchain that creates a MYMETA.json
      signing with makemaker is hard

-----------------------------------------------------------------------

No new revisions were added by this update.

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/pkg-perl/packages/libcpan-checksums-perl.git

_______________________________________________
Pkg-perl-cvs-commits mailing list
Pkg-perl-cvs-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits

Reply via email to