Bug 2441048 - Update Request: Update to v2.1.x
Summary: Update Request: Update to v2.1.x
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mosquitto
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Jonathan Wright
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-19 18:27 UTC by andreaswahlen
Modified: 2026-02-20 09:00 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description andreaswahlen 2026-02-19 18:27:03 UTC
Description of problem:
Newest available package version is 2.0.22, while mosquitto itself is already at 2.1.2. 2.1 comes with major (non breaking) changes, I would like to take advantage of. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Peter Robinson 2026-02-19 18:34:31 UTC
In short I am not prepared to move EPEL (meant to be very stable) to a new release that has only been in rawhide 2 weeks, and is not yet even in a Fedora stable release.

Comment 2 andreaswahlen 2026-02-19 21:48:38 UTC
(In reply to Peter Robinson from comment #1)
> In short I am not prepared to move EPEL (meant to be very stable) to a new
> release that has only been in rawhide 2 weeks, and is not yet even in a
> Fedora stable release.

I am not saying, that it should happen immediately. I mostly want to raise awareness for this and ask, if there is any rough time frame or plan, when (if at all) we can expect an update of mosquitto in EPEL.

Comment 3 Peter Robinson 2026-02-20 09:00:46 UTC
There is no timeframe or plan, it will be a thin line between when it's stable (it's had 2 fixes release already, I have a bunch of things to chase U/S), when 2.0 goes EOL, and when I can be bothered to care about EPEL.


Note You need to log in before you can comment on or make changes to this bug.