On ponedjeljak, 5. prosinca 2016. 15:46:43 CET Lisandro Damián Nicanor Pérez
Meyer wrote:
> Hi! Some time ago Thiago made possible to tag private symbols as such, at
> least on Linux. We have found some more symbols that need this tag
> (QTBUG-57060) and I'm tracking a possible new set on
Hi Thiago,
now I get confused.
>That's not enough. You need to
>cd qtbase && git checkout 5.8.0
When I do this I get the old code which does not compile.
Doing cd qtbase && git checkout 5.8 gives me the new code
>Possibly pull every now and again in there. If you need to be in the bleeding
> On 3 Dec 2016, at 00:36, Kevin Kofler wrote:
>
> Shawn Rutledge wrote:
>> http://www.galago-project.org/about.php
>>
>> sounds like it’s just for “presence” to tell instant-messaging clients
>> whether you are using the computer or not.
>
> I did not suggest you use
On terça-feira, 6 de dezembro de 2016 16:22:39 PST šumski wrote:
> On ponedjeljak, 5. prosinca 2016. 15:46:43 CET Lisandro Damián Nicanor Pérez
> Meyer wrote:
> > Hi! Some time ago Thiago made possible to tag private symbols as such, at
> > least on Linux. We have found some more symbols that need
> On 05 Dec 2016, at 14:11, Milian Wolff wrote:
Hi Milian,
> I'd like to see that happen, more testing is always a win. But we will need
> to
> learn from the coverity lessons:
which lessons? Feel free to reply off-list.
regards
holger
> On 05 Dec 2016, at 14:11, Milian Wolff wrote:
Hi Milian,
> I'd like to see that happen, more testing is always a win. But we will need
> to
> learn from the coverity lessons:
which lessons? Feel free to reply off-list.
regards
holger
On Tuesday, December 6, 2016 6:43:03 PM CET Holger Freyther wrote:
> > On 05 Dec 2016, at 14:11, Milian Wolff wrote:
> Hi Milian,
>
> > I'd like to see that happen, more testing is always a win. But we will
> > need to
> > learn from the coverity lessons:
>
> which
Thiago Macieira wrote:
> And I was actually affected by it: I wanted to backport an XRandR bugfix
> to libQt5XcbQpa, so I just built my own check out of qtbase on the tag +
> cherry- pick. But the lib wouldn't load because the ELF versions were
> different. I had to install qmake & qtbase
On martes, 6 de diciembre de 2016 16:14:39 ART you wrote:
[snip]
> > Contains:
> >
> > -verscript_content = "Qt_$${QT_MAJOR_VERSION}_PRIVATE_API {" \
> > +verscript_content =
> > "Qt_$${QT_MAJOR_VERSION}.$${QT_MINOR_VERSION}.$$
> > {QT_PATCH_VERSION}_PRIVATE_API {" \
> >
> > Do
On martes, 6 de diciembre de 2016 16:22:39 ART šumski wrote:
[snip]
> [1]
> https://build.opensuse.org/package/view_file/openSUSE:Leap:42.2/libqt5-qtba
> se/tell-the-truth-about-private-api.patch?expand=1
Maybe there's a typo in line 28? I see a double ')'
--
No hay preguntas tontas, solo
Thiago Macieira wrote:
> Do other people think that is useful? If so, I can make that permanent
> (though disabled for -developer-build).
>From a Fedora perspective, yes. It will make RPM automatically produce
symbol version dependencies that will correctly break when the package needs
Em terça-feira, 6 de dezembro de 2016, às 20:44:06 PST, Lisandro Damián
Nicanor Pérez Meyer escreveu:
> If I understand the patch correctly that would effectively change the symbol
> version on each new patch release. That's something at least us in Debian
> would like to avoid, but again, if
Em quarta-feira, 7 de dezembro de 2016, às 02:23:15 PST, Kevin Kofler escreveu:
> > I think I had thought of that when I originally came up with the idea, but
> > discarded it. I know I don't want it in developer builds for the same
> > reason that QObjectPrivate's constructor does not complain
Thiago Macieira wrote:
> It would change the ELF version for private symbols. The idea, I guess, is
> that if you forgot to rebuild, then the old .so fails to load. With the
> same ELF version, it would load and may do bad things.
Yes, but on RPM-based distributions, it would not even install,
On terça-feira, 6 de dezembro de 2016 15:53:37 PST Gunnar Roth wrote:
> Hi Thiago,
> now I get confused.
>
> >That's not enough. You need to
> >cd qtbase && git checkout 5.8.0
>
> When I do this I get the old code which does not compile.
> Doing cd qtbase && git checkout 5.8 gives me the new
On martes, 6 de diciembre de 2016 20:42:34 ART Lisandro Damián Nicanor Pérez
Meyer wrote:
> On martes, 6 de diciembre de 2016 16:22:39 ART šumski wrote:
> [snip]
>
> > [1]
> > https://build.opensuse.org/package/view_file/openSUSE:Leap:42.2/libqt5-qtb
> > a
> >
On martes, 6 de diciembre de 2016 08:41:38 ART Thiago Macieira wrote:
> On terça-feira, 6 de dezembro de 2016 16:22:39 PST šumski wrote:
> > On ponedjeljak, 5. prosinca 2016. 15:46:43 CET Lisandro Damián Nicanor
> > Pérez>
> > Meyer wrote:
> > > Hi! Some time ago Thiago made possible to tag
On Sat, Dec 03, 2016 at 12:36:48AM +0100, Kevin Kofler wrote:
> I did not suggest you use the Galago software, just this specification:
> https://people.gnome.org/~mccann/docs/notification-spec/notification-spec-latest.html
> older versions of which were hosted on:
>
On lunes, 5 de diciembre de 2016 11:13:59 ART Thiago Macieira wrote:
> Em segunda-feira, 5 de dezembro de 2016, às 15:46:43 PST, Lisandro Damián
>
> Nicanor Pérez Meyer escreveu:
> > Hi! Some time ago Thiago made possible to tag private symbols as such, at
> > least on Linux. We have found some
On 04/12/16 21:28, Peter Hartmann wrote:
> after Google announced their continuous fuzzing approach some days ago
> (see [1]), I tried to make Qt work with it and the fuzzing testcases I
> have written the last weeks ([2]).
>
> If people agree, we could try going forward with putting Qt onto
>
20 matches
Mail list logo