Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-10124

Package provider removes colon from package name

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PUP 6.9.0
    • Fix Version/s: PUP 5.5.18, PUP 6.4.5, PUP 6.12.0
    • Component/s: None
    • Environment:

      Gentoo Linux last rolling version from 2019-10-23.

      I will add any other requested information as needed because I do not know what cna be relevant.

    • Template:
    • Team:
      Night's Watch
    • Story Points:
      1
    • Sprint:
      NW - 2019-11-13, 2019-11-27, 2019-12-11, 2019-12-24
    • Method Found:
      Needs Assessment
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Fix implementation of colon as a version slot separator for Gentoo Linux
    • QA Risk Assessment:
      Needs Assessment

      Description

      Hello,

      the puppet-agent in version 6.9.0 (I am not sure on which version bug appeared first) has broken package provider in a way than it "eats" colon ":" from package name.

      Which breaks package/slot handling on Gentoo Linux.

      On Gentoo you can install package with emerge to a specific version slot by specifying slot after package name separated with a colon eg.:

      "emerge dev-db/postgresql:11"

      On puppet-agent version 6.7.2 it was working alright.

      Best regards

      AM

       

      Error message:

      Error: /Stage[main]/Package::Dev_db::Postgresql/Package[dev-db/postgresql:11]/ensure: change from 'absent' to 'present' failed: Execution of '/usr/bin/emerge dev-db/postgresql11' returned 1: These are the packages that would be merged, in order:

      Calculating dependencies ... done!

      emerge: there are no ebuilds to satisfy "dev-db/postgresql11".

       

       

        Attachments

          Activity

            People

            • Assignee:
              ciprian.badescu Ciprian Badescu
              Reporter:
              mikula Alexandr Mikula
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support