qq: 3.2.9_240606 -> 3.2.9_240617
Description of changes
qq: 3.2.9_240606 -> 3.2.9_240617
It is seemed that libuuid.so is used to generate uuid. I found the error when the first time opening the new version.
By the way, add me as maintainer because the old maintainer doesn't response for a long time.
Things done
- Built on platform(s)
- [x] x86_64-linux
- [ ] aarch64-linux
- [ ] x86_64-darwin
- [ ] aarch64-darwin
- For non-Linux: Is sandboxing enabled in
nix.conf? (See Nix manual)- [ ]
sandbox = relaxed - [ ]
sandbox = true
- [ ]
- [x] Tested, as applicable:
- NixOS test(s) (look inside nixos/tests)
- and/or package tests
- or, for functions and "core" functionality, tests in lib/tests or pkgs/test
- made sure NixOS tests are linked to the relevant packages
- [ ] Tested compilation of all packages that depend on this change using
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage - [x] Tested basic functionality of all binary files (usually in
./result/bin/) - 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
- [ ] (Package updates) Added a release notes entry if the change is major or breaking
- [ ] (Module updates) Added a release notes entry if the change is significant
- [ ] (Module addition) Added a release notes entry if adding a new NixOS module
- [x] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4105
backport to 24.05 please
hello?
To get review, you can ping some people who reviewed previous PRs of this package.
Please do not include commits like this: Merge branch 'NixOS:master' into updateqq. Use git rebase to resolve conflicts instead. Here is the doc: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#how-to-create-pull-requests.
Backport failed because this pull request contains merge commits. You can either backport this pull request manually, or configure the action to skip merge commits.
Oh, no.