infra/tickets

mirrormanager app no longer builds #13300

New issue

Closed

opened 2026-04-29 21:40:32 +00:00 by kevin · 1 comment

kevin commented

2026-04-29 21:40:32 +00:00

Owner

Description of request

In trying to move mirrormanager from deploymentconfig to deployment, I hit in staging that it wouldn't build.

The build fails with:

error: rustc 1.78.0 is not supported by the following packages:
  diesel@2.3.8 requires rustc 1.86.0
  diesel_derives@2.3.4 requires rustc 1.86.0
  diesel_derives@2.3.4 requires rustc 1.86.0
  diesel_derives@2.3.4 requires rustc 1.86.0
  diesel_table_macro_syntax@0.3.0 requires rustc 1.86.0
  dsl_auto_type@0.2.0 requires rustc 1.86.0
Either upgrade rustc or select compatible dependency versions with
`cargo update <name>@<current-ver> --precise <compatible-ver>`
where `<compatible-ver>` is the latest version supporting rustc 1.78.0

error: build error: building at STEP "RUN /tmp/scripts/assemble": while running runtime: exit status 101

It seems to be using a fedora 38 base. ;(

We should move it to fedora:44 (or fedora:latest) and fix the rust issues in staging.
Once everything is fixed in staging we can roll out the deploymentconfig -> deployment change.

I am hoping @abompard can look at this?

### Description of request In trying to move mirrormanager from deploymentconfig to deployment, I hit in staging that it wouldn't build. The build fails with: ``` error: rustc 1.78.0 is not supported by the following packages: diesel@2.3.8 requires rustc 1.86.0 diesel_derives@2.3.4 requires rustc 1.86.0 diesel_derives@2.3.4 requires rustc 1.86.0 diesel_derives@2.3.4 requires rustc 1.86.0 diesel_table_macro_syntax@0.3.0 requires rustc 1.86.0 dsl_auto_type@0.2.0 requires rustc 1.86.0 Either upgrade rustc or select compatible dependency versions with `cargo update <name>@<current-ver> --precise <compatible-ver>` where `<compatible-ver>` is the latest version supporting rustc 1.78.0 error: build error: building at STEP "RUN /tmp/scripts/assemble": while running runtime: exit status 101 ``` It seems to be using a fedora 38 base. ;( We should move it to fedora:44 (or fedora:latest) and fix the rust issues in staging. Once everything is fixed in staging we can roll out the deploymentconfig -> deployment change. I am hoping @abompard can look at this?

abompard self-assigned this

2026-04-30 08:05:18 +00:00

smoliicek added the

labels

2026-04-30 19:05:36 +00:00

abompard referenced this issue from a commit

2026-05-04 07:25:00 +00:00

Move mirrormanager to the Python 3.14 image

abompard closed this issue

2026-05-04 07:25:00 +00:00

zlopez added this to the Sprint ( 2026-04-20 to 2026-05-04 ) project

2026-05-04 07:52:16 +00:00

abompard commented

2026-05-04 08:57:57 +00:00

Member

Fixed by 18dc805

Fixed by [18dc805](https://forge.fedoraproject.org/infra/ansible/commit/18dc8053f7f5c961063735b9712a6a76edc3c1e2)

Sign in to join this conversation.

No labels

forgejo_migration

Needs investigation

packager_workflow_blocker

🔥 URGENT 🔥

Waiting on Assignee

Waiting on External

Waiting on Reporter

release-monitoring

request-for-resources

websites-general

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

infra/tickets#13300

No description provided.