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

Support --force with cph create #232

Open
2 tasks done
Callek opened this issue Mar 5, 2024 · 1 comment
Open
2 tasks done

Support --force with cph create #232

Callek opened this issue Mar 5, 2024 · 1 comment
Labels
stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability

Comments

@Callek
Copy link
Contributor

Callek commented Mar 5, 2024

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

When modifying a given file that is already in a package, running cph create doesn't seem to re-add or modify files that were already present.

Having a --force that behaves like transmute --force would be useful.

Why is this needed?

In manual testing I:

  • extracted a windows package (.tar.bz2) with cph extract
  • locally codesigned a binary
  • tried to update the .tar.bz2 with cph create ... into the same location as the original

The md5sum of the package did not change, indicating that it was not modified.

What should happen?

The package should be able to be updated/recreated in-place

Additional Context

I created a branch in https://github.com/Callek/conda-package-handling/tree/add-force-create to try and explore doing this, but I ran into an issue with my testing method (it seems the files get updated timestamps) and ran against my wall-clock allotment on looking into this.

I don't know if I'll get back to it, but I'm more than happy if anyone wants to take my work and drive it forward.

@Callek Callek added the type::feature request for a new feature or capability label Mar 5, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Mar 5, 2024
Copy link

github-actions bot commented Mar 5, 2025

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant