Re: [kde-freebsd] [SVN Commit] area51/KDE/net-im/kopete-kde4
I build with "make install WITH_DEBUG=yes" Right? If not correct, where to read about it? Application: Kopete (kopete), signal: Segmentation fault [Switching to Thread 82004c000 (LWP 100187/kopete)] [Current thread is 1 (Thread 82004c000 (LWP 100187/kopete))] Thread 4 (Thread 812806400 (LWP 100130/kopete)): [KCrash Handler] #8 0x in ?? () #9 0x00081f6cc31c in tls1_mac () from /usr/lib/libssl.so.7 #10 0x00081f6d4d2f in ssl3_write_bytes () from /usr/lib/libssl.so.7 #11 0x00081f6d4923 in ssl3_write_bytes () from /usr/lib/libssl.so.7 #12 0x00081f6dc759 in ssl3_do_write () from /usr/lib/libssl.so.7 #13 0x00081f6b4618 in ssl3_connect () from /usr/lib/libssl.so.7 #14 0x00081f471888 in opensslQCAPlugin::MyTLSContext::priv_handshake () from /usr/local/lib/qt4/plugins/crypto/libqca-ossl.so #15 0x00081f470b5d in opensslQCAPlugin::MyTLSContext::update () from /usr/local/lib/qt4/plugins/crypto/libqca-ossl.so #16 0x00080aad1c5b in QCA::TLS::Private::update () from /usr/local/lib/libqca.so.2 #17 0x00080aacf49d in QCA::TLS::writeIncoming () from /usr/local/lib/libqca.so.2 #18 0x00081e291104 in SecureStream::bs_readyRead (this=) at /usr/ports/net-im/kopete-kde4/work/kopete-4.12.1/protocols/jabber/libiris/src/xmpp/xmpp-core/securestream.cpp:203 #19 0x0008050ea522 in QMetaObject::activate () from /usr/local/lib/qt4/libQtCore.so.4 #20 0x0008050ea522 in QMetaObject::activate () from /usr/local/lib/qt4/libQtCore.so.4 #21 0x00081e202e67 in QTcpSocketSignalRelay::qt_static_metacall (_o=, _c=, _id=, _a=) at bsocket.moc:158 #22 0x0008050e61fe in QObject::event () from /usr/local/lib/qt4/libQtCore.so.4 #23 0x0008058eb5cb in QApplicationPrivate::notify_helper () from /usr/local/lib/qt4/libQtGui.so.4 #24 0x0008058ee2e8 in QApplication::notify () from /usr/local/lib/qt4/libQtGui.so.4 #25 0x00080447b190 in KApplication::notify () from /usr/local/lib/libkdeui.so.5 #26 0x0008050d3145 in QCoreApplication::notifyInternal () from /usr/local/lib/qt4/libQtCore.so.4 #27 0x0008050d3c7b in QCoreApplicationPrivate::sendPostedEvents () from /usr/local/lib/qt4/libQtCore.so.4 #28 0x000805100038 in QEventDispatcherGlib::QEventDispatcherGlib () from /usr/local/lib/qt4/libQtCore.so.4 #29 0x00080c312a02 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0 #30 0x00080c312da3 in g_main_context_iterate () from /usr/local/lib/libglib-2.0.so.0 #31 0x00080c312e34 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0 #32 0x0008050ff77e in QEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtCore.so.4 #33 0x00080598b44d in QX11Info::isCompositingManagerRunning () from /usr/local/lib/qt4/libQtGui.so.4 #34 0x0008050d0717 in QEventLoop::exec () from /usr/local/lib/qt4/libQtCore.so.4 #35 0x0008050d36dd in QCoreApplication::exec () from /usr/local/lib/qt4/libQtCore.so.4 #36 0x004162f6 in main (argc=, argv=0x7fffd670) at /usr/ports/net-im/kopete-kde4/work/kopete-4.12.1/kopete/main.cpp:105 Thread 3 (Thread 81280c800 (LWP 100133/kopete)): #0 0x0008072c111a in kevent () from /lib/libc.so.7 #1 0x0008050b517a in QProcessEnvironment::systemEnvironment () from /usr/local/lib/qt4/libQtCore.so.4 #2 0x000804fd909c in QThreadStorageData::finish () from /usr/local/lib/qt4/libQtCore.so.4 #3 0x000806f8f4a4 in pthread_create () from /lib/libthr.so.3 #4 0x in ?? () Thread 2 (Thread 81280e000 (LWP 100147/kopete)): #0 0x0008072c10fa in _clock_gettime () from /lib/libc.so.7 #1 0x000805034186 in QElapsedTimer::clockType () from /usr/local/lib/qt4/libQtCore.so.4 #2 0x0008051013f2 in QEventDispatcherUNIXPrivate::processThreadWakeUp () from /usr/local/lib/qt4/libQtCore.so.4 #3 0x0008050ffd9c in QEventDispatcherGlib::QEventDispatcherGlib () from /usr/local/lib/qt4/libQtCore.so.4 #4 0x00080c312355 in g_main_context_prepare () from /usr/local/lib/libglib-2.0.so.0 #5 0x00080c312c5b in g_main_context_iterate () from /usr/local/lib/libglib-2.0.so.0 #6 0x00080c312e34 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0 #7 0x0008050ff7af in QEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtCore.so.4 #8 0x0008050d0717 in QEventLoop::exec () from /usr/local/lib/qt4/libQtCore.so.4 #9 0x00080aa7ef87 in QCA::SyncThread::run () from /usr/local/lib/libqca.so.2 #10 0x000804fd909c in QThreadStorageData::finish () from /usr/local/lib/qt4/libQtCore.so.4 #11 0x000806f8f4a4 in pthread_create () from /lib/libthr.so.3 #12 0x in ?? () Thread 1 (Thread 82004c000 (LWP 100187/kopete)): #0 0x0008072c10fa in _clock_gettime () from /lib/libc.so.7 #1 0x000805034186 in QElapsedTimer::clockType () from /usr/local/lib/qt4/libQtCore.so.4 #2 0x0008051013f2 in QEventDispatcherUNIXPrivate::processThreadWakeUp () from /usr/local/lib/qt4/libQtCore.so.4 #3 0x0008050ffd9c in QEventDispa
Re: [kde-freebsd] [SVN Commit] area51/KDE/net-im/kopete-kde4
Please reply back to the list, it's not the first time you end up sending your replies only to me... "Alex V. Petrov" writes: > I build with "make install WITH_DEBUG=yes" > Right? > If not correct, where to read about it? > > Application: Kopete (kopete), signal: Segmentation fault > > [Switching to Thread 82004c000 (LWP 100187/kopete)] > > [Current thread is 1 (Thread 82004c000 (LWP 100187/kopete))] > > > Thread 4 (Thread 812806400 (LWP 100130/kopete)): > > [KCrash Handler] > > #8 0x in ?? () > > #9 0x00081f6cc31c in tls1_mac () from /usr/lib/libssl.so.7 > > #10 0x00081f6d4d2f in ssl3_write_bytes () from /usr/lib/libssl.so.7 > > #11 0x00081f6d4923 in ssl3_write_bytes () from /usr/lib/libssl.so.7 > > #12 0x00081f6dc759 in ssl3_do_write () from /usr/lib/libssl.so.7 > > #13 0x00081f6b4618 in ssl3_connect () from /usr/lib/libssl.so.7 > > #14 0x00081f471888 in opensslQCAPlugin::MyTLSContext::priv_handshake () > from /usr/local/lib/qt4/plugins/crypto/libqca-ossl.so > > #15 0x00081f470b5d in opensslQCAPlugin::MyTLSContext::update () from > /usr/local/lib/qt4/plugins/crypto/libqca-ossl.so > > #16 0x00080aad1c5b in QCA::TLS::Private::update () from > /usr/local/lib/libqca.so.2 > > #17 0x00080aacf49d in QCA::TLS::writeIncoming () from > /usr/local/lib/libqca.so.2 > > #18 0x00081e291104 in SecureStream::bs_readyRead (this= out>) at > /usr/ports/net-im/kopete-kde4/work/kopete-4.12.1/protocols/jabber/libiris/src/xmpp/xmpp-core/securestream.cpp:203 [..] > Thread 1 (Thread 82004c000 (LWP 100187/kopete)): [...] > #10 0x00081e2f7e0b in XMPP::NetTrackerThread::run (this=0x820240be0) at > /usr/ports/net-im/kopete-kde4/work/kopete-4.12.1/protocols/jabber/libiris/src/irisnet/corelib/netinterface.cpp:168 Is anyone else on the list able to reproduce this? ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [SVN Commit] area51/KDE
SVN commit 9951 by rakuco: kde4-l10n-*: Fix plist. M +1 -1 arabic/kde4-l10n/pkg-plist M +1 -1 chinese/kde4-l10n-zh_CN/pkg-plist M +1 -1 chinese/kde4-l10n-zh_TW/pkg-plist M +5 -17 french/kde4-l10n/pkg-plist M +5 -5 german/kde4-l10n/pkg-plist M +1 -1 hebrew/kde4-l10n/pkg-plist M +1 -1 hungarian/kde4-l10n/pkg-plist M +1 -1 japanese/kde4-l10n/pkg-plist M +1 -2 korean/kde4-l10n/pkg-plist M +1 -1 misc/kde4-l10n-bg/pkg-plist M +1 -1 misc/kde4-l10n-bs/pkg-plist M +1 -1 misc/kde4-l10n-ca/pkg-plist M +1 -1 misc/kde4-l10n-ca_valencia/pkg-plist M +1 -1 misc/kde4-l10n-cs/pkg-plist M +1 -1 misc/kde4-l10n-csb/pkg-plist M +1 -1 misc/kde4-l10n-da/pkg-plist M +1 -1 misc/kde4-l10n-el/pkg-plist M +1 -1 misc/kde4-l10n-en_GB/pkg-plist M +1 -1 misc/kde4-l10n-eo/pkg-plist M +5 -19 misc/kde4-l10n-es/pkg-plist M +5 -5 misc/kde4-l10n-et/pkg-plist M +1 -1 misc/kde4-l10n-eu/pkg-plist M +1 -1 misc/kde4-l10n-fa/pkg-plist M +1 -1 misc/kde4-l10n-fi/pkg-plist M +1 -1 misc/kde4-l10n-ga/pkg-plist M +5 -5 misc/kde4-l10n-gl/pkg-plist M +1 -1 misc/kde4-l10n-hi/pkg-plist M +1 -1 misc/kde4-l10n-hr/pkg-plist M +1 -1 misc/kde4-l10n-is/pkg-plist M +5 -5 misc/kde4-l10n-it/pkg-plist M +1 -1 misc/kde4-l10n-kk/pkg-plist M +1 -1 misc/kde4-l10n-km/pkg-plist M +1 -1 misc/kde4-l10n-lt/pkg-plist M +1 -1 misc/kde4-l10n-lv/pkg-plist M +1 -1 misc/kde4-l10n-mai/pkg-plist M +1 -1 misc/kde4-l10n-mk/pkg-plist M +1 -1 misc/kde4-l10n-mr/pkg-plist M +1 -1 misc/kde4-l10n-nb/pkg-plist M +1 -1 misc/kde4-l10n-nds/pkg-plist M +5 -5 misc/kde4-l10n-nl/pkg-plist M +1 -1 misc/kde4-l10n-nn/pkg-plist M +1 -1 misc/kde4-l10n-pa/pkg-plist M +1 -1 misc/kde4-l10n-ro/pkg-plist M +1 -1 misc/kde4-l10n-sk/pkg-plist M +1 -1 misc/kde4-l10n-sl/pkg-plist M +4 -4 misc/kde4-l10n-sr/pkg-plist M +5 -5 misc/kde4-l10n-sv/pkg-plist M +1 -1 misc/kde4-l10n-tg/pkg-plist M +1 -1 misc/kde4-l10n-tr/pkg-plist M +1 -1 misc/kde4-l10n-ug/pkg-plist M +5 -7 polish/kde4-l10n/pkg-plist M +5 -8 portuguese/kde4-l10n-pt_BR/pkg-plist M +5 -5 portuguese/kde4-l10n/pkg-plist M +5 -5 russian/kde4-l10n/pkg-plist M +5 -7 ukrainian/kde4-l10n/pkg-plist M +1 -1 vietnamese/kde4-l10n/pkg-plist ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
On Tue, 28 Jan 2014 11:21:39 -0200 Raphael Kubo da Costa wrote: > Max Brazhnikov writes: > > > On Tue, 28 Jan 2014 07:11:32 -0200 Raphael Kubo da Costa wrote: > >> As we're finally close to getting the 4.12.1 ports into a reasonable > >> stable where everything builds, I'd like to start discussing merging > >> area51 back into ports -- we've already skipped the whole 4.11 release > >> cycle. > >> > >> As I see it, the biggest question is what to do with WITH_NEW_XORG=no: > >> kde4-workspace will not build with the ancient version of Mesa that gets > >> build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster > >> does not enable this variable on its 8- and 9- builds, which mean we > >> wouldn't get part of the KDE packages built for those releases at all. > > > > I don't see a problem here, we simply mark kde4-workspace as IGNORE. > > It's not a big package loss: only 25 ports depends on kde-workpace, half of > > them are plasmoinds, window decoration and style plugins. There is almost no > > software that can be used outside KDE desktop. > > That's true, but kde4-workspace is kind of "the KDE desktop" itself -- > people on 8- and 9- (as well as 10.0-RELEASE) would be unable to simply > call "pkg install kde4" and get a working KDE desktop. Look at the bright side: hordes of angry users start bombarding xorg maintainers to enable WITH_NEW_XORG! ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
Max Brazhnikov writes: > On Tue, 28 Jan 2014 07:11:32 -0200 Raphael Kubo da Costa wrote: >> As we're finally close to getting the 4.12.1 ports into a reasonable >> stable where everything builds, I'd like to start discussing merging >> area51 back into ports -- we've already skipped the whole 4.11 release >> cycle. >> >> As I see it, the biggest question is what to do with WITH_NEW_XORG=no: >> kde4-workspace will not build with the ancient version of Mesa that gets >> build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster >> does not enable this variable on its 8- and 9- builds, which mean we >> wouldn't get part of the KDE packages built for those releases at all. > > I don't see a problem here, we simply mark kde4-workspace as IGNORE. > It's not a big package loss: only 25 ports depends on kde-workpace, half of > them are plasmoinds, window decoration and style plugins. There is almost no > software that can be used outside KDE desktop. That's true, but kde4-workspace is kind of "the KDE desktop" itself -- people on 8- and 9- (as well as 10.0-RELEASE) would be unable to simply call "pkg install kde4" and get a working KDE desktop. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [SVN Commit] area51/KDE/x11/kde4
SVN commit 9950 by rakuco: kde4: NO_INTSALL -> NO_INSTALL M +1 -1 Makefile ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
On Tue, 28 Jan 2014 07:11:32 -0200 Raphael Kubo da Costa wrote: > As we're finally close to getting the 4.12.1 ports into a reasonable > stable where everything builds, I'd like to start discussing merging > area51 back into ports -- we've already skipped the whole 4.11 release > cycle. > > As I see it, the biggest question is what to do with WITH_NEW_XORG=no: > kde4-workspace will not build with the ancient version of Mesa that gets > build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster > does not enable this variable on its 8- and 9- builds, which mean we > wouldn't get part of the KDE packages built for those releases at all. I don't see a problem here, we simply mark kde4-workspace as IGNORE. It's not a big package loss: only 25 ports depends on kde-workpace, half of them are plasmoinds, window decoration and style plugins. There is almost no software that can be used outside KDE desktop. Max ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] [SVN Commit] area51/KDE/net-im/kopete-kde4
"Alex V. Petrov" writes: > Kopete has been updated, but when connected to talk.google.com, the > application crashes. I watch it on all versions of area51, since > 4.11.x Please build with debug symbols and provide a backtrace. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] [SVN Commit] area51/KDE/net-im/kopete-kde4
Kopete has been updated, but when connected to talk.google.com, the application crashes. I watch it on all versions of area51, since 4.11.x 2014-01-28 Raphael Kubo da Costa > SVN commit 9944 by rakuco: > > kopete-kde4: Adjust dependencies. > > - Switch from security/libotr3 to security/libotr (v4), as required by > Kopete. > - Depend on devel/jsoncpp (used by the Jabber plugin with Google Talk > libjingle support). > > Relevant items that are listed as not found when building kopete are: > - libsrtp (the latest stable release does not ship a shared library, from > what I could see Linux distros either fetch from a new git repository > from > a different upstream or patch the code themselves to create .so's). We > could switch to a git tarball from the new repository in the future, but > until then the detection will keep failing. > - libkleo (kdepim simply does not install the headers being looked for > here, > I really don't understand what the Kopete plugin author tried to do and > how it ever worked for him). > > > > M +3 -2 Makefile > > > ___ > kde-freebsd mailing list > kde-freebsd@kde.org > https://mail.kde.org/mailman/listinfo/kde-freebsd > See also http://freebsd.kde.org/ for latest information > -- -- Alex V. Petrov ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [SVN Commit] area51/KDE/graphics/kdegraphics4-thumbnailers
SVN commit 9949 by rakuco: kdegraphics4-thumbnailers: Depend on pkgconfig. Yet another case of badly written Find*.cmake that requires pkg-config. M +1 -1 Makefile ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [SVN Commit] area51/KDE/net/kdenetwork4-strigi-analyzers
SVN commit 9948 by rakuco: kdenetwork4-strigi-analyzers: Write something in pkg-descr. kdenetwork4 was failing to install with Installing kdenetwork-strigi-analyzers-4.12.1...pkg-static: package field incomplete: description While here, correctly set svn:mime-type to text/plain, this is not a binary file. MMpkg-descr ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [SVN Commit] area51/CALLIGRA/editors/calligra
SVN commit 9947 by rakuco: Oops, bump PORTREVISION in CALLIGRA/ after r9946 too M +1 -0 Makefile ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [SVN Commit] area51
SVN commit 9946 by rakuco: libkdcraw-kde4: Fix plist. This involves a shlib version bump, which has been done to the dependent ports in PORTS/ (the ones in KDE/ have been updated anyway). M +2 -5 KDE/graphics/libkdcraw-kde4/pkg-plist M +1 -0 PORTS/graphics/digikam-kde4/Makefile M +1 -0 PORTS/graphics/kphotoalbum-kde4/Makefile M +1 -0 PORTS/graphics/libkipiplugins/Makefile ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [SVN Commit] area51/KDE/net-im/kopete-kde4
SVN commit 9945 by rakuco: kopete-kde4: Fix plist M +1 -19 pkg-plist ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [SVN Commit] area51/KDE/net-im/kopete-kde4
SVN commit 9944 by rakuco: kopete-kde4: Adjust dependencies. - Switch from security/libotr3 to security/libotr (v4), as required by Kopete. - Depend on devel/jsoncpp (used by the Jabber plugin with Google Talk libjingle support). Relevant items that are listed as not found when building kopete are: - libsrtp (the latest stable release does not ship a shared library, from what I could see Linux distros either fetch from a new git repository from a different upstream or patch the code themselves to create .so's). We could switch to a git tarball from the new repository in the future, but until then the detection will keep failing. - libkleo (kdepim simply does not install the headers being looked for here, I really don't understand what the Kopete plugin author tried to do and how it ever worked for him). M +3 -2 Makefile ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
On 28-1-2014 10:52, Schaich Alonso wrote: On Tue, 28 Jan 2014 07:11:32 -0200 Raphael Kubo da Costa wrote: As we're finally close to getting the 4.12.1 ports into a reasonable stable where everything builds, I'd like to start discussing merging area51 back into ports -- we've already skipped the whole 4.11 release cycle. As I see it, the biggest question is what to do with WITH_NEW_XORG=no: kde4-workspace will not build with the ancient version of Mesa that gets build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster does not enable this variable on its 8- and 9- builds, which mean we wouldn't get part of the KDE packages built for those releases at all. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information Hi In a mail to stable@ which was not replied so far, ama...@li.ru reported on 2014-01-22 that he can't build even cairo (poppler) without WITH_NEW_XORG, which both are dependecies to KDE4. I have no setup to verify this breakage at the moment, though should this be true it means we have a broken default setup on FreeBSD 8, 9 and 10. Alonso As maintainer of both, I can say that I'm not aware of any problems with either port. I will check the mail report and see if I can find out where that breakage comes from. -Koop ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
On Tue, 28 Jan 2014 07:11:32 -0200 Raphael Kubo da Costa wrote: > As we're finally close to getting the 4.12.1 ports into a reasonable > stable where everything builds, I'd like to start discussing merging > area51 back into ports -- we've already skipped the whole 4.11 release > cycle. > > As I see it, the biggest question is what to do with WITH_NEW_XORG=no: > kde4-workspace will not build with the ancient version of Mesa that gets > build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster > does not enable this variable on its 8- and 9- builds, which mean we > wouldn't get part of the KDE packages built for those releases at all. > ___ > kde-freebsd mailing list > kde-freebsd@kde.org > https://mail.kde.org/mailman/listinfo/kde-freebsd > See also http://freebsd.kde.org/ for latest information Hi In a mail to stable@ which was not replied so far, ama...@li.ru reported on 2014-01-22 that he can't build even cairo (poppler) without WITH_NEW_XORG, which both are dependecies to KDE4. I have no setup to verify this breakage at the moment, though should this be true it means we have a broken default setup on FreeBSD 8, 9 and 10. Alonso ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
On 28-1-2014 10:11, Raphael Kubo da Costa wrote: As we're finally close to getting the 4.12.1 ports into a reasonable stable where everything builds, I'd like to start discussing merging area51 back into ports -- we've already skipped the whole 4.11 release cycle. As I see it, the biggest question is what to do with WITH_NEW_XORG=no: kde4-workspace will not build with the ancient version of Mesa that gets build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster does not enable this variable on its 8- and 9- builds, which mean we wouldn't get part of the KDE packages built for those releases at all. Just a note with my x11@ hat on: As you probably know WITH_NEW_XORG is default on HEAD. The current plan is to enable this on 10-stable in time for 10.1-R but that depends on if vt(9) is merged by then. There is currently no reason to believe this won't happen. -Koop ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
As we're finally close to getting the 4.12.1 ports into a reasonable stable where everything builds, I'd like to start discussing merging area51 back into ports -- we've already skipped the whole 4.11 release cycle. As I see it, the biggest question is what to do with WITH_NEW_XORG=no: kde4-workspace will not build with the ancient version of Mesa that gets build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster does not enable this variable on its 8- and 9- builds, which mean we wouldn't get part of the KDE packages built for those releases at all. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] [SVN Commit] area51
"Alex V. Petrov" writes: > ===>>> Installation of kopete-4.12.1 (net-im/kopete-kde4) failed > ===>>> Aborting update We're almost there, bear with us a little longer. My latest x11/kde4 build failed on kopete (that has a few new dependencies, some of which we still need to create a port for) and libkdcraw (shlib bump + we need to bump PORTREVISION in dependent ports). ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
