https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v

    VoxBot

    05/16/2024, 4:21 PM
    i'm pretty sure lavamind would be extremely happy to get some help from upstream in maintaining those packages, and if perforce is working on improving those packages, we should definitely talk
  • v

    VoxBot

    05/16/2024, 4:22 PM
    i'm happy to look at source code or build log failures too
  • v

    VoxBot

    05/16/2024, 4:22 PM
    ewoud: nope. Our package has been called puppet-agent for ..... a decade now?
  • j

    josh

    05/16/2024, 4:22 PM
    Since Puppet 4 when we introduced AIO packages
  • v

    VoxBot

    05/16/2024, 4:22 PM
    well, I'm just guessing things :)
  • j

    josh

    05/16/2024, 4:24 PM
    I disagree with the "i do not believe package names should be what tells the packages apart" Isn't that the basis for NEVRA? A package can be uniquely identified based on name, epoch, version, release and architecture?
  • v

    VoxBot

    05/16/2024, 4:25 PM
    anarcat: to be clear -- WE can fix our own pipelines, that's not a problem. The problem will come from the gobs of customers & users who install the wrong package accidentally now. Especially those who've been doing it for a decade and their workflow now breaks.
  • v

    VoxBot

    05/16/2024, 4:25 PM
    I mostly think it's confusing that puppet-agent from upstream and downstream mean very different things: one uses system packages and the other has a full blown Ruby env vendored
  • v

    VoxBot

    05/16/2024, 4:26 PM
    what's NEVRA?
  • v

    VoxBot

    05/16/2024, 4:26 PM
    in RPMs you have Name Epoch Version Release Architecture (NEVRA)
  • v

    VoxBot

    05/16/2024, 4:26 PM
    ah
  • v

    VoxBot

    05/16/2024, 4:26 PM
    and that's globally unique?
  • j

    josh

    05/16/2024, 4:26 PM
    About "if perforce is working on improving those packages, we should definitely talk" Yes, agree. We've had a large backlog of agent platforms to add. We're just about done with Ubuntu Noble.
  • v

    VoxBot

    05/16/2024, 4:26 PM
    should be
  • v

    VoxBot

    05/16/2024, 4:27 PM
    ewoud: what's the clearinghouse?
  • v

    VoxBot

    05/16/2024, 4:27 PM
    is there a central repository where clashes are resolved?
  • v

    VoxBot

    05/16/2024, 4:27 PM
    for example, build systems like Koji use it effectively as a primary key
  • v

    VoxBot

    05/16/2024, 4:27 PM
    because i don't know about RPMs, but anyone can write their own .deb file in their basement without asking debian.org
  • v

    VoxBot

    05/16/2024, 4:28 PM
    conflicting package names are not unusual once you cross archive boundaries, this happens all the time
  • v

    VoxBot

    05/16/2024, 4:28 PM
    in RPMs you could do the same, it's more or less a convention
  • v

    VoxBot

    05/16/2024, 4:28 PM
    but who do you ask before you adopt a package name?
  • v

    VoxBot

    05/16/2024, 4:28 PM
    and in Fedora official repos it is enforced
  • v

    VoxBot

    05/16/2024, 4:28 PM
    this is mostly a rhetorical question
  • v

    VoxBot

    05/16/2024, 4:28 PM
    my point is that it's always a policy that's scoped by distro
  • v

    VoxBot

    05/16/2024, 4:28 PM
    of course this is unique in fedora official
  • v

    VoxBot

    05/16/2024, 4:28 PM
    and it's unique in debian
  • v

    VoxBot

    05/16/2024, 4:28 PM
    and it's unique in ubuntu
  • v

    VoxBot

    05/16/2024, 4:29 PM
    so anyway
  • v

    VoxBot

    05/16/2024, 4:29 PM
    i'm not sure what is the ask here
  • v

    VoxBot

    05/16/2024, 4:29 PM
    debian folks would be glad to cooperate on this
1...597598599...648Latest