New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fvwm: 2.6.7 -> 2.6.8 #41565
fvwm: 2.6.7 -> 2.6.8 #41565
Conversation
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/fvwm/versions. These checks were done: - built on NixOS - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm2 passed the binary check. - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-perllib passed the binary check. - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-convert-2.6 passed the binary check. - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-menu-xlock passed the binary check. - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-menu-directory passed the binary check. - Warning: no invocation of /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-menu-desktop had a zero exit code or showed the expected version - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-menu-headlines passed the binary check. - Warning: no invocation of /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/xpmroot had a zero exit code or showed the expected version - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm passed the binary check. - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/FvwmCommand passed the binary check. - Warning: no invocation of /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-root had a zero exit code or showed the expected version - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-config passed the binary check. - /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8/bin/fvwm-bug passed the binary check. - 10 of 13 passed binary check by having a zero exit code. - 3 of 13 passed binary check by having the new version present in output. - found 2.6.8 with grep in /nix/store/kycw0a7gqxh0v7lxq001j9sjysnz1v6h-fvwm-2.6.8 - directory tree listing: https://gist.github.com/94e21d8ab3a4808980c94f1fbb20f1b6 - du listing: https://gist.github.com/6db3d3e079f7808b93a1bbc20e5f396e
Success on x86_64-linux (full log) Attempted: fvwm Partial log (click to expand)
|
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: fvwm Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: fvwm Partial log (click to expand)
|
Looks like a fairly minor release, and it Works for Me. It does restart X, though, which is annoying. I haven't looked too deeply into the window manager setup; is there a way to prevent X from restarting (and just keep running the old fvwm until X restarts for some other reason)? (Or, is there any effort in the works to warn what services will be restarted by a Also, according to the release notes, "fvwm-menu-desktop(1) now requires python3 as an explicit dependency." We should probably be pulling in python3 for this, but given that it currently doesn't work in fvwm 2.6.7, it can be a separate PR. |
@edanaher thanks for testing.
None that I'm aware of, unfortunately.
You can test that with
Agreed. |
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fvwm/versions.
These checks were done:
meta.description for fvwm is: '"A multiple large virtual desktop window manager"'.
cc @edanaher for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
Test this build: