Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Proget - Migration of Legacy Debian feed to "normal" Debian feed is broken

    Scheduled Pinned Locked Moved Support
    3 Posts 2 Posters 13 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • felfertF Offline
      felfert
      last edited by atripp

      Just tried migration of an old legacy Debian feed to a normal Debian feed. No errors were reported during the migration and in proget's web-UI, everything looks fine. However the feed is unusable with apt on any distro.

      When running apt-get update (or apt update), it complains about the Packages file not being parsable like this:

      Reading package lists... Error!
      E: Encountered a section with no Package: header
      E: Problem with MergeList /var/lib/apt/lists/proget.graudatastorage.intern_debian_XTC-deb_dists_jammy_main_binary-amd64_Packages
      E: The package lists or status file could not be parsed or opened.
      

      If I look at the file mentioned above, It turns out, apt is correct in that there are multiple errors:

      • Each package record MUST begin with the Package: field. Proget puts this field in between the other fields.
      • Between the Size: field and the Filename: field, Proget puts an empty line which does not belong there. Empty line are reserved as record separators.

      I also noticed some inconvenience with the Migration itself:

      When migrating, proget uses the name of the legacy feed as Distro for the new feed. So if I want one of the usual Distro names (e.g. like bookworm), then I have to rename the old feed accordingly before starting the Migration. This might impact availability. It would be easier, if the Distro name could be entered manually when starting the migration.

      Proget version: 2024.36 (Build 5) running in a docker container
      Cheers
      -Fritz

      atrippA 1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer @felfert
        last edited by

        Hi Fritz,

        Thanks for reporting this; the underlying with the Packages index file isn't so much the migration, but the code that generates the index file on the new feed.

        Basically, the control files seem to be have an extra new line that isn't being trimmed. The old feed code must have removed them.

        Anyways we will address this via PG-2985 in the next maintenance release or you can try the proget.inedo.com/productimages/inedo/proget:24.0.37-ci.2 container now.

        Cheers,
        Alana

        1 Reply Last reply Reply Quote 1
        • felfertF Offline
          felfert
          last edited by

          Many thanks, Alana!

          I can confirm, that the proget:24.0.37-ci.2 container image works like a charm ☺

          Thanks for the quick fix!

          • Fritz
          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation