Skip to content
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

pixi add license_family on pixi update to unchaged packages in lock file #3288

Open
2 tasks done
trim21 opened this issue Mar 6, 2025 · 1 comment
Open
2 tasks done

Comments

@trim21
Copy link

trim21 commented Mar 6, 2025

before.zip

Checks

  • I have checked that this issue has not already been reported.

  • I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

before.zip
after.zip

Issue description

similar to #3233, this time it add license_family

the lock file is generated with 0.42.0 and I'm currently using 0.42.1 to run pixi update, zero package change but pixi add license_family to one of unchanged package.

❯❯ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
❯❯ pixi update
✔ Lock-file was already up-to-date
❯❯ git diff
diff --git a/pixi.lock b/pixi.lock
index b75034a..84c8f02 100644
--- a/pixi.lock
+++ b/pixi.lock
@@ -1313,6 +1313,7 @@ packages:
   - vc >=14.2,<15
   - vc14_runtime >=14.29.30139
   license: BSD-3-Clause
+  license_family: BSD
   size: 537509
   timestamp: 1741167468116
 - conda: https://conda.anaconda.org/conda-forge/noarch/six-1.17.0-pyhd8ed1ab_0.conda

Expected behavior

add it in the first place or do not add it at all

@trim21 trim21 changed the title pixi add license_family on pixi update to unchaged packages pixi add license_family on pixi update to unchaged packages in lock file Mar 6, 2025
@trim21
Copy link
Author

trim21 commented Mar 6, 2025

the changed package is https://prefix.dev/channels/conda-forge/packages/shapely , which just release a new build (version 2.0.7 build 1) 1 day ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant