feat: add lib.fetchurl function #13
No reviewers
Labels
No labels
Compat
Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: auxolotl/foundation#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "srxl/foundation:fetchurl"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Same change as auxolotl/labs#27 - we should use that wrapper here as well.
f763483699to5418b05ccbWIP: feat: add lib.fetchurl functionto feat: add lib.fetchurl function5418b05ccbto5ab0169d3eIs this needed since we talked about moving this to
lib?Are we? FWIW, I disagree with doing that - it's specific to bootstrapping, and I don't think it's something we should really encourage use of, especially outside of foundation/tidepool.
@srxl wrote in #13 (comment):
These are Nix primitives (fetchurl, fetchTarball, <nix/fetchurl.nix>) without any system requirements. They are provided by Nix itself, we would only be aliasing them on
liblike other helpers. Nothing stops a user from using them if we choose not to alias them. The only difference is that it would make 'lib` consistent.For some reason this fails on hydra at the moment, will investigate later: https://hydra.aux-cache.dev/build/2111/nixlog/1/tail
@ -5,2 +5,2 @@pins = import ./npins;lib = import pins.lib;pins = import ./npins;lib = (import pins.lib).extend (final: prev: prev // {Can we put the fetcher in a namespace?
I attempted to merge this into main locally on my end and test it. After doing that, I get the following:
I think this has something to do with the wrong version of
libbeing passed through?Anyway, I agree with Jake that this belongs in lib, so I think we should add it there rather than here? Unless I'm misunderstanding, I think that this is not specific to bootstrapping, but please feel free to tell me more.
I just hit the same failure locally, but without this patch. It seemed to be intermittent. Maybe related to gnutar impurity in ctime/mtime?
huhhh
the Hydra failure above ends with
ohhhh.... yes I see. normally it wouldn't need to re-run autotools, because their output is checked into the source tree. something about the timestamps, though, convinced it that the autoconf inputs were newer than their outputs, so it tried to re-run but the dependencies it needs for that don't exist at this stage of bootstrapping.
was this what your local failure looked like as well? the gnutar change should only affect certain corner cases that I don't think actually apply, but something else maybe messed with the timestamps?
This isn't something similar to what we fixed in PR#1 and PR#2, is it? Somehow the mode not always getting unpacked correctly, and that causing problems .. somehow?? My memory is so bad the days, I can't remember that far back ..
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.