Bug 2412313

Summary:	prusa-slicer-2.9.4-rc1 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	prusa-slicer	Assignee:	Jan Pazdziora <adelton>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	adelton, jstanek, j, laurent.rineau__fedora, mhroncok, spotrh
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	adelton: needinfo? (j)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	prusa-slicer-2.9.4-1.fc43	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-03-22 00:54:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2025-11-04 18:43:46 UTC

Releases retrieved: 2.9.4-rc1
Upstream release that is considered latest: 2.9.4-rc1
Current version/release in rawhide: 2.9.3-1.fc44
URL: https://github.com/prusa3d/PrusaSlicer

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/20643/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/prusa-slicer

Comment 1 Laurent Rineau 2025-12-20 12:45:51 UTC

1. Prusa Slicer version 2.9.4 was released 2025-11-07:

   https://release-monitoring.org/project/20643/

   That is strange the monitoring bot have not updated this bug.

2. Version 2.9.4 is build in Rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2025-54eff9b2c2

   This bug could be closed.

3. Actually, could 2.9.4 be built for F42 and F43 as well?

4. I offer to co-maintain Prusa Slicer, if you would like:

  - I am a Fedora packager maintaining a few C++ packages around CGAL (www.cgal.org): https://src.fedoraproject.org/user/rineau/projects
  - Prusa Slicer does use `CGAL-devel` as a build requirement.
  - I am a user of the Prusa Slicer (I own a Prusa Core One printer).
  - I am a professional C++ developer.
  - I am willing to check why Prusa Slicer does not support Eigen3 version 5.0.x and contribute an upstream patch to fix it.

Comment 2 Jan Pazdziora 2025-12-20 13:03:12 UTC

I'd love more co-maintainers as my work over the past two years to keep the Fedora package up-to-date with upstream was mostly reactive, with not enough energy for some deeper investigations.

Jason, as the main admin, can you add Laurent in https://src.fedoraproject.org/rpms/prusa-slicer/settings#usersgroups-tab ?

Comment 3 Miro Hrončok 2025-12-20 18:25:06 UTC

I added them.

Comment 4 Jan Pazdziora 2026-03-12 10:06:49 UTC

Hello Laurent,

we currently have bug 2429718 filed reporting Fails to Install on Fedora 44 related to libboost, so we will likely need to make some plan. Will you be able to look at what seems to be the problem there?

Comment 5 Jan Pazdziora 2026-03-12 10:10:28 UTC

Hello Jason,

I can see Spot added https://src.fedoraproject.org/rpms/prusa-slicer/c/ddbac739fc9482082b06028e5606f74c06e1db07?branch=rawhide and built prusa-slicer-2.9.4-2.fc44 (https://koji.fedoraproject.org/koji/buildinfo?buildID=2861951) on 2025-11-15, so could this bugzilla be marked as resolved as the rebase to 2.9.4 has happened?

Yes, there is that bug 2429718 currently blocking installation on Fedora 44 but that is likely a new thing.

Or do we envision going back to 2.9.3 on Fedora 44 (I did not even look into whether it would make a difference) and this bug should stay open for the time being?

Comment 6 Jan Pazdziora 2026-03-13 05:46:30 UTC

Taking.

Comment 7 Jan Pazdziora 2026-03-13 07:10:56 UTC

Builds on Fedora rawhide and 44 are being fixed in bug 2429718.

I've also created https://src.fedoraproject.org/rpms/prusa-slicer/pull-request/65 to rebase to 2.9.4 in Fedora 43.

I don't plan to backport to Fedora 42.

Comment 8 Fedora Update System 2026-03-13 18:07:13 UTC

FEDORA-2026-a47f249288 (prusa-slicer-2.9.4-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-a47f249288

Comment 9 Jan Pazdziora 2026-03-13 18:08:01 UTC

Fedora 43 PR merged.

Fedora 43 build prusa-slicer-2.9.4-1.fc43 done: https://koji.fedoraproject.org/koji/buildinfo?buildID=2959130.

Comment 10 Fedora Update System 2026-03-14 02:56:07 UTC

FEDORA-2026-a47f249288 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-a47f249288`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-a47f249288

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Laurent Rineau 2026-03-18 13:53:16 UTC

(In reply to Jan Pazdziora from comment #4)
> Hello Laurent,
> 
> we currently have bug 2429718 filed reporting Fails to Install on Fedora 44
> related to libboost, so we will likely need to make some plan. Will you be
> able to look at what seems to be the problem there?

Sorry Jan, it seems I am a bit late, and bug #2429718 in the path to be fixed, now.

Comment 12 Fedora Update System 2026-03-22 00:54:27 UTC

FEDORA-2026-a47f249288 (prusa-slicer-2.9.4-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.