Skip to content

(RE-16550): Debian 12 bookworm FOSS build target#629

Merged
span786 merged 3 commits into
puppetlabs:mainfrom
h0tw1r3:debian12
Aug 26, 2024
Merged

(RE-16550): Debian 12 bookworm FOSS build target#629
span786 merged 3 commits into
puppetlabs:mainfrom
h0tw1r3:debian12

Conversation

@h0tw1r3

@h0tw1r3 h0tw1r3 commented Apr 21, 2024

Copy link
Copy Markdown
Contributor

No description provided.

h0tw1r3 added 3 commits April 20, 2024 12:23
possible to install java 17 and java 11, package should be flexible
to accept either as a dependency

@smortex smortex left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/me wants Debian 12 packages for puppetserver and puppetdb 😭

Approving, even if my approval will probably not help at all 😢

@kenyon

kenyon commented Jun 7, 2024

Copy link
Copy Markdown

Typo in PR title: Debain -> Debian

@h0tw1r3 h0tw1r3 changed the title Debain 12 bookworm FOSS build target Debian 12 bookworm FOSS build target Jun 7, 2024
@joshcooper

Copy link
Copy Markdown
Contributor

@h0tw1r3 could you rebase and resolve conflicts?

@span786

span786 commented Aug 23, 2024

Copy link
Copy Markdown
Contributor

@puppetlabs/release-engineering / @puppetlabs/dumpling / @puppetlabs/skeletor
I successfully generated the lein-ezbake JAR using the changes from this PR: lein-ezbake-2.6.2.jar.zip. However, there isn't an ad-hoc Jenkins pipeline available to test if the JAR is functioning correctly. Can we merge this PR and test it in the main pipeline here?

@span786 span786 changed the title Debian 12 bookworm FOSS build target (RE-16550): Debian 12 bookworm FOSS build target Aug 23, 2024
@bastelfreak

Copy link
Copy Markdown

All our lives would be easier if the pipelines would be public again, at least for the Vox Pupuli PMC and Puppet Partners.

@justinstoller

Copy link
Copy Markdown
Member

I believe the practice before was to build a puppetserver and/or puppetdb package using the changes in a PR and then ensure they install on the target system. Once that is manually tested, ideally by both the PR author and reviewer, then the PR can be merged and a new ezbake released by the pipeline you linked, @span786 .

And Tim is also correct.

@justinstoller

Copy link
Copy Markdown
Member

Here is a lightly edited log of me validating this PR as an example: ezbake.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants