Repository navigation
Conversation
Collaborator
|
@claude review plz |
mmlb
force-pushed
the
push-ozkqsxwyrtuz
branch
2 times, most recently
from
October 21, 2026 17:29
071a574 to
933260d
Compare
Package version diff: none (aarch64-linux, x86_64-linux) |
mmlb
force-pushed
the
push-ozkqsxwyrtuz
branch
from
October 21, 2026 21:31
933260d to
aecde92
Compare
The qemu image build has been failing supascan since Oct 14 because ssh.service isn't running when the baseline check runs. Ubuntu 24.04 starts sshd through ssh.socket. The build boots the latest noble cloud image, then runs apt-get dist-upgrade. When the archive has a newer openssh-server than the image, the package upgrade stops ssh.service and restarts only ssh.socket. Packer's existing session keeps working, but nothing opens a new connection, so ssh.service stays stopped until the check runs. Whether the check passes depends on whether Ubuntu has shipped an openssh update since the last cloud image. That's also why #2426 had to flip this same spec six weeks ago. Drop the running check for ssh and check that ssh.socket is enabled instead. That holds whether or not openssh gets upgraded during the build. Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
mmlb
force-pushed
the
push-ozkqsxwyrtuz
branch
from
October 21, 2026 21:31
aecde92 to
ea1e39e
Compare
PostgreSQL Extension Dependency Analysis: PR #2581
SummaryNo extensions had dependencies with MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Extension DependenciesPostgreSQL 17 Extension DependenciesOrioleDB 17 Extension Dependencies |
PostgreSQL Package Dependency Analysis: PR #2581
SummaryNo packages had MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Dependency ChangesExtracting PostgreSQL 15 dependencies...
Runtime Closure Size
Raw Dependency ClosurePostgreSQL 17 Dependency ChangesExtracting PostgreSQL 17 dependencies...
Runtime Closure Size
Raw Dependency Closure |
Split publish into its own workflow, mimicing AMI Release Nix. We don't need the publish steps most of the time so better to avoid all the unnecessary stuff in this file. When we do want to publish compress the output with zstd since its nice and fast, compresses from ~5G to ~1G and should be fine.
mmlb
force-pushed
the
push-ozkqsxwyrtuz
branch
from
October 22, 2026 13:51
ea1e39e to
9483e59
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Gardening
What is the current behavior?
Qemu image builds are not dependent on Nix CI even though it depends on the nix packages being available for fetching.
What is the new behavior?
Qemu image builds now work like the AMI builds.
QMI builds depend on packages in Nix CI, images are not published.
Like AMI Release Nix, Qemu images are published from develop/release branches with postgres_release.yml is modified.