archived the channel

@jonjitsu has joined the channel

@Denis Afonso has joined the channel

@Lee Skillen just a heads up - we noticed paths moved around today (the hazards of us proxying via cloudflare and rewriting paths for backwards compatibility) https://github.com/cloudposse/packages/issues/896

Cloudsmith are presenting a webinar with CircleCI and Hashicorp today on securing the supply chain with end-to-end delivery (+ demo), at 2PM UTC. Would appreciate the support from folks, and it would be worthwhile to you if tackling the supply chain, security and delivery is a problem you solve, or need to solve! 😁
https://www2.circleci.com/cci-hashicorp-cloudsmith-webinar.html

@Mohammed Yahya has joined the channel

@Serge Crinquand has joined the channel

@organicnz has joined the channel

Hey folks! Thanks to @Erik Osterman (Cloud Posse) and the team for inviting me on. It really was a pleasure to shoot the breeze and talk Cloud Posse, package management + start-ups for a while. Thanks for being awesome. 😁 If you've got any questions, ask away here or on Cloudsmith. Intercom is manned by engineering, and we're happy to help!

@Ramesh Yelishala has joined the channel

@Fernando has joined the channel

@Jeremy G (Cloud Posse) has joined the channel

@Rohit Gudi has joined the channel

@uselessuseofcat has joined the channel

@Tom Gibson has joined the channel

Hi Erik, I work with Lee at Cloudsmith, I’ll take a look into this for you now

I'm trying out the any-version feature with alpine

@Lee Skillen any idea what would cause this?

@Andrew Speed has joined the channel

@Kyle Harrison has joined the channel

@Reinholds Zviedris has joined the channel

@MattyB has joined the channel

@Joe Niland has joined the channel

@Matt Gowie has joined the channel

@Stan M has joined the channel

@Andriy Knysh (Cloud Posse) has joined the channel

Looking forward to Debian-based packages though. 😄

So when you see sl @ 1.0.3-1ubuntu2 in the wild, it means the upstream version was 1.0.3 (i.e. the version of the package the source was built from), the Debian version is 1 (i.e. the first package version of 1.0.3 that Debian built and released), and the Ubuntu version is 2 (i.e. the second version of the package that Ubuntu built and released).

Yep, you can upload packages that are in all of the supported distribution indexes, for any release of those distributions. Although if you're looking to create a derivative (forked, flavour, whatever you'd like to call it) package of something that exists, then it's better to represent this in the versioning of the package (rather than it being identical to the upstream). This is how distributions, like Ubuntu, create Debian-derivative packages, but put an "ubuntu" spin on them:
https://www.debian.org/doc/debian-policy/ch-controlfields.html#version

E.g. Imagine that sl at version 1.0.3-1 had an issue. You might create a new variant with a version of 1.0.3-1cp1 which would be semantically greater than 1.0.3-1 but (e.g.) less than 1.0.4-1. When a user goes to install sl from your repository, and 1.0.3-1 already exists alongside your fixed 1.0.3-1cp1 package, yours will be chosen.

In this mode, is it possible to upload packages to override the synthetic packages? e.g. we've had to make bug fixes for certain distros.

@Lee Skillen so I'm looking at the next big initiative which is adding debian support for our cloudposse packages. Cloudsmith has the concept of "universal packages" (right name?) where you can generate the synthetic packages for any major distro.

@Lee Skillen has joined the channel

set the channel description: Cloudsmith package management and hosting

@Erik Osterman (Cloud Posse) has joined the channel