Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-46938

mongodb-org debian repo has malformed Packages file

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • ALL
    • Hide
      $ echo 'deb [arch=amd64] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 multiverse' > /etc/apt/sources.list.d/mongodb-org-4.0.list
      $ sudo apt update
      

      On a debian-based system, obviously. Specifically, I'm on Ubuntu eoan, but this should be reproducible pretty much anywhere.
       

      Show
      $ echo 'deb [arch=amd64] https: //repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 multiverse' > /etc/apt/sources.list.d/mongodb-org-4.0.list $ sudo apt update On a debian-based system, obviously. Specifically, I'm on Ubuntu eoan, but this should be reproducible pretty much anywhere.  

      debian build seems to be appending a bad line to Packages file:

      dpkg-scanpackages: info: Wrote 90 entries to output Packages file.
      

      This is causing apt update and apt upgrade on systems depending on affected repos to fail with the following message:

      E: Encountered a section with no Package: header
      E: Problem with MergeList /var/lib/apt/lists/repo.mongodb.org_apt_ubuntu_dists_bionic_mongodb-org_4.0_multiverse_binary-amd64_Packages
      E: The package lists or status file could not be parsed or opened.
      

      The problem can be fixed by editing /var/lib/apt/lists/repo.mongodb.org_apt_ubuntu_dists_bionic_mongodb-org_4.0_multiverse_binary-amd64_Packages and removing the last line, but obviously this is not a sustainable solution, as any time I apt update this will be overridden.

      The xenial and bionic repos at least both have this issue on the 4.0 amd64 package. Looking around at the other versions, I'm only seeing this affecting 4.0.

      Note: not sure if this is the right project to list this under, but the other possibilities (MAKE? DEVOPS?) don't have many issues for reference/didn't have a linked google doc. Feel free to move if appropriate.

            Assignee:
            kimberly.tao@mongodb.com Kim Tao
            Reporter:
            nathan.perry@tulip.co Nathan Perry
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: