bd sync: 2026-01-15 19:41:26
Some checks failed
Update Nix Packages with nix-update / nix-update (push) Failing after 1s

This commit is contained in:
m3tm3re
2026-01-15 19:41:26 +01:00
parent 8cd56cfd97
commit 50f845425b
2 changed files with 4 additions and 3 deletions

View File

@@ -18,4 +18,4 @@
{"id":"nixpkgs-sys","title":"Update config file format to include args per project","description":"Update the config file at ~/.config/rofi-project-opener/config to support per-project args. Change from PROJECT_DIRS to a format that encodes both path and args, e.g. JSON or structured text.","status":"closed","priority":1,"issue_type":"task","created_at":"2026-01-05T12:45:51.793810575+01:00","created_by":"m3tam3re","updated_at":"2026-01-05T12:48:21.75755315+01:00","closed_at":"2026-01-05T12:48:21.75755315+01:00","close_reason":"Config file now writes JSON (projects.json) with per-project path and args","dependencies":[{"issue_id":"nixpkgs-sys","depends_on_id":"nixpkgs-w3u","type":"parent-child","created_at":"2026-01-05T12:46:01.400263722+01:00","created_by":"m3tam3re"},{"issue_id":"nixpkgs-sys","depends_on_id":"nixpkgs-e2u","type":"blocks","created_at":"2026-01-05T12:46:04.055948778+01:00","created_by":"m3tam3re"}]}
{"id":"nixpkgs-w3u","title":"projectDirs should support args, for example --agent \u003cagentname\u003e","description":"This means project directories need to be an attribute set and we also need to change the launch command to \"opencode \u003cdirectory name\u003e \u003carguments\u003e\".\n","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-01-05T11:56:13.844735432+01:00","created_by":"m3tam3re","updated_at":"2026-01-05T12:49:42.34144046+01:00","closed_at":"2026-01-05T12:49:42.34144046+01:00","close_reason":"Feature complete: projectDirs now supports args per directory"}
{"id":"nixpkgs-xi7","title":"There is a bug in the basecamp-mcp server","description":"OSError: [Errno 30] Read-only file system when trying to write log file.\n\nTraceback:\nFile: /nix/store/708ksr7z3484bj8faysd7djwpa8xvw12-basecamp-mcp-server-0.0.1-unstable/lib/basecamp-mcp-server/basecamp_fastmcp.py, line 35\nError: logging.FileHandler(LOG_FILE_PATH) - attempting to write to read-only Nix store location: /nix/store/708ksr7z3484bj8faysd7djwpa8xvw12-basecamp-mcp-server-0.0.1-unstable/lib/basecamp-mcp-server/basecamp_fastmcp.log\n\nThe package needs to use a writable directory (e.g., XDG_DATA_HOME or /tmp) for log files instead of the Nix store.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-01-12T18:16:37.597147907+01:00","created_by":"m3tam3re","updated_at":"2026-01-12T19:12:57.91076765+01:00","closed_at":"2026-01-12T19:12:57.91076765+01:00","close_reason":"Closed"}
{"id":"nixpkgs-yya","title":"Fix Gitea Actions authentication: checkout step failing with 'could not read Username'","description":"The nix-update workflow is failing at the checkout step with authentication errors when trying to fetch from https://code.m3ta.dev\n\n## Error Details\n\nThe workflow fails at the 'Checkout repository' step with:\n\n\nThe git fetch command retries 3 times and fails each time with exit code 128.\n\n## Investigation Needed\n\n1. Verify the NIX_UPDATE_TOKEN secret is properly configured in Gitea repository settings\n2. Check if the token has the correct permissions (read/write repository)\n3. Investigate why the checkout action's token parameter isn't working with Gitea\n4. Consider alternative authentication methods:\n - Embedding credentials in the URL\n - Using SSH instead of HTTPS\n - Using git credential helper in the workflow\n5. Check if this is a known issue with Gitea Actions + actions/checkout@v4\n\n## Log Reference\n\nFull error logs available in: /home/m3tam3re/Downloads/nix-update-nix-update-5.log\n\n## Workflow File\n\n.gitea/workflows/nix-update.yml (lines 23-27)\n\n## Impact\n\nThe automated package update workflow cannot run successfully, blocking all automated nix-update operations.","notes":"Additional investigation steps:\n\n1. Found SSH keys at ~/.ssh/gitea and ~/.ssh/gitea.pub - suggests SSH authentication might be viable\n2. The workflow is running on 'm3-atlas-runner' with Gitea Actions\n3. The git config shows: 'http.https://code.m3ta.dev/.extraheader AUTHORIZATION: basic ***' \n4. The error suggests the extraheader approach isn't working with Gitea's action runner\n\nPossible quick fixes to try:\n- Use SSH URL format instead of HTTPS in checkout action\n- Add manual git credential configuration before checkout\n- Use server URL with embedded token: https://token@code.m3ta.dev/m3tam3re/nixpkgs\n- Check Gitea runner's docs for checkout action compatibility","status":"in_progress","priority":1,"issue_type":"bug","owner":"p@m3ta.dev","created_at":"2026-01-15T19:14:27.322946651+01:00","created_by":"m3tm3re","updated_at":"2026-01-15T19:21:15.537768383+01:00"}
{"id":"nixpkgs-yya","title":"Fix Gitea Actions authentication: checkout step failing with 'could not read Username'","description":"The nix-update workflow is failing at the checkout step with authentication errors when trying to fetch from https://code.m3ta.dev\n\n## Error Details\n\nThe workflow fails at the 'Checkout repository' step with:\n\n\nThe git fetch command retries 3 times and fails each time with exit code 128.\n\n## Investigation Needed\n\n1. Verify the NIX_UPDATE_TOKEN secret is properly configured in Gitea repository settings\n2. Check if the token has the correct permissions (read/write repository)\n3. Investigate why the checkout action's token parameter isn't working with Gitea\n4. Consider alternative authentication methods:\n - Embedding credentials in the URL\n - Using SSH instead of HTTPS\n - Using git credential helper in the workflow\n5. Check if this is a known issue with Gitea Actions + actions/checkout@v4\n\n## Log Reference\n\nFull error logs available in: /home/m3tam3re/Downloads/nix-update-nix-update-5.log\n\n## Workflow File\n\n.gitea/workflows/nix-update.yml (lines 23-27)\n\n## Impact\n\nThe automated package update workflow cannot run successfully, blocking all automated nix-update operations.","notes":"Additional investigation steps:\n\n1. Found SSH keys at ~/.ssh/gitea and ~/.ssh/gitea.pub - suggests SSH authentication might be viable\n2. The workflow is running on 'm3-atlas-runner' with Gitea Actions\n3. The git config shows: 'http.https://code.m3ta.dev/.extraheader AUTHORIZATION: basic ***' \n4. The error suggests the extraheader approach isn't working with Gitea's action runner\n\nPossible quick fixes to try:\n- Use SSH URL format instead of HTTPS in checkout action\n- Add manual git credential configuration before checkout\n- Use server URL with embedded token: https://token@code.m3ta.dev/m3tam3re/nixpkgs\n- Check Gitea runner's docs for checkout action compatibility","status":"closed","priority":1,"issue_type":"bug","owner":"p@m3ta.dev","created_at":"2026-01-15T19:14:27.322946651+01:00","created_by":"m3tm3re","updated_at":"2026-01-15T19:41:06.779588719+01:00","closed_at":"2026-01-15T19:41:06.779588719+01:00","close_reason":"Closed"}