is it 2 weeks already w/o EAB/townhall call arranged? I understand it's holiday season in US, but I guess this is important enough to find 1 hour in a schedule.

I was hoping to get a final statement from them about the state of their packages and their open source plans

but maybe no answer is also an answer

from other side, we already got community packages, which is what they want.. so maybe we should just start deciding on our own

yeah.. I was in hope we can avoid the fork

I still have some small hope, but longer we wait, less hope is.. I guess it holidays for them are more important than their Puppet business.. well, it's their choice

*if holidays..

bastelfreak, sorry to bother but publishing of puppetboard 6.0.0 to PyPi failed (https://github.com/voxpupuli/puppetboard/actions/runs/12028110016/job/33530525959), I should have fixed the action (https://github.com/voxpupuli/puppetboard/pull/1204), could you have a look at it and eventually rerun the publish?

Hey Yury, I am meeting Tzvika today. The delays reflect we have been actively looking at the feedback and working on the best structure and approaches we can propose based on discussions we have had with community members to cover things like trademarks and repo ownership which unfortunately just takes time.

Still it would be helpful and show some respect to the community, and partners, if Tzvika could actually appear somewhere and community what he's doing/thinking

anarcat, lavamind: requesting insights from Debian developers: would the proposal from Yury ~20 messages above have unexpected consequences? Or is there some "well-known" scheme that avoid this issue? Thanks!

using the version nuumber instead of a codename is an excellent idea

look at how backports do versioning

if you have, e.g. foo-1.0 in stable and foo-2.0 in testing, and want to backport 2.0, you call it 2.0~bpo12

~ is a magic separator, it's kind of weird and means "less than" so 2.0~0 < 2.0

so when you upgrade from stable to testing, you upgrade from 2.0~bpo12 to 2.0

so you could call your package puppet-agent_8.10.0~overlook12

i would make it even shorter like ~oli12

at Tor, we use ~tpo12

(like TorProject.Org)

the only disadvantage is that if there's a backport that shows up, we're a higher version, because ~tpo12 > ~bpo12, so we don't automatically upgrade to backports

but, then again, that can be seen as an advantage

That looks nice, thanks for the details!

There is also a decade old issue in the Perforce jira to switch to numbers

glad to be of service

^^^ @Nick B some neat stuff for you

I don't see this change having any unexpected effects

and I also agree its better

Once I implement this, does anyone mind if I just wholesale replace the files in apt.overlookinfratech.com, or would you prefer to keep them in place and just add new packages/repos?

And, just to be clear,

puppet-agent_8.10.0.overlookinfra-1bookworm_amd64.deb

becomes

puppet-agent_8.10.0.overlookinfra-1debian12_amd64.deb

, yes? Might look into removing that -1 too, I don't think that's ever all that useful.