Bulk resource pack update fails with 'updated filename belongs to another content item' and proposes older 1.21.11 versions

Offen
  • Stimmt etwas nicht?
#8,108 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
43/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
backend, desktop

Rechercherichtung

Start by locating the bulk_update_content flow and the install runner's finalizing logic that raises “the updated filename belongs to another content item.” Compare how bulk updates choose resource pack versions with single-item updates, then inspect the related cases in #7783 and #7737. Done means bulk updates either complete when resource pack filenames collide or report which file or content item caused the failure.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Please confirm the following.
  • I checked the existing issues for duplicate problems
  • I have tried resolving the issue using the support portal
  • I have ensured my Modrinth App installation is up to date
What version of the Modrinth App are you using?

Modrinth App 0.22.0

What operating systems are you seeing the problem on?

Windows (Windows 11 Pro, x86_64)

Describe the bug

Running "Update all" (bulk_update_content) on an instance fails in the finalizing phase with:

instance_error: the updated filename belongs to another content item

The rollback completes and the instance is restored. The same batch failed six times in a row.

The batch contains nine resource pack updates. Five of them point to a version whose filename already exists in the instance as a separate file. Those are the candidates I suspect cause the conflict:

Current file Proposed version (Modrinth version ID) Filename already in the instance
§l3D§f Ladders v1.2.2 - 26.3.zip 1.2.1 for 1.21.11 (iUoPzfpq) §l3D§f+Ladders+v1.2.1 - 1.21.11.zip
Better Lanterns v1.4.0 - 26.2+26.3.zip 1.3.1 for 1.21.11 (CTRXQvvr) Better Lanterns v1.3.1 - 1.21.11.zip
Default-Dark-Mode-26.3-2026.9.0.zip 2026.4.0 for 1.21.11 (sPDc9hXF) Default-Dark-Mode-1.21.11-2026.4.0.zip
Fullbright-UB-26.3 fub-7.0.zip 6.0 (bjc4gBmv) Fullbright-UB-1.21 fub-6.0.zip
Redstone Tweaks 2.5.6.zip (not linked to a content entry) 2.5.3 (XauQUBeR) Redstone Tweaks 2.5.3.zip (linked content entry)

The instance runs Minecraft 1.21.11 (Fabric 0.19.5). Several packs exist in both a 26.x and a 1.21.11 variant as separate files, and some of the 26.x files were added manually rather than through the app. The proposed versions for the five packs above are older releases than the 26.x files currently in use.

Two more observations:

  • Version bJ4fiis6 (target for Totem Of Yuri.zip) is listed by the Modrinth API under a project named "fix" (jAw1CeUD), which does not look like the project the pack came from.
  • Mod and shader updates in the same instance do not show this error in the logs. I have not verified whether a bulk update of only mods succeeds.

Moving the four duplicate 1.21.11 files out of the instance folder (outside the app) did not make the batch succeed. The same error occurred on the next attempt, and the Redstone entry still conflicts.

This may be related to #7783 (same error message, closed) and #7737 (stale content links from manually replaced files blocking updates).

Steps to reproduce
  1. Create or use an instance on Minecraft 1.21.11 with Fabric.
  2. Have resource packs in both a 26.x and a 1.21.11 variant, some added manually to the resourcepacks/ folder.
  3. Click "Update all" so the batch contains resource pack updates like the ones in the table above.
  4. The install job fails during finalizing with the updated filename belongs to another content item.
Expected behavior

Either the resource packs update cleanly, or the job reports exactly which file or content item blocks the update.

Additional context

Workaround: updating these packs one at a time works.

Relevant log lines from launcher_logs/session_20261024_094943.log:

2026-10-24T09:55:20.947555400+02:00 ERROR theseus::install::runner: Install job 1855ad21-e6ec-4190-964e-b6f6d7c0ca07 failed: the updated filename belongs to another content item
2026-10-24T09:55:51.858209100+02:00 ERROR theseus::install::runner: Install job 933ca1c2-cfee-4c0a-aaca-85c6f7cc2f75 failed: the updated filename belongs to another content item
2026-10-24T10:02:42.853081300+02:00 ERROR theseus::install::runner: Install job 61603903-b2b9-43c4-aa59-438f0993b2fa failed: the updated filename belongs to another content item

Question: should a bulk update pick the version that matches the file already installed, or the newest version compatible with the instance's game version? The current batch appears to use the second behaviour, which downgrades packs and runs into existing files.

Vorherrschende Sprache
Rust
Sterne
2.5k
Forks
663
Ø Merge
2 T. 11 Std.
Gemergte PRs (30 T.)
122

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus modrinth/code

Alle Issues in modrinth/code

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.