Bug 1404683

Summary: wammu-0.43 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: wammuAssignee: Xavier Lamien <lxtnow>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: lxtnow, sergio
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: wammu-0.43-1.fc26 wammu-0.43-1.fc25 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-02 22:24:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. none

Description Upstream Release Monitoring 2016-12-14 12:24:29 UTC 
Latest upstream release: 0.43
Current version/release in rawhide: 0.42-1.fc26
URL: http://wammu.eu/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/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/6194/
Comment 1 Upstream Release Monitoring 2016-12-14 12:24:53 UTC 
Patching or scratch build for wammu-0.42 failed.
Comment 2 Upstream Release Monitoring 2016-12-14 12:24:55 UTC 
Created attachment 1231654 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.
Comment 3 Upstream Release Monitoring 2016-12-14 12:24:56 UTC 
Patches were not touched. All were applied properly
Comment 4 Upstream Release Monitoring 2017-08-20 04:15:46 UTC 
sergiomb's wammu-0.43-1.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=958991
Comment 5 Fedora Update System 2017-08-20 16:39:41 UTC 
gammu-1.38.4-1.fc26 python-gammu-2.9-2.fc26 wammu-0.43-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cebdbb301a
Comment 6 Fedora Update System 2017-08-21 01:22:38 UTC 
gammu-1.38.4-1.fc25, python-gammu-2.9-2.fc25, wammu-0.43-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e3dc87c542
Comment 7 Fedora Update System 2017-08-22 18:08:11 UTC 
gammu-1.38.4-1.fc26, python-gammu-2.9-2.fc26, wammu-0.43-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cebdbb301a
Comment 8 Fedora Update System 2017-09-02 22:24:17 UTC 
gammu-1.38.4-1.fc26, python-gammu-2.9-2.fc26, wammu-0.43-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2017-09-14 03:51:16 UTC 
gammu-1.38.4-1.fc25, python-gammu-2.9-2.fc25, wammu-0.43-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.