Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-10161

Artifactory parses epoch version from Debian control file incorrectly

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 4.6.0, 4.7.5
    • Fix Version/s: 4.8.0
    • Component/s: Debian
    • Labels:
      None

      Description

      When deploying a package with an epoch version identifier contained in the Version field of the Debian control file, it may 'trim' out the "Upstream" version identifier and cause Artifactory (4.6.0) to annotate only the epoch number for the version property.

      Moreover, it seems that on 4.7.5 the version property does not annotate at all, even though the metadata calculation finishes successfully and the package information is included in the Packages file.

      Steps to reproduce:
      1. Run a dpkg-deb -f DEBIAN_PACKAGE.deb on a given package to verify it contains a version with epoch time

      2. Deploy this file to a Debian repo in Artifactory

      3. Obeserve the Version proprety after calculation either equaling epoch time (4.6.0) or not present at all (4.7.5)

      Reproduction performed on Artifactory 4.7.5 and 4.6.0 and using this package:

      http://ftp.us.debian.org/debian/pool/main/g/git/git-man_1.9.1-1~bpo70+2_all.deb

      External Debian Doc about Debian Versioning:

      https://www.debian.org/doc/debian-policy/ch-controlfields.html

        Attachments

          Activity

            People

            • Assignee:
              danf Dan Feldman
              Reporter:
              andreik Andrei Komarov
              Assigned QA:
              Matan Katz
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: