Skip to content

chore: update rucio-clients to 40.2.0#313

Open
panta-123 wants to merge 6 commits into
masterfrom
update-rucio-clients
Open

chore: update rucio-clients to 40.2.0#313
panta-123 wants to merge 6 commits into
masterfrom
update-rucio-clients

Conversation

@panta-123

Copy link
Copy Markdown
Contributor

Briefly, what does this PR introduce? Please link to any relevant presentations or discussions.

Reference: spack/spack-packages#5166

What is the urgency of this PR?

  • High (please describe reason below)
  • Medium
  • Low

Rcuio server is updated to release-40 onJune 16 , thus the need to update the client too.

What kind of change does this PR introduce?

  • Bug fix (issue #__)
  • New feature (issue #__)
  • Optimization (issue #__)
  • Updated documentation
  • other: __

Please check if any of the following apply

  • This PR introduces breaking changes. Please describe changes users need to make below.
  • This PR changes default behavior. Please describe changes below.
  • AI was used in preparing this PR. Please describe usage below.

@wdconinc

Copy link
Copy Markdown
Contributor

We don't automatically pick up spack-packages merges, so you have to add the respective commit to spack-packages.sh to cherry-pick it.

@panta-123 panta-123 force-pushed the update-rucio-clients branch from 8ee828b to 40a6024 Compare June 20, 2026 02:22
Comment thread spack-packages.sh
add cherry picked commit hash of spack packages
@panta-123 panta-123 force-pushed the update-rucio-clients branch from 40a6024 to 75d733c Compare June 20, 2026 14:13
@wdconinc wdconinc enabled auto-merge (squash) June 20, 2026 17:14
@wdconinc

Copy link
Copy Markdown
Contributor

This change seems to introduce duplicate packages. Likely a dependency of rucio-clients is newer than what is pinned or limited for another package.

@panta-123

Copy link
Copy Markdown
Contributor Author

@wdconinc , checks are still failing.... Are you working on it ?

@wdconinc

Copy link
Copy Markdown
Contributor

At a conference this week...

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

Successfully merging this pull request may close these issues.

3 participants