Fix for annoying bug / library maintenance
Hi, https://svn.boost.org/trac/boost/ticket/4964 This is out there for years. To me this seems to be clearly explained and a fix is provided, but apparently all bugs assigned to 'bgubenko' aren't monitored (for years there has been no reaction). So is there a way of getting the fix ever applied? Or are such unmaintained libraries just doomed to eventually die, despite the efforts of the people reporting bugs and posting patches? Thanks, Filip
On 3/21/2014 8:58 AM, Filip Konvička wrote:
Hi,
https://svn.boost.org/trac/boost/ticket/4964
This is out there for years. To me this seems to be clearly explained and a fix is provided, but apparently all bugs assigned to 'bgubenko' aren't monitored (for years there has been no reaction).
So is there a way of getting the fix ever applied? Or are such unmaintained libraries just doomed to eventually die, despite the efforts of the people reporting bugs and posting patches?
Thanks, Filip
You could do a pull request for the interval library on the 'develop' branch. If the maintainer of 'interval' does not respond to that, then Boost could look for a co-maintainer who would do so. Also I suggest that you add an interval test as part of your pull request that shows the bug and that also shows that your fix is working. https://svn.boost.org/trac/boost/wiki/StartModPatchAndPullReq
On 23 March 2014 18:34, Edward Diener <eldiener@tropicsoft.com> wrote:
On 3/21/2014 8:58 AM, Filip Konvička wrote:
Hi,
https://svn.boost.org/trac/boost/ticket/4964
This is out there for years. To me this seems to be clearly explained and a fix is provided, but apparently all bugs assigned to 'bgubenko' aren't monitored (for years there has been no reaction).
So is there a way of getting the fix ever applied? Or are such unmaintained libraries just doomed to eventually die, despite the efforts of the people reporting bugs and posting patches?
Thanks, Filip
You could do a pull request for the interval library on the 'develop' branch. If the maintainer of 'interval' does not respond to that, then Boost could look for a co-maintainer who would do so. Also I suggest that you add an interval test as part of your pull request that shows the bug and that also shows that your fix is working.
https://svn.boost.org/trac/boost/wiki/StartModPatchAndPullReq
If enough people get involved, the new boost-maint list will be a good place to discuss things like this: http://lists.boost.org/boost-maint/
Daniel James (25.3.2014 9:29):
On 23 March 2014 18:34, Edward Diener <eldiener@tropicsoft.com <mailto:eldiener@tropicsoft.com>> wrote:
On 3/21/2014 8:58 AM, Filip Konvička wrote:
Hi,
https://svn.boost.org/trac/__boost/ticket/4964 <https://svn.boost.org/trac/boost/ticket/4964>
This is out there for years. To me this seems to be clearly explained and a fix is provided, but apparently all bugs assigned to 'bgubenko' aren't monitored (for years there has been no reaction).
So is there a way of getting the fix ever applied? Or are such unmaintained libraries just doomed to eventually die, despite the efforts of the people reporting bugs and posting patches?
Thanks, Filip
You could do a pull request for the interval library on the 'develop' branch. If the maintainer of 'interval' does not respond to that, then Boost could look for a co-maintainer who would do so. Also I suggest that you add an interval test as part of your pull request that shows the bug and that also shows that your fix is working.
https://svn.boost.org/trac/__boost/wiki/__StartModPatchAndPullReq <https://svn.boost.org/trac/boost/wiki/StartModPatchAndPullReq>
If enough people get involved, the new boost-maint list will be a good place to discuss things like this:
Edward, Daniel, thanks. I will do that (both the pull request and the test). I will eventually post a note on the boost-maint list if there is no response.
You could do a pull request for the interval library on the 'develop' branch. If the maintainer of 'interval' does not respond to that, then Boost could look for a co-maintainer who would do so. Also I suggest that you add an interval test as part of your pull request that shows the bug and that also shows that your fix is working.
https://svn.boost.org/trac/boost/wiki/StartModPatchAndPullReq
I succeeded in cloning the interval library and applying my patch locally. But I was not successful in running the regression tests; bjam says: link.jam: No such file or directory ..\..\..\..\Jamroot:154: in modules.load ERROR: rule "link-directory" unknown in module "Jamfile<C:\build\boost_1_55_0>". C:/build/boost_1_55_0/tools/build/v2/build\project.jam:311: in load-jamfile C:/build/boost_1_55_0/tools/build/v2/build\project.jam:64: in load <snip> I was hoping that I could really provide a test for what my patch fixes. By searching some forums I found out that this is probably due to the process of moving Boost from SVN to Git, and I'm not sure whether or not it makes sense that I fetch the most recent snapshot (from Git? or SVN?) of Boost for the regression test run. Or do you think that I should just make the pull request on just the code change? (The fix is quite simple...) Thanks, Filip
On 5/30/2014 07:59 AM, Filip Konvička wrote:
Or do you think that I should just make the pull request on just the code change? (The fix is quite simple...) I'd go ahead and make the pull request (with your proposed test included.)
If the library is unmaintained, this would seem to be the fastest way towards getting the community maintenance involved. Cheers, Brandon Kohn
participants (4)
-
Brandon Kohn -
Daniel James -
Edward Diener -
Filip Konvička