Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
El sáb., 24 nov. 2018 15:19, Julian Gilbey escribió: > On Fri, Nov 23, 2018 at 10:07:47AM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > Hi Julian! > > > > El jueves, 22 de noviembre de 2018 21:54:30 -03 Julian Gilbey escribió: > > > On Sun, Nov 18, 2018 at 03:35:11PM +, Julian Gilbey wrote: > > > > On Sun, Nov 18, 2018 at 09:01:19AM -0300, Lisandro Damián Nicanor > Pérez > > Meyer wrote: > > > > > Yesterday I've uploaded qtbase with this fix, please try it. > > > > > > > > Excellent, thanks! I just built it on my testing machine, and it > > > > worked perfectly with the Python script in this bug report and the > > > > simplebrowser example. > > > > > > Hi Lisandro, > > > > > > Upstream have now patched what-I-presume-will-become 5.12.1 with > > > almost this patch. But it's gone through several iterations, and now > > > the patch also deletes a couple of #include's. See patch set #7 at > > > https://codereview.qt-project.org/#/c/245294/ > > > > > > I doubt it's worth uploading a new version just for this, but when you > > > are doing the next qtbase upload, you might consider making this > > > change. > > > > That's exactly the patch with which I closed this bug. This is already > in the > > archive. Enjoy! > > Hi Lisandro, > > Version 7 of the patch is slightly different from the one you applied > to the archive: it also removes some conditional #includes. But it is > probably unimportant for Debian. Thank you for the clarification. Dmitry made me note the same thing, and yes, is unimportant. >
Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
On Fri, Nov 23, 2018 at 10:07:47AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Hi Julian! > > El jueves, 22 de noviembre de 2018 21:54:30 -03 Julian Gilbey escribió: > > On Sun, Nov 18, 2018 at 03:35:11PM +, Julian Gilbey wrote: > > > On Sun, Nov 18, 2018 at 09:01:19AM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > > > Yesterday I've uploaded qtbase with this fix, please try it. > > > > > > Excellent, thanks! I just built it on my testing machine, and it > > > worked perfectly with the Python script in this bug report and the > > > simplebrowser example. > > > > Hi Lisandro, > > > > Upstream have now patched what-I-presume-will-become 5.12.1 with > > almost this patch. But it's gone through several iterations, and now > > the patch also deletes a couple of #include's. See patch set #7 at > > https://codereview.qt-project.org/#/c/245294/ > > > > I doubt it's worth uploading a new version just for this, but when you > > are doing the next qtbase upload, you might consider making this > > change. > > That's exactly the patch with which I closed this bug. This is already in the > archive. Enjoy! Hi Lisandro, Version 7 of the patch is slightly different from the one you applied to the archive: it also removes some conditional #includes. But it is probably unimportant for Debian. Best wishes, Julian
Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
Hi Julian! El jueves, 22 de noviembre de 2018 21:54:30 -03 Julian Gilbey escribió: > On Sun, Nov 18, 2018 at 03:35:11PM +, Julian Gilbey wrote: > > On Sun, Nov 18, 2018 at 09:01:19AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > > > Yesterday I've uploaded qtbase with this fix, please try it. > > > > Excellent, thanks! I just built it on my testing machine, and it > > worked perfectly with the Python script in this bug report and the > > simplebrowser example. > > Hi Lisandro, > > Upstream have now patched what-I-presume-will-become 5.12.1 with > almost this patch. But it's gone through several iterations, and now > the patch also deletes a couple of #include's. See patch set #7 at > https://codereview.qt-project.org/#/c/245294/ > > I doubt it's worth uploading a new version just for this, but when you > are doing the next qtbase upload, you might consider making this > change. That's exactly the patch with which I closed this bug. This is already in the archive. Enjoy! -- Antiguo proverbio del Viejo Machi: "Prefiero que mi cerebro esté en la cresta de la ola, y mi PC un paso atrás sirviéndolo y no tener mi PC en el 'estado del arte' y mi cerebro un paso atrás asistiéndola." http://www.grulic.org.ar/lurker/message/20090507.020516.ffda0441.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
On Sun, Nov 18, 2018 at 03:35:11PM +, Julian Gilbey wrote: > On Sun, Nov 18, 2018 at 09:01:19AM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: > > Yesterday I've uploaded qtbase with this fix, please try it. > > Excellent, thanks! I just built it on my testing machine, and it > worked perfectly with the Python script in this bug report and the > simplebrowser example. Hi Lisandro, Upstream have now patched what-I-presume-will-become 5.12.1 with almost this patch. But it's gone through several iterations, and now the patch also deletes a couple of #include's. See patch set #7 at https://codereview.qt-project.org/#/c/245294/ I doubt it's worth uploading a new version just for this, but when you are doing the next qtbase upload, you might consider making this change. Best wishes, Julian
Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
On Sun, Nov 18, 2018 at 09:01:19AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Yesterday I've uploaded qtbase with this fix, please try it. Excellent, thanks! I just built it on my testing machine, and it worked perfectly with the Python script in this bug report and the simplebrowser example. Best wishes, Julian
Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
Yesterday I've uploaded qtbase with this fix, please try it.
Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
On Sat, Nov 17, 2018 at 04:16:30PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Hi Julian! > > On Sat, 17 Nov 2018 at 16:03, Julian Gilbey wrote: > > > > For information, upstream (Michal Klocek) has now produced a much > > better patch: https://codereview.qt-project.org/#/c/245294/ > > Thanks for the pointer! And rest assured we will include it as soon as > possible, as you can see both Dmitry and I have been watching it > already. Hi Lisandro! Pleasure. As you can imagine, I was very pleased to finally track down this bug! Best wishes, Julian
Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
Hi Julian! On Sat, 17 Nov 2018 at 16:03, Julian Gilbey wrote: > > For information, upstream (Michal Klocek) has now produced a much > better patch: https://codereview.qt-project.org/#/c/245294/ Thanks for the pointer! And rest assured we will include it as soon as possible, as you can see both Dmitry and I have been watching it already. Cheers, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
For information, upstream (Michal Klocek) has now produced a much better patch: https://codereview.qt-project.org/#/c/245294/ Best wishes, Julian
Bug#912925: Is the SONAME the same for all the related libs?
On Fri, 2018-11-09 at 08:36 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Hi! Looking at the bug I do have a question: is the libGL.so. > SONAME the > same on all the implementations? > > I'm currently asking upstream why they are dlopening it instead of > just > linking to it, so knowing this detail will certainly help. > > Thanks in advance! Yes. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#912925: Is the SONAME the same for all the related libs?
Hi! Looking at the bug I do have a question: is the libGL.so. SONAME the same on all the implementations? I'm currently asking upstream why they are dlopening it instead of just linking to it, so knowing this detail will certainly help. Thanks in advance! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
