Uploaded image for project: 'Community Package Repository'
  1. Community Package Repository
  2. CPR-44

Broken checksums for trusty packages

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2017/08/02
    • Component/s: None
    • Labels:
      None
    • Template:

      Error rendering 'issue-templates-customfield'. Please contact your Jira administrators.

      Description

      This is about the repository https://apt.puppetlabs.com

      The packages offered for trusty are conflicting with the checksums mentioned in the packages file of therepository.

      I noticed it when setting up a reprepro mirror, which resulted in the following error, when enabling trusty:

      ERROR: Same file is requested with conflicting checksums:
      md5 expected: f1b8d719606c45285f5049f03a43ba38, got: 545d0a64e572bbb28fa91f7b2dfc29a6
      sha1 expected: cfbdb7816cb115fea1a64c13d30391532ac5d30f, got: 7aac0f560ccf55daa0744a025a7849a8c79948a4
      sha256 expected: 8c98077dea77fe24c697f3cb396b988df11bc58224cc4a4cb3dc716849f6a380, got: 77263d83694fccbeaed806c16259b344b32ac1c128be28a9bb9f4eb3a3e4d28a
      ERROR: Same file is requested with conflicting checksums:
      md5 expected: 48d26eec5854cb997c07e00d55a1f4d3, got: 4f326ee6222846c4d68ee2c338a541ea
      sha1 expected: 03b7b3ac52e053b2ff765624ba5215257a6556a0, got: 4b8c4104ec272abfc2f84bf9a182f08901431da6
      sha256 expected: eed184206426de2955b32d40e04724aa4eff3b40c42b6267dbd7918cdeeb9b3a, got: c7e33c596220a4df455cabfcc6a89544b8262ceb6059f8f9d0249e8c7409bb6b
      size expected: 1717, got: 1677

        Attachments

          Activity

            People

            Assignee:
            melissa Melissa Stone
            Reporter:
            edlerd edlerd
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support