nixpkgs icon indicating copy to clipboard operation
nixpkgs copied to clipboard

Remove Folly AUR Fetch

Open dthelegend opened this issue 1 week ago • 4 comments

This patch removes a fetch from the AUR. I noticed the AUR now block curl requests (at least mine) due to anubis (understandable really).

Things done

  • Built on platform:
    • [x] x86_64-linux
    • [ ] aarch64-linux
    • [ ] x86_64-darwin
    • [ ] aarch64-darwin
  • Tested, as applicable:
  • [ ] Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • [ ] Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • [ ] Package update: when the change is major or breaking.
  • NixOS Release Notes
    • [ ] Module addition: when adding a new NixOS module.
    • [ ] Module update: when the change is significant.
  • [ ] Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

Add a :+1: reaction to pull requests you find important.

dthelegend avatar Dec 13 '25 16:12 dthelegend

Could you update commit message to be like: "folly: inline patch due errors fetching from AUR" or something similar?

techknowlogick avatar Dec 13 '25 17:12 techknowlogick

folly: inline patch due errors fetching from AUR

No worries, done 👍🏾

dthelegend avatar Dec 13 '25 17:12 dthelegend

@dthelegend Amazing! Thanks:)

techknowlogick avatar Dec 13 '25 18:12 techknowlogick

I have another patch for w3m as well as I found that one also pulls from the AUR (found because I'm trying to build my entire OS from source). Would you rather I bundle in that patch and any other patches I find one might need to build from source at home here? Or would you rather they stay separate PRs?

EDIT: I have several patches for various packages accumulated now, I would rather not drown you in PRs (more than you may already be), so advice on how to submit all the patches is welcome :)

dthelegend avatar Dec 13 '25 19:12 dthelegend

I have several patches for various packages accumulated now, I would rather not drown you in PRs (more than you may already be), so advice on how to submit all the patches is welcome :)

How many is "several"? If it's less than 5-10 or so (and you already have separate patches for each package), separate PRs for each package would be great. If it's more, doing them all in one PR would make more sense.

Also: welcome! :)

mdaniels5757 avatar Dec 14 '25 05:12 mdaniels5757

Successfully created backport PR for staging-25.11:

  • #470773

nixpkgs-ci[bot] avatar Dec 14 '25 15:12 nixpkgs-ci[bot]