Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

postgresql16Packages.plpgsql_check: 2.7.4 -> 2.7.5 #300394

Conversation

r-ryantm
Copy link
Contributor

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/okbob/plpgsql_check/releases.

meta.description for postgresql16Packages.plpgsql_check is: Linter tool for language PL/pgSQL

meta.homepage for postgresql16Packages.plpgsql_check is: https://github.com/okbob/plpgsql_check

meta.changelog for postgresql16Packages.plpgsql_check is: https://github.com/okbob/plpgsql_check/releases/tag/v2.7.5

Updates performed
  • Version update
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 2.7.5 in filename of file in /nix/store/nsy7kn8xsyy1vr154y2ch1jrvz6lfhc8-plpgsql-check-2.7.5

Rebuild report (if merged into master) (click to expand)
12 total rebuild path(s)

12 package rebuild(s)

First fifty rebuilds by attrpath
postgresql12JitPackages.plpgsql_check
postgresql12Packages.plpgsql_check
postgresql13JitPackages.plpgsql_check
postgresql13Packages.plpgsql_check
postgresql14JitPackages.plpgsql_check
postgresql14Packages.plpgsql_check
postgresql15JitPackages.plpgsql_check
postgresql15Packages.plpgsql_check
postgresql16JitPackages.plpgsql_check
postgresql16Packages.plpgsql_check
postgresqlJitPackages.plpgsql_check
postgresqlPackages.plpgsql_check
Instructions to test this update (click to expand)

Either download from Cachix:

nix-store -r /nix/store/nsy7kn8xsyy1vr154y2ch1jrvz6lfhc8-plpgsql-check-2.7.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A postgresql16Packages.plpgsql_check https://github.com/r-ryantm/nixpkgs/archive/6f452873f394005bed60ec727c982bcfbddf7e20.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/6f452873f394005bed60ec727c982bcfbddf7e20#postgresql16Packages.plpgsql_check

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/nsy7kn8xsyy1vr154y2ch1jrvz6lfhc8-plpgsql-check-2.7.5
ls -la /nix/store/nsy7kn8xsyy1vr154y2ch1jrvz6lfhc8-plpgsql-check-2.7.5/bin


Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

10 packages built:
  • postgresql12JitPackages.plpgsql_check
  • postgresql12Packages.plpgsql_check
  • postgresql13JitPackages.plpgsql_check
  • postgresql13Packages.plpgsql_check
  • postgresql14JitPackages.plpgsql_check
  • postgresql14Packages.plpgsql_check
  • postgresql15JitPackages.plpgsql_check
  • postgresql15Packages.plpgsql_check
  • postgresql16JitPackages.plpgsql_check
  • postgresql16Packages.plpgsql_check

Maintainer pings

cc @marsam for testing.

@marsam marsam closed this in cd1c70d Mar 31, 2024
@r-ryantm r-ryantm deleted the auto-update/postgresql16Packages.plpgsql_check branch March 31, 2024 12:21
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.

None yet

1 participant