Skip to content

Add a how-to for fixing a packaging error#2757

Open
mgorny wants to merge 4 commits intoconda-forge:mainfrom
mgorny:howto-packaging-error
Open

Add a how-to for fixing a packaging error#2757
mgorny wants to merge 4 commits intoconda-forge:mainfrom
mgorny:howto-packaging-error

Conversation

@mgorny
Copy link
Contributor

@mgorny mgorny commented Feb 23, 2026

PR Checklist:

  • note any issues closed by this PR with closing keywords
  • if you are adding a new page under docs/ or community/, you have added it to the sidebar in the corresponding _sidebar.json file
  • put any other relevant information below

Signed-off-by: Michał Górny <mgorny@quansight.com>
@mgorny mgorny requested a review from a team as a code owner February 23, 2026 19:10
@netlify
Copy link

netlify bot commented Feb 23, 2026

Deploy Preview for conda-forge-previews ready!

Name Link
🔨 Latest commit 04755a6
🔍 Latest deploy log https://app.netlify.com/projects/conda-forge-previews/deploys/699dfbf4e6e515000738bd7b
😎 Deploy Preview https://deploy-preview-2757--conda-forge-previews.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 71
Accessibility: 96
Best Practices: 100
SEO: 89
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Co-authored-by: jaimergp <jaimergp@users.noreply.github.com>
Comment on lines 7 to 10
Sometimes a serious packaging error may be discovered once the packages are built and published.
For example, some necessary files may be missing, and part of the functionality may stop working
correctly after an upgrade. Besides publishing a fixed version, it may be desirable to remove the
broken packages to prevent users from installing them.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's clarify that this is not a problem in the source code upstream, but indeed a packaging error introduced while building the artifacts. IOW, it can be fixed without requiring modifications to the source code and hence with the same upstream archive and version.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hopefully clarified a bit now.

mgorny and others added 2 commits February 24, 2026 20:26
Co-authored-by: jaimergp <jaimergp@users.noreply.github.com>
Signed-off-by: Michał Górny <mgorny@quansight.com>
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.

2 participants