Skip to content

w3m: 0.5.3+git20230121 → 0.5.4; add toastal to maintainers#430585

Merged
philiptaron merged 3 commits intoNixOS:stagingfrom
toastal:w3m-0.5.4
Aug 15, 2025
Merged

w3m: 0.5.3+git20230121 → 0.5.4; add toastal to maintainers#430585
philiptaron merged 3 commits intoNixOS:stagingfrom
toastal:w3m-0.5.4

Conversation

@toastal
Copy link
Contributor

@toastal toastal commented Aug 3, 2025

tats/w3m#304

Maintainership & blessing has been handed off from tats to rtka. The code is now actively developed on SourceHut.

Things done

  • Built on platform:
    • 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 👍 reaction to pull requests you find important.

1

Footnotes

  1. Please consider giving up MS GitHub or offering a non-proprietary, non-US-corporate-controlled mirror for this free software project (like w3m just did!). I wish to delete this Microsoft account in the future, but I need more projects like this to support alternative methods to send patches & contribute.

@toastal toastal requested a review from anthonyroussel August 3, 2025 10:05
@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin: 5001+ This PR causes many rebuilds on Darwin and must target the staging branches. 10.rebuild-linux: 5001+ This PR causes many rebuilds on Linux and must target the staging branches. labels Aug 3, 2025
@anthonyroussel
Copy link
Member

@toastal
Copy link
Contributor Author

toastal commented Aug 3, 2025 via email

@toastal toastal changed the base branch from master to staging-next August 3, 2025 13:14
@nixpkgs-ci nixpkgs-ci bot closed this Aug 3, 2025
@toastal toastal requested a review from anthonyroussel August 3, 2025 13:14
@nixpkgs-ci nixpkgs-ci bot reopened this Aug 3, 2025
@toastal
Copy link
Contributor Author

toastal commented Aug 3, 2025

@anthonyroussel I believe all is addressed… comments & staging-next

@toastal toastal force-pushed the w3m-0.5.4 branch 2 times, most recently from 36bd617 to 78974c7 Compare August 4, 2025 06:28
@toastal
Copy link
Contributor Author

toastal commented Aug 4, 2025

Looks like the formatter failed on the an extra newline

@toastal toastal changed the base branch from staging-next to staging August 4, 2025 06:29
@nixpkgs-ci nixpkgs-ci bot closed this Aug 4, 2025
@nixpkgs-ci nixpkgs-ci bot reopened this Aug 4, 2025
@nix-owners
Copy link

nix-owners bot commented Aug 4, 2025

The PR's base branch is set to staging, but 190 commits from the master branch are included. Make sure you know the right base branch for your changes, then:

  • If the changes should go to the master branch, change the base branch to master
  • If the changes should go to the staging branch, rebase your PR onto the merge base with the staging branch:
    # git rebase --onto $(git merge-base upstream/staging HEAD) $(git merge-base upstream/master HEAD)
    git rebase --onto fa154dda31ab1a92efb0d1b79bacc6c6174c5333 20089a898226b2c73114804f6833364f073605e4
    git push --force-with-lease

@toastal
Copy link
Contributor Author

toastal commented Aug 4, 2025

Oh… good bot. Forgot where I needed to rebase from. Switched to using finalAttrs.

Copy link
Contributor

@philiptaron philiptaron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you assess whether the patches are still needed?

Anyone who is able, please run nixpkgs-review pr 430585 -p w3m --no-shell --post-result - I'd love to merge this and that would help.

@philiptaron
Copy link
Contributor

TIL that w3m is part of every NixOS system because of this:

https://discourse.nixos.org/t/nixos-documentation-nixos-help-use-w3m-1-by-default/3124

@toastal
Copy link
Contributor Author

toastal commented Aug 15, 2025

nixpkgs-review pr 430585 -p w3m --no-shell is building a lot of packages (as pointed out). GNU coreutils 9.7 had a failure after an hour of compiling the universe across 2 machines. Rebasing, as maybe that is fixed.

@toastal
Copy link
Contributor Author

toastal commented Aug 15, 2025

Crap, rebased off the default branch again.

@nix-owners
Copy link

nix-owners bot commented Aug 15, 2025

The PR's base branch is set to staging, but 29 commits from the master branch are included. Make sure you know the right base branch for your changes, then:

  • If the changes should go to the master branch, change the base branch to master
  • If the changes should go to the staging branch, rebase your PR onto the merge base with the staging branch:
    # git rebase --onto $(git merge-base upstream/staging HEAD) $(git merge-base upstream/master HEAD)
    git rebase --onto ee11c0fef4ce23fa64299c30243eb0f4e1db4845 c202cddaf0aa39c9200af733cc088433b5c3406f
    git push --force-with-lease

Let us rejoice in the code forge moving away from Microsoft GitHub!
@toastal
Copy link
Contributor Author

toastal commented Aug 15, 2025

As for the patches, they still apply as the code in those spots haven’t changed. The fetched one uncomments values in struct cmdtable schemetable[], & the one in Nixpkgs does something with EDG for randomness? I can’t tell you want these are for off the top of my head.

@toastal toastal requested a review from philiptaron August 15, 2025 03:40
@toastal
Copy link
Contributor Author

toastal commented Aug 15, 2025

TIL that w3m is part of every NixOS system because of this:

I have used this before in specifically the NixOS ISO to set up a new device.

Copy link
Contributor

@philiptaron philiptaron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm running the nixpkgs-review.

@nixpkgs-ci nixpkgs-ci bot added the 12.approvals: 1 This PR was reviewed and approved by one person. label Aug 15, 2025
@philiptaron
Copy link
Contributor

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 430585 --package w3m
Commit: 76d0ab5d74796392aabd37454c4dfee142f99a4e


x86_64-linux

✅ 1 package built:
  • w3m

@philiptaron philiptaron merged commit 3d9e6dd into NixOS:staging Aug 15, 2025
27 of 29 checks passed
@toastal toastal deleted the w3m-0.5.4 branch August 15, 2025 14:58
@toastal toastal mentioned this pull request Aug 23, 2025
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin: 5001+ This PR causes many rebuilds on Darwin and must target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 5001+ This PR causes many rebuilds on Linux and must target the staging branches. 12.approvals: 1 This PR was reviewed and approved by one person.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants