Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1708269
| Summary: | libnice-0.1.16 is available | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stefan Becker <chemobejk> | ||||||||
| Component: | libnice | Assignee: | Kamil Dudka <kdudka> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 29 | CC: | bdpepple, brian, brian.murrell, kdudka, philip, svashisht, upstream-release-monitoring, uraeus | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | libnice-0.1.16-3.fc31 libnice-0.1.16-3.fc30 libnice-0.1.16-3.fc29 libnice-0.1.16-3.fc28 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-05-14 00:59:28 UTC | 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Stefan Becker
2019-05-09 13:41:36 UTC
I'm building one right now to see if 0.1.15 addresses https://sourceforge.net/p/sipe/bugs/352/ Created attachment 1566238 [details] Update to 0.1.15 Seems like the URL & Source0 links are still the same, despite the git repository being moved to gitlab. No idea what the update monitoring is looking at... Attached is my patch to the fedora rpms/libnice repository: - Update to 0.1.15 - drop all upstream patches - drop autoreconf from build - add upstream patch to fix a test failure Scratch build for F29 can be found here: https://koji.fedoraproject.org/koji/taskinfo?taskID=34750701 Quick testing on my F29 machine didn't reveal any issues with Pidgin & SIPE. After I finished my previous change yesterday the project already released the next version 0.1.16. Unfortunately the maintainer forgot to tag it: https://gitlab.freedesktop.org/libnice/libnice/commit/5969b34e3acd9150506ed8d9d109c73665858f3e Created attachment 1566509 [details] Update to 0.1.16 Attached is my patch to the fedora rpms/libnice repository (on top of the previous 0.1.15 patch): - Update to 0.1.16 - drop all upstream patches Scratch build for F29 can be found here: https://koji.fedoraproject.org/koji/taskinfo?taskID=34760187 Quick testing on my F29 machine didn't reveal any issues with Pidgin & SIPE. *** Bug 1708379 has been marked as a duplicate of this bug. *** Thank you for preparing the update, Stefan! I have pushed both your patches: https://src.fedoraproject.org/rpms/libnice/c/279d176c https://src.fedoraproject.org/rpms/libnice/c/cf9b3c49 Then I pushed a patch to reintroduce autoreconf: https://src.fedoraproject.org/rpms/libnice/c/35231eb7 The updated packages are being built now. Stefan, would you like to become a co-maintainer of the libnice package in Fedora? If yes, please send me your fedoraproject ID. Created attachment 1566600 [details] test-new-dribble got renamed to test-new-trickle I missed the fact that dribble tests were renamed to trickle tests. Hence the workaround for the sometimes hanging test test-new-dribble wasn't applied to test-new-trickle. That one is probably causing the hang of the F28 package build. Attached patch updates the SPEC file to apply the workaround to the new test name instead. Scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=34763655 (In reply to Stefan Becker from comment #7) > Created attachment 1566600 [details] > test-new-dribble got renamed to test-new-trickle Thanks! Pushed as: https://src.fedoraproject.org/rpms/libnice/c/036913ac libnice-0.1.16-3.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ebaf0b317a libnice-0.1.16-3.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f5718c4c82 libnice-0.1.16-3.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-28ba01c186 libnice-0.1.16-3.fc30 has been pushed to the Fedora 30 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-2019-ebaf0b317a libnice-0.1.16-3.fc29 has been pushed to the Fedora 29 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-2019-f5718c4c82 libnice-0.1.16-3.fc28 has been pushed to the Fedora 28 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-2019-28ba01c186 libnice-0.1.16-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. libnice-0.1.16-3.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. libnice-0.1.16-3.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. |