Merged
Conversation
ofborg
bot
added
10.rebuild-darwin: 1-10
jtojnar
force-pushed
the
auto-update/ostree
branch
from
b8e74d8 to
4593aea
Compare
13 tasks
Member
|
@ofborg build pkgsMusl.ostree |
Member
|
Looks like the installed test here are another victim of GLib bindings no longer being shipped with gobject-introspection (#306080 (comment)) |
wegank
added
the
2.status: merge conflict
r-ryantm
force-pushed
the
auto-update/ostree
branch
from
4593aea to
1495e07
Compare
Contributor
Author
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ostreedev/ostree/releases. meta.description for ostree is: Git for operating system binaries meta.homepage for ostree is: https://ostreedev.github.io/ostree/ Updates performed
To inspect upstream changesImpactChecks done
Caution A test defined in
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from Cachix: (The Cachix cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
ofborg
bot
removed
the
2.status: merge conflict
wegank
added
the
2.status: merge conflict
Contributor
Author
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ostreedev/ostree/releases. meta.description for ostree is: Git for operating system binaries meta.homepage for ostree is: https://ostreedev.github.io/ostree/ Updates performed
To inspect upstream changesImpactChecks done
Caution A test defined in
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
r-ryantm
force-pushed
the
auto-update/ostree
branch
from
1495e07 to
3ba33b6
Compare
ofborg
bot
removed
the
2.status: merge conflict
github-actions
bot
added
10.rebuild-darwin: 0
jtojnar
force-pushed
the
auto-update/ostree
branch
from
3ba33b6 to
b91c8fa
Compare
jtojnar
force-pushed
the
auto-update/ostree
branch
from
4810250 to
7b5ac29
Compare
Member
|
Installed tests pass now: |
jtojnar
force-pushed
the
auto-update/ostree
branch
2 times, most recently
from
ec11eda to
4039605
Compare
LordGrimmauld
requested changes
Apr 14, 2025
pkgs/by-name/os/ostree/package.nix
Outdated
Contributor
There was a problem hiding this comment.
Is it intended to download a release tarball here and not use fetchFromGitHub instead? AIUI this is not bootstrap, so the github fetcher should be available
Member
There was a problem hiding this comment.
In the absence of policy saying otherwise, I prefer to use the official distribution method.
|
Partially reverts 1a56b35 Also make the patch comments clearly mention that they are for *installed* tests.
gobject-introspection 1.79 no longer ships GIR files for GLib since GLib 2.79 started generating them on its own: https://gitlab.gnome.org/GNOME/gobject-introspection/-/merge_requests/433 That resulted in the following error: JS ERROR: Error: Requiring GLib, version 2.0: Typelib file for namespace 'GLib', version '2.0' not found
jtojnar
force-pushed
the
auto-update/ostree
branch
from
4039605 to
8765133
Compare
Contributor
|
LordGrimmauld
approved these changes
Apr 14, 2025
wegank
added
the
12.approvals: 1
Member
|
Checked musl/static stuff is still fine. 👍 |
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
6 participants
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.
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ostreedev/ostree/releases.
meta.description for ostree is: Git for operating system binaries
meta.homepage for ostree is: https://ostree.readthedocs.io/en/latest/
Previous: #293303
Previous: #366997
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
passthru.testsdid not passRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
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 13 packages failed to build:
48 packages built:
Maintainer pings
cc @copumpkin for testing.