Bug 1251308
Summary: | vdirsyncer-0.6.0 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | vdirsyncer | Assignee: | Michele Baldessari <michele> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | fedora, michele |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | vdirsyncer-0.6.0-1.fc23 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-15 02:21:10 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
2015-08-07 00:17:35 UTC
Failed to kick off scratch build. cmd: sha256sum /var/tmp/thn-LR0F41/100.0% return code: 1 stdout: stderr: sha256sum: /var/tmp/thn-LR0F41/100.0%: No such file or directory mathstuf's vdirsyncer-0.6.0-1.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=675938 vdirsyncer-0.6.0-1.fc23 has been submitted as an update for Fedora 23. https://admin.fedoraproject.org/updates/vdirsyncer-0.6.0-1.fc23 Package vdirsyncer-0.6.0-1.fc23: * should fix your issue, * was pushed to the Fedora 23 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing vdirsyncer-0.6.0-1.fc23' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-13057/vdirsyncer-0.6.0-1.fc23 then log in and leave karma (feedback). vdirsyncer-0.6.0-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. |