Description of problem: Teamgit will not start. It print out a warning message: *** WARNING *** The program 'teamgit' uses the Apple Bonjour compatibility layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=teamgit> Version-Release number of selected component (if applicable): 2.20120202.fc18 How reproducible: Every time teamgit is run Steps to Reproduce: 1. run teamgit from the terminal 2. See warning about not using native avahi Actual results: Program does not start Expected results: Program should start Additional info: The warning points to this page: http://0pointer.de/avahi-compat?s=libdns_sd&e=teamgit
teamgit-0.0.12-1.20130626.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/teamgit-0.0.12-1.20130626.fc18
teamgit-0.0.12-1.20130626.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/teamgit-0.0.12-1.20130626.fc19
teamgit-0.0.12-1.20130626.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/teamgit-0.0.12-1.20130626.fc17
Package teamgit-0.0.12-1.20130626.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing teamgit-0.0.12-1.20130626.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12467/teamgit-0.0.12-1.20130626.fc18 then log in and leave karma (feedback).
teamgit-0.0.12-1.20130626.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
teamgit-0.0.12-1.20130626.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
teamgit-0.0.12-1.20130626.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.