Skip to content

libpeas2: 2.0.5 -> 2.0.7#402100

Closed
r-ryantm wants to merge 1 commit intoNixOS:masterfrom
r-ryantm:auto-update/libpeas2
Closed

libpeas2: 2.0.5 -> 2.0.7#402100
r-ryantm wants to merge 1 commit intoNixOS:masterfrom
r-ryantm:auto-update/libpeas2

Conversation

@r-ryantm
Copy link
Contributor

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for libpeas2 is: GObject-based plugins engine

meta.homepage for libpeas2 is: https://gitlab.gnome.org/GNOME/libpeas

Updates performed
  • Ran passthru.UpdateScript
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 2.0.7 in filename of file in /nix/store/qjg3m99ca5g0j9kmqpnmakgbf2j4v2cf-libpeas-2.0.7

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

13 package rebuild(s)

First fifty rebuilds by attrpath

boatswain
calls
clapper
clapper-enhancers
clapper-unwrapped
gnome-builder
libpeas2
newsflash
pipeline
televido
vala-language-server
valent
Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/qjg3m99ca5g0j9kmqpnmakgbf2j4v2cf-libpeas-2.0.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached 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 libpeas2 https://github.com/r-ryantm/nixpkgs/archive/5d1bb29fd54b4602f9af4a147cef402bf6d04586.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/5d1bb29fd54b4602f9af4a147cef402bf6d04586#libpeas2

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

ls -la /nix/store/qjg3m99ca5g0j9kmqpnmakgbf2j4v2cf-libpeas-2.0.7
ls -la /nix/store/qjg3m99ca5g0j9kmqpnmakgbf2j4v2cf-libpeas-2.0.7/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.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review


x86_64-linux

✅ 18 packages built:
  • boatswain
  • calls
  • calls.devdoc
  • clapper
  • clapper-enhancers
  • clapper-unwrapped
  • clapper-unwrapped.dev
  • clapper-unwrapped.lib
  • gnome-builder
  • gnome-builder.devdoc
  • libpeas2
  • libpeas2.dev
  • libpeas2.devdoc
  • newsflash
  • pipeline
  • televido
  • vala-language-server
  • valent

Maintainer pings

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.


Add a 👍 reaction to pull requests you find important.

@github-actions github-actions bot added 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 11-100 This PR causes between 11 and 100 packages to rebuild on Linux. labels Apr 26, 2025
@jtojnar
Copy link
Member

jtojnar commented Apr 28, 2025

Part of #386514

Should not have been updated nix-community/nixpkgs-update#474

@jtojnar jtojnar closed this Apr 28, 2025
@r-ryantm r-ryantm deleted the auto-update/libpeas2 branch April 29, 2025 00:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 11-100 This PR causes between 11 and 100 packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants