I tested on my local environment by using 'fedpkg local' and Koji by using 'fedpkg build'.
Here is the successful Koji build. https://koji.fedoraproject.org/koji/taskinfo?taskID=37727342
LGTM because I tested on my local environment by using 'fedpkg' and Koji.
Here is the successful Koji build. https://koji.fedoraproject.org/koji/buildinfo?buildID=1267367
This package is a relatively obscure package. Therefore I set a karma (feedback) level at one.
LGTM because I tested on my local environment by using 'fedpkg' and Koji.
Here is the successful Koji build. https://koji.fedoraproject.org/koji/buildinfo?buildID=1267362
This package is a relatively obscure package. Therefore I set a karma (feedback) level at one.
LGTM because I tested on my local environment by using 'fedpkg' and Koji.
Here is the successful Koji build. https://koji.fedoraproject.org/koji/buildinfo?buildID=1267361
This package is a relatively obscure package. Therefore I set a karma (feedback) level at one.
The update from 1.0.32 to 1.0.36 breaks the ABI. However I think the upgrade will not cause a widespread or serious problem for Fedora users because libfullock-1.0.32-1 is the first version that released only 10 days ago. Moreover libfullock is a relatively obscure package.
The main reason of breaking ABI is fixing typo: https://github.com/yahoojapan/fullock/pull/22
This update is generally functional. Karma +1.
LGTM because I tested on my local environment by using 'fedpkg' and Koji.
Here is the successful Koji build. https://koji.fedoraproject.org/koji/taskinfo?taskID=33941967
I set a karma (feedback) level at one because This package is a relatively obscure package. https://fedoraproject.org/wiki/Package_update_HOWTO#Update_attributes
Unretire and update from 1.4.3 to 2.0.0