On Tue, Sep 16, 2014 at 11:26 AM, Bhushan Shah bhus...@gmail.com wrote:
is working fine, will correct it in little time..
Solved in http://commits.kde.org/ark/cf4c338216908f7b50fc1c36be753cb34b7daecc
--
Bhushan Shah
http://bhush9.github.io
IRC Nick : bshah on Freenode
Thanks Bushan,
On 16 Sep 2014, at 08:00 , Bhushan Shah bhus...@gmail.com wrote:
Solved in http://commits.kde.org/ark/cf4c338216908f7b50fc1c36be753cb34b7daecc
indeed, it did! :-)
Another example how useful building on a different toolchain can be!!!
Greets,
Marko
P.S.: I hope you could
See
http://build.kde.org/job/kwindowsystem_master_qt5/Variation=All,label=LINBUILDER/98/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
On Sept. 15, 2014, 8:34 nachm., Thomas Lübking wrote:
src/netwm.cpp, line 4630
https://git.reviewboard.kde.org/r/120213/diff/1/?file=312330#file312330line4630
Tarzan speech. Consider:
- TakeFocusProtocol
- Protocol::TakeFocus
Martin Gräßlin wrote:
we are (to my
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120213/#review66633
---
Ship it!
Ship It!
- Thomas Lübking
On Sept. 16, 2014,
Martin GräßlinOn Monday 15 September 2014 09:44:59 wrote:
Hi Ivan,
could you please have a look at KWindowInfoX11Test::testActivities. The unit
test fails on the CI system and also locally with a setup similar to CI
system (passes with KWin, though). To get a clean setup ensure to have an
On Sept. 15, 2014, 10:28 nachm., Thomas Lübking wrote:
If we merge, we should imo merge in NetWinInfo - having the same function
return different values in NetWinInfo and KWindowInfo feels wrong.
Martin Gräßlin wrote:
I considered it, but decided against it as I consider NETWinInfo
On Sept. 16, 2014, 12:28 a.m., Thomas Lübking wrote:
If we merge, we should imo merge in NetWinInfo - having the same function
return different values in NetWinInfo and KWindowInfo feels wrong.
Martin Gräßlin wrote:
I considered it, but decided against it as I consider NETWinInfo
On Sept. 15, 2014, 10:28 nachm., Thomas Lübking wrote:
If we merge, we should imo merge in NetWinInfo - having the same function
return different values in NetWinInfo and KWindowInfo feels wrong.
Martin Gräßlin wrote:
I considered it, but decided against it as I consider NETWinInfo
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120228/
---
Review request for KDE Frameworks and KDEPIM.
Repository: kdepim
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120228/#review66639
---
It adds a new string, please ask kde-i18n-doc about an
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120217/
---
(Updated Sept. 16, 2014, 9:48 a.m.)
Status
--
This change has been
On Sept. 2, 2014, 6:37 p.m., Marco Martin wrote:
I'm a bit worried by the multitude of user and distro specific scripts that
rely on kdesu being present :/
Marco Martin wrote:
to me either way it gets fixed i'm ok.
the other option is to keep it called kdesu, so it wouldn't be
See
http://build.kde.org/job/kwindowsystem_master_qt5/Variation=All,label=LINBUILDER/99/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
On Sept. 2, 2014, 6:54 p.m., Hrvoje Senjan wrote:
in kde4 kdesu was installed under bin
it was actually also in libexec. just that KStandardDirs::findExe() looked
in libexec paths, QStandardPaths doesn't...
right, it seems on both places here, but is probably a distro thing.
Any idea
On Sept. 2, 2014, 6:54 p.m., Hrvoje Senjan wrote:
in kde4 kdesu was installed under bin
it was actually also in libexec. just that KStandardDirs::findExe() looked
in libexec paths, QStandardPaths doesn't...
Marco Martin wrote:
right, it seems on both places here, but is
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120213/
---
(Updated Sept. 16, 2014, 8:20 a.m.)
Status
--
This change has been
See
http://build.kde.org/job/kwindowsystem_master_qt5/Variation=All,label=LINBUILDER/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
See
http://build.kde.org/job/kwindowsystem_master_qt5/Variation=All,label=LINBUILDER/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
See
http://build.kde.org/job/kwindowsystem_master_qt5/Variation=All,label=LINBUILDER/102/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Hi all,
I just had a little problem with a new autotest for kwindowsystem which passed
on my setup, but failed on build.kde.org. It turned out that it's missing an
xcb_flush(QX11Info::connection()) before blocking in the event loop. I fixed
this problem in Qt, so I'm wondering: which version
On 2014-09-15, Alexander Richardson arichardson@gmail.com wrote:
However, is this even possible? Building manpages seems to require KDocTools
and kcoreaddons is a tier1 framework which would make this impossible.
Do we really need a manpage for it? It seems to me that it is only
used in
On Tue, Sep 16, 2014 at 9:12 PM, Martin Gräßlin mgraess...@kde.org wrote:
Hi all,
Hi Martin,
I just had a little problem with a new autotest for kwindowsystem which passed
on my setup, but failed on build.kde.org. It turned out that it's missing an
xcb_flush(QX11Info::connection()) before
On Tuesday 16 September 2014 21:17:37 Ben Cooksley wrote:
On Tue, Sep 16, 2014 at 9:12 PM, Martin Gräßlin mgraess...@kde.org wrote:
Hi all,
Hi Martin,
I just had a little problem with a new autotest for kwindowsystem which
passed on my setup, but failed on build.kde.org. It turned out
On Tue, Sep 16, 2014 at 9:22 PM, Martin Gräßlin mgraess...@kde.org wrote:
On Tuesday 16 September 2014 21:17:37 Ben Cooksley wrote:
On Tue, Sep 16, 2014 at 9:12 PM, Martin Gräßlin mgraess...@kde.org wrote:
Hi all,
Hi Martin,
I just had a little problem with a new autotest for
On Tuesday 16 September 2014 21:23:54 Ben Cooksley wrote:
I wrote this a bit too quickly.
The correct url is
http://build.kde.org/view/External_Deps/job/qt5_master_qt5/
What the system means by stable in the output is that is the branch
that it should theoretically be building against.
On Tue, Sep 16, 2014 at 9:45 PM, Martin Gräßlin mgraess...@kde.org wrote:
On Tuesday 16 September 2014 21:23:54 Ben Cooksley wrote:
I wrote this a bit too quickly.
The correct url is
http://build.kde.org/view/External_Deps/job/qt5_master_qt5/
What the system means by stable in the output is
On Sept. 2, 2014, 6:54 p.m., Hrvoje Senjan wrote:
in kde4 kdesu was installed under bin
it was actually also in libexec. just that KStandardDirs::findExe() looked
in libexec paths, QStandardPaths doesn't...
Marco Martin wrote:
right, it seems on both places here, but is
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120185/#review66656
---
this approach is probably better than
On Tuesday 16 September 2014 21:50:57 Ben Cooksley wrote:
On Tue, Sep 16, 2014 at 9:45 PM, Martin Gräßlin mgraess...@kde.org wrote:
On Tuesday 16 September 2014 21:23:54 Ben Cooksley wrote:
I wrote this a bit too quickly.
The correct url is
Hi all,
first, brief introductionon what this is:
during a Bof about scripting in applications at Akademy it occurred that some
applications may be interested by the functionality provided by
Plasma::Package, provided it was on a lower tier.
Since I already had kindof the idea of making Package
On Sept. 16, 2014, 10:33 a.m., Marco Martin wrote:
this approach is probably better than
https://git.reviewboard.kde.org/r/120040/
I think we'll need both. We still need to rename the kdesu binary, no?
- Maarten
---
This is an
On Sept. 16, 2014, 10:33 a.m., Marco Martin wrote:
this approach is probably better than
https://git.reviewboard.kde.org/r/120040/
Maarten De Meyer wrote:
I think we'll need both. We still need to rename the kdesu binary, no?
if it goes in libexec yes, otherwise if it goes in
See http://build.kde.org/job/kdelibs_stable/1180/changes
Changes:
[faure] Fix test failure in chroot, reported by maxyz
--
[...truncated 11001 lines...]
[ 32%] Building CXX object kdeui/CMakeFiles/kdeui.dir/widgets/khelpmenu.o
[ 32%]
El Dimarts, 16 de setembre de 2014, a les 12:37:31, Milian Wolff va escriure:
On Tuesday 16 September 2014 21:50:57 Ben Cooksley wrote:
On Tue, Sep 16, 2014 at 9:45 PM, Martin Gräßlin mgraess...@kde.org
wrote:
On Tuesday 16 September 2014 21:23:54 Ben Cooksley wrote:
I wrote this a bit
See http://build.kde.org/job/kdelibs_stable/1181/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
36 matches
Mail list logo