Conversation
5eb8b0f to
8d1ba71
Compare
8d1ba71 to
b5fc5b3
Compare
b5fc5b3 to
5eba4b7
Compare
|
Result of 32 packages marked as broken and skipped:
22 packages failed to build:
179 packages built:
|
|
From the build failures, only irods is caused by this bump, the others seem to be unrelated failing tests. Fixing irods seems to be rather involved, and a bump and some cleanup would be very helpful. @bzizou would be available to help with that? |
|
I just discovered that |
|
@doronbehar & @marsam, may I ask you for a review? |
doronbehar
left a comment
There was a problem hiding this comment.
Thanks for all the work! Pretty much the same review comment multiplied.
pkgs/applications/networking/instant-messengers/nheko/default.nix
Outdated
Show resolved
Hide resolved
5eba4b7 to
ae1831a
Compare
pkgs/applications/networking/instant-messengers/nheko/default.nix
Outdated
Show resolved
Hide resolved
Hi. Just back from holiday, sorry. I can try to upgrade irods packages. Should I wait for this PR to be merged before? |
It can be fixed independently. |
cb73c16 to
904fd80
Compare
|
Looks great now, but there are build failures according to ofborg. One of them is a patch to nheko failing to apply. |
904fd80 to
6a90877
Compare
|
The or-tools failure is related to protobuf. The best way to solve this is to update to the latest version, but that is not trivial. |
And have you touched protobuf in this PR? Or do you think I can find |
It is broken on master. I would link to it but hydra is down. |
|
And what is the package that depends on `or-tools`? I mean, why is ofborg trying to build `or-tools`?
|
For openroad. |
|
Then why did you bother to update openroad, and write patches for it, if one of it's dependencies is failing to build?
…On 5 September 2023 20:21:45 GMT+03:00, tobim ***@***.***> wrote:
> And what is the package that depends on `or-tools`? I mean, why is ofborg trying to build `or-tools`?
For openroad.
--
Reply to this email directly or view it on GitHub:
#250435 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
|
Because it wasn't broken when I started this PR. I think adding the fix here makes the most sense. |
|
I tried to run |
I see, and I agree. |
|
I think it's important to see a nixpkgs-review report for this. |
|
Fixed irods package into #253632 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
It could be that my machine is too weak to run all of these nixpkgs-review builds together, that's why so many of them failed... I'm still investigating. Someone else's |
|
Result of 42 packages marked as broken and skipped:
23 packages failed to build:
175 packages built:
|
|
Interesting.. I wonder why |
I think nixpkgs-review only reports on packages that are affected by the change. |
|
Result of 42 packages marked as broken and skipped:
5 packages failed to build:
193 packages built:
|
|
I ran: And indeed running |
|
Thanks for all the work @tobim ! |
Description of changes
https://github.com/gabime/spdlog/releases/tag/v1.12.0
Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)