Bug 2310844

Summary: New upstream version for whatsup
Product: [Fedora] Fedora EPEL Reporter: andrew-boatrocker <andrew.klaassen>
Component: whatsupAssignee: Neil Hanlon <neil>
Status: ASSIGNED --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: david.brown, neil
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description andrew-boatrocker 2024-09-09 13:40:57 UTC
Description of problem:

Upstream has developed and merged a fix for an issue I was having running whatsup with >100 nodes.

Merge:

https://github.com/chaos/whatsup/commit/f16afb5bf331667fee15330e74db2b0ae92ce3f9

Issue:

https://github.com/chaos/whatsup/issues/20

Comment 1 Neil Hanlon 2024-09-09 16:17:45 UTC
This seems reasonable. Do you have any idea if 1.15 has any breaking changes compared to 1.14? That will inform the EPEL update.

Comment 2 Neil Hanlon 2024-09-09 16:27:27 UTC
I've posed this to the maintainer, as well: https://github.com/chaos/whatsup/issues/23

Comment 3 andrew-boatrocker 2024-09-09 16:45:11 UTC
I also posed it to the maintainer, before I saw that you had.  :-)