Uh oh!
There was an error while loading. Please reload this page.
fix: repoint civiccore wheel dependency to townlight/core (post org-transfer) - #8
Open
scottconverse wants to merge 1 commit into
Open
fix: repoint civiccore wheel dependency to townlight/core (post org-transfer)#8scottconverse wants to merge 1 commit into
scottconverse wants to merge 1 commit into
Conversation
…ransfer) CivicSuite org (repo included) was transferred to townlight on 2026-08-12 ~17:45 UTC, with CivicSuite retained as an empty redirect tombstone. civiccore itself was independently renamed CivicSuite/civiccore -> townlight/core at an earlier point too. The pinned civiccore wheel dependency here still points at the old CivicSuite/civiccore location, riding a redirect chain (org rename + repo rename) to resolve. At this exact pinned commit, this repo's own Dockerfile.civicsuite build hit this directly in the umbrella townlight/townlight repo's installer-cleanroom CI, ~3h after the transfer: Collecting civiccore@ https://github.com/CivicSuite/civiccore/releases/download/v1.2.0/civiccore-1.2.0-py3-none-any.whl#sha256=... (from civicnotice==0.2.0) ERROR: Could not install packages due to an OSError: HTTPSConnectionPool(host='github.com', port=443): Max retries exceeded with url: /CivicSuite/civiccore/releases/download/v1.2.0/civiccore-1.2.0-py3-none-any.whl (Caused by ResponseError('too many 503 error responses')) Repoints the URL at the canonical townlight/core release directly (same tag, same asset, same sha256 -- verified reachable) to remove the redirect hop. Part of the 2026-08-12 CivicSuite -> townlight org-transfer cleanup tracked from townlight/townlight PR #246. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Part of the 2026-08-12 CivicSuite -> townlight org-transfer maintenance, tracked from townlight/townlight PR #246.
Context
The CivicSuite org (including this repo) was transferred to the
townlightorg on 2026-08-12 ~17:45 UTC, withCivicSuiteretained as an empty redirect tombstone.civiccoreitself was also independently renamedCivicSuite/civiccore->townlight/coreat an earlier point.pyproject.toml's pinnedciviccorewheel dependency still points at the oldCivicSuite/civiccorelocation, so resolving it requires riding an org-rename + repo-rename redirect chain. This repo, at this exact pinned commit, is the one that directly failed with it -- its ownDockerfile.civicsuitebuild hit this in the umbrellatownlight/townlightrepo'sinstaller-cleanroomCI, ~3h after the transfer:Fix
Repoints the URL at the canonical
townlight/corerelease directly -- same tag (v1.2.0), same asset, samesha256, verified reachable viacurlbefore opening this PR. Removes the redirect hop instead of depending on it indefinitely.Not merged -- opened for review since this branch was cut directly from the exact commit
townlight/townlight's CI workflows currently pin (2bf0c9d7b764af84cd042657a972e84213a261d5), so merging changes what that pin resolves to; whoever owns the pin bump intownlight/townlightshould coordinate that alongside merging this.Co-Authored-By: Claude Fable 5 noreply@anthropic.com