-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
staging-next 2023-05-16 #232237
Merged
Merged
staging-next 2023-05-16 #232237
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://github.com/sqlalchemy/sqlalchemy/releases/tag/rel_2_0_10 https://github.com/sqlalchemy/sqlalchemy/releases/tag/rel_2_0_11 https://github.com/sqlalchemy/sqlalchemy/releases/tag/rel_2_0_12 https://github.com/sqlalchemy/sqlalchemy/releases/tag/rel_2_0_13
python310Packages.sqlalchemy: 2.0.9 -> 2.0.13
When installing many python packages, a `direct_url.json` file appeared in the lib directory. Example: ```sh ➤ nix build nixpkgs/29755fec55e58a315b517d431b2be261772f2b80#python3Packages.flask ➤ cat result/lib/python3.10/site-packages/Flask-2.2.3.dist-info/direct_url.json {"archive_info": {}, "url": "file:///build/Flask-2.2.3/dist/Flask-2.2.3-py3-none-any.whl"}⏎ ``` As you can see, that file contains a wrong reference to `/build`. In https://discuss.python.org/t/pep-610-usage-guidelines-for-linux-distributions/4012/4 there's an explanation on how to avoid this. Here, I'm implementing that change for nixpkgs. @moduon MT-1075
postgresql: 15.3, 14.8, 13.11, 12.15 and 11.20
X-Reverse-Dependencies: python3.pkgs.aiobotocore
vcunat
requested review from
thoughtpolice,
marsam,
FRidh and
jonringer
as code owners
May 16, 2023 13:38
alsa-ucm-conf: 1.2.8 -> 1.2.9
12 tasks
12 tasks
…file" Certain packages were failing since this was merged. #229472 (comment) This reverts commit bff6c67.
[staging-next] Pipewire 0.3.71
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
1.severity: security
Issues which raise a security issue, or PRs that fix one
6.topic: python
6.topic: ruby
10.rebuild-darwin: 501+
10.rebuild-darwin: 5001+
10.rebuild-linux: 501+
10.rebuild-linux: 5001+
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to 23.05 schedule, breaking changes aren't allowed anymore (except desktop environments). This should be the last time when we pull the
staging
branch in a way that reaches 23.05.Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Mass breakages
(will be edited based on progress)