Ubuntu
z3 package

z3 is incorrectly marked as a MIR candidate

Bug #1971128 reported by Lukas Märdian
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rustc (Ubuntu)
Fix Released
High
Unassigned
Jammy
Fix Released
Medium
Simon Chopin
Kinetic
Fix Released
High
Unassigned
z3 (Ubuntu)
Invalid
High
Unassigned
Jammy
Invalid
Medium
Unassigned
Kinetic
Invalid
High
Unassigned

Bug Description

rustc pulls llvm-13 into main (the llvm-toolchain-13 being already partially seeded, it doesn't raise any issue), and z3 is a dependency of it.

See original description
Lukas Märdian (slyon)
tags: added: fr-2334
Simon Chopin (schopin)
summary: - [MIR] z3
+ z3 is incorrectly marked as a MIR candidate
description: updated
Revision history for this message
Simon Chopin (schopin) wrote :

Since we're shipping rustc primarily as a packaging tool, we can simply demote the llvm-13 Recommends to a Suggests, and instead add it to rust-all (which is in universe)

Changed in z3 (Ubuntu Kinetic):
importance: Undecided → High
Changed in rustc (Ubuntu Kinetic):
importance: Undecided → High
Changed in rustc (Ubuntu Jammy):
importance: Undecided → Medium
Changed in z3 (Ubuntu Jammy):
importance: Undecided → Medium
status: New → Invalid
Changed in z3 (Ubuntu Kinetic):
status: Incomplete → Invalid
Changed in rustc (Ubuntu Jammy):
status: New → Confirmed
Changed in rustc (Ubuntu Kinetic):
status: New → Confirmed
Changed in rustc (Ubuntu Jammy):
assignee: nobody → Simon Chopin (schopin)
Revision history for this message
Simon Chopin (schopin) wrote :
Revision history for this message
Lukas Märdian (slyon) wrote :

Thank you Simon, the changes LGTM and resolve a component-mismatch without the need to do an additional MIR for src:z3.

A test build is available at:
https://launchpad.net/~schopin/+archive/ubuntu/rustc-1.59/+sourcepub/13649849/+listing-archive-extra

I've sponsored your debdiff into Kinetic.

Changed in rustc (Ubuntu Kinetic):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package rustc - 1.59.0+dfsg1-1~ubuntu2

---------------
rustc (1.59.0+dfsg1-1~ubuntu2) kinetic; urgency=medium

  * Drop llvm-13 to Suggests for rustc to avoid having to promote it to Ubuntu
    main (LP: #1971128)

 -- Simon Chopin <email address hidden> Mon, 30 May 2022 09:59:01 +0200

Changed in rustc (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

I see no references to llvm-13-dev from rustc in jammy, and this has been resolved in kinetic by relaxing the package relationship, so closing this task.

Changed in rustc (Ubuntu Jammy):
status: Confirmed → Invalid
Revision history for this message
Simon Chopin (schopin) wrote :

The chain is rustc -> llvm-13 -> llvm-13-dev -> z3, so that's still an issue with Jammy, I think. Reopening :)

Changed in rustc (Ubuntu Jammy):
status: Invalid → Confirmed
Revision history for this message
Simon Chopin (schopin) wrote :

For some reason the bug hasn't been closed automatically when the new version hit jammy-security. Marking it as Fix Released manually.

Changed in rustc (Ubuntu Jammy):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.