Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Done
    • None
    • 2017/08/02
    • Packaging
    • None
    • Release Engineering
    • 2
    • RE 2017-06-28
    • Needs Assessment
    • Needs Assessment

    Description

      Mirroring both the Trusty and Xenial repository using reprepro is broken as it complains there is a duplicate file with mismatching checksum. This appears to be the same issue that was reported in CPR-44 previously.

      root@server:~# /usr/bin/reprepro -b /mnt/data1/apt-reprepro/internal update
      aptmethod got 'http://apt.puppetlabs.com/dists/xenial/Release'
      aptmethod got 'http://apt.puppetlabs.com/dists/trusty/Release'
      aptmethod got 'http://apt.puppetlabs.com/dists/xenial/Release.gpg'
      aptmethod got 'http://apt.puppetlabs.com/dists/trusty/Release.gpg'
      aptmethod got 'http://apt.puppetlabs.com/dists/xenial/PC1/binary-i386/Packages.gz'
      aptmethod got 'http://apt.puppetlabs.com/dists/trusty/PC1/binary-i386/Packages.gz'
      aptmethod got 'http://apt.puppetlabs.com/dists/xenial/PC1/binary-amd64/Packages.gz'
      aptmethod got 'http://apt.puppetlabs.com/dists/trusty/PC1/binary-amd64/Packages.gz'
      Calculating packages to get...
      File "pool/thirdparty/p/puppetdb/puppetdb_4.4.0-1puppetlabs1_all.deb" is already registered with different checksums!
      md5 expected: 277b59948cd559b8bdce30a8b0c623dc, got: 43a2b0410ec128d8f80a65303f1082ce
      sha1 expected: 5e9f57c55e86176ec9b36fa867a05963600d8732, got: 61d4ed671bc8e67e5ce735e41deecf3b17ab969c
      sha256 expected: b2ad980444a789cad59cc34279b982b6e94a68b70f15c24fe5859c5bc52e4afb, got: c8c4a89ec0d8fa0f774488a9e4b90aac9e1b366948158f891efc6e0899f379ba
      size expected: 22372026, got: 22373908
      There have been errors!
      

      Attachments

        Issue Links

          Activity

            People

              daemondazz Darryl Ross
              daemondazz Darryl Ross
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support