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

packages on apt.p.c have the "same" package with different contents

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Template:
    • Team:
      Release Engineering
    • Sub-team:

      Description

      When looking at packages on apt.puppetlabs.com, the majority of them do have the same version across distro releases, leading to this confusion:

      david@zion:~$ curl http://apt.puppetlabs.com/pool/wheezy/main/p/puppetlabs-release/puppetlabs-release_1.0-11_all.deb | md5sum
        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                       Dload  Upload   Total   Spent    Left  Speed
      100  7388  100  7388    0     0  16485      0 --:--:-- --:--:-- --:--:-- 16454
      775a42ee41b1074c497ebe06dda74128  -
      david@zion:~$ curl http://apt.puppetlabs.com/pool/jessie/main/p/puppetlabs-release/puppetlabs-release_1.0-11_all.deb | md5sum
        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                       Dload  Upload   Total   Spent    Left  Speed
      100  7368  100  7368    0     0  21081      0 --:--:-- --:--:-- --:--:-- 21111
      b7a28a220b5023a5c3c0499648064d89  -
      david@zion:~$ 
      

      For example, this means that updating from packages targeting wheezy to packages targeting jessie is weird, because the puppetlabs-release/jessie is the "same" version as puppetlabs-release/wheezy.

      In a similar vein, single-pool repo mirroring tools, like reprepro, get confused by this.

      A solution would be add the target release version into all package's versions. The current practice of putting the release name as is done with some of the PC1 packages (e.g. puppet-agent_1.3.5-1jessie_i386.deb; puppet-agent_1.3.5-1wheezy_i386.deb) is not sufficient, as the ordering for the names is not correct.

      [This was reported to me by a Debian developer.]

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  david.schmitt David Schmitt
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: