Bug 2354655

Summary: Update NetworkManager-ssh to 1.3.0 (Upstream)
Product: [Fedora] Fedora Reporter: Dan Fruehauf <malkodan>
Component: NetworkManager-sshAssignee: Dan Fruehauf <malkodan>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 41CC: echevemaster, malkodan
Target Milestone: ---Keywords: Upstream
Target Release: ---   
Hardware: All   
OS: Linux   
URL: https://github.com/danfruehauf/NetworkManager-ssh
Whiteboard:
Fixed In Version: NetworkManager-ssh-1.3.1-1.fc42 NetworkManager-ssh-1.3.1-1.fc41 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-03-31 01:23:57 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 Dan Fruehauf 2025-03-24 23:48:22 UTC
Update to version 1.3.0 from upstream

Reproducible: Always

Steps to Reproduce:
Nil
Actual Results:  
Nil

Expected Results:  
Updated to version 1.3.0

Comment 1 Fedora Update System 2025-03-25 00:20:29 UTC
FEDORA-2025-02fab79a8c (NetworkManager-ssh-1.3.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-02fab79a8c

Comment 2 Fedora Update System 2025-03-25 00:21:02 UTC
FEDORA-2025-59baaa5f56 (NetworkManager-ssh-1.3.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-59baaa5f56

Comment 3 Dan Fruehauf 2025-03-25 00:21:25 UTC
Update has been pushed to f41, f42 and rawhide.

Comment 4 Fedora Update System 2025-03-26 01:03:51 UTC
FEDORA-2025-59baaa5f56 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-59baaa5f56`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-59baaa5f56

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

Comment 5 Fedora Update System 2025-03-26 01:31:34 UTC
FEDORA-2025-02fab79a8c has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-02fab79a8c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-02fab79a8c

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

Comment 6 Fedora Update System 2025-03-28 15:25:50 UTC
FEDORA-2025-6990b43b90 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6990b43b90`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6990b43b90

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

Comment 7 Fedora Update System 2025-03-28 16:18:00 UTC
FEDORA-2025-41fa3e7158 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-41fa3e7158`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-41fa3e7158

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

Comment 8 Fedora Update System 2025-03-31 01:23:57 UTC
FEDORA-2025-6990b43b90 (NetworkManager-ssh-1.3.1-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-04-05 01:25:43 UTC
FEDORA-2025-41fa3e7158 (NetworkManager-ssh-1.3.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.